Cisco Unified Communications Manager Release 7.1(5a) is available in both restricted (which is the release type that has always been available from Cisco) and unrestricted versions. The unrestricted version is available in limited markets.

Caution Be aware that after you install an unrestricted release, you can never upgrade to a restricted version. You will also not be allowed to fresh install a restricted version on a system that contains an unrestricted version.

System Requirements

The following sections comprise the system requirements for this release of Cisco Unified CM.

Server Support

Make sure that you install and configure Cisco Unified CM on a Cisco Media Convergence Server (MCS) or a Cisco-approved HP server configuration or a Cisco-approved IBM server configuration.

Note Be aware that some servers that are listed in the Cisco Unified Communications Manager Software Compatibility Matrix may require additional hardware support for Cisco Unified CM Release 7.1(5a). Make sure that your server meets the minimum hardware requirements, as indicated in the footnotes of the Cisco Unified Communications Manager Software Compatibility Matrix. Cisco Unified CM requires a minimum of 2 GB of memory, 72 GB disk drive, and 2 GHz processor.

Uninterruptible Power Supply

Cisco recommends that you connect each Cisco Unified Communications Manager server to an uninterruptible power supply (UPS) to provide backup power and protect your system against a power failure.

Note You must connect MCS-7816 and MCS-7825 servers to a UPS to prevent file system corruption during power outages.

When Cisco Unified Communications Manager runs on one of the servers that are listed in Table 1, 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 with the APC SmartUPS 1500VA USB and APC 750VA XL USB. The feature activates automatically during bootup if a connected UPS gets detected.

Alternatively, you can execute the CLI command show ups status that shows the current status of the USB-connected APC smart-UPS device and starts the monitoring service if it is not already started. 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, and administrators cannot stop the shutdown after the feature is activated.

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.

Table 1 Supported Servers for Basic Integration

HP Servers

IBM Servers

MCS-7816-H3

MCS-7815-I1

MCS-7825-H1

MCS-7815-I2

MCS-7825-H2

MCS-7816-I3

MCS-7825-H3

MCS-7816-I3

MCS-7825-H4

MCS-7825-I1

MCS-7828-H3

MCS-7825-I2

MCS-7828-H4

MCS-7825-I3

MCS-7835-H2

MCS-7825I-30

MCS-7845-H2

MCS-7825-I4

MCS-7835-H3

MCS-7828-I3

MCS-7845-H3

MCS-7828-I4

MCS-7828-I4

MCS-7835-I1

MCS-7835I-30

MCS-7845-I2

MCS-7835-I3

MCS-7845-I3

Defects Resolved by Cisco Unified Communications Manager 7.1(5a)

The following defects are resolved by this release of Cisco Unified Communications Manager.

Installing Cisco Unified Communications Manager 7.1(5a)

To perform a fresh install of Cisco Unified Communications Manager , use the Product Upgrade Tool (PUT) to obtain a media kit and license.

To use the PUT, you must enter your Cisco contract number (Smartnet, SASU, or ESW) and request the DVD/DVD set. If you do not have a contract for Cisco Unified Communications Manager, you must purchase the upgrade from Cisco Sales.

Upgrading to Cisco Unified Communications Manager 7.1(5a)

The following sections contain information that is pertinent to upgrading to this release of Cisco Unified CM.

Device Name of Cisco Unified Mobile Communicator Must Not Exceed 15 Characters Before 7.1(5x) Upgrade

Before you upgrade to Cisco Unified Communications Manager 7.1(5x), ensure that the device name of a Cisco Unified Mobile Communicator does not exceed 15 characters in Cisco Unified Communications Manager Administration. If the device name of a Cisco Unified Mobile Communicator exceeds 15 characters, migration of this device will fail when you upgrade to Cisco Unified Communications Manager 7.1(5x) and the following error message gets written to the upgrade log:

InstallFull *ERROR* Name for Cisco Unified Mobile Communicator device(s) must be 15 or
less, please correct and rerun upgrade.

If an existing Cisco Unified Mobile Communicator device name specifies a longer name, shorten the device name to 15 or fewer characters before the upgrade.

Making Configuration Changes During an Upgrade

The administrator must not make any configuration changes to Cisco Unified Communications Manager during an upgrade. Configuration changes include any changes that you make in Cisco Unified Communications Manager Administration, in Cisco Unified Serviceability, and in the Cisco Unified CM User Options windows.

If you are upgrading your system, you must complete the upgrade tasks in this section before you perform any configuration tasks.

Caution If you fail to follow these recommendations, unexpected behavior,may occur; for example, the upgrade may fail or ports may not initialize as expected.

Upgrade Tasks

To successfully complete the upgrade, perform the upgrade tasks in the following order before you begin making configuration changes.

Note Cisco strongly recommends that you do not perform configuration tasks until the upgrade completes on all servers in the cluster, until you have switched the servers over to the upgraded partition, and until you have verified that database replication is functioning.

Procedure

Step 1 Stop all configuration tasks; that is, do not perform configuration tasks in the various Cisco Unified Communications Manager-related GUIs or the CLI (with the exception of performing the upgrade in the Cisco Unified Communications Operating System GUI).

Tip For detailed information about the upgrade process, see the "Software Upgrades" chapter in the Cisco Unified Communications Operating System Administration Guide.

Step 2 Upgrade the first node in the cluster (the publisher node).

Step 3 Upgrade the subsequent nodes in the cluster (the subscriber nodes).

Step 4 Switch over the first node to the upgraded partition.

Step 5 Switch over subsequent nodes to the upgraded partition.

Note You can switch the subsequent nodes to the upgraded partition either all at once or one at a time, depending on your site requirements.

Step 6 Ensure that database replication functions between the first node and the subsequent nodes. You can check database replication status by using one of the following methods:

•In Cisco Unified Reporting, access the Unified CM Database Status report. Before you proceed, ensure the report indicates that you have a good database replication status with no errors. For more information about using Cisco Unified Reporting, see the Cisco Unified Reporting Administration Guide.

•In the Cisco Real Time Monitoring Tool, access the Database Summary service under the CallManager tab to monitor database replication status. The following list indicates the database replication status progress:

–0— Initializing.

–1—Replication setup script fired from this node.

–2—Good replication.

–3—Bad replication.

–4—Replication setup did not succeed.

Before you proceed, ensure that you have a good database replication status. For more information about using the Real Time Monitoring Tool, see the Cisco Unified Real Time Monitoring Tool Administration Guide.

Step 7 When all other upgrade tasks are complete, you can perform any needed configuration tasks as required.

Upgrade Paths

For information about supported Cisco Unified CM upgrades, see the Cisco Unified Communications Manager Software Compatibility Matrix at the following URL:

Ordering the Upgrade Media

To upgrade from Cisco Unified Communications Manager 7.1(5a), use the Product Upgrade Tool (PUT) to obtain a media kit and license or to purchase the upgrade from Cisco Sales.

