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@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Michael Jerris Sent: Friday, October 7, 2016 8:09 AM To: FreeSWITCH Users Help <freeswitch-users@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@gmail.com <mailto:gascagonzalo@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