1. I know SIP works, but why does it not work with _____________? Ensuring Interoperability Sean Rivers 2/1/2011

2. Way for applications to setup sessions for exchanging data SIP does not care about the contents of the session SIP manages the attributes of the session until the session ends What is SIP? 2 SIP VoiceVideoChatSMS

3. What are the issues? 3

4. 4Confidential

5. 5

6. SIP can do both TCP gives more control UDP is faster and lighter TCP vs UDP (the big rumble) 6Confidential Get him! I am in control!

7. Three main options In-band digits are sent through the audio and are subject to the quality of the audio. – Everyone supports this, but it often does not work. – Does not work with compressed audio codecs RFC 2833 digits are sent digitally in the audio packets – Most common preferred method by carriers. – Works more often RFC 2976 SIP INFO – sends digits in SIP messaging via an INFO message. – Pretty reliable and flexible for managing audio – Very few carriers support it. DTMF (I can’t get in this darned conference?) 7Confidential Sometimes it feels like a rotary phone

8. Codecs 8Confidential G.711 G.729a G.722 AMR DoD CELP GIPS GSM iLBC G.722.1 G.722.2 G.723.1 G.726 G.728 LPC10 Speex

9. 2 methods – Re-INVITE – UPDATE Why? – Optimize congestion – Join Conference What works best? – UPDATE What does everyone support? – Re-INVITE Managing media 9Confidential

10. Options: – G.711 (wishful thinking) – T.38 (better) – Pass-through (Cisco only) Requires equipment Call quality can still affect all options New method in Store and Forward is interesting development. Why is fax ALWAYS an issue? 10Confidential

11. REFER – RFC 3515 – Removed the PBX from the call path completely. – Sometimes even removes the carrier – Carriers hate this. Re-INVITE – Standard SIP RFC – PBX stays in signaling path but audio is diverted – Carriers prefer this Transfering Calls 11Confidential

12. Most carriers require registration PBXs have very loose policies on registration – 1 registration per PBX – 1 registration per carrier – 1 registration per trunk For simplicity most wholesale providers just do IP to IP Address Do I need to REGISTER? 12Confidential

13. SIP over TLS (encrypt signaling) IPSec (VPN tunnels) SRTP (enrypt the audio) Carriers fear the support of problematic certificate exchanges Security Scuffle 13Confidential

14. What are the main reasons we can’t get it together? 14 Big companies vs. Little companiesCarriers vs. Manufacturers Big companies see these issues and try to force change, but they are usually new entrants into the SIP world and are not able to push in the right direction to satisfy others. Carriers are slow to change and manufacturers need to release new features. Proprietary vs. Open Established manufacturers have cultures of island development and internal standards. While many upstart Open Sourced developer want to make everything work.

15. Hardware manufacturers test it at SIPit – Every 6 months – No carriers involved SIP Connect – Trunking standards for SIP providers and Manufacturers – Standard still in early adoption phase What is being done about this? 15Confidential

16. You can get rid of most interoperability with Analog or PRI hand-off – Works – Quality can be an issue (too much conversion) – Price (IADs are not cheap) – Many SIP trunking benefits are lost and advanced PBX features as well Chuck it and give them Analog (IAD) 16Confidential

17. Back to Back User Agent – Like an interpreter it listens to each party and speaks their language. – Can reside in the cloud and/or locally What can I do about this now? 17Confidential

18. What is the most common model? (What we do) 18Confidential Carrier must have their SIP standard PBX will have their own B2BUA will translate

19. Thank You… Sean Rivers Director of Product Technology Confidential 19