Dennis Baron, April 3, 2008Page 1np163

VoIP at MITMerit VoIP Seminar

Dennis Baron

April 3, 2008

Dennis Baron, April 3, 2008Page 2np163

Outline

• MIT VoIP Project Goals

• VoIP Service Models

• VoIP Architecture

• Rollout Plan

• Outstanding Issues

• Quick Questions

Dennis Baron, April 3, 2008Page 3np163

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.

Dennis Baron, April 3, 2008Page 4np163

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. email address

• Open standards environment allowing members of the community to experiment

– And maybe something else in between

Dennis Baron, April 3, 2008Page 5np163

VoIP Service Spectrum

MITvoip Basic Functionality• IP Phone Users• Operates like ISDN phone• New VMail @ 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

Dennis Baron, April 3, 2008Page 6np163

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

Dennis Baron, April 3, 2008Page 7np163

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

Dennis Baron, April 3, 2008Page 8np163

Long Term VoIP Architecture

Internal (routing) Proxy

Pliot: openSER

Outbound ProxyPilot:openSER

PSTNPublic IP

External Access

(Trunk Side)

Shared Services

Internal Access

(Line Side)

ENUM (DNS)

Location dB

VoIP GatewaysPilot:Cisco 5850

~ 13,000 IP-Centrex

Session Border Controller (SBC)

SYL Presence Server

Syl Presence Server

SYL Control Server (feature server, registration dB)

SYL Route ServerSYL Route Server Messaging(Iperia)

DMZ SBC Carrier SBC

PBX …..

Fax

Modem, point of sale, alarms, etc.

~ 2,000 Analog Telephone Lines

Emergency Phones

Other Shared Services (conferencing, presence, etc.)

5/9/2007 ~ 1-2,000 Open Source?

New VoIP Platform

Pilot Platform

New Analog Platform

Dennis Baron, April 3, 2008Page 9np163

VoIP Rollout Plan

• SIP experimentation started in 2003

• VoIP pilot in 2007

• Phased deployment began in January 2008

– 13,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

Dennis Baron, April 3, 2008Page 10np163

VoIP Project Timeline

Feb-072/1/2007 6/30/2008

Apr-07 Jul-07 Oct-07 Jan-08 Apr-08 July-08

Transition Plan

Personal SIP Accounts

Migrate VMail inc 5E OPTIN

1/1/2010 7/1/2010

4/1/2010Jan-10 Jul-10

Pilot Server Migration

SBC Deploy

FY 3Q08 1500 phones

VoIP Pilot

Infrastructure Development

Full VoIP Deployment

FY 4Q08 1500 phones FY 3Q10

1500 phones FY 4Q10 1500 phones

Personal SIP Accounts

Full VoIP Deployment

Dennis Baron, April 3, 2008Page 11np163

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

Dennis Baron, April 3, 2008Page 12np163

Questions?