Hello, I'm using outbound ESL socket to control calls and one of the actions is to bridge the A leg to another destination. This works great when the remote party answers, but when the remote party does not answer or is busy the bridge fails and disconnects the A leg. I wish to keep the A leg alive. I've tried setting different kinds of channel variables on the a leg and even the b leg, but without success. There is a thread from a few years ago discussing this very same issue (although they were talking about inbound socket), so I was wondering if anyone has a solution for this? Continue_on_fail, hangup_after_bridge, park_after_bridge, ignore_early_media, all don't work. Any ideas?
Nevermind, my uuid_setvar wasn't working as expected. From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Grant Bagdasarian Sent: Thursday, March 19, 2015 9:00 AM To: FreeSWITCH Users Help (freeswitch-users@lists.freeswitch.org) Subject: [Freeswitch-users] Keep A Leg alive after bridge fails Hello, I'm using outbound ESL socket to control calls and one of the actions is to bridge the A leg to another destination. This works great when the remote party answers, but when the remote party does not answer or is busy the bridge fails and disconnects the A leg. I wish to keep the A leg alive. I've tried setting different kinds of channel variables on the a leg and even the b leg, but without success. There is a thread from a few years ago discussing this very same issue (although they were talking about inbound socket), so I was wondering if anyone has a solution for this? Continue_on_fail, hangup_after_bridge, park_after_bridge, ignore_early_media, all don't work. Any ideas?
participants (1)
-
Grant Bagdasarian