To use the PUT, you must enter your Cisco contract number (Smartnet, SASU, or ESW) and request the DVD/DVD set. If you do not have a contract for Cisco Unified Communications Manager, you must purchase the upgrade from Cisco Sales.

For more information about compatible Cisco Unified Communications Manager upgrades, see the Cisco Unified Communications Manager Software Compatibility Matrix at the following URL:

Note During an upgrade from a compatible Cisco Unified CM 5.1 version (see the Compatibility Matrix at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html) to Cisco Unified CM 7.1(5a) by using the Media Kit, in the Software Installation/Upgrade window, ignore the checksum step that instructs you "To ensure the integrity of the installation file, verify the MD5 hash value against the Cisco Systems website." Click Next.

Upgrading from Unified CM 6.x or Later by Using the UCSInstall File

Note Release 6.x customers can install this version, but the ccm.exe will not run unless 7.0 software licenses exist on the system.

Because of its size, the UCSInstall iso file, UCOS_7.1.5.20000-6.sgn.iso, comprises two parts:

•UCSInstall_UCOS_7.1.5.20000-6.sgn.iso_part1of2

•UCSInstall_UCOS_7.1.5.20000-6.sgn.iso_part2of2

Procedure

Step 1 From the Software Download page on Cisco.com, download the two UCSInstall files.

Step 2 To combine the two files, execute one of the following commands.

Note Because the UCSInstall_UCOS_7.1.5.20000-6 build specifies a nonbootable ISO, the build proves useful only for upgrades. You cannot use this build for new installations.

a. If you have a Unix/Linux system, copy and paste the following command into the CLI:

Note The unrestricted version of Unified CM 7.1(5a) is available in limited markets only.

Be aware that after you install or upgrade to an unrestricted release, you can never upgrade to a restricted version. You will not even be allowed to fresh install a restricted version on a system that contains an unrestricted version.

Installing the Unrestricted COP File

Before you upgrade from Compatible Versions of Cisco Unified Communications Manager 5.1(3x), 6.x or 7.x to unrestricted Cisco Unified Communications Manager 7.1(5a), install the unrestricted COP file (ciscocm.allow_upgrades_to_unrestricted.cop.sgn) that you can find at the following URL (copy and paste the URL into your browser):

Upgrading from a Remote Source

To upgrade the software from a network location or remote server, use the following procedure.

Note Do not use the browser controls, such as Refresh/Reload, while you are accessing Cisco Unified Operating System Administration. Instead, use the navigation controls that are provided by the interface.

Procedure

Step 1 Put the upgrade file on an FTP or SFTP server that the server that you are upgrading can access.

Step 5 In the Directory field, enter the path to the directory that contains the patch file on the remote system.

If the upgrade file is located on a Linux or Unix server, you must enter a forward slash at the beginning of the directory path. For example, if the upgrade file is in the patches directory, you must enter /patches

If the upgrade file is located on a Windows server, remember that you are connecting to an FTP or SFTP server, so use the appropriate syntax, including

•Begin the path with a forward slash (/) and use forward slashes throughout the path.

•The path must start from the FTP or SFTP root directory on the server, so you cannot enter a Windows absolute path, which starts with a drive letter (for example, C:).

Step 6 In the Server field, enter the server name or IP address.

Step 7 In the User Name field, enter your user name on the remote server.

Upgrading From an Engineering Special

If you are currently running an Engineering Special (ES), and want the fixes that exist in Cisco Unified Communications Manager 7.1(5a), contact TAC to obtain an ES with the fixes that are included in 7.1(5a) and the fixes that are included in the ES that you currently use.

Service Updates

After you install this release of Cisco Unified Communications Manager, check to see if Cisco has released critical patches or Service Updates. Service Updates, or SUs, contain fixes that were unavailable at the time of the original release. SUs often include security fixes, firmware updates, or software fixes that can improve operation.

To check for updates, from www.Cisco.com,select Support > Download Software. Navigate to the "Voice and Unified Communications" section and select IP Telephony > Call Control > Cisco Unified Communications Manager (CallManager) > the appropriate version of Cisco Unified Communications Manager for your deployment.

For continued notification of updates for your Cisco products, subscribe to the Cisco Notification Service at:

Related Documentation

Limitations and Restrictions

A list of compatible software releases represents a major deliverable of Cisco Unified Communications Manager System testing. The recommendations, which are not exclusive, represent an addition to interoperability recommendations for each individual voice application or voice infrastructure product.

For a list of software and firmware versions of IP telephony components and contact center components that were tested for interoperability with Cisco Unified Communications Manager 7.1(5a) as part of Cisco Unified Communications System Release 7.1 testing, see

Note 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 CM, you need to wait until a compatible version of the product becomes available before you can install Cisco Unified CM Release 7.1(5x). For the most current compatibility combinations and defects that are associated with other Cisco Unified CM products, refer to the documentation that is associated with those products.

Important Notes

The following section contains important information that may have been unavailable upon the initial release of documentation that supports Cisco Unified Communications Manager Release 7.1(5a).

CSCuc30279 Cannot Disassociate Devices From End Users Using BAT

The Bulk Administration Tool (BAT) cannot be used to disassociate devices that are already associated to an end user.

If you manually delete a controlled device from an exported end user record and then insert the modified user record back in to the Cisco Unified Communications Manager database as a custom CSV data file, the insertion appears as successful when you check the job results using Bulk Administration > Job Scheduler; however, the controlled device is still listed on the end-user page.

CSCtd69640 Downtime when upgrading Publisher server until all Subscriber servers are updated

When upgrading the publisher node, there will be a temporary server outage until all subscriber nodes get upgraded to the new software version.

New License Required when Replacing Motherboard (CSCtz12589 and CSCtz12651)

A new license file is required if you are installing a replacement motherboard in publisher servers or single servers that are not part of a cluster.

Unrestricted Release Limitations

After you install an unrestricted release, you can never upgrade to a restricted version. You will not even be allowed to fresh install a restricted version on a system that contains an unrestricted version.

CSCsz18443 Cisco Unified IP Phone 8961, 9951, 9971 Registered to a Node may Use the Call Park Number Assigned to Another Node

Call Park numbers get configured on the nodes of a Cisco Unified Communications Manager cluster (first/subsequent). Call Park numbers are normally allocated from the node that initiates the call. If the Cisco Unified IP Phone 8961, 9951, 9971 that initiates the call is registered to the first node of the Cisco Unified Communications Manager cluster, then a Call Park number configured on the first node gets used to park the call. This is irrespective of the node to which the called party is registered, or which party (calling or called) invokes the Call Park feature.

For example, if a phone registered to the first node initiates a call to a phone registered to the second node, then regardless of which phone invokes the Call Park feature, a Call Park number configured on the first node is always used.

Similarly, if the Call Park feature gets invoked when a phone in the second node is the call initiator, then a Call Park number configured on the second node is used.

