Transcript ip telephony @ georgetown

IP TELEPHONY @
GEORGETOWN U
HURRY UP – AND WAIT
Georgetown University Stats
www.georgetown.edu
About 12,000 total students





Main Campus
Law Center
Medical Center (research / teaching)
Graduate Schools
Hospital (partnership with to Medstar Health)
About 20,000 data ports (including law)- Cisco
About 18,000 voice ports (including law)- Avaya

Five major PBX’s - about 40 Carrier Circuits
About 1500 CATV ports (including law)
About 135 Core Systems host servers – Mainly Sun
IBM Mainframe still used for certain apps
About six major off campus sites networked
Peaking at about 350Mbps of off campus IP traffic
MESSAGE FOR TODAY
-At Georgetown, we’ve done an enormous amount
of work to enable the deployment, and proper
management of next generation phone services
(not just IP!!!) – but right now, there are not a
lot of IPphones on our network.
-But – we think this is just about to change.
-Actually – we don’t think we’re that different.
-Geeze, perhaps we’re OK after all!
What we’ve done – 1
Or - We’re ready to roll (we think) – where’s the party?
Merged voice/data teams
1999
Completed first ubiquitous
robust campus network
2000
Building second-gen network
(more emphasis on perf mgmt)
2001 -
Invested in training - education for staff
(I2 / Net@Edu / ACUTA / Vendors etc)
Ongoing
Vetted program support issues within technology teams



Help desk
Desktop support teams
Remote site support (suddenly the pc is plugged into the phone)
What we’ve done - 2
Invested in appropriate campus hardware /software

Robust – redundanct Cisco electronics

Robust campus optical and Cat 5 infrastructure

Avaya – PBX- Gateway software upgrades

Explored different terminals (hard / soft)
Ongoing
Invested in Perf mgmt tools

Openview / Netflow / LMS / MRTG / IMS (environmental mgmt)
Invested in improved off campus carrier network
Ongoing

TDM local/ LD carriers

Multiple, and robust ISP connections

Robust regional and national HEC connectivity (Max / I2)
IP trials with various vendors

Cisco / Avaya / Broadsoft
So what’s deployed?
Network team has had IP hard phones successfully deployed now
for 2 years.
Several smaller off campus sites – VoIP has been perfect solution to
an issue we’ve previously never had a good solution for.
Softclients - not many out there, but a great telecommuter
application.
Just starting to work on different applications

MAX – Broadsoft – PaeTec trial (see chart)

Broadsoft emergency hosted non-PBX service
Just about to install next generation Avaya Multivantage



2 completely redundant Linux based application processors that can be
hosted in different buildings. Improved center stage switch.
Greatly improved security for IP phones (Security officer breathing
better – which is always a good thing)
Greatly improved “other” services like cellular phone integration etc…
Barriers (Peabody Perspective)
Fear of leaving the “comfort zone”
Lack of “Gun to our heads” – no one has ever once come to me and
said “I want a VoIP phone”.
Other projects/priorities (Wi-fi / redundancy etc…)
Learning curve - confidence is finally changing (early adopters have
taught us lots of things)
Stability of networks and internet was a large barrier, is still an
operational issue - but no longer a major concern.
Internal Cisco vs Avaya battles
Increased awareness of Security in IPVoice service
High costs of new phone sets
Proprietary phone sets
8000 installed digital TDM terminal “boat anchors”
5000 analog ports – we don’t give students phones
Many others – like E911 location – Emergence of SIP
New / Final perspectives
If you divide the future telephony services program into 4 categories
1.
Carrier / I2 (TDM and IP service) access service
2.
Gateway Hardware (including ancillary hardware - gateways)
3.
Campus network (single network of course)
4.
Phone set (terminals)
The vision / program gets a bit clearer and we can begin to move
forward with the deployment of a next-gen phone program
New / Final perspectives - 2
1.
We will have both TDM and IP transport services off campus over the
next few years.
2. For GU, the “soon to be installed” Avaya switch will be our carrier
gateway for at least the next few years.
3. We are a CISCO network (with potential changes at the edges) for at
least the next few years.
4. NO MORE “HENRY FORD” PHONE TERMINAL PROGRAM
(any phone you want as long as it’s black)
We want the user to pick the terminal of their choice – as long as our
program (technology and financial) supports it.

Cell phones / IP Hardphone / IPsoftclient / Analog phone / Digital
TDM phone – Black/blue/red/green – we should not care!
BOTTOM LINE: If you break it down into segments, understand what the
embedded legacy network realities are, and mesh these realities with
realistic program goals (which keep changing) - the need to “debate”
vendor A versus vendor B diminishes, and you can move forward.
MAX – Broadsoft – PaeTec Trial
Can we build a private, entirely IP phone service
between a public carrier, a private network and an
IPSwitch manufacturer?
Local phone service
LD phone service
Can we enable Production -Carrier class IPV6?
Can we get more experience with SIP enabled
terminals to MAX participants?
Can we build an off site telephony disaster recovery
trial for MAX participants.
MAX – Broadsoft – PaeTec Trial
Can PaeTec leverage this to build an IP disaster plan for switch
failure in the DC area. They only have one CO.
Can we build a production "overflow" service for MAX members
phone calls that routes out the MAX connection?
Can PaeTec build an IP connection to the BroadSoft box, from their
5ess for transport of calls?
Can "non PaeTec" customers get their calls re-routed to the
BroadSoft switch which are properly processed and transported via
the MAX network back to their campus/business? Example, can a
Verizon customer get calls forwarded or re-routed to the BroadSoft
box?
Trial Infrastructure
Broadworks Svrs
MAX
i2
Router
RS
w
ic Flo
Traff
oint
P
t-to
Poin T1
NS
Cisco
1720
AS
PRI
Cisco
5350
Sterling
5E
MS
Max Network
Gerogetown
PSTN
Phone
IP Phone
202-555-1111
DID