Table Of Contents
Release Notes for Cisco Unified Communications Manager Release 7.0(1)
Upgrading to Cisco Unified Communications Manager 7.0(1)
Upgrade Paths to Cisco Unified Communications Manager 7.0(1)
The Latest Software Upgrades for Unified CM 7.0 on Cisco.com
Download Locale Installer, Personal Assistant, and Cisco Security Agent
Use Microsoft Outlook to Receive Cisco Unified Communications Manager Licenses
Cisco Unified Communications Manager Attendant Console Plug-in
Installation Note for CTL Client 5.0 Plug-In
Installation Note for Windows 2000 Users
Error 444 Displays When You Add or Edit Nokia s60 Devices After You Upgrade to Cisco Unified CM 7.0
Serviceability Session Timeout Not Graceful
RTMT Requirement When Cisco Unified Communications Manager Is Upgraded
User Account Control Pop-up Window Displays During Installation of RTMT
For Serviceability, the Administrator That is Created During Installation Must Not Be Removed
Best Practices for Assigning Roles to Serviceability Administrators
Reset the Cluster After You Change the Security Password
ICSCsq22385 Database Replication Setup Fails After You Add a New Subscriber to a Cluster
Serviceability Not Always Accessible from OS Administration
CiscoTSP Limitations on Windows Vista Platform
Changes to Cisco Extension Mobility After Upgrade
CSCsr95074 CLI Command to Set IOWAIT Threshold Added
Cisco CallManager Service Stops After Upgrade to Cisco Unified Communications Manager Release 7.0
Do Not Log On To the Console During Busy Hours
Important Information about Delete Transaction by Using Custom File in BAT
Restoring Deleted Enterprise Cisco Unified IP Phone Services
Configuring the Hostname/IP Address in Cisco Unified Communications Manager
Deleting a Server and Adding a Deleted Server to a Cluster
Verifying and Repairing Database Replication
Clarification for Call Park Configuration
Viewing Privileges for Roles in Cisco Unified Communications Manager Administration
Serviceability Limitation When You Modify IP Addresses
Custom Background Images for Cisco Unified IP Phone 7906G and 7911G
Making Configuration Changes During an Upgrade
HP SCSI Hard Drive Firmware Update
CSCse71185: Certain HP Ultra320 SCSI HDs May Exhibit Reduced Perf and Timeouts
CSCse71295: HP FW Recommended to Min Potential for Media Errors on Certain SCSI HD
CSCso98836: HP Ultra320 SCSI HDD FW Upgrade
Resetting Database Replication When You are Reverting to an Older Product Release
utils dbreplication clusterreset
utils dbreplication dropadmindb
New and Changed Information for Cisco Unified Communications Manager Release 7.0(1)
Installation, Upgrade, Migration, and Disaster Recovery
Installation, Upgrade, and Replacement
Cisco Unified Communications Operating System Administration
Cisco Unified Communications Manager Administration
New and Updated Enterprise and System Parameters
Cisco Unified Communications Manager Features and Applications
Call Forward All Loop Prevention and Breakout
Cisco Emergency Responder Location Management Support in Application Server Configuration Window
Cisco Extension Mobility Feature Safe
Cisco Unified Communications Manager Attendant Console Support in 7.0(1)
Cisco Unified IP Phone Expansion Module 7915 and 7916 Support
Cisco Unified Mobility—Cisco Unified Mobile Communicator
Cisco Unified Mobility—Dial-via-Office Reverse Callback
Cisco Unified Mobility—Directed Call Park via DTMF
Cisco Unified Mobility—SIP URI Dialing
Cisco Unified Mobility—Time-of-Day (ToD) Access
Cisco Click-to-Conference Plug-In with IBM SameTime
G.729a and G.729b Codecs Over SIP Trunks
International Escape Character + Support
Microsoft Windows Server 2008 Active Directory (AD) Support for LDAP Synchronization
Non-Urgent Translation Patterns
Privacy Headers for SIP Trunks
SIP Support for Cisco Unified Communications Manager Features
SIP T.38 Interoperability with Microsoft Exchange
Cisco VG202 and VG204 Gateway Support in Cisco Unified Communications Manager Administration
Voice over Secure IP for SIP Trunks
Time of Day Access feature for the Bulk Administration Tool
Import and Export Enhancements for the Bulk Administration Tool
TAPS Name Change in Bulk Administration Tool
Cisco Unified Mobility Advantage Server Security Profile
Secure-Indication Tone Configuration
New Enterprise Parameters for Alarm Configuration
Configuring the Application Billing Servers
Vendor-Supported MIB OIDs and Descriptions Now Available
Cisco Unified Real-Time Monitoring Tool
CTIManager Improved Throughput
Simultaneous Alert Configuration
RTMT Alert Help in Syslog Viewer
Alert Definitions and Defaults
Cisco Unified Communications Manager CDR Analysis and Reporting
CAR Administrator Privileges Disappear after an Upgrade is Accomplished by Using DMA
Cisco Call Detail Records Has New Guide
Upgrading Cisco Unified Communications Manager
Supported Versions of FTP/SFTP for Billing Servers
Configuring Individual and Department Bills Reports
Configuring Mail Server Parameters
Configuring the CDR Load Schedule
Manual Purging or Reloading the CAR Database
Generating the CAR System Event Log
Configuring CDR Search by Cause for Call Termination
Enabling or Customizing Reports for Automatic Generation
Cisco Unified Communications Manager Call Detail Records
Partition/Extension Numbers in CDRs
Calling Party Normalization and Support for Dialing "+"
Local Route Groups and Called Party Transformation
Call Park CDR Examples with the Use Global Call ID of Parked Call Service Parameter
Video Conference Call CDR Example
Cisco-Specific Call Termination Cause Codes
Cisco Devices That Support VarQMetrics
Cisco Unified JTAPI Developers Guide
Join Across Lines with Conference Enhancements
Locale Infrastructure Development
Extension Mobility Username Login
selectRoute() with Calling Search Space and Feature Priority
Cisco Unified TAPI Developers Guide
Localization Infrastructure Changes
Cisco Unified Communications Manager XML Developers Guide
Administrative XML Layer (AXL) Application Programming Interface
AXL Serviceability Programming
Cisco Unified Communications Manager SCCP Messaging Guide
SCCP Messages Added or Modified
New Cisco Unified IP Phone Quick Start Guide for Administrative Assistants
Cisco Unified IP Phone Expansion Module 7914—SIP Support
Cisco Unified IP Phone Expansion Modules 7915 and 7916
Busy Lamp Field (BLF) Enhancements
Call Forward All Loop Breakout and Prevention
Calling Party Normalization and E.164
Extension Mobility Equivalency Enhancement
Enhanced Services Provisioning
Cisco Unified IP Phone 7931G—SIP Support
Personal Address Book and Fast Dials Enhancements
Programmable Line Keys—SIP Support
Join Across Lines and Single Button Barge—SIP Support
Select for Non-Shared Lines—SIP Support
Open Caveats for Cisco Unified Communications Manager Release 7.0(1) As of August 26, 2008
Cisco Unified Communications Operating System Administration
Parallel Upgrades from Unified CM Releases 5.x and 6.x to Unified CM Release 7.0(1)
Guidelines for Installing COP Files
Characters Allowed in a Pre-Shared Key
Cisco Unified Communications Manager Upgrade Requires a DVD
Upgrades from Cisco Unified Communications Manager 5.1(x)
Cisco Unified Communications Manager Administration
Description for Phone Personalization Is Incorrect in Documentation
Cisco Unified CM Group Chapter Needs Clarification of Auto-Registration Setting
Device Pool Chapter Contains Incomplete Description for Device Pool Name Field
LDAP Authentication Chapter Omits Information on SSL Certificates and IP Addresses/Hostnames
Enterprise Parameters and Service Parameters Chapters Omit Information on Set to Default Button
Information About Using an SRV Destination Port for the CUP Publish Trunk Service Parameter
AAR Group Chapter Includes Incorrect Description for Dial Prefix Field
Hunt Pilot Chapter Needs Clarification of Maximum Hunt Timer Setting
Annunciator Chapter Contains Incorrect Information on Description Field
Gateway Configuration Chapter Contains Incorrect Information on Domain Name Field
For SIP Trunks That are Used with Multiple Device Pools, Configure an SRV Destination Port
Default Device Profile Chapter Incorrectly Includes Expansion Module Settings
Information Omitted for Reroute Incoming Request to new Trunk based on Setting
Do Not Begin Starting and Ending Directory Numbers with a Zero (0)
Time-of-Day Routing Chapter Omits Information About Defined Time Periods
Number of Digits Field Description is Incorrect
Clustering Chapter Omits Information About Subsequent (Subscriber) Node
Redundancy Chapter Needs Clarification on Device Pools and Cisco Unified CM Groups
Licensing Chapter Omits Information on Adjunct Licensing
Cisco TFTP Chapter Omits Configuration Tip on Centralized TFTP
Directory Numbers Chapter Includes Incorrect Example for Shared Lines and Call Forward Busy Trigger
Media Termination Point (MTP) and Transcoder Chapters Omit Information on Call Throttling
CTI Chapter Does Not Describe How Line/Device CSS Works for Redirected Calls
SIP Chapter Omits Information on SIP Port Throttling
SIP Chapter Contains Information on Licensing That Does Not Apply
Trunk Chapter Omits Restrictions for H.323/H.225 Trunks
Call Back Chapter Omits Fact That Cisco Unified IP Phones Support the Programmable Line Key (PLK)
cBarge Chapter Omits Information on Shared Line Restriction for Conferences
Directed Call Park Chapter Requires Update on Reverting Calls That Are Parked
Do Not Disturb Chapter Omits Information on DND Feature Priority
Intercom Chapter Omits How to Configure an Intercom Line or Speed-Dial Button
Information About Changing Region Bandwidth Settings When Video Calls Are Made
Cisco Unified Mobility User Hangs Up Mobile Phone But Cannot Resume Call on Desktop Phone
Cisco Unified Mobility Chapter Omits Information about the DN Mask Field
Cluster Service Activation Node Recommendations
Cisco Unified Real-Time Monitoring Tool
Cisco Unified Real-Time Monitoring Tool Administration Guide
Cisco Unified IP Phone Expansion Module 7914 Phone Guide
Cisco Unified Communications Manager Assistant
Online Help Notes for Hebrew and Arabic
Creating Filter Lists for a Manager
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Unified Communications Manager Release 7.0(1)
Updated July 09, 2009
These release notes discuss the following topics:
•
Updates Made After Initial Release of This Document
•
•
Note You can view the release notes for previous versions of Cisco Unified Communications Manager
here: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_release_notes_list.htmlBefore 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 "The Latest Software Upgrades for Unified CM 7.0 on Cisco.com" section.
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
The following sections comprise the system requirements for this release of Cisco Unified CM .
Server Support
Make sure that you install and configure Cisco Unified CM Release 7.0(1) 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 7.0(1), refer to the Supported Servers for Cisco Unified Communications Manager Releases: http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/prod_brochure0900aecd8062a4f9.html.
Note
Note
Note
Uninterruptible Power Supply
Ensure that you connect each Unified CM node to an uninterruptible power supply (UPS) to provide backup power and protect your system.
Caution
Upgrading to Cisco Unified Communications Manager 7.0(1)
The following sections contain information pertinent to upgrading to this release of Cisco Unified CM .
•
Before You Begin
Before you upgrade the software version of Cisco Unified Communications Manager, verify your current software version.
To do that, open Cisco Unified Communications Manager Administration. The following information displays:
•
•
Upgrade Paths to Cisco Unified Communications Manager 7.0(1)
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.htmOrdering the Upgrade Media
To upgrade to Cisco Unified CM Release 7.0(1), use the Product Upgrade Tool (PUT) to obtain a media kit and license or to purchase the upgrade from Cisco Sales.
To use the PUT, you must enter your Cisco contract number (Smartnet, SASU or ESW) and request the DVD/DVD set. If you do not have a contract for Cisco Unified Communications Manager, you must purchase the upgrade from Cisco Sales.
For more information about 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
See the "Software Upgrades" chapter of the Cisco Unified Communications Operating System Administration Guide.
The Latest Software Upgrades for Unified CM 7.0 on Cisco.com
You can access the latest software upgrades for Unified CM 7.0 on Cisco.com.
•
Download Locale Installer, Personal Assistant, and Cisco Security Agent
To download Unified Commuications Manager Updates, Locale Installer, Personal Assistant, and Cisco Security Agent, follow this procedure.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
•
•
•
Download Phone Firmware
To download phone firmware, follow this procedure.
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Related Documentation
The view documentation that supports Cisco Unified CM Release 7.0(1), go to http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html
Limitations and Restrictions
A list of compatible software releases represents a major deliverable of Cisco Unified Communications Manager System testing. The recommendations, which are not exclusive, represent an addition to interoperability recommendations for each individual voice application or voice infrastructure product.
For a list of software and firmware versions of IP telephony components and contact center components that were tested for interoperability with Cisco Unified Communications Manager 7.0(1) as part of Cisco Unified Communications System Release 7.0 testing, see
http://www.cisco.com/go/unified-techinfo
Note
Important Notes
The following section contains information about caveats that Cisco Unified CM Release 7.0(1) resolves.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Use Microsoft Outlook to Receive Cisco Unified Communications Manager Licenses
When you obtain a license file from the Product License Registration window on www.cisco.com, the system sends the license file(s) to you via e-mail by using the e-mail ID that you provided. When you receive license files from e-mail clients other than Microsoft Outlook, for example, Microsoft Entourage, additional characters may exist in the license file, which can prevent you from being able to upload the license file in Cisco Unified Communications Manager Administration. To avoid this issue, Cisco recommends that you use Microsoft Outlook when you receive license files for Cisco Unified Communications Manager.
If you obtained a license file with additional characters in it, perform the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
For More Information
•
Cisco Extension Mobility Feature Safe Enhancements Require Cisco Unified Communications Manager 7.0 Device Package
To use the functionality that is described in the "Cisco Extension Mobility Feature Safe" section and in the "Cisco Extension Mobility" chapter in the Cisco Unified Communications Manager Features and Services Guide, you must install the Cisco Unified Communications Manager 7.0 device package that supports Cisco Extension Mobility feature safe when it becomes available on the Cisco Unified IP Phone software download site. For information on how to access the device package, refer to the "Download Phone Firmware" section. For information on how to install the device package, refer to the readme document that posts with the device package on the software site.
Cisco Unified Communications Manager Attendant Console Plug-in
If you upgraded Cisco Unified Communications Manager to release 7.0(1), you can download the Cisco Unified Communications Manager Attendant Console plug-in. Cisco does not support the Cisco Unified Communications Manager Attendant Console with new installations of Cisco Unified Communications Manager 7.0(1), and the plug-in does not display in the Find and List Plugins window in Cisco Unified Communications Manager Administration.
If you reinstall Cisco Unified Communications Manager 7.0 on a server after an upgrade to 7.0, the Cisco Unified Communications Manager Attendant Console plug-in does not display in Cisco Unified Communications Manager Administration on that server after you install 7.0.
Cisco recommends that you download the Cisco Unified Communications Manager Attendant Console plug-in from the first node in the cluster. Cisco recommends that you save the plug-in to a location on a PC that you will remember in case you cannot access Cisco Unified Communications Manager Administration.
Installation Note for CTL Client 5.0 Plug-In
If you are upgrading to the CTL Client 5.0 plug-in, you first need to remove eToken Run Time Environment 3.00 by performing the following steps:
Procedure
Step 1
http://support.microsoft.com/kb/290301Step 2
Step 3
Step 4
Step 5
Installation Note for Windows 2000 Users
If you are running Windows 2000 on your workstation or server, you must download Windows Installer 3.0 updates to correctly install CTL Client plug-ins. You can obtain Windows Installer 3.0 at the following URL:
Note
Windows Installer 3.0 requires validation. Follow the instructions to have your PC validated; then, install Windows Installer 3.0; reboot your machine, if necessary, and proceed with CTL Client installation.
Error 444 Displays When You Add or Edit Nokia s60 Devices After You Upgrade to Cisco Unified CM 7.0
Error 444 message displays in each of the two scenario circumstances that follow.
Circumstance 1
•
•
•
Circumstance 2
•
•
•
•
Workaround
Follow one of these suggestions.
1.
2.
a.
b.
Tip
c.
Tip
d.
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 by using the Logout button before making any changes in the user interface.
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.
User Account Control Pop-up Window Displays During Installation of RTMT
When you install RTMT on the Microsoft Vista platform, the system displays the User Account Control pop-up window to indicate that an unidentified program wants access to your computer. This occurs because of a limitation in the InstallAnywhere software. This one-time pop-up displays only when you are installing RTMT. Choose Allow to continue.
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.
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.
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
ICSCsq22385 Database Replication Setup Fails After You Add a New Subscriber to a Cluster
Database replication failure alert displays after you add a new subscriber node to an existing cluster.
After the fresh install completes successfully, the following alert displays (date and time vary).May 7 16:02:09 lg-pub-1 local7 2 : 116: May 07 20:02:09.491 UTC : %CCM_RTMT-RTMT-2-RTMT-ERROR-ALERT: RTMT Alert Name:DBReplicationFailure Detail: DBReplicationFailure occured. CallManager database replication errors, Reason code: Replication setup failed. The alert is generated on Wed May 07 16:02:09 EDT 2008 on node 10.1.1.1. App ID:Cisco AMC Service Cluster ID: Node ID:xxxThe primary AMC server, which by default is the publisher node, raises the DBReplicationFailure alert. You can observe this alert by using RTMT Alert Central or Summary view. You can also find the alerts in the EventViewer - Application Logs (CiscoSyslog) that you can access by using RTMT syslog viewer or platform CLI by using the file view activelog syslog/CiscoSyslog command.
Other Symptoms
The following list gives more symptoms of DBReplicationFailure that you may experience:
1.
dbl_repl_cdr_define_lg_sub_8_ccm6_1_2_1000_13-2008_05_07_12_00_20.logsucmd_err [su -c 'ulimit -c 0;cdr err --zap' - informix ]Executing [su -c 'ulimit -c 0;cdr define server --connect=lg_sub_8_ccm6_1_2_1000_13 --idle=0 --init --sync=g_lg_pub_1_ccm6_1_2_1000_13 g_lg_sub_8_ccm6_1_2_1000_13 --ats=/var/log/active/cm/log/informix/ats --ris=/var/log/active/cm/log/informix/ris;' - informix]We got exception in Cdr defineException from cdr define e.value[100] e.msg [Error executing [su -c 'ulimit -c 0;cdr define server --connect=lg_sub_8_ccm6_1_2_1000_13 --idle=0 --init --sync=g_lg_pub_1_ccm6_1_2_1000_13 g_lg_sub_8_ccm6_1_2_1000_13 --ats=/var/log/active/cm/log/informix/ats --ris=/var/log/active/cm/log/informix/ris;' - informix] returned [25600]]2.
11:47:51 CDR GC: GC could not verify the local server identity in CDR catalog with that in sqlhost file during CDR recovery.3.
By default, the publisher node DB replicator service continuously attempts to define the new server and generates a new log every 5 minutes.
Workaround for a Single Node
Use the following workaround for this caveat.
Caution
node 10.1.1.1. App ID:Cisco AMC Service Cluster ID: Node ID:xxx
Step 1
Step 2
utils dbreplication stop.
Caution
Wait for it to finish before you continue.
Step 3
utils dbreplication dropadmindb
Step 4
utils dbreplication reset <subname> (<subname> equals the name of the subscriber server)
At the end of the command output, the following message displays:
admin:utils dbreplication reset nw104a-195Repairing of replication is in progress.Background repair of replication will continue after that for 30 minutes..command failed -- Enterprise Replication not active (62)This output does not indicate a failure in the reset command. It serves as an informational message that got generated when you dropped the admindb on the subcriber. The reset will complete successfully.
The reset command returns immediately, but the operation can take 30 minutes or more to finish.
Workaround for Multiple Nodes
The preceding instructions apply for single nodes, but multiple subscriber servers may experience this failure. If that occurs, for each subscriber node that is a fresh install and displays the DBReplicationFailure alert, repeat the preceding steps.
Verification
Be aware that replication is set correctly when the RTMT Replication counter "Replicate_State" equals 2 for both the publisher server and the subscriber server that you reset.
You can monitor the counter via the RTMT Database Summary window or via the platform CLI.
Serviceability Not Always Accessible from OS Administration
In some scenarios, you cannot access Cisco Unified Serviceability from Cisco Unified OS Administration. The page displays a "Loading, please wait" message indefinitely.
If the redirect fails, log out from Cisco Unified OS Administration, select Cisco Unified Serviceability from the navigation menu, and log in to Cisco Unified Serviceability.
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.
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).
CSCsr95074 CLI Command to Set IOWAIT Threshold Added
Before you begin an upgrade, use RTMT , during off hours, to monitor the IOWAIT percentage. If it averages above 10 percent over 10 minutes, use the new CLI command utils iothrottle threshold low <new iowait val> to set the IOWAIT number to just above the 10-minute average.
Note
Three new CLI commands exist:
•
•
•
Note
Cisco CallManager Service Stops After Upgrade to Cisco Unified Communications Manager Release 7.0
After you upgrade to Cisco Unified Communications Manager 7.0 from a compatible Cisco Unified CM 5.X or 6.X release, the Cisco CallManager service does not automatically run, even though Cisco Unified Serviceability shows that the Cisco CallManager service is activated.
Immediately after you complete the upgrade to Cisco Unified Communications Manager 7.0, upload the software feature license that is required for Cisco Unified Communications Manager 7.0 in Cisco Unified Communications Manager Administration and restart the Cisco CallManager service in Cisco Unified Serviceability. Until you perform these tasks, devices fail to register with Cisco Unified Communications Manager 7.0.
For more information on licensing, refer to the licensing chapters in the Cisco Unified Communications Manager Administration Guide and the Cisco Unified Communications Manager System Guide.
CSCs096536—Cisco Extension Mobility Service Is Disabled, But You Can Still Get Service on Phone via Service URL
If you uncheck the Enable check box in the Phone Services Configuration window for the Cisco Extension Mobility service, restart the Cisco TFTP service, and reset the phone after you enable, configure, subscribe the phone to the Cisco Extension Mobility service, and add the service URL for the Cisco Extension Mobility service in Cisco Unified Communications Manager Administration, the phone displays the message, "Service not configured," although you can still see the Cisco Extension Mobility service and log in to the phone via the service URL.
To address this issue, perform one of the following tasks:
•
•
After you perform the task, restart the Cisco TFTP service and reset the device for the changes to take effect.
Do Not Log On To the Console During Busy Hours
Cisco does not recommend logging on to the console during busy hours because additional CPU resources get consumed. This can lead to Code Yellow or Code Red alarms depending on the tasks that are being performed and the CPU that is utilized to perform those tasks. Cisco recommends that Console usage (remote or local) should get used to do maintenance or upgrades during Maintenance windows.
Important Information about Delete Transaction by Using Custom File in BAT
Do not use the insert or export transaction files that are created with bat.xlt for the delete transaction. Instead, you must create a custom file with the details of the records that need to be deleted. Use only this file for the delete transaction. In this custom delete file, you do not need a header, and you can enter values for name, description, or user.
Cisco Unified Communications Manager Does Not Support Recovery of Administration or Security Passwords
Cisco Unified Communications Manager does not support recovery of administration or security passwords. If you lose these passwords, you must reset the passwords, as described in the Cisco Unified Communications Operating System Administration Guide.
The Cisco Unified Communications Operating System Administration Guide includes the section, "Recovering the Administrator or Security Passwords," instead of "Resetting the Administrator or Security Passwords." Access the "Recovering the Administrator or Security Passwords" section to reset the passwords.
Resolving Interoperability Issues for Calling Party Normalization and Cisco Unity/Cisco Unity Connection
Cisco Unified Communications Manager 7.0 supports the international escape character +, as described in the "International Escape Character + Support" section; however, Cisco Unity and Cisco Unity Connection do not support this character. Because these applications do not support the +, you must ensure that calls to Cisco Unity or Cisco Unity Connection do not contain the +, which ensures that voice-messaging features work as expected.
If you configure the + for the incoming prefix settings in Cisco Unified Communications Manager Administration to globalize the calling party number, the + gets inserted as a prefix to an incoming calling party number on a H.323, MGCP, or SIP gateway (or trunk, if applicable). If you configure calling party transformations, the device can localize the calling party number to transform the number to display differently than the globalized version. For example, a call from the North American Numbering Plan arrives as a 10-digit calling party number, 2225551234. Cisco Unified Communications Manager prefixes +1 to the calling party number to display the E.164 formatted number as +12225551234. On a phone in North America, Cisco Unified Communications Manager uses a calling party transformation to convert +12225551234 to 10 digits before the number displays on the phone; on a phone outside of North America, Cisco Unified Communications Manager may transform the number to only strip the + and to prefix the 00, as in 0012225551234.
For Cisco Unity and Cisco Unity Connection to work as expected, treat these applications as devices and configure calling party transformations that ensure that the + does not get sent to these voice-messaging applications. If the Cisco Unity or Cisco Unity Connection server uses a North American-based dial plan, localize the calling party number to NANP format before the voice-mail application receives the calling party number. Because no calling party transformation options exist in Cisco Unified Communications Manager Administration for voice-messaging ports, make sure that you configure the calling party number transformations in the device pool that is associated with the voice-messaging ports. To localize the calling party number, also consider prefixing access codes, so the voice-messaging application easily can redial the number for certain features, such as Live Reply. For example, you can convert +12225551234 to 912225551234, and you can convert international number, +4423453456, to include the international escape code, 90114423453456.
For more information on localizing the calling party number, see the "Calling Party Normalization" sectionand the "Calling Party Normalization" chapter in the Cisco Unified Communications Manager Features and Services Guide.
Restoring Deleted Enterprise Cisco Unified IP Phone Services
Cisco Unified Communications Manager 7.0 automatically installs the following enterprise Cisco Unified IP Phone services during the Cisco Unified Communications Manager 7.0 installation/upgrade:
•
•
•
•
•
•
•
You can customize, enable/disable, or delete these enterprise services, depending on the requirements for your system. For example, Cisco Unified Communications Manager disables the Intercom Calls service by default, but, if you want to do so, you can enable this service in the IP Phone Services Configuration window. Likewise, for example, you can update the Service URL field for the Corporate Directory service, so Cisco Unified Communications Manager points to your corporate directory server.
Cisco Unified Communications Manager Administration does not prevent you from deleting enterprise Cisco Unified IP Phone services. If you delete an enterprise Cisco Unified IP Phone service, you can restore the service by issuing the commands in Table 2 in the Command Line Interface (CLI). For information on how to start a CLI session, refer to Command Line Interface Reference Guide for Cisco Unified Solutions. For more information on Cisco Unified IP Phone services, refer to the Cisco Unified Communications Manager Administration Guide, the Cisco Unified Communications Manager System Guide, and the "Enhanced IP Phone Services" section.
Tip
Configuring the Hostname/IP Address in Cisco Unified Communications Manager
Table 3 lists the locations where you can configure a host name in Cisco Unified Communications Manager, the allowed number of characters for the host name, and the recommended first and last characters for the host name. Be aware that, if you do not configure the host name correctly, some components in Cisco Unified Communications Manager, such as the operating system, database, installation, and so on, may not work as expected.
Caution
Tip
Before you configure the host name in any of the locations in Table 3, review the following information:
•
After you install Cisco Unified Communications Manager on the publisher database server, the host name for the publisher automatically displays in this field. Before you install Cisco Unified Communications Manager on the subscriber server, enter either the IP address or the host name for the subscriber server in this field on the publisher database server.
In this field, only configure a host name if Cisco Unified Communications Manager can access the DNS server to resolve host names to IP addresses; make sure that you configure the Cisco Unified Communications Manager name and address information on the DNS server.
Tip
•
During the Cisco Unified Communications Manager installation on the subscriber server, you enter the hostname and IP address of the publisher database server, so Cisco Unified Communications Manager can verify network connectivity and publisher-subscriber validation. Additionally, you must enter the host name and the IP address for the subscriber server. When the Cisco Unified Communications Manager installation prompts you for the host name of the subscriber server, enter the value that displays in the Server Configuration window in Cisco Unified Communications Manager Administration; that is, if you configured a host name for the subscriber server in the Host Name/IP Address field.
Related Topics
•
•
•
•
•
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 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
Before you delete a server, consider the following information:
•
•
•
•
•
•
•
•
•
•
•
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:
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 7.0(1) 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 7.0(1).Step 3
Step 4
Verifying and Repairing Database Replication
To verify and repair database replication, perform the following procedure:
Procedure
Step 1
•
•
•
Step 2
admin: show perf query class "Number of Replicates Created and State of Replication"==>query class :- Perf class (Number of Replicates Created and State of Replication)has instances and values:ReplicateCount -> Number of Replicates Created = 344ReplicateCount -> Replicate_State = 2Be aware that the Replicate_State object shows a value of 2 in this case. The following list shows the possible values for Replicate_State:
•
•
•
•
•
Step 3
a.
b.
a.
a.
Step 4
a.
b.
c.
The following list shows the possible values for the Replication Status pane:
•
•
•
•
•
d.
Tip
Step 5
utils dbreplication repair usage:utils dbreplication repair [nodename]|allFor More Information
•
•
•
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, you must define a unique call park number or range of call park extension numbers 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.
Device Defaults Configuration Window Inaccurately Displays Only SCCP for the Cisco Unified IP Phone 7914 Expansion Module
Although the Device Defaults Configuration window in Cisco Unified Communications Manager Administration displays SCCP as the only supported protocol for the 7914 14-Button Line Expansion Module field, the Cisco Unified IP Phone Expansion Module can support either SCCP or SIP. For the 14-Button Line Expansion Module field, the default device load that displays in the Load Information field supports both protocols.
Viewing Privileges for Roles in Cisco Unified Communications Manager Administration
The Role Configuration window in Cisco Unified Communications Manager Administration displays the privileges for each standard role. To access the Role Configuration window, find the role by choosing User Management > Role; when the Find and List Roles window displays, click Find. Click the link for the standard role that you want to view. After the Role Configuration window displays, you can view the privileges in the Resource Access Information pane.
Serviceability Limitation When You Modify IP Addresses
When you modify the IP Address field, you cannot access the RTMT profiles, custom counters, custom alerts, and generic queries for Trace and Log Collection Tool (TLC) for that server.
You should manually remove any RTMT profiles, custom counters, custom alerts, and generic queries for Trace and Log Collection Tool (TLC) that were set for the old IP Address. 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 includes the 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 the 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.
Browser Requirements
The following browser requirements apply to Cisco Unified Communications Manager Administration, Cisco Unified Serviceability, Bulk Administration Tool, Cisco Unified Communications Operating System, Disaster Recovery System, and Cisco Unified Reporting:
•
•
Tip
The preceding GUIs do not support the buttons or browser controls in your browser. Do not use the browser buttons or browser controls (for example, the Back button) when you perform configuration tasks.
Custom Background Images for Cisco Unified IP Phone 7906G and 7911G
Phone background images may not display properly on the Cisco Unified IP Phone 7906G and 7911G with languages that use large fonts, such as Chinese, Japanese, and Korean. To modify a background image for proper display, follow these guidelines:
•
–
–
Upload the image files to %TFTPPATH%\Desktops\95x28x1.
•
<CiscoIPPhoneImageList>
<ImageItem Image="TFTP:Desktops/95x28x1/image.png"
URL="TFTP:Desktops/95x28x1/image.png" />
</CiscoIPPhoneImageList>
For more information, see the "Creating Custom Background Images" section in the Cisco Unified IP Phone 7906G and 7911G Administration Guide for Cisco Unified Communications Manager 7.0.
Software Feature License
When you upgrade from an earlier release of Cisco Unified Communications Manager to Release 7.0(1), you must download and install a software feature license to activate the new features. For instructions about how to obtain and install a software feature license, see the "License File Upload" chapter in the Cisco Unified Communications Manager Administration Guide.
Making Configuration Changes During an Upgrade
This section describes the restrictions that apply to the configuration and provisioning changes that you can make during an upgrade.
Administration Changes
The administrator must not make any configuration changes to Cisco Unified Communications Manager during an upgrade. Configuration changes include any changes that you make in Cisco Unified Communications Manager Administration, Cisco Unified Serviceability, and the User Option pages.
Any configuration changes that you make during an upgrade could get lost after the upgrade completes, and some configuration changes can cause the upgrade to fail.
For Cisco Unified Communications Manager Release 7.0(1), this restriction applies to upgrades from 4.x, 5.x, and 6.x releases.
For upgrades from Cisco Unified Communications Manager Release 4.x, you must discontinue all configuration activity before you run the Data Migration Assistant (DMA).
For upgrades from Cisco Unified Communications Manager Release 5.x and 6.x, you must discontinue all configuration activity before you upgrade to the new release by using either Cisco Unified Communications Operating System Administration or the Command Line Interface.
User Provisioning
For upgrades from Cisco Unified Communications Manager Release 4.x and 5.x, any provisioning that the end user performs to user-facing features after the upgrade begins could get lost.
For upgrades from Cisco Unified Communications Manager Release 6.x, changes that are made to the following user-facing features get preserved after the upgrade completes:
•
•
•
•
•
•
•
•
•
•
•
HP SCSI Hard Drive Firmware Update
The HP SCSI hard drive firmware update issue addresses the following defects:
•
•
•
CSCse71185: Certain HP Ultra320 SCSI HDs May Exhibit Reduced Perf and Timeouts
A ProLiant server configured with any of the HP Ultra320 SCSI hard drives listed in HP Customer Advisory #C00677430 (available at http://www.hp.com) may exhibit reduced performance or experience excessive timeouts.The dynamically adjusted seek time profile table in the drive firmware causes this performance issue after it becomes degraded.
When this problem occurs, occasional brief delays in command response time while servicing random workloads causes reduced performance and in severe cases the drive may exhibit command timeouts, which require a server reboot for recovery.
CSCse71295: HP FW Recommended to Min Potential for Media Errors on Certain SCSI HD
A ProLiant server configured with any of the HP Ultra320 SCSI hard drives listed in HP Customer Advisory #C00542020 (available at http://www.hp.com) may report media errors or illuminate the drive fault LED. The corrected firmware version (HPB4 or later) reduces the hard drive idle time that could potentially lead to build-up of media lubricant on the disk surface or drive head, causing the drives to report media errors or illuminate the drive fault LED.
CSCso98836: HP Ultra320 SCSI HDD FW Upgrade
A ProLiant server configured with any of the HP Ultra320 SCSI hard drives that are listed in HP Customer Advisory #C00859596 (available at http://www.hp.com) may exhibit timeouts and SCSI downshifts.
These problems may occur on the following server models:
•
•
•
•
•
•
•
•
The affected hard drives for these problems are listed in the associated HP Customer Advisories. However, the Cisco provided HP SCSI Hard Drive Firmware Update CD can be applied to all listed server types and the impacted drives will be updated if applicable.
To update the firmware to a Cisco tested level, use the Cisco provided HP SCSI Hard Drive Firmware Update CD released simultaneous to the Unified Communications 7.0(1) system release. For more details on installing the firmware, see the README.txt file for HP SCSI Hard Drive Firmware Update CD.
The ISO image for the Cisco provided HP SCSI Hard Drive Firmware Update CD and associated readme file may be obtained from Cisco.com at the following navigation path:
http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875240
From the Tools and Resources Downloads page, go to:
Communications Infrastructure ->
Voice Servers ->
Cisco 7800 Series Media Convergence Servers
<SERVER MODEL>
Latest Releases ->
Firmware ->
<Select: HP_SCSI_FW-1.0.1.iso>
<Select: HP_SCSI_FW-Readme.txt>
Resetting Database Replication When You are 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 that reminds you about the requirement to reset database replication if you are reverting to an older product release. The caveats CSCsl57629 and CSCsl57655 also document this behavior.
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
New and Changed Information for Cisco Unified Communications Manager Release 7.0(1)
The following section contains information that is new or changed for Cisco Unified Communications Manager Release 7.0(1).
•
•
•
•
•
•
•
•
•
•
•
Installation, Upgrade, Migration, and Disaster Recovery
This following sections describe the changes that were made to the installation, upgrade, and disaster recovery procedures in Cisco Unified Communications Manager 7.0(1):
Data Migration Assistant
DMA 7.0(1) exports RTMT Reports and Quality Reporting Tool (QRT reports) from Cisco Unified Serviceability to the DMA TAR file.
Installation/Upgrade (Migration) Considerations
DMA exports RTMT Reports data files that reside in C:\CiscoWebs\Service\RTMTReports\. DMA stores the files in the \serv\rtmt directory of the DMA TAR file.
DMA exports QRT files to the DMA TAR file that exists in the location that is specified in the Log File field in the Service Parameter Configuration window for the Cisco Extended Functions service. Ensure that the specified log file path is on the C:\ drive. If the path does not exist on the C:\ drive, DMA does not export the QRT reports, and the administrator must export the reports manually.
For More Information
Refer to the Data Migration Assistant User Guide and the Upgrading to Cisco Unified Communications Manager Release 7.0(1) from Cisco Unified Communications Manager 4.x Releases.
Disaster Recovery System
In Release 7.0, the Disaster Recovery System automatically backs up the backup device that you have configured in the Select Backup Device area of the Backup Device List window and the scheduled backups that you configured on the Schedule List window when you back up your system. When you perform a restore, the system restores the backup device and schedule, so you do not have to reconfigure those settings.
The Disaster Recovery System also provides status of the current restore procedure on the Restore Status window.
GUI Changes
The Restore Status window in the Disaster Recovery System contains a new Status column. This column shows the status of the restoration in progress, including the percentage of completion of the restore procedure. To access the Restore Status window, choose Restore > Status.
For More Information
For more information on the Disaster Recovery System, refer to the Disaster Recovery System Administration Guide.
Installation, Upgrade, and Replacement
This section contains information about installation, upgrade, and replacement changes for this release:
•
–
–
•
•
The patch set file uses the filename format CMUpgrade_UCOS_X.X.X.X-X.sgn.iso, where X.X.X.X-X specifies the release number. The process for upgrading from a local DVD remains the same.
To upgrade from a remote server, you must put the patch set files on the remote FTP or SFTP server. During the upgrade, when you enter the remote path to the upgrade patch, enter the remote path to the directory that contains the patch set files. For more information, refer to Cisco Unified Communications Operating System Administration Guide.
•
•
The Data Migration Assistant generates the configuration file during the DMA export process. If you choose to store the DMA TAR file on a network directory or local directory, DMA stores the platformConfig.xml in the same directory. If you choose to store the DMA TAR file on a tape drive, DMA stores the platformConfig.xml in D:/DMA.
To use the configuration file, copy the platformConfig.xml file to a USB key and place the USB key into the Cisco Unified Communications Manager first node before you boot the server with the Cisco Unified Communications Manager DVD.
•
Cisco Unified Communications Operating System Administration
This section describes changes to the Cisco Unified Communications Operating System Administration GUI.
Show IP Preferences
Cisco Unified Communications Operating System Administration contains a new window that displays a list of registered ports that the system can use. For a description of the fields in the IP Preferences window, see Table 4.
GUI Changes
To access the IP Preferences window from the Cisco Unified Communications Operating System Administration window, choose Show > IP Preferences.
For More Information
Refer to the Cisco Unified Communications Operating System Administration Guide.
Command Line Interface
This section provides information about the following CLI commands that are new or changed for Cisco Unified Communications Manager Release 7.0(1). For more information about command syntax and parameters, see the Command Line Interface Reference Guide for Cisco Unified Solutions.
•
For the current CLICisco Unified Communications Manager Bulk Administration Guide session, this command turns automatic pagination On or Off.
•
This command displays the status of automatic CLI pagination.
•
This command displays the nodes that are part of a network cluster.
•
This commands sets the network host name and then causes a restart of the system.
Caution
Note
•
If NTP is not already running, this command starts it.
•
This command restarts the NTP service.
•
This commands redirects where the system boot output gets sent.
•
This command starts a new upgrade wizard or assumes control of an existing upgrade wizard. The wizard prompts you for the location of the upgrade file.
•
This command collects all the files that are required for CSA diagnostics and assembles them ino a single CSA diagnostics file. You can retrieve this file by using the file get command.
•
This command stops all SNMP agents that the hardware vendor provides.
•
This command displays the list of ports that have been requested to be opened or translated in the firewalls. For a description of the show network ipprefs command output, see the "Show IP Preferences" section.
Cisco Unified Communications Manager Administration
This section contains information on the following topics:
•
•
Tip
New and Updated Enterprise and System Parameters
The following sections contain information on new and updated enterprise and service parameters:
Enterprise Parameters
To access the enterprise parameters in Cisco Unified Communications Manager Administration, choose System > Enterprise Parameters. To display the help for the enterprise parameter, click the name of the enterprise parameter in the window.
•
•
Service Parameters
To access the service parameters in Cisco Unified Communications Manager Administration, choose System > Service Parameters. Choose the server and the service name that the parameter supports. For some parameters, you may need to click Advanced to display the service parameter. To display the help for the service parameter, click the name of the service parameter in the window:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Menu Changes
This section contains information on the following menus in Cisco Unified Communications Manager Administration:
Main Window
If you have a Cisco Unified Presence server that is configured as part of the Cisco Unified Communications Manager cluster, the main Cisco Unified Communications Manager Administration window displays a link to the Cisco Unified Presence publisher server.
To access Cisco Unified PresenceAdministration, click the link to the Cisco Unified Presence publisher server.
System
The System menu provides the following new settings:
•
•
•
•
•
Call Routing
The Call Routing menu provides the following new and updated settings:
•
•
•
•
•
•
•
•
•
•
Media Resources
The Media Resources menu displays the following new and updated settings.
•
•
•
•
•
•
•
Voice Mail
The Voice Mail menu displays the following new and updated settings.
•
•
•
Device
The Device menu displays the following new and updated settings.
•
•
•
•
•
•
•
•
•
Application
No updates or new fields exist for this menu.
User Management
The User Management menu provides the following updates:
•
Bulk Administration
The Bulk Administration menu supports the following updates:
•
•
Cisco Unified Communications Manager Features and Applications
This section contains information on the following Cisco Unified Communications Manager Administration features and applications:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
–
–
Busy Lamp Field Pickup
The Busy Lamp Field (BLF) Pickup feature adds call pickup capability to BLF SpeedDial buttons. When enabled, this feature alerts a user when a BLF SpeedDial destination gets an incoming call, so the user can pick up the call. Call pickup groups control which phones a user can monitor and access. A call pickup group can now include a hunt pilot to support line group pickup.
The busy lamp field indicates the line state at the remote device. An animated icon, LED appearance, and optional tone indicate BLF alerting. You can enable audible alerts at the system and device level.
An alerting call state makes the BLF Pickup button function available. When the user presses the BLF Pickup button, the phone picks up the call.
•
•
•
After call pickup, the BLF Pickup button status reverts to the current status for the monitored destination: idle, busy, or DND (when enabled with the "BLF Status Depicts DND" service parameter).
You must modify the standard line button template to include the BLF SD option for users to invoke the BLF pickup feature. See "Configuring a Customized Phone Button Template for BLF SpeedDial Buttons" in the "Presence" chapter for more information.
The following phones that are equipped with BLF line buttons support the BLF pickup feature: Cisco Unified IP Phone 7931, Cisco Unified IP Phone 7941, Cisco Unified IP Phone 7961, Cisco Unified IP Phone 7970, and Cisco Unified IP Phone 7971. The Cisco Unified IP Phone Expansion Module 7914 supports this feature when it connects to one of these phones.
Adding Call Pickup to a BLF SpeedDial
Using a template that supports BLF SD, configure the BLF SpeedDial and enable call pickup for that destination in Cisco Unified Communications Manager Administration. See "Configuring BLF/SpeedDial buttons" for how to configure BLF speed dials.
You must also assign a subscriber calling search space to the monitoring device, or the user does not receive BLF notifications. See "Configuring and Applying the SUBSCRIBE Calling Search Space" for more information.
See "Cisco Unified Communications Manager Administration Configuration Tips" section for more information about configuring call pickup groups, calling search spaces, and hunt pilots to support the BLF Pickup feature.
Cisco Unified Communications Manager Administration Configuration Tips
Use the following tips to configure BLF pickup in Cisco Unified Communications Manager Administration:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
GUI Changes
The following phone vonfiguration parameters control BLF pickup settings.
•
•
•
Service Parameter and Enterprise Parameter Changes
The following service parameters control BLF pickup audible alerts for your system.
•
–
–
•
–
–
Installation/Upgrade (Migration) Considerations
BLF Pickup, a system feature, comes standard with Cisco Unified Communications Manager software. After you install Cisco Unified Communications Manager, you must configure BLF pickup settings in Cisco Unified Communications Manager Administration to enable the feature.
Serviceability Considerations
No changes for serviceability exist for this feature.
BAT Considerations
BAT supports exports and import of this feature as part of the export/import phones transaction.
BAT administrators can configure BLF pickup in the Busy Lamp Field Speeddial Configuration window. BAT administrators can set BLF pickup audible alerts for a device in the Phone Template Configuration window, through the Update phones functionality in BAT, or through the BAT.xlt (CSV file) and create file format options at the BAT GUI.
CAR/CDR Considerations
No changes for CAR and CDRs exist for this feature.
Security Considerations
To prevent unauthorized monitoring/pickup of user DNs, only administrators can configure BLF Speed Dials and enable call pickup. Administrators must ensure that the watcher is authorized to monitor a destination that is configured as a BLF/SpeedDial button.
CTI Considerations
The AXL add/update/get phone API supports the optional tag `BLFSdOptionBitMask' (blfSpeedDial.BlfSdOptionBitmask) under the parent tag `busyLampField.' The default specifies 0.
The AXL add/update/get phone API supports the optional tags `ringSettingIdleBLFAudibleAlert' (Device.tkBLFAudibleAlerting_Idle) and `ringSettingBusyBLFAudibleAlert' (Device.tkBLFAudibleAlerting_Busy) under the parent tag `busyLampField.' The default specifies 2.
User Tips
The BLF Pickup line button identifies the BLF pickup feature on your phone.
•
•
This feature adds a flashing "alerting" status icon (see the following example) to the existing BLF status icons: busy, idle, and DND (when configured with the BLF Status Depicts DND service parameter).
Phone users can enable or disable all audible phone alerts, including BLF pickup, with the DND softkey at the phone or the DND setting (when available) in the Cisco Unified CM User Options Device window.
For More Information
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Call Forward All Loop Prevention and Breakout
Cisco Unified Communications Manager prevents Call Forward All activation on the phone when a Call Forward All loop is identified. For example, Cisco Unified Communications Manager identifies a call forward loop when the user presses the CFA softkey on the phone with directory number 1000 and enters 1001 as the CFA destination, and 1001 has forwarded all calls to directory number 1002, which has forwarded all calls to directory number 1003, which has forwarded all calls to 1000. In this case, Cisco Unified Communications Manager identifies that a loop occurs and prevents CFA activation on the phone with directory number 1000.
Call Forward All loops do not impact call processing because Cisco Unified Communications Manager supports CFA loop breakout, which ensures that if a CFA loop is identified, the call goes through the entire forwarding chain, breaks out of the Call Forward All loop, and completes as expected, even if CFNA, CFB, or other forwarding options are configured along with CFA for one of the directory numbers in the forwarding chain. For example, the user for the phone with directory number 1000 forwards all calls to directory number 1001, which has forwarded all calls to directory number 1002, which has forwarded all calls to directory number 1000, thus creating a CFA loop. In addition, directory number 1002 has configured CFNA to directory number 1004. The user at the phone with directory number 1003 calls directory number 1000, which forwards to 1001, which forwards to 1002. Cisco Unified Communications Manager identifies a CFA loop, and the call, which breaks out of the loop, tries to connect to directory number 1002. If the No Answer Ring Duration timer expires before the user for the phone with directory number 1002 answers the call, Cisco Unified Communications Manager forwards the call to directory number 1004.
For a single call, Cisco Unified Communications Manager may identify multiple Call Forward All loops and attempts to connect the call after each loop is identified.
Cisco Unified Communications Manager Administration Configuration Tips
If Call Forward All activation occurs in Cisco Unified Communications Manager Administration or the Cisco Unified Communications Manager User Options, Cisco Unified Communications Manager does not prevent the CFA loop.
If the same directory number exists in different partitions, for example, directory number 1000 exists in partitions 1 and 2, Cisco Unified Communications Manager allows the CFA activation on the phone.
Cisco Unified Communications Manager prevents Call Forward All loops if CFA is activated from the phone, if the number of hops for a Call Forward All call exceeds the value that is specified for the Forward Maximum Hop Count service parameter, and if all phones in the forwarding chain have CFA activated [not Call Forward Busy (CFB), Call Forward No Answer (CFNA), or any other call forwarding options]. For example, if the user with directory number 1000 forwards all calls to directory number 1001, which has CFB and CFNA configured to directory number 1002, which has CFA configured to directory number 1000, Cisco Unified Communications Manager allows the call to occur because directory number 1002 acts as the CFB and CFNA (not CFA) destination for directory number 1001.
GUI Changes
If you do not want to use the default value, configure the Forward Maximum Hop Count service parameter. See the "New and Updated Enterprise and System Parameters" section.
Service Parameter and Enterprise Parameter Changes
The Forward Maximum Hop Count service parameter, which supports the Cisco CallManager service, specifies the maximum number of call hops that can occur for a Call Forward All chain; for example, if the value of this parameter equals 7, and a Call Forward All chain occurs consecutively from directory numbers 1000 to 1007, which equals 7 hops, Cisco Unified Communications Manager prevents a phone user with directory number 2000 from activating CFA to directory number 1000 because no more than 7 forwarding hops are supported for a single call. For more information on this service parameter, including special considerations for calls that use Q.SIG trunks, click the Forward Maximum Hop Count link in the Service Parameter Configuration window in Cisco Unified Communications Manager Administration.
Installation/Upgrade (Migration) Considerations
After you install Cisco Unified Communications Manager 7.0, you can configure call forward all loop prevention and breakout.
Serviceability Considerations
The call forward all loop prevention and breakout feature relies on the Cisco CallManager service, so activate this service in Cisco Unified Serviceability.
User Tips
If the phone user activates Call Forward All in Cisco Unified CM User Options, Cisco Unified Communications Manager does not prevent the CFA loop.
For More Information
•
Calling Party Normalization
In line with E.164 standards, calling party normalization enhances the dialing capabilities of some phones and improves call back functionality when a call is routed to multiple geographical locations; that is, the feature ensures that the called party can return a call without modifying the directory number in the call log directories on the phone. Additionally, calling party normalization allows you to globalize and localize phone numbers, so the appropriate calling number presentation displays on the phone.
Tip
Cisco Unified Communications Manager Administration Configuration Tips
The calling party number that displays for a shared line depends on the sequence of call control events in Cisco Unified Communications Manager. To avoid displaying an incorrect localized calling party number on a shared line, especially when the shared line occurs in different geographical locations, make sure that you configure the same Calling Party Transformation CSS for different devices that share the same line.
SIP trunks and MGCP gateways can support sending the international escape character, +, for calls. H.323 gateways do not support the +. QSIG trunks do not attempt to send the +. For outgoing calls through a gateway that supports +, Cisco Unified Communications Manager can send the + with the dialed digits to the gateway. For outgoing calls through a gateway that does not support +, the gateway strips the + when Cisco Unified Communications Manager sends the call information to the gateway.
SIP does not support the number type, so calls through SIP trunks only support the Incoming Calling Party Unknown Number Prefix settings.
A QSIG configuration usually supports a uniform dial plan. Transformation of numbers and prefixes may cause feature interaction issues if you have use QSIG.
For localizing the calling party number, the device must apply the transformation by using digit analysis. If you configure the Calling Party Transformation CSS as None, the transformation does not match and does not get applied. Ensure that you configure the Calling Party Transformation Pattern in a non-null partition that is not used for routing.
If your service provider prepends leading digits (for example, a zero) to the calling party number and you want to strip these digits before prepending other digits (for example, if the leading digits are not part of the E.164 number and you want to transform the calling party number to the E.164 format), you can enter a colon (:) followed by the number of digits that you want to strip in the Incoming Calling Party National Number Prefix, Incoming Calling Party International Number Prefix, Incoming Calling Party Unknown Number Prefix, and/or Incoming Calling Party Subscriber Number Prefix fields to ensure that Cisco Unified Communications Manager strips the leading digits before applying the prefixes to an incoming calling party number. The value that you configure before the colon (:) represents the prefix; the value that you configure after the colon (:) specifies the number of digits that you want Cisco Unified Communications Manager to strip from the calling party number before it applies the prefix.
For example, you configure +:1 in the incoming prefix fields, which alerts Cisco Unified Communications Manager to strip the first digit from the calling party number and then apply the international escape character +. If an incoming call arrives as 04423452345, Cisco Unified Communications Manager strips the first digit, in this case, zero, from the calling party number and prefixes the international escape character + to the calling party number. As a result, the calling party number gets transformed to +4423452345.
To strip digits without prefixing anything, you can configure the colon (:) in the incoming prefix fields without configuring a prefix. If you do not enter a prefix before the colon (:), Cisco Unified Communications Manager strips the number of leading digits that you specify and does not apply a prefix to the calling party number. For example, if you configure :2, Cisco Unified Communications Manager strips 2 leading digits without applying a prefix.
If you want Cisco Unified Communications Manager to strip a certain number of leading digits, and the entire number of digits for the calling party number equals or specifies less than the value that you configure, Cisco Unified Communications Manager strips all digits but still applies the prefix; that is, if you configure a prefix. For example, if you enter +1:6 in the incoming prefix fields, and the calling party number contains 6 or fewer digits, Cisco Unified Communications Manager strips all digits and applies the prefix +1.
If you configure Cisco Unified Communications Manager to strip more digits than exist in the calling party number, Cisco Unified Communications Manager clears the calling party number (makes it blank).
If you do not configure a colon (:) in the incoming prefix fields, Cisco Unified Communications Manager does not strip any digits from the calling party number.
If you configure a prefix but the calling party number that arrives is empty, Cisco Unified Communications Manager does not apply the prefix.
Cisco Unified Communications Manager can strip up to 24 digits from the calling party number. If you enter :26 in the incoming prefix fields, Cisco Unified Communications Manager Administration displays a message and does not allow the configuration.
If an error occurs when Cisco Unified Communications Manager attempts to strip the digits and apply the prefix to the calling party number, Cisco Unified Communications Manager does not manipulate the digits or apply the prefixes; instead, Cisco Unified Communications Manager uses the calling party number that arrived for the call.
GUI Changes
The following changes to the GUI apply:
•
•
•
•
•
•
Before the call occurs, the device must apply the transformation by using digit analysis. If you configure the Calling Party Transformation CSS as None, the transformation does not match and does not get applied. Ensure that you configure the Calling Party Transformation Pattern in a non-null partition that is not used for routing.
All phone device types, CTI route points, gateways, remote destination profiles, and trunks in Cisco Unified Communications Manager Administration can localize the calling party number for themselves; therefore, you can access this setting in the following windows in Cisco Unified Communications Manager Administration: Phone (Device > Phone), CTI Route Points (Device > CTI Route Point), Gateway (Device > Gateway), Trunk (Device > Trunk), Remote Destination Profile (Device > Device Settings > Remote Destination Profile)
•
Service Parameter and Enterprise Parameter Changes
Calling party normalization service parameters support the Cisco CallManager service, so before you configure calling party normalization, activate the Cisco CallManager service in Cisco Unified Serviceability. To locate the service parameters in Cisco Unified Communications Manager Administration, choose System > Service Parameters; choose the server and the Cisco CallManager service. After the parameters display, click Advanced. For information on the service parameter, click the hyperlink for the service parameter name or the question mark that displays in the upper, right corner of the window. The following service parameters support calling party normalization (globalization of the calling party number):
•
•
•
Installation/Upgrade (Migration) Considerations
After you install Cisco Unified Communications Manager 7.0, you can configure calling party normalization.
Serviceability Considerations
Calling party normalization relies on the Cisco CallManager service, so before you configure this feature, activate the service in Cisco Unified Serviceability.
BAT Considerations
You can configure the Calling Party Transformation CSS and Use Device Pool Calling Party Transformation CSS in BAT. You can also configure the incoming prefix settings.
CAR/CDR Considerations
For information on CAR support, see the "Cisco Unified Communications Manager CDR Analysis and Reporting" section.
For information on CDR support, see the "Cisco Unified Communications Manager Call Detail Records" section.
User Tips
Cisco Unified IP Phones 7906, 7911, 7931, 7961, 7962, 7965, 7970, 7971, and 7975 support calling party normalization. Depending on your configuration, a phone user may not need to edit the call log directory entry on the phone before placing a call. Depending on your configuration, the phone user may see the international escape character, +, in the call log directories on the phone.
For More Information
•
•
•
•
•
•
Cisco Emergency Responder Location Management Support in Application Server Configuration Window
Description
Cisco Unified Communications Manger 7.0 supports off-premise emergency call support in Cisco Emergency Responder 7.0.
Cisco Emergency Responder 7.0 supports Intrado V9-1-1 for Enterprise Service in the Cisco Unified Communications environment. If you subscribe to IntradoV9-1-1 for Enterprise Service, you can use Cisco Emergency Responder (ER) to simplify emergency call management. Cisco ER provides an interface that allows you to enter and synchronize on-premise and off-premise phone location information directly to the Intrado database. Cisco ER works in conjunction with Intrado to provide emergency services to phones that are located on the corporate network (on premise) and phones that are located away from the corporate network (off premise).
You must enable the Cisco Emergency Responder Location Management service in the Application Server Configuration in Cisco Unified Communications Manager Administration. When you enable the CER Location Management application, you enter the name that displays in the navigation drop-down box in the Cisco Unified CM User Options and the URL to the Cisco Emergency Responder Off-Premise window. In the Cisco_ER Off-Premise window, users can enter in their location information.
Users with off-premise phones cannot make emergency calls until they enter their location and associate this information with their directory number. After the location information is verified, emergency calls that are placed from off-premise phones can complete.
Cisco Unified Communications Manager Administration Configuration Tips
This feature requires you to enable Cisco Emergency Responder Location Management service in the Application Server Configuration in Cisco Unified Communications Manager Administration.
User Tips
See the Cisco Emergency Responder Off-Premise Location Management User Guide.
For More Information
•
Cisco Extension Mobility Feature Safe
Tip
Cisco Extension Mobility (EM) equivalency eliminates the phone-model dependency of phone button templates. The following factors determine the model equivalency among the various phones:
•
•
EM equivalency includes the following support feature for the Cisco Unified IP Phones:
•
Release 7.0(1) of Cisco Unified Communications Manager enhances the existing Extension Mobility (EM) equivalency mechanism. The equivalency enhancement works across phone types as follows:
•
•
•
•
•
•
•
The enhancement works for all phone models that are equivalent and requires no administration tasks to activate.
Note
Cisco Unified Communications Manager Administration Configuration Tips
To configure a phone button template for a Cisco Unified IP Phone, choose the Device > Device Settings > Phone Button Template in Cisco Unified Communications Manager Administration.
Serviceability Considerations
Cisco Extension Mobility relies on the Cisco CallManager service, so before you configure this feature, activate the service in Cisco Unified Serviceability.
Cisco Extension Mobility relies on the Cisco Extension Mobility service, which allows users to log in or log out of phones via Cisco Extension Mobility. Before you configure this feature, activate the Cisco Extension Mobility service in Cisco Unified Serviceability.
User Tips
Refer to the "Description" section for this feature.
For More Information
•
Cisco Unified Communications Manager Attendant Console Support in 7.0(1)
If you are upgrading from a compatible Cisco CallManager 4.X release or a compatible Cisco Unified Communications Manager 5.X or 6.X release to Cisco Unified Communications Manager Release 7.0(1), you can continue to use the Cisco Unified Communications Manager Attendant Console. As automated within the Cisco Unified Communications Manager upgrade process, the Cisco Unified Communications Manager Attendant Console plug-in will remain viewable from the Find and List Plugins window in Cisco Unified Communications Manager Administration 7.0(1).
Be aware, however, that Cisco no longer supports the Cisco Unified Communications Manager Attendant Console with new installations of Cisco Unified Communications Manager 7.0(x). For new installations, the Cisco Unified Communications Manager Attendant Console plug-in does not display in the Find and List Plugins window in Cisco Unified Communications Manager Administration.
If you previously obtained the Cisco Unified Communications Manager Attendant Console 7.0(1) plug-in from the Cisco software download site, you can use that plug-in with Cisco Unified Communications Manager 7.0(x) but only for upgrades of a compatible Cisco Unified Communications Manager 5.X, 6.X, or 7.0(x) release to Cisco Unified Communications Manager Release 7.0(x). Cisco Systems does not authorize the use of the Cisco Unified Communications Manager Attendant Console 7.0(x) plug-in with new Cisco Unified Communications Manager 7.0(x) installations, and its use does not get supported by the Cisco Technical Assistance Center.
If you need attendant console functionality after a Cisco Unified Communications Manager 7.0(x) installation/upgrade, Cisco recommends that you use the Cisco Unified Business Attendant Console, Cisco Unified Enterprise Attendant Console, or the Cisco Unified Department Attendant Console.
For More Information
•
•
•
To obtain the documentation for Cisco Unified Business Attendant Console, Cisco Unified Enterprise Attendant Console, or Cisco Unified Department Attendant Console, click the Release Notes link or the Maintain and Operate link after you go to the preceding URL.
•
Cisco Unified IP Phone Expansion Module 7915 and 7916 Support
Cisco Unified Communications Manager 7.0 adds support for the Cisco Unified IP Phone Expansion Module 7915 and Cisco Unified IP Phone Expansion Module 7916. The Cisco Unified IP Phone Expansion Module 7915 and Cisco Unified IP Phone Expansion Module 7916 attach to the following phones:
•
•
•
Each expansion module adds up to 24 extra line appearances or programmable buttons to a phone. You can attach up to two expansion modules to a Cisco Unified IP Phone for a total of 48 extra line appearances or programmable buttons.
Cisco Unified Communications Manager Administration Configuration Tips
If you are running SCCP, you can only configure a maximum of 42 lines on a phone. For example, if you configure two 24-line Cisco Unified IP Phone Expansion Modules on a Cisco Unified IP Phone, be aware that only the first 42 lines are available for use - including the first 6 or 8 lines on the Cisco Unified IP Phone.
For More Information
•
•
Cisco Unified Mobility—Cisco Unified Mobile Communicator
The Cisco Unified Mobile Communicator (CUMC) specifies a device type that you can configure in Cisco Unified Communications Manager Administration in the Phone Configuration window. The Cisco Unified Mobile Communicator operates with the Mobile Smart Client device protocol and uses three Device License Units (DLUs), or one DLU, if adjunct.
Cisco Unified Communications Manager Administration Configuration Tips
The following configuration takes place in Cisco Unified Communications Manager Administration to provision and enable the Cisco Unified Mobile Communicator device:
1.
Note
Note
2.
3.
4.
5.
6.
Cisco Unified Mobile Communicator Configuration Details
When you configure a Cisco Unified Mobile Communicator (CUMC), keep in mind the following configuration requirements as you configure the fields in the Phone Configuration window:
•
•
•
•
•
•
Ensure that a directory number is assigned to the Cisco Unified Mobile Communicator.
Keep in mind these other configuration requirements that apply to the Cisco Unified Mobile Communicator:
•
•
•
•
Cisco Unified Mobile Communicator General Considerations
Keep in mind the following general considerations for the Cisco Unified Mobile Communicator device:
•
•
•
•
•
GUI Changes
This feature entails the following GUI changes in Cisco Unified Communications Manager Administration:
•
•
•
•
Service Parameter and Enterprise Parameter Changes
This feature entails no service or parameter changes in Cisco Unified Communications Manager Administration.
Installation/Upgrade (Migration) Considerations
No installation considerations exist for this feature.
No automatic migration support exists for remote destinations. For a remote destination to be upgraded to a Cisco Unified Mobile Communicator device, manual upgrade of the remote destination must occur.
Serviceability Considerations
Cisco Unified Mobility relies on the Cisco CallManager service, so before you configure this feature, activate the service in Cisco Unified Serviceability.
Cisco Unified Mobility relies on the Cisco Extension Mobility service, which allows users to log in or log out of phones via Cisco Extension Mobility. Before you configure this feature, activate the Cisco Extension Mobility service in Cisco Unified Serviceability.
Cisco Unified Mobility relies on the Cisco Unified Mobile Voice Access service, which allows mobile voice access to function. Before you configure this feature, activate the Cisco Unified Mobile Voice Access service in Cisco Unified Serviceability.
Security Considerations
Configure the security profile for the CUMA server by using the System > Security Profile > CUMA Server Security Profile menu option in Cisco Unified Communications Manager Administration.
AXL and CTI Considerations
The following AXL consideration exists for this feature:
•
No CTI considerations exist for this feature.
User Tips
Users can configure their own Cisco Unified Mobile Communicator devices by using the Cisco Unified CM User Options windows. Users can specify the following settings:
•
•
For More Information
•
•
•
•
•
•
•
•
•
•
•
•
Cisco Unified Mobility—Dial-via-Office Reverse Callback
The Cisco Unified Mobility Dial-via-Office Reverse Callback feature resembles the Mobile Voice Access feature, except that Cisco Unified Communications Manager makes both calls. From the Cisco Unified Mobile Communicator (CUMC) client, using the data channel, the phone initiates the Reverse Callback feature. Cisco Unified Communications Manager then calls the remote destination first. When the remote destination answers, Cisco Unified Communications Manager calls the destination number.
Example of Dial-via-Office Reverse Callback
The following example illustrates the sequence of events that takes place in an instance of dial-via-office reverse callback:
1.
2.
3.
4.
5.
Example of Dial-via-Office Reverse Callback to Remote Phone
Using the preceding example, the following characteristics apply to a Reverse Callback instance when a remote phone is called:
1.
2.
3.
4.
CUMA support for this feature exists.
Example of Dial-via-Office Reverse Callback to Non-Remote Phone
Using the preceding example, the following characteristics apply to a Reverse Callback instance when a non-remote phone is called:
1.
2.
3.
4.
CUMA support for this feature exists.
Cisco Unified Communications Manager Administration Configuration Tips
The administrator must configure the enterprise feature access directory number (DN). Use the Call Routing > Directory Number menu option. You must perform this configuration step for the Dial-via-Office features to work.
GUI Changes
This feature entails no changes to the Cisco Unified Communications Manager Administration GUI.
Service Parameter and Enterprise Parameter Changes
This feature entails no service or enterprise parameter changes in Cisco Unified Communications Manager Administration.
Installation/Upgrade (Migration) Considerations
No installation considerations exist for this feature.
No automatic migration support exists for remote destinations. For a remote destination to be upgraded to a Cisco Unified Mobile Communicator device, manual upgrade of the remote destination must occur.
Serviceability Considerations
Cisco Unified Mobility relies on the Cisco CallManager service, so before you configure this feature, activate the service in Cisco Unified Serviceability.
Cisco Unified Mobility relies on the Cisco Extension Mobility service, which allows users to log in or log out of phones via Cisco Extension Mobility. Before you configure this feature, activate the Cisco Extension Mobility service in Cisco Unified Serviceability.
Cisco Unified Mobility relies on the Cisco Unified Mobile Voice Access service, which allows mobile voice access to function. Before you configure this feature, activate the Cisco Unified Mobile Voice Access service in Cisco Unified Serviceability.
AXL and CTI Considerations
The following AXL consideration exists for this feature:
•
No CTI considerations exist for this feature.
User Tips
This feature functions only for remote destinations that have configured a Cisco Unified Mobile Communicator client.
For More Information
•
•
•
•
•
•
Cisco Unified Mobility—Directed Call Park via DTMF
A user can park an existing call by using DTMF digits. Using Directed Call Park from the mobile phone, a user parks a call and inputs a unique mobility user park code. The user can subsequently retrieve the call with the code or have someone else retrieve the call with the code. This feature proves useful for certain vertical markets that require different departments or users to pick up calls.
When a user is in the enterprise and picks up a call on their mobile phone, they may want to pick the call up on a Cisco Unified IP Phone in a conference room or desk where the DN is not visible. The user can park the call and pick up the parked call with only their code.
When the mobile phone user is on an active call, by using the DTMF transfer feature, the user can park the call by transferring the parkee party to the park code that the system administrator configures and assigns to the user.
This feature allows the mobile phone user to park a call by transferring the parkee party to a user-selected park code. When the mobile phone user is on an active call, by using the DTMF transfer feature, the user can park the call by transferring the parkee party to the user-selected park code. The dialing sequence resembles the DTMF transfer sequence, except that a preconfigured parking code replaces the transfer number.
Example of Directed Call Park via DTMF—Parking the Call
In the following example, *82 specifies exclude hold, *84 specifies transfer, the pin specifies 12345, and the call park code specifies 3215. The following actions take place from the mobile phone:
1.
2.
3.
4.
Cisco Unified Communications Manager puts the parkee party on hold and provides dial tone to the parker party, just like the Call Transfer feature.
After Cisco Unified Communications Manager receives the dialed park code digit, the digit analysis engine verifies whether the dialed park code digits are valid. If so, the Directed Call Park feature intercepts the park code and verifies whether the park code is available. If the dialed park code is valid and available, the parker party receives the ringback tone, and the secondary call terminates to a Cisco Unified Communications Manager generic device that associates with the selected park code. The generic device automatically answers and places the parker party on hold with music on hold (MOH) or tone on hold. The last *84 completes the transfer of the parkee to the Cisco Unified Communications Manager generic device that associates with the selected park code. After the transfer completes, the parkee party receives the MOH or tone on hold, and the parkee gets parked on this selected park code and waits for retrieval.
If another user is already using the user-selected park code, Directed Call Park feature logic in Cisco Unified Communications Manager rejects that selected park code and plays busy tone to the parker party. The user gets to select another park code.
If the user-selected park code is not valid, Cisco Unified Communications Manager plays reorder tone to the parker party, and the user gets to select another park code.
For the Directed Call Park feature, be aware that the park code and code range are configurable across a cluster. Every Cisco Unified Communications Manager server in the cluster shares the park code and code range.
Example of Directed Call Park via DTMF—Retrieving the Parked Call
When a user attempts to retrieve the parked call, the user can go off hook on another mobile phone, and the user must use two-stage dialing to dial a digit string that contains the Directed Call Park retrieval prefix digits (for example, 22) plus the park code/code range (for example, 3215). The following sequence of events takes place:
1.
2.
Just like the existing Call Park feature, if the call does not get retrieved on time, the parked call reverts, by default, to the phone number that is associated with the parker party.
If a shared line is configured for the phone line of the parker, all phones that are associated with the shared line will ring. In addition, the dPark feature allows the user to configure a call park reversion number in the Call Park Administration window, so, if the call park reversion number is configured, the non-retrieved call reverts to this number, instead of to the parker party number.
Cisco Unified Communications Manager Administration Configuration Tips
If users want to park calls on extension numbers, the administrator needs to configure a park code or park code range that has extension numbers that compose part of the park code or park code range. For example, if the Cisco Unified Communications Manager system has extension DN range as 3xxx, the administrator can configure a park code range of 213xxx. When a user who has extension 3555 wants to park call on a park code that is associated with his extension, the user can dial park code 213555. Otherwise, call processing will not know whether the user attempts to transfer the call to an extension number or to park the call on a park code that is associated with an extension number.
When a user attempts to retrieve the parked call, the user can go off hook on another mobile phone, and the user must dial a digit string that contains directed call park retrieval prefix digits plus the park code/code range.
If directed call park park codes or code ranges overlap, or park codes/code ranges overlap with a DN range, the user may experience delay to retrieve a parked call due to interdigit time out. This represents an existing limitation of Cisco Unified Communications Manager. To avoid delays in retrieving a parked call, do not configure overlapped park codes/code ranges and do not overlap park codes/code ranges with the extension DN range.
Just like the existing call park feature, if a call is parked by the directed call park feature logic and the call is not retrieved on time, the parked call reverts to the address that is associated with the parker party by default. If a shared line is configured for the phone line of the parker, all phones that are associated with the shared line will ring. In addition, the directed call park feature allows the user to configure a call park reversion number in the Directed Call Park Configuration window, so, if the call park reversion number is configured, the nonretrieved call will revert to this number instead of to the party number of the parker.
GUI Changes
This feature entails no changes to the Cisco Unified Communications Manager Administration GUI.
Service Parameter and Enterprise Parameter Changes
This feature entails no service or enterprise parameter changes in Cisco Unified Communications Manager Administration.
Installation/Upgrade (Migration) Considerations
This feature does not require installation in Cisco Unified Communications Manager Administration.
This feature entails no upgrade (migration) considerations in Cisco Unified Communications Manager Administration.
Serviceability Considerations
Cisco Unified Mobility relies on the Cisco CallManager service, so before you configure this feature, activate the service in Cisco Unified Serviceability.
Cisco Unified Mobility relies on the Cisco Extension Mobility service, which allows users to log in or log out of phones via Cisco Extension Mobility. Before you configure this feature, activate the Cisco Extension Mobility service in Cisco Unified Serviceability.
Cisco Unified Mobility relies on the Cisco Unified Mobile Voice Access service, which allows mobile voice access to function. Before you configure this feature, activate the Cisco Unified Mobile Voice Access service in Cisco Unified Serviceability.
User Tips
The "Cisco Unified Mobility" chapter of the Cisco Unified Communications Manager Features and Services Guide provides examples of use cases for the Cisco Unified Mobility Directed Call Park with DTMF feature.
For More Information
Refer to the following documents for additional configuration details for this feature:
•
•
•
•
•
•
Cisco Unified Mobility—SIP URI Dialing
Description
This feature supports Session Initiation Protocol (SIP) Universal Resource Identifier (URI) as an additional type of remote destination for Cisco Unified Mobility. When the DN is called, Cisco Unified Communications Manager extends the call to a SIP trunk that digit analysis selects with this SIP URI in the To: header.
This feature only allows routing that is based only on the domain name, not based on the full SIP URI.
When a remote destination of this type is configured, other Cisco Unified Mobility features, such as two-stage dialing, transformation to DN number when calling into Cisco Unified Communications Manager, Interactive Voice Response (IVR) support, caller ID match, or DTMF transfer and conferencing, do not get supported.
SIP URI Example
For a remote destination, the SIP URI user@corporation.com is configured. Be aware that a SIP route pattern that specifies corporation.com must also be configured for the SIP URI remote destination to resolve correctly.
Cisco Unified Communications Manager Administration Configuration Tips
The SIP URI dialing feature entails a relaxation of the business rules to allow the entry of a URI in the Destination Number field of the Remote Destination Configuration window. (From Cisco Unified Communications Manager Administration, choose the Device > Remote Destination menu option.)
An additional requirement for this feature specifies that a SIP route pattern that matches the configured URI domain must be configured for the feature to work. To configure a SIP route pattern, from Cisco Unified Communications Manager Administration, choose the Call Routing > SIP Route Pattern menu option.
GUI Changes
This feature entails no changes to the Cisco Unified Communications Manager Administration GUI, but the Destination Number field of the Remote Destination Configuration window now allows entry of a SIP URI.
Service Parameter and Enterprise Parameter Changes
This feature entails no service or enterprise parameter changes in Cisco Unified Communications Manager Administration.
Serviceability Considerations
Cisco Unified Mobility relies on the Cisco CallManager service, so before you configure this feature, activate the service in Cisco Unified Serviceability.
Cisco Unified Mobility relies on the Cisco Extension Mobility service, which allows users to log in or log out of phones via Cisco Extension Mobility. Before you configure this feature, activate the Cisco Extension Mobility service in Cisco Unified Serviceability.
Cisco Unified Mobility relies on the Cisco Unified Mobile Voice Access service, which allows mobile voice access to function. Before you configure this feature, activate the Cisco Unified Mobile Voice Access service in Cisco Unified Serviceability.
AXL and CTI Considerations
The following AXL consideration exists for this feature:
•
No CTI considerations exist for this feature.
User Tips
See the "Description" section for a description of the features that the user can access upon receiving a call to a SIP URI.
For More Information
•
•
•
•
•
•
•
Cisco Unified Mobility—Time-of-Day (ToD) Access
An access list determines whether a call should be extended to a remote destination that is enabled for the Mobile Connect feature. With the addition of time-based control, the Time-of-Day Access feature adds time as another determination factor. The feature allows administrators and users to determine whether a call should reach a remote destination based on the time of day when the call is received.
For calls to remote destinations, the Time-of-Day Access feature adds a ring schedule and associates the ring schedule with an access list to determine the time-of-day access settings for a remote destination.
The provisioning process includes provisioning the following entities:
•
•
As an extension to the existing access list feature, ensure the Time-of-Day Access feature is accessible to end users of Cisco Unified Communications Manager. Therefore, you can provision the feature through use of both Cisco Unified Communications Manager Administration (by administrators) and Cisco Unified CM User Options (by end users).
Time-of-Day Access Example
The following example illustrates a specific time-of-day access application:
Block 1800! during business hours for user browser.
Cisco Unified Communications Manager Administration Configuration Tips
The following procedure provides an overview of the configuration that administrators perform in Cisco Unified Communications Manager Administration to configure the Time-of-Day Access feature for Cisco Unified Mobility:
1.
Use the User Management > End User menu option.
Note
Note
2.
Note
Use the Call Routing > Class of Control > Access List menu option.
3.
Use the Device > Remote Destination menu option.
Note
For successful time-of-day access configuration, you must configure the following areas in the Remote Destination Configuration window:
–
–
Checking the Enable Mobile Connect check box for the remote destination enables Cisco Unified Mobility to apply the settings in the When Mobile Connect is Enabled pane to calls that are made to this remote destination. If the Enable Mobile Connect check box is not checked, the settings do not apply to incoming calls to this remote destination, but the settings remain intact for future use.
Important Notes for Time-of-Day Access
The following important notes apply to time-of-day access configuration:
•
•
•
Refer to the user guide for the applicable Cisco Unified IP Phone model for details of the settings that end users can configure to customize their time-of-day access settings by using the Cisco Unified CM User Options windows.
GUI Changes
The following changes occurred to Cisco Unified Communications Manager Administration menu items:
•
•
•
Service Parameter and Enterprise Parameter Changes
This feature entails no service or enterprise parameter changes in Cisco Unified Communications Manager Administration.
Installation/Upgrade (Migration) Considerations
This feature does not require installation in Cisco Unified Communications Manager Administration.
The following database upgrade (migration) considerations exist for this feature during an upgrade from an earlier release to Release 7.0(1) of Cisco Unified Communications Manager:
•
•
•
Refer to the "Supported Use Cases for Migrating Activated Access Lists from an Earlier Cisco Unified Communications Manager Release" section for details of migration considerations for activated access lists that were created in an earlier release of Cisco Unified Communications Manager.
Serviceability Considerations
Cisco Unified Mobility relies on the Cisco CallManager service, sobefore you configure this feature, activate the service in Cisco Unified Serviceability.
Cisco Unified Mobility relies on the Cisco Extension Mobility service, which allows users to log in or log out of phones via Cisco Extension Mobility. Before you configure this feature, activate the Cisco Extension Mobility service in Cisco Unified Serviceability.
Cisco Unified Mobility relies on the Cisco Unified Mobile Voice Access service, which allows mobile voice access to function. Before you configure this feature, activate the Cisco Unified Mobile Voice Access service in Cisco Unified Serviceability.
BAT Considerations
In anticipation of new Cisco Unified Mobility features, Release 7.0(1) of Cisco Unified Communications Manager must support bulk provisioning of time periods, time schedules, and time-of-day access records through use of the Bulk Administration Tool (BAT).
In earlier releases, the Bulk Administration Tool provided manual migration support for MobilityManager 1.2.x to Release 7.0(1) of Cisco Unified Communications Manager.
The import/export function of the Bulk Administration Tool provides bulk insert and export support for time periods and time schedules. BAT and MobilityManager (for migration) user documentation provides details for how to bulk provision time-of-day access records (including where to insert time periods and time schedules).
Cisco Unified Communications Manager Bulk Administration Tool adds the following new submenu items to add/modify/delete/export time of day access settings:
•
•
•
The Cisco Unified Communications Manager Bulk Administration Tool Bulk Administration > Mobility submenu specifies all the mobility-related menu items (Access List, Remote Destination, Remote Destination Profile, Time of Day Access) to provide a tightly coupled navigation experience.
User Tips
The "Cisco Unified Mobility" chapter of the Cisco Unified Communications Manager Features and Services Guide provides examples of use cases.
The use case scenarios that follow detail the function of the time-of-day access feature with activated access lists that were configured prior to the addition of the time-of-day access feature in Release 7.0(1) of Cisco Unified Communications Manager, as well as with new provisioning that takes place for the feature starting with Release 7.0(1) of Cisco Unified Communications Manager.
Supported Use Cases for Migrating Activated Access Lists from an Earlier Cisco Unified Communications Manager Release
The following use cases detail the function of the Time-of-Day Access feature with Cisco Unified Mobility when migration of an activated access list from a, earlier release of Cisco Unified Communications Manager to Release 7.0(x) or later takes place:
•
Result after migration: The system allows all calls at all hours. The Remote Destination Configuration window displays the When Mobile Connect is Enabled pane. In the Ring Schedule pane, the All the time radio button gets checked. In the When Receiving a call during the above ring schedule pane, the Always ring this destination radio button gets checked.
•
Result after migration: Only the callers that belong to the allowed access list can reach the associated remote destination. The Remote Destination Configuration window displays the When Mobile Connect is Enabled pane. In the Ring Schedule pane, the All the time radio button displays as checked. In the When Receiving a call during the above ring schedule pane, the Ring this destination only if caller is in radio button displays as checked, and the access list displays in the corresponding drop-down list box.
•
Result after migration: The callers that belong to the blocked access list cannot reach the associated remote destination, but all other callers can call the remote destination at all hours. The Remote Destination Configuration window displays the When Mobile Connect is Enabled pane. In the Ring Schedule pane, the All the time radio button displays as checked. In the When Receiving a call during the above ring schedule pane, the Do not ring this destination if caller is in radio button displays as checked, and the access list displays in the corresponding drop-down list box.
Use Cases for Time-of-Day Access with the Current Cisco Unified Communications Manager Release
The following use cases detail the function of the Time-of-Day Access feature with Cisco Unified Mobility with the 7.0 release of Cisco Unified Communications Manager:
•
Configuration: Configure a ring schedule that specifies business hours from Monday to Friday and click the Always ring this destination radio button.
Result: The system allows all callers during business hours, but no calls get extended to this remote destination outside of business hours.
•
Configuration: Configure a ring schedule that specifies business hours from Monday to Friday, click the Ring this destination only if the caller is in radio button, and specify an access list.
Result: Only callers that belong to the access list can call the remote destination during business hours; all other callers get blocked during business hours. Outside business hours, no calls ring this remote destination.
•
Configuration: Configure a ring schedule that specifies business hours from Monday to Friday, click the Don't ring this destination if the caller is in radio button, and specify an access list.
Result: Only callers that belong to the access list get blocked from calling the remote destination during business hours; all other callers can call the remote destination during business hours. Outside business hours, no calls ring this remote destination.
For More Information
Refer to the following documents for additional configuration details for this feature:
•
•
•
•
•
•
•
•
•
•
Cisco Click-to-Conference Plug-In with IBM SameTime
For information on this feature, refer to the Integration Guide for Configuring the Cisco Click-to-Conference Plug-In with IBM Lotus Sametime, which describes how to configure Cisco Unified Communications Manager for this feature. To locate this document, go to http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_configuration_examples_list.html.
Before you configure this feature, refer to the Cisco Unified Communications Manager Software Compatibility Matrix for the click-to-conference feature at http://preview.cisco.com/en/US/products/sw/voicesw/ps556/prod_configuration_examples_list.html.
Directed Call Pickup
The Directed Call Pickup feature allows a user to pick up a ringing call on a directory number (DN) directly by pressing the GPickUp softkey and entering the directory number of the device that is ringing. Cisco Unified Communications Manager uses the associated group mechanism to control the privilege of a user who wants to pick up an incoming call by using Directed Call Pickup. The associated group of a user specifies one or more call pickup groups that have been associated to the pickup group to which the user belongs.
Cisco Unified Communications Manager Administration Configuration Tips
If a user wants to pick up a ringing call from a DN directly, the associated groups of the user must contain the pickup group to which the DN belongs. If two users belong to two different call pickup groups and the associated groups of the users do not contain the call pickup group of the other user, the users cannot invoke Directed Call Pickup to pick up calls from each other.
If a user wants to pick up a ringing call from a DN directly, the associated groups of the user must contain the pickup group to which the DN belongs. If two users belong to two different call pickup groups and the associated groups of the users do not contain the call pickup group of the other user, the users cannot invoke Directed Call Pickup to pick up calls from each other.
When the user invokes the Directed Call Pickup feature and enters a DN from which to pick up an incoming call, the user connects to the call that is incoming to the specified phone whether or not the call is the longest ringing call in the call pickup group to which the DN belongs.
If multiple calls are ringing on a particular DN and the user invokes Directed Call Pickup to pick up a call from the DN, the user connects to the incoming call that has been ringing the specified DN the longest.
GUI Changes
This feature entails no changes to the Cisco Unified Communications Manager Administration GUI.
Service Parameter and Enterprise Parameter Changes
This feature does not require any changes to the existing service or existing enterprise parameters in Cisco Unified Communications Manager Administration.
CAR/CDR Considerations
No CAR considerations exist for this feature.
The following CDR consideration exists for this feature:
•
User Tips
Be aware that the following restrictions are imposed upon users who try to use the Directed Call Pickup feature:
•
•
These restrictions apply beyond the configuration requirements that are detailed in the "Cisco Unified Communications Manager Administration Configuration Tips" section.
For More Information
•
•
•
•
•
•
•
•
•
•
Do Not Disturb Call Reject
The Do Not Disturb (DND) Call Reject feature, which is an enhancement to Do Not Disturb, allows the user or the administrator to configure Cisco Unified Communications Manager, so no incoming call information gets presented to user.
When DND is enabled, all new incoming calls with normal priority will honor the DND settings for the device. High-priority calls, such as Cisco Emergency Responder (CER) calls or calls with Multi-Level Precedence & Preemption (MLPP), will ring on the device. Also, when you enable DND, the Auto Answer feature gets disabled.
The user can enable and disable DND by any of the following methods:
•
•
•
The system administrator can also enable and disable DND on a per-phone basis in Cisco Unified Communications Manager Administration.
When you enable DND, the Cisco Unified IP Phone displays the message that Do Not Disturb is active. The DND line button icon also turns into an empty circle, and the light turns amber when DND is active.
Cisco Unified Communications Manager Administration Configuration Tips
When you enable DND on a device, the DND Option parameter allows you to specify how the DND features handle incoming calls:
•
•
•
Note
When you choose the DND Ringer Off or Call Reject option, DND Incoming Call Alert parameter specifies how a call displays on a phone.
•
•
•
•
Note
GUI Changes
To support DND Call Reject, Cisco Unified Communications Manager now includes the DND Option parameter.
To access the DND Option parameter for phones, choose Device > Phone.
To configure a device profile with DND Call Reject, choose Device > Device Settings > Device Profile.
To set up a common phone profile with DND Call Reject, choose Device > Device Settings > Common Phone Profile.
To configure a Remote Destination Profile with DND Call Reject, choose Device > Device Settings > Remote Destination Profile.
For More Information
•
•
•
•
•
•
G.Clear Codec Support
The G. Clear (Clear channel) codec enables tandem switching of Digital Signal-0 (DS-0) data circuits through a voice network that uses Media Gateway Control Protocol (MGCP) gateways, Session Initiation Protocol (SIP) trunks, and Cisco Unified Communications Manager. The MGCP gateway uses T1 PRI DS-0 circuits to communicate with Cisco Unified Communications Manager.
Figure 1 shows an example of the G.Clear codec configuration in an MGCP network. In this example, legacy video terminals, such as Polycoms, connect to separate PBX switches that are interconnected by the MGCP gateway. The terminals set up individual calls for each DS-0 by using "unrestricted digital information" in the Q.931 bearer capability. Cisco Unified Communications Manager treats the incoming ISDN signal as a voice call that is using G.Clear.
Figure 1 MGCP Network with G.Clear Codec
The G.Clear codec uses 64 kb/s of bandwidth (not including IP packet overhead), which is similar to the G.711 codec. The Cisco Unified Communications Manager Region Manager selects the codec of a voice call and prioritizes the G. Clear codec ahead of the G.711 mulaw and G.711 alaw codecs in the Region Manager media table.
You may require the G.Clear codec or the G.729 codec in a region or some other low-bandwidth codec for calls to remote regions. The G.729 codec, which is optimized for speech, uses significantly less bandwidth than the G. Clear codec. Be aware that the G.Clear codec is an option only to explicitly allow it to run in lower bandwidth regions.
G. Clear codec calls require separate DiffServ CodePoint (DSCP) values in the header of IP packets. This differs from traditional voice codecs and video calls and must be tagged uniquely by the MLPP precedence level. Added service parameters apply these capabilities. See the Service Parameter and Enterprise Parameter Changes for more information.
G. Clear codec calls maintain consistency throughout the gateway by using the RTP dynamic payload type 125. The dynamic payload type gets statically allocated by using Cisco Unified Communications Manager.
SIP trunk support for the G. Clear codec provides intercluster operability. The codec, which is negotiated as a supported media type in SIP Session Description Protocol (SDP) messaging, gets statically encoded to RTP payload type 125.
Note
Support exists for ISDN bearer capability for incoming ISDN data calls (restricted and unrestricted digital) that exit the VoIP network on another T1 PRI trunk.
Figure 2 shows a typical SIP trunk deployment that has the G.Clear codec enabled.
Figure 2 SIP Trunk Deployment with G. Clear Codec
The following SIP service parameters enable the G. Clear codec over SIP trunks: SIP Route Class Naming Authority and SIP Clear Channel Data Route Class Label. The SIP Route Class Naming Authority parameter represents the naming authority and context for the labels that are used in SIP signaling that represent the route class. The value specifies a domain name that is owned by the naming authority. The default specifies cisco.com.
To signal a particular route class value, Cisco Unified Communications Manager incorporates the domain name and the appropriate route class label, as defined in the SIP Clear Channel Data Route Class Label service parameter, into the SIP signaling.
The SIP Clear Channel Data Route Class Label represents the clear channel data route class in SIP signaling. This parameter and the SIP Route Class Naming Authority parameter create the complete signaling syntax for the SIP clear channel data route class value. The default specifies ccdata.
Route class signaling proves useful when you are interworking with TDM networks that make routing decisions based on route class and clear-channel data route classes. The default domain name that is specified in the parameter applies to interaction between Cisco switches. You can change the parameter to any vendor- or deployment-specific requirements. The far-end switch should receive the same value that is configured in the parameter.
For specific configuration information, see Service Parameter and Enterprise Parameter Changes.
The following entities do not get supported or are disabled:
•
•
•
•
•
•
•
•
Cisco Unified Communications Manager Administration Configuration Tips
No Cisco Unified Communications Manager Administration configuration tips exist for this feature.
GUI Changes
A check box in the Gateway Configuration window of Cisco Unified Communications Manager Administration enables or disables G. Clear codec functionality. The default sets the check box to disable (no check mark in the box). In Cisco Unified Communications Manager Administration, choose Device > Gateway.
Note
Service Parameter and Enterprise Parameter Changes
The following service parameters exist for Differentiated Services Code Point (DSCP) values for Quality of Service (QoS) and for overriding bandwidth for G. Clear calls.
Tip
•
•
•
•
•
•
Note
Many DSCP options display for the service parameters; for example, AF11 DSCP (001010), AF12 DSCP (001100), and AF13 DSCP (001110).
Tip
To configure the service parameters for SIP Route Class Naming Authority and SIP Clear Channel Data Route Class Label, choose System > Service Parameter. From the drop-down list, choose your server. From the service list, choose Cisco CallManager. To display all service parameters, click Advanced. Scroll down to the Clusterwide Parameters (Route Class Signaling). Change the SIP Route Class Naming Authority to the local naming authority and leave the SIP Clear Channel Data Route Class Label parameters set to the default. The following rules apply to both the SIP Route Class Naming Authority and SIP Clear Channel Data Route Class Label parameters:
•
•
•
These rules apply to the SIP Route Class Naming Authority parameter only:
•
•
Installation/Upgrade (Migration) Considerations
No additional network installation or upgrade considerations exist. Ensure G. Clear codec is enabled on the T1 PRI trunks that require the codec and that the bandwidth override service parameter is enabled for the regions that provide less than 64 kb/s of bandwidth per call.
No new port requirement exists.
Serviceability Considerations
No Cisco Unified Serviceability considerations exist for this feature. This feature requires no new alarms or counts to be added.
AXL and CTI Considerations
AXL supports an optional tag called GClearEnable in the add/update/get MGCP and SIP API; this tag applies to T1 PRI trunks. The user can use the AXL MGCP and SIP API to enable or disable the G. Clear support for T1 PRI trunks.
No CTI considerations exist for this feature.
User Tips
A negligible amount of delay occurs to MGCP processing.
No software, hardware, or firmware restrictions exist.
No accessibility restrictions or special configuration considerations exist.
For More Information
Refer to the following documents for additional configuration details for this feature:
•
•
•
G.729a and G.729b Codecs Over SIP Trunks
You can use G.729a and G.729b, which are low-bandwidth codecs, for calls that are initiated over SIP trunks. Consider this feature as required for endpoints that do not support delayed media calls and do not want to use a higher-bandwidth codec, such as G.711.
Because an MTP needs to be preallocated for early-offer calls, you must configure an external MTP or transcoder device to use this feature. The software MTP does not support G.729 over SIP trunks.
Although this feature supports all four G.729 codecs (G.729, G.729a, G.729b, and G.729ab), the system cannot distinguish between G.729 and G.729a or between G.729b and G.729ab. Therefore, Cisco Unified Communications Manager Administration provides only two options for configuring these codecs on SIP trunks: G729/G729a and G729b/G729ab.
The G.729 codec over SIP trunks applies only to outgoing calls, and incoming calls do not get affected. Be aware that the system does not support mid-call codec switching from G.729 to any other codec.
Cisco Unified Communications Manager Administration Configuration Tips
In Cisco Unified Communications Manager Administration, you can enable G.728a and G.729b codecs for the MTP Preferred Originating Codec.
Note
This field gets used only when the MTP Termination Point Required check box is checked.
GUI Changes
To access the MTP Preferred Originating Codec parameter, choose Device > Trunk.
For More Information
•
•
•
Enhanced IP Phone Services
The end user can, at the discretion of the Cisco Unified Communications Manager administrator, subscribe to IP Phone Services that are accessible under the Directories and Messages buttons, including the ability to control the presence of standard phone applications such as Call History logs Personal and Corporate Directory.
•
•
•
•
•
Cisco Unified Communications Manager Administration Configuration Tips
To minimize the impact to Cisco Unified Communications Manager performance and call processing, do not put IP phone services on any Cisco Unified Communications Manager server at your site or any server that is associated with Cisco Unified Communications Manager, such as the TFTP server or directory database publisher server. To ensure that variable length calls occur correctly, make sure that you configure the translation patterns as non-urgent.
If you change the service URL, remove an IP phone service parameter, or change the name of a phone service parameter for a phone service to which users are subscribed, be sure to click Update Subscriptions to update all currently subscribed users with the changes. If you do not do so, users must resubscribe to the service to rebuild the URL correctly.
GUI Changes
The following new fields display in the IP Phone Services Configuration window in Cisco Unified Communications Manager Administration:
•
•
•
•
•
•
The following field displays in the Phone Configuration window:
•
The following field displays in the Common Phone Profile Configuration window:
•
For More Information
•
•
•
•
•
Intelligent Bridge Selection
Cisco Unified Communications Manager 7.0 can intelligently select a video conference bridge from the configured Media Resource Group List (MRGL) if two or more of the original conference participants are video enabled. If one or no video participants exists, Cisco Unified Communications Manager selects an audio conference bridge from the configured MRGL.
Cisco Unified Communications Manager selects an audio or a video conference bridge from the configured MRGL of the conference initiator. However, if no MRGL is configured for the conference initiator, Cisco Unified Communications Manager allocates the video or audio conference bridge from the default MRGL.
If a video conference bridge needs to be allocated but none is available, Cisco Unified Communications Manager allocates an audio conference bridge for the conference. Similarly, if an audio conference bridge is needed but is unavailable, Cisco Unified Communications Manager allocates a video conference bridge.
The conference bridge that is allocated depends upon the video capability of the endpoints that are joining the conference.
Note
Cisco Unified Communications Manager Administration Configuration Tips
You need to configure the following service parameters to enable intelligent bridge selection:
•
•
•
If an audio conference bridge has higher priority than any video conference bridge in the MRGL, Cisco Unified Communications Manager ignores this parameter.
This parameter proves useful in situations where the local conference bridge is a video bridge (and configured in the MRGL with the highest priority) and audio conference bridges are only available in remote locations. In such a situation, enabling this parameter enables Cisco Unified Communications Manager to attempt to use the local video conference bridge first, even for audio-only conference calls.
For More Information
For information on Intelligent Bridge Selection features in Cisco Unified Communications Manager, refer to the Cisco Unified Communications Manager System Guide, Release 7.0(1).
International Escape Character + Support
Configuring the international escape character, +, in Cisco Unified Communications Manager Administration allows your phone users to place calls without having to remember and enter the international direct dialing prefix/international escape code that is associated with the called party. Depending on the phone model, for example, dual-mode phones, your phone users can dial + on the keypad of the phone. In other cases, the phone user can return calls by accessing the call log directory entries that contain +. In addition, using the international escape character allows you to support globalization of calling party numbers, which is part of the calling party normalization feature. For information on the calling party normalization feature, see the "Calling Party Normalization" section.
The international escape character, +, signifies the international access code in a complete E.164 number format. For example, NANP numbers have an E.164 global format in the format +1 214 555 1234. The + acts as a leading character that service providers replace in different countries with the international access code to achieve global dial plans.
Cisco Unified Communications Manager Administration Configuration Tips and GUI Changes
To configure the international escape character, +, for patterns and directory numbers, you configure \+ in the windows in Table 5:
Entering + in the windows in Table 5 does not configure the international escape character; instead, entering the + in the pattern fields means that the system should match one or more of the earlier characters during digit analysis, as described in the "Wildcards and Special Characters in Route Patterns and Hunt Pilots" section in the Cisco Unified Communications Manager System Guide. Consider the following information for configuring the international escape character in the windows in Table 5:
•
•
For directory numbers, you can configure the international escape character, \+, at the beginning of the number only.
•
•
Tip
Table 6 provides the configuration windows and fields where you can enter + to indicate the international escape character +.
SIP and MGCP gateways can support sending the international escape character, +, for calls. H.323 gateways do not support the +. QSIG trunks do not attempt to send the +, but SIP trunks can support sending the +.
For outgoing calls through a gateway that supports +, Cisco Unified Communications Manager can send the + with the dialed digits to the gateway. For outgoing calls through a gateway that does not support +, the gateway strips the + when Cisco Unified Communications Manager sends the call information to the gateway.
When + is not supported but the global calling party number includes +, configure the called party transformations and route patterns to send the outdial digits in a format that the device supports.
Service Parameter and Enterprise Parameter Changes
If you want to do so, you can configure the Strip + on Outbound Calls service parameter, which supports the Cisco CallManager service. This parameter determines whether Cisco Unified Communications Manager strips the international escape character, +, from the calling and called parties for outgoing calls through MGCP gateways and SIP trunks. If your network or far-end gateway does not recognize the + as a digit, set this parameter to False; if you set this parameter to True and the + is not supported in network or by the receiving gateway, calls that use + may drop. Ensure that calls over QSIG trunks do not utilize + because QSIG does not send the +. This parameter does not impact H.323 outbound calls because H.323 gateways unconditionally strip the + when they route outbound calls.
If you set the Strip + on Outbound Calls service parameter to True, Cisco Unified Communications Manager strips the + for the calling and called parties for all outgoing calls through all MGCP gateways and SIP trunks. To ensure that Cisco Unified Communications Manager does not strip the + for outgoing calls through particular MGCP gateways and SIP trunks, configure the calling party and called party transformation patterns for outgoing gateways to include the + prefix for international calls.
Installation/Upgrade (Migration) Considerations
After you upgrade to Cisco Unified Communications Manager 7.0, you may need to update your dial plans, speed dials, and so on, in Cisco Unified Communications Manager Administration to support the international escape character +.
Serviceability Considerations
Make sure that the Cisco CallManager service is activated in Cisco Unified Serviceability.
BAT Considerations
You can configure the incoming prefix fields for phones in the Bulk Administration Tool.
CAR/CDR Considerations
For information on how the international escape character + works with CDRs and Cisco Unified Communications Manager CDR Analysis and Reporting, see the "Cisco Unified Communications Manager CDR Analysis and Reporting" section and the "Cisco Unified Communications Manager Call Detail Records" section.
User Tips
The following Cisco Unified IP Phones, which run SIP or SCCP unless noted otherwise, can display + on the phone screen, speed dials, directory numbers, and in call log (Redial, Missed Calls, and so on) directories on the phone.
•
•
•
•
•
•
The Nokia S60, a dual-mode phone, also supports + dialing from the keypad on the phone. For example, a caller in the United States calls an international number in India. If the caller uses a dual-mode phone, the caller can directly dial + to represent the international number. The caller may call 0+91802501523 or +91802501523, depending on the outgoing route pattern settings. Dialing the + on the keypad assumes that the outgoing gateway can support the +; if the outgoing gateway does not support +, you must configure the route pattern like \+!, where Cisco Unified Communications Manager strips the \+ and prefixes 011 to transform the international number to 011 91 802501523.
Consider the following information about + and the phone:
•
•
•
•
•
•
For More Information
•
•
•
•
Local Route Groups
The Local Route Group feature helps reduce the complexity and maintenance efforts of provisioning in a centralized Cisco Unified Communications Manager deployment that uses a large number of locations. The fundamental breakthrough in the Local Route Group feature comprises decoupling the location of a PSTN gateway from the route patterns that are used to access the gateway.
Release 7.0(1) of Cisco Unified Communications Manager introduces a special Local Route Group that can be bound to a provisioned route group differently based on the Local Route Group device pool setting of the originating device. Devices, such as phones, from different locales can therefore use identical route lists and route patterns, but Cisco Unified Communications Manager selects the correct gateway(s) for their local end.
Note
The Local Route Group feature provides the ability to reduce the number of route lists and route patterns that need to be provisioned for implementations of Cisco Unified Communications Manager where each of N sites needs to have access to the local gateways of the other N-1 remote sites. One such scenario occurs with Tail End Hop Off (TEHO).
In simple local routing cases, the provisioning gets reduced from N route patterns and N route lists to one route pattern and one route list. In cases with Tail End Hop Off (TEHO), local route groups allow configuration of N route patterns and N route lists instead of N2 route patterns and N2 route lists. Because values for N can reach much more than 1000 for larger implementations, enormous scalability savings result.
In earlier releases, Cisco Unified Communications Manager treated gateways as devices to which multiple patterns are assigned. A tight, somewhat inflexible, binding existed between a gateway and the patterns that Cisco Unified Communications Manager associated with the gateway. When a call was placed, Cisco Unified Communications Manager viewed the situation as "Caller X has dialed some digits. These digits match pattern Y. Pattern Y directly associates with route lists, route groups, and gateways A, B, and C."
When the administrator adds a new route group to a route list, the Route List Configuration window presents the administrator with all available route groups from which to select. This list includes as its first member the special route group that is named Standard Local Route Group. This local route group specifies a virtual local route group.
The local route group does not statically get bound to any provisioned route group. The local route group does not display in the Find and List Route Groups configuration window, and, therefore, cannot be deleted or modified. You can, however, add the local route group to any route list; when so added, the local route group serves as a placeholder for a provisioned route group that will later get bound to the local route group dynamically during call setup.
Binding Provisioned Route Group to a Local Route Group During a Call
Deferring the binding of a provisioned route group to the local route group until call setup ensures that the desired provisioned route group can be the one that is local to the device that is placing the call. Thus, a device in location X would use a provisioned route group that contains gateways for the location X PSTN while a device in location Y would use a different provisioned group of gateways for the location Y PSTN.
You need to ensure that each device in the system is provisioned to know its local route group. To avoid specifying this information in the configuration window for each device, because the number of devices can be many thousands, Cisco Unified Communications Manager Administration locates the information in the device pool for the device, because device pools specify common site-specific information.
The Local Route Group field in the Device Pool Configuration window includes a drop-down list box that lists all available (provisioned) route groups. This list excludes the special Standard Local Route Group name (because only provisioned route groups should be configured for a device pool) but presents the special name, <NONE>, which specifies the first (default) choice. Choose <NONE> if no binding is desired.
Whenever the default value <NONE> is selected for a device pool, any call that uses a route list that includes the local route group, Standard Local Route Group, gets routed as if the Standard Local Route Group is absent from the list.
With this mechanism, a call that is placed from any device over a route list that contains the special Standard Local Route Group behaves as follows:
1.
2.
•
•
Routing With Local Route Groups
With local route group mapping, Cisco Unified Communications Manager can treat gateways more like a service.
Simple Local Routing
Simple local routing comprises cases in which each site needs to route offnet calls to its local gateways. Provisioning of route patterns and route lists can get reduced from the need to configure N route patterns and N route lists to a configuration in which only one route pattern and one route list are needed.
For this case, assume that all phones that home to a particular site belong to a single calling search space (CSS) that is unique to that site. For example, phones at the Boulder site belong to the CSS-Bldr calling search space and so forth. Without using the Local Route Group feature, regardless of site, a phone always prefers its local gateway when making an offnet call by dialing 9 followed by a 7-, 10-, or 11-digit pattern. As more sites get added, each column must include new entries (rows). If N sites exist, you need N different route lists, route patterns, partitions, and calling search spaces.
In the same implementation, use of the Local Route Group feature allows configuration of a single route list, partition, route pattern, and CSS, regardless of the number of sites. In this case, the following configuration applies:
•
•
•
Thus, the route lists, route patterns, partitions and calling search spaces for this case each get reduced from N to 1. The number of gateways, route groups, and device pools remain N for N sites.
A new partition, P_System, and a new calling search space, CSS_System, get added for accessing the 9.@ pattern from all sites. The calling search space, CSS_Boulder, can contain both P_Boulder and P_System as well, as can the CSS of the other sites.
Tail End Hop Off
Tail End Hop Off (TEHO) refers to routing long-distance calls across the VoIP network and dropping them off to the Public Switched Telephone Network (PSTN), as a local call, at a remote gateway. In TEHO situations, the configuration complexity can get reduced from the need to configure N2 entities to needing only N entities. The following assumptions for TEHO apply:
•
•
Again, Cisco Unified Communications Manager uses an identical routing policy for all sites. The second preference of routing a call through the local PSTN of a site (if the system fails to drop off the call as a local call at the remote PSTN) forces the customer to provision separate instances of all routing information for each site. Each site includes a unique set of route patterns and route lists to each of the other N-1 sites, as well as a generic local route list for all other calls that the remote access codes do not cover. This requirement entails a total of N×(N-1)+N, or N2, route lists and route patterns for the general case.
Using the Local Route Group feature, the N×(N-1) route patterns and route lists that are needed for remote sites reduce to N, and the N local route patterns and local route lists reduce to 1. Overall, the total number of route lists and route patterns decreases from N2 to N+1, and calling search spaces and partitions decrease from N to 1.
The crucial mechanism specifies the use of the Standard Local Route Group as the second choice in each route list. The setting in the device pool of the originating device dynamically determines the actual provisioned route group that gets used during a specific call.
Called Party Transformations
While loose coupling occurs between the enterprise number and the route group/gateway, very tight coupling occurs between the route group/gateway and the patterns that the PSTN expects. If the gateway chosen is in a 7-digit dialing location, the PSTN expects 7 digits; if the chosen gateway is in a 10-digit location, the PSTN expects 10 digits to access local numbers.
Called Party Transformation Example 1
A call gets placed from Dallas; the called number specifies 9.5551212. If the Dallas local gateway is busy or not accessible, assuming that the San Jose gateway is selected, 9.5551212 must be converted to 1 214 555 1212 for the San Jose gateway to dial out.
In the same example for a Local Route Group case, a call is placed from Dallas. The called number is 9.5551212, so the system must perform the following actions:
1.
2.
If a San Jose gateway gets selected, the system converts the global string +1 214 555 1212 to 1 214 555 1212; if a Dallas gateway gets selected, the system converts the global string to 214 555 1212.
Called Party Transformation Example 2
A call gets placed from RTP; the called number specifies 5551212. If the RTP local gateway is busy or not accessible, and if it is assumed that the San Jose gateway is selected, 5551212 must get converted to 1 919 555 1212 for the San Jose gateway to dial out.
In the same example for a Local Route Group case, a call gets placed from RTP. The called number specifies 9.5551212, so the system must perform the following actions:
1.
2.
If a San Jose gateway gets selected, the system converts the global string 91 919 555 1212 to 1 919 555 1212; if the RTP gateway gets selected, the system converts the global string to 555 1212.
Cisco Unified Communications Manager Administration Configuration Tips
When the administrator adds a new route group to a route list, the Route List Configuration window presents the administrator all available route groups from which to select. This list includes as its first member the special route group that is named Standard Local Route Group. This local route group specifies a virtual local route group.
Be aware that the local route group is not statically bound to any provisioned route group. The local route group does not display in the Find and List Route Groups configuration window and therefore cannot be deleted or modified. The local route group can, however, get added to any route list; when so added, the local route group serves as a placeholder for a provisioned route group that will later be bound to the local route group dynamically during call setup.
After it is added to a route list, the local route group can get removed later from that list, or its search-order place in the list can get modified as with any provisioned route group.
GUI Changes
The local route groups feature involves the following new and changed settings in the Cisco Unified Communications Manager Administration GUI:
•
•
•
•
•
•
Service Parameter and Enterprise Parameter Changes
No service parameter changes nor enterprise parameter changes exist for this feature.
Installation/Upgrade (Migration) Considerations
No installation considerations exist for this feature.
When you upgrade from an earlier release of Cisco Unified Communications Manager, the new Standard Local Route Group field gets initialized to the default setting, NULL, for <NONE>.
Serviceability Considerations
This feature affects the Cisco Dialed Number Analyzer service within Cisco Unified Serviceability.
CAR/CDR Considerations
This feature causes the final transformed called party number to be reported in the CDR records.
AXL and CTI Considerations
This feature entails the following AXL requirements:
•
•
•
•
•
No CTI considerations exist for this feature.
User Tips
No user tips exist for this feature.
For More Information
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Microsoft Windows Server 2008 Active Directory (AD) Support for LDAP Synchronization
The DirSync component in Cisco Unified Communications Manager allows Cisco Unified Communications Manager to synchronize the data from LDAP corporate directories to the Cisco Unified Communications Manager database. Cisco Unified Communications Manager allows synchronization from Microsoft Active Directory 2000 and Microsoft Active Directory 2003, Microsoft Active Directory 2008, iPlanet Directory Server 5.1, Sun ONE Directory Server 5.2, and Sun Java System Directory Server 6.0, 6.1, and 6.2 to the Cisco Unified Communications Manager database.
For More Information
•
•
•
•
Non-Urgent Translation Patterns
In earlier releases of Cisco Unified Communications Manager (and Cisco Unified CallManager), Cisco Unified Communications Manager prioritized translation patterns as urgent; that is, Cisco Unified Communications Manager routed the call as soon as digit analysis identified a match with the translation pattern. Because Cisco Unified Communications Manager 7.0 supports local route groups, calling party normalization, and the international escape character +, which allow you to globalize, route, and localize calling party numbers, you can configure translation patterns as urgent or non-urgent to ensure that Cisco Unified Communications Manager does not route the call before it should be routed.
For example, if a caller in the 408 area code dials 95551212, this number gets globalized to +14085551212 through the use of translation patterns; that is, digit analysis does a pattern match for that string to determine where to route the call. In this example, a translation pattern takes 9.[2-9]XXXXXX, translates that string to +1408XXXXXXX, and then maps that value to a calling search space that contains the globalized patterns. This example works as long as you do not use variable-length dialing, as is the case with international calls. If you want to route an international call, you need a translation pattern for 9011.! that disregards the predot and adds the prefix +. If you configure the translation pattern as urgent priority, 9011! matches with the first digit after the 9011, and Cisco Unified Communications Manager attempts to route the call without waiting to match more digits. As a result, international and any other variable length calls do not route correctly.
Cisco Unified Communications Manager Administration Configuration Tips
In earlier releases of Cisco Unified Communications Manager, Cisco Unified Communications Manager did not allow you to configure similar translation patterns, for example, 9.XXXX and 9.XXXXX, in the same partition because the urgent priority configuration for the translation pattern ensured that digit analysis never matched the second pattern, in this case, 9.XXXXX. Because you can configure translation patterns as non-urgent in Cisco Unified Communications Manager 7.0, you can configure similar translation patterns in the same partition and ensure that digit analysis can accurately match the patterns. Even if digit analysis identifies a match with a translation pattern, Cisco Unified Communications Manager attempts to match more digits in other translation patterns if you configure the translation pattern as non-urgent.
To route international and variable-length calls correctly, make sure that you configure the translation patterns as non-urgent.
GUI Changes
In Cisco Unified Communications Manager Administration, you can configure any translation pattern as urgent priority or non-urgent priority. The Urgent Priority check box displays in the Translation Pattern Configuration (Call Routing > Translation Pattern) and Intercom Translation Pattern Configuration windows (Call Routing > Intercom > Intercom Translation Pattern). If you do not check this check box and if the dial plan contains overlapping translation patterns, Cisco Unified Communications Manager does not route the call until the interdigit timer expires (even if it is possible to dial a sequence of digits to choose a current match). To interrupt interdigit timing when Cisco Unified Communications Manager must route a call immediately, check this check box.
Installation/Upgrade (Migration) Considerations
After you install or upgrade Cisco Unified Communications Manager, the Urgent Priority check box in translation patterns displays as checked and enabled. Update your translation patterns, if necessary, to accommodate your dial plan.
Serviceability Considerations
For call routing to work, you must activate the Cisco CallManager service in Cisco Unified Serviceability.
For More Information
•
•
•
Privacy Headers for SIP Trunks
You can configure four new SIP trunk options to determine what type of privacy information will get included in SIP messages.
GUI Changes
To configure the four options in Cisco Unified Communications Manager Administration, choose Device > Trunk > SIP Trunk configuration. Find the four options in the Call Routing pane of the SIP Trunk configuration window:
•
•
•
–
–
–
•
–
–
–
–
For More Information
Refer to the Cisco Unified Communications Manager Administration Guide, "Trunk Configuration chapter, "Trunk Configuration Settings for SIP Trunks" table.
SIP Support for Cisco Unified Communications Manager Features
Cisco Unified Communications Manager 7.0 adds SIP support for features that were previously only available on phones that were running SCCP.
The following features now get supported on phones that are running SIP:
•
•
•
•
•
•
•
•
•
•
•
Cisco Unified Communications Manager Administration Configuration Tips
Configuration of the SIP features match the configuration for the equivalent SCCP features.
User Tips
Notify your end users that they can use these features.
For More Information
•
•
SIP T.38 Interoperability with Microsoft Exchange
The T.38 standard comes from the ITU-T Recommendation for real-time transfer of Group 3 facsimile (fax) communication over IP networks. In Cisco Unified Communications Manager, the implementation of T.38 interoperability with Microsoft Exchange enables the system to switch a call from audio to T.38 fax.
The following steps show how the Microsoft Exchange Server establishes a call to a fax machine:
a.
b.
c.
Cisco Unified Communications Manager Administration allows you to configure a SIP Profile that supports T.38 fax communication. This profile applies to SIP trunks only, not phones that are running SIP or endpoints.
Cisco Unified Communications Manager Administration Configuration Tips
The Outgoing T.38 INVITE Include Audio mline parameter allows the system to accept a signal from Microsoft Exchange that causes it to switch the call from audio to T.38 fax. To use this feature, you must also configure a SIP trunk with this SIP profile.
GUI Changes
To access the Outgoing T.38 INVITE Include Audio mline parameter, choose Device > Device Settings > SIP Profile.
For More Information
•
•
Trusted Relay Points
You can deploy the Cisco Unified Communications system in a network virtualization environment. Cisco Unified Communications Manager enables the insertion of trusted relay points (TRPs). The insertion of TRPs into the media path constitutes a first step toward VoIP deployment within a virtual network.
The underlying network infrastructure comprises one of the key shared assets in an overall network design. A number of customer use cases require support for network infrastructure virtualization, such as the following examples:
•
•
•
•
•
All these applications include a requirement to maintain traffic separation on the network device as well as between network devices.
Traffic separation translates into concepts such as Virtual Routing and Forwarding (VRF). VRF allows multiple instances of a routing table to co-exist within the same router at the same time. In a virtualized network, these different routing domains, or VRFs, typically cannot communicate directly without going through the data center. This situation challenges applications such as Cisco Unified Communications, where devices in the data VRF domain, such as software endpoints that are running on PCs, need to communicate directly with hard phones in the voice VRF domain without hairpinning media in the data center and without directly exposing the voice and data VRFs to each other.
Quality-of-Service Enforcement
In a Cisco voice network, the switch detects Cisco Unified IP Phones that use Cisco Discovery Protocol (CDP), and the switch trusts the Differentiated Services Code Point (DSCP) marking of packets that the Cisco Unified IP Phones send. Because CDP is not secure and can easily be replicated from a PC, the switch generally does not trust the traffic that is coming from a PC. Because it is almost impossible to ensure that only Cisco Unified Communications Manager-authorized traffic will get marked with DSCP, the packets that come from a PC get re-marked to best effort.
To resolve this problem, Cisco Unified Communications Manager inserts a trusted relay point (TRP) in front of the softphone that runs on the PC, and the media stream from the endpoint can be forced to flow through the TRP. The TRP re-marks the DSCP according to instructions from Cisco Unified Communications Manager. The switch honors and trusts media packets that are sent from the TRP.
Cisco Unified Communications Manager Administration Configuration Tips
From the Cisco Unified Communications Manager point of view, the trusted relay point (TRP) always gets placed closest to the endpoint device that requires it. The high-level requirements for TRP insertion follow:
•
•
•
•
•
•
•
•
GUI Changes
Trusted relay points involve the following new settings in the Cisco Unified Communications Manager Administration GUI:
•
•
•
•
•
•
•
•
•
•
•
Service Parameter and Enterprise Parameter Changes
You can configure the Fail Call If Trusted Relay Point Allocation Fails service parameter, which supports the Cisco CallManager service. This service parameter, which is found in the Clusterwide Parameters (System - General) section, determines whether a call that requires a Trusted Relay Point (TRP) is allowed to proceed if no TRP resource is available. Valid values specify True (the call fails if no TRP resource is available) or False (the call proceeds even if a TRP resource is not available).
Choose the best value for a system based on how the system uses TRPs. For example, if the system uses TRP for Virtual Routing and Forwarding (VRF) or for firewall traversal, Cisco Unified Communications Manager cannot connect audio or video without a TRP resource, so the service parameter value should be set to True. If a TRP is used for Quality of Service (QoS) enforcement, Cisco Unified Communications Manager can complete the call if a TRP resource is unavailable, but the call will not have the correct Differentiated Services Code Point (DSCP) marking.
Trusted relay points do not entail any changes to enterprise parameters.
AXL and CTI Considerations
No AXL considerations exist for this feature.
CTI devices, such as CTI route points and CTI ports, can get designated to use a trusted relay point (TRP). These devices can get assigned their own Use Trusted Relay Point setting, or they can inherit their Use Trusted Relay Point setting from their Common Device Configuration setting. The Use Trusted Relay Point setting for an individual device overrides the setting from the associated Common Device Configuration setting.
User Tips
No user tips exist for this feature.
For More Information
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Cisco VG202 and VG204 Gateway Support in Cisco Unified Communications Manager Administration
The Cisco VG202 and VG204 Analog Voice Gateways augment the Cisco Voice Gateway portfolio along with the Cisco Integrated Series Routers (Cisco 3800,2800,1861 and VG224s). These gateways enable an IP telephony solution to continue using traditional analog devices while taking advantage of the productivity that an IP infrastructure affords.
The Cisco VG202 and VG204 comprise Cisco IOS Software-based 2-port and 4-port gateways for analog phones, fax machines, modems, and speakerphones within an enterprise voice system that is based on Cisco Unified Communications Manager and Cisco Unified Communications Manager Express.
After the Cisco VG202 and VG204 release, you can configure the gateways in Cisco Unified Communications Manager Administration.
Cisco Unified Communications Manager Administration Configuration Tips
No new configuration settings exist in Cisco Unified Communications Manager Administration to support these gateways.
GUI Changes
To configure these gateways in Cisco Unified Communications Manager Administration, choose Device > Gateway. Click Add New and choose either VG 202 or VG 204 from the Gateway Type drop-down list box. After you click Next, the Gateway Configuration window displays.
User Tips
These gateways do not impact the end user.
For More Information
For additional information on how to configure gateways in Cisco Unified Communications Manager Administration, refer to the "Gateway Configuration" chapter in the Cisco Unified Communications Manager Administration Guide, Release 7.0(1).
Voice over Secure IP for SIP Trunks
Voice over Secure IP (VoSIP) for SIP trunks includes the following features:
•
•
Note
Multilevel Precedence and Preemption Enhancements
This feature adds the following configuration options to Cisco Communications Manager Administration for MLPP: Resource Priority Namespace Network Domain and Resource Priority Namespace Network Domain List. The following sections describe the options.
Resource Priority Namespace Network Domain
The Resource Priority Namespace Network Domain enables the configuration of namespace domains for a Voice over Secured IP (VoSIP) network that uses SIP trunks. Cisco Unified Communication Manager prioritizes the SIP-signaled resources, so those resources can get used most effectively during emergencies and congestion of telephone circuits, IP bandwidth, and gateways. Endpoints receive the precedence and preemption information, which is based on RFC 4411 and RFC 4412.
The SIP signaling contains a resource-priority header. Consider the resource-priority header as similar to the ISDN precedence Information Element (IE) and ISDN User Part (ISUP) precedence parameters that are used in legacy TDM MLPP networks. The resource-priority header relates to, but differs from the priority header in RFC 3261, Section 20.26.
The RFC 3261 priority header indicates the importance of SIP requests for the endpoint. For example, the header could indicate decisions about call routing to mobile devices and assistants and about call acceptance when the call destination is busy. The RFC 3261 priority header does not affect the usage of PSTN gateway or proxy resources.
In the RFC 3261 priority header, any value could get asserted, but the Resource Priority header field in the namespace network domain is subject to authorization. The Resource Priority header field does not directly influence the forwarding behavior of IP routers or the use of communications resources such as packet forwarding priority.
The RFC 4411 and RFC 4412 resource-priority header in the outbound message provides the basis for the translation or route patterns that direct a call to the SIP trunk. Incoming calls get validated against a list of Resource Priority Namespace Network Domains if the calls are terminating that is to an endpoint configured in Cisco Unified Communications Manager Administration.
The following messages include the Resource Priority header:
•
•
•
The following i example shows an INVITE message that has a resource priority header that specifies immediate priority (value of 4).
INVITE sip:6000@10.18.154.36:5060 SIP/2.0Via: SIP/2.0/TCP 10.18.154.44;branch=z9hG4bK1636ee4aRemote-Party-ID: "Raleigh - 5001" <sip:5001@10.18.154.44>;party=calling;screen=yes;privacy=offFrom: "Raleigh - 5001" <sip:5001@10.18.154.44>;tag=936ad6ec-4d3c-4a42-a812-99ac56d972e1-14875646To: <sip:6000@10.18.154.36>Date: Mon, 21 Mar 2005 14:39:21 GMTCall-ID: 1d13800-23e1dc99-4c-2c9a12ac@172.18.154.44Supported: 100rel,timer,replacesRequire: resource-priorityMin-SE: 1800User-Agent: Cisco-CCM5.0Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFYCSeq: 101 INVITEContact: <sip:5001@10.18.154.44:5060;transport=tcp>Expires: 180Allow-Events: presence, dialog, kpmlCall-Info:<sip:10.18.154.44:5060>;method="NOTIFY;Event=telephone-event;Duration=500"Re source-Priority: namespace.4Max-Forwards: 70Content-Type: application/sdpContent-Length: 269v=0o=CiscoSystemsCCM-SIP 2000 1 IN IP4 10.18.154.44s=SIP Callc=IN IP4 10.18.154.45t=0 0m=audio 19580 RTP/AVP 0 101a=rtpmap:0 PCMU/8000a=ptime:20a=rtpmap:101 telephone-event/8000a=fmtp:101 0-15You can also add a default Resource Priority Namespace Network Domain to a SIP profile to use when misconfigured incoming namespace network domains get handled.
Note
The following supplementary services get supported:
•
•
•
•
The following headers, mapping, and queuing do not get supported:
•
•
•
•
Guest
