<br><br><div class="gmail_quote">On Wed, Mar 23, 2011 at 6:48 AM, lakshmanan ganapathy <span dir="ltr"><<a href="mailto:lakindia89@gmail.com">lakindia89@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>Eventlock is used to say "Whether to queue the commands or not".<br><br>Assume I'm giving playback and bridge command via outbound socket to freeswitch.<br><br>If eventlock is "true" then, first "playback will be executed" and then only the bridge will be executed.<br>
<br>If eventlock is "false", then order of execution is not guaranteed. <br><br>I'm also using Outbound event socket. I'll run it in async mode. After each execute() statement, if I need the output for that event, I will wait for the event and then only I'll proceed. If I don't need event, ( playback ), I just do the other operations.<br>
<br>This works well for me.<br><br></blockquote><div>Be sure that you are using the terms "inbound" and "outbound" event socket correctly. It's inbound or outbound from the perspective of FreeSWITCH, not from the perspective of your script. An easy rule of thumb is this: if you use the 'socket' application in your dialplan then you are using "outbound event socket" because FS has to make an outbound connection to your script.</div>
<div><br></div><div><a href="http://wiki.freeswitch.org/wiki/Event_socket">http://wiki.freeswitch.org/wiki/Event_socket</a></div><div><br></div><div>-MC</div></div>