 Feedback
|
Table Of Contents
Release Notes for Cisco Unified CallManager Release 5.1(3)
Determining the Software Version
Do Not Upgrade from Cisco Unified CallManager 5.1(3) to Cisco Unified Communications Manager 6.x
Cisco Unified CallManager Administration Does Not Support Browser Buttons
Internet Explorer 7 Certificate Support
New Cisco Unified Reporting Application
Updating the Hostname or IP Address in the Server Configuration Window
SIP Network/IP Address Field Required for SIP Fallback to SRST Gateway
RTMT on the Microsoft Vista Platform
Resolved Caveat CSCsj22450 Login Failure Does Not Send a Message to the Syslog
RTMT Requirement When Upgrading Cisco Unified CallManager
iLO Flashing Causes the Login Window to Disappear After Installation or Upgrade
Serviceability Session Timeout Not Graceful
CSCtj61834 MLPP Default Domain Name Displays MLPP ID Value
New and Changed Information for Cisco Unified CallManager Release 5.1(3)
Installation, Upgrade, and Disaster Recovery
Cisco Unified CallManager Administration
General Administration Enhancements
Service and Enterprise Parameter Changes
Cisco Unified CallManager Applications and Features
CSCsi80592 MTP Resources Do Not Support Multicast Music on Hold
Cisco Unified CallManager Assistant
Route Patterns, Automated Alternative Routing, and Applications
AXL Serviceability Programming
Cisco Unified JTAPI Developers Guide
Cisco Unified TAPI Developers Guide
SIP Line Messaging Guide (Standard)
Cisco Unified Communications Manager Data Dictionary
Cisco Unified Wireless IP Phone 7921
Cisco Unified IP Phone 7962G and 7942G (SCCP and SIP)
Cisco Unified IP Phone 7965G and 7945G (SCCP and SIP)
Cisco Unified IP Phone 7975G (SCCP and SIP)
Cisco Unified CallManager Serviceability
Adding RTMT Performance Counters in Bulk
RTMT Database Summary with Database Replication Information
Start Counter(s) Logging in the Menu Bar
RTMT Trace and Log Central Disk IO and CPU Throttling
RTMT Services, Servlets and Service Parameters
Obtaining Documentation, Obtaining Support, and Security Guidelines
Cisco Product Security Overview
Release Notes for Cisco Unified CallManager Release 5.1(3)
October 3, 2011
These release notes describe the enhanced capabilities of Cisco Unified CallManager Release 5.1(3) as well as DDTS fixes that ensure software quality.
July 09, 2009
Added information about to omissions to the "Documentation Updates" section
November 9, 2007
Added information about upgrades to CUCM 6.0 to the "Important Notes" section.
Note
To view the release notes for previous versions of Cisco Unified CallManager, choose the Cisco Unified CallManager version from the following URL: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_release_notes_list.html
Before you install Cisco Unified CallManager, Cisco recommends that you review the "Important Notes" section for information about issues that may affect your system.
Note
Cisco recommends that you check Cisco.com for the latest software updates to Cisco Unified CallManager and its applications and download and install the latest updates on your system before the deployment of your Cisco Unified CallManager system. For a list of commonly used URLs, see the "Upgrading System Software" section.
Contents
These release notes discuss the following topics:
•
•
•
Introduction
Cisco Unified CallManager, a network business communication system, provides high-quality telephony over IP networks. Cisco Unified CallManager enables the conversion of conventional, proprietary, circuit-switched PBXs to multiservice, open LAN systems.
System Requirements
Make sure that you install and configure Cisco Unified CallManager Release 5.1(3) on a Cisco Media Convergence Server (MCS). To see which MCS servers are compatible with this release, see: http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_models_home.html.
Note
You may also install Cisco Unified CallManager on a Cisco-approved HP server or a Cisco-approved IBM server . For Cisco-approved HP or IBM configurations, see: http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_brochure_list.html.
Note
Tip
Supported Platforms
To find which servers support the Cisco Unified CallManager 5.1(3) release, refer to http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_brochure_list.html.
Determining the Software Version
To determine whether you need to upgrade the Cisco Unified CallManager software that you are using, launch Cisco Unified CallManager Administration. The following information displays:
•
•
Upgrading System Software
You can access the latest software upgrades for Cisco Unified CallManager 5.1 on Cisco.com. Table 1 lists the URLs from which you download the software.
Table 1 Download URLs for Software Upgrades
Cisco Unified CallManager 5.1
Locale installers
http://www.cisco.com/kobayashi/sw-center/telephony/callmgr/ locale-installer.shtm
Phone firmware
http://www.cisco.com/cgi-bin/tablebuild.pl/ip-7900ser
http://www.cisco.com/cgi-bin/tablebuild.pl/ip-7900ser-crypto
Cisco Security Agent (CSA)
Upgrade Assistant
Related Documentation
The following documentation supports Cisco Unified CallManager Release 5.1(3):
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Limitations and Restrictions
A list of compatible software releases represents a major deliverable of Cisco Unified CallManager System testing. The recommendations, which are not exclusive, represent an addition to interoperability recommendations for each individual voice application or voice infrastructure product.
For a list of software and firmware versions of IP telephony components and contact center components that were tested for interoperability with Cisco Unified CallManager 5.1(x) as part of Cisco Unified Communications System Release 5.1(x) testing, see
http://www.cisco.com/go/unified-techinfo
Note
Important Notes
The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco Unified CallManager Release 5.1(3).
•
•
•
•
•
•
•
•
•
•
•
•
Do Not Upgrade from Cisco Unified CallManager 5.1(3) to Cisco Unified Communications Manager 6.x
It is not possible to successfully upgrade from Cisco Unified CallManager Release 5.1(3) to Cisco Unified Communications Manager Release 6.x.
Cisco Unified CallManager Administration Does Not Support Browser Buttons
Cisco Unified CallManager Administration does not support the buttons in your browser. Do not use the browser buttons (for example, the Back button) when you perform configuration tasks.
Internet Explorer 7 Certificate Support
This release supports Internet Explorer 7 web browser for Cisco Unified CallManager Administration. Internet Explorer 7 adds security features that change the way the browser handles Cisco certificates for website access. Because Cisco provides a self-signed certificate for the Cisco Unified CallManager server, Internet Explorer 7 flags the Cisco Unified CallManager Administration website as untrusted and provides a certificate error, even when the trust store contains the server certificate.
Note
Be sure to import the Cisco Unified CallManager certificate to Internet Explorer 7 to secure access without having to reload the certificate every time that you restart the browser. If you continue to a website that has a certificate warning and the certificate is not in the trust store, Internet Explorer 7 retains the certificate for the current session only.
After you download the server certificate, Internet Explorer 7 continues to display certificate errors for the website. You can ignore the security warnings when the Trusted Root Certificate Authority trust store for the browser contains the imported certificate.
The following procedure describes how to import the Cisco Unified CallManager certificate to the root certificate trust store in Internet Explorer 7.
JRE must be present to provideall the Java releated browser support for IE6 or IE7.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Internet Explorer 7 Support
The following applications now support Internet Explorer 7:
•
•
•
•
•
•
New Cisco Unified Reporting Application
The new Cisco Unified Reporting web application, which is accessed at the Cisco Unified CallManager console, generates reports for troubleshooting or inspecting cluster data.
This convenient tool provides a snapshot of cluster data without requiring multiple steps to get the data. The tool design facilitates gathering data from existing sources, comparing the data, and reporting irregularities.
A report combines data from one or more sources on one or more servers into one output view. For example, you can view a report that shows the hosts file for all servers in the cluster.
The application gathers information from the publisher server and each subscriber server. A report provides data for all active cluster nodes that are accessible at the time that the report is generated.
Some reports run checks to identify conditions that could impact cluster operations. Status messages indicate the outcome of every data check that is run.
Only authorized users can access the Cisco Unified Reporting application. By default, this includes administrator users in the Standard Unified CM Super Users group. As an authorized user, you can view reports, generate new reports, or download reports at the graphical user interface (GUI).
Cisco Unified Reporting includes the following capabilities:
•
•
Refer to the Cisco Unified Reporting Administration Guide for more information.
Updating the Hostname or IP Address in the Server Configuration Window
Before you change the hostname or IP address of a server in the Server Configuration window in Cisco Unified CallManager Administration, consider the following information:
•
•
•
SIP Network/IP Address Field Required for SIP Fallback to SRST Gateway
Although Cisco Unified CallManager 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 CallManager Administration Guide.
RTMT on the Microsoft Vista Platform
When you install RTMT on the Microsoft Vista platform, the system displays the User Account Control popup window shown in Figure 1 due to a limitation in the InstallAnywhere software. This is a one time popup that displays only when installing RTMT. Select Allow to continue.
Figure 1 User Account Control Popup Window
Resolved Caveat CSCsj22450 Login Failure Does Not Send a Message to the Syslog
This resolved caveats adds the following alarm catalog and two alarms:
LoginAlarmCatalog:
AuthenticationFailed - when a web application login attempt fails
AuthenticationSucceeded - when a web application login attempt succeeds
The alarm events are logged in to the local and remote SYSLOG.
Note
Resolved Caveat CSCsh58895 Cisco Unified CallManager Cannot Send System or Platform Agent Logs to Remote Syslog Server
Cisco Unified CallManager can now send syslog messages to a remote server.
You can configure two new enterprise parameters from Cisco Unified CallManager Administration > System > Enterprise Parameters:
•
Note
Remote Syslog Server Name:
–
–
•
RTMT Requirement When Upgrading Cisco Unified CallManager
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.
iLO Flashing Causes the Login Window to Disappear After Installation or Upgrade
As part of the installation or upgrade processes, the iLO firmware in the servers gets flashed. During the flashing, messages are displayed for the convenience of the user. Because of this, after the installation or upgrade completes, the default login window gets masked by the messages.
To see the login window, press Enter.
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 indicating that the session has timed out and redirecting you to the login window. Once you log in again, you may have to repeat those changes. This behavior occurs in the Alarm, Trace, Service Activation, Control Center, and SNMP windows. The only workaround is to log out using the Logout button before making any changes in the user interface if you know that the session has been idle for more than 30 minutes.
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.
New and Changed Information for Cisco Unified CallManager Release 5.1(3)
The following sections contain information that is new or changed for this release of Cisco Unified CallManager.
•
•
•
•
•
Installation, Upgrade, and Disaster Recovery
Installation Overview
For 5.1(3), the Cisco Unified Communications Manager installation process includes the following new features:
•
•
MTU Size Parameter
During installation, you can configure the MTU size parameter. The MTU size represents the largest packet, in bytes, that the host will transmit on the network. If you are unsure of the MTU setting for your network, use the default value, 1500 bytes.
Note
Enhanced Connectivity Validation
To ensure successful installation of a subsequent node, the system validates that the subsequent node can connect with the first node.
If connectivity validation fails, the installation process stops, and the system prompts you to reenter the network configuration information. After you update the network configuration information, you can continue with the installation.
Prior to connectivity validation, from the Network Connectivity Test Configuration window, you can choose whether you want the installation process to continue uninterrupted after a successful validation test or stop and display a successful validation message.
•
•
Enhanced Documentation
For Release 5.1(3), enhancements to the installation and upgrade documentation to cover additional pre- and post-installation tasks, as well as specific steps for adding a new subscriber node to an existing cluster.
The Release 5.1(3) documentation set also includes a new document that describes the procedures for replacing a cluster or a single server in an existing cluster, Replacing a Cluster or Single Server for Cisco Unified CallManager Release 5.1(3).
Disaster Recovery System
DRS now backs up CAR/CDR data automatically. You do not need to select the CAR/CDR feature to back up this data.
Where to Find More Information
For more information, refer to the following documents:
•
•
•
•
Cisco Unified CallManager Administration
This section contains information on the following topic:
•
•
General Administration Enhancements
The following requirements apply to Cisco Unified CallManager Administration:
•
•
Note
Service and Enterprise Parameter Changes
•
For example, if the value for the parameter equals 20 minutes and the timer expires at 3:00, Cisco Unified CallManager examines the time from 2:40 to 3:00. If traffic occurred during that time, the connection remains open until the next examination at 3:20. If no traffic occurred from 3:00 to 3:20, Cisco Unified CallManager closes the TCP connection at or shortly after 3:20. If traffic occurred from 3:00 to 3:20, the TCP connection remains open until Cisco Unified CallManager checks for traffic again at 3:40, and so on.
After you update this parameter, you must restart the Cisco CallManager service for the changes to take effect.
For the default, maximum, and minimum values for the parameter, access the parameter in Cisco Unified CallManager Administration and either click the name of the service parameter or click the ? button in the Service Parameter Configuration window.
Note
•
•
–
–
Cisco Unified CallManager Applications and Features
The following sections describe the Cisco Unified CallManager 5.1 applications enhancements:
•
•
CSCsi80592 MTP Resources Do Not Support Multicast Music on Hold
The following restriction exists for multicast music on hold (MOH) when a media termination point (MTP) is invoked. When an MTP resource gets invoked in a call leg at a site that is using multicast MOH, the caller receives silence instead of music on hold. To avoid this scenario, configure unicast MOH or Tone on Hold instead of multicast MOH
Cisco Unified CallManager Assistant
In Cisco Unified CallManager 5.1(3), the assistant no longer obtains the assistant console application via a URL that the administrator provides; instead, a plug-in from Cisco Unified CallManager 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.0 (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).
A previous 5.x version of the assistant console application works with Cisco Unified CallManager 5.1(3), but if you decide to install the 5.1(3) plug-in, you must uninstall the previous 5.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 5.1(3), you must install the assistant console plug-in. Before you install the plug-in, uninstall the 4.X version of the assistant console application.
Uninstalling the Assistant Console Application
To uninstall previous versions of the assistant console application, choose Start> ...Programs > Cisco Unified CallManager Assistant > Uninstall Assistant Console.
To uninstall the new plugin-based assistant 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 CallManager 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 CallManager Assistant Server Port and the Cisco Unified CallManager 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 CallManager Assistant Settings window allows you to enable trace for the assistant console.
Cisco and Third-Party APIs
This following sections describe new features and changes that are pertinent to Release 5.1(3) of the Cisco Unified Communications Manager APIs and the Cisco extensions to third-party APIs.
•
•
•
•
•
•
Windows Vista Support
Cisco Unified CallManager Release 5.1(3) adds support for Cisco TAPI and Cisco JTAPI on the Windows Vista platform.
For information about the JVM versions that Cisco JTAPI supports on Windows Vista and other platforms, see Table 3.
Route Patterns, Automated Alternative Routing, and Applications
Cisco Unified CallManager only applies Automated Alternative Routing (AAR) to the endpoints that it controls.hNetwork congestion and bandwidth restrictions can cause tail-end hop-off (TEHO) calls to fail if you configure Cisco Unified CallManager to use AAR. To provide failover support for route patterns, you must configure the route lists to take advantage of their built-in redundancy.
Application developers who use the Cisco Unified CallManager TAPI and JTAPI APIs should be aware of this behavior.
AXL Programming
The following table summarizes the AXL schema changes in Release 5.1(3):
The change in the callingSearchSpaceName tag to String50 type affects APIs that inherit from Device. The change also affects add, get, and update APIs of CTIRoutePoint, DevicePool, DeviceProfile, DirectedCallPark, GatewayEndPoint, H323Gateway, H323Phone, H323Trunk, HuntPilot, Line, MGCPEndPoint, PilotPoint, RemoteDestinationProfile, SIPTrunk, VoiceMailPilot, and VoiceMailPort.
Change to axl.xsd for the ringSetting Element
The definition of the ringSetting element changes in Release 5.1(3) to make this element optional:
<xsd:element name="ringSetting" type="axl:XRingSetting" default="Ring" nillable="false" minOccurs="0"/>Prior to this release, ringSetting comprised a required element:
<xsd:element name="ringSetting" type="axl:XRingSetting" default="Ring" nillable="false"/>Documentation Supplement
WSDL AXL and AXIS
By default, AXIS2 creates all the methods and requests in the same stub file, which might be as large as 35 Mb. AXIS1.4 creates individual files for every method,which yields individual files smaller than 2 Mb.
AXIS2 includes the option "-d xmlbeans" to change the binding option, which creates separate files for all methods as with AXIS1.4. For more information, see this URL:
http://ws.apache.org/axis2/1_1_1/userguide-creatingclients.html.Changes in the Initial Version of Release 5.1
The following sections describe the API changes that were introduced in the initial version of Cisco Unified CallManager Release 5.1.
AXL APIs
The following list provides AXL API calls that are new in Cisco Unified CallManager Release 5.1:
•
•
•
•
These APIs add and update credentials (passwordreserve) in siprealm.
New AXL Service Parameter
Cisco Unified CallManager Administration 5.1 release adds a new service parameter, Send Valid Namespace in AXL Response, under the Cisco Database Layer Monitor service. This parameter determines the namespace that gets sent in the AXL response from Cisco Unified CallManager.
When this parameter specifies True, Cisco Unified CallManager sends the valid namespace (that is,http://www.cisco.com/AXL/API/1.0) in the AXL response, so the namespace matches the AXL schema specification.
If the parameter specifies False, Cisco Unified CallManager sends an invalid namespace (that is,http://www.cisco.com/AXL/1.0) in the AXL response, which does not match the AXL schema specification.
The default service parameter value specifies False to maintain backward compatibility with the AXL response in the Cisco Unified Communications Manager 5.0 release. Cisco recommends that you set this parameter to True, so Cisco Unified CallManager sends the valid namespace.
AXL Serviceability Programming
No changes to the AXL Serviceability APIs exist for Release 5.1(3).
Summary of Changes in Previous Releases
For a summary of changes in previous releases, see the following table:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/devguide/6_0_1/Svc_API_table.html
Documentation Errata
This section corrects some errors in the Cisco Unified CallManager Developers Guide for Release 5.0.
An error exists in the example that shows the PerfmonAddCounter request with two counters and a single-reference accessor. The
SessionHandleelement contains an incorrect value for thetypeattribute. The corrected example follows.<?xml version="1.0" encoding="utf-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:PerfmonAddCounter soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://schemas.cisco.com/ast/soap/"><SessionHandle xsi:type="ns1:SessionHandleType">b60b683a-24fd-11dc-8000-000000000000</SessionHandle><ArrayOfCounter soapenc:arrayType="ns1:CounterType[2]" xsi:type="soapenc:Array" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><item xsi:type="ns1:CounterType"><Name xsi:type="ns1:CounterNameType">\\sampleserver\Process\Nice</Name></item><item xsi:type="ns1:CounterType"><Name xsi:type="ns1:CounterNameType">\\sampleserver\Process\PID</Name></item></ArrayOfCounter></ns1:PerfmonAddCounter></soapenv:Body></soapenv:Envelope>An error also exists in the section Real-Time Information (RisPort) > Selecting Cisco Unified CallManager Real-Time Information > Request Format > SOAP Action and Envelope Information.
The SOAPAction should beSOAPAction:http://schemas.cisco.com/ast/soap/action/#RisPort#SelectCmDevice
Extension Mobility API
No changes exist in the Extension Mobility API in Release 5.1(3).
Web Dialer
The following change to Web Dialer occurred for Cisco Unified CallManager Release 5.1(3):
•
Documentation Errata
The Cisco Unified CallManager Release 5.1(1) New and Changed Information Guide states that the Cisco Unified CallManager Administration directory search page uses the makeCall interface. However, beginning with Release 5.0, the directory search page actually uses the makeCallProxy interface.
Changes in Release 5.1
The initial 5.1 release of Cisco Unified CallManager included the following change to Cisco Unified CallManager Web Dialer:
•
Developers should format Redirector and Web Dialer requests to use HTTPS. Cisco Unified CallManager requires the secured protocol to prevent unauthorized applications from reading user data.
For More Information
•
•
Cisco Unified JTAPI Developers Guide
No changes to Cisco Unified JTAPI exists in Release 5.1(3). As stated previously, beginning with this release, Cisco Unified JTAPI supports the Windows Vista platform.
The following sections supplement the Cisco Unified CallManager JTAPI Developers Guide.
Hunt List Targets
The Cisco JTAPI implementation does not support hunt lists. Applications cannot observe an Address, CiscoAddress, or CiscoRouteAddress that is a member of a HuntList LineGroup.
Translation Pattern Support
If a calling party transformation mask is configured for a translation pattern that is applied to a JTAPI application-controlled Address, the application may see extra connections that get created and disconnected when both the calling and called party are observed. A Connection gets created for a transformed calling party instead of the actual calling party, and CiscoCall.getCurrentCallingParty() would return the transformed calling party, when only the called party is observed. In general, JTAPI might not be able to create the appropriate Connection in the Call, and might not be able to provide correct information for currentCalling, currentCalled, calling, called, and lastRedirecting parties.
For example, consider a translation pattern X that is configured with a calling party transformation mask Y and called party transformation mask B. If A calls X, the call goes to B. This scenario follows:
•
•
Other inconsistencies could exist in the calling information if further features get performed on a basic call. Cisco recommends that you not configure a calling party transformation mast for a translation pattern that might get applied to JTAPI application-controlled addresses.
Supported JVM Versions
Table 3 lists the supported Java Virtual Machine versions for all the Cisco JTAPI platforms.
Documentation Errata
Be aware of the following issues in the Cisco Unified CallManager JTAPI Developers Guide:
•
•
Cisco Unified TAPI Developers Guide
No changes occurred to Cisco Unified TAPI in Release 5.1(3). As stated previously, beginning with this release, Cisco Unified TAPI supports the Windows Vista platform.
The following sections supplement the Cisco Unified CallManager TAPI Developers Guide.
Hunt List Targets
CTI does not support controlled devices as part of Hunt List members. This could result in erroneous behavior for Cisco Unified TAPI applications.
Translation Pattern
TSP does not support the Translation Pattern because it may cause a dangling call in a conference scenario. The application needs to clear the call to remove this dangling call, or simply close and reopen the line.
Documentation Supplement: New and Changed Information Summary
The following tables summarize changes in Release 5.1 and earlier. This information applies to Release 5.1(3) and all other sub-versions of Release 5.1. The tables indicate whether a feature was Added (A) or Modified (M) in the indicated release. Modifications and changes that are marked with an asterisk (M*) might impact backward compatibility of TAPI applications.
Table 8 TAPI Phone Functions
phoneDevSpecific
A
PhoneGetStatus
A
PhoneReqRTPSnapshot
A
Table 9 TAPI Phone Messages
PHONE_REMOVE
A
Table 10 TAPI Phone Structures
PHONECAPS
M
PHONESTATUS
A
M
SCCP Messaging Guide
No changes to SCCP occurred messages in Release 5.1(3)
SIP Line Messaging Guide (Standard)
No changes to SIP line messages occurred in Release 5.1(3).
Cisco Unified Communications Manager Data Dictionary
Cisco did not update this document for release 5.1(3). For information about AXL schema changes in this release, see AXL Programming.
Cisco Unified Reporting
The Cisco Unified Reporting Administration Guide, a new document, describes how to use the new Cisco Unified Reporting web application. Refer to New Cisco Unified Reporting Application in the "Important Notes" section for a brief description of the application.
Cisco Unified IP Phones
Cisco Unified CallManager 5.1(3) adds support the following phones:
•
•
•
•
Cisco Unified Wireless IP Phone 7921
The Cisco Unified Wireless IP Phone 7921 as a second-generation wireless IP phone extends advanced voice and unified communications capabilities across the enterprise, supporting a host of enhanced calling features, including the following ones:
•
•
•
•
•
Where to Find More Information
•
•
•
•
•
Cisco Unified IP Phone 7962G and 7942G (SCCP and SIP)
The system supports Cisco Unified IP Phones 7962G and 7942G for Cisco Unified CallManager Release 5.1(3) and later. The Cisco Unified IP Phones 7962G and 7942G design meets the needs of businesses with moderate telephone traffic and specific call requirements. The Cisco Unified IP Phones 7962G and 7942G support IEEE 802.3af Power over Ethernet, security, and other calling features. Dedicated hold, redial, and transfer keys facilitate call handling. Illuminated mute and speakerphone keys give a clear indication of speaker status.
Where to Find More Information
•
•
•
•
Cisco Unified IP Phone 7965G and 7945G (SCCP and SIP)
The system supports Cisco Unified IP Phones 7965G and 7945G on Cisco Unified CalManager Release 5.1(3) and later. The Cisco Unified IP Phones 7965G and 7945G design meets the needs of businesses with moderate telephone traffic and specific call requirements. The Cisco Unified IP Phones 7965G and 7945G support IEEE 802.3af Power over Ethernet, security and other calling features. Dedicated hold, redial, and transfer keys facilitate call handling. Illuminated mute and speakerphone keys give a clear indication of speaker status.
Where to Find More Information
•
•
•
•
Cisco Unified IP Phone 7975G (SCCP and SIP)
The system supports Cisco Unified IP Phone 7975G on Cisco Unified CallManager Release 5.1(3) and later. The Cisco Unified IP Phone 7975G design meets the needs of businesses with moderate telephone traffic and specific call requirements. The Cisco Unified IP Phones 7975G supports IEEE 802.3af Power over Ethernet, security, and other calling features. Dedicated hold, redial, and transfer keys facilitate call handling. Illuminated mute and speakerphone keys give a clear indication of speaker status.
Where to Find More Information
•
•
•
Operating System CLI Commands
This section describes Cisco Unified Communications Operating System CLI commands that are added or updated in this release.
file fragmentation sdi
This command displays file fragmentation information about SDI log files.
Command Syntax
file fragmentation sdi
all outfilename
file filename {verbose}
most fragmented number
most recent number
Parameters
•
•
•
•
•
Options
•
Requirements
Command privilege level: 1
Allowed during upgrade: Yes
file fragmentation sdl
This command displays file fragmentation information about SDL log files.
Command Syntax
file fragmentation sdl
all outfilename
file filename {verbose}
most fragmented number
most recent number
Parameters
•
•
•
•
•
Options
•
Requirements
Command privilege level: 1
Allowed during upgrade: Yes
file get
The file get command has the new parameters salog and partBsalog. The file get command sends the file to another system by using SFTP.
Command Syntax
file get
salog directory/filename [reltime] [abstime] [match] [recurs]
partBsalog directory/filename [reltime] [abstime] [match] [recurs]
Parameters
•
•
•
Options
•
•
•
•
Usage Guidelines
After the command identifies the specified files, you get prompted to enter an SFTP host, username, and password.
Requirements
Command privilege level: 0
Allowed during upgrade: Yes
file list
The file list command has the new parameters salog and partBsalog. The file list command lists the log files in an available log directory.
Command Syntax
file list
salog directory [page] [detail] [reverse] [date | size]
partBsalog directory [page] [detail] [reverse] [date | size]
Parameters
•
•
•
Options
•
•
•
•
•
Requirements
Command privilege level: 1 for logs, 0 for TFTP files
Allowed during upgrade: Yes
file view
The file view command has a new system-management-log parameter. The file view command displays the contents of a file.
Command Syntax
file view
system-management-log
Parameters
•
Requirements
Command privilege level: 0
Allowed during upgrade: Yes
set network dhcp
The set network dhcp command is updated as described in this section. This command configures DHCP on Ethernet interface 0. You cannot configure Ethernet interface 1.
Command Syntax
set network dhcp eth0
enable
disable node_ip net_mask gateway_ip
Parameters
•
•
•
•
•
•
Usage Guidelines
The system asks whether you want to continue to execute this command.
Caution
Requirements
Command privilege level: 1
Allowed during upgrade: No
set network restore
This command configures the specified Ethernet port to use a specified static IP address.
Caution
Caution
Command Syntax
set network restore eth0 ip-address network-mask gateway
Parameters
•
•
•
•
Requirements
Command privilege level: 0
Allowed during upgrade: Yes
show ctl
This command displays the contents of the Certificate Trust List (CTL) file on the server. It notifies you if the CTL is not valid.
Command Syntax
show ctl
show diskusage
This command displays information about disk usage on the server.
Command Syntax
show diskusage
activelog {filename filename | directory | sort}
common {filename filename | directory | sort}
inactivelog {filename filename | directory | sort}
install {filename filename | directory | sort}
tftp {filename filename | directory | sort}
tmp {filename filename | directory | sort}
Parameters
•
•
•
•
•
•
Options
•
•
•
Requirements
Command privilege level: 0
Allowed during upgrade: Yes
show environment
This command displays information about the server hardware.
Command Syntax
show environment
fans
power-supply
temperatures
Parameters
•
•
•
Requirements
Command privilege level: 0
Allowed during upgrade: Yes
show iptables
The show iptables command was removed. The utils firewall list command now displays similar information.
show memory
This command displays information about the server memory.
Command Syntax
show memory
count
module [ALL | module_number]
size
Parameters
•
•
•
Options
•
•
show network cluster
This command has a new cluster parameter.
Command Syntax
show network
cluster
Parameters
•
Requirements
Command privilege level: 0
Allowed during upgrade: Yes
show tech database
This command has the new parameters dump and session.
Command Syntax
show tech database
dump
sessions
Parameters
•
•
show tech network
The show tech network command is updated as described in this section. This command displays information about the network aspects of the server.
Command Syntax
show tech network
all [page] [search text] [file filename]
hosts [page] [search text] [file filename]
interfaces [page] [search text] [file filename]
resolv [page] [search text] [file filename]
routes [page] [search text] [file filename]
sockets {numeric}
Parameters
•
•
•
•
•
•
Options
•
•
•
•
Usage Guidelines
The file option saves the information to platform/cli/filename.txt. The file name cannot contain the "." character.
Requirements
Command privilege level: 1
Allowed during upgrade: Yes
show tech runtime
The show tech runtime command is updated as described in this section. This command displays runtime aspects of the server.
Command Syntax
show tech runtime
all [page] [file filename]
cpu [page] [file filename]
disk [page] [file filename]
env [page] [file filename]
memory [page] [file filename]
Parameters
•
•
•
•
•
Options
•
•
Usage Guidelines
The file option saves the information to platform/cli/filename.txt. The file name cannot contain the "." character.
Requirements
Command privilege level: 1
Allowed during upgrade: Yes
show tech system
The show tech system command is updated as described in this section. This command displays system aspects of the server.
Command Syntax
show tech system
all [page] [file filename]
bus [page] [file filename]
hardware [page] [file filename]
host [page] [file filename]
kerenl [page] [file filename]
software [page] [file filename]
tools [page] [file filename]
Parameters
•
•
•
•
•
•
•
Options
•
•
Usage Guidelines
The file option saves the information to platform/cli/filename.txt. The file name cannot contain the "." character.
Requirements
Command privilege level: 1
Allowed during upgrade: Yes
utils create report
This command creates reports about the server in the platform/log directory.
Command Syntax
utils create report
hardware
platform
Parameters
•
•
Usage Guidelines
You are prompted to continue after you enter the command.
After creating a report, use the command file get activelog platform/log/filename, where filename is the report filename that is displayed after the command completes, to get the report.
Requirements
Command privilege level: 0
Allowed during upgrade: Yes
utils fior
This command allows you to monitor the I/O on the server. The File I/O Reporting service provides a kernel based daemon for collecting file I/O per process.
Command Syntax
utils fior
disable
enable
list [start=date-time] [stop=date-time]
start
status
stop
top number [read | write | read-rate | write-rate] [start=date-time] [stop=date-time]
Options
•
•
•
•
•
•
•
•
•
•
•
•
Requirements
Command privilege level: 1
Allowed during upgrade: Yes
utils firewall
This command manages the firewall on the node.
Command Syntax
utils firewall
disable {time}
enable
list
status
Parameters
•
•
–
–
–
If you do not specify a time, the default is 5 minutes.
f you
•
•
•
Requirements
Command privilege level: 0
Allowed during upgrade: Yes
utils network connectivity
This command verifies the node's network connection to the first node in the cluster. It is only valid on a subsequent node.
Command Syntax
utils network connectivity
Requirements
Command privilege level: 0
Allowed during upgrade: Yes
utils service
The utils service command has a new auto-restart parameter. You can enable auto-restart on a service to cause it to automatically restart.
Command Syntax
utils service
auto-restart {enable | disable | show} service-name
Parameters
•
Options
•
•
•
•
Requirements
Command privilege level: 0
Allowed during upgrade: Yes
utils snmp
The utils snmp command has the new parameters get, hardware-agents, and walk.
Command Syntax
utils snmp
get version community ip-address object [file]
hardware-agents [status | restart]
walk version community ip-address object [file]
Parameters
•
•
•
•
•
•
•
•
•
Requirements
Command privilege level: 1
Allowed during upgrade: Yes
Cisco Unified CallManager Serviceability
This section contains the following sub-sections:
•
•
•
•
•
Adding RTMT Performance Counters in Bulk
On the RTMT Perfmon Monitoring pane, in table format only (not in chart format), you can now select multiple counters and multiple instances of counters and add them all with a single click. Prior to this enhancement, you could add them only one at a time.
For more information, see Documentation Updates.
RTMT Database Summary with Database Replication Information
The RTMT database summary predefined monitoring object now includes the following information:
•
•
Start Counter(s) Logging in the Menu Bar
Prior to this release, the RTMT Performance Monitoring window included a Start Counter(s) Logging menu item for each tab, but not at the RTMT top menu bar level. Now, this menu item consistently remains available.
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 effect slows down the operations when IO utilization is in high demand for call processing, so that call processing can take precedence.
For more information, see Documentation Updates.
Trace Compression Support
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 following benefits of tracefile compression apply:
•
•
For more information, see Documentation Updates.
RTMT Critical Services
Cisco Unified CallManager Real-Time Monitoring Tool (RTMT) provides new states for the critical services that display in RTMT. The Critical Services monitoring category (choose Monitor > Server > Critical Services or click the Server button and Critical Services icon) provides the name of the critical service, the status (whether the service is starting, up, stopping, down, stopped by the administrator, not activated, or in an unknown state), and the elapsed time during which the services have existed in a particular state for a particular Cisco Unified CallManager node. For a specific description of each state, review the following information:
•
•
•
•
Tip
•
•
•
Preconfigured Alerts
The Preconfigured Alerts chapter of the Cisco Unified CallManager Serviceability Guide contains the following alerts.
•
•
•
•
•
•
•
RTMT Services, Servlets and Service Parameters
The list of RTMT Services, Servlets, and Service Parameters now includes RisDC .
Supported Operating Systems
The list of supported operating systems now includes Windows Vista.
For More Information
•
•
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.
Caveats describe unexpected behavior on a Cisco Unified CallManager 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 CallManager Release 5.1(2a) by using Bug Toolkit, which is an online tool that is available for customers to query defects according to their own needs.
Tip
To access the Bug Toolkit, log on to http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.
UsingBug Toolkit
The system grades known problems (bugs) according to severity level. These release notes contain descriptions of the following bug levels:
•
•
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
Tip
Open Caveats
Table 11 describes possible unexpected behaviors in Cisco Unified CallManager Release 5.1(2a), which are sorted by component.
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 CallManager interim versions in which the defect was fixed. These interim versions then get integrated into Cisco Unified CallManager 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 CallManager 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 CallManager 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
.
Documentation Updates
Updates to Cisco Unified Communications Manager 5.1(3) Documentation provides information about omissions, errors, or updates for the documentation that supports Cisco Unified Communications Manager 5.1(3x).To obtain this document, go to the following URL:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/5_1_3/cucm-doc_updates-513.html
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, 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
Cisco Product Security Overview
This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at: http://www.cisco.com/wwl/export/crypto/tool/stqrg.html. If you require further assistance please contact us by sending email to export@cisco.com.
CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath 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. (0708R)
