It is not possible to “initiate a new one and take control again” when working on outbound mode.
In outbound mode, your application will be listening for incoming connections and FreeSWITCH acts as a ‘client’ of your application. If you drop the socket
connection, there’s no way to regain control of the connected call other than having additional <action application=”socket” /> entries on the dialplan, as FreeSWITCH will, by default, move to the next action on the dialplan if the socket connection is dropped
and the current action is completed.
For example: if your application sends a ‘record’ command (to record audio) with a timeout of 15 seconds then closes the socket connection, once the record
command is completed FreeSWITCH will just move to the next action on the dialplan. There’s no way for you to regain control of this call in outbound mode, other than having additional ‘socket’ commands on the dialplan, and even if you have those you’ll have
to figure out how to reestablish the ‘context’ of the call within your application.
From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org]
On Behalf Of Grant Bagdasarian
Sent: Monday, September 15, 2014 1:49 AM
To: FreeSWITCH Users Help
Subject: Re: [Freeswitch-users] Disconnect the call when ESL connection gets disconnected
So, what it comes down to is that there is no mechanism in freeswitch which will also end the call when the ESL connection is disconnected for any reason?!
I guess I’ll have to write my application so that it will “never” close the connection by mistake (read bug) and if it does initiate a new one and take control
again.
From:
freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org]
On Behalf Of servtelar
Sent: Saturday, September 13, 2014 4:20 PM
To: FreeSWITCH Users Help
Subject: Re: [Freeswitch-users] Disconnect the call when ESL connection gets disconnected
When the call is bridged you can close the ESL connection and the call remains connected.
On Sep 12, 2014, at 12:16 PM, Hector Geraldino <Hector.Geraldino@ipsoft.com> wrote:
Well, I think it depends on which action is being executed on the call leg. If it is a park(), or bridge() I don’t think it is possible.
As I understand it, FreeSWITCH will ‘cede’ the control of the call to an external (ESL) application when the “socket” action is executed on the dialplan. If
the socket gets disconnected, I would suspect that the next action on the dialplan will be executed once the current action is finished, but I don’t know/am not sure that if, for example, the call is parked (or bridged to another leg) by the application, the
current operation will be canceled (call un-parked or un-bridge) because the socket is now closed.
From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On
Behalf Of Grant Bagdasarian
Sent: Friday, September 12, 2014 10:22 AM
To: FreeSWITCH Users Help (freeswitch-users@lists.freeswitch.org)
Subject: [Freeswitch-users] Disconnect the call when ESL connection gets disconnected
Hello,
Is there a way to disconnect the call(s) managed by an ESL connection when the ESL connection gets disconnected in outbound mode?
Regards,
Grant
_________________________________________________________________________
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-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.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