How best to use event system for many originates with listeners
I'm designing an application that will originate many calls via the event system which I also want to attach event listeners to. i want each event listener to only listen for events particular to each originated call. Since I want FreeSWITCH to control the call after I originate it, it seems that I should use an inbound connection. The two possible workflows I see are: a) Issue an originate command via inbound, then turn it into an outbound-type connection via a 'myevents <uuid>' call (or 'handlecall' using mod_erlang_event) once the channel is up. With this method, it seems that I could miss critical channel events between the time the call is originated and the listener is attached. b) Set up an inbound listener filtered on a pre-determined UUID for the call, then originate the call with that UUID. This would seem to guarantee that no events are missed by the listener, but I'm wondering about the performance of having potentially hundreds of inbound connections with filters going at the same time. So my questions are: 1) Is there a way to accomplish a) without potentially missing any channel events? 2) Is b) vastly less efficient than a)?
Chad, What is your event listener? Just curious. It seems to me that you could do an inbound event socket to generate the call and then let that call hit the dialplan and send it to the socket app which in turn would send the call to your event listener. (I suppose you could even do something like "bgapi originate sofia/foo/bar@baz &socket("127.0.0.1:8084")" if you wanted to.) -MC On Tue, Dec 6, 2011 at 8:10 AM, Chad Phillips -- Apartment Lines < chad@apartmentlines.com> wrote:
I'm designing an application that will originate many calls via the event system which I also want to attach event listeners to. i want each event listener to only listen for events particular to each originated call.
Since I want FreeSWITCH to control the call after I originate it, it seems that I should use an inbound connection. The two possible workflows I see are:
a) Issue an originate command via inbound, then turn it into an outbound-type connection via a 'myevents <uuid>' call (or 'handlecall' using mod_erlang_event) once the channel is up. With this method, it seems that I could miss critical channel events between the time the call is originated and the listener is attached.
b) Set up an inbound listener filtered on a pre-determined UUID for the call, then originate the call with that UUID. This would seem to guarantee that no events are missed by the listener, but I'm wondering about the performance of having potentially hundreds of inbound connections with filters going at the same time.
So my questions are:
1) Is there a way to accomplish a) without potentially missing any channel events?
2) Is b) vastly less efficient than a)?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (2)
-
Chad Phillips -- Apartment Lines
-
Michael Collins