On 2006/07/13 19:46, Gustavo Rios wrote: > Performance and reliability. If you just want to route calls between SIP phones, SER/OpenSER are faster and less resource-hungry (but the important part of the configuration file is written in a programming language for routing SIP messages, /not/ calls as with Asterisk extensions.conf, so it requires more in-depth knowledge of the protocol).
If you need more PBX/IVR features and/or codec translation, look at the more complicated software e.g. Asterisk, sipx. With a lot of the voip software and hardware, expect patchy documentation in places... voip-info.org wiki is often the most useful doc but is frequently slow or down - for Asterisk bugs.digium.com is pretty useful too, especially when it does odd things). Interoperability with voip hardware from various vendors isn't always fantastic (take dtmf, for example). Traditionally Asterisk has not been the most portable software, it has improved between 1.0 and 1.2 releases, and it's getting better, but developers are mainly using Fedora Core and the further away from that the harder some things become. The development (to-be-1.4) code should fix a number of problems with 1.2 but oh joy, they have changed the build system for some menu-driven download-and-build thing which I haven't summoned the enthusiasm to look at properly yet...
