[Freeswitch-users] ESL terminate calls

[Ken Rice]

As Michael commented, TCP connections going up and down can be expensive from a processing stand point, its almost always much more efficient to leave the connections up and re-use them vs tearing them down and restarting them for each new use

 

From: freeswitch-users-bounces at lists.freeswitch.org [mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of Michael Jerris
Sent: Friday, October 7, 2016 8:09 AM
To: FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org>
Subject: Re: [Freeswitch-users] ESL terminate calls

 

why would you hang up a call that just hung up?  if you keep disconnecting the esl connection don't you just have to keep connecting a new one?  why do you do that?

On Friday, October 7, 2016, Gonzalo Gasca Meza <gascagonzalo at gmail.com <mailto:gascagonzalo at gmail.com> > wrote:

I'm launching API Calls using ESL in FS 1.6 (via python)

 

For each new call, after call is hangup, 

I send a uuid_kill and then ESL.client.disconnect()

Are both necessary, or I can skip uuid_kill?

 

I'm trying to improve performance in my ESL and avoid unnecessary TCP connections to Freeswitch.

 

Thanks

 

-G

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20161007/77e4f5b1/attachment-0001.html