Table Of Contents
Release Notes for Cisco Unified CallManager Release 5.1(2b)
Determining the Software Version
HP NC-Series Broadcom Firmware Updates Available for Supported NICs.
iLO Firmware on MCS-7825H1, MCS-7835H1 and MCS-7845H1
Smart Array 6i Requires HD Firmware Update to Avoid POST Notification
Smart Array 5i Requires HD Firmware Update to Avoid POST Notification
CSCsi75567 MCS-7825H2-IPC1 Reboots Randomly
CSCsg97059 SIP and H323 Third-Party Device
CSCsc81681 Complex Database Causes Extension Mobility Performance Degradation
Music On Hold (MOH) Source Files
Configuring Fixed Music on Hold by Using the Cisco USB MOH Adaptor
Verify Adequate Disk Space Prior to Installation/Upgrade
Online Help for Cisco Unified CallManager Release 5.1(2x)
CSCsh58558 BIOS Flash Not Forced
CSCsh50712 IBM 7835I2 Server BIOS Flash Files Corrupt
CSCsh50685 IBM BIOS MTM Change
CSCsh20023 Some Browsers and WinZip
Upgrading from Cisco Unified CallManager Release 5.0(4) to Release 5.1(x)
MTP and Cisco Unified IP Phones That Are Using SIP
Using SIP Trunks Between Release 4.x and 5.x Systems
Configuring Phones That are Running SIP with the Same Directory Number
New and Changed Information for Cisco Unified CallManager Release 5.1(2b)
2007 Daylight Saving Time Adjustment for New Zealand
CSCsj72914 Conference Calls Experience Poor Audio Quality
CSCsj42921 Abbreviated Dialing Does Not Work for Index 43 and Higher
New and Changed Information for Cisco Unified CallManager Release 5.1(2a)
CSCsj45679 Data Validation Fails for Lowercase Device Names
CSCsj42131 User with Incorrect Primary Extension in Directory Export
CSCsj22669 User and User Profile Association Issue in Directory Export
CSCsi20684 CSS Call Forward All
CSCsi71128 DMA Requires a Long Time to Run
New and Changed Information for Cisco Unified CallManager Release 5.1(2)
New and Changed Information for Cisco Unified CallManager Release 5.1(2) Administration
BAT Support for VG224 Gateways
Call Forward All Calling Search Space Backward Compatibility
Locations and Region Enhancements
New and Changed Information for Cisco Unified CallManager Serviceability
New and Changed Information for Cisco Unified CallManager Release 5.1(1b)
New and Changed Information for Cisco Unified CallManager Administration
Cisco Unified CallManager Installation
General Administration Enhancements
Cisco Unified CallManager Administration Menu Updates
Third-Party SIP Phone Enhancements
Phone Configuration Enhancements
Phone Button Configuration Enhancements
License Capabilities Assignment
Phone Configuration—Product-Specific Configuration Changes
Additional Corporate Directory Support
New and Changed Information for Cisco Unified Communications Operating System Administration
New CLI Commands and Command Options
New and Changed Information for Cisco Unified CallManager Features
Arabic Language (right to left) Support
New and Changed Information for Cisco Unified CallManager Applications
DirSync Application Enhancements
New and Changed Information for Cisco Unified CallManager Bulk Administration Features
New and Changed Information for Cisco Unified CallManager Security Features
TFTP Exclude Digest Credentials Check Box Display
Upgrading Cisco Unified IP Phones to Authenticate with LSCs Not MICs
New and Changed Information for Cisco Unified CallManager Serviceability
Cisco Unified CallManager Serviceability Administration
Cisco Unified CallManager Real-Time Monitoring Tool (RTMT)
Cisco Unified CallManager Analysis and Reporting (CAR)
New and Changed Information for Third-Party API
New and Changed Information for Cisco Unified IP Phones
Automated Alternate Routing (AAR) Limitation with Remote Gateways
Call Throttling and the Code Yellow State
New Column in the User Options Find and List Directory Entries Window
Searching for a Device in Cisco Unified Real Time Monitoring Tool with the Any Status Option
Planning Your Software MTP Configuration
Ad Hoc Conference Settings Restrictions for SIP Phones
Alphanumeric Characters Allowed in the Pickup Group Name Field
Cisco Unified CallManager Features and Services Guide Indicates Support for Disks of Less Than 72GB
Survivable Remote Site Configuration
Changing HostName/IP Address During an Upgrade
CAPF System Interactions and Requirements
Recommended Number of Devices in Device Pool
Updated Voice Gateway Model Information
Number of Login or Logout Operations that Cisco Extension Mobility Supports
Obtaining Documentation, Obtaining Support, and Security Guidelines
Cisco Product Security Overview
Release Notes for Cisco Unified CallManager Release 5.1(2b)
Updated May 20, 2008
Note
A new Cisco advisory is posted at
http://www.cisco.com/warp/public/707/cisco-sa-20070801-IOS-voice.shtml.
Summary
Cisco recommends that customers who run Cisco Unified CallManager Release 5.1(2) upgrade to release 5.1(2b). This recommendation is made because of the following information.
Multiple voice-related vulnerabilities are identified in Cisco IOS software, one of which (malformed SIP packet) is also shared with Cisco Unified Communications Manager.
SIP is a protocol that is used to establish, modify, and terminate multimedia sessions. Most commonly, SIP is used for Internet telephony. SIP call signaling can use UDP (User Datagram Protocol) or TCP (Transport Control Protocol) as an underlying transport protocol. In all cases vulnerabilities can be triggered by processing a malformed SIP packet.
A malformed SIP packet can cause a vulnerable device to crash and can allow arbitrary code to be executed. These vulnerabilities are documented as the following Cisco Bug ID:
CSCsi80102 Cisco Unified Communications Manager crashes while processing malformed SIP packet.
Successful exploitation of the vulnerabilities listed as Cisco Bug ID CSCsi80102 can lead to remote code execution.
Successful exploitation of other SIP-related vulnerabilities listed in the Cisco Systems advisory can cause the affected device to crash. Repeated exploitation could result in a sustained denial of service (DoS) attack.
When considering software upgrades, also consult http://www.cisco.com/go/psirt and any subsequent advisories to determine exposure and a complete upgrade solution.
In all cases, you should exercise caution to be certain that the devices to be upgraded contain sufficient memory and that current hardware and software configurations will continue to be supported properly by the new release. If the information is not clear, contact the Cisco Technical Assistance Center ("TAC") or your contracted maintenance provider for assistance.
Cisco has made free software available to address the vulnerabilities for affected customers. Fixed Cisco IOS software fixes for all vulnerabilities mentioned in the advisory.
There are no workarounds available to mitigate the effects of any of the vulnerabilities apart from disabling the protocol or feature itself.
Obtaining Fixed Software
Cisco has made free software available to address these vulnerabilities. Prior to deploying software, customers should consult their maintenance provider or check the software for feature set compatibility and known issues specific to their environment.
Customers may only install and expect support for the feature sets they have purchased. By installing, downloading, accessing or otherwise using such software upgrades, customers agree to be bound by the terms of Cisco's software license terms found at
http://www.cisco.com/public/sw-license-agreement.html, or as otherwise set forth at Cisco.com Downloads at
http://www.cisco.com/public/sw-center/sw-usingswc.shtml.These release notes describe the new features, resolved caveats and open caveats for Cisco Unified CallManager Release 5.1(2b).
Note
Before you install Cisco Unified CallManager 5.1(2b), Cisco recommends that you review the "Important Notes" section for information about issues that may affect your system.
Note
Cisco recommends that you check Cisco.com for the latest software updates to Cisco Unified CallManager and its applications and download and install the latest updates on your system before the deployment of your Cisco Unified CallManager system. For a list of commonly used URLs, see the "Upgrading System Software" section.
Contents
These release notes discuss the following topics:
•
•
•
•
•
•
Introduction
Cisco Unified CallManager, a network business communication system, provides high-quality telephony over IP networks. Cisco Unified CallManager enables the conversion of conventional, proprietary, circuit-switched PBXs to multiservice, open LAN systems.
System Requirements
Make sure that you install and configure Cisco Unified CallManager Release 5.1(2b) on a Cisco Media Convergence Server (MCS) appliance.
You may also install Cisco Unified CallManager on a Cisco-approved HP server configuration or a Cisco-approved IBM server configuration.
Cisco Unified CallManager 5.1(2b) requires a minimum of the following items on the Cisco MCS appliance:
•
•
•
Note
Supported Platforms
To find which servers support the Cisco Unified CallManager 5.1(2b) release, refer to http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_brochure_list.html.
Determining the Software Version
To determine whether you need to upgrade the Cisco Unified CallManager software that you are using, launch Cisco Unified CallManager Administration. The following information displays:
•
•
Upgrading System Software
You can access the latest software upgrades for Cisco Unified CallManager 5.1 on Cisco.com. Table 1 lists the URLs from which you download the software.
Warning
Table 1 Download URLs for Software Upgrades
Cisco Unified CallManager 5.1
Locale installers
http://www.cisco.com/kobayashi/sw-center/telephony/callmgr/ locale-installer.shtm
Phone firmware
http://www.cisco.com/pcgi-bin/tablebuild.pl/ip-7900ser
http://www.cisco.com/pcgi-bin/tablebuild.pl/ip-7900ser-crypto
Cisco Security Agent (CSA)
Upgrade Assistant
http://www.cisco.com/pcgi-bin/tablebuild.pl/callmgr-utilpage
Related Documentation
The documentation that supports Cisco Unified CallManager Release 5.1(2b) comprises existing release 5.0(4) documentation that is listed in the Cisco Unified CallManager Release 5.1(2) Documentation Guide, as well as the following release 5.1(x) documents:
•
•
•
•
•
•
•
•
Limitations and Restrictions
A list of compatible software releases represents a major deliverable of Cisco Unified Communications System testing. The recommendations, which are not exclusive, represent an addition to interoperability recommendations for each individual voice application or voice infrastructure product.
For a list of software and firmware versions of IP telephony components and contact center components that were tested for interoperability with Cisco Unified CallManager 5.1(x) as part of Cisco Unified Communications System Release 5.1(x) testing, see
http://www.cisco.com/go/unified-techinfo
Note
Important Notes
The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco Unified CallManager Release 5.1(x).
Important Notes for Cisco Unified CallManager Release 5.1(2b)
•
•
•
•
•
Important Notes for Cisco Unified CallManager Releases 5.1(1) through 5.1(2a)
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
HP NC-Series Broadcom Firmware Updates Available for Supported NICs.
The upgrade includes
•
•
You can update firmware manually by downloading and booting from the HP Firmware Maintenance CD version 7.80 (10 May 07) that is located at http://h18023.www1.hp.com/support/files/server/us/download/27225.html
iLO Firmware on MCS-7825H1, MCS-7835H1 and MCS-7845H1
iLO firmware on MCS-7825H1, MCS-7835H1, and MCS-7845H1platforms may include versions older than version 1.82. The firmware update, version 1.82, contains critical bug fixes and is the minimum version required. The current released version is 1.84.
Workaround
Download the firmware update from the Hewlett-Packard site and apply them manually.
MCS-7835-H1 and 7845-H1
http://h18000.www1.hp.com/support/files/server/us/family/model/5561.html?lang=en&cc=usSmart Array 6i Requires HD Firmware Update to Avoid POST Notification
You should upgrade hard drive models that experience excessive SCSI command timeout . Failure to upgrade may result in the bus down-shifting from Ultra 320 to Ultra 3.
Upgrade following hard disk models to the specified versions:
Workaround
You can update firmware manually by downloading and booting from the HP Firmware Maintenance CD version 7.80 (10 May 07) that is located at http://h18023.www1.hp.com/support/files/server/us/download/27225.html
Smart Array 5i Requires HD Firmware Update to Avoid POST Notification
Smart Array 5i version 2.66 recommends updates for some SCSI disk drive models after the Smart Array firmware gets installed.
Workaround
You can download updates and apply them manually. Find information concerning specific hard drive models and the location of firmware updates at
ftp://ftp.compaq.com/pub/softlib2/software1/doc/p1821026293/v33269/266-5i_532.pdfCSCsi75567 MCS-7825H2-IPC1 Reboots Randomly
Sporadic reboots of the 7825H2 servers get triggered during long system hangs. ASR functionality autorecovers the servers after 10 minutes of kernel unresponsiveness. Event timing ranges from once every 3 months to once every 3 days.
Workaround
See http://www.cisco.com/warp/public/770/fn62850.shtml.
CSCsg97059 SIP and H323 Third-Party Device
Calls on Cisco Unified CallManager Release 5.x(x) that involve both SIP and H323 third-party device may experience one-way video or no video because of dynamic payload type problems. At this time, no workaround exists.
CSCsc81681 Complex Database Causes Extension Mobility Performance Degradation
Symptom
When you initiate a login from a phone, the database requests a change notify. The phone configuration window changes, and the Extension Mobility login perfmon counter gets updated.
After the RTMT EM perfmon counter and phone configuration window both validate a successful EM login, it can take up to 60 minutes to see the change on the phone.
After you log in, if you see that the phone screen did not change, you can press the service button, and the interface will ask you to log out even though the phone login did not complete.
Cause
The system introduces the EM logins/logouts to Cisco Unified CallManager at a faster rate than it can respond. Cisco Unified CallManager does not reset the phone quickly enough, so the queue to reset the phone backs up when too many change notifications reach the Cisco Unified CallManager.
In the series of events during a login, phone reset change notify gets lower priority in the queue of change requests; so the phone reset change notify requests build up a backlog of queued requests. This backlog, in the event of a stress performance test, creates a huge lag time.
Disaster Recovery Restore Attempt on a Publisher Node Fails with an Error on the Cisco Unified CallManager Database Component
When you attempt to restore the publisher node or database to a previously saved version by using DRS and the restore fails, look at the DRS logs on the Cisco Unified CallManager database component. You will see the following information:
CCMDB Restore failed, installdb failed
425: Database is currently opened by another user.
Perform the following steps to complete the restoration.
Step 1
admin:utils service listRequesting service status, please wait......Cisco Database Layer Monitor[STOPPED]...admin::59 pts/0 00:00:00 grep dbmonStep 2
admin:utils service listRequesting service status, please wait......Cisco Database Layer Monitor[STARTED]...admin:
Music On Hold (MOH) Source Files
Music audio source files must comprise .wav files in one of the following formats:
•
•
Configuring Fixed Music on Hold by Using the Cisco USB MOH Adaptor
The fixed music on hold audio source gives you a way to use a custom audio source (that is, radio, mp3 player) as the music on hold audio source.
To do this, ensure each MOH server is provisioned with a Cisco USB MOH adaptor.
Installing the Adaptor
Step 1
Step 2
Step 3
Note
Step 4
Step 5
The Fixed MOH Audio Source Configuration window displays. The system assigns the Source ID.
Step 6
Step 7
Step 8
Step 9
Verify Adequate Disk Space Prior to Installation/Upgrade
To avoid problems, you should verify that adequate disk space exists on the common partition prior to initiating an upgrade.
Use the following criteria to determine how much space will be required:
•
•
•
Note
CSCsi52140 Extension Mobility Impacts Upgrades from Cisco Unified CallManager Release 4.1(x) to Cisco Unified CallManager Release 5.1(x) or from Cisco Unified CallManager 5.x to Cisco Unified CallManager Release 6.x
Ensure that users are not logged in to their phones during an upgrade from Cisco Unified CallManager Release 4.1(x) to Cisco Unified CallManager 5.1(x). Phones that users are logged in to during the upgrade will not function properly.
Phones that are at their default profile during an upgrade will function properly
Online Help for Cisco Unified CallManager Release 5.1(2x)
Because these release notes comprise the only updated documentation for Cisco Unified CallManager Release 5.1(2x), the online help version specifies 5.0(4).
CSCsh58558 BIOS Flash Not Forced
Hewlett-Packard servers forced the BIOS flash during a fresh install if the BIOS version on the server did not match the Cisco Unified CallManager image version. Changes ensure that the BIOS does not get flashed when the server has a later (newer) BIOS than exists on the Cisco Unified CallManager release.
CSCsh50712 IBM 7835I2 Server BIOS Flash Files Corrupt
On the Cisco MCS 783512 Unified CallManager appliance, in the case of a fresh software-only installation, if the server that was purchased from IBM has a newer BIOS version than the one that is bundled in Cisco Unified CallManager, the installation will fail.
CSCsh50685 IBM BIOS MTM Change
Be aware that software-only IBM servers (including 7815I2, 7825I2-2800, 7825I2-3400, 7835I1, 7835I2, 7845I1) that were purchased after IBM rolled out their Xcellator ordering process are impacted, and the installation of Cisco Unified CallManager Release 5.1(1) will fail.
Workaround
Upgrade to Cisco Unified CallManager 5.1(1b) or later, or
Manually change MTM strings with help from IBM field support by using these steps:
Step 1
Step 2
Step 3
CSCsh20023 Some Browsers and WinZip
When the Cisco Unified CallManager upgrade patch file is downloaded from cisco.com, some browsers may download files with the extension tar.gz.sgn as tar.gz.gz.
Workaround
After the patch file is downloaded, rename it with the extension .gz.sgn (in place of.gz.gz) and proceed with the install.
CSCsh50754 Do Not Install Cisco Unified CallManager Release 5.1(1) or 5.1(1a) on Hewlett-Packard 7835H2 or 7845H2 Servers
If you install Cisco Unified CallManager Release 5.1(1) or 5.1(1a) on Hewlett-Packard 7835H2 or 7845H2 Windmill server, the server will become nonbootable.
Workaround
Do not install Cisco Unified CallManager Release 5.1(1) or 5.1(1a) on the new servers. You must install Cisco Unified CallManager Release 5.1(1b) or later instead.
Upgrading from Cisco Unified CallManager Release 5.0(4) to Release 5.1(x)
During the upgrade of Cisco Unified CallManager, the server experiences high disk I/O activity. This can adversely impact call processing. In the worst case, phones that are currently registered with that Cisco Unified CallManager server may fail over to their backup server. Cisco strongly recommends that you ensure that all trace levels are set to the default level on all servers in your cluster before you start the upgrade process.
Furthermore, if you have concerns that the upgrade may impact call-processing service, Cisco recommends that you perform the upgrade during off-peak hours. If you want to minimize the disruptions to the call-processing service, you may choose to stop the Cisco Unified CallManager service on the server before you start the upgrade process.
As always, follow standard best practices while you are performing a Cisco Unified CallManager upgrade.
MTP and Cisco Unified IP Phones That Are Using SIP
You can configure Cisco Unified CallManager SIP devices (lines and trunks) to always use an MTP. If the configuration parameters are set to not use an MTP (default case), Cisco Unified CallManager will attempt to dynamically allocate an MTP if the DTMF methods for the call are not compatible.
For example, SCCP phones support only out-of-band DTMF, and Cisco Unified IP Phones (7905, 7912, 7940, 7960) that are using SIP support RFC2833. Because the DTMF methods are not identical, Cisco Unified CallManager will dynamically allocate an MTP.
If, however, a SCCP phone that supports RFC2833 and out-of-band use, such as Cisco Unified IP Phone 7971, calls a Cisco Unified IP Phone 7940 that is using SIP, Cisco Unified CallManager will not allocate an MTP because both phones support RFC2833. Because the same type of DTMF method is supported on each phone, no need exists for an MTP.
Caution
If you check the "MTP Required" check box, you may experience problems with Cisco Unified CallManager features such as shared line.
When you leave this check box unchecked, Cisco Unified CallManager will still insert MTPs dynamically as needed, so you will experience no benefit from checking the "MTP Required" check box for Cisco Unified IP Phones that are using SIP.
Although this configuration option for Cisco Unified IP Phones that are running SIP may be removed in a future Cisco Unified CallManager release, Cisco will continue to support it for generic, third-party phones that are running SIP.
Rebuilding Failed RAID Drives
A RAID drive may fail and may require manual intervention to rebuild one of the physical drives in a logical pair during normal Cisco Unified CallManager operation.
RAIDed disks, also termed RAID arrays, get arranged in logical pairs. A single logical pair comprises two physical drives. The system keeps the pair of drives in sync with the same data in real time to provide redundancy ultimately for data integrity and assurance. When one physical drive fails to synchronize or begins to experience read or write failures, you may need to rebuild the drive. Many things can cause the failure, but the main concern remains whether the data in a logical drive pair is compromised due to failures in one of the physical drives.
Monitoring software usually detects RAID failures, and failures get reported as a failed drive or a loss of drive redundancy. The procedure for rebuilding a failing drive follows and applies to all Cisco MCS 7825, 7835, and 7845 Unified CallManager Appliances.
Note
Check the status of the RAID array by using the CLI show hardware command and verify whether the Status field reads Ok or Okay. An example follows:
admin:show hardwareHW Platform : 7835IProcessors : 1Type : Intel(R) Xeon(TM) CPU 3.06GHzCPU Speed : 3066Memory : 2048 MBytesObject ID : 1.3.6.1.4.1.9.1.585OS Version : UCOS 2.0.1.0-37RAID Details :Found 1 IBM ServeRAID controller(s).Read configuration has been initiated for controller 1...----------------------------------------------------------------------Logical drive information----------------------------------------------------------------------Logical drive number 1Status of logical drive : Okay (OKAY)RAID level : 1Size (in MB) : 70006Write cache status : Temporary write through (TWT)Number of chunks : 2Stripe-unit size : 8 KBAccess blocked : NoPart of array : AArray A stripe order (Channel/SCSI ID) : 1,0 1,1 Command completed successfully.If the RAID array status field does not read Ok or Okay (for example, shows Degraded or Critical), perform the following steps:
Step 1
For information on how to access the console to perform CLI commands, see the Cisco Unified Communications Operating System Administration Guide.
Step 2
Step 3
Step 4
a.
1:ServeRAID-5i Slot 2, Logical drv=1, Firmware=7.12.07, Status=Fail1 Drive(s) not responding or found at new location(s)Press F2 Detailed informationF4 Retry the commandF5 Change the configuration and set the drive(s) defunctF10 Continue without changing the configurationb.
Step 5
Step 6
Step 7
Step 8
If the status does not read Ok or Okay, you may need to replace the physical drive.
Using SIP Trunks Between Release 4.x and 5.x Systems
Cisco Unified CallManager Release 5.0 and later and Cisco Unified CallManager Release 4.0 and later support TCP and UDP as Transport Types when they are used with SIP trunks. However, release 4.x uses one TCP connection per SIP call; 5.x supports multiple SIP calls over the same TCP connection (referred to as TCP connection reuse).
The following Cisco products support TCP; however, not all support TCP Reuse (see Table 4 for more information):
•
•
•
•
•
•
•
Table 4 lists the SIP trunk connectivity that is supported between Cisco Unified CallManager Release 4.x and 5.x and the IOS gateway.
If a release 5.x system makes multiple calls over a TCP-based SIP trunk to a 4.x system, the 4.x system will only connect one call. The rest of the calls will not get connected.When using SIP trunks between 4.x and 5.x systems, you must configure both systems to use UDP as the Outgoing Transport Type, so calls between the release 4.x and 5.x systems will connect properly. (See Table 4.)
To configure UDP, use Cisco Unified CallManager Administration.
•
•
For more information about SIP trunks, see the Cisco Unified CallManager System Guide and the Cisco Unified CallManager Administration Guide.
Configuring Phones That are Running SIP with the Same Directory Number
Cisco Unified IP Phones 7906, 7911, 7941, 7961, 7970, and 7971 that are running SIP can support multiple lines with the same directory number in different partitions; however, configuring and using other Cisco Unified IP Phones that are running SIP with multiple lines with the same directory number do not get supported.
New and Changed Information for Cisco Unified CallManager Release 5.1(2b)
The following section contains information about the new features that the Cisco Unified CallManager Release 5.1(2b) contains.
•
•
•
Additional Servers Supported
This release of Cisco Unified CallManager includes support for four additional servers. The servers are MCS-7816H3, MCS-7816I3, MCS-7825H3 and MCS-7825I3.
2007 Daylight Saving Time Adjustment for New Zealand
As announced in New Zealand, beginning this year, daylight saving time (DST) starts on the last Sunday in September and will end on the following first Sunday in April.
Cisco incorporated changes into this release, so the new DST implementation will correctly occur on September 30th, 2007 and will end on April 6th, 2008.
Warning
CSCsj72914 Conference Calls Experience Poor Audio Quality
Conference calls that are using the software media resources (MTP, MOH, and CFB) on a Cisco Unified CallManager 5.1(2x) server experience poor audio quality when they traverse a WAN that has QoS implemented.
Because the RTP that is coming from Cisco Unified CallManager has a DSCP of 0x00 these packets can get queued and/or dropped behind other voice signaling and RTP packets at the WAN router. Depending on network conditions for the WAN link this can cause poor audio quality.
Current Condition
The release of Cisco Unified CallManager Release 5.1(2b) resolves this problem.
CSCsj42921 Abbreviated Dialing Does Not Work for Index 43 and Higher
Abbreviated dialing does not work for indexes 43 and higher.
Current Condition
The release of Cisco Unified CallManager Release 5.1(2b) resolves this problem.
New and Changed Information for Cisco Unified CallManager Release 5.1(2a)
The following sections contain information about the caveats that are resolved in the release of Cisco Unified CallManager 5.1(2a)
•
•
•
•
•
CSCsj45679 Data Validation Fails for Lowercase Device Names
Caveat
DMA 5.1(2) data validation reports rules compliance errors that are related to device names that contain lowercase characters. If you migrate to Cisco Unified CallManager 5.1(2) despite these error messages, various administrative activities that involve these records and those that use them can fail.
Current Condition
The release of Cisco Unified CallManager Release 5.1(2a) and Data Migration Assistant 5.1(2b) resolves this problem.
CSCsj42131 User with Incorrect Primary Extension in Directory Export
Caveat
After migration from Cisco Unified CallManager Release 4.x to Cisco Unified CallManager Release 5.x, the user gets associated with the wrong primary extension.
Current Condition
The release of Data Migration Assistant 5.1(2b) resolves this problem.
CSCsj22669 User and User Profile Association Issue in Directory Export
Caveat
Multiple CNN profiles per user exist in the Cisco Unified CallManager Release 4.x directory. After an upgrade to Cisco Unified CallManager 5.1(2), despite a clean DMA run, lost/missing/incorrect login profiles and device associations exist.
Current Condition
The release of Data Migration Assistant 5.1(2b) resolves this problem.
CSCsi20684 CSS Call Forward All
Caveat
DMA fails to validate when invalid contents exist in the CSSForCFA table and one of the following errors is received in the DMA Backup log:
Pre-DMA5.1(2b):
The following directory numbers have invalid CallingSearchSpaces for forward: 61880. Please remove or set these CallingSearchSpaces for these DNs and rerun DMA.
Exportable format of Cisco CallManager databases backed up successfully.
DMA5.1(2b):
Failure: #####>>> Invalid Call Forward All Calling Search Space settings have been detected. The following directory number(s) are involved: [ 61880 ]. These DN records, (usually Phone related), must be either corrected or removed and DMA then re-executed. The problem data may have resulted from either residual settings from an older CM version or from an external, adjunct, or third-party CM call forwarding application directly storing into this column. If the affected DN records are obsolete or easily re-entered, they should be deleted via the administration menus. The administrative interface does not provide any means to otherwise correct the problem data. If the problem records can not be deleted, correction will require the use of Enterprise Manager or other SQL access tools. Correction using these direct DB modification tools may require the approval and assistance of Cisco Support. If pursuing record correction, the following SQL query may be helpful to identify problem records that can not be deleted: [ SELECT * FROM NumPlan WHERE CSSforCFA IS NOT NULL AND CSSforCFA NOT LIKE '{%' ]. Additionally, correct settings for the CSSforCFA column include either empty/null or the PKID of a valid CSS in the form '{pkid}:{}'.
modExportDatabase=Failure
Could not complete database processing successfully.
Failed to back up exportable format of Cisco CallManager databases.
Current Condition
The release of Data Migration Assistant 5.1(2b) resolves this problem.
CSCsi71128 DMA Requires a Long Time to Run
Caveat
Upgrading to Cisco Unified CallManager Release 5.x from releases of Cisco Unified CallManager prior to release 4.1(3), DMA execution takes a very long time in the premigration phase. If this occurs, you should wait for completion. A delay in this phase of up to 23 hours for 45,000 devices has occurred.
Current Condition
The release of Data Migration Assistant 5.1(2b) resolves this problem.
New and Changed Information for Cisco Unified CallManager Release 5.1(2)
The following sections describe new features and changes that are pertinent to Cisco Unified CallManager Release 5.1(2). The sections may include configuration tips for the administrator, information about users, and where to find more information.
•
•
New and Changed Information for Cisco Unified CallManager Release 5.1(2) Administration
Cisco Unified CallManager Release 5.1(2) made the following changes:
•
•
•
AXL Field Enhancement
Cisco Unified CallManager Release 5.1(2) supports the following new tags that have been added to the AXL APIs:
1.
2.
3.
•
•
•
•
•
BAT Support for VG224 Gateways
In the past, using Cisco Unified CallManager Administration to provision analog phones one by one on the VG224 gateway proved very time consuming. Now, you can provision all parameters that can be provisioned from Cisco Unified CallManager Administration through the Bulk Administration Tool (BAT).
This section contains information for
•
•
•
•
•
•
Creating CSV Data Files for VG224 Gateways
Before you create a VG224 gateway template, you must create a CSV data file for the VG224 gateway.
These sections describe how to create the CSV data file.
•
•
•
Using the BAT Spreadsheet for CSV Data Files for VG224 FXS Gateways and Ports
Use the BAT spreadsheet to create the CSV data file that contains the details, such as domain name, MGCP description, and port identifier, for individual FXS ports.
To create a text-based CSV data file for VG224 gateways, see Creating a Text-Based CSV File for VG224 Gateways
For more information, see the Cisco Unified CallManager Bulk Administration Guide 5.0(4).
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
a.
b.
c.
d.
e.
f.
Step 9
•
The host name must match exactly the host name that is configured on the Cisco IOS gateway. For example, if the host name is configured on the gateway to resolve to vg224-1 and the IP domain name is not configured, enter the host name in this field (in this case, vg224-1). If the host name is configured on the gateway as vg224-1 and the IP domain name is configured on the gateway as cisco.com, enter vg224-1.cisco.com in this field.
•
•
•
Note
•
•
•
Step 10
The system saves the file to C:\XLsDataFiles (or to your choice of another existing folder) as VG224Gateways#timestamp.txt where "timestamp" represents the precise date and time that the file was created.
Tip
If you enter a blank row in the spreadsheet, the system treats the empty row as the end of the file. Data that is entered after a blank line does not get converted to the BAT format.You must upload the CSV data file to the first node of the Cisco Unified CallManager server, so BAT can access the data input file. For more information, see the "Uploading and Downloading Files" chapter in the Cisco Unified CallManager Bulk Administration Guide 5.0(4).
Note
Creating a Text-Based CSV File for VG224 Gateways
Instead of using the BAT spreadsheet for data input to add Cisco VG224 gateways, you can create the comma separated values (CSV) file by using lines of ASCII text with values that are separated by commas.
To create a CSV text file for VG224 gateways, use this procedure.
Procedure
Step 1
Step 2
The section FXS Trunks CSV File Format for VG224, provides descriptions and examples.
Note
FXS Trunks CSV File Format for VG224
The following sample format shows the required field length and string types followed by sample of CSV files for a VG224 gateway.
MGCP Domain Name(Mandatory, 1 to 64 characters),Description(Optional, up to 100 characters),Slot(Mandatory, up to 3 numerals), Subunit (Mandatory, up to 3 numerals), Port Number(Mandatory, up to 3 numerals), Port Description Optional, up to 50 characters),Port Directory Number(Optional, up to 24 numerals and special characters)
Sample
MGCPTest,VG224 Lab Gateway,2,0,0,Port 0,97255576601MGCPTest,VG224 Lab Gateway,2,0,1,Port 1,97255572001
Note
Example 1
If the Description for a VG224 gateway is blank, use this format:
MGCPTest, ,2,0,0,Port 0,97255576601
Guest