Note Be aware that you can restrict the Call Park feature only by using calling search space and partitions. Not configuring a Call Park number on a node will not ensure that the Call Park feature is not available to the phones in that node.

CSCsz31137 Parked Call Gets Reverted When the Parkee is on

When an inter-cluster parked call connected by an Intercluster Trunk ( ICT) is put on hold, the call reverts when the Park Monitoring Reversion Timer and the Park Monitoring Forward No Retrieve Timer expire. Such a call reverts even though the parkee is on hold. This is a known limitation of inter-cluster calls connected via ICT that use the Call Park feature.

CSCsz35994 Incorrect Display for Park Monitoring Forward No Retrieve

For inter-cluster parked called connected by an ICT, after the Park Reversion Timer and Park Monitoring Forward No Retrieve Timer expire, the call gets forwarded to the Park Monitoring Forward No Retrieve destination. The display of the incoming call is incorrect on the destination device.

The display on the device is "From DN" instead of "Forwarded for DN". For example, if the initial call is an inter-cluster call via ICT from DN 1000 to DN 3000 and gets forwarded to DN 2000, the display on DN 2000 is "From 3000" instead of "Forwarded for 1000".

CSCtb53159 Display Limitation in ConfList

You can add as many conference participants as the conference bridge supports; however, ConfList only displays 16 participants. From the 17th participant onwards, the list displays only the latest 16 participants.

Signaling and Media Encryption is Disabled

Be aware that Cisco Unified CM UI allows you to provision signaling or media encryption for lines or trunks (for example, endpoints, gateways, trunks, SIP, MGCP, H.323, H.225); however, none of those settings is actually enabled internally in Unified CM. (This is one of the unrestricted requirements).

CSCtd01766 Destination Port on Trunk Remains Unchanged After Upgrade

During an upgrade to an unrestricted Cisco Unified CM release, the SIP trunk incoming port gets changed to 5060; however, the destination port on the trunk remains what it was before the upgrade.

CSCtd87058 BAT Impact in Unrestricted Unified CM

If your Cisco Unified CM is unrestricted, Cisco recommends that you do not edit the following fields by using BAT - Import/Export:

In the event of a system lock up, IBM I3-type servers do not automatically restart.

Conditions

Under rare critical failures, such as a kernel panic, the IBM I3-type servers do not automatically get restarted by the BIOS ASR functionality and logs the event. The server remains unresponsive until it is rebooted manually. In IMM Control > System Settings > Server Timeouts, the OS Watchdog timeout default specifies disabled.

Workaround

Manually set the OS Watchdog timer to the time interval during which the watchdog should check for activity.

Caution Currently the ASR / OS Watchdog feature gets triggered unexpectedly during fresh install and potentially during upgrade from 7.1(3) to 7.1(5). If the server is restarted due to Watchdog Timer expiring the install or upgrade may fail.

Until this defect gets resolved, use the ASR / OS Watchdog feature with care. Before a fresh install or upgrade, disable the OS Watchdog Feature by using IMM to avoid unexpected failures.

CSCtf15332 Node Licenses Missing After an Upgrade

If the node license file contains multiple features (for example: SW_FEATURE + CCM_NODE), after you upgrade to this release of Cisco Unified Communications Manager, the following licensing warnings might display:

Step 1 Lower the threshold for the low active partition disk space warning to less than 4%.

Step 2 Back up your system.

Step 3 Perform a fresh installation.

Step 4 Restore the system so that the disk gets repartitioned and is no longer limited by the inefficient 5.x disk partitioning.

Disaster Recovery System Caution

When you restore your data, the hostname, server IP address, DNS configuration, version, and the deployment type values must match their values during the backup. DRS does not restore across different hostnames, IP addresses, DNS configurations, versions, and deployment types.

CSCso98836 HP Ultra320 SCSI HDD FW Upgrade

A ProLiant server that is configured with any of the HP Ultra320 SCSI hard drives that are listed in HP Customer Advisory #C00859596 (available at http://www.hp.com) may exhibit timeouts and SCSI downshifts.

These problems may occur on the following server models:

•MCS-7835-1266 (DL380-G2)

•MCS-7835H-2.4 (DL380-G3)

•MCS-7835H-3.0 (DL380-G3)

•MCS-7835-H1 (DL380-G4)

•MCS-7845-1400 (DL380-G2)

•MCS-7845H-2.4 (DL380-G3)

•MCS-7845H-3.0 (DL380-G3)

•MCS-7845-H1 (DL380-G4)

The associated HP Customer Advisories list the affected hard drives that experience these problems. However, you can apply the Cisco-provided HP SCSI Hard Drive Firmware Update CD to all listed server types and the impacted drives get updated if applicable.

To update the firmware to a Cisco-tested level, use the Cisco provided HP SCSI Hard Drive Firmware Update CD released simultaneous to the Unified Communications 7.0(1) system release. For more details on installing the firmware, see the README.txt file for HP SCSI Hard Drive Firmware Update CD.

You can obtain the ISO image for the Cisco-provided HP SCSI Hard Drive Firmware Update CD and associated readme file from Cisco.com at the following navigation path:

CSCtb95488 Phones That Support Monitoring and Recording Features

The "Monitoring and Recording" chapter of the Cisco Unified Communications Manager Features and Services Guide,includes a partial list of devices that support monitoring and recording in the "Agent Devices" subsection of the "Devices That Support Call Monitoring and Call Recording" section.

The list of devices that support the monitoring and recording features varies per version and device pack.

Use the Cisco Unified Reporting application to generate a complete list of devices that support monitoring and recording for a particular release and device pack. To do so, follow these steps:

1. Start Cisco Unified Reporting by using any of the methods that follow.

The system uses the Cisco Tomcat service to authenticate users before allowing access to the web application. You can access the application

LogCollectionPort Service: selectLogFiles Operation

Description

The selectLogFiles operation retrieves log files based on a selection criteria. This API takes FileSelectionCriteria object as an input parameter and returns the file name and location for that object.

Parameters

The selectLogFiles operation includes the following elements:

•ServiceLogs—Array of strings. The available service options depends on the services that are activated on the Cisco Unified CM. The actual available options are those that the listNodeServiceLogs operation returns at run time. For example:

–Cisco Syslog Agent

–Cisco Unified CM SNMP Service

–Cisco CDP Agent

•SystemLogs—Array of strings.

Note SystemLogs element is not available in Cisco Unified CM release 7.1.3, and therefore should be empty.

•JobType—The collection type. The available options are the following:

–DownloadtoClient

–PushtoSFTPServer

If you select PushtoSFTPServer, the following elements are also required:

•IPAddress

•UserName

•Password

•Port

•Remote Download Folder

•SearchStr—A non-null string.

•Frequency—The frequency of log collection. The available options are the following:

–OnDemand

–Daily

–Weekly

–Monthly

Note Only OnDemand option is currently supported for the Frequency element. The other options (Daily, Weekly, and Monthly) apply to schedule collection, which is currently not supported.

