Nitzan Kon wrote: > My concerns with OpenSIPS: > > 1. It's a software based solution, which means higher chance > of software-related failure, and higher chance of failure due > to problems with the Linux box hosting it.
A little bit of proper engineering will overcome that reasonably. > 2. Overkill to install and maintain (if we can get a simpler > solution) Really? It is, admittedly, a somewhat recondite product, but you don't have to build everything you run into your core competency; you can divest yourself of some parts of your infrastructure and streamline and all that and get someone else to do it, like a real Enterprise. :-) Secondly, as difficult as it may be, I can't imagine anything simpler to accomplish what you're looking for. The logic required is quite granular. > 3. Incoming calls - I admit complete ignorance. I don't know > how OpenSIPS handles incoming calls, but for those to arrive > at the user reliably they must arrive from the same IP address > the user is registered to. Otherwise their broadband router's > NAT firewall will just block the connection. How does OpenSIPS > handle this? (does it handle this??) What role are you envisioning the proxy to be in here? If it's a registrar, it will have their IP information in the stored contact URI. If not, the calls can be sent somewhere else for resolution. Something, somewhere must know how to contact the user, yes. -- Alex Balashov Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671 Mobile : (+1) (706) 338-8599 _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
