[Freeswitch-users] ESL outbound /inbound

[Rafqat .]

Hi Chris,

Thanks for your advice. 

In terms of tighter integration and control, do you think using inbound event socket for billing and 
sendmsg to control call flow would be a good approach for a calling card application.  I have no problem using lua but feel that once i get passed the trivial stuff of checking account funds etc. I may have logic scattered around in more than one place.

Sorry for being a pita but your advice (and the freeswitch community's advice)  is invaluable to a newbie like me.

Thanks

Raf


Date: Fri, 24 Dec 2010 15:20:00 -0500
From: chris at cloudtel.com
To: freeswitch-users at lists.freeswitch.org
Subject: Re: [Freeswitch-users] ESL outbound /inbound

I use inbound to monitor switches as a socket client and mod_xml_curl to direct call flow from a seperate web app. This allows me to receive events across multiple channels across multiple switches without worrying about call flow, which is a good design for what I am doing in this example ... monitoring call flow and conferencing events for realtime display in a UI. Our call flow systems are critical and monitoring is non-critical so it works well to seperate them. As a calling card app your system will probably require tighter integration of call flow and billing, so combining them could make sense.


The main benefit of outbound is you can use a socket server and each of your clients represents a distinct channel on one of your switches. It can make directing call flow easy and it is simple to require your socket server or play an "oops we are busy" message when it is down ... and it helped everyone quickly port their FAGI apps to this project :)


You are correct that you can just use event socket and sendmsg to control call flow and not use lua at all. Yes there is overlap of functionality between inbound/outbound because both allow you to do basically the same thing, but as different roles in the socket connection.