1 / 14

IPT @ UCAR

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

deepak
Download Presentation

IPT @ UCAR

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IPT @ UCAR Teresa Shibao & Paul Dial

  2. The Major Components of IPT • Communications Manager (formerly Call Manager) • Voicemail • Phones • Miscellaneous others

  3. 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

  4. Communications Manager (cont.) • Upgraded from version 3.3(3) in April of 2006Current 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

  5. Cisco Unified Communications Manager Releases & Upgrade Paths 2005 2006 2007 Windows Server 2000 3.3(5) CCM 3.X Windows 2000 Windows Server 2003 4.3(1) CCM 4.X 4.0(2a) 4.1(3) 4.2(3) 4.2(1) Appliance Model 5.0(4) 5.1(2) 5.1(2) 5.1(1) CCM 5.X Appliance Model CCM 6.X 6.0(1) Shipping Upgrade Path Released 6/2007 Our Planned Upgrade Path

  6. 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 ConnectSimultaneous ringing for multiple devices Single voice messaging system • Adding new features all the time

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

  8. 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)

  9. 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

  10. Phone Futures • Should we move to SIP? • Other vendors? • Wireless?

  11. 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

  12. 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

  13. No change is invisible • Test, test and check again • Users notice differences • Notification is important

More Related