[OpenSIPS-Users] [OpenSIPS-Devel] [RELEASES] Planing OpenSIPS 1.9.0 major release

[Olle E. Johansson]

31 okt 2012 kl. 18:17 skrev Ali Pey <alipey at gmail.com>:

> 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.
Well, Using OverSIP as an inbound proxy for WS clients doesn't mean anything in regards of moving your routing, location server or anything else. Just that those clients enter your SIP network in a different way. 
You will still have full control over everything in your OpenSIPS server.

/O
> 
> Regards,
> Ali Pey
> 
> 
> On Wed, Oct 31, 2012 at 12:48 PM, Iñaki Baz Castillo <ibc at aliax.net> wrote:
> 2012/10/31 Ali Pey <alipey at gmail.com>
> Using OverSIP and the OpenSIPS would make things just more complex specially for larger deployments.
> 
> 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.
> 
> In a large deployment run N OverSIP proxies in front of your OpenSIPS registrar. Just it.
> 
> -- 
> Iñaki Baz Castillo
> <ibc at aliax.net>
> 
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> 
> 
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20121031/1d9b159f/attachment-0001.htm>