•ToDate—The end date for file collection. Format is mm/yy/dd hh:mm AM/PM. The ToDate element is required if you use absolute time range.File collection time range can be absolute or relative. If you prefer relative time range, the following elements are required:

•RelText

•RelTime

If you prefer absolute time range, then the following elements are required:

•ToDate

•FromDate

•FromDate—The start date for file collection. Format is mm/yy/dd hh:mm AM/PM. The FromDate element is required if you use absolute time range.

•RelText—The file collection time range. The available options are:

–Week

–Day

–Month

–Hours

–Minutes

•RelTime—The file collection time value. Gives all files from the specified time up to present. The available range specifies 1 to 100.For example, if the RelText is "Day" and RelTime is 1, then we get all files modified in the previous one day.

•TimeZone—The time zone value. The format isClient: (GMT ±n) Name of the time zonewhere n is the offset time of the specified time zone and GMT. For example:

–Client: (GMT-0:0) Greenwich Mean Time

–Client: (GMT-8:0) Pacific Standard Time

•Port—The port number of the node.

•IPAddress—The IP address of the node.

•UserName—The service administrator username for the node.

•Password—The service administrator password for the node.

•ZipInfo—Indicates whether to compress the files during collection. This element is applicable only for PushtoSFTPServer option. The available options are:

–True—The files are compressed.

–False—The files are not compressed.

•RemoteFolder—The remote folder where the files are to be uploaded. This option is used only if you choose to upload trace files to SFTP or FTP server.

Fault

If the specified frequency is null, it throws a remote exception, "LogCollection frequency is null." If the array of ServiceLogs and System Logs is null, it throws a remote exception, "No Service/Syslog are provided for the collection." If a matching file is not found, it throws a remote exception, "The File Vector from the server is null."

Perform DRS Backup After You Regenerate Certificates

After you regenerate certificates in Cisco Unified Communications Operating System, you must perform a backup so that the latest backup contains the regenerated certificate(s). If your backup does not contain the regenerated certificates and you must perform restoration tasks for any reason, you must manually unlock each phone in your system so that the phone can register with Cisco Unified Communications Manager. For information on performing a backup, refer to the Disaster Recovery System Administration Guide.

Important Information About Create File Format Capability in BAT

The Create File Format window provides the option to set the maximum number of Lines, Speed Dials, and so on. The file format that gets created by using BAT stores the selected Device, Line, Intercom, Speed Dial, BLF Speed Dial, BLF Directed Call Park, and IP Phone Service fields in the database. Because the database column length allows up to 32K characters, the BAT Administrator cannot choose all the fields with maximum allowed number because this will exceed 32K. When the file format length exceeds 32K, BAT displays the following error message:

"Cannot Insert a file format with characters more than 32K"

The BAT Administrator must use BAT Phone Templates to define the common attributes.

Limitation Between QSIG PRI and SIP Trunk for MWI

In previous releases of Cisco Unified CM, to route an MWI request from QSIG PRI to a SIP trunk, the route pattern that was specified had to point directly to the SIP trunk.

If the route pattern pointed to a Route List/Route Group that included the SIP trunk, MWI failed. After the first failure, all subsequent MWI indications to any number in the cluster failed.

In Cisco Unified CM 7.x, the MWI routing gets handled differently.

If MessageWaiting gets an SsDataInd signal while in the mwi_nailed_up_ssinfores state, MessageWaiting does not process any subsequent MWIs.

SDL traces should look like the example below, which indicates that a previous MWI request caused the system to hit the limitation.

Cisco Unified Communications Manager Assistant Wizard Constraint

Be aware that you can run the IPMA Wizard only once. Attempts to run it more than once will fail.

Creating a Custom Help Desk Role and Custom Help Desk User Group

Some companies want their help desk personnel to have privileges to be able to perform certain tasks, such as adding a phone, adding an end user, or adding an end user to a user group in Cisco Unified Communications Manager Administration.

Performing the steps in the following example allows help desk personnel to add a phone, add an end user, and add the end user to the Standard CCM End Users user group, which allows an end user to access and update the Cisco Unified CM User Options.

Example—Allows Help Desk Personnel to Add Phone, Add End User, and Add End User to User Group

Step 4 In the Name field, enter the name of the role; for example, Help Desk.

Step 5 In the Description field, enter a short description; for example, for adding phones and users.

Step 6 Choose one of the following options, which depends on where you want the help desk personnel to perform the task:

a. If you want the help desk personnel to add a phone in the Phone Configuration window and then add an end user in the End User Configuration window. check the read and update privileges check boxes for the User web page resource and the Phone web pages resource; then, click Save.

b. If you want the help desk personnel to add both a phone and a user at the same time in the User and Phone Add window, check the read and update privileges check boxes for the User and Phone add resource and the User web page resource; then, click Save.

Step 7 By performing the following tasks, you create a custom user group for the help desk:

e. Check the check box for the custom role that you created in Step 1 through Step 6; in this example, Help Desk. In addition, check the check box for the Standard CCM Admin Users role; then, click Add Selected.

f. In the User Group Configuration window, verify that the roles display in the Role Assignment pane; then, click Save.

Next Steps

In Cisco Unified Communications Manager Administration, the help desk personnel can add the phone, add the user, and add the end user to the user group.

•To add a phone in the Phone Configuration window, choose Device > Phone; then, to add an end user in the End User window, choose User Management > End User.

•To add both a phone and user at the same time in the User and Phone Add window, choose User Management > User and Phone Add.

Considerations for LDAP Port Configuration

When you configure the LDAP Port field 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.

Your configuration may require that you enter a different port number than the numbers that are listed in the following items. Before you configure the LDAP Port field, contact the administrator of your directory server to determine the correct port number to enter.

LDAP Port for When the LDAP Server Is Not a Global Catalog Server

•389—When SSL is not required. (This port number specifies the default that displays in the LDAP Port field.)

•636—When SSL is required. (If you enter this port number, make sure that you check the Use SSL check box.)

LDAP Port for When the LDAP Server Is a Global Catalog Server

•3268—When SSL is not required.

•3269—When SSL is required. (If you enter this port number, make sure that you check the Use SSL check box.)

Table 2 lists the locations where you can configure a host name for the Cisco Unified Communications Manager server, the allowed number of characters for the host name, and the recommended first and last characters for the host name. Be aware that, if you do not configure the host name correctly, some components in Cisco Unified Communications Manager, such as the operating system, database, installation, and so on, may not work as expected.

Caution Before you change the host name or IP address for any locations that are listed in
Table 2, refer to
Changing the IP Address and Host Name for Cisco Unified Communications Manager 7.1(2). Failing to update the host name or IP address correctly after it is configured may cause problems for Cisco Unified Communications Manager.

Tip The host name must follow the rules for ARPANET host names. Between the first and last character of the host name, you can enter alphanumeric characters and hyphens.

Before you configure the host name in any location in Table 2, review the following information:

