The modes are both "event socket" and therefore quite scalable. The primary difference is in how the connection gets started.<div><br></div><div>With outbound event socket, there is always a call involved. A call comes in to FreeSWITCH and somewhere in the dialplan there is a call to the socket application. At that point FreeSWITCH makes an "outbound" connection to your application which is listening for connections on the IP:Port in question.</div>
<div><br></div><div>With inbound event socket, FreeSWITCH is the one sitting there waiting for your application to connect, i.e. an "inbound" socket connection from your program. Once your program is connected it can do pretty much whatever you want: show channels to see what's going on, originate to create new channels, fifo list, conference list, etc. etc. BTW, fs_cli is a great example of an inbound event socket application. fs_cli literally connects to FS via event socket.</div>
<div><br></div><div>Hope this helps.</div><div><br></div><div>-MC</div><div><br><div class="gmail_quote">On Tue, Nov 8, 2011 at 10:53 AM, envelopes envelopes <span dir="ltr"><<a href="mailto:sunwood360@gmail.com">sunwood360@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><p>Both modes can send command and receive events. Which mode is more scalable? <br>
And pros vs cons of each mode.</p>
<br><br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<br></blockquote></div><br></div>