[Serusers] Call transfer
jorain
jorain at caliber.com.sg
Wed Dec 6 08:21:27 CET 2006
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 at lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20061206/d9c50293/attachment.htm>
More information about the sr-users
mailing list