CallManager 4 to Communications Manager 6 training notes, day 1

| No Comments | No TrackBacks

The three-day course that Doug and I are attending is on upgrading from CM 4 to 6 and becoming familiar with version 6, including understanding some of the new features and noting some of the changes in existing features.

  • Communications Manager 6.x is stable (comparable to 4.1.3; contrast with 5.x). Statement based on qualititative data (customer discussion in users groups, at training classes).

  • 6.x - lots of SIP support. SIP on local endpoints "sucks" (says the class instructor, who is not a Cisco employee) - not because of CM's support of it but because of limitations of SIP. SCCP is a high quality protocol for local endpoints. Use SIP for remote/soft clients.

  • Operating system is Linux based on RedHat distro; database is IBM Informix.

  • Appliance model restricts access to filesystem and database. My reaction is to want to fight against this but can see the benefits of closing this up. Access to database for CDR: no ODBC. Can push out the CDR records to an external server on a regular interval. (CSV)

  • Realtime Monitoring Tool (RTMT) is improved and is now a primary way of accessing many data/statistics of CM.

  • "Workspace Licensing" - the Standard offering contains most of the PSU per-user needs including IP phone, voice mail (Unity voice-mail-only), user control of devices, plus softphone (IP communicator) which we are becoming more interested in. IP contact center agents would still need to be licensed individually.

The actual upgrade process is mostly automated using provided upgrade tools. Some files need to be copied manually from the 4.x installation. Upgrading CM itself is not too bad. The devil is in the supporting applications, namely Unity and CRS (IP contact center and IVR). Unity 5 supports both CallManager 4.x and 6.x and so can be upgraded prior to CM. CRS 3.5.4 is not supported with CM 6.x. The upgrade path here would have to be CRS to version 4, then upgrade CallManager and CRS immediately afterward to the version that works with CM6. We felt bad for others in the class who had a large suite of Cisco IP telephony apps hooked into Call Manager.

No TrackBacks

TrackBack URL: https://blogs.psu.edu/mt4/mt-tb.cgi/8152

Leave a comment

March 2009

Sun Mon Tue Wed Thu Fri Sat
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30 31        

Contact Me


AIM: TNS BillS

View William Simon's profile on LinkedIn

Donate

Make a gift
Like this blog? Support education and research at Penn State by donating any amount to an area of your choice.

Subscribe

Blogroll

Disclaimer

We are Penn State, but I am not. Opinions expressed on this blog are those of the author and do not represent the opinions of The Pennsylvania State University or any division therein, including but not limited to the author's workgroup, department, administrative unit, or campus. Technologies and ideas discussed on this blog do not describe a production service unless noted.