park_after_bridge does not work if far end does 180 Ringing
Hello, I see a different behaviour for 183 Ringing vs 180 Ringing and a 408 Request Timeout response message with regards to park_after_bridge: 1) I have "park_after_bridge=true". 2) Do a bridge to a PSTN number (SIP Trunk) 3) After sometime freeswitch receives 408 Request Timeout message: a) if carrier had sent 183 Ringing (in band ring back tone) the a-leg is parked after the 408 timeout message. b) if carrier had sent 180 Ringing, the aleg is hungup after timeout (408 message) Is this a bug? Is there a work around? Thanks, Ali Pey
183 means early media and the bridge by default is considered successful by FreeSWITCH --> https://freeswitch.org/confluence/display/FREESWITCH/Early+Media#EarlyMedia-... "Successful"CallAttempt So park_after_bridge will only park the call if FreeSWITCH has received 183 or 200 from far end. Not a bug, expected behavior. Let me know if I'm wrong On Tue, Mar 17, 2015 at 1:04 PM, Ali Pey <alipey@gmail.com> wrote:
Hello,
I see a different behaviour for 183 Ringing vs 180 Ringing and a 408 Request Timeout response message with regards to park_after_bridge:
1) I have "park_after_bridge=true". 2) Do a bridge to a PSTN number (SIP Trunk) 3) After sometime freeswitch receives 408 Request Timeout message: a) if carrier had sent 183 Ringing (in band ring back tone) the a-leg is parked after the 408 timeout message. b) if carrier had sent 180 Ringing, the aleg is hungup after timeout (408 message)
Is this a bug? Is there a work around?
Thanks, Ali Pey
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Ítalo Rossi
if you ignore_early_media you can make 180 and 183 act the same.
On Mar 17, 2015, at 1:34 PM, Ítalo Rossi <italorossib@gmail.com> wrote:
183 means early media and the bridge by default is considered successful by FreeSWITCH --> https://freeswitch.org/confluence/display/FREESWITCH/Early+Media#EarlyMedia-... <https://freeswitch.org/confluence/display/FREESWITCH/Early+Media#EarlyMedia-A>"Successful"CallAttempt
So park_after_bridge will only park the call if FreeSWITCH has received 183 or 200 from far end.
Not a bug, expected behavior.
Let me know if I'm wrong
On Tue, Mar 17, 2015 at 1:04 PM, Ali Pey <alipey@gmail.com <mailto:alipey@gmail.com>> wrote: Hello,
I see a different behaviour for 183 Ringing vs 180 Ringing and a 408 Request Timeout response message with regards to park_after_bridge:
1) I have "park_after_bridge=true". 2) Do a bridge to a PSTN number (SIP Trunk) 3) After sometime freeswitch receives 408 Request Timeout message: a) if carrier had sent 183 Ringing (in band ring back tone) the a-leg is parked after the 408 timeout message. b) if carrier had sent 180 Ringing, the aleg is hungup after timeout (408 message)
Is this a bug? Is there a work around?
Thanks, Ali Pey
I use uuid_bridge to connect two uuids. I have set park_after_bridge=true. No matter if I set ignore_early_media to true or false, if b-leg does 183 Ringing and then times out (408 timeout response), a-leg will be parked. If b-leg does 180 Ringing and then times out, a-leg is dropped. How can I make sure a-leg will always be parked if b-leg is parked? This seems a bug to me. Regards, Ali Pey On Tue, Mar 17, 2015 at 2:11 PM, Michael Jerris <mike@jerris.com> wrote:
if you ignore_early_media you can make 180 and 183 act the same.
On Mar 17, 2015, at 1:34 PM, Ítalo Rossi <italorossib@gmail.com> wrote:
183 means early media and the bridge by default is considered successful by FreeSWITCH --> https://freeswitch.org/confluence/display/FREESWITCH/Early+Media#EarlyMedia-... "Successful"CallAttempt
So park_after_bridge will only park the call if FreeSWITCH has received 183 or 200 from far end.
Not a bug, expected behavior.
Let me know if I'm wrong
On Tue, Mar 17, 2015 at 1:04 PM, Ali Pey <alipey@gmail.com> wrote:
Hello,
I see a different behaviour for 183 Ringing vs 180 Ringing and a 408 Request Timeout response message with regards to park_after_bridge:
1) I have "park_after_bridge=true". 2) Do a bridge to a PSTN number (SIP Trunk) 3) After sometime freeswitch receives 408 Request Timeout message: a) if carrier had sent 183 Ringing (in band ring back tone) the a-leg is parked after the 408 timeout message. b) if carrier had sent 180 Ringing, the aleg is hungup after timeout (408 message)
Is this a bug? Is there a work around?
Thanks, Ali Pey
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (3)
-
Ali Pey
-
Michael Jerris
-
Ítalo Rossi