In my experience, ESL (mod_event_socket) is the perfect solution for this kind of implementation.

I’ve done some simple conference handling, and I’m using ESL for it all.

/Peter

Från: freeswitch-dev-bounces@lists.freeswitch.org [mailto:freeswitch-dev-bounces@lists.freeswitch.org] För Erjian Li
Skickat: den 21 februari 2012 11:25
Till: freeswitch-dev@lists.freeswitch.org
Ämne: [Freeswitch-dev] Look for some advice on how to implement a FreeSWITCH controlling module

Hi everyone,

I am developing software for a conference call product with FreeSWITCH as IP PBX software, and I have some troubles on a module implementation.  So I come here for some advice. Thanks in advance.

My requirement of the module:
I want to implement a controlling module (or separate program) for FreeSWITCH, this module (or separate program) receives the admin messages from a so-called admin server , parses the messages, and generates FreeSWITCH commands according to the message data, then send these commands to FreeSWITCH to execute (e.g. send a "conference dial ..." command to add a member into the conference call). Also, this module (or separate program) is required to listen the CHANNEL related events fired by FreeSWITCH, and report the FreeSWITCH channel status to admin server.

My questions:
 I want to implement above functionality in a separate program. When running this program communicates with FreeSWITCH via FreeSWITCH's event socket library, is it applicable?  I don't have much knowledge about FreeSWITCH's loadable module, is it better to implement it as a FreeSWITCH's loadable module, like the modules in src/mod/applications?    

--
Best Regards

Erjian

!DSPAM:4f43a50432761362825821!