VoIP at MIT. Merit VoIP Seminar. Dennis Baron April 3, Dennis Baron, April 3, 2008 Page 1. np163

Transcription

1 VoIP at MIT Merit VoIP Seminar Dennis Baron April 3, 2008 Page 1

2 Outline MIT VoIP Project Goals VoIP Service Models VoIP Architecture Rollout Plan Outstanding Issues Quick Questions Page 2

3 Voice over IP Project Goals Smoothly migrate MIT to Voice over IP (VoIP) with minimal impact to the end user community; determine optimal timing for the transition Highly robust, carrier class infrastructure Roll-out plan developed in coordination with departments, labs, and centers: site surveys of existing telephony services scheduled migration Deployment support models from intensive & local hands-on by IS&T to cooperative support for DLC IT staff. Page 3

4 Voice over IP Service Model Provide a flexible infrastructure for MIT faculty, students, and staff. MITvoip managed enterprise service for most users Focus on desktop phone replacement Robust, reliable, and secure Scalable and supportable Voice only service PersonalSIP accounts for everyone Self-service activation Based on your MIT electronic identity ie. address Open standards environment allowing members of the community to experiment And maybe something else in between Page 4

5 VoIP Service Spectrum MITvoip Basic Functionality IP Phone Users Operates like ISDN phone New old VMail No / little training required Full Support Personal SIP Accounts SIP account only BYO Phone, Client or Application Telephone number assigned Limited (5 digit) outbound dialing Limited IS&T Support, Peer Support Advanced Functionality Advanced user functions via Sylantro web pages Flexibility for early technology adopters Options for building SIP applications Page 5

6 Desktop Replacement Service MITvoip Polycom for desktop devices SoundPoint IP430, 550, and 650 Soundstation IP4000 conference phones Hitachi Cable WIP5000 WiFi phones Sylantro for call control Iperia for voice mail Covergence for Session Border Controller (SBC) Media and signaling encryption Currently out of service Home grown provisioning system Page 6

7 PersonalSIP Accounts Based on pilot/open source infrastructure OpenSER and Asterisk Bring your own device Soft clients (applications) that run on Windows, Macs, Linux, mobile devices Phones & soft clients that support video Modified support model Limited IS&T support Peer support: wiki and user forums Leverages Mobile Partners Allows for experimentation Greater flexibility lesser reliability Features may evolve over time Encourages innovation Page 7

8 Long Term VoIP Architecture 5/9/2007 ~ 1-2,000 Open Source? ~ 13,000 IP-Centrex ~ 2,000 Analog Telephone Lines Emergency Phones Fax Session Border Controller (SBC) Modem, point of sale, alarms, etc. Internal Access (Line Side) Location db Outbound Proxy Pilot:openSER SYL Presence Server SYL Syl Control Presence Server (feature Server server, registration db) PBX.. Shared Services ENUM (DNS) Internal (routing) Proxy Pliot: openser SYL Route Server SYL Route Server Messaging (Iperia) Other Shared Services (conferencing, presence, etc.) External Access (Trunk Side) DMZ SBC Carrier SBC VoIP Gateways Pilot:Cisco 5850 New VoIP Platform Pilot Platform New Analog Platform Public IP PSTN Page 8

9 VoIP Rollout Plan SIP experimentation started in 2003 VoIP pilot in 2007 Phased deployment began in January ,000-15,000 phones to be transitioned Rollout to take ~ 2.5 years Deployment criteria: New construction (no telco wiring) VoIP Pilot groups (partially transitioned) Building renovation or group move Buildings with adequate infrastructure (wiring, data closets, etc.) Department readiness Page 9

10 VoIP Project Timeline Page 10

11 Outstanding Issues Limited support for VoIP over WiFi Currently no guarantee for quality of service No ability to centrally configure and manage handsets Capabilities expected to change over the life of the service Service delivery model for non-is&t campus networks Service level agreements, phone configuration and initialization, emergency services/endpoint location, and quality of service Evolving ability to support emergency services ( 100/911 ) Using network data to self-report IP phone location. Need for additional analog phones (key offices and hallway placement) in the event of power and/or network outages Whether to provide a student VoIP service offering Parity with existing telephony service offering Page 11

12 Questions? Page 12