Cisco Unified Communications Manager
History
1997 Selsius-CallManager 1.0
In 1997, it was renamed Selsius-CallManager and changed from a video conferencing solution to a system designed to route voice calls over an IP network. It was during this time that support for the Skinny Client Control Protocol (SCCP) and Skinny Gateway Control Protocol (SGCP) were added. x
1998 Selsius-CallManager 2.0
By 1998 Selsius-CallManager 2.0 had been released. Selsius Systems was later that year acquired by Cisco Systems, Inc..
2000 Cisco CallManager 3.0
CallManager underwent a large design and engineering effort to enable scalability and redundancy to the software. Clustering was introduced at this time and [MGCP] support was added.
2001 Cisco CallManager 3.1
This CallManager release was built off of the 3.0 release. This version supported more gateway devices, IP phone devices and added more enhancements and features. The following features and enhancements were introduced in version 3.1.
Music on hold (MOH)
Support for digital interfaces on [MGCP] gateways
Added support for XML and HTML applications in Cisco IP Phones
Extension mobility
Call preservation between IP phones and MGCP gateways
TAPI (Telephony Application Programming Interface) is introduced
2004 Cisco CallManager 4.0
In 2004 Cisco made a large scale release with CallManager 4.0. Customers were pleased with a large amount of new features. Previously IP phones were restricted to only 2 calls per any given line appearance. This caveat was eliminated and IP phones could now have a user configurable maximum (up to 200) number of calls per line appearance.
Some new features and enhancements added during this release were:
Hunt group
Privacy for shared lines
Call barge
Improved security with media encryption between phones
Multi Level Administration (MLA) allowed delegated administration
Direct transfer allowed a user to select two calls from the same line and connect them together
Call join allowed users to select several calls from a line and conference them together
Additional QSIG features added
Many bug fixes
This version (as well as all Windows 2000-based versions of CallManager (4.0, 4.1 and 4.2) are End of Life (announcement was made November 15, 2007, with an End of Sale date of May, 2008).
2004 Cisco CallManager 4.1
In a short time after the release of version 4.0, Cisco released a minor upgrade to 4.1. This version focused on improved stability and support for even more features. Several utility tools were added as well. Additionally, some of the new features of CCM 4.0 include greatly enhanced conference calling features, enhanced Client Matter Code (CMC) and Forced Account Code (FAC), Multilevel Precedence and Preemption (MLPP) and Malicious Call Identification (MCID). CallManager 4.1 also enhances the encryption capabilities first introduced in CallManager 4.0. When using Cisco Phones 7940/7960/7970 or 7971 it is now possible to encrypt signaling as well as voice traffic itself.
More QSIG enhancements
Dialed number analyzer (DNA) is a tool used to analyze how dialed strings route
Forced authorization codes (FAC)
Time of day routing
Client matter codes (CMC)
Malicious Call Identification (MCID)
Increased security through addition support for encryption
2006 Cisco Unified CallManager 4.2
CallManager 4.2 was released in parallel with CallManager 5.0 on Monday the 6th of March . At the same time Cisco re branded the product “Cisco Unified CallManager”; they also added the Unified tag to all of their Voice and Video offerings (i.e. Cisco Unified Contact Center, Cisco Unified MeetingPlace).
Cisco Unified CallManager 4.2 runs on Windows 2000 and includes new PABX features over 4.1(3) (namely logging into hunt groups and call-forward on no coverage (so, if you forward a line to a hunt group, and the hunt group is unavailable or busy, you can forward calls somewhere else); Also introduced was Call Forward Unregistered, so that if you called a remote site, but the WAN link was down, you could automatically forward that call to the PSTN. This version does not include SIP end-point support.
2007 Cisco Unified CallManager 4.3
CallManager 4.3 runs on MCS Operating System 2003 (Cisco Proprietary Operating system based in Windows 2003).
2006 Cisco Unified CallManager 5.0
CallManager 5.0 was released in parallel with CallManager 4.2 on Monday 6 March 2006. Cisco Unified CallManager 5.0 is Linux based (Cisco VOS) and for the first time can use Session Initiation Protocol (SIP) to IP end-points; apart from the addition of SIP it is feature compatible with CallManager 4.1(3). CallManager 5.0 servers are being sold as pre-installed appliances. Cisco Unified CallManager 5.0 can also be installed on compatible MCS servers and Cisco approved HP and IBM servers. Users of CallManager 4.x can upgrade to Unified CallManager 5.0 and keep their current Databases by having another server on the LAN with a shared drive available during the upgrade process. New database being use is IBM Informix. Unified CallManager 5.0 comes with an introduction of a new licensing structure that is based on device-weights. A license file must be acquired and installed before any services can be activated. Operating System access is restricted to some commands. Root access is generated via remote account by Cisco TAC or Business Unit.
2007 Cisco Unified CallManager 5.1
This version is essentially bug fixes for Communications Manager 5.0.
2007 Cisco Unified Communications Manager 6.0
Cisco renamed the product to Unified Communications Manager. Version 6 was supposed to merge all features of the Linux appliance (SIP support and licensing requirements) between the Linux platform and Windows version, and it was based on Red Hat Enterprise Linux. The released version of Unified Communications Manager will not support the Windows platform.
This version added an intercom feature between endpoints (station-to-station only), and integrated Mobility Manager (single number reach to multiple destinations, IP Phone, Cell Phone, etc.).
This version utilizes a slightly different licensing model from that found in 5.X. First off, CUCM 6.0 requires service licenses (for Communications Manager, etc.) and comes with a ‘starter’ license for a single node and 50 device weights (about 10 phones), and will install natively on VMWare for lab purposes; in addition it requires a ‘feature license’ to activate the CallManager feature.
NOTE: Upgrades to Communications Manager 6.X from Communications Manager 5.X require the acquisition of a new license; proceeding with the upgrade without acquiring this license will result in a non-functional system.
Also released was Cisco Unified Communications Manager Business Edition (CUCMBE, aka Cucumber), which places Cisco Unified Communications Manager 6.0 and Cisco Unity Connections 2.0 (Voicemail) on the same server (an MCS 7828 with dual 250GB hard drives and 6GB of RAM).
Version 6.1 was released in January 2008 and contained bug fixes.
2008 Cisco Unified Communications Manager 7.0
Released in September 2008, this version was originally stated to be available in both Windows and Appliance models. However Cisco has since stated that OS Independence will not be a feature of any version of CallManager after 4.3. Cisco refers to their entire suite of products to be released in 2008 as “System 7”; major updates are expected to Presence Server and Client at the same time as Communications Manager 7.0 is released.
The database will be standardized using IBM Informix (Microsoft SQL will not appear in any version after 4.3).
Version 7 is an attempt to bring all Cisco Unified Communications products to the same version number (CUCM, CUPS, CER, CUPC, Cisco IP Communicator, UCCX, etc.)
Operation
CUCM evaluates called numbers and activates gateway events to receive or send calls to the PSTN or IP Network.
The Cisco CallManager is installed on either a Cisco Media Convergence Server (MCS) or Cisco approved server.
Typically, a CCM cluster can manage up to 30,000 IP Phones using 20 Servers with incorporates a publisher, two TFTP servers, 8 Subscribers (four primary and four secondary) and up to nine media resource servers.
The Cisco Unified Communications Manager “Supercluster” can manage up to 60,000 phone numbers, and incorporates a publisher, two TFTP servers, 16 Subscribers (eight primary and eight secondary) and up to nine media resource servers.
Administration and Configuration
The configuration of the CUCM is done primarily through a web interface. Therefore the CUCM supports the following browsers: Microsoft Internet Explorer (supported from version 5.x) and Mozilla Firefox. The Bulk Administration Tool (BAT) is available for large imports, exports and changes. In addition to an administrative web access each user may also make changes to the telephony features.
Access to the Linux operating system (root access) and the database is no longer available from CUCM version 5.x and higher. The more recent CUCMs only offer a command line interface (CLI) with a limited command set for troubleshooting, including queries regarding system information or database information. The root access is reserved for the technical support from Cisco (TAC).
Provisioning systems, including TiM (Telephone Interface Communications Manager) simplify the management of the Cisco Unified Communications Manager (CUCM). These programs facilitate and automate repetitive tasks and consequently relieve the IT department. Furthermore, provisioning systems not only increase the efficiency of the CUCM, but also add new features. With the support of TiM the CUCM is expanded by:
Multi-client capability
Comprehensive rights & roles system
Cluster capability
Redundancy
Wizards for recurrent tasks
TemplateEngine for recurrent settings
Multilingual and ergonomic user interface
Cisco Unified Communications Manager Express
Cisco Unified Communications Manager Express (CUCME), formerly Cisco Unified CallManager Express and Cisco CallManager Express, is a Cisco IOS based IP-PBX for small medium business, enterprise branch office and commercial customers. It provides a rich set of call control and voice application features for the above mentioned customer profiles. It supports Cisco IP phones using Skinny Client Control Protocol (SCCP) and Session Initiation Protocol (SIP). Call Manager Express also provides a rich set of traditional PSTN connectivity options using both digital and analog lines.
For advanced customers, CUCME also provides integrations with TAPI clients, has a basic Automatic call distribution application, provides an integrated Auto Attendant, Voicemail and Interactive voice response systems.
There have been very few that have attempted to provide comprehensive reporting for Cisco UCME. The logs are complex and voluminous. RSI was the first to offer Shadow CMS for communication management.
More information on CUCME can be found on the external Cisco Support Wiki – Cisco CME Support Wiki
References
^ Cisco Systems acquisition of Selsius Systems
^ “Cisco Unified Communications Manager – Hardware, Software and Clustering”. http://searchnetworkingchannel.techtarget.com/generic/0,295582,sid100_gci1316822,00.html. Retrieved 2009-02-05.
External links
Cisco.com
Cisco Unified Communications Manager (CallManager)
Comparable is the Clarity Communication Center
Official TiM website
Categories: Cisco products | VoIP software
I am an expert from China Quality Dress, usually analyzes all kind of industries situation, such as flavored powder , powdered milk bulk.
Processing your request, Please wait....