•The Host Name/IP Address field in the Server Configuration window, which supports device-to-server, application-to-server, and server-to-server communication, allows you to enter an IPv4 address in dotted decimal format or a host name.

After you install Cisco Unified Communications Manager on the publisher database server, the host name for the publisher automatically displays in this field. Before you install Cisco Unified Communications Manager on the subscriber server, enter either the IP address or the host name for the subscriber server in this field on the publisher database server.

In this field, only configure a host name if Cisco Unified Communications Manager can access the DNS server to resolve host names to IP addresses; make sure that you configure the Cisco Unified Communications Manager name and address information on the DNS server.

•During the Cisco Unified Communications Manager installation of the publisher database server, you enter the host name, which is mandatory, and IP address of the publisher server to configure network information; that is, if you want to use static networking.

During the Cisco Unified Communications Manager installation on the subscriber server, you enter the hostname and IP address of the publisher database server, so Cisco Unified Communications Manager can verify network connectivity and publisher-subscriber validation. Additionally, you must enter the host name and the IP address for the subscriber server. When the Cisco Unified Communications Manager installation prompts you for the host name of the subscriber server, enter the value that displays in the Server Configuration window in Cisco Unified Communications Manager Administration; that is, if you configured a host name for the subscriber server in the Host Name/IP Address field.

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.

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:

A blind transfer or an unanswered conference call that gets forwarded to voice-mail over QSIG PRI trunk reaches the general greeting instead of the called party.

Important Information About Delete Transaction by 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.

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 consistent with the Bulk Administration user interface.

Basic Uninterruptible Power Supply (UPS) Integration

When Cisco Unified Communications Manager 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 starts as soon as the low battery threshold is reached. Resumption or fluctuation of power does 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 Make sure that the restore runs on the same Cisco Unified Communications Manager version as the backup. The Disaster Recovery System supports only matching versions of Cisco Unified Communications Manager for restore.

Serviceability Not Always Accessible from OS Administration

If the redirect fails, log out of 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.

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

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

Serviceability Session Timeout Is 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 you make any changes in the user interface.

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

CSCtj61834 MLPP Default Domain Name Displays MLPP ID Value

When you configure the MLPP Domain Name in Cisco Unified Communications Manager, the default name for MLPP Domain Name displays the MLPP ID value 000000 instead of Default as stated on the help page.

CSCtr40861 Incoming Calling Party Numbers should be up to 16 characters

When configuring the Incoming Calling Party Numbers setting, the number of characters you can enter is 16 not 8 for:

•Incoming Calling Party National Number Prefix

•Incoming Calling Party International Number Prefix

•Incoming Calling Party Unknown Number Prefix

•Incoming Calling Party Subscriber Number Prefix

