[Freeswitch-users] Defunct processes from starting a script

Frederic Jean makafre at gmail.com
Fri Oct 9 16:04:10 UTC 2020

Thank you very much for the insight John.

- Fred

On 2020-10-08 12:48:07, "Bote Man" <botelist at gmail.com> wrote:

I do not know what your script does, and that determines the best 
approach to solve the problem.

In the only case with which I have experience, I run a perl script as a 
stand-alone linux process using the normal perl interpreter. This script 
then connects to FreeSWITCH via ESL (the Event Socket Library) and 
listens for certain FreeSWITCH events, then reacts to them. This removes 
the script from the telephony processing loop in the dialplan and 
eliminates any possible blocking of telephony processing in the dialplan 
(which seems to be a common problem with many script implementations 
when called from the dialplan).

This method requires compiling the ESL.pm module which is part of the FS 
source; this module provides the connection from perl to FS. Install it 
using these instructions:


There are perl examples on this wiki page:


That’s not much, but I hope it helps.


John Boteler

BnC Group U.S.A.

From: FreeSWITCH-users <freeswitch-users-bounces at lists.freeswitch.org> 
On Behalf Of Frederic Jean
Sent: Thursday, 8 October, 2020 10:38
To:freeswitch-users at lists.freeswitch.org
Subject: [Freeswitch-users] Defunct processes from starting a script

Dear community,

Newbie here; I am currently experiencing aleatory defunct processes by 
starting a Perl script this way:

<action application="set" data= 

<action application="socket" data=" sync full"/>

Are there any better ways to have it executed and avoid these?



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

More information about the FreeSWITCH-users mailing list