SIPit 22 summary now available

May 8th, 2008 by Dan York

sipit.jpgAs we mentioned previously, SIPit22 was held April 14-18, 2008, up at the University of New Hampshire Interoperability Lab. SIPit coordinator Robert Sparks has now posted a SIPit22 Summary which provides a view into the types of products that were being tested.

Now the summary is based on surveys filled out by individual vendors, so it relies on their accuracy (i.e. the information is not independently verified) but it makes for interesting reading. (I was personally struck by the fact that 42% of the SIP implementations indicated they had IPv6 support!) These summaries (older ones available, too) are useful in seeing what vendors are actually deploying and developing versus what we are discussing in the IETF. As noted in Robert’s final paragraph, the issue of NAT traversal for SIP still continues to be one of the most challenging aspects of interoperability.

For our part, attending SIPit 22 was very worthwhile as it gave one of our lead developers a chance to really test the improvements we are making to our SIP stack in an upcoming release of Prophecy. Stay tuned for more on that in the months ahead.

If you do have a product that works with SIP, we do strongly recommend that you do consider attending a SIPit event with your product. We’re a huge believer in open standards… and there’s no better way to test how “standard” your implementation is than to be testing it with a wide range of other vendors!

Technorati Tags:
, , , , , ,

Tags: ,

One Response to “SIPit 22 summary now available”

  1. Speaking of Standards » Blog Archive » SIPit 23 announced for October 13-17 in France Says:

    [...] I’ve written about before, we’re fans of the SIPit interoperability events that are sponsored by the SIP Forum as they [...]

Leave a Reply

Please note: By submitting a comment you agree to comply with our Comment Policy. We welcome all comments, positive or negative, but do reserve the right to remove all or part of blog comments that do not comply with our policy.