Transcript ppt - Common Solutions Group

A CSG Presentation
January 5, 2005
Tom Ball
Manager
Voice Network Engineering
[email protected]
Agenda
► VoIP
and Cornell, Our Situation
► Campus Life Concerns
► Student Survey
► Cellular Activity
► Summary
Legacy PBX Environment
► What’s
our plan?
► When are we going…?
► Why….why not?
Current PBX
► PBX
environment since 1985
► AVAYA DEFINITY PBX
► Avaya
Communication Manager 1.3
► IP
capable PBX supporting soft / hard phones and
voice gateways
► RFP replaced old G2.2 with G3r in 2001
 “Who Knew?” … seamless transition …
► The
plan was to be fully capitalized by June of
2005
 In 2000, knew VoIP was coming…
VoIP Technical Considerations
►
Common Building Infrastructure
 Not all Cat 5/6
 Long term upgrade plan…. “EzraNet”
►
Data Network
 Feel good about existing bandwidth & capacity
 Not PoE capable switches
 Edge network not on UPS
►
Emergency Power
 Large investment to do so
►
911 Location Assurance
 Data Network jack locations are not as accurate in databases
VoIP Social Considerations
► Managing
expectations of reliability
 Voice Vs. Data availability
► Re-tooling
and re-training of personnel
 Not just the technical staff…
► Concept
of change & users
 You’re thinking of taking out my old phone?!
VoIP Financial Considerations
► Justify
the full, or partial replacement of a
fully capitalized, up to date PBX.
► Are there really significant costs savings?
►IE:
Proprietary Digital set Vs. IP HardPhone
 PoE switches
 Additional UPS systems
►PSTN
savings?
►Potential Savings for moves, adds & changes?
Graduate Student Thesis, 2003
“Internet Protocol Telephony and The Future
of Cornell University’s Telephone System”
By: Kevin Byrnes, Graig Diamond, Jonathan Wang
Master of Engineering Project Report, sponsored by
the Office of Information Technologies at Cornell
University.
‘
Scope
► The
existing voice and data networks at Cornell
were analyzed








Voice PBX
Data network, core, edge, I1/2 connectivity
Infrastructure (copper and fiber)
Local / LD costs
Historical traffic trends
Financial considerations
Power systems
911
VoIP Report Conclusions
►
Did not recommend an aggressive conversion to VoIP due
to:






Full ownership of campus area network
PBX status (capabilities and ownership)
911 solutions for VoIP are currently weak
Emergency Power / UPS considerations
No recognizable voice WAN cost savings
80% of Wiring Infrastructure not CAT 5e/6
Recommended developing a plan to move common
infrastructure towards supporting VoIP services.
► Stay in tune with developments…
►
Voice Network Vision
► Leverage
existing PBX investment
► Deploy IP enabled endpoints off the PBX
where feasible and economically justified
► Develop a long term migration plan for the
current PBX
► Evaluate how to best provide for future VoIP
/ SIP capability
Tough Questions - Campus Life
► Students:
about 4800 phones.
 CIT faced questions like:
►“We
want to lower our costs”
►“Can we rip phones out?”
►“Has CIT thought about alternatives for students like
cellular?”
Approach
► Formed





a committee of stakeholders
CIT
Campus Life
Cornell Police
Environmental Health and Safety
Purchasing Office
Committee Discussion
► CIT
offering wireless voice services?
► Removing phones from the Residence Halls?
► Cellular Services?
► Do VoIP technologies fit here?
► What about 911 assurance?
Committee Q’s
► We
had good discussions, candid thoughts,
but no answers….
 Is there risk in providing wireless IP devices and
NOT providing specific 911 detail?
 Cellular in lieu of wired?
 We knew others are doing this…so why not?
To Counsel and Risk Management
► “Is
there a requirement to continue
providing wired voice service to students?”
 Cellular?
► “What
if we cannot provide exact location
information to the police for 911 purposes?”
 Softphones / Cellular
Outcomes
►
►
►
Providing wired phones is essentially a business decision,
however:
 Need a business plan for further review
 More emergency phones / blue lights
 Cellular network reliability and availability concerns
Clearly define and communicate expectations for these
devices relative to 911.
 “This is not your primary means of communications for
911 purposes…use a wired phone or a blue light if
threatened”
Must address how wireless devices will fit into 911 and
emergency services scheme. (?)
Now What?
► Need
to better understand student
perspectives
► Fall student survey…
 Annual incoming Freshman
 Q’s: Scale of 1 to 5
 About 1,100 respondents
Student Survey Questions
ResNet Phone vs. Cellular
►
I depend on my ResNet phone in my room
►
I currently have a cell phone I brought with me
►
If Cornell offered a cellular service I would use it
►
I would like a service that rings my cell phone when my
ResNet phone rings
►
My cell phone works well in my residence hall.
I depend on my ResNet Phone
313
27% agreed
18% neutral
55% said NO
285
192
197
Agree
Neutral
105
Strongly Agree
Disagree
Strongly
Disagree
I currently have a cell phone
677
85% agreed
14% don’t
1% not sure…?
252
117
Strongly Agree
Agree
14
32
Neutral
Disagree
Strongly
Disagree
If Cornell offered a cell service, I
would use it
22% agreed
40% weren’t sure
38% said no…
437
271
174
142
68
Strongly Agree
Agree
Neutral
Disagree
Strongly
Disagree
I would like a service that rings my cell
phone when my ResNet phone rings
336
291
46% agreed
27% neutral
28% said NO
202
163
102
Strongly Agree
Agree
Neutral
Disagree
Strongly
Disagree
My Cell Works well within my
Residence Hall
330
257
36% agreed
17% were neutral
47% said NO
186
178
Neutral
Disagree
140
Strongly Agree
Agree
Strongly
Disagree
Cellular Activities
► Working
with primary cellular providers to:
 Improve existing macro coverage
 In-Building coverage
► Discover
developments with next generation
networks: CDMA / GSM
 Meeting with carriers for network updates and
technology “chalk talks”
► Site
more companies to help offset the loss in
traditional voice revenues….
Pending Pilot
► Extension
to Cellular (EC-500)
 Cell phone bridging feature with AVAYA PBX
 Additional product?
►Staff….clear
interest
►Students….not sure
 Determine impacts on trunk utilization
Closing
► Continue
to evaluate next steps to support
VoIP and SIP
► Further define requirements with respect to
emergency services
► Better understand financial impacts of
legacy vs. IP model for our PBX.