IPT @ UCAR

Teresa Shibao & Paul Dial

The Major Components of IPT

Communications Manager (formerly Call Manager)

Voicemail Phones Miscellaneous others

Communications Manager (CM)

Current version 4.1(3)Windows OS

3 CMs in our cluster– Publisher - keeper of the database, call records,

tftp server (device config files), and where changes are made

– 2 Subscribers – handle the traffic, phones, gateways (trunks) and voicemail access

Communications Manager (cont.)

Upgraded from version 3.3(3) in April of 2006

Current version is very stable – Provides increase redundancy– Long distance account codes kept in CM

database instead of separate server/application– A few additional features provided to users

through the web interface

Cisco Unified Communications Manager Releases & Upgrade Paths

CCM 3.X

CCM 4.X

CCM 5.X

Shipping

4.2(3)

3.3(5)

4.1(3)

Windows Server 2000

4.0(2a)

Windows 2000

2005 2006

5.0(4)

Upgrade Path

5.1(1)

CCM 6.X 6.0(1)

Appliance Model

Released 6/2007

2007

4.3(1)

Appliance Model

4.2(1)

Windows Server 2003

5.1(2)5.1(2)

Our Planned Upgrade Path

CM Futures

Move to Linux OS Database resiliency

– Features still work when publisher off-line

Applications that previously required a separate server are being migrated into CM– Mobile Connect

Simultaneous ringing for multiple devices Single voice messaging system

Adding new features all the time

Voicemail

Still using the original hardware purchased in January 2003

Windows OS, MS Exchange based 1650 user mailboxes Current version - Unity 4.0(5) Upgraded from version 3.1(5) In December of 2006

– Cisco support was ending – No real additional features – Migration path to newer Unity versions & Unity Connections

Voicemail (cont.)

Currently testing Unity Connections 1.2– Time to replace existing server– Still Windows OS– Some IMAP or web interface capabilities?– Voice Recognition?

Can be upgraded to version 2.0– Appliance based (Linux)

Phones

~2050 of our standard desk set (7960G) in the system database

Phones are 10/100 switches– What do we do as we move to 1G?

Cisco has not published an End of Life notice– Usually 5 years of support after notice

Phone Futures

Should we move to SIP? Other vendors? Wireless?

Miscellaneous Others

Analog– Started out with problem prone 6500 blades– VG248s performing well

Monitoring– Initial product was Prognosis – Cisco Unified Operations Manager (CUOM)

Conferencing– Conference Connection – audio only– Meeting Place Express (Linux)

Emergency Responder (CER)– No real changes here, very stable

Issues

Our biggest problem has been with phones– Phones get unplugged and are not locatable– Hook switch failures

Monthly Windows patches Hardware rollover

– Servers– Gateways– Eventually phones

No change is invisible

Test, test and check again Users notice differences Notification is important