1. SIP User Agents SIP.edu Workshop BCIT, Burnaby, British Columbia Ben Teitelbaum SIP.edu Workshop BCIT, Burnaby, British Columbia Ben Teitelbaum

2. 2 Outline Why UAs Matter What they do or might do Phyla Hard phones Soft phones Mobile devices B2BUAs GWs and Tas Media servers

3. 3 Quick SIP Review: REGISTER * 200 - OKREGISTER: sip:dbaron@MIT.EDU401 - Unauthorized User B MIT.EDU Registrar REGISTER: (add credentials) MIT.EDU Location sip:dbaron@MIT.EDU Contact 18.18.2.4 * Slide courtesy of Dennis Baron

4. 4 Quick SIP Review: INVITE * INVITE: sip:dbaron@MIT.EDU Calls dbaron @MIT.EDU INVITE: sip:dbaron@18.18.2.4100 - Trying 180 - Ringing Rings180 - Ringing200 - OKAnswers 200 - OK ACK BYEHangs up200 - OK User A User B MIT.EDU Proxy Talking RTP * Slide courtesy of Dennis Baron

5. 5 User Agents: Architectural Role User Agent Client (UAC) User Agent (UA) Architecturally significant role Global SIP ecosystem is a balance of campus/enterprise infrastructure and P2P Far more P2P than PSTN SIP pushes functionality out to end-points Signaling after communication established Media transport and negotiation PBX-style features NAT traversal …

6. 6 User Agents: User Experience Personal communications is personal UIs matter hugely Usability (How do I do x?) Ergonomics (Does it feel good in my pocket?) Style (Hello Kitty SIP phone, anyone?) Can campuses can stay out of the SIP UA business, just as most of us are out of the MUA business?

7. 7 User Agents: Edge Innovation P2P nature of SIP should support forklift-free path forward Just as IP has provided edge-enabling connective network infrastructure, SIP will provide edge- enabling connective applications infrastructure Points of possible P2P innovation New codecs (some baseline LCD needed) SIP extensions (e.g. SIMPLE) New features (e.g. CPL, personal IVRs, P2P conferencing)

8. 8 UA Features UI or form factor (for devices) Codec support (G.711, G.729, iLBC, Speex) Encryption (SRTP) NAT traversal Asserted identity PBX feature set (hold, transfer, MWI, mute, DND, conferencing) DNS, ENUM, registration

9. 9 Hard Phones: Low End Basic functionality Zero, one or two line display Grandstream BudgeTone 100

10. 10 Fancier displays High-quality speakerphones Directory integration Programmability Lots of buttons POE Snom 360 Cisco 7960 Hard Phones: Mid-Range

11. 11 Hard Phones: High End Video Style Status Motorola Ojo Some Crazy Thing

12. 12 Soft Phones Software running on a PC or laptop UI options Picture of a phone Contact list Right-click application integration

13. 13 Softphone UI: a Picture of a Phone Pingtel Instant Expressa Familiar interface But on a PC, does this make sense?! Some of these feel like HW simulators for firmware developers

14. 14 Softphone UI: Contact List Wave Three Softwares Session Microsoft Windows Messenger Presence-centric UI Borrowed from AIM, etc.

15. 15 Some of Both Xten eyeBeam

16. 16 Mobile Devices Pulver WiSIP HP iPAQ Music + Communication Coming Soon... Vocera Wearable

17. 17 B2BUAs Jasomi PeerPoint Netrake nCite NAT-traversal CALEA Bad, bad, bad.

18. 18 Gateways and TAs Sonus GSX9000Grandstream HandyTone ATA-286 Cisco 2600 Series * SmallHugeMedium

19. 19 Media Servers IVRs Conference servers …

20. 20 P2P SIP Skype phenomenon has caused rethinking of need for proxy/registrar 100% P2P SIP is on the way Basic idea: clients REGISTER to join DHT, which is then used for routing Chord for DHT http://www.p2psip.org/ Node A Node-ID 023 Node B Node-ID 245 Alices Node Node-ID 503 1. REGISTER 302 Node B 2. REGISTER 200 OK Alice-> Alices Node Node C Node-ID 520

21. 21 Can Campus/Enterprise SIP Compete? With proper plumbing to campus IT assets and freedom for P2P edge innovation, I believe it can If we lock down VoIP (e.g. deployed as a PBX replacement strategy) and not allow edge innovation, campus SIP will lose out to consumer services

22. 22