Hi all,
Is it deal with the ctd.sh script? Configure inside loose_route()?
I can get the REFER message but no responses (202 Accepted and NOTIFY) to it. So I send reply 202 inside loose_route if method=REFER.
After that, inside ethereal, I can see the code 202 response to REFER. However, It send REFER again and after a while 408 TIMEOUT.
This is what i configured:
if(loose_route()){ if(method=="BYE"){ setflag(1); setflag(2); };
if(method=="REFER"){ sl_send_reply("202","Accepted"); };
t_relay(); break; };
Please help.
Thanks in advance
Regards, jorain ----- Original Message ----- From: Greger V. Teigre To: jorain Sent: Tuesday, December 05, 2006 9:30 PM Subject: Re: [Serusers] Call transfer
cc serusers
jorain wrote: Thanks Greger,
Could you give me some clues how to do that or some references about it? I really have no idea.
Thanks again.
Regards, jorain ----- Original Message ----- From: Greger V. Teigre To: jorain Cc: SER+RTPproxy Sent: Monday, December 04, 2006 7:48 PM Subject: Re: [Serusers] Call transfer
Well, yes, you have to route REFER, and you should allow NOTIFYs. g-)
jorain wrote: Hi all,
I have some question about call transfer.
When I press transfer key follow by the new destination and "send", I can see the REFER message inside ethereal but after that request timeout error(408).
Inside REFER message, i can see the refer-to and referred-by values are correct. Do I need to add something inside ser.cfg to enable call transfering? Because I cannot find any sample codings regarding ser call transfer.
Thanks for any help.
Regards, jorain ------------------------------------------------------------------------ _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
You need to relay REFER to the other UA, SER should not be involved. The NOTIFY should not be stopped either, but relayed. Normally, REFER should be t_relay'ed directly to the UA, but you may have some NAT issues as the UA never answers. Look at the REFER and see where it goes. g-)
jorain wrote:
Hi all,
Is it deal with the ctd.sh script? Configure inside loose_route()?
I can get the REFER message but no responses (202 Accepted and NOTIFY) to it. So I send reply 202 inside loose_route if method=REFER.
After that, inside ethereal, I can see the code 202 response to REFER. However, It send REFER again and after a while 408 TIMEOUT.
This is what i configured:
if(loose_route()){ if(method=="BYE"){ setflag(1); setflag(2); };
if(method=="REFER"){ sl_send_reply("202","Accepted"); }; t_relay(); break;
};
Please help.
Thanks in advance
Regards, jorain
----- Original Message ----- *From:* Greger V. Teigre <mailto:greger@teigre.com> *To:* jorain <mailto:jorain@caliber.com.sg> *Sent:* Tuesday, December 05, 2006 9:30 PM *Subject:* Re: [Serusers] Call transfer cc serusers jorain wrote:
Thanks Greger, Could you give me some clues how to do that or some references about it? I really have no idea. Thanks again. Regards, jorain ----- Original Message ----- *From:* Greger V. Teigre <mailto:greger@teigre.com> *To:* jorain <mailto:jorain@caliber.com.sg> *Cc:* SER+RTPproxy <mailto:serusers@lists.iptel.org> *Sent:* Monday, December 04, 2006 7:48 PM *Subject:* Re: [Serusers] Call transfer Well, yes, you have to route REFER, and you should allow NOTIFYs. g-) jorain wrote:
Hi all, I have some question about call transfer. When I press transfer key follow by the new destination and "send", I can see the REFER message inside ethereal but after that request timeout error(408). Inside REFER message, i can see the refer-to and referred-by values are correct. Do I need to add something inside ser.cfg to enable call transfering? Because I cannot find any sample codings regarding ser call transfer. Thanks for any help. Regards, jorain ------------------------------------------------------------------------ _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Hi Greger
Thanks, I got it.
Regards, jorain ----- Original Message ----- From: Greger V. Teigre To: jorain Cc: SER+RTPproxy Sent: Wednesday, December 06, 2006 8:43 PM Subject: Re: [Serusers] Call transfer
You need to relay REFER to the other UA, SER should not be involved. The NOTIFY should not be stopped either, but relayed. Normally, REFER should be t_relay'ed directly to the UA, but you may have some NAT issues as the UA never answers. Look at the REFER and see where it goes. g-)
jorain wrote: Hi all,
Is it deal with the ctd.sh script? Configure inside loose_route()?
I can get the REFER message but no responses (202 Accepted and NOTIFY) to it. So I send reply 202 inside loose_route if method=REFER.
After that, inside ethereal, I can see the code 202 response to REFER. However, It send REFER again and after a while 408 TIMEOUT.
This is what i configured:
if(loose_route()){ if(method=="BYE"){ setflag(1); setflag(2); };
if(method=="REFER"){ sl_send_reply("202","Accepted"); };
t_relay(); break; };
Please help.
Thanks in advance
Regards, jorain ----- Original Message ----- From: Greger V. Teigre To: jorain Sent: Tuesday, December 05, 2006 9:30 PM Subject: Re: [Serusers] Call transfer
cc serusers
jorain wrote: Thanks Greger,
Could you give me some clues how to do that or some references about it? I really have no idea.
Thanks again.
Regards, jorain ----- Original Message ----- From: Greger V. Teigre To: jorain Cc: SER+RTPproxy Sent: Monday, December 04, 2006 7:48 PM Subject: Re: [Serusers] Call transfer
Well, yes, you have to route REFER, and you should allow NOTIFYs. g-)
jorain wrote: Hi all,
I have some question about call transfer.
When I press transfer key follow by the new destination and "send", I can see the REFER message inside ethereal but after that request timeout error(408).
Inside REFER message, i can see the refer-to and referred-by values are correct. Do I need to add something inside ser.cfg to enable call transfering? Because I cannot find any sample codings regarding ser call transfer.
Thanks for any help.
Regards, jorain -------------------------------------------------------------------- _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers ---------------------------------------------------------------------------- _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers