<div>Which one sounds simpler? Having a new layer of proxies and extra hardware on different software packages with their own set of configurations, limitations and bugs than having WebSocket enabled on opensips and control your routing logic all in one place off of same DB.</div>
<div><br></div><div>Regards,</div><div>Ali Pey</div><div><br></div><br><div class="gmail_quote">On Wed, Oct 31, 2012 at 12:48 PM, Iñaki Baz Castillo <span dir="ltr"><<a href="mailto:ibc@aliax.net" target="_blank">ibc@aliax.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_extra"><div class="im">2012/10/31 Ali Pey <span dir="ltr"><<a href="mailto:alipey@gmail.com" target="_blank">alipey@gmail.com</a>></span><br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Using OverSIP and the OpenSIPS would make things just more complex specially for larger deployments.</blockquote></div><br></div>Really? IMHO it makes things MUCH MORE simple. Use OverSIP as an Outbound EDGE Proxy and you are done. Otherwise wait for a proper TCP/TLS and WebSocket support in OpenSIPS.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">In a large deployment run N OverSIP proxies in front of your OpenSIPS registrar. Just it.<span class="HOEnZb"><font color="#888888"><br clear="all"><div><br></div>
-- <br>Iñaki Baz Castillo<br><<a href="mailto:ibc@aliax.net" target="_blank">ibc@aliax.net</a>><br>
</font></span></div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br>