1. Columbia's NetPhone VoIP service November 1, 2007 Alan Crosswell

2. 2 Network Convergence Strategic Direction One common network infrastructure for: –Voice –Video –Data –Security –Building Management Systems Reduces capital and operating costs Provides flexibility Distance limits are removed Enables new ways of doing business

3. 3 Walking the Convergence Talk Access control Surveillance cameras Intrusion & fire systems monitoring HVAC monitoring Electric meters NetPhone Voice over IP service

4. 4 First “new” building on new Manhattanville campus First step in replacing 20,000 obsolete ROLM PBX phones at 12 sites 700 users are administrative staff in IT, Finance and HR departments (400+ phones deployed so far) PBX-equivalent phone service with some difficult (for SIP) “business” features: –Bridged/Shared Line Appearance –Directed/Group Call Pickup Compatibility/interop with existing PBX dial plan Advanced apps using SIP for Presence & Integrated Comms

5. 5

6. 6 CU NetPhone Feature Summary (1/2) Multiple line appearances Bridged lines Privacy Multiple “Stacked” lines per registration Call Waiting Caller & Called number & name display Speaker Headset Cordless Headset Mute Hold Transfer – Consultative & Blind Call Forward Always/Busy/No Answer Do Not Disturb Redial Call Return Call Log Buzz Intercom Intercom groups Hunt groups Call Park/Pickup Directed/Group Call pickup Message Waiting Indicator Conference Speed Dial Distinctive Ring Personal Security Codes DTMF passthru

7. 7 CU NetPhone Feature Summary (2/2) Anonymous Call Reject Anonymous Calling Restricted Calling Conference Bridge Analog Lines Fax Voicemail as email Voicemail forwarding Voicemail broadcast Voicemail distribution groups Voicemail referral extension Automatic Call Distribution E911 Improvements over current PBX: –Call Waiting –Multiple Lines per Registration –Call Log –Redial –Voicemail as Email –Web settings (my NetPhone)

8. 8 Ongoing Issues & Wish List Need a good Provisioning app –Combines Registrar, Voicemail, Phone provisioning –Started with code from U Penn “Business PBX” features –Based on Sylantro, etc. drafts as implemented by Polycom (draft- anil-sipping-bla; RFC3265 event notification & RFC4235 dialog) –Hopeful that IETF BLISS will bless this and generate some RFCs –Would like to have this stuff work with other UAs besides Polycom phones and Cisco media GWs Lack of “advanced” SIP features support –Lots of IOS bugs. Pick your train, get some features, not others. –Re-INVITE with Replaces header not well handled by ITSPs

9. 9 Couldn't have done any of this without help from our friends (and vendors) University of Pennsylvania University of North Carolina Chapel Hill MIT OpenSER developers and users Voice-System SRL Internet2 PIC, SIP.edu and VoIP working groups Polycom Cisco