Hello
I am in the process of evaluating a SIP stack for IMS
enhancements (for CSCF). I compared SIPx and reciprocate stacks for CSCF
development.
Resiprocate:
Pros:
- Slightly less distributed architecture than SIPx
- Can run as registrar/proxy/redirect server
- TLS support for Security
- Support for NAT
- Web based management interface
- IPv6 support
- Maximum standards compliance
Other notes:
- Developers are mostly RFC authors also, so
implementation is full and true reference implementation
- SIP foundry says that resiprocate is most advanced and
interoperable open source SIP stack
- Many IMS headers are supported in latest release 1.0
SIPx:
Pros:
- Complete SIP based IP-PBX solution
- Distributed architecture
- Can run as registrar/proxy/redirect server
- TLS support for Security
- Support for NAT
- Web based management interface
Cons:
- Missing IPv6 support
- Large footprint
I have following queries:
- Can somebody point out if anything out of above is not
correct or if people can add more?
- In resiprocate, some of the IMS headers are being
handled. Is it only the parsing part or the processing is also done in the
stack as per 3GPP standards?
- Are there any plans of IMS support in any near future
reciprocate release?
Regards,
Gaurav Kansal