[Freeswitch-users] Persist outbound event socket after channel is destroyed

Michael Jerris mike at jerris.com
Wed Aug 9 15:01:55 UTC 2017


linger is the closest thing to this.  It will wait for final events before it drops.

> On Aug 8, 2017, at 10:14 AM, Guillermo Ruiz Camauer <grcamauer at gmail.com> wrote:
> 
> What exactly do you want to do?  The call is already over...  If you want to monitor FS or do anything else not related to the call, you should probably be using an INBOUND socket.
> 
> Guillermo
> 
> On Mon, Aug 7, 2017 at 5:35 AM, Sean Ingham <sean at missionlabs.co.uk <mailto:sean at missionlabs.co.uk>> wrote:
> I'm using the socket application in the dialplan to establish an outbound event socket to my app. I use the async and full flags to expose full api functionality.
>  
> I currently use myevents to filter only events related to the current channel, I also use the linger command to ensure the socket stays up until all channel events have been sent to my app (after which FS then tears down the socket). 
> 
> However, what I'm trying to do is prevent FS closing the socket at all, and always leave it up to my app to close the socket when it's finished with it. Is this possible with ESL in outbound mode?
> 
> In other words, I want the socket to linger longer :)
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20170809/f8fce789/attachment.html>


More information about the FreeSWITCH-users mailing list