Hi Michael, Thanks, that works in scenario when B legs response with 100 and then let's say 486. But if B legs do ringing, i.e. 100, 180/183, 486 it doesn't work. I found this in wiki "By the way, you'll be unable to rewrite the hangup cause for a bridge that gets a 180 or 183 packet from the gateway before getting a 4xx, 5xx or 6xx packet (because those bridges don't 'fail')." I understand that continue_on_fail won't help with this scenario. I see that's a popular topic in the list, but nobody got a solution. BR, Alex. From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Michael Collins Sent: Wednesday, August 29, 2012 6:21 PM To: FreeSWITCH Users Help Subject: Re: [Freeswitch-users] Prevent A leg from hangup after bridge with inbound ESL socket Try this: http://wiki.freeswitch.org/wiki/Channel_Variables#continue_on_fail -MC On Wed, Aug 29, 2012 at 6:57 AM, Alex Massover <alex@jajah.com<mailto:alex@jajah.com>> wrote: Hi, I have a very simple dialplan that just do park for incoming calls. All rest of leg management is done via ESL inbound socket. I'm trying to do the same behavior like in this dialplan example, but from ESL inbound socket: <action application="set" data="hangup_after_bridge=false"/> <action application="bridge" data="sofia/internal/1001@$${domain}"/> <action application="bridge" data="sofia/internal/1002@$${domain}"/> The problem is with bridge API, if B leg doesn't answer (e.g. 404, or busy), A leg disconnects. But I'm trying to prevent A leg from disconnecting in order to do bridge to other place. Looks like hangup_after_bridge=false, park_after_bridge=true, transfer_after_bridge etc don't have any effect when bridge done from inbound socket. A leg disconnects always. Is there any way to keep A leg after bridge with inbound socket? I'm aware of originate, but prefer to user bridge. -- Best Regards, Alex Massover _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org<mailto: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 -- Michael S Collins Twitter: @mercutioviz http://www.FreeSWITCH.org http://www.ClueCon.com http://www.OSTAG.org

