 Feedback
|
Table Of Contents
Release Notes for Cisco Unified Communications Manager Release 6.1(1b)
Upgrade Paths To Cisco Unified Communications Manager 6.1(1b)
Upgrading from CUCM 4.x and 5.x
Out of Service Nodes and Cisco License Manager
Reset the Cluster After You Change the Security Password
Best Practices for Assigning Roles to Serviceability Administrators
For Serviceability, the Administrator That is Created During Installation Must Not Be Removed
Clarification for Call Park Configuration
Connecting to Third-Party Voice Messaging Systems
Resetting Database Replication When Reverting To an Older Product Release
utils dbreplication clusterreset
utils dbreplication dropadmindb
User Account Control Pop-up Window Displays During Installation of RTMT
CiscoTSP Limitations on Windows Vista Platform
Time Required for Disk Mirroring
Cisco Unified Mobility Supports Nine Locales
Each Remote Destination Supports a Maximum of Two Active Calls
Changes to Cisco Extension Mobility After Upgrade
RTMT Requirement When Cisco Unified Communications Manager Is Upgraded
Changes to Cisco Extension Mobility After Upgrade
Serviceability Session Timeout Not Graceful
Updating the IP Address in the Server Configuration Window
Deleting Then Adding Back a Server in Cisco Unified Communications Manager Administration
SIP Network/IP Address Field Required for SIP Fallback to SRST Gateway
Cisco Unified Reporting Application
CSCtj61834 MLPP Default Domain Name Displays MLPP ID Value
CSCub52944 IP Phones Automatically Upgrade Firmware After Switch Version
CSCuc10415 Tip for Adding a New Server
CSCuc79185 Device Mobility Calling Search Space is Used When Device CSS is <none>
CSCtw44980 Missing Exceptions for Voice-Mail Pilot
CSCud34740 Application User AXL Password Must Not Contain Special Characters
CSCud70447 Missing Etoken Recovery Steps in Troubleshooting Guide
New and Changed Information in Cisco Unified Communications Manager 6.1(1x)
Basic Uninterruptible Power Supply (UPS) Integration
New Service Parameters Added to Extension Mobility
Disaster Recovery Manual Backup Window
Cisco Unified Communications Operating System CLI Commands
utils dbreplication clusterreset
utils dbreplication dropadmindb
utils dbreplication setrepltimeout
Installation, Upgrade, Migration, and Disaster Recovery
Where to Find More Information
Cisco Unified Communications Operating System Administration
Where to Find More Information
Cisco Unified Communications Manager Administration
Browser Requirements for Cisco Unified Communications Manager Administration
Service Parameter and Enterprise Parameter Changes
Where to Find More Information
Cisco Unified Communications Manager Features and Applications
Cisco Unified Communications Manager Assistant
Intercom for Cisco Extension Mobility
Licensing for Cisco Unified Mobility
Phone Button Template, Line, and Security Enhancements for the Nokia S60 Device
Cisco Unified Communications Manager Bulk Administration Tool
Database Summary Includes Database Replication Information
New Preconfigured Alerts in Cisco Unified Serviceability
Adding RTMT Performance Counters in Bulk
RTMT Trace and Log Central Disk IO and CPU Throttling
CDR Analysis and Reporting Tool/Call Detail Record (CAR/CDR)
CAR System Scheduler Default Status
Automatically Generated Reports
Tbl_pregenmail_option Table Data
Calculation of the Utilization of H.323 Gateways
CDR Search Reports Display Time in Two Ways
CAR Scheduler Now a Network Service
Cisco Unified Communications Manager User Options
Cisco Unified IP Phone 7965G and 7945G
Cisco Unified IP Phone 7962G and 7942G
Cisco Unified IP Conference Station 7937G
Intercom with Cisco Extension Mobility
Cisco Unified IP Phone Support for Cisco Unified Communications Manager 6.1 Features
Cisco Unified Communications Manager Configuration XML
Cisco Unified Communications Manager Serviceability XML
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Unified Communications Manager Release 6.1(1b)
January 4, 2013
This document contains information that existed in the Cisco Unified CallManager Releases 6.1(1), and 6.1(1a).
These release notes describe the caveats that release 6.1(1a) and 6.1(1b) resolve as well as the new features and caveats for Cisco Unified Communications Manager Release 6.1(1x). To view the release notes for previous versions of Cisco Unified Communications Manager, choose the Cisco Unified Communications Manager version from the following URL: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_release_notes_list.html
Summary of Cisco Unified Communications Manager Release 6.1(1b)
The following noncomprehensive list gives the caveats that were resolved in this release of Unified CM:
1.
CSCsm37017 - Prior to this release, when you configured traces in the serviceability window, no CCMUser option existed, which meant that you could not change the default CCMuser trace level.
2.
"ATTENTION: The Firmware image in the controller is corrupted!! Please run the Firmware Update Utility from the OS to update the firmware. Error code: 86"
3.
4.
5.
6.
•
Before you install Cisco Unified Communications Manager, 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 Communications Manager and its applications and download and install the latest updates on your system before the deployment of your Cisco Unified Communications Manager 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 Communications Manager, the call-processing component of the Cisco Unified Communications System, extends enterprise telephony features and capabilities to IP phones, media processing devices, voice-over-IP (VoIP) gateways, mobile devices, and multimedia applications.
System Requirements
Server Support
Make sure that you install and configure Cisco Unified CM Release 6.1(1b) on a Cisco Media Convergence Server (MCS) or a Cisco-approved HP server configuration or a Cisco-approved IBM server configuration.
To find which MCS are compatible with Cisco Unified CM Release 6.1(1b), refer to the Supported Servers for Cisco Unified Communications Manager Releases: http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/prod_brochure0900aecd80 62a4f9.html.
Note
Note
Uninterruptible Power Supply
Ensure that you connect each Cisco Unified Communications Manager node to an uninterruptible power supply (UPS) to provide backup power and protect your system.
Caution
Upgrading System Software
Before you upgrade the software version of Cisco Unified Communications Manager, verify your current software version.
To do that, open Cisco Unified Communications Manager Administration. The following information displays:
•
•
Upgrade Paths To Cisco Unified Communications Manager 6.1(1b)
For information about supported Cisco Unified CM upgrades, see the Cisco Unified Communications Manager Software Compatibility Matrix at the following URL:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html.
Caution
Upgrading from CUCM 4.x and 5.x
If you are upgrading from 4.1.3, 4.2.3, 5.1.1, 5.1.2, or 5.1.3, use the Product Upgrade Tool (PUT) or the PUT for registered customers only to obtain a media kit and license or purchase the upgrade from Cisco Sales.
To use the PUT, you 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 Unified CM upgrades, see the Cisco Unified Communications Manager Software Compatibility Matrix at the following URL:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html
Upgrading from Cisco Unified Communications Manager Release 6.0(1a) or 6.1(1a) to Release 6.1(1b) Using the UCSInstall File
Caution
Because of its size, the UCSInstall iso file, UCSInstall_UCOS_6.1.1.2000-3.sgn.iso, has been divided into two parts:
•
–
•
–
Procedure
Step 1
Step 2
Note
a.
cat UCSInstall_UCOS_6.1.1.3000-2.sgn.iso_part1of2 UCSInstall_UCOS_6.1.1.3000-2.sgn.iso_part2of2 > UCSInstall_UCOS_6.1.1.3000-2.sgn.iso
b.
COPY /B UCSInstall_UCOS_6.1.1.3000-2.sgn.iso_part1of2+UCSInstall_UCOS_6.1.1.3000-2.sgn.iso_part2of2 UCSInstall_UCOS_6.1.1.3000-2.sgn.iso
Step 3
38ea200efd06fb6bb8c0515fd852aadb UCSInstall_UCOS_6.1.1.3000-2.sgn.iso
Software Download URLs
Software Download URLs
You can access the latest software upgrades for Cisco Unified Communications Manager at http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875240
Related Documentation
The documentation that supports Cisco Unified Communications Manager Release 6.1 resides at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.htmlLimitations and Restrictions
A recommendation of compatible software releases that have been verified by the test for customers represents a major deliverable of the Cisco Unified Communications System testing. The recommendations, which are not exclusive, represent an addition to interoperability recommendations for each individual voice application or voice infrastructure product.
For a list of software and firmware versions of IP telephony components that were tested for interoperability with Cisco Unified Communications Manager 6.1 as part of Unified Communications System Release 6.1 testing, see http://www.cisco.com/go/unified-techinfo.
For a list of software and firmware versions of contact center components that were tested for interoperability with Cisco Unified Communications Manager 6.1 as part of Unified Communications System Release 6.1 testing, see http://tools.cisco.com/ITDIT/vtgsca/.
Be aware that the release of Cisco IP telephony products does not always coincide with Cisco Unified Communications Manager releases. If a product does not meet the compatibility testing requirements with Cisco Unified Communications Manager, you need to wait until a compatible version of the product becomes available before you can upgrade to Cisco Unified Communications Manager 6.1(1a). For the most current compatibility combinations and defects that are associated with other Cisco Unified Communications products, refer to the documentation that is associated with those products.
Important Notes
The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco Unified Communications Manager Release 6.1(1x).
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Cisco Recommendations
Cisco offers the following recommendations.
Installation Note
Do not install Cisco Unified Communications Manager in a large Class A or Class B subnet that contains a large number of devices. When you install Cisco Unified Communications Manager in a large subnet with a large number devices in that subnet, the Address Resolution Protocol (ARP) table can fill up quickly (maximum 1024 entries, by default).
When the ARP table gets full, Cisco Unified Communications Manager can have difficulty talking to endpoints and cannot add more phones.
Out of Service Nodes and Cisco License Manager
Symptom
After an upgrade from Cisco Unified CallManager Release 5.1.2 to Cisco Unified Communications Manager 6.1(1), apply the 6.x software license. Restart CUCM services on all nodes. Cisco Unified Communications Manager and all services start, except Cisco License Manager. Attempts to manually restart Cisco License Manager are not successful.
Workaround
If dummy nodes exist in the cluster, you should map the IP addresses of the dummy nodes to the hostnames in the DNS server. If you do not Cisco Unified Communications Manager generates alarms that the License Manager service is down.
Reset the Cluster After You Change the Security Password
Servers in a cluster use the Security password to authenticate communication between servers.
To change the Security password, use the set password security CLI command or reset the password from the console.
Step 1
Step 2
Note
Note
Best Practices for Assigning Roles to Serviceability Administrators
Cisco recommends that you configure application users, rather than end users, to access remote nodes to perform such tasks as starting and stopping services. Starting and stopping services requires that the Standard SERVICEABILITY Administration and Standard RealtimeAndTraceCollection roles be assigned.
For Serviceability, the Administrator That is Created During Installation Must Not Be Removed
Removing the Administrator that is created during installation or upgrade can cause communication with remote nodes via Serviceability Administration to fail.
Clarification for Call Park Configuration
Consider the following information when you configure Call Park:
Call Park numbers cannot overlap between Cisco Unified Communications Manager servers. Ensure that each Cisco Unified Communications Manager 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 Communications Manager in the cluster.
When the end user invokes Call Park, Cisco Unified Communications Manager attempts to find an available Call Park number from a Call Park partition that is currently accessible via the calling search space for the party that invoked Call Park.
Connecting to Third-Party Voice Messaging Systems
Administrators can connect third-party voice-messaging systems to Cisco Unified Communications Manager. Ensure the voice-messaging system has a simplified message desk interface (SMDI) that is accessible with a null-modem EIA/TIA-232 cable (and an available serial port). To connect the EIA/TIA-232 cable to Cisco Unified Communications Manager Release 5.0 or later, use a Cisco certified serial-to-USB adapter with the part number USB-SERIAL-CA=.
Resetting Database Replication When Reverting To an Older Product Release
If you revert the servers in a cluster to run an older product release, you must manually reset database replication within the cluster. To reset database replication after you revert all the cluster servers to the older product release, enter the CLI command utils dbreplication reset all on the publisher server.
When you switch versions by using Cisco Unified Communications Operating System Administration or the CLI, you get a message reminding you about the requirement to reset database replication if you are reverting to an older product release. This behavior is also documented in the caveats CSCsl57629 and CSCsl57655.
utils dbreplication clusterreset
This command resets database replication on an entire cluster.
Command Syntax
utils dbreplication clusterreset
Usage Guidelines
Before you run this command, run the command utils dbreplication stop first on all subscribers servers, and then on the publisher server.
Requirements
Command privilege level: 0
Allowed during upgrade: Yes
utils dbreplication dropadmindb
This command drops the Informix syscdr database on any server in the cluster.
Command Syntax
utils dbreplication dropadmindb
Usage Guidelines
You should run this command only if database replication reset or cluster reset fails and replication cannot be restarted.
Requirements
Command privilege level: 0
Allowed during upgrade: Yes
User Account Control Pop-up Window Displays During Installation of RTMT
When you install RTMT on the Microsoft Vista platform, the system displays the User Account Control pop-up window to indicate that an unidentified program wants access to your computer. This occurs because of a limitation in the InstallAnywhere software. This one-time pop-up displays only when installing RTMT. Select Allow to continue.
CiscoTSP Limitations on Windows Vista Platform
Always perform the first-time installation of the CiscoTSP and Cisco Unified Communications Manager TSP Wave Driver on a Vista machine as a fresh install.
If secure connection to Cisco Unified Communications Manager is to be used, turn off the Windows firewall.
If Cisco Unified Communications Manager TSP Wave Driver is used for inbound audio streaming, turn off the Windows firewall.
If Cisco Unified Communications Manager TSP Wave Driver is used for audio streaming, disable all other devices in the "Sound, video and game controllers" group.
Time Required for Disk Mirroring
Disk mirroring on server model 7825 I3 with 160 GB SATA disk drives takes approximately 3 hours.
Disk mirroring on server model 7828 I3 with 250 GB SATA disk drives takes approximately 4 hours.
Cisco Unified Mobility Supports Nine Locales
Cisco Unified Mobility (Mobile Connect and Mobile Voice Access) support a maximum of nine locales, so Cisco Unified Communications Manager Administration blocks you from configuring 10 or more locales for Cisco Unified Mobility. In the Mobility Configuration window, more than nine locales can display in the Available Locales pane if they are installed for Cisco Unified Communications Manager, but you can only save nine locales in the Selected Locales pane. If you attempt to configure more than nine locales for Cisco Unified Mobility, the following error message displays: "Update failed. Check constraint (informix.cc_ivruserlocale_orderindex) failed."
Each Remote Destination Supports a Maximum of Two Active Calls
For Cisco Unified Mobility, each remote destination supports a maximum of two active calls via Cisco Unified Communications Manager. Using the enterprise feature access directory number (DID number) to transfer or conference with DTMF counts as one call. When a Cisco Unified Mobility user receives a call while the user has two active calls for the remote destination or while the user is using DTMF to transfer/conference a call from the remote destination, the received call does not reach the remote destination and instead goes to the enterprise voice mail; that is, if Call Forward No Answer (CFNA) is configured or if the call is not answered on a shared line.
Changes to Cisco Extension Mobility After Upgrade
If you chose a user created profile from the Log Out Profile drop-down list on the Phone Configuration window and checked the Enable Extension Mobility check box, the settings in that profile become the permanent settings on the phone after an upgrade from Cisco Unified CallManager 4.x or Cisco Unified Communications Manager 5.x to Cisco Unified Communications Manager 6.1(1a).
RTMT Requirement When Cisco Unified Communications Manager Is Upgraded
If you are running the Cisco Unified Communications Real-Time Monitoring Tool (RTMT) client and monitoring performance counters during a Cisco Unified Communications Manager upgrade, the performance counters will not update during and after the upgrade. To continue monitoring performance counters accurately after the upgrade completes, you must either reload the RTMT profile or restart the RTMT client.
Changes to Cisco Extension Mobility After Upgrade
If you chose a user created profile from the Log Out Profile drop-down list on the Phone Configuration window and checked the Enable Extension Mobility check box, the settings in that profile become the permanent settings on the phone after an upgrade from Cisco Unified CallManager 4.x or Cisco Unified Communications Manager 5.x to Cisco Unified Communications Manager 6.1(1a).
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 have to repeat those changes. This behavior occurs in the Alarm, Trace, Service Activation, Control Center, and SNMP windows.
Workaround
If you know that the session has been idle for more than 30 minutes, log out using the Logout button before making any changes in the user interface.
Problem Configuring Mobility Identity for Nokia S60 Device in Cisco Unified Communications Manager Administration
The following error message may display in the Phone Configuration window in Cisco Unified Communications Manager Administration when you try to configure Mobility Identity for the Nokia S60 device: "Add failed. [10102] Check the type of device specified in fkDevice_DualMode. Remote Destionations other than Dual Mode must use fkDevice_RemoteDestinationTemplate."
The error occurs under one of the following circumstances:
•
•
If the error message displays, you can perform the following tasks to ensure that you can configure Mobility Identity for the Nokia S60 device:
1.
2.
Tip
3.
Tip
4.
Updating the IP Address in the Server Configuration Window
Before you change the IP address of a server in the Server Configuration window in Cisco Unified Communications Manager Administration, consider the following information:
•
•
•
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080094601.shtml
Serviceability Limitations
When you modify the IP Address field, you cannot access the RTMT profiles, custom counters, custom alerts, and generic queries for Trace & Log Collection Tool (TLC) for that server.
You should manually remove any RTMT profiles, custom counters, custom alerts, and generic queries for Trace and Log Collection Tool (TLC) that were set for the old IP Address. When you modify the IP Address field, you will need to re-create the RTMT profile, custom counters, custom alerts, and generic queries for TLC the next time that you log in to the server on RTMT.
Cisco AMC Service service includes two user-configurable service parameters, Primary Collector and Failover Collector. These service parameters use Host Name/IP Address to designate the primary and failover AMC server. If you change the IP address of the AMC primary collector or failover collector, you should check these service parameters and update them accordingly.
Cisco Serviceability Reporter service includes one user-configurable service parameter, RTMT Reporter Designated Node. This service parameter uses Host Name/IP Address to designate the node on which RTMTReporter runs. If you changed the IP address of the RTMT Reporter Designated Node, you should check this service parameter and update it accordingly.
Deleting Then Adding Back a Server in Cisco Unified Communications Manager Administration
In Cisco Unified Communications Manager Administration, you cannot delete the first node of the cluster, but you can delete subsequent nodes. Before you delete a subsequent node in the Find and List Servers window, Cisco Unified Communications Manager Administration displays the following message: "You are about to permanently delete one or more servers. This action cannot be undone. Continue?". If you click OK, the server gets deleted from the Cisco Unified Communications Manager database and is not available for use.
Tip
If you delete a subsequent node (subscriber) from Cisco Unified Communications Manager Administration and you want to add it back to the cluster, perform the following procedure:
Tip
Procedure
Step 1
Step 2
Tip
If the first node in the cluster runs 6.1(1a) and a service release (or engineering special), you must choose the Upgrade During Install option when the installation displays the installation options; before you choose this option, ensure that you can access the service release (or engineering special) image on DVD or a remote server. For more information on how to perform an installation, refer to Installing Cisco Unified Communications Manager 6.1(1).Step 3
Deleting a Server
The Cisco Unified Communications Manager Administration Guide does not provide the messages that display when you attempt to delete a server. Disregard the entire section, Deleting a Server, in the "System-Level Configuration Settings" chapter in the Cisco Unified Communications Manager System Guide. Instead, refer to the following:
Deleting a Server and Adding a Deleted Server to a Cluster
In Cisco Unified Communications Manager Administration, you cannot delete the first node of the cluster, but you can delete subsequent nodes. Before you delete a subsequent node in the Find and List Servers window, Cisco Unified CM Administration displays the following message: "You are about to permanently delete one or more servers. This action cannot be undone. Continue?". If you click OK, the server gets deleted from the Cisco Unified CM database and is not available for use.
Tip
Before you delete a server, consider the following information:
•
•
•
•
•
•
•
•
•
•
•
If you delete a subsequent node (subscriber) from Cisco Unified CM Administration and you want to add it back to the cluster, perform the following procedure:
Procedure
Step 1
Step 2
Tip
Make sure that the version that you install on the subsequent node matches the version that runs on the first node (publisher) in the cluster.
If the first node in the cluster runs Cisco Unified Communications Manager 6.1(4) version and a service release (or engineering special), you must choose the Upgrade During Install option when the installation displays the installation options; before you choose this option, ensure that you can access the service release (or engineering special) image on DVD or a remote server. For more information on how to perform an installation, refer to installation documentation that supports your version of Unified CM.Step 3
Step 4
SIP Network/IP Address Field Required for SIP Fallback to SRST Gateway
Although Cisco Unified Communications Manager Administration does not list the SIP Network/IP Address field as a required setting, you must configure the SIP Network/IP Address field and the SIP Port field in the SRST Reference Configuration window for a SIP device to fall back to the SRST-enabled gateway. For more information on these fields and SRST references, refer to the Cisco Unified Communications Manager Administration Guide.
Cisco Unified Reporting Application
The Cisco Unified Reporting web application, which is accessed at the Cisco Unified Communications Manager console or from the Cisco Unified Communications Manager Real-Time Monitoring Tool, generates reports for troubleshooting or inspecting cluster data. You can find more information about this application in the Cisco Unified Reporting Administration Guide.
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.
CSCub52944 IP Phones Automatically Upgrade Firmware After Switch Version
After you perform a switch version when you upgrade Unified CM, IP phones request a new configuration file. This request results in an automatic upgrade to the device firmware.
CSCuc10415 Tip for Adding a New Server
The following tip needs to be added to the "Server settings" topic in the Cisco Unified Communications Manager Administration Guide.
To avoid errors, Cisco recommends that you add a server to the system with a name that has less than 47 characters. Then, update the server name to the target length.
CSCuc79185 Device Mobility Calling Search Space is Used When Device CSS is <none>
The following note is missing from the "Phone Settings" topic in the Cisco Unified Communications Manager Administration Guide:
When set to <none>, Unified CM uses the device mobility calling search space, which is configured on the device pool.
CSCtw44980 Missing Exceptions for Voice-Mail Pilot
The following information is missing for the Voice Mail Pilot Name field description in the "Voice-Mail Pilot Settings" topic in the Cisco Unified Communications Manager Administration Guide:
Allowed characters are numeric (0-9), plus (+), asterisk (*), and pound (#).
CSCud34740 Application User AXL Password Must Not Contain Special Characters
The following note is missing from the Application User Settings topic in the Cisco Unified Communications Manager Administration Online Help:
Note
CSCud70447 Missing Etoken Recovery Steps in Troubleshooting Guide
The Cisco Unified Communications Manager Troubleshooting Guide is missing the following procedure for troubleshooting if you lose all security tokens (etokens):
Perform the following procedure if you lose the security tokens and you need to update the CTL file.
Tip
Step 1
file list tftp CTLFile.tlv
Step 2
file delete tftp CTLFile.tlv
Step 3
Step 4
Step 5
Tip
Step 6
Step 7
New and Changed Information in Cisco Unified Communications Manager 6.1(1x)
The following section describes new features and changes that are pertinent to Cisco Unified Communications Manager, Release 6.1(1x) or later. The sections may include configuration tips for the administrator, information about users, and information about where to find more information.
•
•
•
•
•
•
•
•
•
•
•
Basic Uninterruptible Power Supply (UPS) Integration
When Cisco Unified Communications Manager 6.0(1a) runs on an MCS 7825H2 or MCS 7835H2, basic integration to the UPS model APC SmartUPS 1500VA USB and APC 750VA XL USB gets supported. Integration occurs via a single point-to-point Universal Serial Bus (USB) connection. Serial and SNMP connectivity to UPS does not get supported, and the USB connection must be point-to-point (in other words, no USB hubs). Single- and dual-USB UPS models get supported. The feature activates automatically during bootup if a connected UPS gets detected.
Alternatively, on MCS-7835H2, you can execute the show ups CLI command which shows the current status of the USB-connected APC smart-UPS device and starts the monitoring service if it is not already started.
On supported servers, the CLI command also displays detected hardware, detected versions, current power draw, remaining battery runtime, and other relevant status information.
When the feature is activated, graceful shutdown will commence as soon as the low battery threshold is reached. Resumption or fluctuation of power will not interrupt or abort the shutdown.
For unsupported Cisco Unified Communications Manager releases, MCS models and/or UPS vendor/make/models, you can cause an external script to monitor the UPS. When low battery gets detected, you can log on to Cisco Unified Communications Manager by using Secure Shell (SSH), access the CLI, and execute the utils system shutdown command.
New Service Parameters Added to Extension Mobility
Extension Mobility includes four new service parameters. You can find these new parameters at System > Service Parameters > Cisco Extension Mobility > Advanced.
•
Validate IP Address
This parameter specifies whether validation of the IP address of the source that is requesting login or logout occurs.
The paramater can take values of true or false.
•
Validation Procedure
–
–
–
Validation Effect
–
–
•
Note
For more information, refer to the design guidelines in the Extension Mobility documentation.
Trusted List of IPs
This parameter displays as a text box (maximum length - 1024 characters). You can enter strings of trusted IP addresses or hostnames, separated by semi-colons, in the text box. IP address ranges and regular expressions do not get supported.
Allow Proxy
Allow Proxy can take values of true or false.
•
•
Note
Extension Mobility Cache Size
This parameter displays as a text box in which the administrator can configure the size of the device cache maintained by Extension Mobility. The minimum value for this field is 1000 and the maximum is 20000. The default specifies 10000.
Note
Disaster Recovery Manual Backup Window
Disaster Recovery System backs up CAR/CDR data automatically when you check the CCM checkbox on the Manual Backup window. The Manual Backup window no longer contains a CAR/CDR checkbox.
Cisco Unified Communications Operating System CLI Commands
This section describes Cisco Unified Communications Operating System CLI commands that are added or updated in this release.
file delete
The file delete command includes the parameters dir tftp and license. The file delete command deletes one or more files.
Command Syntax
file delete
dir tftp directory [detail]
license filename [detail]
Parameters
•
•
Options
•
Usage Guidelines
You get prompted for confirmation after entering the command.
You cannot delete directories or files that are in use.
file dump
The file dump command includes the new parameter sftpdetails. The file dump command dumps the contents of a file to the screen, a page at a time.
Command Syntax
file dump
sftpdetails filename [hex] [regexp expression] [recent]
Parameters
•
•
Options
•
•
•
Usage Guidelines
To determine which files you can dump with this command, first enter the following command:
file list sftpdetails *
The output lists the filenames that you can dump.
Requirements
Command privilege level: 1
Allowed during upgrade: Yes
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 includes the new parameters salog, 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 includes the new parameters salog and partBsalog, and sftpdetails. 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]
sftpdetails filespec [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 includes 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
run loadxml
Run this command as a workaround when service parameters or product-specific information does not appear in the administration window as expected.
You may need to restart some services may be required after this command.
Command Syntax
run loadxml
Requirements
Command privilege level: 1
Allowed during upgrade: No
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
Be aware that the show iptables command was removed. The utils firewall list command now displays similar information.
show process
This command displays information about process that is running on the system.
Syntax
show process
list [file filename] [detail]
load [cont] [clear] [noidle] [num number] [thread] [cpu | memory| time] [page]
name process [file filename]
open-fd process-id [, process-id2]
search regexp [file filename]
using-most cpu [number] [file filename]
using-most memory [number] [file filename]
Parameters
•
•
•
•
•
•
•
Options
•
•
•
•
•
•
•
•
•
•
•
•
•
show tech database
This command includes the new parameters dump and session.
Command Syntax
show tech database
dump
sessions
Parameters
•
•
show tech network
The show tech network command gets 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 gets 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 gets 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]
kernel [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 dbreplication clusterreset
This command resets database replication on an entire cluster.
Command Syntax
utils dbreplication clusterreset
Usage Guidelines
Before you run this command, run the command utils dbreplication stop first on all subscribers servers, and then on the publisher server.
Requirements
Command privilege level: 0
Allowed during upgrade: Yes
utils dbreplication dropadmindb
This command drops the Informix syscdr database on any server in the cluster.
Command Syntax
utils dbreplication dropadmindb
Usage Guidelines
You should run this command only if database replication reset or cluster reset fails and replication cannot be restarted.
Requirements
Command privilege level: 0
Allowed during upgrade: Yes
utils dbreplication setrepltimeout
You can use this command to set the timeout for database replication on large clusters.
Command Syntax
utils dbreplication setrepltimeout timeout
Options
•
Usage Guidelines
The default database replication timeout equals 5 minutes. All subscriber servers that are requesting replication within 5 minutes get on the broadcast list and get replicated. For large clusters, you can use the command to increase the default timeout.
Requirements
Command privilege level: 0
Allowed during upgrade: Yes
utils diagnose
This command enables you to diagnose and attempt to automatically fix system problems.
Command Syntax
utils diagnose
fix
list
module module_name
test
version
Parameters
•
•
•
•
•
•
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 snmp
The utils snmp command includes 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
utils system switch-version
For this modified commandthe switch-version parameter includes the new option nodatasync. The utils system switch-version command allows you to restart the system on the inactive partition.
Command Syntax
utils system
switch-version [nodatasync]
Options
•
Usage Guidelines
A warning message displays, and you are prompted for confirmation before this command runs with the nodatasync option.
If you use the nodatasync option, any changes to UFF data on the active partition will be lost. You should use this option only to force the versions to switch if the system otherwise will not switch versions because a data synchronization failure occurred.
Administrative changes that are made on the active partition, such as adding new phones, are not synchronized when you switch versions. UFF data gets synchronized when you switch versions, unless you use the nodatasync option.
This option does not support command auto-completion. You must enter the entire option name.
Installation, Upgrade, Migration, and Disaster Recovery
The following sections describe the changes that were made to the installation, upgrade, and disaster recovery procedures in Cisco Unified Communications Manager 6.1(1a):
•
Installation Overview
For 6.1(1a), 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
Connectivity Validation
To ensure successful installation of a subsequent node, the system now 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.
When connectivity validation succeeds, you can choose whether you want the installation process to continue uninterrupted or stop and display a successful validation message. To display the confirmation message, check the check box for Show confirmation on successful connection to first node on the First Node Access Configuration window.
Enhanced Documentation
For Release 6.1, installation and upgrade documentation enhancements 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 6.1 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 Communications Manager Release 5.1(3).
Changing IP Addresses
The document Changing the IP Address for Cisco Unified Communications Manager 5.x and 6.x Servers describes how to change the IP address of Cisco Unified Communications Manager servers for releases 5.x and 6.x.
Where to Find More Information
•
•
•
•
•
Cisco Unified Communications Operating System Administration
For Cisco Unified Communications Manager 6.1(1a), you can perform many common system administration functions through the Cisco Unified Communications Operating System.
This chapter comprises the following topics:
•
Overview
You cannot log in to Cisco Unified Communications Operating System and Cisco Unified Communications Manager Administration at the same time.
Browser Requirements
You can access Cisco Unified Communications Manager Administration by using the following browsers:
•
•
Note
Where to Find More Information
•
Cisco Unified Communications Manager Administration
The following sections describe the Cisco Unified Communications Manager Administration enhancements:
•
•
•
Browser Requirements for Cisco Unified Communications Manager Administration
The following browser requirements apply to Cisco Unified Communications Manager Administration:
•
•
Tip
Service Parameter and Enterprise Parameter Changes
Cisco Unified Communications Manager 6.1 supports the following service parameter changes:
•
For example, if the value for the parameter equals 20 minutes and the timer expires at 3:00, Cisco Unified Communications Manager 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 Communications Manager 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 Communications Manager 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 Communications Manager Administration and either click the name of the service parameter or click the ? button in the Service Parameter Configuration window.
Note
•
•
Tip
•
•
The Report Socket Read Timeout parameter specifies the maximum number of seconds that the application uses when reading data from another server. Increase this time if you experience connection issues on a slow network. For this required field, the range goes from 5 to 600 seconds, and the default value specifies 60 seconds.
•
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 Communications Manager Administration and either click the name of the service parameter or click the ? button in the Service Parameter Configuration window.
Menu Changes
The following changes occurred in the Cisco Unified Communications Manager Administration menus:
•
•
•
•
•
•
•
•
•
•
•
•
•
Where to Find More Information
•
•
•
•
•
Cisco Unified Communications Manager Features and Applications
The following sections describe the Cisco Unified Communications Manager 6.1 feature and application enhancements:
•
•
•
•
Cisco Unified Communications Manager Assistant
The assistant no longer obtains the assistant console application via a URL that the administrator provides; instead, a plug-in from Cisco Unified Communications Manager Administration gets downloaded and installed on the assistant PC.
The assistant console application installation supports Netscape 7.1 (or later) and Microsoft Internet Explorer 6 (or later). You can install the application on a PC that runs Windows 2000, Windows XP, or Windows Vista [new support for 5.1(3) and later].
A previous 5.x or 6.x version of the assistant console application works with Cisco Unified Communications Manager 6.1(1a), but if you decide to install the 6.1(1a) plug-in, you must uninstall the previous 5.x or 6.x version of the assistant console application before you install the plug-in.
Previous versions of the assistant console application do not work with Windows Vista. If the PC runs Windows Vista, install the plug-in.
After you upgrade from Cisco Unified CallManager Release 4.x to Cisco Unified Communications Manager 6.1(1a), you must install the assistant console plug-in. Before you install the plug-in, uninstall the 4.x version of the assistant console application.
To uninstall previous versions of the assistant console application (6.0(1), 4.x, or any 5.x version before 5.1(3)), choose Start> ...Programs > Cisco Unified CallManager Assistant > Uninstall Assistant Console.
To uninstall 5.1(3) (or later) attendant console application, go to the Control Panel and remove it.
Tip
To install the assistant console application, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Tip
The installation wizard displays.
Step 4
Step 5
Step 6
Tip
Step 7
The installation begins.
Step 8
Tip
Before the assistant logs in to the console, give the assistant the port number and the IP address or hostname of the Cisco Unified Communications Manager server where the Cisco IP Manager Assistant service is activated. The first time that the assistant logs in to the console, the assistant must enter the information in the Cisco Unified Communications Manager Assistant Server Port and the Cisco Unified Communications Manager Assistant Server Hostname or IP Address fields.
Before the assistant logs in to the console, give the assistant the user name and password that is required to log in to the console.
The Advanced tab in the Cisco Unified Communications Manager Assistant Settings window allows you to enable trace for the assistant console.
Intercom for Cisco Extension Mobility
Cisco Unified Communications Manager Administration Configuration Tips
Beginning with Release 6.1(1a) of Cisco Unified Communications Manager, intercom directory numbers require configuration of the Default Activated Device field in the Intercom Directory Number Configuration window if the intercom directory number is to be active.
Beginning with Release 6.1(1a) of Cisco Unified Communications Manager, you can also configure intercom directory numbers for use with Cisco Extension Mobility by configuring the Default Activated Device field.
Cisco Extension Mobility uses a default device that is configured for an intercom line. An intercom line only gets presented on the default device. You can assign an intercom line to a device profile.
The system presents an intercom line to a user who uses Cisco Extension Mobility to log in to a phone that supports the intercom feature if the device profile that the user uses to log in has an intercom line that is provisioned. The phone must act as the default device for that intercom line. When a user logs on to a device that is not the default device, the intercom line does not get presented.
GUI Change
Call Routing > Intercom > Intercom Directory Number—Displays a new row for Default Activated Device. For the intercom feature to function for users who log in to phones remotely by using Cisco Extension Mobility ensure that the new Default Activated Device is configured.
Service Parameter and Enterprise Parameter Changes
No service parameter or enterprise parameter considerations exist for configuration of the intercom feature with Cisco Extension Mobility.
Installation/Upgrade (Migration) Considerations
For an existing intercom line that is assigned to a device, migration from release 6.0(1) of Cisco Unified Communications Manager to release 6.1(1a) or later automatically designates the intercom default device for that intercom line.
Serviceabilty Considerations
No serviceability considerations exist for configuration of the intercom feature with Cisco Extension Mobility.
BAT Considerations
For information on how the intercom feature works with Cisco Extension Mobility in the Bulk Administration Tool, see the "Cisco Unified Communications Manager Bulk Administration Tool" section.
CAR/CDR Considerations
No CAR/CDR considerations exist for configuration of the intercom feature with Cisco Extension Mobility.
Security Considerations
No security considerations exist for configuration of the intercom feature with Cisco Extension Mobility.
CTI Considerations
No administrator-configuratble CTI considerations exist for configuration of the intercom feature with Cisco Extension Mobility.
User Tips
For information on how the intercom feature works with Cisco Extension Mobility on Cisco Unified IP Phones, see the discussion of Intercom with Cisco Extension Mobility in the "Cisco Unified IP Phones" section.
For More Information
•
•
•
•
Join Across Lines
Cisco Unified Communications Manager Administration Configuration Tips and GUI Changes
•
•
•
•
•
BAT Considerations
For information on how you can configure join across lines in BAT, see the "Cisco Unified Communications Manager Bulk Administration Tool" section.
AXL and CTI Considerations
For information on join across lines works with AXL, see the "Cisco and Third-Party APIs" section.
User Tips
For information phone support for join across lines, see the "Cisco Unified IP Phones" section.
For More Information
•
•
•
•
Licensing for Cisco Unified Mobility
This section contains information on licensing for Cisco Unified Mobility.
Cisco Unified Communications Manager Administration Configuration Tips and GUI Changes
•
•
If you check the Enable Mobility check box and fail to choose an adjunct device from the Primary User Device drop-down list box, four device license units (DLUs) get consumed, as indicated in the Mobility Enabled End Users row in the License Unit Calculation window.
If you enable Cisco Unified Mobility and later choose an adjunct device from the Primary User Device drop-down list box, the system credits you with two DLUs, as indicated in the Mobility Enabled End Users row in the License Unit Calculation window.
•
After you check the Enable Mobility check box, choose an adjunct device that you want to assign to the user specifically for Cisco Unified Mobility. For example, choose a device, such as a desktop phone, that the user uses in addition to the cell phone for Cisco Unified Mobility.
Before you choose an adjunct device, consider the following information:
–
–
–
–
BAT Considerations
For information on how Cisco Unified Mobility and licensing work for Bulk Administration Tool, see the "Cisco Unified Communications Manager Bulk Administration Tool" section.
AXL and CTI Considerations
For information on how Cisco Unified Mobility and licensing work for AXL, see the "Cisco and Third-Party APIs" section.
For More Information
•
•
•
Single Button Barge
Cisco Unified Communications Manager Administration Configuration Tips and GUI Changes
•
•
•
•
•
BAT Considerations
For information on how you can configure single button barge in BAT, see the "Cisco Unified Communications Manager Bulk Administration Tool" section.
AXL and CTI Considerations
For information on how join across lines works with AXL, see the "Cisco and Third-Party APIs" section.
User Tips
For information on phone support for single button barge, see the "Cisco Unified IP Phones" section.
For More Information
•
•
•
•
•
SIP Trunk Identification
This section contains information on how Cisco Unified Communications Manager identifies the SIP trunk to use for a call.
Cisco Unified Communications Manager Administration Configuration Tips and GUI Changes
•
Cisco Unified Communications Manager only accepts calls from the SIP device whose IP address matches the destination address of the configured SIP trunk. In addition, the port on which the SIP message arrives must match the one that is configured on the SIP trunk. After Cisco Unified Communications Manager accepts the call, Cisco Unified Communications Manager uses the configuration for the Reroute Incoming Request to new Trunk based setting to determine whether the call should get rerouted to another trunk.
From the drop-down list box, choose the method that Cisco Unified Communications Manager uses to identify the SIP trunk where the call gets rerouted:
–
–
–
AXL and CTI Considerations
For information on SIP trunk identification and AXL, see the "Cisco and Third-Party APIs" section.
For More Information
•
•
Thai Language Support
Cisco Unified Communications Manager Release 6.1 supports Thai locales on Cisco Unified Communications Manager user interfaces and Thai text on phone screen displays for the following Cisco Unified IP phones.
Supported Cisco Unified IP Phones (SCCP and SIP)
7975G, 7971G-GE, 7970G, 7965G, 7962G, 7961G-GE, 7961G, 7945G, 7942G, 7941G-GE, 7941G, 7931G (SCCP only)
Turkish Language Support
Cisco Unified Communications Manager Release 6.1 supports Turkish locales on Cisco Unified Communications Manager user interfaces and Turkish text on phone screen displays for the following Cisco Unified IP phones.
Supported Cisco Unified IP Phones (SCCP and SIP)
7975G, 7971G-GE, 7970G, 7965G, 7962G, 7961G-GE, 7961G, 7945G, 7942G, 7941G-GE, 7941G, 7931G (SCCP only)
Phone Button Template, Line, and Security Enhancements for the Nokia S60 Device
In Cisco Unified Communications Manager 6.1, the following enhancements exist for the Nokia S60, the dual-mode device that you can use with Cisco Unified Mobility.
Cisco Unified CallManager Administration Configuration Tips and GUI Changes
You can configure a phone security profile for the Nokia S60 in the Phone Security Profile Configuration window in Cisco Unified Communications Manager Administration 6.1 (System > Security Profile > Phone Security Profile). From the Device Security Mode drop-down list box, you can choose Nonsecure, Authenticated, or Encrypted, as described in the Cisco Unified Communications Manager Security Guide.
In the Phone Configuration window (Device > Phone), you can configure a phone button template for the Nokia S60 by choosing the Nokia S60 phone template from the Phone Button Template drop-down list box.
In the Association Information pane in the Phone Configuration window for the Nokia S60, you can configure up to two lines and assign them to the device, as described in the Cisco Unified Communications Manager Administration Guide. You can configure additional lines under the Unassigned Associated Items pane.
In the Find and List Phone Button Template window (Device > Device Settings > Phone Button Template), you can view and copy the Standard Nokia S60 SCCP phone button template.
Installation/Upgrade (Migration) Considerations
Consider installing the latest 6.1(1a) compatible Nokia .cop file as optional; that is, you can use the pre-6.1(1a) mobility configuration, such as Remote Destination Profiles and Remote Destinations, for the Nokia S60 devices without installing the latest 6.1(1a) compatible Nokia .cop file. Before you can use the 6.1(1a) enhancements for the Nokia S60 in Cisco Unified Communications Manager 6.1, however, you must install the latest 6.1(1a) compatible Nokia .cop file.
If you configured Nokia S60 devices by using the pre-6.1(1a) Nokia .cop file, install the latest 6.1(1a) compatible Nokia S60 .cop file before you upgrade to Cisco Unified Communications Manager 6.1. If you choose not to upgrade to Cisco Unified Communications Manager 6.1(1a) after you install the latest Nokia S60 .cop file, your existing Nokia S60 devices do not automatically migrate as dual-mode phones that are supported with Cisco Unified Mobility after you upgrade to Cisco Unified Communications Manager 6.1(1a). For additional migration considerations, see the following scenarios:
•
If you installed the pre-6.1(1a) Nokia .cop file, configured single-mode remote destinations for mobile destination numbers in a previous Cisco Unified Communications Manager release, and now want to use the features (for example, Mobility Identity) that the latest 6.1(1a) compatible Nokia .cop file supports, install the latest 6.1(1a) compatible Nokia .cop file before you perform the Cisco Unified Communications Manager 6.1 upgrade. After you perform the upgrade to 6.1(1a), manually delete the remote destinations in Cisco Unified Communications Manager Administration and reconfigure the destination numbers as dual-mode Mobility Identity.
•
In this situation, existing Nokia S60 devices do not automatically migrate after you install the latest 6.1(1a) compatible Nokia .cop file. To work around this limitation, you must manually delete all existing Nokia S60 devices from Cisco Unified Communications Manager Administration (or BAT) 6.1(1a) and reconfigure the devices after you install the latest 6.1(1a) compatible Nokia .cop file. Remember to reset the devices after you configure them.
For additional Nokia S60 configuration considerations, see the "Problem Configuring Mobility Identity for Nokia S60 Device in Cisco Unified Communications Manager Administration" section
BAT Considerations
You can use BAT to configure the Nokia S60 device.
Security Considerations
You can configure a phone security profile for the Nokia S60 in the Phone Security Profile Configuration window in Cisco Unified Communications Manager Administration 6.1 (System > Security Profile > Phone Security Profile). From the Device Security Mode drop-down list box, you can choose Nonsecure, Authenticated, or Encrypted, as described in the Cisco Unified Communications Manager Security Guide.
For More Information
•
•
•
•
Cisco Unified Communications Manager Bulk Administration Tool
The following sections contain information regarding changes and additions that have been made to the Cisco Unified Communications Manager Bulk Administration Tool.
GUI Changes
The following GUI changes exist in this release of BAT:
•
•
•
•
•
•
Cisco Unified Serviceability
This section contains these subsections:
•
•
•
•
Collecting Installation Logs
Trace and Log Central now allows the collection of installation logs. In the Cisco Unified Communications Manager Real-Time Monitoring Tool Trace and Log Central window, double-click Collect Install Logs. The Collect Install Logs wizard launches and steps you through the rest of the process.
For more information, see the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide.
Database Summary Includes Database Replication Information
RTMT displays information on predefined Cisco Unified Communications Manager objects in the monitoring pane when you select Communications Manager in the quick launch channel. It monitors the predefined objects on all nodes in the cluster. The Service category includes the Database Summary that now provides the number of replicates that have been created and the status of the replication in addition to the other types of connection information that was previously provided.
To display information on the database, choose CallManager > Service > Database Summary.For more information, see the Cisco Unified Communications Manager Real-Time Monitoring Tool Administration Guide.New Preconfigured Alerts in Cisco Unified Serviceability
The following list shows preconfigured alerts that are now available:
•
•
•
•
•
RTMT Critical Services
Cisco Unified Communications Manager 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 the Cisco Unified Communications Manager server. For a specific description of each state, review the following information:
•
•
•
•
Tip
•
•
•
For More Information
•
•
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 the Cisco Unified Communications Manager Real-Time Monitoring Administration Tool Guide.
RTMT Trace and Log Central Disk IO and CPU Throttling
RTMT now supports the throttling of critical Trace and Log Central operations and jobs, whether they are running on demand, scheduled, or automatic. The effect of the throttling slows the operations when IO utilization is in high demand for call processing, so that call processing can take precedence.
For more information, see the Cisco Unified Communications Manager Real-Time Monitoring Administration Tool Guide.
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 benefits of tracefile compression include
•
•
For more information, see Documentation Updates.
CDR Analysis and Reporting Tool/Call Detail Record (CAR/CDR)
The following sections detail changes in CAR/CDR in release 6.1(1a) of Cisco Unified Communications Manager.
•
•
•
•
•
•
CAR System Scheduler Default Status
The CAR System Scheduler default status now specifies that CAR processes CDRs continuously 24 hours per day and 7 days per week. However, you can set the loading time, interval, and duration as needed. In addition, the default setting loads only CDR records. Call Management Records (CMR) records do not get loaded.
An option allows you to uncheck the "Load CDR Only" check box in the CAR System Scheduler window to allow CMR records to load.
Automatically Generated Reports
You can schedule CAR reports to generate automatically at a regular time. Each report that can be scheduled has its own report generation interval. In previous releases of Cisco Unified Communications Manager, the automatically generated reports default status specified Enabled. Beginning with Cisco Unified Communications Manager Release 6.1(1a), the default status specifies Disabled for the automatically generated reports. You must enable each automatically generated report after CAR is activated on your system.
Automatic E-Mail Alerts
For all new installations of Cisco Unified Communications Manager, you must enable the automatic e-mail alerts. The default status for all alerts specifies Disabled. In previous releases of Cisco Unified Communications Manager, the default status for all automatic e-mail alerts specified Enabled.
Tbl_pregenmail_option Table Data
For all Cisco Unified Communications Manager upgrades from Release 5.x to a later release of Cisco Unified Communications Manager, the tbl_pregenmail_option table data migrates only if the CAR Scheduler service is active.
Calculation of the Utilization of H.323 Gateways
For calculation of the utilization of H.323 gateways, the system uses the port numbers from the CAR Gateway Configuration window. To find this window, choose System > System Parameters > Gateway Configuration. You cannot take port details for H.323 gateways from the Cisco Unified Communications Manager database because the H.323 port number always equals zero in the database. The user must update H.323 gateway ports information in the CAR Gateway Configuration window.
Be aware that the only port detail information that is taken from the CAR Gateway Configuration window is for those gateways that do not have port details that are available or that show zero in the Cisco Unified Communications Manager database.
CDR Search Reports Display Time in Two Ways
The CDR Search by User Extension, CDR Search by Gateway, CDR Search by Call Precedence Levels, and CDR Search for Malicious Calls reports now display current time in both Coordinated Universal Time (UTC) and local time and use the following rules:
•
•
•
•
CAR Scheduler Now a Network Service
Installed automatically, network services include services that the Cisco Unified Communications Manager Business edition system requires to function. Because these services are required for basic functionality, you cannot activate them in the Service Activation window. Cisco CAR Scheduler now represents a network service. In the previous release of Cisco Unified Communications Manager Business Edition the Cisco CAR Scheduler represented a feature service.
Cisco Unified Communications Manager User Options
The following enhancements occurred in the Cisco Unified CM User Options Menu (referred to as User Options) in release 6.1.
Call Forward
This section contains information on updates to the Cisco Unified CM User Options, Call Forward feature. Previous to release 6.1, users had only the Call Forward All option.
The Cisco Unified Communications Manager administrator determines the call forwarding options that are available to all users. From the Enterprise Parameters Configuration window, in the Show Call Forwarding field, the administrator chooses one of these options:
•
•
•
From the Cisco Unified CM User Options window, users can configure the call forward all, call forward busy, call forward no answer, and call forward no coverage user options. To set the call forward user option, the user chooses User Options > Device and then clicks the Line Settings button. Users configure incoming external or internal calls to either a phone number or to a voice-messaging number.
Cisco Unified IP Phones
This section provides the following information:
•
•
•
•
•
Cisco Unified IP Phone 7975G
The Cisco Unified IP Phone 7975G is a full-feature IP-based phone that demonstrates the latest advances in VoIP telephony.
The Cisco Unified IP Phone 7975G extends the functionality of the existing Cisco Unified IP Phone 7970G and 7971G-GE models with the following features:
•
•
•
•
•
•
•
•
Requirements:
The Cisco Unified IP Phone 7975G requires one of the following releases at minimum:
•
•
Cisco Unified IP Phone 7965G and 7945G
The Cisco Unified IP Phone 7965G and 7945G is a full-feature IP-based phone that demonstrates the latest advances in VoIP telephony.
The Cisco Unified IP Phone 7965G and 7945G extend the functionality of the existing Cisco Unified IP Phone 7961G, 7961G-GE, 7941G, 7941G-GE models with the following features:
•
•
•
•
•
•
•
•
•
•
•
Requirements:
The Cisco Unified IP Phone 7965G and 7945G requires one of the following releases at minimum:
•
•
Cisco Unified IP Phone 7962G and 7942G
The Cisco Unified IP Phone 7962G and 7942G extends the features and functionality of the existing Cisco Unified IP Phone 7961G and 7942G while enhancing the telephone user experience with the following features:
•
•
•
•
•
•
•
•
Requirements:
The Cisco Unified IP Phone 7962G and 7942G requires one of the following releases at minimum:
•
•
Cisco Unified IP Conference Station 7937G
The Cisco Unified IP Conference Station 7937G, a full-feature IP-based conference station, allows you to place and receive calls, put calls on hold, transfer calls, make conference calls, and to access features such as mute, speed dial, call forward, and more.
Cisco Unified IP Conference Station 7937G for firmware release 1.0(1) provides support for the following features:
•
•
•
•
•
Note
Connection Monitor
Connection Monitor enables an administrator to change the time that a link between a phone, which is registered with an SRST due to a failover, and a Cisco Unified Communications Manager must remain stable (with no link-flapping) before the phone falls back from SRST to the Cisco Unified Communications Manager.
Define the connection monitor duration in Cisco Unified Communications Manager Administration by using System > Device Pool. It applies to all IP phones in a specific device pool. The default value specifies 120 seconds.
Supported Cisco Unified IP Phones (SCCP and SIP)
7962G, 7942G, 7975G, 7965G, 7945G, 7970G, 7970G-GE, 7971G, 7971G-GE, 7906G, 7911G, 7931G (SCCP only), 7940G, 7960G
Intercom with Cisco Extension Mobility
Cisco Unified Communications Manager Release 6.1 supports the intercom feature for Cisco Extension Mobility users.
You must configure the following information for intercom:
•
•
–
–
Note
For more information, refer to Cisco Unified Communications Manager Features and Services Guide, Release 6.1, Intercom chapter.
Supported Cisco Unified IP Phones (SCCP and SIP)
7975G, 7971G-GE, 7970G, 7965G, 7962G, 7961G-GE, 7961G, 7945G, 7942G, 7941G-GE, 7941G, 7931G (SCCP only)
Single Button Barge (SCCP)
When single button barge (SBB) is enabled, and when one call exists on the shared line, a user can barge by pressing the line key that corresponds to the call. To enable SBB, choose the applicable setting from the Single Button Barge drop-down list box that is on the Phone Configuration window.
If more than one call exists on the line or if SBB is not enabled, the user must highlight the call and press the Barge or cBarge softkey instead.
Supported Cisco Unified IP Phones (SCCP only)
7941G, 7941G-GE, 7942G, 7945G, 7961G, 7961G-GE, 7962G, 7965G, 7970G, 7971G and G-GE, 7975G
Join Across Lines (SCCP)
Join allows a user to join and combine existing calls into a conference. Previous to release 6.1, Join required that calls be on the same line.
Join Across Lines (JAL) allows a user to join calls that are on multiple lines (either on different DNs, or on the same DN but on different partitions).
To enable JAL, choose the applicable setting from the Join Across Lines drop-down list box that is on the Phone Configuration window.
Supported Cisco Unified IP Phones (SCCP only)
7931G, 7940G, 7960G, 7941G, 7941G-GE, 7942G, 7945G, 7961G, 7961G-GE, 7962G, 7965G, 7970G, 7971G and G-GE, 7975G
Cisco Unified IP Phone Support for Cisco Unified Communications Manager 6.1 Features
Table 2 lists Cisco Unified IP Phones that support new Cisco Unified Communications Manager 6.1 features.
Cisco and Third-Party APIs
This following sections describe new features and changes that are pertinent to this release of the Cisco Unified Communications Manager APIs and the Cisco extensions to third-party APIs.
•
•
Cisco Unified TAPI
The following sections provide information about Cisco Unified TAPI for Cisco Unified Communications Manager Release 6.1(1a). Refer to Cisco Unified TAPI Developers Guide for additional information about Cisco Unified TAPI.
•
New Features
The following new features apply.
TSP Intercom Support with Extension Mobility
•
•
•
•
TSP Product Security Incident Response Team (PSIRT) Enhancements
•
•
TSP Join Across Lines
•
•
•
•
•
•
•
TSP Vista Support
•
•
–
–
–
–
Backward Compatibility Overview
No backward compatibility issue exists for all features that are introduced in 6.0 release if the feature is not used
Join Across Lines Use Case
This section provides an example of the join across lines functionality.
Cisco Unified JTAPI
The following sections provide information about Cisco Unified JTAPI for Cisco Unified Communications Manager Release 6.1(1a). Refer to Cisco Unified JTAPI Developers Guide for related information about Cisco Unified JTAPI.
•
•
New Features
These new features apply.
Certificate Download API Enhancement
New certificate download APIs provide increased security. New APIs require applications to specify a certificate passphrase, which is used to encrypt the java key store where client/server certificates are stored.
The system deprecates old certificate download APIs but they are still supported to avoid backward compatibility issue for applications. Cisco strongly recommends that applications migrate to the new APIs.
JTAPI also provides new API deleteCertificate() and deleteSecurityPropertyForInstance(), which applications can use to delete certificates that are already installed. To change passphrase for the certificate java key store, an application must delete the old certificate by using this API and upload the new certificate.
The enhanced JTAPI Preferences security tab provides two new buttons:
•
•
Be aware that this feature is compatible with previous releases of Cisco Unified Communications Manager.
Join Across Lines
The join across lines feature allows support for conferences across lines. It allows two or more calls on different addresses of the same terminal to be joined though the Join softkey on a Cisco Unified IP Phone or through the conference() API that JTAPI provides.
The behavior to JTAPI applications will change from previous releases because applications will not see a common controller in final and consult calls. No change occurs in the API, and same events get delivered whether calls are conferenced on the same address (regular conference) or across addresses (join across lines). When the join across lines feature is performed, CiscoConferenceStartEv/EndEv gets provided to all addresses on the controller terminal that have consult or final calls that are being joined into one conference. In CiscoConferenceStartEv, the conferenceControllerAddress always represents the primary controller address.
An application can set the controller via the setConferenceController() API. If an application does not specify this information, JTAPI itself finds a suitable controller for the conference. However, CIsco recommends that applications set the controller address when the join across lines feature is invoked. If an observer is not added on the controller address, applications may see null values for the talking or held terminal connection values in the CiscoConferenceStartEv.
With this release, the enhanced conference() API implementation means that all requests pass through after finding suitable terminal connections of the final and consult calls. JTAPI relies on the common terminal of the addresses that are involved in the call to find suitable terminal connections.
The system also supports multiple conference across address when more than two calls need to be joined.
SIP devices do not support this feature. JTAPI throws the exception (ILLEGAL_HANDLE) if this feature is requested on a SIP device.
You can disable this feature, which is backward compatible, by turning off the Join Across Lines Policy service parameter while Conference Chaining. You can disable the feature to allow a non-controller to add a participant to a conference by disabling the Advanced Ad Hoc Conference Enabled and Non-linear Ad Hoc Conference Linking Enabled service parameters.
Intercom Support for Extension Mobility
This enhancement provides support for the intercom feature for Extension Mobility while maintaining the single destination, non-sharable nature of intercom addresses. It requires intercom addresses to be configured with default terminal and allows configuring of intercom address on an Extension Mobility profile. When a user logs in to a terminal with an Extension Mobility profile that is configured with an intercom address, the system makes the intercom address available only if the default terminal of the intercom address is the same as the terminal where user logged in.
If an intercom address is configured on a terminal but the default terminal for the intercom address is not that terminal, the intercom address does not appear on the terminal. If this terminal is configured in the control list of JTAPI application, JTAPI does not create the intercom address in the provider domain.
From JTAPI point of view, no need exists for new interface or changes to support this feature. This feature, however, introduces some transitional scenarios in which the intercom functionary may not work on intercom addresses.
Consider this feature as compatible with previous releases of Cisco Unified Communications Manager.
Backward Compatibility Issues
This release of JTAPI is backward compatible with applications that are written for Cisco Unified Communications Manager 6.0.
Consider upgrading CiscoJtapiClient as not mandatory. Be aware that applications are required upgrade to Cisco Unified Communications Manager 6.1 CiscoJTAPIClient only if it is using any new features that are provided in this release.
Cisco Unified Communications Manager Configuration XML
The following sections provide information about Communications Manager Release 6.1(1a) XML. Refer to Cisco Unified Communications Manager XML Developers Guide for Release 6.0(1) for related information.
•
Documentation Updates
The information in Cisco Unified Communications Manager XML Developers Guide for Release 6.0(1) applies to Release 6.1(1a), with the following updates:
•
POST /axl/ HTTP/1.0Host:10.77.31.194:8443Authorization: Basic Q0NNQWRtaW5pc3RyYXRvcjpjaXNjb19jaXNjbw==Accept: text/*Content-type: text/xmlSOAPAction: "CUCM:DB ver=6.1"Content-length: 427<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xmlns:xsd="http://www.w3.org/2001/XMLSchema"><SOAP-ENV:Body><axl:getUser xmlns:axl=http://www.cisco.com/AXL/API/6.1xsi:schemaLocation="http://www.cisco.com/AXL/API/6.1 http://ccmserver/schema/axlsoap.xsd"sequence="1234"> <userid>tttt</userid> </axl:getUser></SOAP-ENV:Body></SOAP-ENV:Envelope>•
HTTP/1.1 200 OKServer: Apache-Coyote/1.1Set-Cookie: JSESSIONIDSSO=950805DE5E10F32C5788AE164EEC4955; Path=/Set-Cookie: JSESSIONID=151CF94ACF20728B1D47CC5C3BECC401; Path=/axl; SecureSOAPAction: "CUCM:DB ver=6.1"Content-Type: text/xml;charset=utf-8Content-Length: 728Date: Mon, 22 Jan 2007 06:51:42 GMTConnection: closeAdded and Changed APIs
Cisco Unified Communications Manager 6.1 adds no new calls..
Table 3 describes the API calls that changed from the previous release. These changes might require updates to existing user code in which a changed feature is used.
Backward Compatibility Issues
Be aware that all Cisco Unified Communications Manager 6.0 AXL methods, with the exception of ExecuteSQLQuery and ExecuteSQLupdate, are backward compatible with Cisco Unified Communications Manager 6.1. By default, the interface automatically uses the 6.0 AXL schema. Developers should specify SOAPAction: "CUCM:DB ver=6.1" in the HTTP header to use any new 6.1 methods.
AXL Database APIs
Find detailed information for each method below in the Cisco Unified Communications Manager AXL-SOAP API Documentation - v6.0(1) Interface Specification, which is available at Cisco Developer Services:
Table 4 provides information about the AXL database APIs. This table includes these designations:
•
•
•
Table 4 AXL Database APIs
addAARGroup
X
X
X
S
S
X
X
X
S
S
S
removeAARGroup
X
X
X
S
S
X
X
X
S
S
S
updateAARGroup
X
X
X
S
S
X
X
X
S
S
S
getAARGroup
X
X
X
S
S
X
X
X
S
S
S
updateAARGroupMatrix
X
X
X
S
S
X
X
X
S
S
S
listAARGroupByName
S
S
S
S
S
S
S
S
S
S
S
addApplicationToSoftkeyTemplate
X
X
X
S
S
X
X
X
S
S
S
removeApplicationToSoftkeyTemplate
X
X
X
S
S
X
X
X
S
S
S
updateAppUser
X
X
X
X
X
S
S
S
M
S
S
addAttendantConsoleHuntGroup
X
X
X
S
S
S
S
S
S
S
S
removeAttendantConsoleHuntGroup
X
X
X
S
S
S
S
S
S
S
S
updateAttendantConsoleHuntGroup
X
X
X
S
S
M
S
S
S
S
S
getAttendantConsoleHuntGroup
X
X
X
S
S
S
S
S
S
S
S
addAttendantConsoleUser
X
X
X
S
S
S
S
S
S
S
S
removeAttendantConsoleUser
X
X
X
S
S
S
S
S
S
S
S
updateAttendantConsoleUser
X
X
X
S
S
S
S
S
S
S
S
getAttendantConsoleUser
X
X
X
S
S
S
S
S
S
S
S
addCalledPartyTransformationPattern
X
X
X
X
X
X
X
X
X
X
S
removeCalledPartyTransformationPattern
X
X
X
X
X
X
X
X
X
X
S
updateCalledPartyTransformationPattern
X
X
X
X
X
X
X
X
X
X
S
getCalledPartyTransformationPattern
X
X
X
X
X
X
X
X
X
X
S
addCallerFilterList
X
X
X
X
X
X
X
X
S
S
S
removeCallerFilterList
X
X
X
X
X
X
X
X
S
S
S
updateCallerFilterList
X
X
X
X
X
X
X
X
S
S
S
getCallerFilterList
X
X
X
X
X
X
X
X
S
S
S
addCallManager
S
S
S
S
S
M
S
S
S
S
S
removeCallManager
S
S
S
S
S
S
S
S
S
S
S
updateCallManager
S
S
S
S
S
M
S
S
S
S
S
getCallManager
S
S
S
S
S
M
S
S
S
S
S
addCallManagerGroup
S
S
S
S
S
S
S
S
S
S
S
removeCallManagerGroup
S
S
S
S
S
S
S
S
S
S
S
updateCallManagerGroup
S
S
S
S
S
S
S
S
S
S
S
getCallManagerGroup
S
S
S
S
S
S
S
S
S
S
S
addCallPark
S
S
S
S
S
M
S
S
S
S
S
removeCallPark
S
S
S
S
S
S
S
S
S
S
S
updateCallPark
S
S
S
S
S
S
S
S
S
S
S
getCallPark
S
S
S
S
S
S
S
S
S
S
S
addCallPickupGroup
S
S
S
S
S
S
S
S
M
S
S
removeCallPickupGroup
S
S
S
S
S
S
S
S
S
S
S
updateCallPickupGroup
S
S
S
S
S
S
S
S
M
S
S
getCallPickupGroup
S
S
S
S
S
S
S
S
M
S
S
getCCMVersion
X
X
X
X
X
X
X
X
S
S
S
addCMCInfo
X
X
S
S
S
S
S
S
S
S
S
removeCMCInfo
X
X
S
S
S
S
S
S
S
S
S
updateCMCInfo
X
X
S
S
S
S
S
S
S
S
S
getCMCInfo
X
X
S
S
S
S
S
S
S
S
S
addCommonDeviceConfig
X
X
X
X
X
X
X
X
S
S
M
removeCommonDeviceConfig
X
X
X
X
X
X
X
X
S
S
S
updateCommonDeviceConfig
X
X
X
X
X
X
X
X
S
S
M
getCommonDeviceConfig
X
X
X
X
X
X
X
X
S
S
M
addConferenceBridge
X
X
X
S
S
S
S
S
M
S
M
removeConferenceBridge
X
X
X
S
S
S
S
S
S
S
S
updateConferenceBridge
X
X
X
S
S
M
S
S
M
S
M
getConferenceBridge
X
X
X
S
S
S
S
S
M
S
M
addCredentialPolicy
X
X
X
X
X
X
X
X
S
S
S
removeCredentialPolicy
X
X
X
X
X
X
X
X
S
S
S
updateCredentialPolicy
X
X
X
X
X
X
X
X
S
S
S
getCredentialPolicy
X
X
X
X
X
X
X
X
S
S
S
addCSS
S
S
S
S
S
S
S
S
M
S
S
removeCSS
S
S
S
S
S
S
S
S
S
S
S
updateCSS
S
S
S
S
S
S
S
S
M
S
S
getCSS
S
S
S
S
S
S
S
S
M
S
S
listCSSByName
S
S
S
S
S
S
S
S
S
S
S
addCTIRoutePoint
S
M
S
S
S
S
S
S
S
S
M
removeCTIRoutePoint
S
S
S
S
S
S
S
S
S
S
S
updateCTIRoutePoint
S
M
S
S
S
S
S
S
S
S
M
getCTIRoutePoint
S
M
S
S
S
S
S
S
S
S
M
addDDI
S
S
S
S
S
X
X
X
X
X
X
Use IDP to add DDI, DialPlan, and DialPlanTag.
removeDDI
S
S
S
S
S
X
X
X
X
X
X
Use IDP to add DDI, DialPlan, and DialPlanTag.
updateDDI
S
S
S
S
S
X
X
X
X
X
X
Use IDP to add DDI, DialPlan, and DialPlanTag.
getDDI
S
S
S
S
S
S
S
S
S
S
S
addDeviceMobility
X
X
X
S
S
X
X
X
S
S
S
removeDeviceMobility
X
X
X
S
S
X
X
X
S
S
S
updateDeviceMobility
X
X
X
S
S
X
X
X
S
S
S
getDeviceMobility
X
X
X
S
S
X
X
X
S
S
S
addDeviceMobilityGroup
X
X
X
S
S
X
X
X
S
S
S
removeDeviceMobilityGroup
X
X
X
S
S
X
X
X
S
S
S
updateDeviceMobilityGroup
X
X
X
S
S
X
X
X
S
S
S
getDeviceMobilityGroup
X
X
X
S
S
X
X
X
S
S
S
addDeviceProfile
S
M
M
S
S
S
S
M
M
M
S
removeDeviceProfile
S
S
S
S
S
S
S
S
S
S
S
updateDeviceProfile
S
M
M
S
S
M
S
M
M
M
S
getDeviceProfile
S
M
M
S
S
S
S
M
M
M
S
addDevicePool
S
M
S
M
S
M
S
M
M
M
M
removeDevicePool
S
S
S
S
S
S
S
S
S
S
S
updateDevicePool
S
M
S
M
S
M
S
M
M
M
M
getDevicePool
S
M
S
S
S
S
S
M
M
M
M
listDevicePoolByName
S
S
S
S
S
S
S
S
S
S
S
addDialPlan
S
S
S
S
S
X
X
X
X
X
X
Use IDP to add DDI, DialPlan, and DialPlanTag.
removeDialPlan
S
S
S
S
S
X
X
X
X
X
X
Use IDP to remove DDI, DialPlan, and DialPlanTag.
updateDialPlan
S
S
S
S
S
X
X
X
X
X
X
Use IDP to update DDI, DialPlan, and DialPlanTag.
getDialPlan
S
S
S
S
S
S
S
S
S
S
S
addDialPlanTag
S
S
S
S
S
X
X
X
X
X
X
Use IDP to add DDI, DialPlan, and DialPlanTag.
removeDialPlanTag
S
S
S
S
S
X
X
X
X
X
X
Use IDP to remove DDI, DialPlan, and DialPlanTag.
updateDialPlanTag
S
S
S
S
S
X
X
X
X
X
X
Use IDP to update DDI, DialPlan, and DialPlanTag.
getDialPlanTag
S
S
S
S
S
S
S
S
S
S
S
addDirectedCallPark
X
X
X
S
S
X
X
X
S
S
S
removeDirectedCallPark
X
X
X
S
S
X
X
X
S
S
S
updateDirectedCallPark
X
X
X
S
S
X
X
X
S
S
S
getDirectedCallPark
X
X
X
S
S
X
X
X
S
S
S
addFACInfo
X
X
S
S
S
S
S
S
S
S
S
removeFACInfo
X
X
S
S
S
S
S
S
S
S
S
updateFACInfo
X
X
S
S
S
S
S
S
S
S
S
getFACInfo
X
X
S
S
S
S
S
S
S
S
S
addGatekeeper
X
S
S
S
S
S
S
S
S
S
S
removeGatekeeper
X
S
S
S
S
S
S
S
S
S
S
updateGatekeeper
X
S
S
S
S
S
S
S
S
S
S
getGatekeeper
X
S
S
S
S
S
S
S
S
S
S
listGatekeeperByName
X
S
S
S
S
S
S
S
S
S
S
addGatewayEndpoint
S
M
M
S
S
M
S
S
M
S
M
removeGatewayEndpoint
S
S
S
S
S
S
S
S
S
S
S
updateGatewayEndpoint
S
M
M
S
S
M
S
S
M
S
M
getGatewayEndpoint
S
M
M
S
S
M
S
S
M
S
M
addH323Gateway
X
S
M
S
S
M
S
S
S
S
M
removeH323Gateway
X
S
M
S
S
S
S
S
S
S
S
updateH323Gateway
X
S
M
S
M
M
S
S
S
S
S
getH323Gateway
X
S
M
S
S
M
S
S
S
S
M
addH323Phone
X
S
M
S
S
M
S
M
M
S
M
removeH323Phone
X
S
M
S
S
S
S
S
S
S
S
updateH323Phone
X
S
M
S
M
S
S
M
M
S
M
getH323Phone
X
S
M
S
S
S
S
M
M
S
M
addH323Trunk
X
S
M
S
S
S
S
S
M
S
M
removeH323Trunk
X
S
M
S
S
S
S
S
S
S
S
updateH323Trunk
X
S
M
S
M
S
S
S
M
S
M
getH323Trunk
X
S
M
S
S
M
S
S
M
S
M
addHuntList
X
X
S
S
S
M
S
S
S
S
S
removeHuntList
X
X
S
S
S
S
S
S
S
S
S
updateHuntList
X
X
S
S
S
M
S
S
S
S
S
getHuntList
X
X
S
S
S
M
S
S
S
S
S
addHuntPilot
X
X
S
S
S
S
S
S
S
S
M
removeHuntPilot
X
X
S
S
S
S
S
S
S
S
S
updateHuntPilot
X
X
S
S
S
M
S
S
S
S
M
getHuntPilot
X
X
S
S
S
S
S
S
S
S
M
addIVRUserLocale
X
X
X
X
X
X
X
X
S
S
S
removeIVRUserLocale
X
X
X
X
X
X
X
X
S
S
S
aupdateIVRUserLocale
X
X
X
X
X
X
X
X
S
S
S
agetIVRUserLocale
X
X
X
X
X
X
X
X
S
S
S
updateLicenseCapabilities
X
X
X
X
X
X
X
X
S
S
S
getLicenseCapabilities
X
X
X
X
X
X
X
X
S
S
S
addLine
S
M
M
M
S
S
S
S
M
M
S
removeLine
S
S
S
S
S
S
S
S
S
S
S
updateLine
S
M
M
M
S
M
S
S
M
M
S
getLine
S
S
S
S
S
S
S
S
M
M
S
addLineGroup
X
X
X
S
S
M
S
S
S
S
S
removeLineGroup
X
X
X
S
S
M
S
S
S
S
S
updateLineGroup
X
X
X
S
S
M
S
S
S
S
S
getLineGroup
X
X
X
S
S
M
S
S
S
S
S
addLocation
S
M
S
S
S
S
S
S
S
S
S
removeLocation
S
S
S
S
S
S
S
S
S
S
S
updateLocation
S
M
S
S
S
S
S
S
S
S
S
getLocation
S
M
S
S
S
S
S
S
S
S
S
listLocationByName
S
S
S
S
S
S
S
S
S
S
S
addMediaResourceGroup
S
S
S
S
S
S
S
S
S
S
S
removeMediaResourceGroup
S
S
S
S
S
S
S
S
S
S
S
updateMediaResourceGroup
S
S
S
S
S
S
S
S
S
S
S
getMediaResourceGroup
S
S
S
S
S
S
S
S
S
S
S
listMediaResourceGroupByName
S
S
S
S
S
S
S
S
S
S
S
addMediaResourceList
S
S
S
S
S
S
S
S
S
S
S
removeMediaResourceList
S
S
S
S
S
S
S
S
S
S
S
updateMediaResourceList
S
S
S
S
S
S
S
S
S
S
S
getMediaResourceList
S
S
S
S
S
S
S
S
S
S
S
addMeetMe
X
X
X
S
S
X
X
X
S
S
S
removeMeetMe
X
X
X
S
S
X
X
X
S
S
S
updateMeetMe
X
X
X
S
S
X
X
X
S
S
S
getMeetMe
X
X
X
S
S
X
X
X
S
S
S
listMediaResourceListByName
S
S
S
S
S
S
S
S
S
S
S
addMGCP
S
S
S
S
S
S
S
S
M
S
S
MGCP represents the box level configuration for a gateway.
removeMGCP
S
S
S
S
S
S
S
S
S
S
S
updateMGCP
S
S
S
S
S
M
S
S
S
S
S
getMGCP
S
S
S
S
S
S
S
S
M
S
S
addMGCPEndpoint
S
M
S
S
S
M
S
S
S
S
M
MGCPEndpoint specifies the port on the gateway.
removeMGCPEndpoint
S
S
S
S
S
S
S
S
S
S
S
addMGCPUnit
S
S
S
S
S
S
S
S
S
S
S
MGCPUnit specifies the gateway Network Module.
removeMGCPUnit
S
S
S
S
S
S
S
S
S
S
S
addMGCPSubunit
S
S
S
S
S
S
S
S
S
S
S
MGCPSubunit specifies the gateway VIC or VWIC.
removeMGCPSubunit
S
S
S
S
S
S
S
S
S
S
S
addMobileVoiceAccess
X
X
X
X
X
X
X
X
S
S
S
removeMobileVoiceAccess
X
X
X
X
X
X
X
X
S
S
S
updateMobileVoiceAccess
X
X
X
X
X
X
X
X
S
S
S
getMobileVoiceAccess
X
X
X
X
X
X
X
X
S
S
S
addMobility
X
X
X
X
X
X
X
X
S
S
S
removeMobility
X
X
X
X
X
X
X
X
S
S
S
updateMobility
X
X
X
X
X
X
X
X
S
S
S
getMobility
X
X
X
X
X
X
X
X
S
S
S
updateMOHAudioSource
S
S
S
S
S
S
S
S
S
S
S
removeMOHAudioSource
S
S
S
S
S
S
S
S
S
S
S
Blanks out the MOHAudioSource as if it were removed.
getMOHAudioSource
S
S
S
S
S
S
S
S
S
S
S
listMOHAudioSourceByName
S
S
S
S
S
S
S
S
S
S
S
addMOHServer
X
X
X
S
S
X
X
X
S
S
M
removeMOHServer
X
X
X
S
S
X
X
X
S
S
S
updateMOHServer
X
X
X
S
S
X
X
X
S
S
M
getMOHServer
X
X
X
S
S
X
X
X
S
S
M
addPhone
S
M
M
S
S
M
S
M
M
M
M
removePhone
S
S
S
S
S
S
S
S
S
S
S
updatePhone
S
M
M
S
S
M
S
M
M
M
M
getPhone
S
M
M
S
S
M
S
M
M
M
M
listPhoneByDescription
S
S
S
S
S
S
S
S
S
S
S
listPhoneByName
S
S
S
S
S
S
S
S
S
S
S
listPhoneTemplateByName
S
S
S
S
S
S
S
S
S
S
S
addPhoneTemplate
X
X
X
S
S
X
X
X
S
S
S
removePhoneTemplate
X
X
X
S
S
X
X
X
S
S
S
updatePhoneTemplate
X
X
X
S
S
X
X
X
S
S
S
getPhoneTemplate
X
X
X
S
S
X
X
X
S
S
S
addPhysicalLocation
X
X
X
S
S
X
X
X
S
S
S
removePhysicalLocation
X
X
X
S
S
X
X
X
S
S
S
updatePhysicalLocation
X
X
X
S
S
X
X
X
S
S
S
getPhysicalLocation
X
X
X
S
S
X
X
X
S
S
S
addPilotPoint
X
X
S
S
S
M
S
S
S
S
S
removePilotPoint
X
X
S
S
S
S
S
S
S
S
S
updatePilotPoint
X
X
S
S
S
M
S
S
S
S
S
getPilotPoint
X
X
S
S
S
M
S
S
S
S
S
addProcessNode
S
S
M
S
S
S
S
S
S
S
M
removeProcessNode
S
S
M
S
S
S
S
S
S
S
S
updateProcessNode
S
S
M
S
S
S
S
S
S
S
M
getProcessNode
S
S
M
S
S
S
S
S
S
S
M
updateProcessNodeService
S
S
S
S
S
M
S
S
S
S
S
getProcessNodeService
S
S
S
S
S
M
S
S
S
S
S
listProcessNodesByService
S
S
M
S
S
S
S
S
S
S
S
listAllProcessNodes
S
S
M
S
S
S
S
S
S
S
S
addRecordingProfile
X
X
X
X
X
X
X
X
S
S
S
removeRecordingProfile
X
X
X
X
X
X
X
X
S
S
S
updateRecordingProfile
X
X
X
X
X
X
X
X
S
S
S
getRecordingProfile
X
X
X
X
X
X
X
X
S
S
S
addRegion
S
S
S
S
S
S
S
S
M
S
S
removeRegion
S
S
S
S
S
S
S
S
S
S
S
updateRegion
S
S
S
S
S
S
S
S
M
S
S
getRegion
S
S
S
S
S
S
S
S
M
S
S
updateRegionMatrix
S
M
S
S
S
S
S
S
M
S
S
addRemoteDestination
X
X
X
X
X
X
X
X
S
S
M
removeRemoteDestination
X
X
X
X
X
X
X
X
S
S
S
updateRemoteDestination
X
X
X
X
X
X
X
X
S
S
M
getRemoteDestination
X
X
X
X
X
X
X
X
S
S
M
addRemoteDestinationProfile
X
X
X
X
X
X
X
X
S
S
M
removeRemoteDestinationProfile
X
X
X
X
X
X
X
X
S
S
S
updateRemoteDestinationProfile
X
X
X
X
X
X
X
X
S
S
M
getRemoteDestinationProfile
X
X
X
X
X
X
X
X
S
S
M
updateResourcePriorityDefaultNamespace
X
X
X
X
X
X
X
X
X
X
S
getResourcePriorityDefaultNamespace
X
X
X
X
X
X
X
X
X
X
S
addResourcePriorityNamespace
X
X
X
X
X
X
X
X
X
X
S
removeResourcePriorityNamespace
X
X
X
X
X
X
X
X
X
X
S
updateResourcePriorityNamespace
X
X
X
X
X
X
X
X
X
X
S
getResourcePriorityNamespace
X
X
X
X
X
X
X
X
X
X
S
addResourcePriorityNamespaceList
X
X
X
X
X
X
X
X
X
X
S
removeResourcePriorityNamespaceList
X
X
X
X
X
X
X
X
X
X
S
updateResourcePriorityNamespaceList
X
X
X
X
X
X
X
X
X
X
S
getResourcePriorityNamespaceList
X
X
X
X
X
X
X
X
X
X
S
addSIPTrunkSecurityProfile
X
X
X
X
X
X
X
X
X
X
S
removeSIPTrunkSecurityProfile
X
X
X
X
X
X
X
X
X
X
S
updateSIPTrunkSecurityProfile
X
X
X
X
X
X
X
X
X
X
S
getSIPTrunkSecurityProfile
X
X
X
X
X
X
X
X
X
X
S
getMobileSmartClientProfile
X
X
X
X
X
X
X
X
X
X
S
addRouteFilter
S
S
S
S
S
S
S
S
S
S
S
removeRouteFilter
S
S
S
S
S
S
S
S
S
S
S
updateRouteFilter
S
S
S
S
S
S
S
S
S
S
S
getRouteFilter
S
S
S
S
S
S
S
S
S
S
S
addRouteGroup
S
S
S
S
S
S
S
S
S
S
S
removeRouteGroup
S
S
S
S
S
S
S
S
S
S
S
updateRouteGroup
S
S
S
S
S
S
S
S
S
S
S
getRouteGroup
S
S
S
S
S
S
S
S
S
S
S
addRouteList
S
M
M
S
S
S
S
S
S
S
M
removeRouteList
S
S
S
S
S
S
S
S
S
S
S
updateRouteList
S
M
M
S
S
S
S
S
S
S
M
getRouteList
S
M
M
S
S
S
S
S
S
S
M
addRoutePartition
S
S
M
S
S
S
S
S
M
S
S
removeRoutePartition
S
S
M
S
S
S
S
S
S
S
S
updateRoutePartition
S
S
M
S
S
S
S
S
M
S
S
getRoutePartition
S
S
M
S
S
S
S
S
M
S
S
listRoutePartitionByName
S
S
S
S
S
S
S
S
S
S
S
addRoutePattern
S
M
M
S
M
M
S
S
S
S
M
removeRoutePattern
S
S
S
S
S
S
S
S
S
S
S
updateRoutePattern
S
M
M
S
M
M
S
S
S
S
M
getRoutePattern
S
M
M
S
M
S
S
S
S
S
M
listRoutePlanByType
S
S
S
S
S
S
S
S
S
S
S
updateServiceParameter
S
S
S
S
S
M
S
S
S
S
S
getServiceParameter
S
S
S
S
S
S
S
S
S
S
S
listServiceParameters
S
S
S
S
S
S
S
S
S
S
S
addSIPProfile
X
X
X
X
X
X
X
X
X
X
S
removeSIPProfile
X
X
X
X
X
X
X
X
X
X
S
updateSIPProfile
X
X
X
X
X
X
X
X
X
X
S
getSIPProfile
X
X
X
X
X
X
X
X
X
X
S
addSIPRealm
X
X
X
X
X
X
S
S
S
S
S
removeSIPRealm
X
X
X
X
X
X
S
S
S
S
S
updateSIPRealm
X
X
X
X
X
X
S
S
S
S
S
getSIPRealm
X
X
X
X
X
X
S
S
S
S
S
addSIPTrunk
X
X
S
S
S
M
S
S
M
S
M
removeSIPTrunk
X
X
S
S
S
S
S
S
S
S
S
updateSIPTrunk
X
X
S
S
S
M
S
S
M
S
M
getSIPTrunk
X
X
S
S
S
M
S
S
M
S
M
updateSoftKeySet
X
X
X
S
S
X
X
X
S
S
S
getSoftKeySet
X
X
X
S
S
X
X
X
S
S
S
addSoftKeyTemplate
X
X
X
S
S
X
X
X
S
S
S
removeSoftKeyTemplate
X
X
X
S
S
X
X
X
S
S
S
updateSoftKeyTemplate
X
X
X
S
S
X
X
X
S
S
S
getSoftKeyTemplate
X
X
X
S
S
X
X
X
S
S
S
addTimePeriod
X
X
S
S
S
S
S
S
S
S
M
removeTimePeriod
X
X
S
S
S
S
S
S
S
S
S
updateTimePeriod
X
X
S
S
S
S
S
S
S
S
M
getTimePeriod
X
X
S
S
S
S
S
S
S
S
M
addTimeSchedule
X
X
S
S
S
S
S
S
S
S
M
removeTimeSchedule
X
X
S
S
S
S
S
S
S
S
S
updateTimeSchedule
X
X
S
S
S
S
S
S
S
S
M
getTimeSchedule
X
X
S
S
S
S
S
S
S
S
M
addTODAccess
X
X
X
X
X
X
X
X
X
X
S
removeTODAccess
X
X
X
X
X
X
X
X
X
X
S
updateTODAccess
X
X
X
X
X
X
X
X
X
X
S
getTODAccess
X
X
X
X
X
X
X
X
X
X
S
addTranscoder
X
X
X
S
S
X
X
X
S
S
M
removeTranscoder
X
X
X
S
S
X
X
X
S
S
S
updateTranscoder
X
X
X
S
S
X
X
X
S
S
M
getTranscoder
X
X
X
S
S
X
X
X
S
S
M
addTransformationPattern
X
X
X
X
X
X
X
X
S
S
M
For adding CallingPartyTransformationPattern
removeTransformationPattern
X
X
X
X
X
X
X
X
S
S
S
For removing CallingPartyTransformationPattern
updateTransformationPattern
X
X
X
X
X
X
X
X
S
S
M
For updating CallingPartyTransformationPattern
getTransformationPattern
X
X
X
X
X
X
X
X
S
S
M
For getting CallingPartyTransformationPattern
addTransPattern
S
M
S
S
S
S
S
S
S
S
M
removeTransPattern
S
S
S
S
S
S
S
S
S
S
S
updateTransPattern
S
M
S
S
S
M
S
S
S
S
M
getTransPattern
S
M
S
S
S
S
S
S
S
S
M
addUser
S
M
M
S
S
M
S
S
M
M
M
removeUser
S
M
M
S
S
S
S
S
S
S
S
updateUser
S
M
M
S
S
M
S
S
M
M
M
getUser
S
M
S
S
S
M
S
S
M
M
M
listUserByName
S
M
M
S
S
M
S
S
S
S
S
addUserGroup
X
X
X
X
X
S
S
S
S
S
S
removeUserGroup
X
X
X
X
X
S
S
S
S
S
S
updateUserGroup
X
X
X
X
X
S
S
S
S
S
S
getUserGroup
X
X
X
X
X
S
S
S
S
S
S
addVoiceMailPilot
X
X
S
S
S
S
S
S
S
S
S
removeVoiceMailPilot
X
X
S
S
S
S
S
S
S
S
S
updateVoiceMailPilot
X
X
S
S
S
S
S
S
S
S
S
getVoiceMailPilot
X
X
S
S
S
S
S
S
S
S
S
addVoiceMailPort
S
M
S
S
S
S
S
S
M
S
M
removeVoiceMailPort
S
S
S
S
S
S
S
S
S
S
S
updateVoiceMailPort
S
M
S
S
S
S
S
S
M
S
M
getVoiceMailPort
S
M
S
S
S
S
S
S
M
S
M
addVoiceMailProfile
X
X
S
S
S
S
S
S
S
S
S
removeVoiceMailProfile
X
X
S
S
S
S
S
S
S
S
S
updateVoiceMailProfile
X
X
S
S
S
S
S
S
S
S
S
getVoiceMailProfile
X
X
S
S
S
S
S
S
S
S
S
listVoiceMailProfileByName
S
S
S
S
S
S
S
S
S
S
S
createAutogeneratedProfile
S
S
S
S
S
S
S
S
S
S
S
doAuthenticateUser
X
X
X
X
X
S
S
S
S
S
S
doDeviceLogin
S
S
S
S
S
S
S
S
S
S
S
doDeviceLogout
S
S
S
S
S
M
S
S
S
S
S
doDeviceReset
S
S
S
S
S
M
S
S
S
S
S
executeSQLQuery
X
S
S
S
S
S
S
S
S
S
S
executeSQLUpdate
X
X
X
X
X
S
S
S
S
S
S
getNumDevices
S
S
S
S
S
S
S
S
S
S
S
listDeviceByNameAndClass
S
S
S
S
S
S
S
S
S
S
S
1 UCR = Under consideration or review.
Cisco Unified Communications Manager Serviceability XML
No changes occurred for Cisco Unified Communications Manager Serviceability XML from release 6.0, and no issues with backward compatibility exist.
Table 5 provides information about the Serviceability SOAP API. This table includes these designations:
•
•
•
Table 5 Serviceability SOAP API Details
RisPort (Real Time Information Port)
selectCmDevice
X
S
S
S
S
S
S
selectCtiItem
X
S
S
S
S
S
S
getServerInfo
X
X
X
S
S
S
S
SelectCmDevice (new API)
X
X
X
X
X
X
S
PerfmonPort (Performance Information Port)
perfmonOpenSession
S
S
S
S
S
S
S
perfmonAddCounter
S
S
S
S
S
S
S
perfmonRemoveCounter
S
S
S
S
S
S
S
perfmonCollectSessionData
S
S
S
S
S
S
S
perfmonCloseSession
S
S
S
S
S
S
S
perfmonListInstance
S
S
S
S
S
S
S
perfmonQueryCounterDescription
S
S
S
S
S
S
S
perfmonListCounter
S
S
S
S
S
S
S
perfmonCollectCounterData
S
S
S
S
S
S
S
ControlCenterServicesPort (All Service Control APIs)
soapGetStaticServiceList
X
X
X
S
S
S
S
soapGetServiceStatus
X
X
X
S
S
S
S
soapDoServiceDeployment
X
X
X
S
S
S
S
soapDoControlServices
X
X
X
S
S
S
S
getProductInformationList
X
X
X
X
S
S
S
LogCollectionPort (All Log Collection APIs)
listNodeServiceLogs
X
X
X
S
S
S
S
selectLogFiles
X
X
X
S
S
S
S
CDRonDemand (All CDR APIs)
get_file_list
X
X
X
S
S
S
S
get_file
X
X
X
S
S
S
S
DimeGetFileService (Getting Single File)
GetOneFile
X
X
X
S
S
S
S
1 UCR = Under consideration or review.
Caveats
The following sections contain information on how to obtain the latest resolved caveat information and descriptions of open caveats of severity level 1, 2, and 3.
Caveats describe unexpected behavior on a Cisco Unified Communications Manager server. Severity 1 caveats represent the most serious caveats, severity 2 caveats represent less serious caveats, and severity 3 caveats represent moderate caveats.
Resolved Caveats
You can find the latest resolved caveat information for Cisco Unified Communications Manager Release 6.1(1a) 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/action.do?hdnAction=searchBugs.
Using Bug Toolkit
Known problems (bugs) get graded according to severity level. These release notes contain descriptions of
•
•
You can search for problems by using the Cisco Software Bug Toolkit.
, you need the following items:
•
•
•
To use the Software Bug Toolkit, follow these steps:
Procedure
Step 1
Step 2
Step 3
For information about how to search for bugs, create saved searches, create bug groups, and so on, click Help in the Bug Toolkit window.
Open Caveats
Table 6 describes possible unexpected behaviors in Cisco Unified Communications Manager Release 6.1(1b), 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 Communications Manager interim versions in which the defect was fixed. These interim versions then get integrated into Cisco Unified Communications Manager releases.
Some more clearly defined versions include identification for Engineering Specials (ES) or Service Releases (SR); for example 03.3(04)ES29 and 04.0(02a)SR1. However, the version information that displays for the Cisco Unified Communications Manager maintenance releases may not be as clearly identified.
The following examples show how you can decode the maintenance release interim version information. These examples show you the format of the interim version along with the corresponding Cisco Unified Communications Manager release that includes that interim version. You can use these examples as guidance to better understand the presentation of information in these fields.
•
•
•
•
Note
Tip
.
Documentation Updates
The Updates to Cisco Unified Communications Manager 6.1(1) Documentation document provides information about documentation omissions, errors, or updates that are not included in the documentation that supports the Unified CM 6.1 release train.To obtain this document, go to the following URL:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/6_1_1/cucm-doc_updates-611.html.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
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.
