In my FreeSWITCH environment, calls are originated out to customers who are
placed into a fifo upon answer. There are members (x-lite endpoints) in this
fifo who handle those customer calls. I am writing a monitoring application
that uses event_socket to watch the channels involved in this
On Thu, Sep 18, 2008 at 3:49 PM, Luke Graybill [EMAIL PROTECTED] wrote:
My suggested solution is to apply the job-id concept from bgapi to messages
as well, and to go a step further; borrow the Asterisk idea of transmitting
an identifier along with each command. Every response and event
Oops, I forgot to mention anthm as well - he provided great feedback on irc!
On Fri, Sep 19, 2008 at 10:19 AM, Luke Graybill [EMAIL PROTECTED] wrote:
On Thu, Sep 18, 2008 at 3:49 PM, Luke Graybill [EMAIL PROTECTED] wrote:
My suggested solution is to apply the job-id concept from bgapi
that doesn't confuse
things - I'm not great on concise terminology.
Killarny
On Fri, Sep 19, 2008 at 10:45 AM, Michael Jerris [EMAIL PROTECTED] wrote:
On Sep 19, 2008, at 12:19 PM, Luke Graybill wrote:
On Thu, Sep 18, 2008 at 3:49 PM, Luke Graybill [EMAIL PROTECTED] wrote:
My suggested solution
I've been doing a lot of work recently with FreeSWITCH's mod_event_socket,
and I wanted to comment a bit about the syntax used for commands through the
socket while using asynchronous mode. I haven't tried the synchronous mode
yet, as I always want to be free to be able to execute commands without
