Table Of Contents
Release Notes for Cisco Unified CallManager Release 5.1(3a)
Determining the Software Version
Cisco Unified CallManager Release 5.1(3a) Installed on a 5.1(3) Engineering Special
Venezuela Implements New Timezone
Clarification for Call Park Configuration
Upgrading to Cisco Unified CallManager 5.1(3x)
Address Resolution Protocol (ARP) Table Can Fill Up Quickly
Do Not Upgrade from Cisco Unified CallManager 5.1(3) to Cisco Unified Communications Manager 6.0(1x)
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 Cisco Unified CallManager is Upgraded
iLO Flashing Causes the Login Window to Disappear After Installation or Upgrade
Serviceability Session Timeout Not Graceful
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
Incorrect Information for Voice Mail Port Name Field in Help for This Page
Call Forward All Call Search Space Backward Compatibility Not Documented
CTI Does Not Support Members of Line Groups
Certificate Documentation Not Provided for Microsoft Internet Explorer 7.0
Documentation Does Not List Correct Browser Support
Documentation Does Not State That Last Name Is Required for LDAP Synchronization
Documentation Does Not State the Minimum Requirement for the Perform a Re-sync Every Field
Restrictions Not Documented for the User ID Field in the End User Configuration Window
RTMT Trace and Log Central Disk IO and CPU Throttling
Adding RTMT Performance Counters in Bulk
Time-of-Day Routing Chapter Omits Information About Defined Time Periods
Number of Supported Locations and Regions Increased
Description of Create all new ports like port 1 Button Incorrect
Message Waiting Configuration Field Descriptions
Media Resource Group Configuration Field Description
Transcoder Configuration Field Description
Application and End User CAPF Profile Configuration Instance ID Setting
Incorrect Description for User ID Field End User, Phone, DN, and LA Configuration Window
Incorrect Information on How to Install Assistant Console Application
Incorrect Information for Description Field in the Message Waiting Configuration Window
Restoring Data to a Subsequent Node
Configuring a Custom Background Image
Incorrect URL for the Cisco Unified CallManager User Option Pages
Incorrect Information on Configuring Partitions and DNs for JTAPI/TAPI Controlled Devices
Default Device Profile Information
Using Cisco Extension Mobility Description in Cisco Unified IP Phone User Guides
Recovering Administrator and Security Passwords
Changing a Cisco Unified CallManager Server IP Address
IPMA Assistant Console Installation and Windows Vista Support
Devices That are Associated with the Attendant Console Application User
Third-Party Certificate Authority Verification
Obtaining Documentation, Obtaining Support, and Security Guidelines
Cisco Product Security Overview
Release Notes for Cisco Unified CallManager Release 5.1(3a)
July 09, 2009
This document includes
•
Information that was contained in the Release Notes for Cisco Unified CallManager Release 5.1(3)
•
Note
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, the call-processing component of the Cisco Unified Communications System, extends enterprise telephony features and capabilities to IP phones, media processing devices, voice-over-IP (VoIP) gateways, mobile devices, and multimedia applications.
System Requirements
Make sure that you install and configure Cisco Unified CallManager Release 5.1(3x) 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 2 lists the URLs from which you download the software.
Table 2 Download URLs for Software Upgrades
Cisco Unified CallManager 5.1
Locale installers
http://www.cisco.com/kobayashi/sw-center/telephony/callmgr/ locale-installer.shtm
Phone firmware
http://www.cisco.com/pcgi-bin/tablebuild.pl/ip-7900ser
http://www.cisco.com/pcgi-bin/tablebuild.pl/ip-7900ser-crypto
Cisco Security Agent (CSA)
Upgrade Assistant
http://www.cisco.com/pcgi-bin/tablebuild.pl/callmgr-utilpage
Related Documentation
The 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
Important Notes for Cisco Unified CallManager Release 5.1(3a)
The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco Unified CallManager Release 5.1(3a).
•
•
•
•
•
Important Notes for Cisco Unified CallManager Release 5.1(3)
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).
•
•
•
•
•
•
•
•
•
•
•
Cisco Unified CallManager Release 5.1(3a) Installed on a 5.1(3) Engineering Special
Because Cisco Unified CallManager Release 5.1(3a) does not contain all the fixes in the 5.1(3) Engineering Specials (ES), installing Cisco Unified CallManager 5.1(3a) release on a 5.1.3 Engineering Special might result in the loss of some or all fixes that are contained the Engineering Special.
To obtain a release that contains all the fixes in the Cisco Unified CallManager 5.1(3a) release and the ES you are currently running, go to: http://www.cisco.com/pcgi-bin/tablebuild.pl/CUCM-ES5X
If no Engineering Special that contains the fixes included in your ES and Release 5.1(3a) exists, contact TAC.
Australia Summer Time
This year, Australia Summer Time ends on April 6, 2008.
Summer Time begins again at 2:00AM October 5, 2008 (the first Sunday in October) and ends at 2:00AM on April 5, 2009 (the first Sunday in April).
This release of Cisco Unified CallManager includes the specific dates for the Australia Summer Time changes for this year.
Venezuela Implements New Timezone
Venezuela implemented a new time zone that is one-half hour behind the previous timezone (GMT-4).
Cisco Unified CallManager Release 5.1(3a) incorporates this new timezone into Cisco products used in Venezuela.
Brazil Daylight Saving Time
In 2007, most southern states in Brazil observed the beginning of Daylight Saving Time (DST) on Sunday, October 14, 2007. Those same states will observe the end of DST on Sunday, February 17, 2008 by setting clocks back one hour.
Cisco Unified CallManager Release 5.1(3a) incorporates this reversion into Cisco products used in Brazil.
Note
Clarification for Call Park Configuration
Consider the following information when you configure Call Park:
Call Park numbers cannot overlap between Cisco Unified CallManager servers. Ensure that each Cisco Unified CallManager server has its own unique number range.
Call Park numbers may have an associated partition that restricts access to the Call Park numbers and prevents retrieval of parked calls. If partitions are used to restrict access to Call Park numbers, a unique call park number or range of call park extension numbers must be defined for each partition on each Cisco Unified CallManager in the cluster.
When the end user invokes Call Park, Cisco Unified CallManager attempts to find an available Call Park number from a Call Park partition that is currently accessible via the calling search space for the party that invoked Call Park.
Upgrading to Cisco Unified CallManager 5.1(3x)
If you are upgrading from 4.1.3, or 4.2.3,, use the Product Upgrade Tool (PUT) or the PUT for registered customers only to obtain a media kit and license or purchase the upgrade from Cisco Sales.
To use the PUT, you are required to enter your Cisco Software Application Support Plus Upgrades (SASU) contract number and request the CD/CD set. If you do not have a SASU contract, you must purchase the upgrade from Cisco Sales.
For more information about supported CUCM upgrades, see the Cisco Unified Communications Manager Compatibility Matrix at the following URL:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html
Address Resolution Protocol (ARP) Table Can Fill Up Quickly
Do not install Cisco Unified CallManager in a large Class A or Class B subnet that contains a large number of devices because the Address Resolution Protocol (ARP) table can fill up quickly (maximum 1024 entries, by default). When the ARP table gets full, Cisco Unified CallManager can have difficulty talking to endpoints and cannot add more phones.
Do Not Upgrade from Cisco Unified CallManager 5.1(3) to Cisco Unified Communications Manager 6.0(1x)
You cannot successfully upgrade from Cisco Unified CallManager Release 5.1(3) to Cisco Unified Communications Manager Release 6.0(1x). The supported upgrade path for release 5.1(3x) is release 6.1(1x) or higher.
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.
Ensure JRE is present to provide all 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 that is shown in Figure 1 due to a limitation in the InstallAnywhere software. This one-time popup displays only when you are 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 Cisco Unified CallManager is Upgraded
If you are running the Cisco Unified Communications Real-Time Monitoring Tool (RTMT) client and monitoring performance counters during a Cisco Unified CallManager 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 display 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. 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. The only workaround requires you to log out by 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.
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 release 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 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
•
•
–
–
Refer to New Cisco Unified Reporting Application in the"Important Notes" section for a brief description of the application.
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 4.
Route Patterns, Automated Alternative Routing, and Applications
Cisco Unified CallManager only applies Automated Alternative Routing (AAR) to the endpoints that it controls. Network 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 SessionHandle element contains an incorrect value for the type attribute. 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 4 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 9 TAPI Phone Functions
phoneDevSpecific
A
PhoneGetStatus
A
PhoneReqRTPSnapshot
A
Table 10 TAPI Phone Messages
PHONE_REMOVE
A
Table 11 TAPI Phone Structures
PHONECAPS
M
PHONESTATUS
A
M
SCCP Messaging Guide
No changes to SCCP messages occurred 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:
•
•
•
•
Note
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 gets 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
Although 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
This section describes the show tech network command updates. 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
This section describes the show tech runtime command updates. 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
This section describes the show tech system command updates. 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 specifies the report filename that displays 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 equals 5 minutes.
f you
•
•
•
Requirements
Command privilege level: 0
Allowed during upgrade: Yes
utils network connectivity
This command verifies the node network connection to the first node in the cluster. Be aware that 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 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(3a) 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://tools.cisco.com/Support/BugToolKit.
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 12 describes possible unexpected behaviors in Cisco Unified CallManager Release 5.1(3a), 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
This section provides documentation changes that were unavailable when the Cisco Unified CallManager Release 5.1(3) documentation suite was released.
Omissions
This section contains information on the following topics:
•
•
•
•
•
•
•
•
•
•
•
Incorrect Information for Voice Mail Port Name Field in Help for This Page
The Port Name field allows 1 to 45 characters including letters, numbers, dots, underscores and dashes, followed by -VI and the port number (from 1 to 96).
Barge Phone Display Messages
When a user initiates a barge to a SIP device, the barge initiator phone displays "To Barge <Display name> (Shared Line DN)."
When a user initiates a barge to a SCCP device, the barge initiator phone displays "To Barge <Display name>."
Call Forward All Call Search Space Backward Compatibility Not Documented
The Cisco Extension Mobility chapter in the Cisco Unified Features and Services Guide does not provide information on backward compatibility for the Call Forward All calling search space.
This enhancement allows Cisco Unified CallManager Release 4.x customers who are using device mobility and extension mobility to upgrade to Cisco Unified CallManager Release 5.1 without loss of functionality.
The new service parameter (CFA CSS Activation Policy) supports this enhancement. In the Service Parameter Configuration window, this parameter displays in the Clusterwide Parameters (Feature - Forward) section with two options.
•
•
If you select the With Configured CSS option, the Forward All Calling Search Space that is explicitly configured in the Directory Number Configuration window controls the forward all activation and call forwarding. If the Forward All Calling Search Space is set to None, no calling search space gets configured for Forward All. A forward all activation attempt to any directory number with a partition will fail. No change in the Forward All Calling Search Space and Secondary Calling Search Space for Forward All occurs during the forward all activation.
If you prefer to use the combination of the Directory Number Calling Search Space and Device Calling Search Space without explicitly configuring a Forward All Calling Search Space, select With Activating Device/Line CSS for the CSS Activation Policy. For this option, when Forward All is activated from the phone, the Forward All Calling Search Space and Secondary Calling Search Space for Forward All automatically get populated with the Directory Number Calling Search Space and Device Calling Search Space for the activating device.
With this configuration (Calling Search Space Activation Policy set to With Activating Device/Line), if the Forward All Calling Search Space is set to None, when forward all is activated through the phone, the combination of Directory Number Calling Search Space and activating Device Calling Search Space gets used to verify the forward all attempt.
By default, the value of the CFA CSS Activation Policy service parameter gets set to With Configured CSS.
Roaming
When a device is roaming in the same device mobility group, Cisco Unified CallManager uses the Device Mobility CSS to reach the local gateway. If a user sets Call Forward All at the phone, the CFA CSS gets set to None, and the CFA CSS Activation Policy gets set to With Activating Device/Line CSS; then,
•
•
•
For more information about configuration options for Call Forward All, see the Directory Number Configuration chapter in the Cisco Unified CallManager Administration Guide and the Understanding Directory Numbers chapter in the Cisco Unified CallManager System Guide.
CTI Does Not Support Members of Line Groups
The Cisco Unified CallManager Administration Guide and Cisco Unified CallManager System Guide omit the following restriction: If a DN is a member of a line group or hunt list, you should not associate any device (CTI port, CTI route point, SCCP phone, or SIP phone) that uses that DN with a CTI user.
CTI ports and CTI route points with directory numbers (DNs) that are members of line groups and, by extension, that are members of hunt lists. If a DN is a member of a line group or hunt list, you cannot associate that DN with either a CTI port (that you configure with the Phone Configuration window) nor with a CTI route point (that you configure with the CTI Route Point Configuration window).
If you configure a DN as part of a line group, you cannot associate that DN with a CTI port nor a CTI route point. Conversely, when you configure a CTI port or CTI route point, you cannot specify a DN that already belongs to a line group or to a hunt list.
Certificate Documentation Not Provided for Microsoft Internet Explorer 7.0
The Cisco Unified CallManager Administration Guide and Cisco Unified CallManager System Guide do not provide information on importing the certificate for Internet Explorer 7.0. For information on importing the certificate for Internet Explorer 7.0, see the "Internet Explorer 7 Certificate Support" section.
Documentation Does Not List Correct Browser Support
The Cisco Unified CallManager Administration Guide and Cisco Unified CallManager System Guide do not list all browsers that are supported with Cisco Unified CallManager Administration In Release 5.1(3). For the current list of supported browsers, see the "General Administration Enhancements" section.
Documentation Does Not State That Last Name Is Required for LDAP Synchronization
The Cisco Unified CallManager documentation does not include the following information.
When you configure a user in Microsoft Windows Server 2000 and Windows Server 2003 Active Directory (AD), Netscape/iPlanet Directory, Sun ONE Directory Server 5.1, and Sun Java System Directory Server 5.2, ensure that you configure a last name for the user. After you configure LDAP synchronization in Cisco Unified CallManager Administration, users without last names in the corporate directory do not synchronize with the Cisco Unified CallManager database. No error displays in Cisco Unified CallManager Administration, but the log file indicates which users did not synchronize.
Documentation Does Not State the Minimum Requirement for the Perform a Re-sync Every Field
The Cisco Unified CallManager Administration Guide does not state the minimum requirement for the Perform a Re-sync Every Field in the LDAP Directory window in Cisco Unified CallManager Administration. Cisco Unified CallManager can synchronize directory information every 6 hours, which is the minimum requirement for the Perform a Re-Sync Every Field.
Using the G.722 Codec
The Cisco Unified CallManager Administration Guide and the Cisco Unified CallManager System Guide do not provide the following information on the G.722 codec.
Cisco Unified CallManager 5.1(3) supports the Advertise G.722 Codec enterprise parameter, which determines whether Cisco Unified IP Phones will advertise the G.722 codec to Cisco Unified CallManager. Codec negotiation involves two steps. First, the phone must advertise the supported codec(s) to Cisco Unified CallManager (not all phones support the same set of codecs). Second, when Cisco Unified CallManager gets the list of supported codecs from all phones that are involved in the call attempt, it chooses a commonly supported codec based on various factors, including the region pair setting. This parameter only applies to Cisco Unified IP Phone 7941G, 7941G-GE, 7961G, 7961G-GE, 7970G, and 7971G-GE. Valid values specify True (the specified Cisco Unified IP Phones advertise G.722 to Cisco Unified CallManager) or False (the specified Cisco Unified IP Phones do not advertise G.722 to Cisco Unified CallManager).
Note
The Product-Specific Configuration area in the Phone Configuration window supports the parameter, Advertise G.722 Codec. Use this parameter to override the enterprise parameter on an individual phone basis.
Table 13 indicates how the phone responds to the configuration options.
Cisco Unified CallManager supports G.722, which is a wideband codec, as well as a propriety codec simply named Wideband. Both represent wideband codecs. Wideband codecs such as G.722 provide a superior voice experience because wideband frequency response is 200 Hz to 7 kHz compared to narrowband frequency response of 300 Hz to 3.4 kHz. At 64 KB/s, the G.722 codec offers conferencing performance and good music quality.
When users use a headset that supports wideband, they experience improved audio sensitivity when the wideband setting on their phones is enabled (it remains disabled by default). To access the wideband headset setting on the phone, users choose the Settings icon > User Preferences > Audio Preferences > Wideband Headset. Users should check with their system administrator to be sure their phone system is configured to use G.722 or wideband. If the system is not configured for a wideband codec, they may not detect any additional audio sensitivity, even when they are using a wideband headset.
The following Cisco Unified IP Phones (both SCCP and SIP) support the wideband codec G.722 for use with a wideband headset:
•
•
•
•
•
•
When you choose a G.711 or G.722 codec in Region Configuration, you are choosing the bandwidth utilization. Choosing either codec produces the same effect. When you choose either G.711 or G.722, these codecs disallow selecting codecs that have a payload greater than 64 KB/s, such as the G.722 wideband codec and Advanced Audio Codec (ACC) (when ACC uses more than one channel).
If you choose a region that is lower than G.711 or G.722, the Advertise G.722 Codec enterprise parameter gets ignored because the system does not allow G.722, G.711, AAC, and wideband.
Tip
Tip
When enabled, the service parameter allows Cisco Unified IP Phones (such as 7971, 7970, 7941, 7961) to negotiate and use the G.722 codec when calls are within the same region.
If individual phone control and use of a specific codec type is required (for example, G.711), check the configuration of each phone (by using Phone Configuration) for the parameter Advertise G.722 Codec and change the setting to Disabled. Save and reset the device.
Note
Restrictions Not Documented for the User ID Field in the End User Configuration Window
The Cisco Unified CallManager Administration Guide does not state that you can enter any character, including alphanumeric and special characters, in the User ID field in the End User Configuration window in Cisco Unified CallManager Administration. No character restrictions exist for this field.
Tip
CTI Monitored Lines
To calculate the number of CTI monitored lines in a system, use the following formula:
number of pilot point DNs + (number of clients open * number of directory numbers per phone) + (number of parked directory numbers * number of open clients) = CTI Monitored Lines
Shared Line Configuration
The Tips section for Shared Line Appearance in the Cisco Unified CallManager System Guide and the Directory Number Configuration chapter in the Cisco Unified CallManager Administration Guide require this addition:
Shared lines always have identical DN settings, except for the field sections in the Directory Number Configuration window that contains the naming convention "on Device SEPXXXXXXXXXXXX," which are maintained/mapped to a specific device.
If you add a shared line to a device, the shared DN configuration settings, such as Calling Search Space and Call Forward and Pickup, display. If these DN configuration settings are changed, the new settings apply to all the shared lines.
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 means that the operations are slowed when IO utilization is in high demand for call processing, so call processing can take precedence.
When a user makes a request for an on demand operation when the call processing node is running under high IO conditions, the system now displays a warning which gives the user the opportunity to abort the operation. Be aware that the IO rate threshold values control when the warning displays are configurable with the following new service parameters (CiscoRIS Data Collector Service):
•
•
The values of these parameters get compared to the system actual CPU and IOWait values. If the goal (the value of the service parameter) is lower than the actual value, the system issues a warning.
For More Information
•
Trace Compression Support
This feature enables the ROS (Recoverable Outstream) library to support the compressed output of tracefiles. The files are compressed as they are being generated. The benefits of tracefile compression include:
•
•
Use the new enterprise parameter, Trace Compression, to enable or disable trace compression. The default value for this parameter is Disabled. For information on setting the values of enterprise parameters, see the Enterprise Parameters Configuration chapter in the Cisco Unified Communications Manager Administration Guide.
Caution
You can recognize compressed files by their .gz extension (.gzo if the file is still being written to). To open a compressed file, double click the file name and the file opens in the log viewer.
For More Information
•
Adding RTMT Performance Counters in Bulk
The Cisco Unified CallManager Serviceability Administration Guide omits the following information about adding multiple counters and instances of counters in a single add operation.
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.
In table format, be aware that all the following methods are now available for selecting counters to view:
•
•
•
•
•
•
In chart format makes the following methods available:
•
•
If you attempt to add multiple counters at one time while in chart format, a message displays to indicate that you can only select a single counter or instance while in chart format.
For more information about performance monitoring, see the Configuring and Using Performance Monitoring chapter in the Cisco Unified CallManager Serviceability Administration Guide.
Time-of-Day Routing Chapter Omits Information About Defined Time Periods
The "Time-of-Day Routing" chapter of the Cisco Unified Communications Manager System Guide omits the following information.
•
Example:
Consider the following example:
•
•
In this case, on December 31st, the afterofficehours period will not be considered because it gets overriden by the more specific newyearseve period.
Errors
This section contains information on the following topics:
•
•
•
•
•
•
•
•
•
•
•
•
•
Cisco Unified IP Phone 7970 Series Administration Guide for Cisco Unified CallManager, Release 5.1 (for models 7970G and 7971G-GE) (SCCP)
The Cisco Unified IP Phone 7970 Series Administration Guide for Cisco Unified CallManager Release 5.1 (SCCP) incorrectly documents where the List.xml file is stored in the TFTP server. The following sections provide the correct procedure.
List.xml File Format Requirements
The List.xml file defines an XML object that contains a list of background images. The following subdirectory on the TFTP server stores the List.xml file:
/Desktops/320x212x12
Tip
For more information, see the Cisco TFTP chapter in Cisco Unified CallManager System Guide and the Software Upgrades chapter in Cisco Unified CallManager Operating System Administration Guide.
The List.xml file can include up to 50 background images. The images occur in the order in which they appear in the Background Images menu on the phone. For each image, the List.xml file contains one element type, called ImageItem. The ImageItem element includes these two attributes:
•
•
The following example shows a List.xml file that defines two images. Ensure the required Image and URL attributes are included for each image. The TFTP URI that is shown in the example represents the only supported method for linking to full-size and thumbnail images. Be aware that HTTP URL support is not provided.
List.xml Example
<CiscoIPPhoneImageList>
<ImageItem Image="TFTP:Desktops/320x212x12/TN-Fountain.png"
URL="TFTP:Desktops/320x212x12/Fountain.png"/>
<ImageItem Image="TFTP:Desktops/320x212x12/TN-FullMoon.png"
URL="TFTP:Desktops/320x212x12/FullMoon.png"/>
</CiscoIPPhoneImageList>
The Cisco Unified IP Phone firmware includes a default background image. The List.xml file does not define this image. The default image always represents the first image that appears in the Background Images menu on the phone.
Obtaining a License File
Licensing helps manage Cisco Unified CallManager licenses and enforces the licenses for Cisco Unified CallManager nodes and devices.
The Cisco Unified CallManager Administration Guide and Cisco Unified CallManager System Guide contain incomplete information on obtaining and uploading licenses.
The following sections provide the correct information on obtaining licenses for new Cisco Unified CallManager nodes and/or devices as well as for Cisco Unified CallManager nodes that have been upgraded from various releases.
Note
Note
To obtain and upload a license, see the section that applies to your situation:
•
•
New Cisco CallManager Servers and Devices
Use the following procedure to obtain a node license file for new Cisco Unified CallManager servers and to obtain device licenses for new devices that require additional device license units.
Each node in your cluster requires one node license unit. Each device type requires a fixed number of licenses units, depending on the type. For example, Cisco Unified IP Phone 7920 requires four license units, and Cisco Unified IP Phone 7970 requires five units. If you want licenses for four Cisco Unified IP Phones 7920 and four Cisco Unified IP Phones 7970 phones, you require 36 phone license units.
You use the Product Authorization Key (PAK) that came with your product to obtain the necessary permanent licenses, as described in the following procedure.
Procedure
Step 1
Step 2
Step 3
Note
The system sends the license file(s) to you via e-mail by using the e-mail ID that you provided. The format of a license file specifies CCM<timestamp>.lic. If you retain the .lic extension, you can rename the license file. You cannot use the license if you edit the contents of the file in any way.
Note
Step 4
Note
Upgrading From Cisco Unified CallManager 4.x Releases
When you upgrade from supported Cisco Unified CallManager Manager 4.x releases, the system calculates the licenses that are required for existing devices and Cisco Unified CallManager nodes and generates an intermediate file (XML file) that contains this information. You use this file to obtain license files that you can upgrade into Cisco Unified CallManager Administration. You receive these licenses free of cost because you are already using these phones for a Cisco Unified CallManager 4.x release.Use the following procedure to obtain licenses for Cisco Unified CallManager when upgrading from supported 4.x releases.
Note
Procedure
Step 1
The License File Upload window displays.
Step 2
Step 3
Step 4
Step 5
Step 6
The system sends the license file to you via e-mail by using the e-mail address that you provided.
Step 7
Step 8
Uploading a License file
Use the following procedure to upload a license file to the Cisco Unified CallManager server with the matching MAC address that is provided when a license file is requested. For information about obtaining a license file, see the "Obtaining a License File" section. The Cisco Unified CallManager server where the license file is loaded takes on the functionality of the license manager.
Note
Procedure
Step 1
The License File Upload window displays.
Step 2
Note
Step 3
The Upload File pop-up window displays.
Step 4
Note
Step 5
After the upload process completes, the Upload Result file displays.
Step 6
Step 7
Note
License File Contents
The Cisco Unified CallManager System Guide does not include the following example of a permanent Cisco Unified CallManager node license:
Example 0-1 Permanent CCM_Node licenses
# Optional usage agreement, legal language, tracking information# Some other commentsINCREMENT CCM_NODE cisco 5.0 permanent uncounted \VENDOR_STRING=<Count>3</Count><OrigMacId>000BCD4EE59D</OrigMacId><LicFileVersion>1.0</LicF ileVersion> \HOSTID=000bcd4ee59d \NOTICE="<LicFileID>20050826140539162</LicFileID><LicLineID>1</LicLineID> \<PAK></PAK>" SIGN="19B3 4C6C 25AC 6D22 4D75 DE6A 656B 08C5 \30E4 16DB 771B 1393 9DC1 DBC4 C5AA 15CC 6E6C B7B8 895A DCBA \B40F C551 2625 1C97 F20D 9977 6CFF 3603 081E 6FF2"The preceding license file includes the following information:
•
•
•
•
Number of Supported Locations and Regions Increased
The Cisco Unified CallManager System Guide and Cisco Unified CallManager Administration Guide incorrectly state the number of regions and locations that Cisco Unified CallManager supports.
Cisco Unified CallManager supports up to 1000 locations and up to 2000 regions. The following limitations and restrictions apply:
•
•
•
Description of Create all new ports like port 1 Button Incorrect
The Cisco Unified CallManager Administration Guide describes the Create all new ports like port 1 button incorrectly. When you configure the button, use the following information.
The Create all new ports like port 1 button allows you to create ports 2 through 48 with the same parameters and settings as port 1, only if ports 2 through 48 are not configured.
Message Waiting Configuration Field Descriptions
The descriptions that are provided in the Cisco Unified CallManager Administration Guide do not match the allowed values for various fields. The following table contains the revised field descriptions.
Media Resource Group Configuration Field Description
The description that is provided in the Cisco Unified CallManager Administration Guide does not match the allowed values for the Description field of the Media Resource Group Configuration window. The following table contains the revised field description.
Transcoder Configuration Field Description
The description that is provided in the Cisco Unified CallManager Administration Guide does not match the details for the Description field of the Transcoder Configuration window. The following table contains the revised field description.
Application and End User CAPF Profile Configuration Instance ID Setting
The Application and End User CAPF Profile Configuration Settings table in the Cisco Unified CallManager Security Guide incorrectly states that the Instance Id field allows these characters: dots (.), dashes(-) and underscore (_). The Instance ID field allows only alphanumeric characters (a-zA-Z0-9).
Incorrect Description for User ID Field End User, Phone, DN, and LA Configuration Window
The Cisco Unified CallManager Administration Guide incorrectly describes the User ID field that displays in the End User, Phone, DN, and LA Configuration window in Cisco Unified CallManager Administration. When you configure that field, use the following information instead of the information in the administration guide: Enter the end user identification name. Cisco Unified CallManager does not permit modifying the user ID after it is created. You may use the following special characters: =, +, <, >, #, ;, \, , ""
Incorrect Information on How to Install Assistant Console Application
The Cisco Unified CallManager Features and Services Guide incorrectly describes how to obtain the assistant console application for Cisco Unified CallManager Assistant. In Release 5.1(3), the assistant no longer obtains the assistant console application via the URL that is listed in the guide. Instead, the assistant must download the Cisco Unified CallManager Assistant plug-in from Cisco Unified CallManager Administration (choose Applications > Plugins), as described in the "Cisco Unified CallManager Assistant" section.
The Cisco Unified CallManager Features and Services Guide does not state that the assistant console application supports Windows Vista.
Disregard the entire section, Assistant Console Dialog Options, in the Cisco Unified CallManager Features and Services Guide. Instead, use the information in the "Cisco Unified CallManager Assistant" section.
Incorrect Information for Description Field in the Message Waiting Configuration Window
The Cisco Unified CallManager Administration Guide incorrectly states that you can enter up to 30 characters in the Description field in the Message Waiting Configuration window in Cisco Unified CallManager Administration. You can enter up to 50 characters.
Restoring Data to a Subsequent Node
The Restoring Subsequent Cluster Nodes section of the Disaster Recovery System Administration Guide incorrectly states that you must restore a subsequent node by restoring it from the same DRS backup file that you used to restore the first node.
Instead, you restore a subsequent node by performing a restore operation on the first node in the cluster. The Restore wizard allows you to select which nodes to restore and prompts you to enter the location of the directory where you backed up your data by using DRS. You do not specify a backup file within this directory. DRS automatically obtains the correct backup data to restore the nodes that you selected.
Cisco Unified IP Phone 7902G, 7905G, and 7912G Administration Guide for Cisco Unified CallManager Release 5.0 (SCCP)
The Cisco Unified IP Phone 7902G, 7905G, and 7912G Administration Guide for Cisco Unified CallManager Release 5.0 (SCCP) incorrectly documents how an administrator should customize the 7905G and 7912G phones logo. The following sections provide the correct procedure.
Configuring a Custom Background Image
To configure custom background images for the Cisco Unified IP Phone, follow these steps:
Procedure
Step 1
bmp2logo imageID image.bmp image.logo
where:
•
•
Note
For example, if the image identifier is 10 and the base name of your image file is mylogo, enter this command:
bmp2logo 10 mylogo.bmp mylogo.log
Step 2
/
Note
Step 3
upgradelogo:imageID,TFTPServerID,image.logo
where:
•
•
•
For example, if the image identifier is 10, the converted file is stored on the same TFTP server as the Cisco Unified IP Phone configuration file, and the base name of the converted image file specifies mylogo, add the following line to the configuration file:
upgradelogo:10,0,mylogo.logo
Note
Step 4
Step 5
/
Note
To upload the files, choose Software Upgrades > Upload TFTP Server File in Cisco Unified OS Administration. For more information, see the "Software Upgrades" chapter in Cisco Unified Communications Operating System Administration Guide.
You must also copy the customized binary files to the other TFTP servers that the phone may contact to obtain these files.
Note
Note
Step 6
The new graphic displays when the phone restarts
Incorrect URL for the Cisco Unified CallManager User Option Pages
The Cisco WebDialer chapter in the Cisco Unified CallManager Features and Services Guide provides an incorrect URL for the Cisco Unified CallManager User Option Pages. The URL should read
https://<IP address of the Cisco Unified CallManager server>:8443/ccmuser/showhome.do.
Incorrect Information on Configuring Partitions and DNs for JTAPI/TAPI Controlled Devices
Disregard the following note in the Directory Number Configuration chapter in the Cisco Unified CallManager Administration Guide: If a JTAPI or TAPI application controls or monitors a device, you should not configure multiple instances of the same DN (with different partitions) on that device.
In fact, if a JTAPI or TAPI application controls a device, you can configure multiple instances of the same DN (with different partitions) on that device.
Default Device Profile Information
The Default Device Profile Configuration chapter of the Cisco Unified CallManager Administration Guide incorrectly states that the Default Device Profile can be configured to subscribe to services. Disregard the following text:
•
•
rtmt.log Storage Location
The Trace Collection and Log Central in RTMT chapter of the Cisco Unified CallManager Serviceability Administration Guide inaccurately describes the storage location of the rtmt.log file. The correct information follows:
Updating the Trace Configuration Setting for RTMT
To edit trace settings for the Real-Time Monitoring plug-in, choose Edit > Trace Settings; then, click the radio button that applies. The system stores the rtmt.log file in the Documents and Settings directory for the user; for example, on a Windows machine, the log gets stored in C:\Documents and Settings\<userid>\.jrtmt\log.
Updates
This section contains updates that have occurred since the release of the Cisco Unified CallManager 5.1(3) documentation. These changes may not appear in the current documentation or the online help for Cisco Unified CallManager:
•
•
•
Single Sign-On Capability
The Application Users and End Users chapter of the Cisco Unified CallManager System Guide requires this update for single sign-on capability:
Administrator users in the Standard Unified CM Super Users group can access all administrative applications in the Cisco Unified CallManager Administration navigation menu (Cisco Unified CallManager Administration, Cisco Unified Serviceability, and Cisco Unified Reporting) with a single sign-on to one of the applications.
You set the default Administrator username and password during Cisco Unified CallManager installation. You can change the Administrator password or set up a new Administrator account in the Application User Configuration window in Cisco Unified CallManager Administration.
Using Cisco Extension Mobility Description in Cisco Unified IP Phone User Guides
The following information on extension mobility needs updating in the Cisco Unified IP Phone Guide (all phone models).
Cisco Extension Mobility (EM) allows you to temporarily configure a Cisco Unified IP Phone as your own. After you log in to EM, the phone adopts your user profile, including your phone lines, features, established services, and web-based settings. Your system administrator must configure EM for you.
Tips
•
•
•
•
Recovering Administrator and Security Passwords
This section replaces the Recovering the Administrator Password section in the Log In To Cisco Unified Communications Operating System Administration chapter of the Cisco Unified Communications Operating System Administration Guide for releases 5.0(4), 5.1(1), and 6.0(1).
If you lose the administrator password or security password, use the following procedure to reset these passwords.
Note
Procedure
Step 1
•
•
The Welcome to platform password reset window displays.
Step 2
Step 3
Step 4
The system tests to ensure that you have removed the CD or DVD from the disk drive.
Step 5
The system tests to ensure that you have inserted the disk.
Step 6
•
•
•
Step 7
Step 8
The password must contain at least 6 characters. The system checks the new password for strength. If the password does not pass the strength check, you get prompted to enter a new password.
Step 9
Caution
Changing a Cisco Unified CallManager Server IP Address
To change the IP address of a Cisco Unified CallManager server, refer to the following document:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080094601.shtml
Changes
This section contains changes that have occurred since the release of the Cisco Unified CallManager 5.1(3) documentation. These changes may not appear in the current documentation or the online help for Cisco Unified CallManager:
•
•
•
IPMA Assistant Console Installation and Windows Vista Support
The following changes that have been made to IPMA Assistant Console installation support Windows Vista.
The URL-based installation no longer gets supported by Cisco Unified CallManager Administration and is available only via the Cisco Unified CallManager Administration plug-in download page.
Procedure
Step 1
Step 2
Step 3
CDR Search Report GUI
The CDR Search Report GUI windows changed to show both the UTC and Local time of the server, including the date and time string (time string format equals HH:MM:SS), as in Aug 31, 2007 12:00:00. The default ToDate search criteria changed to be that of the time of the server in UTC and the default FromDate got set to 1 hour earlier than the ToDate.
Devices That are Associated with the Attendant Console Application User
The Cisco Unified CallManager Features and Services Guide incorrectly states that administrators who are configuring Cisco Unified CallManager Attendant Console must associate devices with the Cisco Unified CallManager Attendant Console ac application user, unless the administrators enable the superprovider feature.
The document should state that administrators must always enable the superprovider feature by associating the ac application user with the user group"Standard CTI Allow Control of All Devices and must not associate any devices with the Cisco Unified CallManager Attendant Console ac application user.
Caution
During an upgrade from Cisco Unified CallManager Release 4.x, the system automatically converts the ac application user to a superprovider user and disassociates the devices that were previously associated to the application user.
To enable device security for the Cisco Unified CallManager Attendant Console, configure an ACDeviceAuthenticationUser application user and associate the attendant phones with that user.
Third-Party Certificate Authority Verification
The Cisco Unified Communications Operating System Administration Guide, Release 5.1(1) states that Cisco has verified Verisign as a source for third-party certificates. Be aware that this is no longer correct, and Verisign is not a verified CA.
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.
This document is to be used in conjunction with the documents listed in the "Related Documentation <required for IOS - optional for other>" section.
CCVP, the Cisco logo, and Welcome to the Human Network 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, 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, Networkers, 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. (0711R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2008 Cisco Systems, Inc. All rights reserved.
Printed in the USA on recycled paper containing 10% postconsumer waste.
Guest