You can enter up to 16 characters, which include digits, the international escape character (+), asterisk (*), or the pound sign (#).

CSCtr84167 Block Offnet to Offnet Transfer

When you enable the service parameter Block Offnet to Offnet Transfer and make a blind transfer with Cisco Unity Connection, the Q.931 SETUP message which Cisco Unified Communications Manager sends to the PSTN gateway for an outbound PRI call still reaches the gateway. This transfer results in a dropped call.

CSCtr21486 Troubleshooting Guide Update to Switch Version

When there is a version mismatch between a subscriber server and publisher server, the Cisco Unified Communications Manager history file does not log a switch version entry.

MDCX Sendonly Message Suppressed for MGCP Calls

For all MGCP calls, Cisco Unified Communications Manager suppresses the media layer from sending any MDCX (M:sendonly) messages to the MGCP gateway. This is done to prevent one-way audio scenarios.

DTMF Suppressed when G.Clear is Advertised

Cisco Unified Communications Manager suppresses DTMF configuration settings for all calls on which G.Clear is advertised in the list of codecs, irrespective of whether G.Clear is chosen as the codec for the call.

CSCtx00678 Do not use Voicemail for Alerting Name or ASCII Alerting Name

Do not use the word "Voicemail" anywhere in the Alerting Name or ASCII Alerting Name fields in the Directory Number Configuration window. Use of the word "Voicemail" can cause Cisco Unity Connection to process the call as a direct call rather than as a forwarded call.

CSCtx86215 Database Replication

This section of the Cisco Unified Communications Manager System Issues chapter in the Troubleshooting Guidefor Cisco Unified Communications Manager requires this addition:

Extension Mobility does not work when database replication breaks between the Unified CM node running Extension Mobility and the Unified CM node to which the phone is registered.

CSCtc71174 Call Park and Directed Call Park Restriction

The following call flow shows a limitation with the Call Park and Directed Call Park features.

1. Phone A calls Phone B.

2. Phone B parks the call. Phone A is now connected to MOH.

3. Phone A presses Hold (Mutual Hold).

4. Phone C dials the parked number through a H323 Trunk.

5. No audio is produced and the call fails after 12 sec (MXTimeout).

In this call flow, when you retrieve a parked call across an H323 ICT that is also on hold, the call fails. By the time phone C tries to retrieve the parked call, the parked party is on hold and Unified CM cannot cut through media.

CSCuc10415 Tip for Adding a New Server

The following tip needs to be added to the "Server settings" topic in the Cisco Unified Communications Manager Administration Guide.

To avoid errors, Cisco recommends that you add a server to the system with a name that has less than 47 characters. Then, update the server name to the target length.

CSCuc79185 Device Mobility Calling Search Space is Used When Device CSS is <none>

The following note is missing from the "Phone Settings" topic in the Cisco Unified Communications Manager Administration Guide:

When set to <none>, Unified CM uses the device mobility calling search space, which is configured on the device pool.

CSCtw44980 Missing Exceptions for Voice-Mail Pilot

The following information is missing for the Voice Mail Pilot Name field description in the "Voice-Mail Pilot Settings" topic in the Cisco Unified Communications Manager Administration Guide:

Step 5 By using the Cisco CTL client, create the CTL File, as described in "Installing the Cisco CTL Client" and "Configuring the Cisco CTL Client".

Tip If the clusterwide security mode is in mixed mode, the Cisco CTL client displays the message No CTL File exists on the server but the CallManager Cluster Security Mode is in Mixed Mode. For the system to function, you must create the CTL File and set CallManager Cluster to Mixed Mode. Click OK; then, choose Set CallManager Cluster to Mixed Mode and complete the CTL file configuration.

Step 6 Reboot all the servers in the cluster.

Step 7 After you create the CTL file on all the servers and reboot all servers in the cluster, delete the CTL file from the phone, as described in "Deleting the CTL File on the Cisco Unified IP Phone".

CSCud95087 Limitation of SIP Forking on Trunk Not Documented

The following information is missing from "Understanding Session Initiation Protocol" in the Cisco Unified Communications Manager System Guide:

•Cisco Unified CallManager Release 4.x does not accept provisional responses (such as 180 Ringing) from more than five destinations. It does not accept a successful response (200 Ok) from any destination that is not among the first five to respond.

•Cisco Unified CallManager Release 5.x and Cisco Unified Communications Manager Release 6.x do not accept provisional responses (such as 180 Ringing) from more than 20 destinations. They do not accept a successful response (200 Ok) from any destination that is not among the first 20 to respond.

utils ldap config fqdn

This command configures the system to use an FQDN for LDAP authentication, which is the preferred method.

Note Because this method requires that DNS be configured, if the system is not configured to use DNS, execute utils ldap config ipaddr instead.

Command Syntax

utils ldap config fqdn

Requirements

Command privilege level: 0

Allowed during upgrade: No

utils ldap config ipaddr

This command configures the system to use an IP address for LDAP authentication.

Note Because using an IP address for LDAP authentication is not the preferred method, use this command if the system is not, or cannot, be configured to use DNS. If your system is configured to use DNS, use utils ldap config fqdn instead.

Command Syntax

utils ldap config ipaddr

Requirements

Command privilege level: 0

Allowed during upgrade: No

Command Updated

The following command got updated in the Command Line Interface Reference Guide for Cisco Unifed Communications Solutions, Release 7.1(5):

New and Updated Enterprise and System Parameters

No new or updated enterprise parameters exist in Cisco Unified Communications Manager 7.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.

•Always Use Preferred G.729 Packet Size For SIP Trunk Answers

This parameter determines whether the value specified in the Preferred G.729 Millisecond Packet Size service parameter is always used in outgoing answers that contain G.729 (including any of the four variants: G.729, G.729a, G.729b, or G.729ab) and that are sent to SIP Trunks. Valid values specify True or False; the default value specifies False.

When set to True, the preferred G.729 packet size is used as the G.729 ptime (packetization time) in the outgoing answer to the SIP trunk only when Cisco Unified Communications Manager selects G.729 from the codecs in the offer, regardless of which G.729 ptime is specified in the incoming offer from the trunk. This answer to the SIP trunk tells the device behind the trunk to send a G.729 stream with that packet size to the other party in the call. The other party in the call also gets signaled to stream G.729 with that packet size to the device behind the SIP trunk. However, if the other party uses SCCP, H.323, or MGCP, and the preferred packet size exceeds the packet size that the other party advertises, the other party's advertised packet size gets used instead for both the outgoing answer to the SIP trunk and for the signals to the other party. This service parameter applies only to calls in which media resources (including media termination points and transcoders) are not allocated.

When set to False, the preferred G.729 packet size gets used only when it does not exceed the packet sizes that the SIP trunk and the other party in the call advertise. This procedure is normally used for all audio codecs.

Menu Changes

This section contains information on the following menus in Cisco Unified Communications Manager Administration:

Midcall Codec Support

This feature allows Cisco Unified Communications Manager to handle changes in codec, IP address, or port information during an audio or video call. A new check box, Require SDP Inactive exchange for mid-call media change, in the SIP Profile Configuration window allows you to enable or disable sending mid-call media changes without breaking the existing media path with an inactive SDP.

Note This feature is applicable to mid-call reInvites coming from a peer SIP endpoint.

The mid-call codec feature supports:

•Change of codec in the mid-call Invite in audio/ video mlines.

•Change of IP address at the session level or mline level in audio/video mlines.

•Change of port in the mid-call Invite in audio/video mlines.

When you modify the codec, IP address, or port on the peer SIP endpoint during a call and enable the configuration by checking the Require SDP Inactive exchange for mid-call media change check box, Cisco Unified Communications Manager sends an inactive SIP invite to disconnect the current media channel at the peer SIP endpoint. Then it re-establishes the media path and sends an SDP containing the changes to the SIP line side device with incoming reInvite (or SIP trunk).

The inactive Invite gets sent because a Cisco Unified Communications Manager device may not support mid-call codec changes. When the device at the peer SIP endpoint detects a mid-call codec, IP address, or port change, it drops the call. Enabling the configuration check box has the effect of resetting the media path.

If the configuration is enabled, when the SIP trunk receives the SDP information with the modified codec, IP address, or port during a call, Cisco Unified Communications Manager disconnects the media path at the peer SIP endpoint and re-establishes the media path and sends the changed SDP information to the SIP trunk.

The default value of the check box specifies unchecked. If the check box remains unchecked, Cisco Unified Communications Manager does not disconnect the media. Instead, it passes the incoming changed SDP back to the peer SIP endpoint and lets it handle the changed information.

Note For those SIP devices that do not support SDP changes without breaking the media, the check box on the SIP Profile Configuration window can be checked. This way, Cisco Unified CM will first send an inactive SDP Invite to break the media path, followed by a reInvite with the changed SDP information.

Example

Phone A changes the port number mid-call by creating a new media description with the port number in the `m' line. Though the change is sent, Phone A continues to listen for media on the old port until a response is received from the SIP trunk and media arrives on the new port. Ceasing to listen could result in loss of media during the transition.

If the updated stream is accepted by the SIP trunk, the SIP trunk begins sending traffic for that stream to the new port immediately. If the SIP trunk changes the port from the previous SDP, it must be prepared to receive media on both the old and new ports as soon as the answer is sent. The SIP trunk continues to listen for media on the old port until it arrives on the new port.

If the updated media stream is rejected, Phone A can cease being prepared to receive media on the new port soon after receiving the rejection. The procedure for changing the IP Address and port number are similar except that the connection line is updated for IP Address, not the port number.

You must enable the check box at the peer SIP endpoint. By default, this parameter specifies unchecked, which implies that the mid-call SDP can be forwarded as-is to the peer SIP. You are required to associate the newly created SIP Profile to the peer SIP Intercluster Trunk (SIP ICT).

Using a SIP trunk, the new parameter in the SIP Profile Configuration window helps maintain backward compatibility with the releases prior to Cisco Unified Communications Manager 7.1(5) that are connected to Cisco Unified Communications Manager 7.1(5).

Note Cisco Unified Communications Manager supports mid-call codec update. But if a codec change exists in the new offer, you will be required to set up the media again.

The following are important points to remember when you use this feature:

•The feature is applicable only to mid-call reInvites coming from a peer SIP endpoint.

•If there is a codec or IP address change in the SIP trunk in the non-inactive mid-call invite, Cisco Unified Communications Manager disconnects media at the peer SIP endpoint. While the new SDP is negotiated, the SIP trunk might experience a temporary pause. During this pause, no packets will flow in or out of the old port of the peer SIP. When the two-way media channels are negotiated at the peer SIP side and the SIP trunk receives an answer, the two-way RTP begin flowing between the new ports.

•If there is a port change in the SIP trunk in the non-inactive mid-call invite, and if the peer SIP side is MGCP or SCCP device, the SIP trunk continues to send packets to the old port but may not receive packets from the old port for a small duration during the re-opening of channels. When the channels are re-opened on the peer SIP side and the SIP trunk receives an answer, it begins receiving RTP packets on the new port.

•If the peer SIP endpoint is a SIP or H.323 device, the SIP trunk might experience a temporary pause during which two way channels are reopened on the peer SIP side.

Unrestricted Export Support

The restricted US export classification on Cisco Unified CM meant that governmental and military customers in many countries could not employ Unified CM in their networks.

In addition to the delay inherent in obtaining export licenses, products classified as restricted by the Department of Commerce (DoC) carry a requirement to allow US government representatives to demand on-site inspections at any time to confirm that the product is being used in accordance with its licensed purpose. This post-shipment verification (PSV) is unacceptable to many customers.

Additionally, some foreign countries maintain import restrictions which prohibited Unified CM from being available to customers in those countries. Both US export and foreign import issues stem from Unified CM support for strong encryption of signaling and media.

Unrestricted Classification

Because Cisco has obtained an unrestricted classification from the DoC for a version of Unified CM, beginning with Unified CM 7.1(5), both restricted and unrestricted versions of Unified CM will be released in parallel.

Limitations

Signaling and media encryption is permanently disabled in the unrestricted version, but remains unchanged in the restricted version.

Migration from the unrestricted version to the restricted version is not supported.

Note No impact exists to other security features such as HTTP(s), SSH, password encryption and authentication (for example, SIP digest authentication), mechanisms used by unrestricted Unified CM clients such as JTAPI, TSP, encryption of SNMP traffic, encryption of data related to database that is done by using IPSEC and IMS on the server side.

The communication between CTL client and provider remains encrypted.

Universal IOS Transcoding

Description

Cisco Unified Communications Manager 7.1(5) and later leverage the IOS-based DSP universal transcoding to do codec conversion between a wide range of codec combinations to enable disparate endpoints to communicate with each other.

In earlier releases, Cisco Unified Communications Manager used only a subset of the IOS-based DSP transcoding capability, requiring that one side of the connection had to be G.711. Cisco Unified Communications Manager now allows all types of transcoding requests to IOS-based DSP transcoders. It detects transcoders capable of doing universal transcoding and allocates these resources for any-to-any transcoding requests.

Note The universal transcoder does not support all the standard codecs that are currently available. It can transcode between supported codec types only.

Example

Phone A (which supports only G723) calls Phone B (which supports only G729). After the initial call handling, when Cisco Unified CM tries to establish media between the two phones, it discovers the need for a transcoder to convert G723 to G729.

Cisco Unified Communications Manager finds a Dixieland-based Universal Xcoder in the available resources pool and allocates it for this call. The Universal Xcoder is capable of converting the media to and from G723 and G729 and, thus, starts streaming to the phones after receiving OLC (Open logical channel) and SMT (Start media transmission) signals from Cisco Unified Communications Manager.

You configure and register a Dixieland Universal Transcoder the same way as the regular Dixieland Transcoder. During the registration with Cisco Unified Communications Manager; however, the Universal Transcoder includes an extra capability (Media payload type 222) to indicate that it supports Universal Transcoding.

Example

On the IOS server, `DSPFarm Profile 100 Transcode' will be suffixed with `Universal' after configuration. So, the profile name will read: `DSPFarm Profile 100 Transcode Universal.'

Cisco Mobile 8.0 provides iPhone users with voice over IP (VoIP) calling, visual voicemail, and access to the corporate directory while users are connected to the corporate network over Wi-Fi, either on premises or over VPN. Cisco Mobile 8.0 specifies an IP telephony endpoint that associates with Cisco Unified Communications Manager.

Note Cisco Mobile 8.0 is distinct from the Cisco Mobile application that runs in conjunction with a Cisco Unified Mobility Advantage server.

In order for Cisco Unified Communications Manager to support Cisco Mobile 8.0, Cisco Unified Communications Manager administrators must take at least the following step:

The Administration Guide for Cisco Mobile 8.0 for iPhone provides the details of the complete configuration that is required to configure Cisco Mobile 8.0, including the steps that must be performed in Cisco Unified Communications Manager Administration. Refer to the document at the following URL:

Prior to Release 7.1(5), the Cisco Unified CM administrator had to specify the firmware load for the phone by using the Device Defaults Configuration window or by using the phone settings. The IP phone would then download the firmware to the Inactive firmware bank in the background; the phone continued to provide service by using its Active firmware load.

Cisco Unified CM administrators can specify the firmware load for both the Active and Inactive firmware banks for the Cisco Unified Communications Manager Release 7.1(5) and later. A new Switch Loads function will swap the Active and Inactive settings and continue to control both the settings while preserving the former Active setting in the Inactive entry.

Enabling the independent image download and switchover enhances control of dual-banked firmware supporting device types and allows the Cisco Unified CM administrator greater control and visibility during the download of the dual-banked phone firmware and switchover. Administrators can:

•Control the download of the dual-banked phone firmware and switchover, while retaining backward compatibility.

•Alter the Inactive image setting to initiate an image download only.

•Implement separate switch load requests to cause the phone to start using a previously downloaded Inactive firmware load while preserving the Active load designation as the new Inactive image.

•Use independent Switch Loads to implement a revert function when a newly installed firmware load does not behave as desired.

The Cisco Unified CM administrator can upload the new firmware before the upgrade. The new firmware (a COP file) is uploaded by using Cisco Unified Communications Operating System, Software Uploads.

Note The dual-banked firmware update feature allows Cisco Unified CM administrator to upgrade phone firmware with a new load before resetting the new load to an Inactive load status. Instead of waiting for all the phones to download the firmware, Cisco Unified CM administrators can use the Switch Loads function to quickly switch from the old load to the new load in less time.

Upgrading the dual-banked firmware reduces the bandwidth congestion and the delay in download during system maintenance while allowing Cisco Unified CM administrators to determine when to set the new firmware to Active load.

The Dual-Bank Information area indicates Load A as the Inactive load and Load B as the Active load.

Step 4 Click Swap Loads to swap Load A and Load B.

The Dual-Bank Information area indicates Load A as the Active load and Load B as the Inactive load.

Step 5 Click Save to save the configuration settings. All the phones will run with Load B as Inactive load.

Step 6 In Cisco Unified CM Administration, go to Device > Phone.

Step 7 Change Load B to Active load. This changes the Load A to an Inactive load.

Step 8 Click Save.

The Load B is Active and the Load A is Inactive.

Note During dual-banked firmware upgrade, the previous Active load will be swapped as an Inactive load. No change will be made if the new load matches with the Active load settings. If there is no previous Active load, (fresh install), the Inactive load setting will be left empty.

GUI Changes

A new area in the Device Defaults Configuration (Device > Device Settings) window allows you to monitor and change the Dual Bank Information (for dual-banked firmware capable devices only).

Specifies the protocol that the corresponding device in the Device Type column uses.

Load Information

Specifies the ID number of the firmware load that is used with a particular type of hardware device. If you install an upgrade or patch load, you must update the load information for each type of device that uses the new load.

Inactive Load Information

Specifies the ID number of the Inactive firmware load.

Device Pool

Specifies the device pool that is associated with each type of device. The device pool defines common characteristics for all devices in the pool.

Phone Template

Specifies the phone button template that each type of Cisco Unified IP Phone uses. The template defines what keys on the phone perform that function.

In the Dual Bank Information area in the Device Defaults Configuration (Device > Device Settings) window, there is a new Swap Loads icon. Administrators can override the default installation of new firmware as the Active load by using the Switch Loads operation prior to execution of the Apply Config. This will move the new firmware load to the Inactive load setting restoring the previous Active load setting.

Service Parameter and Enterprise Parameter Changes

No service or enterprise parameter changes exist for this feature.

Installation/Upgrade (Migration) Considerations

After you install or upgrade to Cisco Unified Communications Manager 7.1(5), you can use this feature.

COP file or system install/upgrade operations will remain unaltered with the following exceptions related to devices supporting Dual-Banked firmware and Apply Config features:

2. The existing Active firmware load designation in the Device Defaults will be preserved by copying it to the Inactive firmware load setting prior to marking of the new firmware as the Active load.

Note If the new load already matches the active load setting, then no change will be made to either the Active or the Inactive loads.

3. The Cisco Unified CM administrator may set the newly downloaded firmware as the Inactive load, restoring the Active load setting from the Inactive bank setting. This would cause the phone to download the new firmware to its Inactive bank. The administrator can later switch the phones to use the new load as the Active load with no download delay.

Note This would be accomplished via the Device Defaults web page. There the administrator can use the Switch Loads icon to swap the Active and Inactive loads prior to an Apply Config request or device reset/restart. This will restore the current load as the configured Active Load and place the newly installed firmware into the configured Inactive Load.

Serviceability Considerations

No serviceability considerations exist for this feature.

BAT Considerations

BAT is able to accept load information as previously for the Active load, load information for the inactive load, or both. BAT import/export tool supports this feature.

A Trusted Device represents a Cisco device or a third-party device that has passed Cisco security criteria for trusted connections. This includes, but is not limited to, signaling/media encryption, platform hardening, and assurance. If a device is trusted, a Security icon displays, and a secure tone plays on supported devices. Also, the device may provide other features or indicators that are related to secure calls.

Cisco Unified Communications Manager determines whether a device is trusted when you add it to your system. The security icon displays for information purposes only, and the administrator cannot configure it directly.

This section describes the behavior of the security icon for trusted devices on both the Cisco Unified IP Phones and in Cisco Unified Communications Manager Administration.

Cisco Unified Communications Manager Administration

The following windows in Cisco Unified Communications Manager Administration indicate whether a device is trusted:

CTI Route Point Configuration

The CTI Route Point Configuration window (Device > CTI Route Point) displays either Device is trusted or Device is not trusted, along with a corresponding icon.

The system determines whether the device is trusted, based on the device type. You cannot configure whether the device is trusted.

Voice Mail Port Configuration

The Voice Mail Port Configuration window (Advanced Features > Voice Mail > Cisco Voice Mail Port) displays either Device is trusted or Device is not trusted, along with a corresponding icon.

The system determines whether the device is trusted, based on the device type. You cannot configure whether the device is trusted.

Gateway Configuration

For each gateway type, the Gateway Configuration window (Device > Gateway) displays either Device is trusted or Device is not trusted, along with a corresponding icon.

The system determines whether the device is trusted, based on the device type. You cannot configure whether the device is trusted.

Phone Configuration

For each phone device type, the Phone Configuration window (Device > Phone) displays either Device is trusted or Device is not trusted, along with a corresponding icon.

The system determines whether the device is trusted, based on the device type. You cannot configure whether the device is trusted. For a list of trusted Cisco Unified IP Phones, see the "Trusted Devices" section.

Cisco Unified IP Phones

Beginning with Cisco Unified Communications Manager Release 7.1(3x), the type of device that a user calls will affect the security icon that displays on the phone. Previously, the system set the security icon by determining whether the signalling and media were secure. For Release 7.1(3x), the system will consider the following three criteria to determine whether the call is secure:

•Are all devices that are on the call trusted?

•Is the signaling secure (authenticated and encrypted)?

•Is the media secure?

Before a supported Cisco Unified IP Phone displays the Lock Security icon, be aware that all three criteria must be met. For calls that involve a device that is not trusted, regardless of signaling and media security, the overall status of the call will stay unsecure, and the phone will not display the Lock icon. For example, if you include an untrusted device in a conference, the system considers its call leg, as well as the conference itself, to be unsecure.

Trusted Devices

For a list of security features that are supported on your phone, refer to the phone administration and user documentation that supports this Cisco Unified Communications Manager release or the firmware documentation that supports your firmware load.

You can also use Cisco Unified Reporting to list the phones that support a particular feature. For more information about using Cisco Unified Reporting, see the Cisco Unified Reporting Administration Guide.

Cisco Unified Serviceability

Audit Log Records User Logout Events

In earlier releases of Cisco Unified Communications Manager, when you logged in to Cisco Unified Communications Manager Administration, performed required tasks and logged out, the log in event got recorded in the audit logs but the logout event did not get recorded.

Cisco Unified Communications Manager 7.1(5). resolved this issue.

To see the log in and log out events, check the audit logs from RTMT > Trace & Log Central > Real Time Trace >Audit Logs.

Caveats

The following sections contain information on how to obtain the latest resolved caveat information and descriptions of open caveats of severity levels 1, 2, and 3.

Resolved Caveats

You can find the latest resolved caveat information for Cisco Unified Communications Manager Release 7.1 by using Bug Toolkit, which is an online tool that is available for customers to query defects according to their own needs.

Tip You need an account with Cisco.com (Cisco Connection Online) to use the Bug Toolkit to find open and resolved caveats of any severity for any release.

When you open the online record for a defect, you will see data in the "First Fixed-in Version" field. The information that displays in this field 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.

Tip Bug Toolkit requires that you have an account with Cisco.com (Cisco Connection Online). By using the Bug Toolkit, you can find caveats of any severity for any release. Bug Toolkit may also provide a more current listing than this document provides. To access the Bug Toolkit, log on to http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.

Open Caveats for Cisco Unified Communications Manager Release 7.1(5a) As of June 28, 2010

The following information comprises unexpected behavior (as of April 10, 2010) that you may encounter in Release 7.1(5a) of Cisco Unified Communications Manager.

Table 8 Open Caveats for Cisco Unified Communications Manager Release 7.1(5a) as of June 28, 2010

Documentation Updates

The Updates to Cisco Unified Communications Manager 7.1(x) Documentation document provides information about documentation omissions, errors, or updates that are not included in the documentation that supports the Unified CM 8.0(x) release train.To obtain this document, go to the following URL:

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

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 by using a reader application. Be aware that the RSS feeds are a free service, and Cisco currently supports RSS version 2.0.

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. (0711R)