Hi, We tried that, it doesn't do a trick, the bridge app still assumes success, even if 180 is not forwarded to A leg. But I think the problem is related to ESL socket, especially to inbound socket. I'm pretty sure that all these things work with dailplan, and as far as I remember even with outbound socket it's much easier. But looks like outbound socket bypass some of these flags, as channel is control by XML dialplan, but then is bridged by ESL API and not sure what exactly happens. I understand that hangup_after_bridge=false may not work, as it's not clear what should happen with the channel in case of inbound socket (as dialplan is ended), but no reason for park_after_bridge=true not to park a channel. Maybe it worth to fill a bug in JIRA about park_after_bridge=true and ESL inbound socket. I'll do some more clear tests and will fill one. BR, Alex. From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Michael Collins Sent: Thursday, August 30, 2012 7:17 PM To: FreeSWITCH Users Help Subject: Re: [Freeswitch-users] Prevent A leg from hangup after bridge with inbound ESL socket If that's the case then you also need ignore_early_media=true: <action application="bridge" data="{ignore_early_media=true}sofia/internal/1001@$${domain}"/> If you don't ignore early media then the bridge app assumes that when it receives media from the far end that the bridge is "successful" even if you don't actually get a 200OK. The caveat is that since you're ignoring early media (i.e. ringing) from the B leg that you will need to supply some sort of ringing indicator to the A leg. The good news is that you can do whatever you want; just use the ring_back chan var. -MC On Thu, Aug 30, 2012 at 12:07 AM, Alex Massover <alex@jajah.com<mailto:alex@jajah.com>> wrote: Hi Michael, Thanks, that works in scenario when B legs response with 100 and then let's say 486. But if B legs do ringing, i.e. 100, 180/183, 486 it doesn't work. I found this in wiki "By the way, you'll be unable to rewrite the hangup cause for a bridge that gets a 180 or 183 packet from the gateway before getting a 4xx, 5xx or 6xx packet (because those bridges don't 'fail')." I understand that continue_on_fail won't help with this scenario. I see that's a popular topic in the list, but nobody got a solution. BR, Alex. From: freeswitch-users-bounces@lists.freeswitch.org<mailto:freeswitch-users-bounces@lists.freeswitch.org> [mailto:freeswitch-users-bounces@lists.freeswitch.org<mailto:freeswitch-users-bounces@lists.freeswitch.org>] On Behalf Of Michael Collins Sent: Wednesday, August 29, 2012 6:21 PM To: FreeSWITCH Users Help Subject: Re: [Freeswitch-users] Prevent A leg from hangup after bridge with inbound ESL socket Try this: http://wiki.freeswitch.org/wiki/Channel_Variables#continue_on_fail -MC On Wed, Aug 29, 2012 at 6:57 AM, Alex Massover <alex@jajah.com<mailto:alex@jajah.com>> wrote: Hi, I have a very simple dialplan that just do park for incoming calls. All rest of leg management is done via ESL inbound socket. I'm trying to do the same behavior like in this dialplan example, but from ESL inbound socket: <action application="set" data="hangup_after_bridge=false"/> <action application="bridge" data="sofia/internal/1001@$${domain}"/> <action application="bridge" data="sofia/internal/1002@$${domain}"/> The problem is with bridge API, if B leg doesn't answer (e.g. 404, or busy), A leg disconnects. But I'm trying to prevent A leg from disconnecting in order to do bridge to other place. Looks like hangup_after_bridge=false, park_after_bridge=true, transfer_after_bridge etc don't have any effect when bridge done from inbound socket. A leg disconnects always. Is there any way to keep A leg after bridge with inbound socket? I'm aware of originate, but prefer to user bridge. -- Best Regards, Alex Massover _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org<mailto: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 -- Michael S Collins Twitter: @mercutioviz http://www.FreeSWITCH.org http://www.ClueCon.com http://www.OSTAG.org _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org<mailto: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 -- Michael S Collins Twitter: @mercutioviz http://www.FreeSWITCH.org http://www.ClueCon.com http://www.OSTAG.org

Hi All, Using version 1.2.9 Just wondering if this ever got resolved as i am having a similar issue. I am also using ESL inbound and my event driven script will answer the call, set the ringback to a UK tone, play 1 second of silence, then issue the bridge as follows: {ignore_early_media=true,continue_on_fail=true,park_after_bridge=true,hangup_after_bridge=false}sofia/external/ 200010006@sipserv.net Once this has all gone through everything works correctly when the user is available. When busy however the calling channel is ending the call rather than returning to park. I had anticipated collecting the CHANNEL_EXECUTE_COMPLETE event for the bridge command, reading the variable_DIALSTATUS for "BUSY" and then playing busy tone but it is just hanging up. Is there a clean way to resolve this? Even if its just setting the "busytone" equivalent of "ringback" that would probably do? Any help would be appreciated, Thanks, Callum ______________________________ Callum Guy Developer X-on Framlingham Technology Centre Station Road, Framlingham, Suffolk, IP13 9EZ T 0333 332 0116 E callum.guy@x-on.co.uk X-on is a trading name of Storacall Technology Ltd a limited company registered in England and Wales Registered Office : Avaland House, 110 London Road, Apsley, Hemel Hempstead, Herts, HP3 9SD Company Registration No. 2578478 This email has been sent from X-on.The contents and attachments are confidential to the sender and the intended addressees.If the message is received by anyone other than the addressee please return the message to the sender by replying to it and then delete the message from your computer without copying or disclosing the contents to anyone.Opinions, conclusions and statements of intent in this email are those of the sender and do not bind X-on unless confirmed by authorised representatives independently of this message.While best endeavours have been taken to avoid transmission of viruses, it is the responsibility of the recipient to scan for these.Please note emails sent to and from X-on are routinely monitored for record keeping and quality control, to ensure regulatory compliance and prevent unauthorised use of our systems. Please consider the environment before printing this email. On 3 September 2012 10:28, Peter Olsson <peter.olsson@visionutveckling.se>wrote:

try park_after_bridge=true, it should park the call again after the bridge, and keep it alive.

/Peter ________________________________ Från: freeswitch-users-bounces@lists.freeswitch.org [ freeswitch-users-bounces@lists.freeswitch.org] för Alex Massover [ alex@jajah.com] Skickat: den 3 september 2012 09:00 Till: FreeSWITCH Users Help Ämne: Re: [Freeswitch-users] Prevent A leg from hangup after bridge with inbound ESL socket

Hi,

We tried that, it doesn't do a trick, the bridge app still assumes success, even if 180 is not forwarded to A leg. But I think the problem is related to ESL socket, especially to inbound socket. I'm pretty sure that all these things work with dailplan, and as far as I remember even with outbound socket it's much easier. But looks like outbound socket bypass some of these flags, as channel is control by XML dialplan, but then is bridged by ESL API and not sure what exactly happens. I understand that hangup_after_bridge=false may not work, as it's not clear what should happen with the channel in case of inbound socket (as dialplan is ended), but no reason for park_after_bridge=true not to park a channel.

Maybe it worth to fill a bug in JIRA about park_after_bridge=true and ESL inbound socket. I'll do some more clear tests and will fill one.

BR, Alex.

From: freeswitch-users-bounces@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Michael Collins Sent: Thursday, August 30, 2012 7:17 PM To: FreeSWITCH Users Help Subject: Re: [Freeswitch-users] Prevent A leg from hangup after bridge with inbound ESL socket

If that's the case then you also need ignore_early_media=true: <action application="bridge" data="{ignore_early_media=true}sofia/internal/1001@$${domain}"/>

If you don't ignore early media then the bridge app assumes that when it receives media from the far end that the bridge is "successful" even if you don't actually get a 200OK. The caveat is that since you're ignoring early media (i.e. ringing) from the B leg that you will need to supply some sort of ringing indicator to the A leg. The good news is that you can do whatever you want; just use the ring_back chan var.

-MC On Thu, Aug 30, 2012 at 12:07 AM, Alex Massover <alex@jajah.com<mailto: alex@jajah.com>> wrote: Hi Michael,

Thanks, that works in scenario when B legs response with 100 and then let's say 486. But if B legs do ringing, i.e. 100, 180/183, 486 it doesn't work.

I found this in wiki "By the way, you'll be unable to rewrite the hangup cause for a bridge that gets a 180 or 183 packet from the gateway before getting a 4xx, 5xx or 6xx packet (because those bridges don't 'fail')."

I understand that continue_on_fail won't help with this scenario. I see that's a popular topic in the list, but nobody got a solution.

BR, Alex.

From: freeswitch-users-bounces@lists.freeswitch.org<mailto: freeswitch-users-bounces@lists.freeswitch.org> [mailto: freeswitch-users-bounces@lists.freeswitch.org<mailto: freeswitch-users-bounces@lists.freeswitch.org>] On Behalf Of Michael Collins Sent: Wednesday, August 29, 2012 6:21 PM To: FreeSWITCH Users Help Subject: Re: [Freeswitch-users] Prevent A leg from hangup after bridge with inbound ESL socket

Try this: http://wiki.freeswitch.org/wiki/Channel_Variables#continue_on_fail

-MC On Wed, Aug 29, 2012 at 6:57 AM, Alex Massover <alex@jajah.com<mailto: alex@jajah.com>> wrote: Hi,

I have a very simple dialplan that just do park for incoming calls. All rest of leg management is done via ESL inbound socket.

I'm trying to do the same behavior like in this dialplan example, but from ESL inbound socket: <action application="set" data="hangup_after_bridge=false"/> <action application="bridge" data="sofia/internal/1001@$${domain}"/> <action application="bridge" data="sofia/internal/1002@$${domain}"/>

The problem is with bridge API, if B leg doesn't answer (e.g. 404, or busy), A leg disconnects. But I'm trying to prevent A leg from disconnecting in order to do bridge to other place.

Looks like hangup_after_bridge=false, park_after_bridge=true, transfer_after_bridge etc don't have any effect when bridge done from inbound socket. A leg disconnects always.

Is there any way to keep A leg after bridge with inbound socket? I'm aware of originate, but prefer to user bridge.

-- Best Regards, Alex Massover

_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com

FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com

Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com

FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org<mailto: 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

-- Michael S Collins Twitter: @mercutioviz http://www.FreeSWITCH.org http://www.ClueCon.com http://www.OSTAG.org

_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com

FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com

Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com

FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org<mailto: 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

-- Michael S Collins Twitter: @mercutioviz http://www.FreeSWITCH.org http://www.ClueCon.com http://www.OSTAG.org

!DSPAM:504453d832762136219851!

_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com

FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com

Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.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