[reSIProcate] Resiprocate for IMS

[Gaurav Kansal]

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:

1.	Slightly less distributed architecture than SIPx
2.	Can run as registrar/proxy/redirect server
3.	TLS support for Security
4.	Support for NAT
5.	Web based management interface
6.	IPv6 support
7.	Maximum standards compliance

Other notes:

1.	Developers are mostly RFC authors also, so implementation is full
and true reference implementation
2.	SIP foundry says that resiprocate is most advanced and interoperable
open source SIP stack
3.	Many IMS headers are supported in latest release 1.0

 

SIPx: 

Pros:

1.	Complete SIP based IP-PBX solution
2.	Distributed architecture
3.	Can run as registrar/proxy/redirect server
4.	TLS support for Security
5.	Support for NAT
6.	Web based management interface

Cons:

1.	Missing IPv6 support
2.	Large footprint

 

I have following queries:

1.	Can somebody point out if anything out of above is not correct or if
people can add more?
2.	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? 
3.	Are there any plans of IMS support in any near future reciprocate
release?

 

Regards,

Gaurav Kansal

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20061012/ab066956/attachment.htm>