I haven't encountered every event yet (I'm still in the process of writing my client) but perhaps some others can help? I'll post the ones I know about so far though.. - command/reply - CHANNEL_EXECUTE - CHANNEL_EXECUTE_COMPLETE - CHANNEL_ANSWER - CHANNEL_PARK The last two are uncertain because, in my view, they apply to channel state; something that the client can track independently without regard to whether it is related to a previously sent command. Note: I tend to use the word 'command' when referring to anything that the client is transmitting to mod_event_socket. I hope that doesn't confuse things - I'm not great on concise terminology. Killarny On Fri, Sep 19, 2008 at 10:45 AM, Michael Jerris <mike@jerris.com> wrote:
On Sep 19, 2008, at 12:19 PM, Luke Graybill wrote:
On Thu, Sep 18, 2008 at 3:49 PM, Luke Graybill <killarny@gmail.com> 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 related to that command should then contain the very same identifier in the header.
After speaking with bkw and MikeJ on irc, I'd like to further clarify my suggestion to account for the fact that not all events apply directly to specific commands, but for the ones which do (such as CHANNEL_EXECUTE_COMPLETE, and for non-events, like command/reply) I believe the suggestion stands :)
Killarny _______________________________________________
Can you catalog the specific events this would effect?Mike
_______________________________________________ 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