Release Notes for Cisco Unified Communications Manager Business Edition Release 6.1(3b)
Available Languages
Table Of Contents
Release Notes for Cisco Unified Communications Manager Release 6.1(3b)
Windows 2000 Users Must Download Windows Installer 3.0 Updates
Upgrading to Cisco Unified Communications Manager 6.1(3x)
Special Upgrade Considerations
Upgrade Paths To Cisco Unified Communications Manager 6.1(3x)
Upgrading to Unified CM 6.1(3x) From Unified CM 4.x and 5.x
Upgrading From an Engineering Special
Adding or Updating SIP Dial Rules Causes Cisco TFTP Service To Rebuild All Phone Configuration Files
CSCsy25150 Unified CM Does Not Send Daylight Saving Time Updates
CSCsx94914 Disable NonRegistered SCCP KeepAlives Service Parameter Forced to False
Caveats Resolved in Unified CM Release 6.1(3x)
SDI Trace Delete from User Interface May Cause High IO
Alerts During Upgrades to Cisco Unified Communications Manager Business Edition 6.1(3x)
Cisco CallManager Service Stops After Upgrade to Cisco Unified Communications Manager 6.x
Important Information About Delete Transaction Using Custom File in BAT
Partition Size Limitations When You Upgrade From a 5.x Release to a 6.x Release
Clarification for Call Park Configuration
Viewing Privileges for Roles in Cisco Unified CM Administration
TAPS Name Change in Bulk Administration Tool
Basic Uninterruptible Power Supply (UPS) Integration
Serviceability Not Always Accessible from OS Administration
Voice Mailbox Mask Interacts with Diversion Header
CTL Client 5.0 Plug-In Installation Note
Best Practices for Assigning Roles to Serviceability Administrators
For Serviceability, the Administrator That Is Created During Installation Must Not Be Removed
Connecting to Third-Party Voice Messaging Systems
Database Replication When You Revert to an Older Product Release
User Account Control Pop-up Window Displays During Installation of RTMT
CiscoTSP Limitations on Windows Vista Platform
Time Required for Disk Mirroring
Cisco Unified Mobility Supports Nine Locales
Each Remote Destination Supports a Maximum of Two Active Calls
Changes to Cisco Extension Mobility After Upgrade
RTMT Requirement When Cisco Unified Communications Manager Is Upgraded
Serviceability Session Timeout Not Graceful
Serviceability Limitations When You Modify the IP Address
SIP Network/IP Address Field Required for SIP Fallback to SRST Gateway
Online Help Was Not Updated for Cisco Unified Communications Manager, Release 6.1(3x)
New and Changed Information in Cisco Unified Communications Manager 6.1(3x)
Installation, Upgrade, and Migration
Cisco Security Agent for Cisco Unified Communications Manager Log File
System History Log for Cisco Unified Communications Manager
Cisco Unified Communications Manager Administration
New and Updated Enterprise and System Parameters
Cisco Unified Communications Manager Features and Applications
Always Use Prime Line for Voice Message
Barge, cBarge, and Single Button Barge Support for PLAR
Cisco Unified Communications Manager Assistant
Cisco Web Dialer Configured in Application Server Window
Location-Based Call Admission Control Over Intercluster Trunk
Logging Missed Calls For Shared Lines
Multicast Music On Hold Over H.323/SIP Trunk
Transit Counter That is Implemented in Codeset5 for QSIG PRI Trunks
Unconfigured Device Registration Attempts Restricted
Viewing Held Calls on Shared Lines
Support for Party Entrance Tone
Support for Always Use Prime Line
Support for VG202 and VG204 Gateways
Cisco UXL Web Service Added to Service Activation Window
Cisco Unified Real-Time Monitoring Tool
System History Log Displays in RTMT
Cisco Unified Communications Manager CDR Analysis and Reporting
Configuring Department Bills Reports
SIP Call with URL as Extension Number Now Supported
CDR Search by User Extension Supports "+" and URLs for SIP Calls
Changes to Mail Server Configuration GUI
Change in Supported FTP/SFTP Versions for CAR Billing Servers
New Error Message That Is Introduced If Data Present in Invalid or Remainder Partitions
Configuring Individual and Department Bills Reports
Cisco Unified Communications Manager Call Detail Records
Updated Information on Global Call ID CDR Field
CallingPartyNumber CDR Field Not Affected by Direct Calls
Video Conference Call CDR Example
Skinny Client Control Protocol (SCCP)
Busy Lamp Field (BLF) Enhancements
Cisco Unified IP Phone Expansion Modules 7915 and 7916
Cisco Unified IP Phone Support HTTPS
Personal Directory and Fast Dial Service
Restrict Unconfigured Phone Registration
Cisco Unified Communications Manager Administration Guide
Route Plan Report Description Omits Mention of Mobile Voice Access Numbers
End User Chapter Includes Incorrect Information for Manager User ID Field
.Device Pool Chapter Contains Incomplete Description for Device Pool Name Field
Credential Policy Configuration Settings Display Description is Incorrect
Incorrect Information Exists in the Meet-Me Number/Pattern Configuration
Considerations for LDAP Port Configuration
Incorrect Description for User ID Field in Application User Window
Logging In To the Web Interface When the Firewall Is Disabled
Unclear Documentation on Called Party Name Presentation
Misleading Documentation About Creating Cisco Unity and Cisco Unity Connection Voice Mailboxes
Adding an Administrator User to Cisco Unity or Cisco Unity Connection
Documentation Does Not Include the Latest List of Supported Phone Models
Upgrade Procedure Contains Incorrect Information
Application Server Configuration Not Required for Cisco Unity Connection 2.x
Incorrect Documentation on How to Delete Parameter for Phone Service
Default Device Profile Chapter Incorrectly Includes Expansion Module Settings
Hunt Pilot Chapter Needs Clarification of Maximum Hunt Timer Setting
Annunciator Chapter Contains Incorrect Information on Description Field
Gateway Configuration Chapter Contains Incorrect Information on Domain Name Field
AAR Group Chapter Includes Incorrect Description for Dial Prefix Field
Generating a License File from DMA
Enterprise Parameters and Service Parameters Chapters Omit Information on Set to Default Button
Information About Using an SRV Destination Port for the CUP Publish Trunk Service Parameter
Information About Changing Region Bandwidth Settings When Video Calls Are Made
Information Omitted for Reroute Incoming Request to New Trunk Based on Setting
Do Not Begin Starting and Ending Directory Numbers with a Zero (0)
Time-of-Day Routing Chapter Omits Information About Defined Time Periods
Cisco Unified Communications Manager System Guide
RSVP Reservation Teardown for Shared-Line Calls
Considerations for LDAP Port Configuration
RSVP Reservation Teardown for Shared-Line Calls
Application Server Configuration Not Required for Cisco Unity Connection 2.x
Unclear Documentation on Called Party Name Presentation
Automated Alternate Routing (AAR) Limitation with Remote Gateways
Documentation Does Not State That Line Group With No Members Is Not Supported for Routing Calls
Peer-to-Peer Image Distribution
Recommended Number of Devices in Device Pool
Call Admission Control Bandwidth Example Correction
Directory Numbers Chapter Includes Incorrect Example for Shared Lines and Call Forward Busy Trigger
Licensing Chapter Omits Information on Adjunct Licensing
Cisco TFTP Chapter Omits Configuration Tip on Centralized TFTP
Information About Changing Region Bandwidth Settings When Video Calls Are Made
Trunk Chapter Omits Restrictions for H.323/H.225 Trunks
Information About Changing Region Bandwidth Settings When Video Calls Are Made
Cisco Unified Communications Manager Features and Services Guide
CTI and Attendant Console Chapters Omit Information on CTI Monitored Lines
Incorrect Information on How to Install Assistant Console Application
Do Not Disturb Feature Priority
Extension Mobility Successful Authentication Cache
Devices Associated with the Attendant Console Application User
CTI Devices Do Not Support Multicast Music on Hold (MOH)
Attendant Console Phones Do Not Support the Intercom Feature
Unclear Documentation on How Locales Work for Mobile Voice Access
cBarge Chapter Omits Information on Shared Line Restriction for Conferences
Cisco Unified IP Phones Supporting Call Back with PLKs
Number of Login or Logout Operations That Cisco Extension Mobility Supports
None Option Not Documented for DND Incoming Call Alert Setting
Cisco Extension Mobility Chapter Error
Barge with Shared Conference Bridge
Number of Alphanumeric Characters That Are Allowed in the Pickup Group Name Field
Documentation Does Not Include the Latest List of Supported Phone Models
Do Not Disturb Documentation Provides Incorrect Information About Phone Tone
Destination Number in Remote Destination Configuration Window
Cisco Extension Mobility Supplemental Information
Cisco Unified IP Phones Supporting Barge
Cisco Unified IP Phones Supporting Call Back
Cisco Unified Communications Manager Security Guide
Support for Certificates from External CAs
CAPF System Interactions and Requirements
Software Conference Bridge Not Supported
Cisco Unified Communications Manager XML Developers Guide for Release 6.0(1)
Cisco Unified Serviceability Administration Guide
DNS Required for RTMT Alerts by E-mail
Warning Displays When SIP Stack Trace Is Enabled
SNMP Traps and Informs Correction
Cisco Unified Communications Manager Assistant User Guide
Online Help Notes for Hebrew and Arabic
Cisco Unified Communications Manager Assistant
Creating Filter Lists for a Manager
Cisco Unified IP Phone Documentation
Cisco Unified IP Phone User Guide (7906, 7911, 7931, 7945, 7965, 7975)
Cisco Unified IP Phone Administration Guides (7905G, 7912G, 7921G)
Cisco Unified Wireless IP Phone Guide 7920 for Cisco Unified CallManager 5.0 (SCCP)
Cisco Unified Wireless IP Phone Guide (7975, 7971, 7965, 7945, 7962, 7942, 7941, 7931, 7911, 7906)
Cisco Unified CallManager Bulk Administration Guide
Description for Phone Personalization Is Incorrect in Documentation
Incorrect Path Is Documented for Add File Format Window
Primary User Device Field on the Update Users Window in BAT
Single Button Barge (new field)—Phone Template Configuration Window in BAT
Join Across Lines (new field)—Phone Template Configuration Window in BAT
Single Button Barge (new field)—UDP Template configuration Window in BAT
Join Across Lines (new field)—UDP Template configuration Window in BAT
Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide
RTMT Trace and Log Central Disk IO and CPU Throttling
Path for Accessing Cisco Unified Reporting
Perfmon Log File—Maximum File Size Default Value
Path for Accessing Cisco Unified Reporting
DNS Required for RTMT Alerts by E-mail
Minimum Memory Requirement for RTMT Client
Cisco Unified Communications Operating System Administration Guide
Install New COP Files Before You Upgrade Cisco Unified Communications Manager
Digital Certificate Key Length Restrictions
set network dhcp eth0 disable Command Parameters
Remote Support Account Duration
System Generates a DBReplicationFailure Alert
Information On ARP Cache Limits Omitted from Operating System Administration Guide
Third-Party Certificate Authority Verification
Recovering Administrator and Security Passwords
Software Feature License Information Omitted from Operating System Administration Guide
Characters Allowed in a Pre-Shared Key
Troubleshooting Guide for Cisco Unified Communications Manager
Automated Alternate Routing (AAR) Limitation with Remote Gateways
Cisco Unified Mobility User Hangs Up Mobile Phone But Cannot Resume Call on Desktop Phone
Cisco Unified Communications Manager 6.1 TCP and UDP Port Usage
Disaster Recovery System Administration Guide
Upgrading to Cisco Unified Communications Manager from 4.x Releases Guide
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Unified Communications Manager Release 6.1(3b)
Updated December 22, 2009
CautionBe aware that you can not upgrade directly from Unified CM 6.1(3x) to Unified CM 7.0
See: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html
This document contains information pertinent to Cisco Unified Communications Manager Release 6.1(3x).
Before you install Cisco Unified Communications Manager, Cisco recommends that you review the "Upgrading to Cisco Unified Communications Manager 6.1(3x)" section for information about upgrading and the "Important Notes" section for information about issues that may affect your system.
To view the release notes for previous versions of Cisco Unified Communications Manager, choose the Cisco Unified Communications Manager version from the following URL: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_release_notes_list.html
Note
Contents
These release notes discuss the following topics:
•
–
•
–
•
Introduction
Cisco Unified Communications Manager, the call-processing component of the Cisco Unified Communications System, extends enterprise telephony features and capabilities to IP phones, media processing devices, voice-over-IP (VoIP) gateways, mobile devices, and multimedia applications.
System Requirements
Server Support
Make sure that you install and configure Cisco Unified CM Release 6.1(3b) on a Cisco Media Convergence Server (MCS) or a Cisco-approved HP server configuration or a Cisco-approved IBM server configuration.
To find which MCS are compatible with Cisco Unified CM Release 6.1(3b), refer to the Supported Servers for Cisco Unified Communications Manager Releases, go here.
Note
Note
Uninterruptible Power Supply
Ensure that you connect each Cisco Unified Communications Manager node to an uninterruptible power supply (UPS) to provide backup power and protect your system.
Caution
Installation Notes
The following sections comprise installation notes for Unified CM 6.1(3x).
•
Windows 2000 Users Must Download Windows Installer 3.0 Updates
If you are running Windows 2000 on your workstation or server, you must download Windows Installer 3.0 updates to correctly install CTL Client plug-ins. You can obtain Windows Installer 3.0 at the following URL:
Note
Procedure
Step 1
Step 2
Step 3
Step 4
Do Not Install Unified CM in a Large Class A or Class B Subnet That Contains a Large Number of Devices
Do not install Cisco Unified Communications Manager in a large Class A or Class B subnet that contains a large number of devices. When you install Cisco Unified Communications Manager in a large subnet with a large number devices in that subnet, the Address Resolution Protocol (ARP) table can fill up quickly (maximum 1024 entries, by default).
When the ARP table gets full, Cisco Unified Communications Manager experiences difficulty communicating with endpoints and cannot add more phones.
Upgrading to Cisco Unified Communications Manager 6.1(3x)
The following sections contain information pertinent to upgrading to this release of Unified CM.
•
•
•
•
Before You Begin
Before you upgrade the software version of Cisco Unified Communications Manager, verify your current software version.
To do that, open Cisco Unified Communications Manager Administration. The following information displays:
•
•
Special Upgrade Considerations
Cisco only supports replacing failed hard drives. Cisco does not support drive pulling/swapping as a method of fast upgrade reversion, restore, or server recovery.
Upgrade Paths To Cisco Unified Communications Manager 6.1(3x)
For information about supported Cisco Unified CM upgrades, see the Cisco Unified Communications Manager Compatibility Matrix at the following URL:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html.
Caution
Upgrading to Unified CM 6.1(3x) From Unified CM 4.x and 5.x
If you are upgrading from 4.1.3, 4.2.3, 4.3(2), 5.1.2, or 5.1.3, use the Product Upgrade Tool (PUT) or the PUT for registered customers only to obtain a media kit and license or purchase the upgrade from Cisco Sales.
To use the PUT, you must enter your Cisco contract number (Smartnet, SASU, or ESW) and request the CD/CD set. If you do not have a contract for Cisco Unified Communications Manager, you must purchase the upgrade from Cisco Sales.
Upgrading From an Engineering Special
If you want to upgrade to Cisco Unified CM 6.1(3b) and you are currently running an Engineering Special (ES), contact TAC to obtain the fixes that are included in the ES that you currently use.
Upgrading From Cisco Unified Communications Manager Release 6.1(1x) or higher to Release 6.1(3b) by Using the UCSInstall File
Because of its size, the UCSInstall iso file, UCOS_6.1.3.3000-1.sgn.iso, comprises two parts:
•
•
Procedure
Step 1
Step 2
Note
a.
cat UCSInstall_UCOS_6.1.3.2000-1.sgn.iso_part1of2 UCSInstall_UCOS_6.1.3.2000-1.sgn.iso_part2of2 > UCSInstall_UCOS_6.1.3.2000-1.sgn.iso
b.
COPY /B UCSInstall_UCOS_6.1.3.3000-1.sgn.iso_part1of2+UCSInstall_UCOS_6.1.3.3000-1.sgn.iso_part2of2 UCSInstall_UCOS_6.1.3.3000-1.sgn.iso
Step 3
0e2994c852d931cd09a334cae69dc2c6 UCSInstall_UCOS_6.1.3.3000-1.sgn.iso
Related Documentation
The documentation that supports Cisco Unified Communications Manager Release 6.1 resides at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.htmlLimitations and Restrictions
A recommendation of compatible software releases that have been verified by the test for customers represents a major deliverable of the 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 that were tested for interoperability with Cisco Unified Communications Manager 6.1 as part of Unified Communications System Release 6.1 testing, see http://www.cisco.com/go/unified-techinfo.
For a list of software and firmware versions of contact center components that were tested for interoperability with Cisco Unified Communications Manager 6.1 as part of Unified Communications System Release 6.1 testing, see http://tools.cisco.com/ITDIT/vtgsca/.
Be aware that the release of Cisco IP telephony products does not always coincide with Cisco Unified Communications Manager releases. If a product does not meet the compatibility testing requirements with Cisco Unified Communications Manager, you need to wait until a compatible version of the product becomes available before you can upgrade to Cisco Unified Communications Manager 6.1(3x). For the most current compatibility combinations and defects that are associated with other Cisco Unified Communications products, refer to the documentation that is associated with those products.
Software Download URLs
You can access the latest software upgrades for Cisco Unified Communications Manager at http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875240
Important Notes
The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco Unified Communications Manager Release 6.1(3x).
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Adding or Updating SIP Dial Rules Causes Cisco TFTP Service To Rebuild All Phone Configuration Files
When you add or update a SIP dial rule in Cisco Unified Communications Manager Administration, be aware that the Cisco TFTP service rebuilds all phone configuration files, which may cause CPU to spike on the server where the Cisco TFTP service runs, especially if you have a large system with many phones. To ensure that CPU does not spike, add or update the SIP dial rule during a maintenance window or temporarily stop the Cisco TFTP service in Cisco Unified Serviceability before you make the configuration change. If you stop the Cisco TFTP service, remember to restart the service in Cisco Unified Serviceability after you add or update the SIP dial rule.
CSCsy25150 Unified CM Does Not Send Daylight Saving Time Updates
Earlier releases of Unified CM 6.1(3) did not send Daylight Savings Time updates to Cisco IP Phones.
For important information about this issue, see the Field Notice at: http://www.cisco.com/en/US/customer/ts/fn/632/fn63213.html
CSCsx94914 Disable NonRegistered SCCP KeepAlives Service Parameter Forced to False
On systems that were upgraded to an Engineering Special (ES) or Unified CM release that resolves CSCsa67496, when TCP sessions to TCP port 2000 get initiated and then abandoned, the sessions remain in the established state on the server because ccm.exe never closes the session. This causes a TCP connection leak and a memory leak, which results in low virtual memory.
In Cisco Unified Communications Manager Release 6.1(3b), the Disable NonRegistered SCCP KeepAlives service parameter gets forced to False so the leaks do not occur.
Caveats Resolved in Unified CM Release 6.1(3x)
The following information comprises unexpected behavior that is addressed by this release of Cisco Unified Communications Manager.
------------------------------------------------------------------------------
Identifier: CSCsw93549
Component : phones
Headline : Error in IP phone rules file causes sidecar not to register to Unified CM.
------------------------------------------------------------------------------
Identifier: CSCsx35470
Component : call processing
Headline : SDL version change for Unified CM 613a.
------------------------------------------------------------------------------
Identifier: CSCsx16330
Component : cli
Headline : Nodatasync option on switchversion causes permanent data loss.
------------------------------------------------------------------------------
Identifier: CSCsw97038
Component : sip trunk
Headline : Unified CM sends incorrect codec in SDP of ACK for outgoing mobility call.
-----------------------------------------------------------------------------
Identifier: CSCsw76629
Component : mobility
Headline : Third-party SIP endpoint fails to register with digest authentication enabled.
-----------------------------------------------------------------------------
SDI Trace Delete from User Interface May Cause High IO
This caveat is resolved in Unified CM 6.1(2), but not in 6.1(3x).
In Unified CM 6.1(3x), when you change the number of SDI trace files, all existing trace files get deleted. If the number of trace files is extremely large, this can cause high IOWait problems and phones may unregister.
Workaround
Manually delete the excessive trace files during off hours.
Use the CLI to delete the files first and then use the Trace Configuration window to update the maximum number of files or the maximum file size settings.
Cisco recommends that you delete the files in batches of 500 files, or fewer, at a time.
Example
Since CLI support "wild card" characters, to delete trace files from ccm00000600.txt to ccm00000699.txt use following CLI:
file delete activelog cm/trace/ccm/sdi/ccm000006*.* noconfirm
The CLI command does not delete files that are currently open, so there will not be any interruption to the current ccm trace log.
Ensure that files that you intend to delete are of no value; otherwise, download them before deleting them.
Alerts During Upgrades to Cisco Unified Communications Manager Business Edition 6.1(3x)
During an upgrade to Cisco Unified Communications Manager Business Edition, users may experience following alerts in the Cisco Unified Real-Time Monitoring Tool. Users may disregard these alerts during the upgrade process:
•
•
•
•
•
Cisco Unified JTAPI
In Cisco Unified Communications Manager Releases 6.x and 5.x, if an application tries to conference two or more addresses on the same terminal, based on the order of participants in the request, an application may receive CiscoJtapiException.CONFERENCE_INVALID_PARTICIPANT for the conference request. The conference might then start successfully with some of the participants. In such cases, no guarantees exist which application joins the conference. The system creates the conference with only one of the addresses on a terminal. It ignores the other addresses.
This situation occurs in the following scenarios.
Scenario 1
Assume that B1 and B2 represent different addresses on the same terminal, TB.
A -> B1 - GC1
A -> B2 - GC2
A -> C - GC3
Assume that an application issues a conference request GC1.conference(GC2,GC3).
In Cisco Unified Communications Manager Releases 6.x and 5.x, the application receives CiscoJtapiException.CONFERENCE_INVALID_PARTICIPANT; however, A, B1, and C join into conference, and the following normal set of events in a conference scenario occur:
GC1 CiscoConferenceStartEvGC2 TermConnDroppedEv TBGC2 CallCtlTermConnDroppedEv TBGC2 ConnDisconnectedEv B1GC2 CallCtlConnDisconnectedEv B1GC1 CallCtlTermConnTalkingEv TBGC2 CiscoCallChangedEvGC1 ConnCreatedEv CGC1 ConnConnectedEv CGC1 CallCtlConnEstablishedEv CGC1 TermConnCreatedEv TCGC1 TermConnActiveEv TCGC1 CallCtlTermConnTalkingEv TCGC2 TermConnDroppedEv TCGC2 CallCtlTermConnDroppedEv TCGC2 ConnDisconnectedEv CGC2 CallCtlConnDisconnectedEv CGC2 CallInvalidEvGC1 CiscoConferenceEndEvScenario 2
Assume that B1 and B2 represent different addresses on the same terminal, TB.
A -> B1 - GC1
A -> B2 - GC2
A -> C - GC3
Assume that an application issues a conference request GC3.conference(GC1,GC2).
In Cisco Unified Communications Manager Releases 5.x, the application does not receive an exception, and the request processes successfully. A, C, and B1 join the conference with the regular set of conference events.
In Cisco Unified Communications Manager releases 5.x 6.x, the application receives CiscoJtapiException.CONFERENCE_INVALID_PARTICIPANT; however, A, C, B1 join conference, and the normal set of conference events occurs.
SFTP Server Products
Cisco allows you to use any SFTP server product with applications that require SFTP access but recommends SFTP products that have been certified with Cisco through the Cisco Technology Developer Partner program (CTDP). CTDP partners, such as GlobalSCAPE, certify their products with specified version of Cisco Unified Communications Manager. For information on which vendors have certified their products with your version of Cisco Unified Communications Manager, refer to http://www.cisco.com/pcgi-bin/ctdp/Search.pl. For information on using GlobalSCAPE with supported Cisco Unified Communications versions, refer to http://www.globalscape.com/gsftps/cisco.aspx.Cisco uses the following servers for internal testing. You may use one of the servers, but you must contact the vendor for support:
•
•
•
Note
Cisco CallManager Service Stops After Upgrade to Cisco Unified Communications Manager 6.x
After you upgrade to Cisco Unified Communications Manager 6.X from a compatible Cisco Unified CM 5.X release, the Cisco CallManager service does not automatically run, even though Cisco Unified Serviceability shows that the Cisco CallManager service is activated.
Immediately after you complete the upgrade, upload the software feature license that is required for Cisco Unified Communications Manager 6.X in Cisco Unified Communications Manager Administration and restart the Cisco CallManager service in Cisco Unified Serviceability. Until you perform these tasks, devices fail to register with Cisco Unified Communications Manager.
For more information on licensing, refer to the licensing chapters in the Cisco Unified Communications Manager Administration Guide and the Cisco Unified Communications Manager System Guide.
Important Information About Delete Transaction Using Custom File in BAT
Do not use the insert or export transaction files that are created with bat.xlt for the delete transaction. Instead, you must create a custom file with the details of the records that need to be deleted. Use only this file for the delete transaction. In this custom delete file, you do not need a header, and you can enter values for name, description, or user.
Partition Size Limitations When You Upgrade From a 5.x Release to a 6.x Release
Cisco Unified Communications Manager 5.x releases create disk partitions of a fixed size. If you install a 5.x release on a server with more disk space than required by the fixed partitions, the partitions still get created at the fixed size.
When you upgrade such a server from a 5.x release to a 6.x release, the disk partitions remain at the fixed size. If you perform a fresh installation of a 6.x release, the disk partitions get created as percentages of the available disk space, so your server will use all the available disk space effectively.
Cisco Unified Communications Manager Does Not Support Recovery of Administration or Security Passwords
Cisco Unified Communications Manager does not support recovery of administration or security passwords. If you lose these passwords, you must reset the passwords, as described in the Cisco Unified Communications Operating System Administration Guide.
The Cisco Unified Communications Operating System Administration Guide calls the section "Recovering the Administrator or Security Passwords" instead of "Resetting the Administrator or Security Passwords." Access the "Recovering the Administrator or Security Passwords" section to reset the passwords.
Clarification for Call Park Configuration
Consider the following information when you configure Call Park:
Call Park numbers cannot overlap between Cisco Unified CM servers. Ensure that each Cisco Unified CM server has its own unique number range.
Call Park numbers may have an associated partition that restricts access to the Call Park numbers and prevents retrieval of parked calls. If partitions are used to restrict access to Call Park numbers, you must define a unique call park number or range of call park extension numbers for each partition in Cisco Unified Communications Manager Administration.
When the end user invokes Call Park, Cisco Unified Communications Manager attempts to find an available Call Park number from a Call Park partition that is currently accessible via the calling search space for the party that invoked Call Park.
Viewing Privileges for Roles in Cisco Unified CM Administration
The Role Configuration window in Cisco Unified CM Administration displays the privileges for each standard role. To access the Role Configuration window, find the role by choosing User Management > Role; when the Find and List Roles window displays, click Find. Click the link for the standard role that you want to view. After the Role Configuration window displays, you can view the privileges in the Resource Access Information pane.
TAPS Name Change in Bulk Administration Tool
Documentation refers to the Tool for Auto-Registered Phone Support (TAPS) as Cisco Unified Communications Manager Auto-Register Phone Tool in the Online Help for Bulk Administration. All references to 'Cisco Unified Communications Manager Auto-Register Phone Tool' in the Bulk Administration Tool Online Help should be read as 'Tool for Auto-Registered Phone Support (TAPS)'. This makes the terminology compliant with the Bulk Administration user interface.
For More Information
For information on configuring additional features in BAT, refer to the BAT documentation for Cisco Unified CM.
Basic Uninterruptible Power Supply (UPS) Integration
When Cisco Unified Communications Manager 6.0(1a) runs on an MCS 7825H2 or MCS 7835H2, basic integration to the UPS model APC SmartUPS 1500VA USB and APC 750VA XL USB gets supported. Integration occurs via a single point-to-point Universal Serial Bus (USB) connection. Serial and SNMP connectivity to UPS does not get supported, and the USB connection must be point-to-point (in other words, no USB hubs). Single- and dual-USB UPS models get supported. The feature activates automatically during bootup if a connected UPS gets detected.
Alternatively, on MCS-7835H2, you can execute the show ups CLI command that shows the current status of the USB-connected APC smart-UPS device and starts the monitoring service if it is not already started.
On supported servers, the CLI command also displays detected hardware, detected versions, current power draw, remaining battery runtime, and other relevant status information.
When the feature is activated, graceful shutdown will commence as soon as the low battery threshold is reached. Resumption or fluctuation of power will not interrupt or abort the shutdown.
For unsupported Cisco Unified Communications Manager releases, MCS models and/or UPS vendor/make/models, you can cause an external script to monitor the UPS. When low battery gets detected, you can log on to Cisco Unified Communications Manager by using Secure Shell (SSH), access the CLI, and execute the utils system shutdown command.
Strict Version Checking
Disaster Recovery System adheres to strict version checking and allows restore only between matching versions of Cisco Unified Communications Manager.
Note
Consider the following examples of restore to understand strict version checking:
In essence, the product version needs to match, end-to-end, for the Disaster Recovery System to run a successful Cisco Unified Communications Manager database restore.
Serviceability Not Always Accessible from OS Administration
In some scenarios, you cannot access Cisco Unified Serviceability from Cisco Unified OS Administration. The window displays a "Loading, please wait" message indefinitely.
If the redirect fails, log out from Cisco Unified OS Administration, select Cisco Unified Serviceability from the navigation menu, and log in to Cisco Unified Serviceability.
Voice Mailbox Mask Interacts with Diversion Header
When a call gets redirected from a DN to a voice-messaging server/service that is integrated with Unified CM by using a SIP trunk, the voice mailbox mask on the voice-mail profile for the phone modifies the diverting number in the SIP diversion header. Be aware that this behavior is expected because the Unified CM server uses the diversion header to choose a mailbox.
CTL Client 5.0 Plug-In Installation Note
If you are upgrading to the CTL Client 5.0 plug-in, you first need to remove eToken Run Time Environment 3.00 by performing the following steps:
Procedure
Step 1
http://support.microsoft.com/kb/290301Step 2
Step 3
Step 4
Step 5
Best Practices for Assigning Roles to Serviceability Administrators
Cisco recommends that you configure application users, rather than end users, to access remote nodes to perform such tasks as starting and stopping services. Starting and stopping services requires that the Standard Serviceability Administration and Standard RealtimeAndTraceCollection roles be assigned.
For Serviceability, the Administrator That Is Created During Installation Must Not Be Removed
Removing the Administrator that is created during installation or upgrade can cause communication with remote nodes via Serviceability Administration to fail.
Connecting to Third-Party Voice Messaging Systems
Administrators can connect third-party voice-messaging systems to Cisco Unified Communications Manager. Ensure the voice-messaging system has a simplified message desk interface (SMDI) that is accessible with a null-modem EIA/TIA-232 cable (and an available serial port). To connect the EIA/TIA-232 cable to Cisco Unified Communications Manager Release 5.0 or later, use a Cisco certified serial-to-USB adapter with the part number USB-SERIAL-CA=.
Database Replication When You Revert to an Older Product Release
If you revert the servers in a cluster to run an older product release, you must manually reset database replication within the cluster. To reset database replication after you revert all the cluster servers to the older product release, enter the CLI command utils dbreplication reset all on the publisher server.
When you switch versions by using Cisco Unified Communications Operating System Administration or the CLI, you get a message that reminds you about the requirement to reset database replication if you are reverting to an older product release. The caveats CSCsl57629 and CSCsl57655 also document this behavior.
For information about the utils dbreplication clusterreset, utils dbreplication dropadmindb, and utils dbreplication forcedatasyncsub commands, see the Command Line Interface Reference Guide for Cisco Unified Communications Solutions Release 7.0(1) document at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/cli_ref/7_0_1/cli_ref.html.
User Account Control Pop-up Window Displays During Installation of RTMT
When you install RTMT on the Microsoft Vista platform, the system displays the User Account Control pop-up window to indicate that an unidentified program wants access to your computer. This occurs because of a limitation in the InstallAnywhere software. This one-time pop-up displays only when you are installing RTMT. To continue, select Allow.
CiscoTSP Limitations on Windows Vista Platform
Always perform the first-time installation of the CiscoTSP and Cisco Unified Communications Manager TSP Wave Driver on a Vista machine as a fresh install.
If secure connection to Cisco Unified Communications Manager is to be used, turn off the Windows firewall.
If Cisco Unified Communications Manager TSP Wave Driver is used for inbound audio streaming, turn off the Windows firewall.
If Cisco Unified Communications Manager TSP Wave Driver is used for audio streaming, disable all other devices in the "Sound, video and game controllers" group.
Time Required for Disk Mirroring
Disk mirroring on server model 7825 I3 with 160 GB SATA disk drives takes approximately 3 hours.
Disk mirroring on server model 7828 I3 with 250 GB SATA disk drives takes approximately 4 hours.
Cisco Unified Mobility Supports Nine Locales
Cisco Unified Mobility (Mobile Connect and Mobile Voice Access) support a maximum of nine locales, so Cisco Unified Communications Manager Administration blocks you from configuring 10 or more locales for Cisco Unified Mobility. In the Mobility Configuration window, more than nine locales can display in the Available Locales pane if they are installed for Cisco Unified Communications Manager, but you can only save nine locales in the Selected Locales pane. If you attempt to configure more than nine locales for Cisco Unified Mobility, the following message displays: "Update failed. Check constraint (informix.cc_ivruserlocale_orderindex) failed."
Each Remote Destination Supports a Maximum of Two Active Calls
For Cisco Unified Mobility, each remote destination supports a maximum of two active calls via Cisco Unified Communications Manager. Using the enterprise feature access directory number (DID number) to transfer or conference with DTMF counts as one call. When a Cisco Unified Mobility user receives a call while the user has two active calls for the remote destination or while the user is using DTMF to transfer/conference a call from the remote destination, the received call does not reach the remote destination and instead goes to the enterprise voice mail; that is, if Call Forward No Answer (CFNA) is configured or if the call is not answered on a shared line.
Changes to Cisco Extension Mobility After Upgrade
If you chose a user-created profile from the Log Out Profile drop-down list on the Phone Configuration window and checked the Enable Extension Mobility check box, the settings in that profile become the permanent settings on the phone after an upgrade from Cisco Unified CallManager 4.x or Cisco Unified Communications Manager 5.x to Cisco Unified Communications Manager 6.1(1a).
RTMT Requirement When Cisco Unified Communications Manager Is Upgraded
If you are running the Cisco Unified Communications Real-Time Monitoring Tool (RTMT) client and monitoring performance counters during a Cisco Unified Communications Manager upgrade, the performance counters will not update during and after the upgrade. To continue monitoring performance counters accurately after the upgrade completes, you must either reload the RTMT profile or restart the RTMT client.
Serviceability Session Timeout Not Graceful
When a session has been idle for more than 30 minutes, the Cisco Unified Serviceability user interface allows you to make changes before it indicates that the session timed out and redirects you to the login window. After you log in again, you may need to repeat those changes. This behavior occurs in the Alarm, Trace, Service Activation, Control Center, and SNMP windows.
Workaround
If you know that the session has been idle for more than 30 minutes, log out by using the Logout button before making any changes in the user interface.
Problem Configuring Mobility Identity for Nokia S60 Device in Cisco Unified Communications Manager Administration
The following message may display in the Phone Configuration window in Cisco Unified Communications Manager Administration when you try to configure Mobility Identity for the Nokia S60 device: "Add failed. [10102] Check the type of device specified in fkDevice_DualMode. Remote Destionations other than Dual Mode must use fkDevice_RemoteDestinationTemplate."
The error occurs under one of the following circumstances:
•
•
If the message displays, you can perform the following tasks to ensure that you can configure Mobility Identity for the Nokia S60 device:
1.
2.
Tip
3.
Tip
4.
Serviceability Limitations When You Modify the IP Address
When you modify the IP Address field, you cannot access the RTMT profiles, custom counters, custom alerts, and generic queries for Trace & Log Collection Tool (TLC) for that server.
You should manually remove any RTMT profiles, custom counters, custom alerts, and generic queries for Trace and Log Collection Tool (TLC) that were set for the old IP Address. When you modify the IP Address field, you will need to re-create the RTMT profile, custom counters, custom alerts, and generic queries for TLC the next time that you log in to the server on RTMT.
Cisco AMC Service service includes two user-configurable service parameters, Primary Collector and Failover Collector. These service parameters use Host Name/IP Address to designate the primary and failover AMC server. If you change the IP address of the AMC primary collector or failover collector, you should check these service parameters and update them accordingly.
Cisco Serviceability Reporter service includes one user-configurable service parameter, RTMT Reporter Designated Node. This service parameter uses Host Name/IP Address to designate the node on which RTMTReporter runs. If you changed the IP address of the RTMT Reporter Designated Node, you should check this service parameter and update it accordingly.
SIP Network/IP Address Field Required for SIP Fallback to SRST Gateway
Although Cisco Unified Communications Manager Administration does not list the SIP Network/IP Address field as a required setting, you must configure the SIP Network/IP Address field and the SIP Port field in the SRST Reference Configuration window for a SIP device to fall back to the SRST-enabled gateway. For more information on these fields and SRST references, refer to the Cisco Unified Communications Manager Administration Guide.
Online Help Was Not Updated for Cisco Unified Communications Manager, Release 6.1(3x)
When you view online help in Cisco Unified Communications Manager 6.1(3x), be aware that the online help did not get updated for 6.1(3x). The following graphical user interfaces (GUIs) contain online help:
•
•
•
•
•
•
For information on features that were introduced in Cisco Unified Communications Manager Business Edition 6.1(2), refer to the Release Notes for Cisco Unified Communications Manager Business Edition, Release 6.1(2). For a list of documents that were updated for Cisco Unified Communications Manager Business Edition 6.1(2), refer to the Cisco Unified Communications Manager Business Edition Documentation Guide for Release 6.1(2).
New and Changed Information in Cisco Unified Communications Manager 6.1(3x)
The following section describes new features and changes that are pertinent to Cisco Unified Communications Manager, Release 6.1(3x) or later. The sections may include configuration tips for the administrator, information about users, and information about where to find more information.
•
•
•
•
•
•
Installation, Upgrade, and Migration
The following sections describe the changes for installation, upgrade, and migration in Cisco Unified Communications Manager 6.1(3x):
•
•
Cisco Security Agent for Cisco Unified Communications Manager Log File
The CLI command that accesses the Cisco Security Agent file log changed to utils create report csa.
System History Log for Cisco Unified Communications Manager
This system history log provides a central location for getting a quick overview of the initial system install, system upgrades, Cisco option installations, DRS backups and DRS restores, as well as switch version and reboot history.
Description
This section provides a description of the system history log feature.
Overview
The system history log exists as a simple ASCII file, system-history.log, and the data does not get maintained in the database. Because it does not get excessively large, the system history file does not get rotated.
The system history log provides the following functions:
•
•
•
•
•
•
•
•
System History Log Fields
Each system history log entry contains the following fields:
•
The log also displays a common header which contains information about product name, product version and kernel image.
=======================================
Product Name - Cisco Unified Communications Manager
Product Version - 7.1.0.39000-9023
Kernel Image - 2.6.9-67.EL
=======================================
The system history log fields can contain the following values:
•
•
•
–
–
–
–
–
–
–
–
–
–
–
•
–
–
–
–
–
•
–
–
–
Example
Example 1 shows a sample of the system history log.
Example 1 System History Log
admin:file dump install system-history.log=======================================Product Name - Cisco Unified Communications ManagerProduct Version - 6.1.2.9901-117Kernel Image - 2.4.21-47.EL.cs.3BOOT=======================================07/25/2008 14:20:06 | root: Install 6.1.2.9901-117 Start07/25/2008 14:50:38 | root: Boot 6.1.2.9901-117 Start07/25/2008 15:05:37 | root: Install 6.1.2.9901-117 Success07/25/2008 15:05:38 | root: Boot 6.1.2.9901-117 Start07/30/2008 10:08:56 | root: Upgrade 6.1.2.9901-126 Start07/30/2008 10:46:31 | root: Upgrade 6.1.2.9901-126 Success07/30/2008 10:46:43 | root: Switch Version 6.1.2.9901-117 to 6.1.2.9901-126 Start07/30/2008 10:48:39 | root: Switch Version 6.1.2.9901-117 to 6.1.2.9901-126 Success07/30/2008 10:48:39 | root: Restart 6.1.2.9901-126 Start07/30/2008 10:51:27 | root: Boot 6.1.2.9901-126 Start08/01/2008 16:29:31 | root: Restart 6.1.2.9901-126 Start08/01/2008 16:32:31 | root: Boot 6.1.2.9901-126 StartCLI Considerations
You can access the system history log by using the CLI file command; for example:
•
•
Cisco Unified Communications Manager Administration Configuration Tips
No Cisco Unified Communications Manager Administration configuration tips exist for this feature.
GUI Changes
No GUI changes exist for this feature.
Service Parameter and Enterprise Parameter Changes
No service parameter and enterprise parameter changes exist for this feature.
Installation/Upgrade (Migration) Considerations
No installation or upgrade consideration exist for this feature.
Serviceability Considerations
To access the system history log in RTMT, navigate to RTMT Trace Collection:
RTMT > Trace Log Collection
BAT Considerations
No BAT considerations exist for this feature.
CAR/CDR Considerations
No CAR/CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL and CTI considerations exist for this feature.
User Tips
No user tips exist for this feature.
For More Information
For more information about using the CLI, see the Cisco Unified Communications Operating System Administration Guide or the Command Line Interface Reference Guide for Cisco Unified Solutions.
For more information about RTMT, see the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide.
Command Line Interface
This section contains information about the Command Line Interface (CLI).
Spaces in File Names
For Cisco Unified Communications Manager Release 6.1(3x), you can use CLI commands to directly work with file names that contain spaces. For example, you could use the file delete command to delete a log file with the name cisco test log in the Platform directory:
file delete activelog platform cisco test log
Relative Paths
When you download a file to your local computer with the file get command, the system prompts you to enter a download directory. For Cisco Unified Communications Manager Release 6.1(3x), you can specify a relative path for the download directory by using the ./ notation, as shown in the following example:
Download directory: ./RepStat
If you specify a download directory that does not exist on your local computer, the file get command creates it for you.
New Commands and Parameters
This section provides information about the following new CLI command for Cisco Unified Communications Manager Release 6.1(3x):
utils create report csa
This command collects all the files that are required for CSA diagnostics and assembles them into a single CSA diagnostics file. You can retrieve this file by using the file get command.
For more information about command syntax and parameters, see Appendix A of the Cisco Unified Communications Operating System Administration Guide and the Command Line Interface Reference Guide for Cisco Unified Solutions.
Cisco Unified Communications Manager Administration
This section contains information on the following topics:
•
•
•
New and Updated Enterprise and System Parameters
The following sections contain information on new and updated enterprise and service parameters:
Enterprise Parameters
No enterprise parameters updates occurred for Cisco Unified Communications Manager 6.1(3x).
Service Parameters
To access the service parameters in Cisco Unified Communications Manager Administration, choose System > Service Parameters. Choose the server and the service name that the parameter supports. For some parameters, you may need to click Advanced to display the service parameter. To display the help for the service parameter, click the name of the service parameter in the window.
•
•
•
•
•
Menu Changes
This section contains information on the following menus in Cisco Unified Communications Manager Administration:
Main Window
After you log in to Cisco Unified Communications Manager Administration, messages may display that indicate the current state of licenses for Cisco Unified Communications Manager. For more information, see the "Licensing Enhancements" section.
System
The System menu contains the following changes:
•
•
•
Call Routing
The Call Routing menu provides the following new and updated settings.
•
Media Resources
No changes exist for the Media Resources menu.
Voice Mail
No changes exist for the Voice Mail menu.
Device
The Device menu displays the following new and updated settings.
•
•
•
•
Application
No updates or new fields exist for this menu.
User Management
No changes exist for the User Management menu.
Bulk Administration
The Bulk Administration menu displays the following new and updated settings.
•
•
•
•
•
•
•
•
•
•
•
•
•
Cisco Unified Communications Manager Features and Applications
This section contains information on the following Cisco Unified Communications Manager Administration features and applications:
This section contains information on the following Cisco Unified Communications Manager Administration features and applications:
•
•
•
•
•
•
•
•
•
Always Use Prime Line
Tip
Description
After you configure the Always Use Prime Line setting in Cisco Unified Communications Manager Administration, when the phone is idle (off hook) and receives a call on any line, the primary line gets chosen for the call.
Tip
Cisco Unified Communications Manager Administration Configuration Tips
When you configure this feature, going off hook makes only the first line active, even when a call rings on another line on the phone; that is, the call does not get answered on that line. In this case, the phone user must choose the other line to answer the call.
For more configuration considerations, see Table 3.
GUI Changes
The Always Use Prime Line for Voice Message setting displays in the following windows in Cisco Unified Communications Manager Administration.
•
•
•
•
•
For information on how the Always Use Prime Line setting works when a phone idle or busy, see Table 3.
Tip
Service Parameter and Enterprise Parameter Changes
If you want to configure this feature via the clusterwide service parameter, Always Use Prime Line, which supports the Cisco CallManager service, choose System > Service Parameters in Cisco Unified Communications Manager Administration. Then, choose the server and the Cisco CallManager service. From the Always Use Prime Line drop-down list box, choose True.
Installation/Upgrade (Migration) Considerations
No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 6.1(3x), you can configure this feature per device or per device profile.
Serviceability Considerations
This feature relies on the Cisco CallManager service, so activate the service by choosing Tools > Service Activation in Cisco Unified Serviceability. In addition, you can run SDI trace for the Cisco CallManager service. When you view the log in RTMT, you can see the configured value that is used by the device; for example, alwaysPrimeLine=1, which indicates that the device uses On for the configuration.
BAT Considerations
The Bulk Administration GUI has the following updates to support the Always Use Prime Line feature:
•
–
–
–
Note
Note
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
•
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL or CTI considerations exist for this feature.
User Tips
For a list of phones that support this feature, see the "Line Select" section.
For More Information
•
Always Use Prime Line for Voice Message
Tip
Description
After you configure the Always Use Prime Line for Voice Message setting in Cisco Unified Communications Manager Administration, the primary line on the phone becomes the active line for retrieving voice messages when the phone user presses the Messages button on the phone.
Tip
Cisco Unified Communications Manager Administration Configuration Tips
For configuration considerations, see Table 4.
GUI Changes
The Always Use Prime Line for Voice Message setting displays in the following windows in Cisco Unified Communications Manager Administration.
•
•
•
•
•
For information on how the Always Use Prime Line for Voice Message setting works when a phone is idle or busy, see Table 4.
Tip
Service Parameter and Enterprise Parameter Changes
If you want to configure this feature via the clusterwide service parameter, Always Use Prime Line for Voice Message, which supports the Cisco CallManager service, choose System > Service Parameters in Cisco Unified Communications Manager Administration. Then, choose the server and the Cisco CallManager service. From the Always Use Prime Line for Voice Message drop-down list box, choose True.
Installation/Upgrade (Migration) Considerations
No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 6.1(3x), you can configure this feature per device.
Serviceability Considerations
This feature relies on the Cisco CallManager service, so activate the service by choosing Tools > Service Activation in Cisco Unified Serviceability. In addition, you can run SDI trace for the Cisco CallManager service. When you view the log in RTMT, you can see the configured value that is used by the device; for example, alwaysUsePrimeLineForVM=2, which indicates that the device uses the default.
BAT Considerations
The Bulk Administration GUI has the following updates to support the Always Use Prime Line for Voice Mail feature:
Always Use Prime Line for Voice Message drop-down list box—choose one of the following options:
•
•
•
Note
Note
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL or CTI considerations exist for this feature.
User Tips
For a list of phones that support this feature, see the "Line Select" section.
For More Information
Barge, cBarge, and Single Button Barge Support for PLAR
Tip
Description
Barge, cBarge, or single-button barge allow a phone user to get added to a remotely active call that is on a shared line. Private Line Automatic Ringdown (PLAR) allows the phone user to dial a preconfigured number, and only this number, from the PLAR line. In Cisco Unified Communications Manager 6.1(3x), a barge, cBarge, or single-button barge initiator can barge into a call via a shared line that is configured for PLAR; that is, the initiator can barge into the call if the barge target uses the preconfigured number that is associated with the PLAR line while on the call.
In previous releases of Cisco Unified Communications Manager, Cisco Unified Communications Manager sent the cBarge invocation to the PLAR line before connecting the barge call. If the PLAR line was busy in previous releases, the initiator received a busy reorder tone. In Cisco Unified Communications Manager 6.1(3x), Cisco Unified Communications Manager does not send the barge invocation to the PLAR line before it connects the barge call, so the barge occurs no matter what the state of the PLAR destination.
Cisco Unified Communications Manager Administration Configuration Tips
To make barge, cBarge, or single-button barge work with PLAR, you must configure barge, cBarge, or single-button barge, as described in the "Barge and Privacy" chapter in the Cisco Unified Communications Manager Features and Services Guide. In addition, you must configure the PLAR destination, a directory number that is used specifically for PLAR. The following examples describe how to enable PLAR functionality for phones that are running SCCP and for phones that are running SIP.
A and A' represent shared-line devices that you configured for barge, cBarge, or single-button barge, and B1 represents the directory number for the PLAR destination. To enable PLAR functionality from A/A', which are running SIP, see the following example:
Tip
Example for How to Configure PLAR
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
GUI Changes
No new configuration settings display in Cisco Unified Communications Manager Administration for this feature.
Service Parameter and Enterprise Parameter Changes
For parameters that you configure for barge, refer to the "Barge and Privacy" chapter in the Cisco Unified Communications Manager Features and Services Guide and the "Party Entrance Tone" section.
Installation/Upgrade (Migration) Considerations
You can use this feature after you install or upgrade to Cisco Unified Communications Manager 6.1(3x).
Serviceability Considerations
No special serviceability considerations exist for this feature.
BAT Considerations
No BAT considerations exist for this feature.
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL or CTI considerations exist for this feature.
User Tips
By pressing the Barge, cBarge, or Single Button Barge softkey in the remote in use call state, the initiator gets added to the call with all parties, and all parties receive a barge beep tone (if configured).
For a list of phones that support this feature, see the "Barge Tone Enhancements" section.
For More Information
•
Cisco Unified Communications Manager Assistant
Tip
Cisco Unified Communications Manager Release 6.1(3x) supports numeric user ID login for Cisco Unified Communications Manager Assistants from their Cisco Unified IP Phones.
To configure numeric user ID login, perform the following steps:
Procedure
Step 1
Step 2
In the section "Clusterwide Parameters (Parameters that apply to all servers)" set Alpha Numeric UserID to False.
Step 3
Cisco Web Dialer Configured in Application Server Window
Tip
Description
In previous releases of Cisco Unified Communications Manager, the List of WebDialers field in the Service Parameter window supported a maximum of 255 characters, which limited the scalability of the Redirector. In Cisco Unified Communications Manager 6.1(3x), you configure the Web Dialer servers in the Application Server Configuration window instead of the Service Parameters Configuration window.
Cisco Unified Communications Manager Administration Configuration Tips and GUI Changes
It is now possible for you to add a Cisco Web Dialer application server through the Application Server Configuration window. You access the Application Server Configuration window by choosing System > Application Server in Cisco Unified Communications Manager Administration. Cisco Web Dialer appears as one of the options in the Application Server Type drop-down list box.
If you add a Cisco Web Dialer application server in the Application Server Configuration window, the server displays in the List of WebDialers field in the Service Parameter Configuration window for the Cisco WebDialer Web Service.
Service Parameter and Enterprise Parameter Changes
In Cisco Unified Communications Manager 6.1(3x), you can configure either the List of WebDialers service parameter or the Cisco Web Dialer application server through the Application Server Configuration window. If you add a Cisco Web Dialer application server in the Application Server Configuration window, the server displays in the List of WebDialers field in the Service Parameter Configuration window for the Cisco WebDialer Web Service. You can access the Service Parameter Configuration window by choosing System > Service Parameters in Cisco Unified Communications Manager Administration.
Installation/Upgrade (Migration) Considerations
If you configured the List of WebDialers field in the Service Parameter Configuration window for the Cisco WebDialer Web Service before the upgrade to Cisco Unified Communications Manager 6.1(3x).
If you install Cisco Unified Communications Manager 6.1(3x) and plan to use Cisco Web Dialer, configure the Cisco Web Dialer application server in the Application Server Configuration window. You do not need to configure the List of WebDialers field in the Service Parameter Configuration window if you configure the application server in the Application Server Configuration window.
Serviceability Considerations
Cisco Web Dialer relies on the Cisco WebDialer Web Service. If you have not already done so, activate this service in the Service Activation window in Cisco Unified Serviceability.
BAT Considerations
No BAT considerations exist for this feature.
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
See the "Cisco Web Dialer API" section.
User Tips
For user enhancements for Cisco Web Dialer, see the "Web Dialer Enhancements" section.
For More Information
•
Location-Based Call Admission Control Over Intercluster Trunk
Description
When a call is made across cluster through an intercluster trunk (ICT) and gets hairpinned back to the same location or site of the same cluster, although the media is exchanged between two endpoints in the same site or location, the current design of Cisco Unified Communications Manager location call admission control (CAC) deducts location bandwidth twice, once for the outbound call and again for the inbound call. The result does not correctly reflect the bandwidth consumption, which eventually causes denial of a new call to or from the site or location.
To resolve the bandwidth calculation problem, this feature enables Cisco Unified Communications Manager to pass location information, the primary key ID (PKID) of location record and location name, as a proprietary information element (IE) between the calling and called parties through an ICT, either in the H.323 protocol or SIP. Thus, either endpoint knows the true location information of the party/endpoint, not the location information of the ICT.
Currently, Cisco Unified Communications Manager has Hub_None as the default location that has unlimited bandwidth, plus any user-created location to which the user can assign a device and for which the user can configure bandwidth.
A new type of Cisco Unified Communications Manager location gets created specifically for the ICT for this application type. This new type of location, designated as the Phantom location, also has unlimited bandwidth. The locations server does not deduct bandwidth for a device that is assigned to the Phantom location. A device, such as the ICT, that is assigned to the Phantom location can use its own location or the true location of the connected device. Likewise, the outbound ICT can use its own location or the callee location, and the inbound ICT can use its own location or the caller location to deduct or adjust the bandwidth.
When the media connects, Cisco Unified Communications Manager adjusts the allocated location bandwidth according to the negotiated media codec. Cisco Unified Communications Manager can correctly readjust the location bandwidth based on received callee location information for the outbound call. This enhancement helps the outbound call, which has reserved bandwidth during call setup time, to adjust the bandwidth back to 0 if the call is hairpinned back to the same site or location.
Some supplementary services, such as transfer, can also hairpin the call back to the same site or location after the initial call setup process. Consider passing the location information of the final destination through the Notify signals (H.323) and re-INVITE signals (SIP) back to the calling cluster, so bandwidth can be adjusted to the right value as also required.
Because location record PKID is uniquely defined within the Cisco Unified Communications Manager enterprise environment, Cisco Unified Communications Manager uses location record PKID to identify whether the call over ICT has been looped back to the same cluster for the location-based CAC purpose. If other applications, like Cisco Voice Proxy (CVP), that do not have access to the Cisco Unified Communications Manager database for location record PKID information and also because PKID is a string of characters and digits, applications may need to rely on the location name information being passed around for the purpose of CAC. The same location name may exist for different locations with different location PKIDs in two different Cisco Unified Communications Manager clusters, which may cause confusion to the applications.
Cisco Unified Communications Manager Administration Configuration Tips
The Location Configuration window specifies the Phantom location as a location, besides the Hub_None location, that can get selected. Administrators cannot delete the Phantom location.
Administrators can create a new default location for the new Phantom location, similar to the Hub_None location. The Phantom location has unlimited audio and video bandwidth value, and the administrator cannot modify the audio and video bandwidth values. The user can assign a location-pair RSVP policy between this new location and other existing locations.
Caution
GUI Changes
This feature does not entail any new menu options or new fields in Cisco Unified Communications Manager Administration. The Phantom value is added for all entities that specify a location in the Location drop-down list box. Find the Location field on the Device Pool Configuration, Annunciator Configuration, Music On Hold (MOH) Server Configuration, Conference Bridge Configuration, Voice Mail Port Configuration, Voice Mail Port Wizard Configuration, CTI Route Point Configuration, Gateway Configuration, Phone Configuration, Trunk Configuration, and Pilot Point Configuration windows.
Service Parameter and Enterprise Parameter Changes
No service parameter nor enterprise parameter changes apply to this feature.
Installation/Upgrade (Migration) Considerations
Cisco Unified Communications Manager maintains the RSVP policy for the Phantom location during migration.
Serviceability Considerations
No serviceability considerations exist for this feature.
BAT Considerations
No BAT considerations exist for this feature.
CAR/CDR Considerations
No CAR nor CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL nor CTI considerations exist for this feature.
User Tips
This feature does not entail user interaction.
For More Information
•
•
•
•
Licensing Enhancements
Description
Cisco Unified Communications Manager 6.1(3x) identifies the state of a license; that is, if it is missing, if it represents a demo license, or if it represents an uploaded license. In addition, Cisco Unified Communications Manager Administration warns you whether Cisco Unified Communications Manager currently operates with demo licenses, with an insufficient number of licenses, or with an incorrect software feature license.
Cisco Unified Communications Manager Administration Configuration Tips
For information on how to configure licensing, refer to the licensing chapters in the Cisco Unified Communications Manager Administration Guide.
GUI Changes
The following windows display the state of licenses in Cisco Unified Communications Manager Administration:
•
–
–
–
•
•
Service Parameter and Enterprise Parameter Changes
No service parameters or enterprise parameters considerations exist for these licensing enhancements.
Installation/Upgrade (Migration) Considerations
After you upgrade to Cisco Unified Communications Manager 6.1(3x) from a compatible Cisco Unified CM 5.x or 6.x release, the Cisco CallManager service does not automatically run, even though Cisco Unified Serviceability shows that the Cisco CallManager service is activated.
When you upgrade from any supported release of Cisco Unified Communications Manager to Release 6.1(3x), you must download and install a software feature license to activate the new features. The Cisco Unified Communication Administration Guide indicates that you must install a software feature license only if you are upgrading from 5.x or 6.x releases. You also need a license if you are upgrading from supported 4.x releases. For instructions about how to obtain and install a software feature license, see the "License File Upload" chapter in the Cisco Unified Communications Manager Administration Guide.
Immediately after you complete the upgrade to Cisco Unified Communications Manager 6.1(3x), upload the software feature license that is required for Cisco Unified Communications Manager 6.1(3x) in Cisco Unified Communications Manager Administration and restart the Cisco CallManager service in Cisco Unified Serviceability. Until you perform these tasks, devices fail to register with Cisco Unified Communications Manager 6.1(3x).
Serviceability Considerations
After you upload a license file, you must restart the Cisco CallManager service for the changes to take effect.
BAT Considerations
No BAT considerations exist for these licensing enhancements.
CAR/CDR Considerations
No CAR or CDR considerations exist for these licensing enhancements.
Security Considerations
No security considerations exist for these licensing enhancements.
AXL and CTI Considerations
No AXL or CTI considerations exist for these licensing enhancements.
User Tips
This feature does not impact the end user.
For More Information
•
Logging Missed Calls For Shared Lines
Tip
Description
With the missed call logging for shared lines feature, the administrator can configure Cisco Unified Communications Manager Administration, or the phone user can configure Cisco Unified CM User Options, so Cisco Unified Communications Manager logs missed calls in the call history to a specified shared line appearance on a phone.
Tip
The examples in Table 5, which use the following phones, describe how the missed call logging feature works for shared lines:
•
•
•
Cisco Unified Communications Manager Administration Configuration Tips
If this feature is not configured, the call history on the phone does not display missed calls for the specified line appearance.
GUI Changes
The Directory Number Configuration window in Cisco Unified Communications Manager Administration displays the Logged Missed Calls check box, which turns on or off this feature. If the check box displays as checked (turned on), which is the default for this setting, Cisco Unified Communications Manager logs missed calls in the call history for that shared line appearance on the phone. To access the check box, choose Call Routing > Directory Number. In the Directory Number Configuration window, highlight the associated device in the Associated Devices pane; then, click the Edit Line Appearance button.
In the Line Settings Configuration window in the Cisco Unified CM User Options, the phone user can check and uncheck the Log Missed Calls check box.
Service Parameter and Enterprise Parameter Changes
No new or updated parameters exist for this feature.
Installation/Upgrade (Migration) Considerations
Cisco Unified Communications Manager 6.1(3x) introduces this feature.
Serviceability Considerations
No serviceability considerations exist for this feature.
BAT Considerations
The Bulk Administration GUI has the following updates to support the Log Missed Calls feature:
•
Note
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
–
–
•
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL or CTI considerations exist for this feature.
User Tips
Tip
For a list of phone models that support this feature, see the "Missed Calls" section.
For More Information
Multicast Music On Hold Over H.323/SIP Trunk
Description
The Multicast Music on Hold (MOH) over H.323/SIP Trunk feature allows multicast MOH to work over H.323 and Session Initiation Protocol (SIP) intercluster trunks (ICTs). Prior to the implementation of this feature, multicast MOH used bandwidth for each unicast MOH over the same ICT, which wasted bandwidth.
Prior to the implementation of this feature, the H.323 Open Logical Channel (OLC) ACK message carried the IP address and port for multicast MOH. With the implementation of this feature, the H.323 OLC message now carries the IP address and port for multicast MOH, and Cisco Unified Communications Manager adds the mechanism to handle the information in the H.323 OLC message.
The new service parameter, Send Multicast MOH in H.245 OLC Message, controls the new feature. Both Cisco Unified Communications Manager nodes that are involved in the call must support single-transmitter multicast for the setting of this parameter to have any effect. This service parameter affects only the side of the party that places the call on hold and does not affect how the far end carries the multicast transport address. Even if this parameter is turned off, multicast MOH applies for the held-party side of the call as long as the held party has the capability to support single-transmitter multicast.
When a call connects over an intercluster trunk and one of the parties presses the Hold key, MOH will stream over the intercluster trunk. If multicast MOH is turned on and the holding party and trunk are configured to use the multicast MOH server, MOH streams with multicast. Only one multicast MOH stream streams over the trunk no matter how many calls get put on hold on this trunk.
Cisco Unified Communications Manager Administration Configuration Tips
Calls that connect over Cisco Unified Communications Manager intercluster trunks use this feature for multicast MOH. This feature does not work if any middle box between Cisco Unified Communications Managers does not pass the new fields in Terminal Capability Set (TCS) and OLC message.
No additional configuration exists for this new feature in addition to the normal configuration for setting up multicast MOH. This new feature only applies between Cisco Unified Communications Managers that support single-transmitter multicast.
You can turn this feature off by changing the default True value of the new Send Multicast MOH in H.245 OLC Message service parameter to False. You may need to do so if an interoperability issue arises.
GUI Changes
This feature does not entail any GUI changes to Cisco Unified Communications Manager Administration.
Service Parameter and Enterprise Parameter Changes
If you want to configure this feature via the clusterwide service parameter, Send Multicast MOH in H.245 OLC Message, which supports the Cisco CallManager service, choose System > Service Parameters in Cisco Unified Communications Manager Administration. Then, choose the server and the Cisco CallManager service. From the Send Multicast OH in H.245 OLC Message drop-down list box, choose True.
The new feature remains active by default. To turn off the feature, set the value of the Send Multicast MOH in H.245 OLC Message service parameter to False. Do so to resolve interoperability issues that the feature may cause.
The new service parameter governs the multicast MOH behavior on H.323 trunks and devices. The new service parameter does not control multicast MOH over SIP trunks, because multicast MOH over SIP trunks does not constitute a new behavior.
Installation/Upgrade (Migration) Considerations
No installation nor upgrade considerations exist for this feature. You may, however, turn off the feature if interoperability issues arise as a result of the feature. To do so, set the value of the Send Multicast MOH in H.245 OLC Message service parameter to False.
Serviceability Considerations
No serviceability considerations exist for this feature.
BAT Considerations
No BAT considerations exist for this feature.
CAR/CDR Considerations
No CAR nor CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL considerations exist for this feature.
CTI-controlled phones work as before for multicast MOH. CTI-controlled applications such as CTI ports, and CTI route points do not perform multicast MOH, which is the same behavior as prior to the implementation of this feature.
User Tips
When multicast MOH gets turned on in Cisco Unified Communications Manager Administration, phone users receive MOH if the call connects through an intercluster trunk.
For More Information
•
Party Entrance Tone
Tip
Description
Tip
With the party entrance tone feature, a tone plays on the phone when a basic call changes to a mult-party call; that is, when a basic call changes to a barged call, cBarged call, ad hoc conference, meet-me conference, or a joined call. In addition, a different tone plays when a party leaves the multiparty call.
If the controlling device, that is, the originator of the multiparty call, has a built-in bridge, the tone gets played to all parties if you configured party tone entrance for the controlling device. When the controlling device leaves the call, Cisco Unified Communications Manager identifies whether another device on the call can play the tone; if another device on the call can play the tone, Cisco Unified Communications Manager plays the tone. If the controlling device cannot play the tone, Cisco Unified Communications Manager does not play the tone even if you enable the party entrance tone feature.
When a joined call or ad hoc conference begins, Cisco Unified Communications Manager uses the party entrance tone configuration from the conference controller. Cisco Unified Communications Manager uses this configuration until the conference ends.
If two ad hoc conferences are chained together and the controlling device for one conference has the party entrance tone set to True while the other controlling device for the other conference has a party entrance tone of False, Cisco Unified Communications Manager determines whether to plan the tone based on the conference to which the new party is added.
When a barge call gets created, the party entrance tone configuration of the barge target that shares the line with the barge initiator determines whether Cisco Unified Communications Manager plays the party entrance tone.
When a cBarge call gets created, the party entrance tone configuration of the cBarge target that shares the line with the cBarge initiator determines whether Cisco Unified Communications Manager plays the party entrance tone. However, if the target for the call is an existing ad hoc conference that is in the same cluster, the party entrance tone configuration for the ad hoc conference controller determines whether Cisco Unified Communications Manager plays the tone.
When a meet-me conference gets created, the party entrance tone configuration for the first party to enter the conference determines whether Cisco Unified Communications Manager plays the tone. Cisco Unified Communications Manager uses the configuration for the first party until the conference ends.
Cisco Unified Communications Manager Administration Configuration Tips and GUI Changes
To use the party entrance feature, ensure that you turned the privacy feature off for the devices and ensure that the controlling device for the multiparty call has a built-in bridge.
To configure the party entrance tone for a specific directory number, choose Call Routing > Directory Number in Cisco Unified Communications Manager Administration. From the Party Entrance Tone drop-down list box, choose one of the following options:
•
•
•
Service Parameter and Enterprise Parameter Changes
To configure this feature for all phones that are configured in Cisco Unified Communications Manager Administration instead of configuring this feature per line, configure the Party Entrance Tone service parameter, which supports the Cisco CallManager service. To access this parameter, choose System > Service Parameters in Cisco Unified Communications Manager Administration; choose the server and the Cisco CallManager service. When the parameters display, locate the Party Entrance Tone service parameter. For more information on this parameter, click the name of the service parameter or the question-mark button in the Service Parameter Configuration window.
Installation/Upgrade (Migration) Considerations
Cisco Unified Communications Manager 6.1(3x) introduces this feature.
Serviceability Considerations
This feature relies on the Cisco CallManager service, so make sure that the service is activated in Cisco Unified Serviceability.
BAT Considerations
The Bulk Administration GUI has the following updates to support the party entrance tone feature:
•
–
–
–
Note
•
•
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL or CTI considerations exist for this feature.
User Tips
For information on the phones that support this feature, see the "Barge Tone Enhancements" section.
For More Information
Transit Counter That is Implemented in Codeset5 for QSIG PRI Trunks
An IE that Q.931 supports, called Transit Counter, stops routing loops on PBXs.
The transit counter information element specifies a maximum length of 3 octets and may get included in the setup message. It indicates the number of private network transit exchanges that occur in a requested connection.
Cisco Unified CM parses a transit counter that is received in a setup message on a QSIG Trunk (as well as Annex M.1) when it is received in locking codeset5 and sends it to call control. If the subsequent leg of the call is QSIG , that leg increments the received transit counter and sends it outbound over QSIG (and Annex M.1) in locking codeset5.
Note
A new service parameter, Enable Transit Counter Processing on QSIG Trunks, controls this implementation.
When the service parameter is set to false, the Unified CM
•
•
When the service parameter is set to true, the Unified CM
•
•
Unconfigured Device Registration Attempts Restricted
Prior to Cisco Unified Communications Manager 6.1(3x), if a Cisco Unified IP Phone had not been added to the Cisco Unified Communications Manager database and did not have auto-registration enabled, the phone would repeatedly attempt to register (unsuccessfully) with Cisco Unified Communications Manager, thus wasting Cisco Unified Communications Manager with these repeated registration requests.
However, in Cisco Unified Communications Manager 6.1(3x), if auto-registration is not enabled and the phone has not been added to the Cisco Unified Communications Manager database, the phone will not attempt to register with Cisco Unified Communications Manager. The phone continues to display the Configuring IP message until auto-registration gets enabled or until the phone gets added to the Cisco Unified Communications Manager database.
Supported Devices
The following devices support this changed registration behavior:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
For more information, refer to the Cisco Unified IP Phone Administration Guide.
Cisco Unified Communications Manager Administration Configuration Tips
For information on configuring autoregistration, refer to the "Autoregistration" chapter in the Cisco Unified Communications Manager System Guide. For information on configuring a phone, refer to the "Phone Configuration" chapter in the Cisco Unified Communications Manager Administration Guide.
Before you configure a phone, consider the following information:
•
–
–
•
For a phone that uses a real MAC address, not the dummy MAC address that is created via BAT, the check box displays as checked and disabled, which indicates that the phone uses device license units and can register with Cisco Unified Communications Manager.
For a phone that uses the dummy MAC address that is created via BAT, the Is Active check box displays as unchecked and enabled. If you manually convert the dummy MAC address to a real MAC address in the Phone Configuration window, check the Is Active check box, which ensures that the phone can register with Cisco Unified Communications Manager and that licensing consumes device license units for the phone.
•
•
•
•
GUI Changes
No new fields display in Cisco Unified Communications Manager Administration for this feature.
Service Parameter and Enterprise Parameter Changes
No parameter changes exist for this feature.
Installation/Upgrade (Migration) Considerations
After you install Cisco Unified Communications Manager 6.1(3x), if auto-registration is not enabled and the phone has not been added to the Cisco Unified Communications Manager database, the phone does not attempt to register with Cisco Unified Communications Manager.
Serviceability Considerations
The Real-Time Monitoring Tool and Cisco Unified Reporting can display information on registered and unregistered devices. For more information, refer to the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide and the Cisco Unified Reporting Administration Guide.
BAT Considerations
For information on adding devices through BAT, refer to the Cisco Unified Communications Manager Bulk Administration Guide.
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL or CTI considerations exist for this feature.
User Tips
If the Configuring IP message displays on the phone, the phone user should contact the phone administrator.
Viewing Held Calls on Shared Lines
Tip
Description
With the held calls on shared lines feature, a phone user can determine whether the call was put on hold by the phone user locally at the primary device or by another party remotely on a shared device. How the held call displays on the devices depends on whether the primary device or shared device puts the call on hold. For information on how the held call displays on the devices, see the "Hold Status" section.
Cisco Unified Communications Manager Administration Configuration Tips and GUI Changes
This feature requires no configuration to work.
Service Parameter and Enterprise Parameter Changes
This feature requires no configuration to work.
Installation/Upgrade (Migration) Considerations
Cisco Unified Communications Manager 6.1(3x) introduces this feature.
Serviceability Considerations
No serviceability considerations exist for this feature.
BAT Considerations
No BAT considerations exist for this feature.
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL or CTI considerations exist for this feature.
User Tips
For a list of phones that support this feature, see the "Hold Status" section.
For More Information
Bulk Administration Tool
This section contains information on the following topics:
•
•
•
Support for Party Entrance Tone
The Bulk Administration GUI has the following updates to support the party entrance tone feature:
•
–
–
–
Note
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
–
–
–
•
•
Support for Log Missed Calls
The Bulk Administration GUI has the following updates to support the Log Missed Calls feature:
•
Note
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
–
–
•
•
Support for Always Use Prime Line
The Bulk Administration GUI has the following updates to support the Always Use Prime Line feature:
•
–
–
–
•
–
–
–
Note
Note
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
•
•
•
Support for VG202 and VG204 Gateways
BAT now supports VG202 and VG204 gateways. The Bulk Administration Tool has the following updates to support VG202 and VG204 gateways:
•
•
•
•
•
•
•
Cisco Unified Serviceability
The following sections comprise new and changed features in serviceability for Unified CM 6.1(3x).
•
Cisco UXL Web Service Added to Service Activation Window
In most Cisco Unified Communications Manager releases, the TabSync client in Cisco IP Phone Address Book Synchronizer uses AXL for end-user queries to the Cisco Unified Communications Manager database. In Cisco Unified Communications Manager 6.1(3x), the TabSync client uses the Cisco UXL Web Service for queries to the Cisco Unified Communications Manager database, which ensures that Cisco IP Phone Address Book Synchronizer users have access only to end-user data that pertains to them.
In the Service Activation window in Cisco Unified Serviceability (Tools > Service Activation), you can activate the Cisco UXL Web Service, which performs the following functions:
•
•
Cisco Unified Real-Time Monitoring Tool
This section contains information on the following topics:
•
Quality Report Tool Reports
A change occurred in the Call State information that is collected from Cisco Unified Communications Manager/CTIManager and displayed in the Quality Report Tool (QRT) reports. Previously, the information included Connected, Connected Conference, Connected Transfer, and On Hook call state information. Now, the report only includes Connected and On Hook call state information.
System History Log Displays in RTMT
To access the system history log in RTMT, navigate to RTMT Trace Collection:
RTMT > Trace Log Collection
For more information on the system history log, see the "System History Log for Cisco Unified Communications Manager" section.
Cisco Unified Communications Manager CDR Analysis and Reporting
This section contains these subsections:
•
•
•
•
•
•
•
•
Configuring Department Bills Reports
The following additional note applies to Step 6 of the Configuring Department Bills Reports procedure:
Click the Down radio button to view your direct reports. Use the Up and Down radio buttons to move up and down the report chain.
Reports That Are Unavailable to Administrator While CAR Database Gets Manually Purged or CDR Records Get Reloaded
A CAR administrator can no longer generate CAR reports when a manual purge of the CAR database is in process or CDR records are reloading. The following message displays when you try to run reports during these processes:
10023: Manual Purge/Reload is in process. Please run the reports once the Manual Purge/Reload is over.Both the Purge button and the Reload All Call Detail Records button get disabled, and the following message displays on the Manual Purge window, when either a manual purge or CDR reload occurs:
Manual Purge/Reload is still running. User will not be allowed to run another instance of Manual Purge/Reload. So, both Purge and Reload All Call Detail Records buttons are disabled.Before this enhancement, a CAR administrator could request CAR reports during the purge, but message 10012 displayed.
SIP Call with URL as Extension Number Now Supported
Because calling and called parties can have SIP calls where the extension number is a URL, you can use all printable ASCII characters in the extension number. No space gets allowed in the URL. For example, extension "1000 1001" does not get accepted as a valid URL. The following message displays:
30035 Invalid extension number.
Note
CDR Search by User Extension Supports "+" and URLs for SIP Calls
When you use the CDR Search by User Extension feature, you may use the "+" in any position of the user extension number; however, in the current release of Cisco Unified Communications Manager and previous releases, the "+" cannot be used in any dial plan configurations.
When the user extension number is a SIP call with a URL, the system allows no space in the URL.
Changes to Mail Server Configuration GUI
You must now configure the mail ID, mail domain, and mail server name when you configure the mail server. Previously, you only had to configure the mail ID.
Procedure
Step 1
The Mail Parameters window displays.
Step 2
Note
Step 3
Step 4
Step 5
Note
Step 6
Change in Supported FTP/SFTP Versions for CAR Billing Servers
Cisco allows you to use any SFTP server product but Cisco recommends SFTP products that have been certified with Cisco through the Cisco Technology Developer Partner (CTDP) program.
CTDP partners, such as GlobalSCAPE, certify their products with a specified version of Cisco Unified Communications Manager. You may use one of these servers, but you must contact the vendor for support:
•
•
•
For issues with third-party products that have not been certified through the CTDP process, contact the third-party vendor for support.
Cisco has tested and will support the following versions of FTP or SFTP for CAR billing servers:
Linux/Unix
FTP: Unix (SunOS 5.6 Generic_105181-10) and Linux server (2.4.21-47.ELsmp and 2.6.9-42.7.ELsmp)
SFTP: Unix (SunOS 5.6 Generic_105181-10) and Linux server (2.4.21-47.ELsmp and 2.6.9-42.7.ELsmp)
Windows
FTP: Microsoft FTP service (Windows 2000 5.00.2195 sp4, IIS 5.0) and WAR FTP Daemon (1.82.0.10)
Configuring CDR Error Reports
To determine why the error records fail the CDR load, you must review the information in the tbl_error_id_map table.
Table 6 lists the CDR error codes and the definition of the error.
Event Log Report Status
A new field has been added to the Event Log report status: Scheduled—If this check box is checked, the event log report includes tasks that have been scheduled but have not yet started.
When the Scheduler restarts, all unfinished jobs with a status of Scheduled get deleted. Current jobs with the status of In Progress or Scheduled get changed to Unsuccessful.
New Error Message That Is Introduced If Data Present in Invalid or Remainder Partitions
A message gets logged in the CAR Scheduler traces if data is present in invalid and remainder partitions of the tbl_billing_data and tbl_billing_error files.
The LWM/HWM/2M e-mail alerts that get sent to the CAR administrator when CAR detects records in either the part_invalid or part_remainder partitions will contain the following information:
Data is present in invalid/remainder partition also, which cannot be removed by Automatic-Purge. Please delete these record(s) manually from Manual-Purge.Configuring Individual and Department Bills Reports
Before you can configure the Individual Bills report, you must ensure that a device with an assigned Owner User ID exists in Cisco Unified Communications Manager Administration for each user that is included in the report. Use the following procedure to create the Owner User IDs:
Procedure for Adding Owner User ID to Individual Bills
In Cisco Unified Communications Manager Administration, choose Device > Phone > Add a New Phone > Phone Configuration.
Add the information for the device and the user.
Before you can configure the Department Bills report, you must ensure that a device with an assigned Owner User ID and Manager User ID exists in Cisco Unified Communications Manager Administration for each user that is included in the report. Use the following procedure to add the device, Owner User ID, and the associated Manager UserID for each user:
Procedure for Adding Owner User ID and Manager ID to Department Bills
In Cisco Unified Communications Manager Administration, choose Device > Phone > Add a New Phone > Phone Configuration.
Add the information for the device and the user.
In Cisco Unified Communications Manager Administration, choose User Management > End User > Add.
Add the Manager User ID information to the end user information.
For both individual bills and department bills, if the Extension Mobility feature is enabled on the device and the user logs in to the phone and places a call, the User ID that gets recorded in the CDRs represents the logged in User ID. If Cisco Extension Mobility is not enabled on the device, the User ID that gets recorded in the CDRs specifies the Owner User ID that is configured for the device. In the situation where neither the User ID or the Owner User ID is configured (that is, Cisco Extension Mobility is not enabled, and the Owner User ID is not configured), the User ID field in the CDRs gets recorded as blank. In this situation, CAR uses the default User ID of "_unspecified user" when it loads the CDRs, and the CDRs do not display in the Individual Bills User reports because no user by the name of "_unspecifieduser" exists in the Cisco Unified Communications Manager database. If you look for the reports for a particular end user in the directory, either the User ID for the particular end user must be configured as the Owner User ID for the device or the particular end user must have logged in to the device with the Cisco Extension Mobility feature enabled.
Cisco Unified Communications Manager Call Detail Records
This section contains these subsections:
•
•
•
Updated Information on Global Call ID CDR Field
For Cisco Unified Communications Manager Release 5.x and later releases, the value in the GlobalCallId CDR field survives over Cisco Unified Communications Manager restarts. In Release 4.x and earlier releases, even though the GlobalCallId field is time-based, the field gets reused under conditions of heavy traffic. Because of this behavior, problems can occur with customer billing applications and the ability of CAR to correlate CMRs with CDRs and to correlate conference call CDRs. For Release 5.x and later releases, GlobalCallId redesign ensures the field retains a unique value, at least for a certain number of days. Now, the last used globalCallId_callId value gets written to disk periodically (for every x number of calls). The value gets retrieved after a Cisco Unified Communications Manager restart, and the new globalCallId_callId value begins with this number plus x.
CallingPartyNumber CDR Field Not Affected by Direct Calls
When the Add Incoming Number Prefix to CDR service parameter gets set to True, type of number provides the basis for the prefixing digits that get configured. Setting this service parameter to True prefixes only the following prefixing (advanced) service parameters, based on the type of number for the incoming call:
•
•
•
•
Note
For normal calls, without any redirection or split/join in case of feature interaction, the CDR entry for the CallingPartyNumber field remains the same as the incoming number. But for pickup calls (one-touch), the CallingPartyNumber field in the CDR gets changed to the number after transformation at translation pattern level because the CallingPartyNumber field in the CDR gets updated every time a new call request or a split/join or redirection occurs. When an incoming call from a gateway occurs, the nontranslated number gets received for the CallingPartyNumber field in the CDR.
For a direct call, no split/join requests exist; therefore, the CallingPartyNumber field remains the nontranslated number. However, for a one-touch pickup call, upon pickup, the Cisco Unified Communications Manager splits the original call and the pickup call and then joins them together upon pickup. At this point, the translation pattern gets applied to the calling party, and the CDR uses the translated number for the calling party.
In the following examples, the number 89999999 has a calling party transform mask that gets entered as 0351441132. A call comes in from a PSTN from calling party 89999999 to an IP phone on the Cisco Unified Communications Manager.
CDR Example 1
The IP phone answers the call. The calling party transform mask does not get applied to the calling party number.
CDR Example 2
The call gets picked up by another IP phone that is using the one-touch pickup feature. The calling party transform mask gets applied to the calling party number.
CMR Examples Provided
The following examples of CMRs get generated during a normal call (IP phone to IP phone). Normal calls log three records per call: one CDR and two CMRs (one for each endpoint).
These examples represent a call between directory number 1010 and 1014. To see a sample of the CDR that gets generated during a normal call, see the "Normal Calls" section of the latest release of the Cisco Unified Communications Manager Call Detail Records Administration Guide.
CMR Example
Video Conference Call CDR Example
Calls that are part of a video conference have multiple records logged. The number of CDR records that get generated depends on the number of parties in the video conference. One CDR record exists for each party in the video conference: one for the original placed call, one for each setup call that was used to join other parties to the video conference, and one for the last two parties that are connected in the video conference.
Therefore, for a three-party ad hoc video conference, six CDR records exist:
•
•
•
•
Video Conference Call CDR Example
1.
2.
3.
4.
5.
Note
Cisco Unified Reporting
Cisco Unified Reporting includes a new report that indicates the number of phones with no associated users, the number of users that are associated with only one phone, and the number of users that are associated with more than one phone.
For a complete description of reports that are available on your system and the data that gets captured in a report, access the Report Descriptions report, as described in the Cisco Unified Reporting Administration Guide.
Cisco and Third-Party APIs
The following sections describe new features and changes that are pertinent to this release of the Cisco Unified Communications Manager APIs and the Cisco extensions to third-party APIs.:
•
Skinny Client Control Protocol (SCCP)
The following sections describe updates to the SCCP interface:
BLF Enhancements
This release supports the following variations of Busy Lamp Field (BLF):
•
•
I-Hold
This feature provides visual distinction that shows which line placed a call on hold in a shared line configuration. With this enhancement, when a call is put on hold by the local line, the current LED behavior (flashing green) continues, and the remote line changes to a flashing red LED status.
Updated SCCP Messages
This release adds, modifies, or deletes the following SCCP messages:
New messages
•
•
•
•
•
Modified message
•
Deleted messages
•
•
Administrative XML Interface
The Administrative XML (AXL) interface uses the Tomcat web service that is running on the Cisco Unified Communication Manager publisher server to return client data. Several other publisher server features share this service, including Cisco Unified Communication Administration, Cisco IP Manager Assistant, Cisco Web Dialer, Cisco Extension Mobility, and the Bulk Administration Tool. The Cisco Unified Communications Manager publisher server includes enhancements that ensure that no single application can consume all available Tomcat resources.
The AXL interface now includes a throttling mechanism that limits the amount of data that client can return. The limit for data that gets returned in any single request specifies 8 MB. The limit for concurrent data requests specifies 16 MB, which can be split over any number of concurrent requests (for example, 8 concurrent requests with each requiring 2 MB of data to be returned; 4 concurrent requests with each requiring 4 MB of data to be returned; or any other combination not exceeding 8 MB per request or 16 MB concurrently).
This feature
•
•
•
•
•
AXL Data Throttling
The following AXL methods now include data throttling:
•
•
•
•
•
•
With data throttling, the AXL interface now returns the following message when the 8-MB limit is reached: "Query request too large. Total rows matched: <Matched Rows>. Suggested row fetch: less than <Number of Rows>."
In addition, new <skip> and <first> tags for the List X methods allow developers to fetch the data requested.
Developers who use ExecuteSQLQuery should use standard SQL Skip and First tags in the request to retrieve the desired data set.
Interaction
This section describes how the interface responds in a variety of situations.
Example 1, Option 1: Client requests data that exceeds 8 MB
Server response: ProcessingConstraintException AXL error code 5011"Query request too large. Total rows matched: <Matched Rows>. Suggested row fetch: less than <Number of Rows>"
<Number of Rows> specifies the suggested number of rows that a single request can return to keep the data exchange under the 8-MB limit. Clients should use <Matched Rows> to determine the number of iterations that are required to retrieve the complete data set that a query tries to fetch.
Client response, Option 1:
1.
2.
3.
4.
5.
6.
7.
Example 1, Option 2: Client requests data that exceeds 8 MB
Server response: ProcessingConstraintException AXL error code 5011 "Query request too large. Total rows matched: <Matched Rows>. Suggested row fetch: less than <Number of Rows>"
<Number of Rows> specifies the suggested number of rows that a single request can return to keep the data exchange under the 8-MB limit. Clients should use <Matched Rows> to determine the number of iterations that are required to retrieve the complete data set that a query tries to fetch.
Client response, Option 2:
1.
2.
Note
3.
4.
5.
6.
7.
8.
9.
If the response is not a MemoryConstraintException, the client continues the iteration.
10.
Example 2: Client sends single 8-MB request
Server responds with requested data.
Example 3: Client sends two 8-MB requests simultaneously
Server responds with requested data.
Example 4: Client sends more than two 8-MB requests simultaneously
The server processes the first two requests. Other concurrent requests that may be received generate this exception: MemoryConstraintException AXL error code 5009: "Maximum AXL Memory Allocation Consumed. Please retry once requests in progress have completed."
Client response:
1.
Cisco recommends that applications wait 2 to 3 minutes before resubmitting the request.
2.
Example 5: Concurrent data requests reach 16-MB limit
This example applies to all AXL methods.
This situation returns MemoryConstraintException AXL error code 5009: "Maximum AXL Memory Allocation Consumed. Please retry once requests in progress have completed."
Cisco recommends that applications wait 2 to 3 minutes after receiving this message before resubmitting the request.
Using <skip> and <first> Tags in List APIs
The new <skip> and <first> tags provide additional functionality when data is retrieved by using the List methods. If a List Response exceeds 8 MB, the client can fetch data in sets of rows by using a combination of these tags. These tags provide navigation functionality. Be aware that they are not mandatory and have no default values.
In addition,
•
•
•
•
Suggested Use of <skip> and <first> Tags in List APIs
If a client request exceeds 8 MB of data, the server responds: "Total rows matched: <Matched Rows>. Suggested row fetch: less than <Number of Rows>."
<Number of Rows> specifies the suggested number of rows that a single request can return to keep the data exchange under the 8-MB limit. Clients should use <Matched Rows> to determine the number of iterations that are required to retrieve the complete data set that a query tries to fetch.
Client response:
1.
2.
3.
a.
b.
c.
4.
Sample Code for Use of <skip> and <first> Tags in List APIs
Example 1
If the recommended RowFetch is X = 100 for ListPhoneByName, the client should use this logic:
StepSize = RowFetch (X = 9999)//Two variables to store the skip and first values.Int skip = 0;Int first = StepSize;//start the iterationWhile (1){Try {//A function to Modify the values of <first> and <skip> in the request with variables values defined abovemodifyRequest(FilePath);//Sending the modified requestResponse = SendExecuteSQLQuery (select SKIP <SkipCount> First <StepSize> * from endusers;)//Modify the variablesSkip+ = StepSize;First+= StepSize;Check for fault_message from reply//An SQL Exception from server while trying to fetch rows greater than that present in databaseIf(fault_message .contains("No Current Row Found")){Break;}Else{Continue the loop;}} /* end of while*/Example 2
#Declare variable for first and skiplong skip = 0;long first = suggestiveRowFetch;#Calculate number of iterations requiredfloat precision = totalRowFetch/suggestiveRowFetch;calculate the decimal point of variable precisionif decimal point == 0;no. Of Iterations = totalRowFetch/suggestiveRowFetch;if decimal point <5no. Of Iterations = Math.round(totalRowFetch/suggestiveRowFetch)+1;if decimal point >5no. Of Iterations = Math.round(totalRowFetch/suggestiveRowFetch);****Here (no. Of Iterations = 15)********#iteratorint iLoop = 1;while( iLoop <=no. Of Iterations){#modify the values of first and skip in the queryString mdSQLQuery = modifySQLQuery(skip,first); /* Its like select skip 0 first 2000 * from device for first loop*/#send the request and get responseresponse = sendRequest(mdSQLQuery);#update the skip and first variablesskip+=suggestiveRowFetch;first+=suggestiveRowFetch;#check for responseif(response contains MemoryConstraintException){#undo the variable modification to get attributes (i.e skip and first) of the query , that failed with an exception.skip - =suggestiveRowFetch;first - =suggestiveRowFetch;wait till the requests in Progress Gets Processed;continue the loop;}else{iLoop++;}}Sample Code for ExecuteSQLQuery
Example 1
To obtain the first X rows and then next X rows, a client should send queries as described in this section. For example, the client should use the following logic if the recommended RowFetch is X = 9999 for the query "select * from endusers;":
StepSize = RowFetch (X = 9999)SkipCount = 0While (1){Try {Response = SendExecuteSQLQuery (select SKIP <SkipCount> First <StepSize> * from endusers;)RowsReturned = Rowcount (Response);If RowsReturned < StepSizeBreak; /* All the rows have been fetched*/ElseSkipCount = SkipCount + StepSize /*Increase the SkipCount to get the next set of rows*/}Catch for any exception{Take appropriate action based on ExceptionBreak;}} /* end of while*/Example 2
#sql query to be executedsqlQuery = "select * from device";#send the query to serverresponse = sendRequest(sqlQuery);#what is in response?processResponse();**** Response contains an Exception: "Query request too large.Suggestive row fetch 2000 rows.Total row fetch 30000" ****#Declare two variableslong suggestiveRowFetch = 0; /*contains Suggestive RowFetch Count*/long totalRowFetch = 0; /*contains Total RowFetch*/#fetch the two values and store it into variables.parseExceptionMessage();Testing Suggestions
This section provides tests that you can run to check various operations.
Testing ListPhoneByDescription and ListPhoneByName Methods
To test the ListPhoneByDescription and ListPhoneByName AXL methods, follow these steps:
Step 1
Step 2
Step 3
Expected Results: The interface returns "<API name> API request exceeds Threshold Limit. Total rows matched: <Matched Rows>. Suggested row fetch: less than <Number of Rows>." <API name> specifies the name of the API method.
Testing listDeviceByNameAndClass and listDeviceByServiceName Methods
To test the listDeviceByNameAndClass and listDeviceByServiceName AXL methods, follow these steps:
Step 1
Step 2
Step 3
Expected Results: The interface returns "<API name> API request exceeds Threshold Limit. Total rows matched: <Matched Rows>. Suggested row fetch: less than <Number of Rows>." <API name> specifies the name of the API method.
Testing the ExecuteSQLQuery AXL Method
To test the ExecuteSQLQuery AXL method, follow these steps:
Step 1
Step 2
Step 3
Expected Results: Demonstrate that Row Fetch Count logic works and, at the end loop, client can retrieve the entire set of required data from Cisco Unified Communications Manager.
Verifying That Tomcat Resources Are Protected
To verify that Tomcat resources are protected (Publisher server continues to operate under heavy AXL load):
Step 1
Step 2
Step 3
Step 4
Step 5
This analysis indicates whether the total responses that are processed by the AXL interface are within 16 MB. Every third concurrent request should have been rejected. By looking at the JVM on the Tomcat server that was available during the test, you can determine whether enough JVM exits to allow other applications to function properly.
Cisco Web Dialer API
The following sections describe updates to the Cisco Web Dialer API:
•
•
User Interface Enhancements
The following enhancements apply to the Make Call window:
•
•
•
•
•
The following enhancements apply to the Hang Up window:
•
•
Hidden Proxy User Credentials
Credentials no longer display in clear text in a URL. For example, a URL that displayed as follows in previous versions
https://wdserver.com/webdialer/Webdialer?cmd=doSetProfile&destination=&loc=en-us&red=null&uid=wd&pwd=xyz
now displays as
https://wdserver.com/webdialer/Webdialer
As a result, developers who use the browser interface should use the HTTP POST method to pass the parameters. For example, this approach reduces the delay when Web Dialer converts GET parameters to POST:
<FORM action="https://42.88.86.1/webdialer/Webdialer" method="post"><P><INPUT type="hidden" name="destination" value="+666"><INPUT type="submit" value="Send"></P></FORM>Redirector Throttling
Redirector throttling supports up to 8 sessions/requests per second. The system throws the following error if it exceeds the throttle:
HTTP Status 503 - Service temporarily unavailable, please try again later
Configuration Changes
The following configuration changes occurred:
•
•
•
•
1.
2.
Update to Endcall SOAP Method
The SOAP method Endcall update means that it no longer drops all calls on a device. Endcall now ends an active call, but not a call on hold.
Internet Explorer 7 Support
When you exit Cisco Web Dialer when you run it with Internet Explorer 7, the pop-up window that prompts for confirmation no longer displays. This change does not affect the programming interface.
Cisco Unified IP Phones
This section provides the following information:
•
•
•
•
•
See Table 7 for a listing of features and supported phone models.
Barge Tone Enhancements
The Party Entrance Tone configuration is available as a per-line setting, in addition to a service parameter setting for Cisco Unified CM administrators. The default value for the line setting specifies the service parameter setting. Because the Party Entrance Tone is configurable on a per-line basis, it is possible for one caller to hear a tone when he/she creates a conference, but if another caller has Party Entrance Tone set to No, then they do not hear the tone when that he/she creates another conference.
The Party Entrance Tone setting gets applied to Barge, cBarge, Join, Ad-hoc, and Meet Me conferences in the same manner as before.
Barge and cBarge support the interaction with Private Line Automatic Ringdown (PLAR). When a shared line has PLAR configured, a user can Barge or cBarge into a call that is connected on the shared PLAR line.
These Barge Tone enhancements gets supported on the following phones that are running SIP and SCCP:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Where to Find More Information
•
Busy Lamp Field (BLF) Enhancements
Cisco Unified Communications Manager 6.1(3x) introduces the following enhancements for the Busy Lamp Field (BLF) feature:
•
•
These BLF enhancements get supported on the following phones that are running SCCP:
•
•
•
•
•
•
•
•
•
•
•
•
Where to Find More Information
•
•
Cisco Unified IP Phone Expansion Modules 7915 and 7916
The Cisco Unified IP Phone Expansion Module 7915 (grayscale display) and Cisco Unified IP Phone Expansion Module 7916 (color display) attach to your Cisco Unified IP Phone 7962G, 7965G, or 7975G (SCCP or SIP). Each expansion module adds up to 24 extra line appearances or programmable buttons to your phone. You can attach up to two expansion modules to your Cisco Unified IP Phone for a total of 48 extra line appearances or programmable buttons.
Note
Where to Find More Information
•
•
Cisco Unified IP Phone Support HTTPS
Cisco Unified IP Phones can securely access the web with the use of a phone trust store called "phone-trust." Administrators can upload certificates to a phone-trust store by using the Cisco Unified Communications Manager Operating System GUI. The Cisco Unified IP Phone will display a menu option called "Application Server" for each phone-trust store whose certificates have been uploaded into Cisco Unified OS Administration and later downloaded into the Cisco Unified IP Phone CTL file.
The phone-trust certificates and secure HTTPS web access get supported on the following phones that are running SCCP and SIP:
–
–
–
–
–
–
–
–
–
–
–
–
Where to Find More Information
•
•
•
Hold Status
Cisco Unified Communications Manager 6.1(3x) introduces the following enhancements to hold status:
•
•
The hold status enhancement gets supported on the following phones that are running SCCP and SIP:
•
•
•
•
•
•
•
•
•
•
•
•
Where to Find More Information
•
•
Line Select
Cisco Unified Communications Manager 6.1(3x) introduces settings to determine whether the primary line is automatically selected when a call is answered, or when the Messages button is pressed. Be aware that these settings can be made for all phones in the system, or for a single phone.
•
•
Note
These enhancements are supported on the following SIP and SCCP phones:
•
•
•
•
•
•
•
•
•
•
•
•
Where to Find More Information
•
•
•
Missed Calls
The missed calls feature allows the phone administrator to specify whether missed calls will get logged in the missed calls directory for a given line appearance. The following properties apply to the missed calls feature:
•
•
•
•
•
•
•
•
In addition to these properties, the following properties continue to apply all calls:
•
•
The missed calls feature gets supported on the following phones that are running SCCP and SIP:
•
•
•
•
•
•
•
•
•
•
•
•
Where to Find More Information
•
•
Personal Directory and Fast Dial Service
Administrators can set up a service URL that allows users to access their Fast Dials and PAB as services without having to authenticate each time:
•
•
The personal directory and fast dial service get supported on the following phones that are running SCCP and SIP:
•
•
•
•
•
•
•
•
•
•
•
•
Where to Find More Information
•
•
Restrict Unconfigured Phone Registration
Prior to Cisco Unified Communications Manager 6.1(3x), if a Cisco Unified IP Phone had not been added to the Cisco Unified Communications Manager database and did not have auto-registration enabled, the phone would repeatedly attempt to register (unsuccessfully) with Cisco Unified Communications Manager, thus continually notifying Cisco Unified Communications Manager with these repeated registration requests.
With Cisco Unified Communications Manager 6.1(3x), if auto-registration is not enabled, and the phone has not been added to the Cisco Unified Communications Manager database, the phone will not attempt to register with Cisco Unified Communications Manager. The phone will continue to display the "Configuring IP" message until auto-registration has been enabled, or until the phone has been added to the Cisco Unified Communications Manager database.
The registration behavior is supported on the following phones and devices that are running SCCP and SIP:
–
–
–
–
–
–
–
–
–
–
–
–
–
–
Where to Find More Information
•
•
Web Dialer Enhancements
Cisco Unified Communications Manager 6.1(3x) supports the following Web Dialer enhancements:
•
•
•
•
•
Calling <Username if available> at <dial-out number>
If authorization codes are required, enter them now
The Web Dialer enhancements get supported on the following phones that are running SCCP and SIP:
•
•
•
•
•
•
•
•
•
•
•
•
Where to Find More Information
•
Table 7 lists Cisco Unified IP Phones that support the Cisco Unified Communications Manager 6.1(3x) features.
Cisco Unified CM User Options
See the following sections for enhancements to the Cisco Unified CM User Options:
•
Caveats
The following sections contain information on how to obtain the latest resolved caveat information and descriptions of open caveats of severity level 1, 2, and 3.
Caveats describe unexpected behavior on a Cisco Unified Communications Manager server. Severity 1 caveats represent the most serious caveats, severity 2 caveats represent less serious caveats, and severity 3 caveats represent moderate caveats.
Resolved Caveats
You can find the latest resolved caveat information for Cisco Unified Communications Manager Release 6.1(3x) by using Bug Toolkit, which is an online tool that is available for customers to query defects according to their own needs.
Procedure
From http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs perform the following:
Step 1
Step 2
Step 3
Step 4
Step 5
Now, the only option that will get acted upon is the Fixed option.
Step 6
Tip
To access the Bug Toolkit, log on to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.
Using Bug Toolkit
Known problems (bugs) get graded according to severity level. These release notes contain descriptions of
•
•
You can search for problems by using the Cisco Software Bug Toolkit.
To access Bug Toolkit, you need the following items:
•
•
•
To use the Software Bug Toolkit, follow these steps:
Procedure
Step 1
Step 2
Step 3
For information about how to search for bugs, create saved searches, create bug groups, and so on, click Help in the Bug Toolkit window.
Open Caveats
The "Open Caveats as of March 10, 2009" section describes possible unexpected behaviors, supported by component, in Cisco Unified Communications Manager Release 6.1(3x).
Tip
Understanding the Fixed-in Version and the Integrated-in Fields in the Online Defect Record
When you open the online record for a defect, you may see data in the "First Fixed-in Version" or "Integrated-in" fields. The information that displays in these fields identifies the list of Cisco Unified Communications Manager interim versions in which the defect was fixed. These interim versions then get integrated into Cisco Unified Communications Manager releases.
Some more clearly defined versions include identification for Engineering Specials (ES) or Service Releases (SR); for example 03.3(04)ES29 and 04.0(02a)SR1. However, the version information that displays for the Cisco Unified Communications Manager maintenance releases may not be as clearly identified.
The following examples show how you can decode the maintenance release interim version information. These examples show you the format of the interim version along with the corresponding Cisco Unified Communications Manager release that includes that interim version. You can use these examples as guidance to better understand the presentation of information in these fields.
•
•
•
•
Note
Tip
Open Caveats as of March 10, 2009
The following list contains the caveat that was open on March 10, 2009.
CSCsy27340
Component: bps-bat
The need exists for the phone template field in the CSV data file for BAT to be renamed.CSCsv79895
Component: cli
When the user closes the SSH window, CLI terminates and files related to that CLI session are corrupted.CSCsx42403
Component: cmcti
Signaling DSCP from Unified CM is incorrect for CS5, CS6, CS7, EF.CSCsy27594
Component: cmui
User cannot select the standard phone button template by using the Find button.CSCsv08484
Component: database
PMR 34513 CUCM replication error 99 displays.CSCsy07560
Component: directory
DMA does not migrate files with an ICD extension.Documentation Updates
This section provides documentation changes that were unavailable when the Cisco Unified Communications Manager Release 6.1(1x) documentation suite was released.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Cisco Unified Communications Manager Administration Guide
The following sections comprise documentation updates for the Cisco Unified Communications Manager Administration Guide.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Route Plan Report Description Omits Mention of Mobile Voice Access Numbers
The first paragraph of the "Route Plan Report" chapter in the Cisco Unified Communications Manager Administration Guide omits mention of the Mobile Voice Access number as one of the numbers that the route plan report provides. The text that follows replaces the first paragraph of the chapter.
The route plan report lists all of the following types of directory and other numbers in the system:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
The route plan report allows you to view either a partial or full list and to go directly to the associated configuration windows by clicking the entry in the Pattern/Directory Number, Partition, or Route Detail columns of the report.
End User Chapter Includes Incorrect Information for Manager User ID Field
The "End User Configuration" chapter in the Cisco Unified Communications Manager Administration Guide incorrectly describes the Manager User ID field.
Incorrect Description
For the Manager User ID field, enter the user ID of the end user manager ID. The manager user ID that you enter must already exist in the directory as an end user.
Correct Description
For the Manager User ID field, enter the user ID of the end user manager ID.
.Device Pool Chapter Contains Incomplete Description for Device Pool Name Field
The "Device Pool Configuration" chapter in the Cisco Unified Communications Manager Administration Guide does not contain the supported characters that you can enter in the Device Pool Name field. In this field, you can enter alphanumeric characters, period (.), hyphen (-), underscore (_), or a blank space. You can enter up to 50 characters.
Credential Policy Configuration Settings Display Description is Incorrect
The Credential Policy Configuration Settings section of the User Management Chapter of the Cisco Unified Communications Manager Administration Guide contains an incorrect description of the Display field. The correct information follows:
Specify the credential policy name. Enter up to 64 characters, except for quotation marks (""). Do not enter tab.
Incorrect Information Exists in the Meet-Me Number/Pattern Configuration
The Description field in the Meet-Me Number/Pattern Configuration Settings table incorrectly states that you can enter up to 30 alphanumeric characters as a description of the meet-me number/pattern.
The description should state that you can enter up to 50 characters in the description field.
Considerations for LDAP Port Configuration
Tip
When you configure the LDAP Port field in the LDAP Authentication window in Cisco Unified Communications Manager Administration, you specify the port number that the corporate directory uses to receive LDAP requests. How your corporate directory is configured determines which port number to enter in this field. For example, before you configure the LDAP Port field, determine whether your LDAP server acts as a Global Catalog server and whether your configuration requires LDAP over SSL. Consider entering one of the following port numbers:
Tip
LDAP Port For When the LDAP Server Is Not a Global Catalog Server
•
•
LDAP Port For When the LDAP Server Is a Global Catalog Server
•
•
Software Feature License
When you upgrade from any supported release of Cisco Unified Communications Manager to Release 6.1(3x), you must download and install a software feature license to activate the new features. The Cisco Unified Communication Administration Guide indicates that you must install a software feature license only if you are upgrading from 5.x or 6.x releases. You also need a license if you are upgrading from supported 4.x releases. For instructions about how to obtain and install a software feature license, see the "License File Upload" chapter in the Cisco Unified Communications Manager Administration Guide.
Incorrect Description for User ID Field in Application User Window
The "Application User Configuration" chapter in the Cisco Unified Communications Manager Administration Guide incorrectly states that you can enter quotation marks (") in the User ID field in the Application User Configuration window in Cisco Unified Communications Manager Administration. In the User ID field, you can enter the following characters: alphanumeric (a-zA-Z0-9), dash(-), underscore(_), or space( ).
Logging In To the Web Interface When the Firewall Is Disabled
When the firewall is disabled, you must enter the URL of the Cisco Unified Communications Manager server in the following format to log in to the web interface:
https://server:8443/where server specifies the servername or IP address of the server.
Note
Credential Policy Settings
The Credential Policy Configuration Settings (table) in the "Credential Policy" chapter of the Cisco Unified Communications Manager Administration Guide requires the following changes:
•
•
.
You cannot delete the server where you install Cisco Unified Communications Manager Business Edition. Disregard all information on deleting a server in the Cisco Unified Communications Manager Administration Guide for Cisco Unified Communications Manager Business Edition and Cisco Unified Communications Manager System Guide for Cisco Unified Communications Manager Business Edition.
Unclear Documentation on Called Party Name Presentation
The Cisco Unified Communications Manager Administration Guide provides unclear information about called party name presentation.
The Cisco Unified Communications System Guide states that when the Always Display Original Dialed Number service parameter is set to True, the originating phone displays only the dialed digits for the duration of the call. To clarify the documentation, if you set the Cisco CallManager service parameter to True, the name of the called party does not display on the phone of the calling party.
The Cisco Unified Communications Manager Administration Guide does not state that setting the Always Display Original Dialed Number service parameter to True impacts the configuration for the Alerting Name field. If you set the service parameter to True, the alerting name does not display on the calling phone; only the original dialed number displays.
Misleading Documentation About Creating Cisco Unity and Cisco Unity Connection Voice Mailboxes
The Cisco Unified Communications Manager Administration Guide contains misleading information about creating Cisco Unity and Cisco Unity Connection voice mailboxes. Consider the following information when you configure the voice mailboxes:
•
•
Barge Visual Indicator
The "Cisco Unified IP Phone Configuration" chapter in the Cisco Unified Communications Manager Administration Guide incorrectly states that a spinning circle on the phone display indicates that a barge is taking place. Only an audible indicator occurs.
Adding an Administrator User to Cisco Unity or Cisco Unity Connection
The "Application User" chapter of the Cisco Unified Communications Manager Administration Guide incorrectly states that you can use the Create Cisco Unity Application User link in the Related Links drop-down list box to create an application user voice mailbox in Cisco Unity or Cisco Unity Connection. You use this link to add an administrator user to Cisco Unity or Cisco Unity Connection.
1.
Next Steps
If you want to associate devices with this application user, continue with the "Associating Devices to an Application User" procedure.
To manage credentials for this application user, continue with the "Managing Application User Credential Information" procedure.
To add this administrator user to Cisco Unity or Cisco Unity Connection, continue with the procedure in "Adding an Administrator User to Cisco Unity or Cisco Unity Connection" section.
2.
Adding an Administrator User to Cisco Unity or Cisco Unity Connection
The Create Cisco Unity Application User link on the Application Configuration window allows you to add this user as an administrator user to Cisco Unity or Cisco Unity Connection. With this method, you configure the application user in Cisco Unified Communications Manager Administration; then, configure any additional settings for the user in Cisco Unity or Cisco Unity Connection Administration
You can also use the import tool in Cisco Unity or Cisco Unity Connection to import application users as administrative users. To import users, refer to the Cisco Unity or Cisco Unity Connection documentation. (The system does not support the import feature for Cisco Unity Connection 1.1 or 1.2.)
The Create Cisco Unity User link displays only if the Cisco Unity administrator installed and configured the appropriate software. Refer to the applicable Cisco Unified Communications Manager Integration Guide for Cisco Unity or the applicable Cisco Unified Communications Manager SCCP Integration Guide for Cisco Unity Connection.
Before You Begin
Ensure that you have defined an appropriate template for the user that you plan to push to Cisco Unity or Cisco Unity Connection. For Connection users, refer to the applicable User Moves, Adds, and Changes Guide for Cisco Unity Connection. For Cisco Unity users, refer to the Cisco Unity System Administration Guide.
Procedure
Step 1
Step 2
The Add Cisco Unity User dialog box displays.
Step 3
Step 4
Step 5
The administrator account gets created in Cisco Unity or Cisco Unity Connection. The link in Related Links changes to Edit Cisco Unity User in the Application User Configuration window. You can now view the user that you created in Cisco Unity Administration or Cisco Unity Connection Administration.
Note
Note
Documentation Does Not Include the Latest List of Supported Phone Models
The Cisco Unified Communications Manager Administration Guide, Cisco Unified Communications Manager System Guide, and Cisco Unified Communications Manager Features and Services Guide may not contain the latest list of supported Cisco Unified IP Phones. To identify whether the phone supports a feature, refer to the phone documentation that supports this version of Cisco Unified Communications Manager and the phone model.
Upgrade Procedure Contains Incorrect Information
In the Upgrading From Cisco Unified CallManager 4.x Releases section of the Cisco Unified Communications Administration Guide, the procedure indicates that a pop-up window displays when the user chooses an existing license file and chooses the View File button. The license actually displays in the main window after the screen refreshes
Application Server Configuration Not Required for Cisco Unity Connection 2.x
The Cisco Unified Communications Manager Administration Guide suggests that you must configure a Cisco Unity Connection 2.x server in the Application Server Configuration window in Cisco Unified Communications Manager Administration to maintain an association with the Cisco Unity Connection 2.x server. In fact, configuring a Cisco Unity Connection 2.x server in Cisco Unified Communications Manager Administration creates a blank list of user templates for Cisco Unity Connection in Cisco Unified Communications Manager. Instead of configuring the application server in Cisco Unified Communications Manager Administration, create an AXL connection via Unity Connection 2.x, as described in the System Administration Guide for Cisco Unity Connection. Creating the AXL connection via Cisco Unity Connection 2.x pushes a list of valid user templates for Cisco Unity Connection 2.x to Cisco Unified Communications Manager.
Incorrect Documentation on How to Delete Parameter for Phone Service
The Cisco Unified Communications Manager Administration Guide incorrectly states how to delete a service parameter in the IP Phone Services Configuration window in Cisco Unified Communications Manager Administration. To delete a parameter for an IP phone service, click the Delete Parameter button; after the deletion message displays, click OK.
To delete an IP phone service, click the Delete button in the IP Phone Services Configuration window or check the IP phone service check box in the Find and List Phone Services window and click Delete Selected.
Default Device Profile Chapter Incorrectly Includes Expansion Module Settings
The "Default Device Profile" chapter in the Cisco Unified Communications Manager Administration Guide includes descriptions for the following settings, which you cannot configure in the Default Device Profile Configuration window in Cisco Unified CM Administration: Module 1 and Module 2. Ignore these descriptions in this chapter.
Hunt Pilot Chapter Needs Clarification of Maximum Hunt Timer Setting
The "Hunt Pilot Configuration" chapter in the Cisco Unified Communications Manager Administration Guide provides the following description for the Maximum Hunt Timer setting:
Enter a value (in seconds) that specifies the maximum time for hunting. Valid values specify 1 to 3600. The default value specifies 1800 seconds (30 minutes).
This timer cancels if either a hunt member answers the call or if the hunt list gets exhausted before the timer expires. If you do not specify a value for this timer, hunting continues until a hunt member answers or hunting exhausts. If neither event takes place, hunting continues for 30 minutes, after which the call gets taken for final treatment.
Tip
In addition, the description should state that Cisco Unified CM only uses the configuration for the Maximum Hunt Timer setting if you configure the Hunt Forward settings in the Hunt Pilot Configuration window.
Annunciator Chapter Contains Incorrect Information on Description Field
The "Annunciator Configuration" chapter in the Cisco Unified Communications Manager Administration Guide states that you can configure up to 54 characters in the Description field. Actually, you can configure up to 128 characters.
Gateway Configuration Chapter Contains Incorrect Information on Domain Name Field
The "Gateway Configuration" chapter in the Cisco Unified Communications Manager Administration Guide incorrectly states that you can enter 50 characters in the Domain Name field in the MGCP gateway configuration window. Actually, you can enter up to 64 characters in the Domain Name field for MGCP gateways.
AAR Group Chapter Includes Incorrect Description for Dial Prefix Field
The "Automated Alternate Routing Group Configuration" chapter in the Cisco Unified Communications Manager Administration Guide includes incorrect entries for the Dial Prefix field.
Incorrect Information
Dial Prefix field—Enter the prefix characters and symbols to use for automated alternate routing within this AAR group. Valid entries include the following digits: [ ^ 0 1 2 3 4 5 6 7 8 9 - ] + ? ! X * # . @
Correct Information
Dial Prefix field—Enter the prefix digits to use for automated alternate routing within this AAR group. Valid entries include numeric characters (0-9), alpha characters (A-D), asterisk (*), and pound (#).
Dual Phone Mode Support
The "Cisco Unified IP Phone Configuration" chapter of the Cisco Unified Communications Manager Administration Guide omitted this information.
To support Mobile Connect and Mobile Voice Access for dual-mode phones, the following field displays on the Phone Configuration window:
Mobility User ID (dual-mode phones only) - From the drop-down list box, choose the user ID of the person to whom this dual-mode phone is assigned.
Note
Generating a License File from DMA
The "License File Upload" chapter of the Cisco Unified Communications Manager Administration Guide for Release 6.1(3x) does not describe that there is an alternate method to obtain a product license. In this method, the user generates the product license from Data Migration Assistant (DMA). Data Migration Assistant User Guide Release 6.1(3x) describes how to use this method to generate the file.
Upgrading to Cisco Unified Communications Manager Release 6.1(3) from Cisco Unified Communications Manager 4.x Releases describes how to upload the file to Cisco Unified Communications Manager Release 6.1(3x).
Uploading a License File
The Uploading a License File section of the Cisco Unified Communications Manager Administration Guide does not instruct administrators to restart the Cisco CallManager service after uploading the license file. Administrators must restart the service for the license changes to take effect.
Enterprise Parameters and Service Parameters Chapters Omit Information on Set to Default Button
The "Enterprise Parameters Configuration" and the "Service Parameters Configuration" chapters in the Cisco Unified Communications Manager Administration Guide do not contain information on the Set to Default button. Clicking the Set to Default button in either the Enterprise Parameters Configuration window or Service Parameter Configuration window updates all parameters to the suggested value, which is the default that displays on the right side of the parameter. If a parameter does not have a suggested value, Cisco Unified CM does not update the value when you click the Set to Default button; for example, the Phone URL Parameters in the Enterprise Parameters Configuration window do not display a suggested value, so clicking the Set to Default button does not change the parameter that you configured.
A warning message displays after you click the Set to Default button. If you click OK in the dialog box, Cisco Unified CM updates all parameters in the configuration window to the suggested value; that is, if the parameter has a suggested value.
Information About Using an SRV Destination Port for the CUP Publish Trunk Service Parameter
The "Service Parameters Configuration" chapter in the Cisco Unified Communications Manager Administration Guide omits the following information.
You can configure a SIP trunk to use a DNS SRV port on a Cisco Unified Presenceserver as a destination. If you use a SIP trunk with a DNS SRV destination to configure the CUP Publish Trunk service parameter and then modify the DNS record, you must restart all devices (phones) that previously published, so they point to the correct Cisco Unified Presenceserver destination.
To configure the CUP Publish Trunk parameter, navigate to System Service Parameters and choose Cisco CallManager service for the server that you want to configure.
For an overview of configuring Cisco Unified Presence with Cisco Unified CM, see "Cisco Unified Communications Manager and Cisco Unified Presence High-Level Architecture Overview" in the Cisco Unified Communications Manager System Guide.
Information About Changing Region Bandwidth Settings When Video Calls Are Made
The following informational reference will get added to the Cisco Unified Communications Manager administration documentation:
Refer to the "Regions" subtopic under the "Administration Considerations" topic of the "IP Video Telephony" chapter of the Cisco Unified Communications Solution Reference Network Design (SRND) for the current release, which provides recommendations as to how the video bandwidth should be set for regions and locations, so the video portion of video calls will succeed, and the video calls will not get rejected nor set up as audio-only calls.
The reference will get added to the following topics of the Cisco Unified CM Administration documentation:
•
chapter: Location Configuration
topic: list of restrictions at the beginning of the chapter•
chapter: Region Configuration
topic: list of limitations and restrictions at the beginning of the chapterInformation Omitted for Reroute Incoming Request to New Trunk Based on Setting
Instead of using the information for the Reroute Incoming Request to New Trunk Based on Setting in the "SIP Profile Configuration" chapter in the Cisco Unified Communications Manager Administration Guide/online help, use the following information when you configure the Reroute Incoming Request to New Trunk Based on Setting in the SIP Profile Configuration window in Cisco Unified Communications Manager Administration.
Cisco Unified Communications Manager only accepts calls from the SIP device whose IP address matches the destination address of the configured SIP trunk. In addition, the port on which the SIP message arrives must match the one that is configured on the SIP trunk. After Cisco Unified Communications Manager accepts the call, Cisco Unified Communications Manager uses the configuration for this setting to determine whether the call should get rerouted to another trunk.
From the drop-down list box, choose the method that Cisco Unified Communications Manager uses to identify the SIP trunk where the call gets rerouted:
•
•
•
Tip
Do Not Begin Starting and Ending Directory Numbers with a Zero (0)
In Table 3 of the "Cisco Unified Communications Manager Configuration" chapter, under Auto-registration Information, the descriptions of Starting Directory Number and Ending Directory Number omit the information that neither number should begin with a zero (0).
Time-of-Day Routing Chapter Omits Information About Defined Time Periods
The "Time-of-Day Routing" chapter of the Cisco Unified Communications Manager System Guide omits the following information.
•
Example:
Consider the following example:
•
•
In this case, on December 31st, the afterofficehours period will not be considered because it gets overriden by the more specific newyearseve period.
Cisco Unified Communications Manager System Guide
The following sections comprise documentation updates for the Cisco Unified Communications Manager System Guide.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
RSVP Reservation Teardown for Shared-Line Calls
The Cisco Unified Communications Manager System Guide incorrectly documents the teardown of RSVP reservations that takes place when a shared-line call gets answered. The RSVP and Shared-Line Calls section of the "Resource Reservation Protocol" chapter provides an example that includes the following erroneous statement to describe the reservation teardown:
After phone B2 (in location 3) answers the shared-line call, the RSVP reservation between location 1 and location 3, as well as the reservation between location 1 and location 4, get torn down.
The correct information follows:
After phone B2 (in location 3) answers the shared-line call, the RSVP reservation between location 1 and location 2, as well as the reservation between location 1 and location 4, get torn down. Only the RSVP reservation between location 1 and location 3 remains established.
Considerations for LDAP Port Configuration
Tip
When you configure the LDAP Port field in the LDAP Authentication window in Cisco Unified Communications Manager Administration, you specify the port number that the corporate directory uses to receive LDAP requests. How your corporate directory is configured determines which port number to enter in this field. For example, before you configure the LDAP Port field, determine whether your LDAP server acts as a Global Catalog server and whether your configuration requires LDAP over SSL. Consider entering one of the following port numbers:
Tip
LDAP Port For When the LDAP Server Is Not a Global Catalog Server
•
•
LDAP Port For When the LDAP Server Is a Global Catalog Server
•
•
RSVP Reservation Teardown for Shared-Line Calls
The Cisco Unified Communications Manager System Guide incorrectly documents the teardown of RSVP reservations that takes place when a shared-line call gets answered. The RSVP and Shared-Line Calls section of the "Resource Reservation Protocol" chapter provides an example that includes the following erroneous statement to describe the reservation teardown:
After phone B2 (in location 3) answers the shared-line call, the RSVP reservation between location 1 and location 3, as well as the reservation between location 1 and location 4, get torn down.
The correct information follows:
After phone B2 (in location 3) answers the shared-line call, the RSVP reservation between location 1 and location 2, as well as the reservation between location 1 and location 4, get torn down. Only the RSVP reservation between location 1 and location 3 remains established.
Application Server Configuration Not Required for Cisco Unity Connection 2.x
The Cisco Unified Communications Manager System Guide suggests that you must configure a Cisco Unity Connection 2.x server in the Application Server Configuration window in Cisco Unified Communications Manager Administration to maintain an association with the Cisco Unity Connection 2.x server. In fact, configuring a Cisco Unity Connection 2.x server in Cisco Unified Communications Manager Administration creates a blank list of user templates for Cisco Unity Connection in Cisco Unified Communications Manager. Instead of configuring the application server in Cisco Unified Communications Manager Administration, create an AXL connection via Unity Connection 2.x, as described in the System Administration Guide for Cisco Unity Connection. Creating the AXL connection via Cisco Unity Connection 2.x pushes a list of valid user templates for Cisco Unity Connection 2.x to Cisco Unified Communications Manager.
Unclear Documentation on Called Party Name Presentation
The Cisco Unified Communications Manager System Guide provides unclear information about called party name presentation.
The Cisco Unified Communications System Guide states that when the Always Display Original Dialed Number service parameter is set to True, the originating phone displays only the dialed digits for the duration of the call. To clarify the documentation, if you set the Cisco CallManager service parameter to True, the name of the called party does not display on the phone of the calling party.
The Cisco Unified Communications Manager Administration Guide does not state that setting the Always Display Original Dialed Number service parameter to True impacts the configuration for the Alerting Name field. If you set the service parameter to True, the alerting name does not display on the calling phone; only the original dialed number displays.
Automated Alternate Routing (AAR) Limitation with Remote Gateways
AAR exhibits the limitation that calls that are routed over a remote gateway during a high-bandwidth situation fail, and the calls cannot be routed over the local gateway when AAR is used. This functionality proves to be important to customers who use Tail-End Hop Off (TEHO) for toll bypass.
Workaround Example
Use a specific partition for the TEHO in question.
In the following example, headquarters (HQ) has area code 408 and the Branch (BR1) has area code 919.
Configure as follows:
1.
2.
3.
4.
5.
6.
Results
In an out-of-bandwidth situation, after Cisco Unified Communications Manager tries to allocate the first route group for TEHO (BR1 route group), Cisco Unified CM retries the second route group, at which point the system strips the 91919 string and replaces it with the 1919 string, which is suitable for long-distance dialing. Because the string is configured for use by the local gateway, less rerouting takes place.
AAR works on a per-external-phone-number-mask basis and cannot be processed for an external PSTN number because the system does not know the phone number mask of the PSTN number. This workaround provides AAR functionality and improves network resiliency.
Documentation Does Not State That Line Group With No Members Is Not Supported for Routing Calls
The Cisco Unified Communications Manager documentation does not state that you can configure an empty line group with no members (directory numbers) in Cisco Unified Communications Manager Administration. Although you can configure an empty line group with no members, Cisco Unified Communications Manager does not support this configuration for routing calls. If the line group contains no members, the hunt list stops hunting when the call gets routed to the empty line group. To avoid this situation, make sure that you configure at least one member in the line group.
Peer-to-Peer Image Distribution
Use the following information from the Cisco Unified Communications Manager System Guide, "Cisco Unified IP Phones" chapter, to replace the first paragraph of the Peer to Peer Image Distribution section.
The Peer Firmware Sharing feature provides these advantages in high-speed campus LAN settings:
•
•
•
In most conditions, the Peer Firmware Sharing feature optimizes firmware upgrades in branch deployment scenarios over bandwidth-limited WAN links.
When the feature is enabled, it allows the phone to discover like phones on the subnet that are requesting the files that make up the firmware image and to automatically assemble transfer hierarchies on a per-file basis. The individual files that make up the firmware image get retrieved from the TFTP server by only the root phone in the hierarchy and are then rapidly transferred down the transfer hierarchy to the other phones on the subnet using TCP connections.
For more information, see the applicable Cisco Unified IP Phone administration guide.
Recommended Number of Devices in Device Pool
The following information from the Cisco Unified Communications Manager System Guide, "Redundancy" chapter, needs clarification.
You associate devices with a Cisco Unified Communications Manager group by using device pools. You can assign each device to one device pool and associate each device pool with one Cisco Unified Communications Manager group. You can combine the groups and device pools in various ways to achieve the desired level of redundancy.
Note
Throttling on SIP UDP Ports
The "SIP and Cisco Unified Communications Manager" chapter in the Cisco Unified Communications Manager System Guide requires this update for SIP UDP port throttling.
SIP UDP port throttle thresholds help prevent Denial of Service (DOS) attacks from SIP trunks and SIP stations. When the incoming packet rate exceeds the configured threshold for a SIP station or SIP trunk UDP port, Cisco Unified Communications Manager throttles (drops) the packets that exceed the threshold.
The SIP Service Parameters section of this chapter does not include the following parameters for SIP UDP throttling.
SIP UDP Port Throttling Thresholds
These throttle thresholds apply only to SIP UDP ports and do not affect SIP TCP or TLS ports.
Tip
Table 8 describes the configurable threshold values:
The Incoming Port description in Table 15-1 in the Cisco Unified Communications Manager Security Guide requires this addition for SIP UDP Port Throttling:
Tip
Call Admission Control Bandwidth Example Correction
The "Call Admission Control" chapter of the Cisco Unified Communications Manager System Guide incorrectly describes the amount of bandwidth that is consumed in an example locations-type call admission control scenario.
Original explanation:
Cisco Unified Communications Manager continues to admit new calls to a link as long as sufficient bandwidth is still available. Thus, if the link to the Austin location in the example has 160 kb/s of available bandwidth, that link can support one G.711 call at 80 kb/s (in each direction), three G.723 or G.729 calls at 24 kb/s each (in each direction), or two GSM calls at 29 kb/s each (in each direction). If any additional calls try to exceed the bandwidth limit, the system rejects them, the calling party receives reorder tone, and a text message displays on the phone.
Correct explanation:
Cisco Unified Communications Manager continues to admit new calls to a link as long as sufficient bandwidth is still available. Thus, if the link to the Austin location in the example has 160 kb/s of available bandwidth, that link can support two G.711 calls at 80 kb/s each, six G.723 or G.729 calls at 24 kb/s each, or five GSM calls at 29 kb/s each. If any additional calls try to exceed the bandwidth limit, the system rejects them, the calling party receives reorder tone, and a text message displays on the phone
Directory Numbers Chapter Includes Incorrect Example for Shared Lines and Call Forward Busy Trigger
The "Understanding Directory Numbers" chapter in the Cisco Unified Communications Manager System Guide includes incorrect example for shared lines and call forward busy trigger. Use the following information instead of the information in the guide:
Devices with shared-line appearance support the Call Forward Busy Trigger and the Maximum Number of Calls settings. You can configure Call Forward Busy Trigger per line appearance, but the configuration cannot exceed the maximum number call setting for that directory number.
The following example demonstrates how three Cisco Unified IP Phones with the same shared-line appearance, directory number 2000, use Call Forward Busy Trigger and Maximum Number of Calls settings. This example assumes that two calls occur. The following values configuration applies for the devices:
•
•
•
When Cisco Unified IP Phone User 1 dials directory number 2000 for the first call, all three devices ring. The user for Cisco Unified IP Phone 3 picks up the call, and Cisco Unified IP Phones 1 and 2 go to remote in use. When the user for Cisco Unified IP Phone 3 puts the call on hold, user can retrieve the call from the Cisco Unified IP Phone 1 or Cisco Unified IP Phone 2. When User 2 dials directory number 2000 for the second call, only Cisco Unified IP Phone 3 rings.
Licensing Chapter Omits Information on Adjunct Licensing
The "Licensing" chapter in the Cisco Unified Communications Manager System Guide omits the fact that an error occurs when you configure an application, for example, Cisco IP Communicator, as the adjunct device, and the adjunct device requires more device license units (DLUs) than the primary device; for example, the Cisco Unified IP Phone 7906.
With adjunct licensing, fewer device license units (DLUs) get consumed for adjunct (secondary) devices, such as Cisco IP Communicator, Cisco Unified Personal Communicator, and Cisco Unified Mobile Communicator, when these applications get used with a Cisco Unified IP Phone 79xx, which serves as the primary device. For adjunct licensing to work, the adjunct device must consume fewer or the same number of DLUs as the primary device.
For example, if you configure Cisco IP Communicator as a secondary device for the Cisco Unified IP Phone 7970, Cisco IP Communicator consumes only 1 DLU. Adjunct licensing works because the Cisco Unified IP Phone 7970 consumes 5 DLUs, and Cisco IP Communicator consumes 3 DLUs.
In another example, if you configure Cisco IP Communicator as a secondary device for the Cisco Unified IP Phone 7906, adjunct licensing fails because the Cisco Unified IP Phone 7906 consumes 2 DLUs, and Cisco IP Communicator consumes 3 DLUs.
To ensure that Cisco Unified Communications Manager treats Cisco IP Communicator, Cisco Unified Personal Communicator, and Cisco Unified Mobile Communicator as adjunct (secondary) devices, configure the Primary Phone setting in the Phone Configuration window for Cisco IP Communicator, Cisco Unified Personal Communicator, and Cisco Unified Mobile Communicator, as described in the "Phone Configuration" chapter in the Cisco Unified Communications Manager Administration Guide.
Cisco TFTP Chapter Omits Configuration Tip on Centralized TFTP
The "Cisco TFTP" chapter in the Cisco Unified Communications Manager System Guide does not contain the following information on configuring centralized TFTP:
For centralized TFTP configurations, ensure that the main TFTP server exists in the cluster that runs the highest version of Cisco Unified Communications Manager; for example, if you are using a centralized TFTP server between a compatible Cisco Unified CallManager 4.X cluster and a Cisco Unified Communications Manager 6.X cluster, ensure that your main TFTP server exists in the Cisco Unified Communications Manager 6.X cluster. If the main TFTP server exists in the cluster that runs the lower version of Cisco Unified Communications Manager, the phones use the locale files from the lower version of Cisco Unified Communications Manager, which can cause issues with the phone; for example, the phone displays Undefined or ??? for the Do Not Disturb feature instead of displaying that DND is active. These errors display on the phone because the locale files that are served to the phones from the main cluster do not include the localized phrases.
Information About Changing Region Bandwidth Settings When Video Calls Are Made
The following informational reference will get added to the Cisco Unified Communications Manager administration documentation:
Refer to the Regions subtopic under the Administration Considerations topic of the "IP Video Telephony" chapter of the Cisco Unified Communications Solution Reference Network Design (SRND) for the current release, which provides recommendations as to how the video bandwidth should be set for regions and locations, so the video portion of video calls will succeed, and the video calls will not get rejected nor set up as audio-only calls.
The reference will get added to the following topics of the Cisco Unified CM Administration documentation:
•
chapter: Understanding Video Telephony
topic: Bandwidth Management•
chapter: Call Admission Control
topic: Bandwidth CalculationsTrunk Chapter Omits Restrictions for H.323/H.225 Trunks
The "Understanding Cisco Unified Communications Manager Trunks Types" chapter in the Cisco Unified Communications Manager System Guide does not contain the following restriction for H.323/H.225 trunks.
You cannot configure more than one H.323 trunk of any type (gatekeeper- or non-gatekeeper-controlled) between the same clusters. Configuring more than one H.323 trunk can break inbound calls because Cisco Unified Communications Manager uses the received IP address to choose which trunk handles the call. If you configure more than one H.323 trunk between the same clusters, Cisco Unified Communications Manager may choose the wrong trunk device when a call gets processed. To avoid this issue, Cisco Unified Communications Manager checks the following configuration:
•
•
If you configure one trunk with an IP address, and you configure another trunk with a hostname that resolves to the same IP address, Cisco Unified Communications Manager does not detect this configuration, which causes duplicate trunk configuration and problems with call processing.
Cisco Unified Communications Manager cannot detect the configuration of a gatekeeper-controlled trunk and a non-gatekeeper-controlled trunk or the configuration of multiple gatekeeper-controlled trunks between the same Cisco Unified Communications Manager clusters. Additionally, Cisco Unified Communications Manager cannot detect the configuration of a gatekeeper-controlled H.323 trunk with the configuration of an H.323 gateway that is accessible from that same gatekeeper-controlled H.323 trunk. These configurations can cause problems for call processing, so carefully configure your trunks in Cisco Unified Communications Manager to avoid these issues.
Information About Changing Region Bandwidth Settings When Video Calls Are Made
The following informational reference will get added to the Cisco Unified Communications Manager administration documentation:
Refer to the Regions subtopic under the Administration Considerations topic of the "IP Video Telephony" chapter of the Cisco Unified Communications Solution Reference Network Design (SRND) for the current release, which provides recommendations as to how the video bandwidth should be set for regions and locations, so the video portion of video calls will succeed, and the video calls will not get rejected nor set up as audio-only calls.
The reference will get added to the following topics of the Cisco Unified CM Administration documentation:
•
chapter: Understanding Video Telephony
topic: Bandwidth Management•
chapter: Call Admission Control
topic: Bandwidth CalculationsCisco Unified Communications Manager Features and Services Guide
The following sections comprise documentation updates for the Cisco Unified Communications Manager Features and Services Guide.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
CTI and Attendant Console Chapters Omit Information on CTI Monitored Lines
To calculate the number of CTI monitored lines in a system, use the following formula:
number of pilot point DNs + (number of clients open * number of directory numbers per phone) + (number of parked directory numbers * number of open clients) = CTI Monitored Lines
Incorrect Information on How to Install Assistant Console Application
The Cisco Unified Communications Manager Features and Services Guide incorrectly describes how to obtain the assistant console application for Cisco Unified Communications Manager Assistant. In release 6.1(1a), the assistant no longer obtains the assistant console application via the URL that is listed in the guide. Instead, the assistant must download the Cisco Unified Communications Manager Assistant plug-in from Cisco Unified Communications Manager Administration (choose Applications > Plugins), as described in the "Cisco Unified Communications Manager Assistant User Guide" section.
The Cisco Unified Communications Manager Features and Services Guide does not state that the assistant console application supports Windows Vista.
Disregard the entire Assistant Console Dialog Options section in the Cisco Unified Communications Manager Features and Services Guide. Instead, use the information in the "Cisco Unified Communications Manager Assistant User Guide" section.
Do Not Disturb Feature Priority
On Cisco Unified IP Phones, the text message that indicates the Do Not Disturb (DND) feature is active takes priority over the text message that indicates the user has new voicemail messages, which allows the user to know when DND is active. However, the text message that indicates the Call Forward All feature is active has a higher priority than DND.
Extension Mobility Successful Authentication Cache
The Extension Mobility application maintains a cache of all logged on user information for 2 minutes. If a request comes to extension mobility regarding a user who is represented in the cache, the user gets validated with information from the cache. This means that, if a user changes the password, logs out, and then logs back in within 2 minutes, both the old and new passwords get recognized.
Devices Associated with the Attendant Console Application User
You must always enable the superprovider feature by associating the ac application user with the user group "Standard CTI Allow Control of All Devices" and must not associate any devices with the Cisco Unified Communications Manager Attendant Console ac application user.
Caution
CTI Devices Do Not Support Multicast Music on Hold (MOH)
CTI devices do not support the multicast Music on Hold feature. If a CTI device is configured with a multicast MOH device in the media resource group list of the CTI device, call control issues may result. CTI devices do not support multicast media streaming.
Attendant Console Phones Do Not Support the Intercom Feature
The Cisco Unified Communications Manager Attendant Console does not support the intercom feature. The attendant console GUI shows intercom and other lines but does not display the hunt group member line when the intercom feature is configured on a phone that is a member of a hunt group.
Unclear Documentation on How Locales Work for Mobile Voice Access
The Cisco Unified Communications Manager Features and Services Guide does not address how locales work for mobile voice access. Mobile voice access uses the first locale that displays in the Selected Locales pane in the Mobile Voice Access window in Cisco Unified Communications Manager Administration (Media Resources > Mobile Voice Access) when the IVR is used. For example, if English United States displays first in the Selected Locales pane, the Cisco Unified Mobility user receives English when the IVR is used during a call.
Mobile Connect and Mobile Voice Access Chapter Omits Information About Configuring the Mobile Voice Access Media Resource
The "Mobile Connect and Mobile Voice Access" chapter in the Cisco Unified Communications Manager Features and Services Guide omits the following information about configuring the mobile voice access media resource:
Be aware that this configuration is required for making calls with the Mobile Voice Access feature. After the gateway collects the required digits from the user to make a call, the call gets transferred to the DN that is configured in this window. This DN can represent an internal DN to Cisco Unified Communications Manager, and the end user does not need to know the DN. The administrator must configure a dial-peer, so the MVA service can transfer the call from the gateway to this DN. Also, ensure this DN is placed in a partition where the inbound calling search space (CSS) of the gateway or the remote destination profile CSS can reach the DN, as configured in the Inbound Calling Search Space for Remote Destination service parameter in the Clusterwide Parameters (System - Mobility) pane.
cBarge Chapter Omits Information on Shared Line Restriction for Conferences
The "Barge and Privacy" chapter in the Cisco Unified Communications Manager Features and Services Guide does not contain the following cBarge restriction for shared lines and conferences:
If the number of shared-line users in the conference is equal to or greater than the configuration for the Maximum Number of Calls setting for the device from which you are attempting to barge, the phone displays the message, Error Past Limit.
Note
Cisco Unified IP Phones Supporting Call Back with PLKs
The "Call Back" chapter of the Cisco Unified Communications Manager Features and Services Guide omits the following information:
Many Cisco Unified IP Phone support the Cisco Call Back feature by using the programmable line key (PLK). The following URL lists the phone documentation that is available for the various Cisco Unified IP Phones:
http://www.cisco.com/en/US/products/hw/phones/ps379/tsd_products_support_series_home.html
Intercom Configuration
The "Intercom" chapter in the Cisco Unified Communications Manager Features and Services Guide omits the following steps that should be taken to successfully install the intercom feature.
Procedure
Step 1
a.
Note
b.
Note
Step 2
Note
Step 3
Step 4
Note
Where to Find More Information
•
•
•
•
•
Extension Mobility Redundancy
The "Extension Mobility" chapter in the Cisco Unified Communications Manager Features and Services Guide omits the following statement:
For information on extension mobility redundancy, see the "Cisco Unified Communications Manager Applications" chapter of the latest Cisco Unified Communications SRND that is located at http://www.cisco.com/go/srnd.
Number of Login or Logout Operations That Cisco Extension Mobility Supports
The Cisco Unified Communications Manager Features and Services Guide omits the maximum number of login or logout operations that Cisco Extension Mobility supports for Cisco Unified Communications Manager Release 6.1(1a). The correct guideline follows:
Cisco Extension Mobility supports a maximum of 250 login or logout operations per minute (or 15,000 operations per hour). Remember that these operations are sequential, not concurrent. (Some devices may support more login or logout operations per hour.)
None Option Not Documented for DND Incoming Call Alert Setting
The Cisco Unified Communications Manager Administration Guide and Cisco Unified Communications Manager Features and Services Guide ("Do Not Disturb" chapter) do not describe the None option that displays in the DND Incoming Call Alert drop-down list box.
Tip
The following information describes the DND Incoming Call Alert drop-down list box:
When you enable the DND Ringer Off option, this parameter specifies how a call displays on a phone. From the drop-down list, choose one of the following options:
•
•
•
•
Mobile Connect and Mobile Voice Access Chapter Contains Incorrect Information About Configuring an H.323 Gateway for System Remote Access by Using Hairpinning
In the "Mobile Connect and Mobile Voice Access" chapter in the Cisco Unified Communications Manager Features and Services Guide, the procedure for configuring an H.323 gateway for system remote access by using hairpinning contains minor errors. The following procedure contains the corrected steps.
Procedure
Step 1
Sample configuration for IOS Version 12.3 (13) and later
•
•
Sample configuration before IOS Version 12.3(12)
•
•
Note
Step 2
Sample configuration for IOS 12.3(13) and later
•
•
•
•
•
Sample configuration for IOS 12.3(12) and earlier
•
•
•
•
•
Step 3
Sample configuration for primary Cisco Communications Manager
•
•
•
Note
•
•
•
•
•
Sample configuration for secondary Cisco Communications Manager (if needed):
•
•
•
Note
•
•
•
•
•
Step 4
•
•
Mobile Connect and Mobile Voice Access Chapter Contains Incorrect Information About Configuring an H.323 Gateway for System Remote Access by Using PRI
In the "Mobile Connect and Mobile Voice Access" chapter in the Cisco Unified Communications Manager Features and Services Guide, the procedure for configuring an H.323 gateway for system remote access by using PRI contains minor errors. The following procedure contains the corrected steps.
Procedure
Step 1
Sample configuration
•
•
•
•
Step 2
Sample configuration
•
•
•
•
•
•
•
Step 3
Sample configuration for IOS Version 12.3 (13) and later
•
•
Sample configuration before IOS Version 12.3(12)
•
•
Note
Step 4
Sample configuration for IOS 12.3(13) and later
•
•
•
•
Sample configuration for IOS 12.3(12) and earlier
•
•
•
•
Step 5
Sample configuration for primary Cisco Unified Communications Manager
•
•
•
Note
•
•
•
•
Sample configuration for secondary Cisco Unified Communications Manager (if needed)
•
•
•
Note
•
•
•
•
Cisco Extension Mobility Chapter Error
The "Cisco Extension Mobility" chapter in the Cisco Unified Communications Manager Features and Services Guide states that you can configure the Module 1 and Module 2 drop-down list boxes in the Default Device Profile Configuration window, which is not true.
Barge and Security
The Restrictions section of the "Barge and Privacy" chapter in the Cisco Unified Communications Manager Features and Services Guide misstates the capabilities of encrypted phones to accept barge requests from unencrypted phones or from calls with a lower security level in Cisco Unified Communications Manager Release 6.1(1a).
The correct information follows:
Any phone can barge in to any existing call regardless of security level. An icon on the phone indicates the lowest security level of all participants:
•
•
•
Barge with Shared Conference Bridge
The "Barge and Privacy" chapter in the Cisco Unified Communications Manager Features and Services Guide does not correctly describe the process for configuration of the Barge with Shared Conference Bridge feature. The Standard User and Standard Feature softkey templates do not support cBarge and cannot be modified. The following corrections apply to the Barge with Shared Conference Bridge (cBarge) Configuration Checklist (table).
Replace Step 1 with the following information:
To create a softkey template that includes cBarge, make a copy of the Standard Feature softkey template. Modify this user-named copy to add the Conference Barge (cBarge) softkey to the Selected Softkeys in the Remote in Use call state. See the Adding Non-Standard Softkey Templates section in the "Device Configuration" chapter of the Cisco Unified Communications Manager Administration Guide for more information on creating copies of standard softkey templates.
After Step 3, insert the following sentence:
Disable privacy on phones to allow cBarge.
Number of Alphanumeric Characters That Are Allowed in the Pickup Group Name Field
The Cisco Unified Communications Manager Features and Services Guide incorrectly states that you can enter up to 30 alphanumeric characters in the Pickup Group Name field in the Call Pickup Group Configuration window. The guide should state that you can enter up to 100 characters in the Pickup Group Name field.
Documentation Does Not Include the Latest List of Supported Phone Models
The Cisco Unified Communications Manager Features and Services Guide may not contain the latest list of supported Cisco Unified IP Phones. To identify whether the phone supports a feature, refer to the phone documentation that supports this version of Cisco Unified Communications Manager and the phone model.
Do Not Disturb Documentation Provides Incorrect Information About Phone Tone
The "Do Not Disturb" chapter in the Cisco Unified Communications Manager Features and Services Guide states that the phone periodically plays a tone to remind you that DND is active. The phone does not play a tone to remind you that DND is active. Instead, the status on the phone displays Do Not Disturb is active.
Destination Number in Remote Destination Configuration Window
The "Mobile Connect and Mobile Voice Access" chapter of the Cisco Unified Communications Manager Features and Services Guide incorrectly documents the Destination Number field of the Remote Destination Configuration window. In the Remote Destination Configuration Settings section, the following statements in the Destination Number description require correction:
•
•
•
Cisco Extension Mobility Supplemental Information
Consider the following information as supplementary to the information that is provided in the "Cisco Extension Mobility" chapter of the Cisco Unified Communications Manager Features and Services Guide:
When you subscribe devices to the Extension Mobility IP Phone Service (Device > Device Settings > Phone Services), an error results if you click Update Subscriptions more than once. When you update many phones, it can take some time for the changes to propagate to all devices. You must click Update Subscriptions only once and wait for this propagation to complete.
Cisco Unified IP Phones Supporting Barge
Replace the following out-of-date statement in the "Barge and Privacy" chapter of the Cisco Unified Communications Manager Features and Services Guide:
Original statement:
Some Cisco Unified IP Phones (such as 7940 and 7960) have the built-in conference bridge capability, which barge uses.
Updated information:
Most Cisco Unified IP Phones include the built-in conference bridge capability, which barge uses.
Cisco Unified IP Phones Supporting Call Back
The Interactions and Restrictions section in the "Cisco Call Back" chapter of the Cisco Unified Communications Manager Features and Services Guide did not get updated with regard to the specific Cisco Unified Communications Manager IP Phones that support Cisco Call Back.
The following URL lists the phone documentation that is available for the various Cisco Unified IP Phones:
http://www.cisco.com/en/US/products/hw/phones/ps379/tsd_products_support_series_home.html
To check which phones support Cisco Call Back, refer to the phone administration guide that supports the phone and refer to the Telephony Features for the Cisco Unified IP Phone table.
To check which phones also support Cisco Call Back with PLKs, refer to the phone user guide that supports the phone and refer to the Understanding Feature Availability section.
Cisco Unified Communications Manager Security Guide
The following sections comprise documentation updates for the Cisco Unified Communications Manager Security Guide.
•
•
•
•
Support for Certificates from External CAs
This section in the "Security Overview" chapter of the Cisco Unified Communications Manager Security Guide updates the existing sentence to include IPSec and Tomcat, as follows: Customers who currently use third-party CAs should use the CSR mechanism to issue certificates for Communications Manager, CAPF, IPSec, and Tomcat.
CAPF System Interactions and Requirements
This section in the "Using the Certificate Authority Proxy Function" chapter of the Cisco Unified Communications Manager Security Guide requires this new item:
If a secure phone gets moved to another Cisco Unified Communications Manager server, the Cisco Unified Communications Manager will not trust the LSC certificate that the phone sends because it was issued by another CAPF whose certificate is not in the CTL file. To enable the secure phone to register, delete the existing CTL file by using the "Deleting the CTL File on the Cisco Unified IP Phone" procedure in the Cisco Unified Communications Manager Security Guide. You can then use the Upgrade/Install option to install a new LSC certificate with the new CAPF and reset the phone for the new CTL file (or use the MIC). Use the Delete option in the CAPF section on the Phone Configuration window to delete the existing LSC before the phones are moved.
Security Icons and Encryption
Reviewers, is the information below correct for Co-Res?
This subsection of the Restrictions section in the "Security Overview" chapter in the Cisco Unified Communications Manager Security Guide requires this addition:
If a call from an encrypted phone over a SIP trunk gets transferred back to an encrypted phone that is configured on the same server as the phone that transferred the call, the call does not get encrypted, and the lock icon does not display even though the encrypted phones are configured on the same server.
Software Conference Bridge Not Supported
The "Configuring Secure Conference Resources" chapter in the Cisco Unified Communications Manager Security Guide requires this addition: Due to the performance impact to Cisco Unified Communications Manager processing, secure conferencing does not get supported on software conference bridge.
Cisco Unified Communications Manager XML Developers Guide for Release 6.0(1)
The information in Cisco Unified Communications Manager XML Developers Guide for Release 6.0(1) applies to Release 6.1(1a), with the following updates:
•
POST /axl/ HTTP/1.0Host:10.77.31.194:8443Authorization: Basic Q0NNQWRtaW5pc3RyYXRvcjpjaXNjb19jaXNjbw==Accept: text/*Content-type: text/xmlSOAPAction: "CUCM:DB ver=6.1"Content-length: 427<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xmlns:xsd="http://www.w3.org/2001/XMLSchema"><SOAP-ENV:Body><axl:getUser xmlns:axl=http://www.cisco.com/AXL/API/6.1xsi:schemaLocation="http://www.cisco.com/AXL/API/6.1 http://ccmserver/schema/axlsoap.xsd"sequence="1234"> <userid>tttt</userid> </axl:getUser></SOAP-ENV:Body></SOAP-ENV:Envelope>•
HTTP/1.1 200 OKServer: Apache-Coyote/1.1Set-Cookie: JSESSIONIDSSO=950805DE5E10F32C5788AE164EEC4955; Path=/Set-Cookie: JSESSIONID=151CF94ACF20728B1D47CC5C3BECC401; Path=/axl; SecureSOAPAction: "CUCM:DB ver=6.1"Content-Type: text/xml;charset=utf-8Content-Length: 728Date: Mon, 22 Jan 2007 06:51:42 GMTConnection: closeCisco Unified Serviceability Administration Guide
The following sections comprise documentation updates for the Cisco Unified Serviceability Administration Guide.
•
•
•
DNS Required for RTMT Alerts by E-mail
The Cisco Unified Serviceability Administration Guide does not explain that to configure RTMT to send alerts via e-mail, you must configure DNS. For information on configuring the primary and secondary DNS IP addresses and the domain name in Cisco Unified Communications Manager Server Configuration, see the "DHCP Server Configuration" chapter in the Cisco Unified Communications Manager Administration Guide.
Warning Displays When SIP Stack Trace Is Enabled
In the Trace Configuration window in Cisco Unified Serviceability, Enable SIP Stack Trace represents one of the trace filter settings that are available. If you enable this log, you may experience severe performance degradation; so, when you click the Enable SIP Stack Trace check box, the following warning displays:
Enabling SIP Stack Trace can cause extreme performance degradation especially during high traffic hours.Missing MIB Changes
The Cisco Unified Serviceability Administration Guide requires updates for these MIB changes:
•
•
SNMP Traps and Informs Correction
The Cisco Unified Serviceability Administration Guide requires the deletion of this sentence from the SNMP Traps and Informs section: For some alarms, if the routing list in the alarm definition displays SNMP traps, the CCMAgent receives alarm notifications from the alarms. The notifications are received as XML messages which are parsed and traps are sent. In the case of Phone Failed and Phone Status events, the Phone Failed and Phone Status MMFs are populated.
Cisco Unified Communications Manager Assistant User Guide
The following sections comprise documentation updates for the Cisco Unified Communications Manager Assistant User Guide.
•
•
•
Cisco Unified Communications Manager Assistant User Guide for Cisco Unified Communications Manager 6.0
Consider the following note.
Note
Online Help Notes for Hebrew and Arabic
In the Cisco Unified Communications Manager Assistant User Guide, the chapter called "Introduction to Cisco Unified Communications Manager Assistant" does not contain the following information that Hebrew and Arabic users may need to know: Beginning in Cisco Unified Communications Manager Release 6.1 release, Cisco provides PDF versions of the Cisco Unified Communications Manager Assistant User Guide in Hebrew and Arabic as online help on the client PC that is running Cisco Unified Communications Manager Assistant. Therefore, this client must have Adobe Reader installed.
Cisco Unified Communications Manager Assistant
The assistant no longer obtains the assistant console application via a URL that the administrator provides; instead, a plug-in from Cisco Unified Communications Manager Administration gets downloaded and installed on the assistant PC.
The assistant console application installation supports Netscape 7.1 (or later) and Microsoft Internet Explorer 6 (or later). You can install the application on a PC that runs Windows 2000, Windows XP, or Windows Vista [new support for 5.1(3) and later].
A previous 5.x or 6.x version of the assistant console application works with Cisco Unified Communications Manager 6.1(1a), but if you decide to install the 6.1(1a) plug-in, you must uninstall the previous 5.x or 6.x version of the assistant console application before you install the plug-in.
Previous versions of the assistant console application do not work with Windows Vista. If the PC runs Windows Vista, install the plug-in.
After you upgrade from Cisco Unified CallManager Release 4.x to Cisco Unified Communications Manager 6.1(1a), you must install the assistant console plug-in. Before you install the plug-in, uninstall the 4.x version of the assistant console application.
To uninstall previous versions of the assistant console application (6.0(1), 4.x, or any 5.x version before 5.1(3)), choose Start> ...Programs > Cisco Unified CallManager Assistant > Uninstall Assistant Console.
To uninstall 5.1(3) (or later) attendant console application, go to the Control Panel and remove it.
Tip
To install the assistant console application, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Tip
The installation wizard displays.
Step 4
Step 5
Step 6
Tip
Step 7
The installation begins.
Step 8
Tip
Before the assistant logs in to the console, give the assistant the port number and the IP address or hostname of the Cisco Unified Communications Manager server where the Cisco IP Manager Assistant service is activated. The first time that the assistant logs in to the console, the assistant must enter the information in the Cisco Unified Communications Manager Assistant Server Port and the Cisco Unified Communications Manager Assistant Server Hostname or IP Address fields.
Before the assistant logs in to the console, give the assistant the user name and password that is required to log in to the console.
The Advanced tab in the Cisco Unified Communications Manager Assistant Settings window allows you to enable trace for the assistant console.
Directory Search Correction
In the Cisco Unified Communications Manager Assistant User Guide, "Getting Started" chapter, the Using the Directory section, the following sentence exists:
To search for a coworker, enter any portion of the person's first and/or last name in the search fields and click Search. The directory displays a list of all users that match your search string.
Replace the preceding information with the following information:
To search in the directory, enter the first letter of the first name or the first letter of the last name, followed by the trailing letters in the first or last name (whichever name that you are entering), and click Search. The results that match the search string display.
The following wildcards do not get supported:
•
•
•
Creating Filter Lists for a Manager
In the "How to Configure Manager Features" chapter of the Cisco Unified Communications Manager Assistant User Guide, in the How to Create Filter Lists for a Manager section, the following information now applies:
•
•
Cisco Unified IP Phone Documentation
The following sections comprise the documentation updates for the Cisco Unified IP Phone Administration Guide.
•
•
•
•
•
Cisco Unified IP Phone User Guide (7906, 7911, 7931, 7945, 7965, 7975)
The following information on extension mobility needs updating in the Cisco Unified IP Phone Guide (7906, 7911, 7931, 7945, 7965, 7975).
Using Cisco Extension Mobility
Cisco Extension Mobility (EM) allows you to temporarily configure a Cisco Unified IP Phone as your own. After you log in to EM, the phone adopts your user profile, including your phone lines, features, established services, and web-based settings. Your system administrator must configure EM for you.
Tips
•
•
•
•
Extension Mobility Successful Authentication Cache
The extension mobility application maintains a cache of all logged on user information for 2 minutes. If a request comes to extension mobility regarding a user who is represented in the cache, the user gets validated with information from the cache. This means that, if a user changes the password, logs out, and then logs back in within 2 minutes, both the old and new passwords get recognized.
Do Not Disturb Feature Priority
On Cisco Unified IP Phones, the text message that indicates the Do Not Disturb (DND) feature is active takes priority over the text message that indicates the user has new voicemail messages, which allows the user to know when DND is active. However, the text message that indicates the Call Forward All feature is active has a higher priority than DND.
Cisco Unified IP Phone Administration Guides (7905G, 7912G, 7921G)
The following information on Configuring a Custom Background Image needs updating in the Cisco Unified IP Phone Administration Guide (7905G, 7912G, 7921G).
Use the following procedure if you need to do the following types of updates to your IP phone:
•
•
Tip
Configuring a Custom Background Image
To configure custom background images for the Cisco Unified IP Phone, follow these steps:
Procedure
Step 1
bmp2logo imageID image.bmp image.logo
where:
•
•
Note
For example, if the image identifier is 10 and the base name of your image file is mylogo, enter this command:
bmp2logo 10 mylogo.bmp mylogo.log
Step 2
/usr/local/cm/tftp/<country>/
where:
<country> is the country of your locale installer (for example, Greece for Greek).
Note
Step 3
upgradelogo:imageID,TFTPServerID,image.logo
where:
•
•
•
For example, if the image identifier is 10, the converted file gets stored on the same TFTP server as the Cisco Unified IP Phone configuration file, and the base name of the converted image file specifies mylogo, add the following line to the configuration file:
upgradelogo:10,0,mylogo.logo
Note
Step 4
Step 5
//usr/local/cm/tftp/<lowercase country name>/
Note
To upload the files, choose Software Upgrades > Upload TFTP Server File in Cisco Unified OS Administration.
For more information, see the "Software Upgrades" chapter in Cisco Unified Communications Operating System Administration Guide.
You must also copy the customized binary files to the other TFTP servers that the phone may contact to obtain these files.
Note
Step 6
The new graphic displays when the phone restarts.
Cisco Unified Wireless IP Phone Guide 7920 for Cisco Unified CallManager 5.0 (SCCP)
The Using Personal Directory on Your Phone section incorrectly states that you access the personal address book from the Services button on the Cisco Unified Wireless IP Phone 7920. The following section provides the correct procedure.
Using Personal Directory on Your Phone
The Personal Directory feature set contains your Personal Address Book (PAB) and Fast Dials. This section describes how to set up and use Personal Directory on your phone.
Cisco Unified Wireless IP Phone Guide (7975, 7971, 7965, 7945, 7962, 7942, 7941, 7931, 7911, 7906)
The information for Cisco Web Dialer for Cisco Unified Communications Manager 6.1(2) was updated in the Cisco Unified IP Phone Guide for Cisco Unified Communications Manager 6.1(3).
Using Cisco Web Dialer
On the Preferences page (Make Call page in release 6.1(3x)), the default device for an Extension Mobility only user changed from Use EM Profile to Permanent Device. In release 6.1(3x), the default for EM only user changes back to Use EM Profile.
Cisco Unified CallManager Bulk Administration Guide
The following sections comprise documentation updates to the Cisco Unified CallManager Bulk Administration Guide.
•
•
•
•
•
•
•
Description for Phone Personalization Is Incorrect in Documentation
The Cisco Unified Communications Manager Bulk Administration Guide, Cisco Unified Communications Manager System Guide, and Cisco Unified Communications Manager Administration Guide contain incorrect information on phone personalization. If you plan to configure the Phone Personalization setting in Cisco Unified Communications Manager Administration, use the following information:
The Phone Personalization setting allows you to enable a Cisco Unified IP Phone, so it works with Phone Designer, a Cisco Unified Communications widget that allows a phone user to customize the wallpaper and ring tones on the phone. You can enable phone personalization in the Enterprise Parameter Configuration window, the Phone Configuration window, the Common Phone Profile Configuration window, or the Phone Template window in Cisco Unified Communications Manager Administration.
Tip
If you configure phone personalization in the Phone Configuration window (Device > Phone), Common Phone Profile Configuration window (Device > Device Settings > Common Phone Profile), or the Phone Template window (Bulk Administration > Phones > Phone Template), choose one of the following options from the Phone Personalization drop-down list box:
•
•
•
You must install and configure Phone Designer, so the phone user can customize the phone. Before you install and configure Phone Designer, identify which Cisco Unified IP Phone models work with Phone Designer, as described in the Phone Designer release notes. To obtain the Phone Designer documentation, go to the following URL:
http://www.cisco.com/en/US/products/ps9829/tsd_products_support_series_home.html
Incorrect Path Is Documented for Add File Format Window
The "Phones and User File Format" chapter in the Cisco Unified Communications Manager Bulk Administration Guide includes an incorrect path to the Add File Format window. The Adding Phones/User File Formats section incorrectly states that you choose Bulk Administration > Phones and Users> Phones & Users File Format > Assign File Format to access the Add File Format window. Disregard the path in the BAT documentation and choose the following path to access the Add File Format window: Bulk Administration > Phones and Users > Phones & Users File Format > Add File Format.
Primary User Device Field on the Update Users Window in BAT
The Cisco Unified CallManager Bulk Administration Guide omitted this information. A new field called Primary User Device displays in the Mobility Information section of the End User Configuration window. This field controls the number of device license units that are consumed for adjunct devices for mobile connect and works in conjunction with the Enable Mobility check box in the End User Configuration window.You can access this window through Users > Update Users.
Single Button Barge (new field)—Phone Template Configuration Window in BAT
The Cisco Unified CallManager Bulk Administration Guide omitted this information. Single Button Barge (new field)—This new field displays in the Phone Template Configuration window, and when you add a new phone configuration for a phone that is running SCCP, a new row exists for Single Button Barge/cBarge. You can set the Single Button Barge/cBarge feature Off, Barge. cBarge, or Default. If it is set to Default, the phone inherits the Single Button Barge/cBarge setting from the service parameter and device pool settings.
Join Across Lines (new field)—Phone Template Configuration Window in BAT
The Cisco Unified CallManager Bulk Administration Guide omitted this information. Join Across Lines (new field)—This new field displays in the Phone Template Configuration window. When you add a new phone configuration for a phone that is running SCCP, a new row exists for Join Across Lines. You can set the Join Across Lines feature to Off, On, or Default. If it is set to Default, the phone inherits the Join Across Lines setting from the service parameter and device pool settings.
Single Button Barge (new field)—UDP Template configuration Window in BAT
The Cisco Unified CallManager Bulk Administration Guide omitted this information. Single Button Barge (new field)—This new field displays in the UDP Template configuration window. When you add a new device profile configuration for a phone that is running SCCP, a new row exists for Single Button Barge/cBarge. You can set the Single Button Barge/cBarge feature to Off, Barge, cBarge, or Default. If it is set to Default, the phone inherits the Single Button Barge/cBarge setting from the service parameter and device pool settings.
Join Across Lines (new field)—UDP Template configuration Window in BAT
The Cisco Unified CallManager Bulk Administration Guide omitted this information. Join Across Lines (new field)—This new field displays inthe UDP Template configuration window. When you add a new device profile configuration for a phone that is running SCCP, a new row exists for Join Across Lines. You can set the Join Across Lines feature to Off, On, or Default. If it is set to Default, the phone inherits the Join Across Lines setting from the service parameter and device pool settings.
Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide
The following sections comprise the documentaiton updates for the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide.
•
•
•
•
•
•
•
RTMT Trace and Log Central Disk IO and CPU Throttling
RTMT now supports the throttling of critical Trace and Log Central operations and jobs, whether they are running on demand, scheduled, or automatic. The throttling slows down the operations when IO utilization is in high demand for call processing, so call processing can take precedence.
When a user makes a request for an on-demand operation when the call processing node is running under high IO conditions, the system now displays a warning, which gives the user the opportunity to abort the operation. You can configure the IO rate threshold values that control when the warning displays with the following new service parameters:
•
•
The system compares the values of these parameters against the system actual CPU and IOWait values. If the goal (the value of the service parameter) is lower than the actual value, the system issues the warning.
For More Information
•
Trace Compression Support
The following information provides an updated version of what appears in the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide.
This feature enables the ROS (Recoverable Outstream) library to support the compressed output of tracefiles. The files get compressed as they are being generated. The benefits of tracefile compression include
•
•
Use the new enterprise parameter, Trace Compression, to enable or disable trace compression. The default value for this parameter specifies Disabled. For information on setting the values of enterprise parameters, see the "Enterprise Parameters Configuration" chapter in the Cisco Unified Communications Manager Administration Guide.
Caution
You can recognize compressed files by their .gz extension (.gzo if the file is still being written to). To open a compressed file, double click the file name, and the file opens in the log viewer.
For More Information
•
Path for Accessing Cisco Unified Reporting
In both the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide ("Installing and Configuring Real-Time Monitoring Tool" chapter) and the Cisco Unified Serviceability Administration Guide ("Understanding Cisco Unified Serviceability" chapter), the RTMT menu path for accessing Cisco Unified Reporting is incorrect. The correct path follows: File>Cisco Unified Reporting.
Perfmon Log File—Maximum File Size Default Value
Chapters 4 and 5 ("Understanding Performance Monitoring" and "Configuring and Displaying Performance Counters") in the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide incorrectly specify the default value of the Maximum File Size perfmon data-logging parameter as 2 megabytes. The correct default value equals 5 megabytes.
Path for Accessing Cisco Unified Reporting
Both the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide ("Installing and Configuring Real-Time Monitoring Tool" chapter) and the Cisco Unified Serviceability Administration Guide ("Understanding Cisco Unified Serviceability" chapter) show an incorrect RTMT menu path for accessing Cisco Unified Reporting. The correct path follows: File>Cisco Unified Reporting.
DNS Required for RTMT Alerts by E-mail
The Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide do not explain that to configure RTMT to send alerts via Email, you must configure DNS. For information on configuring the primary and secondary DNS IP addresses and the domain name in Cisco Unified Communications Manager Server Configuration, see the "DHCP Server Configuration" chapter in the Cisco Unified Communications Manager Administration Guide.
Minimum Memory Requirement for RTMT Client
Chapter 2, "Installing and Configuring Real-Time Monitoring Tool (RTMT)" in the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide does not include the minimum memory requirement for running the RTMT client on a Windows OS machine. The minimum memory requirement equals 128 MB.
Cisco Unified Communications Operating System Administration Guide
The following sections comprise documentation updates for the Cisco Unified Communications Operating System Administration Guide.
•
•
•
•
•
•
•
•
•
•
COP File Installation
Before you begin the upgrade, install any new COP files that apply to the release you plan to install.
Tip
NTP Version 4
To avoid potential compatibility, accuracy, and network jitter problems, the external NTP servers that you specify for the primary node should be NTP v4 (version 4).
Support for NIC Teaming
The Cisco Unified Communications Operating System Administration Guide does not indicate the appropriate support for NIC teaming. Server platforms with dual Ethernet network interface cards (NICs) can support NIC teaming for network fault tolerance with Cisco Unified Communications Manager . Cisco began support of NIC teaming on HP servers in the 5.0(1) release and began support on IBM servers in the 6.1(2) release. This feature allows a server to be connected to the Ethernet via two NICs and, hence, two cables. NIC teaming prevents network downtime by transferring the workload from the failed port to the working port. NIC teaming cannot be used for load balancing or increasing the interface speed.
Install New COP Files Before You Upgrade Cisco Unified Communications Manager
If you have new .cop files for your devices, be sure you install them before you upgrade Cisco Unified Communications Manager to a newer build. If you do not install the new .cop file before you upgrade, your devices might not function correctly after the upgrade.
Digital Certificate Key Length Restrictions
In 5.x releases of Cisco Unified Communications Manager you must use digital certificates with a key length of 2048 bits or less. Cisco Unified Communications Operating System in these releases does not support digital certificates with a key length larger than 2048 bits.
set network dhcp eth0 disable Command Parameters
The set network dhcp eth0 disable command now requires the following parameters:
•
•
•
Remote Support Account Duration
When you create a remote support account in Cisco Unified Communications Operating System Administration, you must enter the duration for which the account will be active in the Account Duration field. Enter a number of days between 1 and 30. The remote support account will automatically expire after the number of days that you enter. The default account duration specifies 30 days.
System Generates a DBReplicationFailure Alert
During supported upgrades from Cisco Unified Communications Manager 5.x or 6.x to Cisco Unified Communications Manager 6.1(x), the system may generate a DBReplicationFailure alert while the system transitions to the new software release. Administrators can disregard this alert until all servers in the cluster have been upgraded and are running Cisco Unified Communications Manager 6.1(x).
For more information on viewing alerts, refer to the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide.
Information On ARP Cache Limits Omitted from Operating System Administration Guide
Do not install Cisco Unified Communications Manager in a large Class A or Class B subnet that contains a large number of devices. When you install Cisco Unified Communications Manager in a large subnet with a large number devices in that subnet, the Address Resolution Protocol (ARP) table can fill up quickly (maximum 1024 entries, by default). When the ARP table gets full, Cisco Unified Communications Manager can have difficulty talking to endpoints and cannot add more phones.
Third-Party Certificate Authority Verification
The Cisco Unified Communications Operating System Administration Guide, Release 6.0(1) states that Cisco has verified Verisign as a source for third party certificates. Be aware that this is no longer correct, and Verisign is not a verified CA.
Recovering Administrator and Security Passwords
This section replaces the section Recovering the Administrator Password in the "Log In to Cisco Unified Communications Operating System Administration" chapter" of the Cisco Unified Communications Operating System Administration Guide for releases 5.0(4), 5.1(1), 6.0(1), and 6.1(1a).
If you lose the administrator password or security password, use the following procedure to reset these passwords.
Note
Procedure
Step 1
•
•
The Welcome to platform password reset window displays.
Step 2
Step 3
Step 4
The system tests to ensure that you have removed the CD or DVD from the disk drive.
Step 5
The system tests to ensure that you have inserted the disk.
Step 6
•
•
•
Step 7
Step 8
The password must contain at least 6 characters. The system checks the new password for strength. If the password does not pass the strength check, you get prompted to enter a new password.
Step 9
Software Feature License Information Omitted from Operating System Administration Guide
The "Software Upgrades" chapter of the Cisco Unified Communications Operating System Administration Guide omits the following information:
You must obtain a software feature license if you are upgrading from Cisco Unified Communications Manager 5.x. A software feature license activates features on your system for the specified license version. To use 5.0 device licenses with Cisco Unified Communications Manager 6.(x) or later, make sure that you obtain the software feature license for the Cisco Unified Communications Manager version that is running on your system.
For more information on obtaining and installing licenses, see the "License File Upload" chapter in the Cisco Unified Communications Manager Administration Guide.
Cisco Unified Communications Manager Does Not Support Recovery of Administration or Security Passwords
Chapter 2 of the Cisco Unified Communications Operating System Administration Guide does not contain the following information.
Cisco Unified CM does not support recovery of administration or security passwords. If you lose these passwords, you must reset the passwords, as described in the Cisco Unified Communications Operating System Administration Guide.
Tip
Characters Allowed in a Pre-Shared Key
Chapter 6 of the Cisco Unified Communications Operating System Administration Guide does not contain the following information.
Pre-shared IPSec keys can contain alphanumeric characters and hyphens only, not white spaces or any other characters. If you are migrating from a Windows-based version of Cisco Unified CM, you may need to change the name of your pre-shared IPSec keys, so they are compatible with current versions of Cisco Unified CM.
Troubleshooting Guide for Cisco Unified Communications Manager
The following section comprises documentation updates for the Troubleshooting Guide.
•
•
Automated Alternate Routing (AAR) Limitation with Remote Gateways
AAR exhibits the limitation that calls routed over a remote gateway during a high-bandwidth situation fail, and the calls cannot get routed over the local gateway when AAR is used. Be aware that this functionality is important to customers who use Tail-End Hop Off (TEHO) for toll bypass.
Workaround Example
Use a specific partition for the TEHO in question.
In the following example, headquarters (HQ) has area code 408, and the Branch (BR1) has area code 919.
Configure as follows:
1.
2.
3.
4.
5.
6.
Results
In an out-of-bandwidth situation, after Cisco Unified Communications Manager tries to allocate the first route group for TEHO (BR1 route group), Cisco Unified CM retries the second route group, at which point the system strips the 91919 string and replaces it with the 1919 string, which is suitable for long-distance dialing. Because the string is configured for use by the local gateway, less rerouting takes place.
AAR works on a per-external-phone-number-mask basis and cannot be processed for an external PSTN number because the system does not know the phone number mask of the PSTN number. This workaround provides AAR functionality and improves network resiliency.
Cisco Unified Mobility User Hangs Up Mobile Phone But Cannot Resume Call on Desktop Phone
Symptom
When a remote destination (mobile phone) is not a smart phone and a call to this mobile phone is anchored through Cisco Unified CM, the user can hang up the mobile phone and expect to see a Resume softkey on the user desktop phone to resume the call. The user cannot resume this call on the user desktop phone.
Possible Cause
If the calling party receives busy/reorder/disconnect tone when the mobile phone hangs up, the mobile phone provider probably did not disconnect the media. Cisco Unified CM cannot recognize this circumstance because no disconnect signals came from the provider. To verify whether this is the case, let the calling party wait for 45 seconds, when service provider will time out and send disconnect signals, upon which Cisco Unified CM can provide a Resume softkey to resume the call.
Recommended Action
Perform the following actions:
•
voice call disc-pi-off
•
Cisco Unified Communications Manager 6.1 TCP and UDP Port Usage
The following section comprises the documentation updates for the Cisco Unified Communications Manager 6.1 TCP and UDP Port Usage documentation.
Ephemeral Port Range
The Cisco Unified Communications Manager 6.1 TCP and UDP Port Usage document requires the following update:
The Ephemeral port range for the system equals 32768 - 61000.
Disaster Recovery System Administration Guide
The topic "Restoring the Entire Cluster" in the Disaster Recovery System Administration Guide currently includes the following information:
If a major failure or a hardware upgrade occurs, or in the event of a hardware migration, you may need to rebuild all nodes in the cluster.
Correct this section to include the following information and to add the following tip:
Upgrading to Cisco Unified Communications Manager from 4.x Releases Guide
The Upgrading to Cisco Unified Communications Manager from 4.x Releases Guide should include the following information :
If you change the Servername during the upgrade, the original Servername—rather than the changed Servername— displays in the Cisco Unified Communications Manager Administration window.
If you want to change the Servername from what displays in the Cisco Unified Communications Manager Administration window, so it matches the name that you assigned during the upgrade, you can do so after the upgrade. Be aware, however, that this step is not required.
For more information on how to make this change, refer to the Changing the IP Address and Host Name for Cisco Unified Communications Manager document at the following URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco Ironport, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flip Video, Flip Video (Design), Flipshare (Design), Flip Ultra, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Store, and Flip Gift Card are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0907R)
Feedback