Table Of Contents
Release Notes for Cisco Unified Communications Manager Release 7.1(2a)
Introduction
System Requirements
Upgrading to Cisco Unified Communications Manager 7.1(2a)
Before You Begin
Special Upgrade Information
I/O Throttling
Device Name of Cisco Unified Mobile Communicator Must Not Exceed 15 Characters Before 7.1(2a) Upgrade
Making Configuration Changes After an Upgrade
Upgrade Paths to Cisco Unified Communications Manager 7.1(2a)
Ordering the Upgrade Media
Upgrading from Cisco Unified Communications Manager Release 5.1(3e) to 7.1(x) Releases
Upgrading to Unified CM 7.1(2a) by Using the UCSInstall File
Upgrading From an Engineering Special
The Latest Software Upgrades for Unified CM 7.1 on Cisco.com
Related Documentation
Limitations and Restrictions
Important Notes
Context-Sensitive Help Does Not Display for Some Windows
Deleting Unassigned Directory Numbers
CSCta09513 Switch Version Does Not Complete
CSCta12062 Null Value in NetworkLocale Caused Database Exception
CSCsz91530 Logical Partitioning Feature Does Not Work Correctly in Conference Scenario When Multiple H.323 Gateways Are Configured in a Route Group
CSCsy92863 Intercom Route Partition Online Help Is Incorrect
Admin Password Gets Corrupted If Correction is Made During Password Reset
Passwords Do Not Match
Password Too Short or Password in Dictionary
Removing Hard Drives
CSCsz33878 IPMA Wizard Constraint
CSCsz21235 Core Dump File Gets Generated During the Cisco Security Agent Shutdown Process
Creating a Custom Help Desk Role and Custom Help Desk User Group
Use Microsoft Outlook to Receive Cisco Unified Communications Manager Licenses
Multiple Tenant MWI Modes Service Parameter
Considerations for LDAP Port Configuration
New and Changed Information
Documentation Changes
Installation, Upgrade, and Migration
System History Log for Cisco Unified Communications Manager
Description
Data Migration Assistant (DMA)
Device Name of Cisco Unified Mobile Communicator Must Not Exceed 15 Characters Before 7.1(2) Upgrade
Cisco Unified Communications Operating System Administration
Customized Log-on Message
Ethernet IPv6 Configuration Settings
Command Line Interface
show memory
Spaces in File Names
Relative Paths
New Commands and Parameters
Cisco Unified Communications Manager Administration
New and Updated Enterprise and System Parameters
Menu Changes
Cisco Unified Communications Manager Features and Applications
Always Use Prime Line
Always Use Prime Line for Voice Message
Barge, cBarge, and Single Button Barge Support for PLAR
Calling Party Normalization Enhancements
Cisco Unified Communications Manager Assistant Enhancements for Numeric User ID Login
Cisco Unified Communications Manager Attendant Console Support in 7.1(2)
Cisco Web Dialer Configured in Application Server Window
G.Clear Codec Support on SIP Trunks
Geolocations, Geolocation Filters, and Location Conveyance
H.235—Pass-Through Support
H.329—Extended Video Channel Support
Internet Protocol Version 6 (IPv6)
Licensing Enhancements
Location-Based Call Admission Control Over Intercluster Trunk
Logging Missed Calls for Shared Lines
Logical Partitioning
Multicast Music On Hold Over H.323 Intercluster Trunks
Off-Hook Abbreviated Dial
OpenLDAP 2.3.41 Can Synchronize with Cisco Unified Communications Manager Database
Party Entrance Tone
Phone Migration in Cisco Unified Communications Manager Administration
QSIG Variant Configuration for a Gateway or Trunk
Standard Audit Log Administration Role
Standard Audit Users User Group
Synchronization of Configuration Settings
Table Out of Sync Detection
Unconfigured Device Registration Attempts Restricted
Viewing Held Calls on Shared Lines
Security
CAPF Interaction with IPv6 Addressing
SSH Credentials in the Common Device Profile window
H.235 Pass-Through Support
CTL File Size Limitation
Security Icons
Cisco Security Agent Version
Accessing Cisco Security Agent Logs
Bulk Administration Tool
Support for Party Entrance Tone
Support for Log Missed Calls
Support for Always Use Prime Line
Support for VG202 and VG204 Gateways
Phone Migration in BAT
Support for Geolocations and Logical Partitioning
New fields That Are Supported for Export by Import/Export
Support for Seamless Integration (Apply Config)
Cisco Unified Serviceability
IPv6 and Serviceability
Service Manager Enhancements
Audit Logging
Alarms
Cisco Unified Cisco Unified Real-Time Monitoring Tool
IPv6 and RTMT
Alerts
Performance Monitoring Counters
Trace and Log Central
Quality Report Tool Reports
Cisco Unified Communications Manager CDR Analysis and Reporting
Audit Events Get Logged for CAR
Customized Log-on Message
Upgrade of CAR Data
Backup of CAR Data
Ensure CAR Administrator Privileges Are Restored After Upgrade
Cisco Unified Communications Manager Call Detail Records
IPv6 and CDRs
H.239 and CDRs
Logical Partitioning
New Call Termination Cause Codes
SIP Calls with URL in callingPartyNumber Field
GlobalCallId Survives Over Cisco Unified Communications Manager Restarts
Cisco Unified Reporting
APIs
Cisco Unified TAPI Service Provider (TSP)
Cisco Unified JTAPI
Skinny Client Control Protocol (SCCP)
Administrative XML (AXL) Programming
Serviceability XML Programming
Cisco Unified IP Phones
Cisco Unified IP Phone 6900 Series
Enterprise Phone Configuration Window
Join and Direct Transfer Policy Configuration Parameter
Barge Tone Enhancements
Cisco Unified IP Phone Support HTTPS
Hold Status
Internet Protocol Version 6 on the Cisco Unified IP Phone
Line Select
Missed Calls
Off-Hook Abbreviated Dialing
Restrict Unconfigured Phone Registration
Secure Icon
Cisco Web Dialer Enhancements
Cisco Unified CM User Options
Caveats
Resolved Caveats
UsingBug Toolkit
Open Caveats
Open Caveats for Cisco Unified Communications Manager Release 7.1(2) As of May 27, 2009
Documentation Updates
Cisco Unified Communication Manager CDR Analysis and Reporting
Purpose of Cisco Unified Communications Manager CDR Analysis and Reporting
"Mailing a Report" Recipients
Cisco Unified Communications Manager Security
Definition of Locally Significant Certificate
Using Certificates Issued by a Third-Party Certificate Authority
Cisco Unified Communications Operating System
Guidelines for Installing COP Files
Disk Space Before Upgrading
Pre-Upgrade Task Is Omitted From Software Upgrades Chapter
Cisco Unified Communications Manager Administration
Number of Digits Field Description is Incorrect
Number of Locations and Regions That Cisco Unified Communications Manager Supports
Intercom Route Partition Configuration Settings Description Field Information Is Incorrect
Mobile Connect Support Restrictions
Configuring an H.323 Gateway for System Remote Access by Using Hairpinning
Enterprise Feature Access Two-Stage Dialing
Valid Characters in Name Field of Access List Configuration Window
Valid Characters in Name Field of Role Configuration Window
Valid Characters in Name and Description Fields of Remote Destination Profile Window
Valid Characters in Name Field of Geolocation Filter Configuration Window
Valid Characters in Name Field of Geolocation Configuration Window
IPv6 Chapter Incorrectly Describes How IPv6 Addresses Display in the Find and List Phones Window
Directory Number Chapter Includes Incorrect Information on Alerting Name and Display Name Fields
End User Chapter Includes Incorrect Information for Manager User ID Field
Intercom Calls Cannot Be Placed on Hold
Device Pool Configuration Chapter Does Not State That You Can Enter -1 in the Connection Monitor Duration Field
Trunk Configuration Chapter Does Not State That You Can Enter Hostname in Destination Address Field
IPv6 Chapter Does Not Contain Information on NTP Server
Cisco Unified Communications Manager Does Not Support Logical Partitioning for Cisco Unified MeetingPlace and Cisco Unified MeetingPlace Express Calls
Licensing Chapter Does Not State That You Should Use Microsoft Outlook to Receive Licenses
Voice Mail Chapters Do Not Describe MWI Service Parameter
Cisco Unified Communications Manager Does Not Support Logical Partitioning for Cisco Unified MeetingPlace and Cisco Unified MeetingPlace Express Calls
Device Name of Cisco Unified Mobile Communicator Must Not Exceed 15 Characters
Mobile Voice Access Directory Number Field Description
Recording Destination Address Field Description
OpenLDAP Version 2.3.41 Not Listed in LDAP Synchronization Documentation
Do Not Begin Starting and Ending Directory Numbers with a Zero (0)
Time-of-Day Routing Chapter Omits Information About Defined Time Periods
Changed Values of Mobility Cell Pick
Cisco Unified Serviceability
Password Description Omitted
Cluster Service Activation Node Recommendations
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Unified Communications Manager Release 7.1(2a)
Updated August 27, 2009
Note 
You can view release notes for Cisco Unified Communications Manager Business Edition at http://www.cisco.com/en/US/products/ps7273/prod_release_notes_list.html
This document contains information pertinent to Cisco Unified Communications Manager Release 7.1(2) (which got deferred) as well as information specific to Cisco Unified CM 7.1(2a).
Updates to Cisco Unified CM 7.1(2a):
•August 27, 2009—Added the note under the "Upgrading from Cisco Unified Communications Manager Release 5.1(3e) to 7.1(x) Releases" section
•August 22, 2009—Added the "Enterprise Phone Configuration Window" section, "Join and Direct Transfer Policy Configuration Parameter" section and "Cisco Unified IP Phone 6900 Series" section.
•August 24, 2009—Added the "Context-Sensitive Help Does Not Display for Some Windows" section and updated the "I/O Throttling Overview" section
•Introduction
•System Requirements
•Upgrading to Cisco Unified Communications Manager 7.1(2a)
•Related Documentation
•Important Notes
•New and Changed Information
•Caveats
•Documentation Updates
•Obtaining Documentation and Submitting a Service Request
To view the release notes for previous versions of Cisco Unified Communications Manager, choose the Cisco Unified Communications Manager version from the following URL: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_release_notes_list.html.
Before you install Cisco Unified Communications Manager, Cisco recommends that you review the "Important Notes" section for information about issues that may affect your system.
Note To ensure continuous operation and optimal performance of your Cisco Unified Communications Manager system, you should upgrade to Cisco Unified Communications Manager 7.1(2a).
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.1 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 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 this release of Cisco Unified CM, 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 Make sure that the matrix shows that your server model supports Cisco Unified CM Release 7.1(2a).
Note Be aware that some servers that are listed in the Cisco Unified Communications Manager Software Compatibility Matrix may require additional hardware support for Cisco Unified CM Release 7.1(2a). Make sure that your server meets the minimum hardware requirements, as indicated in the footnotes of the Cisco Unified Communications Manager Software Compatibility Matrix. Cisco Unified CM requires a minimum of 2 GB of memory, 72 GB disk drive, and 2 GHz processor.
Uninterruptible Power Supply
Cisco recommends that you connect each Cisco Unified Communications Manager server to an uninterruptible power supply (UPS) to provide backup power and protect your system against a power failure.
Note You must connect MCS-7816 and MCS-7825 servers to a UPS in order to prevent file system corruption during power outages.
When Cisco Unified Communications Manager runs on one of the servers listed in Table 1, basic integration to the UPS model APC SmartUPS 1500VA USB and APC 750VA XL USB gets supported.
Integration occurs via a single point-to-point Universal Serial Bus (USB) connection. Serial and SNMP connectivity to UPS does not get supported, and the USB connection must be point-to-point (in other words, no USB hubs). Single- and dual-USB UPS models get supported with the APC SmartUPS 1500VA USB and APC 750VA XL USB. The feature activates automatically during bootup if a connected UPS gets detected.
Alternatively, you can execute the show ups status CLI command which shows the current status of the USB-connected APC smart-UPS device and starts the monitoring service if it is not already started. The CLI command also displays detected hardware, detected versions, current power draw, remaining battery runtime, and other relevant status information.
When the feature is activated, graceful shutdown will commence as soon as the low battery threshold is reached. Resumption or fluctuation of power will not interrupt or abort the shutdown, and administrators cannot stop the shutdown once the feature is activated.
For unsupported Cisco Unified Communications Manager releases, MCS models and/or UPS vendor/make/models, you can cause an external script to monitor the UPS. When low battery gets detected, you can log on to Cisco Unified Communications Manager by using Secure Shell (SSH), access the CLI, and execute the utils system shutdown command.
Table 1 Supported Servers for Basic Integration
HP Servers
|
IBM Servers
|
MCS-7816-H3
|
MCS-7815-I1
|
MCS-7825-H1
|
MCS-7815-I2
|
MCS-7825-H2
|
MCS-7816-I3
|
MCS-7825-H3
|
MCS-7816-I3
|
MCS-7825-H4
|
MCS-7825-I1
|
MCS-7828-H3
|
MCS-7825-I2
|
MCS-7828-H4
|
MCS-7825-I3
|
MCS-7835-H2
|
MCS-7825I-30
|
MCS-7845-H2
|
MCS-7825-I4
|
| |
MCS-7828-I3
|
| |
MCS-7828-I4
|
| |
MCS-7828-I4
|
| |
MCS-7835-I1
|
| |
MCS-7835I-30
|
| |
MCS-7845-I2
|
Upgrading to Cisco Unified Communications Manager 7.1(2a)
The following sections contain information pertinent to upgrading to this release of Cisco Unified CM.
•Before You Begin
•Special Upgrade Information
•Upgrade Paths to Cisco Unified Communications Manager 7.1(2a)
•Ordering the Upgrade Media
•The Latest Software Upgrades for Unified CM 7.1 on Cisco.com
•Upgrading from Cisco Unified Communications Manager Release 5.1(3e) to 7.1(x) Releases
•Upgrading to Unified CM 7.1(2a) by Using the UCSInstall File
•Upgrading From an Engineering Special
Before You Begin
1. 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:
–Cisco Unified Communications Manager System version
–Cisco Unified Communications Manager Administration version
2. Read the "Special Upgrade Information" section.
Special Upgrade Information
The following sections include information that you must know before you begin the upgrade process.
•I/O Throttling
•Device Name of Cisco Unified Mobile Communicator Must Not Exceed 15 Characters Before 7.1(2a) Upgrade
•Making Configuration Changes After an Upgrade
I/O Throttling
This section describes how I/O throttling affects the upgrade process, identifies possible causes of slow or stalled upgrades, and provides actions you can take to speed up the upgrade.
I/O Throttling Overview
I/O throttling prevents call processing degradation during the upgrade but may cause the upgrade to take longer. I/O throttling, which is necessary if you perform the upgrade during normal business hours, gets enabled by default. If you disable throttling during normal business hours or other high-traffic hours, this may cause a core dump in Cisco Unified Communications Manager. Be aware that the higher the call processing load on the system during the upgrade, the longer the upgrade takes.
Disabling I/O throttling
If you can perform the upgrade during a maintenance window, you can disable I/O throttling to decrease the time that it takes for the upgrade to complete.
To disable I/O throttling, use one of the following methods before you start the upgrade:
•To disable I/O throttling in Cisco Unified Operating System Administration, choose Software Upgrades > Install/Upgrade, and check the Disable I/O throttling checkbox.
•To disable I/O throttling from the command line interface (CLI) use the utils iothrottle disable command.
Note If call traffic exists on the system with I/O throttling disabled, the system may become overloaded and deny new calls. In the worst case, the Cisco CallManager service might restart; however, existing calls get preserved if the Cisco CallManager service restarts.
Note If you want to reenable I/O throttling after you start the upgrade, you must cancel the upgrade, reenable I/O throttling, and then restart the upgrade.
Server Models
The server model that you have also impacts the upgrade speed. Upgrades on servers that have SATA hard drives, such as MCS-7816, MCS-7825, MCS-7828, take longer than servers with SAS/SCSI hard drives, such as MCS-7835 and MCS-7845.
Write-Cache
A disabled write-cache on the server also causes the upgrade process to run more slowly. Multiple factors can cause the write-cache to get disabled, including dead batteries on older servers.
Before starting an upgrade, verify the status of the write-cache on the MCS-7828-H4 and MCS-7835/45 disk controllers. You do not need to verify the write-cache status on the MCS-7816, MCS-7825, or other MCS-7828 servers. To verify write-cache status, access the Cisco Unified Operating System Administration, and choose Show > Hardware.
If you determine that your write-cache is disabled because of a dead battery, you need to replace the hard disk controller cache battery. Follow your local support procedures to get this battery replaced.
See the following examples of output from the Show > Hardware menu for details on determining the battery and write-back cache status.
The following example shows write-cache enabled. The example indicates that 50 percent of the cache is reserved for write and 50 percent of the cache is reserved for read. If the write-cache was disabled, 100 percent of the cache would be reserved for read or the Cache Status would not equal "OK". Also, the battery count equals "1". If the controller battery was dead or missing, it would indicate "0".
Example 1-1 7835/45-H1, 7835/45-H2, 7828-H4 Servers with Write-Cache Enabled
-------------------------------
Cache Serial Number: P75B20C9SR642P
RAID 6 (ADG) Status: Disabled
Surface Scan Delay: 15 sec
Cache Board Present: True
Accelerator Ratio: 50% Read / 50% Write
SATA NCQ Supported: False
The following example indicates that the battery status is enabled and that the the write-cache mode is enabled in (write-back) mode.
Example 1-2 7835/45-I2 Servers with Write-Cache Enabled
----------------------------------------------------------------------
----------------------------------------------------------------------
Channel description : SAS/SATA
Controller Model : IBM ServeRAID 8k
Controller Serial Number : 20ee0001
Defunct disk drive count : 0
Logical drives/Offline/Critical : 2/0/0
---------------------------------------------------
Controller Version Information
---------------------------------------------------
Boot Flash : 5.1-0 (15421)
---------------------------------------------------
Controller Battery Information
---------------------------------------------------
Capacity remaining : 100 percent
Time remaining (at current draw) : 4 days, 18 hours, 40 minutes
---------------------------------------------------
Controller Vital Product Data
---------------------------------------------------
Controller FRU# : 25R8076
----------------------------------------------------------------------
Logical drive information
----------------------------------------------------------------------
Logical drive name : Logical Drive 1
Status of logical drive : Okay
Read-cache mode : Enabled
Write-cache mode : Enabled (write-back)
Write-cache setting : Enabled (write-back) when protected by battery
Drive(s) (Channel,Device) : 0,0 0,1
Logical drive name : Logical Drive 2
Status of logical drive : Okay
Read-cache mode : Enabled
Write-cache mode : Enabled (write-back)
Write-cache setting : Enabled (write-back) when protected by battery
Drive(s) (Channel,Device) : 0,2 0,3
Device Name of Cisco Unified Mobile Communicator Must Not Exceed 15 Characters Before 7.1(2a) Upgrade
Before you upgrade to Cisco Unified Communications Manager 7.1(2a), ensure that the device name of a Cisco Unified Mobile Communicator does not exceed 15 characters in Cisco Unified Communications Manager Administration. If the device name of a Cisco Unified Mobile Communicator exceeds 15 characters, migration of this device will fail when you upgrade to Cisco Unified Communications Manager 7.1(2a) and the following error message gets written to the upgrade log:
InstallFull *ERROR* Name for Cisco Unified Mobile Communicator device(s) must be 15 or
less, please correct and rerun upgrade.
If an existing Cisco Unified Mobile Communicator device name specifies a longer name, shorten the device name to 15 or fewer characters before the upgrade.
Making Configuration Changes After an Upgrade
The administrator must not make any configuration changes to Cisco Unified Communications Manager during an upgrade. Configuration changes include any changes that you make in Cisco Unified Communications Manager Administration, Cisco Unified Serviceability, and the User Option windows.
If you are upgrading your system, you must complete the upgrade tasks in this section before you perform any configuration tasks.
Caution If you fail to follow these recommendations, unexpected behavior may occur; for example, ports may not initialize as expected.
Upgrade Tasks
To successfully complete the upgrade, perform the upgrade tasks in the following order before you begin making configuration changes.
Note Cisco strongly recommends that you do not perform configuration tasks until the upgrade completes on all servers in the cluster, until you have switched the servers over to the upgraded partition, and until you have verified that database replication is functioning.
Procedure
Step 1 Stop all configuration tasks; that is, do not perform configuration tasks in the various Cisco Unified Communications Manager-related GUIs or the CLI (with the exception of performing the upgrade in the Cisco Unified Communications Operating System GUI).
Tip For detailed information about the upgrade process, see Chapter 7, Software Upgrades, in the Cisco Unified Communications Operating System Administration Guide.
Step 2 Upgrade the first node in the cluster (the publisher node).
Step 3 Upgrade the subsequent nodes in the cluster (the subscriber nodes).
Step 4 Switch over the first node to the upgraded partition.
Step 5 Switch over subsequent nodes to the upgraded partition.
Note You can switch the subsequent nodes to the upgraded partition either all at once or one at a time, depending on your site requirements.
Step 6 Ensure that database replication is functioning between the first node and the subsequent nodes. You can check database replication status by using one of the following methods:
•In Cisco Unified Reporting, access the Unified CM Database Status report. Before you proceed, ensure the report indicates that you have a good database replication status with no errors. For more information about using Cisco Unified Reporting, see the Cisco Unified Reporting Administration Guide.
•In the Cisco Cisco Unified Real-Time Monitoring Tool, access the Database Summary service under the CallManager tab to monitor database replication status. The following list indicates the database replication status progress:
–0— Initializing.
–1—Replication setup script fired from this node.
–2—Good replication.
–3—Bad replication.
–4—Replication setup did not succeed.
Before you proceed, ensure that you have a good database replication status. For more information about using the Cisco Unified Real-Time Monitoring Tool, see the Cisco Unified Cisco Unified Real-Time Monitoring Tool Administration Guide.
Step 7 When all other upgrade tasks are complete, you can perform any needed configuration tasks as required.
Upgrade Paths to Cisco Unified Communications Manager 7.1(2a)
For information about supported Cisco Unified CM upgrades, see the Cisco Unified Communications Manager Software Compatibility Matrix at the following URL:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html
Ordering the Upgrade Media
To upgrade to Cisco Unified CM Release 7.1(2a), 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.
Upgrading from Cisco Unified Communications Manager Release 5.1(3e) to 7.1(x) Releases
This information applies when you upgrade from any of the following releases to any 7.1.x release:
•5.1(3e) (5.1.3.6000-2)
•The following 5.1(3e) Engineering Special releases:
–5.1(3.6103-1)
–5.1(3.6102-1)
–5.1(3.6101-1)
Before you upgrade, you must install the COP file ciscocm.513e_upgrade.cop.sgn on the server. This COP file is available from the following URL:
http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=COP-Files&mdfid=280735907&sftType=Unified+Communications+Manager%2FCallManager+Utilities&optPlat=&nodecount=2&edesignator=null&modelName=Cisco+Unified+Communications+Manager+Version+5.1&treeMdfId
For information about installing this COP file, follow the installation instructions included with the COP file.
Note During an upgrade from a compatible Cisco Unified CM 5.1 version (see the Compatibility Matrix at http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html) to Cisco Unified CM 7.1(2a) by using a DVD, in the Software Installation/Upgrade window, ignore the checksum step that tells you "To ensure the integrity of the installation file, verify the MD5 hash value against the Cisco Systems website." Click "Next".
Upgrading to Unified CM 7.1(2a) by Using the UCSInstall File
Because of its size, the UCSInstall iso file, UCOS_7.1.2.20000-2.sgn.iso, comprises two parts:
•UCSInstall_UCOS_7.1.2.20000-2.sgn.iso_part1of2
•UCSInstall_UCOS_7.1.2.20000-2.sgn.iso_part2of2
Procedure
Step 1 From the Software Download page on Cisco.com, download the two UCSInstall files.
Step 2 To combine the two files, execute one of the following commands.
Note Because the 7.1.2.20000-2 build is a nonbootable ISO, it proves useful only for upgrades. You cannot use it for new installations.
a. If you have a Unix/Linux system, copy and paste the following command into the CLI:
b. If you have a Windows system, copy and paste the following command into the command prompt (cmd.exe):
COPY /B UCSInstall_UCOS_7.1.2.20000-2.sgn.iso_part1of2+UCSInstall_UCOS_7.1.2.20000-2.sgn.iso_part2of2 UCSInstall_UCOS_7.1.2.20000-2.sgn.iso
|
Step 3 Use an md5sum utility to verify that the MD5 sum of the final file is correct.
4b9836cd8c29d02c90dd5f9bd8863f16 UCSInstall_UCOS_7.1.2.20000-2.sgn.iso
Step 4 Create a non-bootable DVD that contains the files necessary for the upgrade.
Consider the following:
•Choose the option to burn a disc image, not the option to copy files. Burning a disc image extracts the thousands of files from the .iso file that you created above and writes them to a DVD which is necessary for the files to be accessible for the upgrade.
•Use the Joliet file system, which accommodates filenames up to 64 characters long.
•If the disc-burning application that you use includes an option to verify the contents of the burned disc, choose that option. The application then compares the contents of the burned disc to the source files.
Step 5 Delete unnecessary files, including the two .iso files that you downloaded and the combined .iso file that you created, from the hard disk to free disk space.
Upgrading From an Engineering Special
If you want to upgrade to Cisco Unified CM 7.1(2a) and you are currently running an Engineering Special (ES), contact TAC to obtain the fixes that are included in the ES that you currently use.
The Latest Software Upgrades for Unified CM 7.1 on Cisco.com
You can access the latest software upgrades for Unified CM 7.1 from http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml.
Related Documentation
The view documentation that supports Cisco Unified CM Release 7.1(2a), 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.1(2a) as part of Cisco Unified Communications System Release 7.1 testing, see
http://www.cisco.com/go/unified-techinfo
Note Be aware that the release of Cisco IP telephony products does not always coincide with Cisco Unified Communications Manager releases. If a product does not meet the compatibility testing requirements with Cisco Unified CM, you need to wait until a compatible version of the product becomes available before you can upgrade to Cisco Unified CM Release 7.1(2a). For the most current compatibility combinations and defects that are associated with other Cisco Unified CM products, refer to the documentation that is associated with those products.
Important Notes
The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco Unified Communications Manager Release 7.1(2a).
•Context-Sensitive Help Does Not Display for Some Windows
•CSCta09513 Switch Version Does Not Complete
•CSCta12062 Null Value in NetworkLocale Caused Database Exception
•CSCsz91530 Logical Partitioning Feature Does Not Work Correctly in Conference Scenario When Multiple H.323 Gateways Are Configured in a Route Group
•CSCsy92863 Intercom Route Partition Online Help Is Incorrect
•Admin Password Gets Corrupted If Correction is Made During Password Reset
•Removing Hard Drives
•CSCsz33878 IPMA Wizard Constraint
•CSCsz21235 Core Dump File Gets Generated During the Cisco Security Agent Shutdown Process
•Creating a Custom Help Desk Role and Custom Help Desk User Group
•Use Microsoft Outlook to Receive Cisco Unified Communications Manager Licenses
•Multiple Tenant MWI Modes Service Parameter
•Considerations for LDAP Port Configuration
Context-Sensitive Help Does Not Display for Some Windows
Context-sensitive help (Help > This Page) does not display for the Network Configuration window in the Cisco Unified Communications Operating System (Show > Network). To access the online help for this page, choose Help > Contents. After the online help displays, choose Status and Configuration > Network Configuration.
Context-sensitive help (Help > This Page) does not display for the following windows in the Bulk Administration Tool.
•Access List Export Configuration—Bulk Administration > Mobility > Access List > Access List Export
To access the online help for this page, click Help > Contents. After the online elp displays, choose Cisco Unified CM Bulk Administration Guide > Mobility > Access List > Exporting Access Lists.
•Remote Destination Profile Export Configuration—Bulk Administration > Remote Destination Profile > Remote Destination Profile Export
To access the online help for this page, click Help > Contents. After the online help displays, choose Cisco Unified CM Bulk Administration Guide > Mobility > Remote Destination Profile > Exporting Remote Destination Profile > Using Remote Destination Profile Export.
•Unassigned DN window—Bulk Administration > Phones > Delete Phones > Delete Unassigned DN
See the following section for information on this window:
Deleting Unassigned Directory Numbers
Use the following procedure to delete unassigned directory numbers by creating a query to locate the phone records.
Procedure
Step 1 Choose Bulk Administration > Phones > Delete Phones > Delete Unassinged DN.
The Delete Unassigned Directory Numbers window displays.
Step 2 From the first Delete Bulk Unassigned Directory Number where drop-down list box, choose one of the following criteria:
•Pattern
•Description
•Route Partition
From the second Delete Bulk Unassigned Directory Number where drop-down list box, choose one of the following criteria:
•begins with
•contains
•is exactly
•ends with
•is empty
•is not empty
Step 3 Specify the appropriate search text, if applicable.
Step 4 Click Find.
A list of discovered phones displays by
•Pattern
•Description
•Partition
Tip To find all unassigned directory numbers that are registered in the database, click Find without entering any search text.
Step 5 In the Job Information area, enter the Job description.
The default description is Delete Unassigned DN - Query
Step 6 To delete the unassigned directory numbers immediately, click the Run Immediately radio button. Click Run Later to delete the phone records at a later time.
Step 7 Click Submit to create a job for deleting the phone records.
Note Make sure to browse the entire list of displayed results before submitting the job.
Step 8 To schedule and/or activate this job, use the Job Configuration window.
CSCta09513 Switch Version Does Not Complete
Prior to the release of Cisco Unified Communications Manager Release 7.1(2a), if your servers were running Cisco Unity Connection 2.x and you attempt to upgrade to Cisco Unified CM 7.1(2), the switch version task did not complete to make the new version software the active partition.
The release of Cisco Unified CM 7.1(2a) resolves this problem.
CSCta12062 Null Value in NetworkLocale Caused Database Exception
Prior to Cisco Unified Communications Manager Release 7.1(2), AXL did not allow a tkField to get updated to NULL. When an EMPTY value was sent in tags (for example, <networkLocale></networkLocale> in the UpdatePhone API), the EMPTY value was ignored.
Cisco Unified CM 7.1(2) included a change to this behavior. EMPTY values did not get ignored. They updated the database with a NULL value.
This behavioral change caused applications that send EMPTY values in ENUM tags in their insert operations to fail.
The release of Cisco Unified CM Release 7.1(2a) restores the original behavior. EMPTY tkFields get ignored.
CSCsz91530 Logical Partitioning Feature Does Not Work Correctly in Conference Scenario When Multiple H.323 Gateways Are Configured in a Route Group
The logical partitioning feature does not work as defined in the Cisco Unified Communication Manager Administration Guide under the following conditions:
Conditions
•Enterprise parameter, logical partitioning feature is enabled.
•A single route group gets configured with multiple H.323 gateways
or
A route group gets configured with an H.323 gateway in combination with another MGCP port/SIP trunk device.
Effect
Be aware that, under these conditions, when a call gets routed to the H.323 gateway, the geolocation that corresponds to the call is not available for logical partitioning policy matching.
Workaround
To ensure that you do not encounter this caveat, either
•Configure the route group with a single H.323 gateway.
•Configure the route group with MGCP gateways/ports or SIP trunks (with no limitation on number or combinations).
For more information see CSCsz91530.
CSCsy92863 Intercom Route Partition Online Help Is Incorrect
The Intercom Route Partition Configuration Settings description field in the Configuring Intercom chapter of the Cisco Unified Communications Manager Administration Guide omits a complete list of the non-alphanumeric characters that are not allowed in the description. The unacceptable characters comprise double-quotes ("), angle brackets (<>), square bracket ([ ]), ampersand (&), percentage sign (%).
Admin Password Gets Corrupted If Correction is Made During Password Reset
When you use the Pwrecovery tool to reset your password, if the new password is unacceptable, one of the following messages displays.
•Passwords do not match.
This message displays if, when you attempted to change the password, you did not enter exactly the same word when you confirmed the new password.
•Password too short.
This message displays if the password that you entered is fewer than 6 characters.
•Password in dictionary.
This message displays if the password that you entered already exists in the dictionary or is based on a word that already exists in the dictionary.
If you continue by entering an acceptable password, the system seems to accept the reset password; however, that password cannot be used and attempts to use pwrecovery do not work. GUI log in still works, but you cannot log into the platform GUI or CLI.
Workarounds
•Passwords Do Not Match
•Password Too Short or Password in Dictionary
Passwords Do Not Match
Log in as pwrecovery to relaunch the pwrecovery tool and follow normal procedure.
Password Too Short or Password in Dictionary
Contact TAC to reset the admin password.
Removing Hard Drives
Cisco only supports replacing failed hard drives. Cisco does not support drive pulling/swapping as a method of fast upgrade reversion, restore, or server recovery. For information on replacing a failed hard drive, refer to the Troubleshooting Guide for Cisco Unified Communications Manager.
CSCsz33878 IPMA Wizard Constraint
Be aware that you can run the IPMA Wizard only once. Attempts to run it more than once will fail.
CSCsz21235 Core Dump File Gets Generated During the Cisco Security Agent Shutdown Process
Intermittently, your system may experience a core dump during the Cisco Security Agent for Unified Communications Manager shutdown process.
Cause
Causes of the core dump include
•Use of the CLI command utils disable csa, which disables Security Agent for Unified CM.
•Use of the following CLI commands that shut down Security Agent for Unified CM:
–utils system restart
–utils system shutdown
–utils system switch-version
–utils system upgrade
•During an upgrade, Security Agent for Unified CM shuts down and may cause the core dump file to get generated.
Workaround
No workaround exists. You initiated an action that required Security Agent for Unified CM to shut down. Security Agent for Unified CM will shut down properly, but might leave a core file as a result of the shutdown operation.
The core file gets generated infrequently. This defect does not introduce any security concern and does not impact call processing as it is only encountered after a user-initiated action that requires Security Agent for Unified CM to be shut down.
Creating a Custom Help Desk Role and Custom Help Desk User Group
Some companies want their help desk personnel to have privileges to be able to perform certain tasks, such as adding a phone, adding an end user, or adding an end user to a user group in Cisco Unified Communications Manager Administration.
Performing the steps in the following example allows help desk personnel to add a phone, add an end user, and add the end user to the Standard CCM End Users user group, which allows an end user to access and update the Cisco Unified CM User Options.
Example—Allows Help Desk Personnel to Add Phone, Add End User, and Add End User to User Group
Step 1 In Cisco Unified Communications Manager Administration, choose User Management > Role.
Step 2 Click Add New.
Step 3 From the Application drop-down list box, choose Cisco Unified CM Administration; then, click Next.
Step 4 In the Name field, enter the name of the role; for example, Help Desk.
Step 5 In the Description field, enter a short description; for example, for adding phones and users.
Step 6 Choose one of the following options, which depends on where you want the help desk personnel to perform the task:
a. If you want the help desk personnel to add a phone in the Phone Configuration window and then add an end user in the End User Configuration window. check the read and update privileges check boxes for the User web page resource and the Phone web pages resource; then, click Save.
b. If you want the help desk personnel to add both a phone and a user at the same time in the User and Phone Add window, check the read and update privileges check boxes for the User and Phone add resource and the User web page resource; then, click Save.
Step 7 By performing the following tasks, you create a custom user group for the help desk:
a. In Cisco Unified Communications Manager Administration, choose User Management > User Group; then, click Add New.
b. Enter the name of the custom user group; for example, Help Desk.
c. From the Related Links drop-down list box, choose Assign Roles to User Group; then, click Go.
d. Click the Assign Role to Group button.
e. Check the check box for the custom role that you created in Step 1 through Step 6; in this example, Help Desk. In addition, check the check box for the Standard CCM Admin Users role; then, click Add Selected.
f. In the User Group Configuration window, verify that the roles display in the Role Assignment pane; then, click Save.
Next Steps
In Cisco Unified Communications Manager Administration, the help desk personnel can add the phone, add the user, and add the end user to the user group.
•To add a phone in the Phone Configuration window, choose Device > Phone; then, to add an end user in the End User window, choose User Management > End User.
•To add both a phone and user at the same time in the User and Phone Add window, choose User Management > User and Phone Add.
•To associate the end user with the Standard CCM End Users user group, choose User Management > User Group.
Tip For more information on how to perform these tasks in Cisco Unified Communications Manager Administration, refer to the Cisco Unified Communications Manager Administration Guide.
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 Use the CLI to delete the license file from the Cisco Unified Communications Manager server. In the CLI, run the command, file delete license <name of license file>.
Step 2 Restart the Cisco License Manager service in Cisco Unified Serviceability.
Step 3 Use Microsoft Outlook to save the received license file.
Step 4 In Cisco Unified Communications Manager Administration, upload the saved license file, as described in the "Uploading a License File" section of the Cisco Unified Communications Manager Administration Guide.
For More Information
•"Licensing" chapter, Cisco Unified Communications Manager System Guide
Multiple Tenant MWI Modes Service Parameter
The Multiple Tenant MWI Modes service parameter, which supports the Cisco CallManager service, specifies whether to apply translation patterns to voice-message mailbox numbers. Valid values specify True, which means that Cisco Unified Communications Manager uses translation patterns to convert voice-message mailbox numbers into directory numbers when your voice-messaging system issues a command to set a message waiting indicator, or False, which means that Cisco Unified Communications Manager does not translate the voice-message mailbox numbers that it receives from your voice-messaging system.
Be aware that this service parameter supports Cisco Unified Communications Manager integrations with Cisco Unity Connection or Cisco Unity. If your voice-mail extensions require translation in Cisco Unified Communications Manager, set the Multiple Tenant MWI Modes service parameter to True after you install or upgrade to Cisco Unified Communications Manager 7.1(2).
Considerations for LDAP Port Configuration
When you configure the LDAP Port field in Cisco Unified Communications Manager Administration, you specify the port number that the corporate directory uses to receive LDAP requests. How your corporate directory is configured determines which port number to enter in this field. For example, before you configure the LDAP Port field, determine whether your LDAP server acts as a Global Catalog server and whether your configuration requires LDAP over SSL. Consider entering one of the following port numbers:
Your configuration may require that you enter a different port number than the numbers that are listed in the following bullets. Before you configure the LDAP Port field, contact the administrator of your directory server to determine the correct port number to enter.
LDAP Port For When the LDAP Server Is Not a Global Catalog Server
•389—When SSL is not required. (This port number is the default that displays in the LDAP Port field.)
•636—When SSL is required. (If you enter this port number, make sure that you check the Use SSL check box.)
LDAP Port For When the LDAP Server Is a Global Catalog Server
•3268—When SSL is not required.
•3269—When SSL is required. (If you enter this port number, make sure that you check the Use SSL check box.)
New and Changed Information
This section contains information on the following topics:
•Installation, Upgrade, and Migration
•Cisco Unified Communications Operating System Administration
•Command Line Interface
•Cisco Unified Communications Manager Administration
•Cisco Unified Communications Manager Features and Applications
•Security
•Bulk Administration Tool
•Cisco Unified CM User Options
•Cisco Unified Cisco Unified Real-Time Monitoring Tool
•Cisco Unified Communications Manager CDR Analysis and Reporting
•Cisco Unified Communications Manager Call Detail Records
•Cisco Unified IP Phones
•Cisco Unified CM User Options
Documentation Changes
This section highlights some documentation changes for the 7.1(2) release; for example, this section highlights new documents, new chapters in guides, and information that moved from one document to another document. This section does not contain all the documentation updates for the 7.1(2) release. Use this section in conjunction with the information in the "New and Changed Information" section and the "Documentation Updates" section.
Cisco Unified Communications Manager Administration Updates
•In the Cisco Unified Communications Manager Features and Services Guide and the Cisco Unified Communications Manager System Guide, the configuration checklists now display at the beginning of the chapters.
•In the Cisco Unified Communications Manager Administration Guide, the configuration settings tables now display at the beginning of the chapters.
•In previous releases, the information on configuring the intercom route partition, intercom calling search space, intercom directory number, and intercom translation pattern displayed in the Cisco Unified Communications Manager Administration Guide. This configuration information now exists in the "Intercom" chapter in the Cisco Unified Communications Manager Features and Services Guide.
Troubleshooting information for intercom now exists in the Troubleshooting Guide for Cisco Unified Communications Manager, instead of in the "Intercom" chapter of the Cisco Unified Communications Manager Features and Services Guide.
•In previous releases, the information on configuring device mobility groups and device mobility info displayed in the Cisco Unified Communications Manager Administration Guide. This configuration information now exists in the "Device Mobility" chapter in the Cisco Unified Communications Manager Features and Services Guide.
•The Cisco Unified Communications Manager Features and Services Guide contains a new chapter, "Internet Protocol Version 6 (IPv6)." For information on configuring IPv6, see the "Internet Protocol Version 6 (IPv6)" section and the new chapter.
•The Cisco Unified Communications Manager Features and Services Guide contains a new chapter, "Geolocations and Location Conveyance." For information on configuring geolocations, geolocation filters, and location conveyance, see the "Geolocations, Geolocation Filters, and Location Conveyance" section and the new chapter.
•The Cisco Unified Communications Manager Features and Services Guide contains a new chapter, "Logical Partitioning." For information on configuring logical partitioning, see the "Logical Partitioning" section and the new chapter.
•The Release 7.0(1) version of the "Cisco Unified Mobility" chapter of the Cisco Unified Communications Manager Features and Services Guide included information about all Cisco Unified Mobility features, including Cisco Unified Mobility features and capabilities that are native to Cisco Unified Communications Manager and require configuration entirely within Cisco Unified Communications Manager Administration, as well as Cisco Unified Mobility features and capabilities that require configuration of both Cisco Unified Communications Manager Administration and also Cisco Unified Mobility Advantage.
The Release 7.1(2) version of the "Cisco Unified Mobility" chapter of the Cisco Unified Communications Manager Features and Services Guide includes only the Cisco Unified Mobility features and capabilities that are native to Cisco Unified Communications Manager.
The Cisco Unified Mobility features and capabilities that require configuration of Cisco Unified Mobility Advantage and Cisco Unified Mobile Communicator now get documented in the new chapter, "Cisco Unified Mobility Advantage and Cisco Unified Mobile Communicator Integration," of the Cisco Unified Communications Manager Features and Services Guide. The "Cisco Unified Mobility Advantage and Cisco Unified Mobile Communicator Integration" chapter discusses the following topics:
–Configuration Checklist for Cisco Unified Mobility with Cisco Unified Mobility Advantage
–Introducing Cisco Unified Mobility with Cisco Unified Mobility Advantage, including the following topics—Definitions, List of Cisco Unified Mobility Features with Cisco Unified Mobility Advantage, and Cisco Unified Mobile Communicator, Dial-via-Office Reverse Callback
–Use Case Scenarios for Cisco Unified Mobility Features
–Interactions and Restrictions
–System Requirements
–Configuring Cisco Unified Mobility with Cisco Unified Mobility Advantage
Serviceability Updates
•In previous releases, the Cisco Unified Serviceability Administration Guide contained the "SNMP Troubleshooting" chapter. This chapter now exists in the Troubleshooting Guide for Cisco Unified Communications Manager.
•The Cisco Unified Serviceability Administration Guide contains a new chapter, "Configuring the Audit Log." For information on configuring the audit log, see the "Audit Logging" section and the new chapter.
•With Cisco Unified Communications Manager, Release 7.1(2), a new documentation guide for Managed Service Providers, Cisco Unified Communications Manager Managed Services Guide, Release 7.1, contains the following information:
–New and changed information for Cisco Unified Communications Manager, release-to-release, beginning with 6.0(x).
–Managing and monitoring the health of Cisco Unified Communications Manager Systems including an overview of supported interfaces, hardware platform monitoring, RTMT monitoring of Cisco Unified Communications Manager system health, and critical processes to monitor.
–Overview of the Simple Network Management Protocol, including SNMP tips, troubleshooting, and SNMP/R MIBs.
–Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon, and Alerts chapter describing trace tools and collection, trace field descriptions, and performance monitoring.
–Cisco Unified Serviceability Alarms and CiscoLog Messages that include descriptions, application names, facility/subfacility headers, corrective actions, level of severity.
–Applicable Cisco MIBs, including CISCO-CCM-MIB.
–Applicable industry-standard MIBs, including HOST-RESOURCES-MIB.
–Applicable vendor-specific MIBs, including a list of Cisco-supported servers and MIBs for HP, Intel, and IBM.
Installation, Upgrade, and Migration
This following sections describe the changes for installation, upgrade, and migration in Cisco Unified Communications Manager 7.1(2):
•System History Log for Cisco Unified Communications Manager
•Data Migration Assistant (DMA)
•Device Name of Cisco Unified Mobile Communicator Must Not Exceed 15 Characters Before 7.1(2) Upgrade
System History Log for Cisco Unified Communications Manager
This system history log provides a central location for getting a quick overview of the initial system install, system upgrades, Cisco option installations, DRS backups and DRS restores, as well as switch version and reboot history.
Description
This section provides a description of the system history log feature.
Overview
The system history log exists as a simple ASCII file, system-history.log, and the data does not get maintained in the database. Because it does not get excessively large, the system history file does not get rotated.
The system history log provides the following functions:
•Logs the initial software installation on a server.
•Logs the success and failure of every software upgrade (Cisco option files and patches).
•Logs every DRS backup and restore that is performed.
•Logs every invocation of Switch Version, issued through either the CLI or the GUI.
•Logs every invocation of Restart and Shutdown, issued through either the CLI or the GUI.
•Logs every boot of the system. If not correlated with a restart or shutdown entry, the boot occurs as the result of a manual reboot, power cycle, or kernel panic.
•Maintains a single file that contains the system history, since initial installation or since feature availability.
•Exists in the install folder. You can access the log from the CLI by using the file commands and by using the Real Time Monitoring Tool (RTMT).
System History Log Fields
Each system history log entry contains the following fields:
•<timestamp> <userid> <action> <description> <start/result>
The system history log fields can contain the following values:
•timestamp—Displays the local time and date on the server with the format mm/dd/yyyy hh:mm:ss.
•userid—Displays the user name of the user who invokes the action.
•action—Displays one of the following actions:
–Basic Install
–Windows Upgrade
–Upgrade During Install
–Upgrade
–Cisco Option Install
–Switch Version
–System Restart
–Shutdown
–Boot
–DRS Backup
–DRS Restore
•description—Displays one of the following messages:
–Version: Displays for the Basic Install, Windows Upgrade, Upgrade During Install, Upgrade, and ServerPak Install actions.
–Cisco Option file name: Displays for the Cisco Option Install action.
–Timestamp: Displays for the DRS Backup and DRS Restore actions.
–Active version to inactive version: Displays for the Switch Version action.
–Active version: Displays for the System Restart, Shutdown, and Boot actions.
•result—Displays the following results:
–Start
–Success or Failure
–Cancel
Example
Example 3 shows a sample of the system history log.
Example 3 System History Log
admin:file dump install system-history.log
=======================================
Product Name - Cisco Unified Communications Manager
Product Version - 6.1.2.9901-117
Kernel Image - 2.4.21-47.EL.cs.3BOOT
=======================================
07/25/2008 14:20:06 | root: Install 6.1.2.9901-117 Start
07/25/2008 15:05:37 | root: Install 6.1.2.9901-117 Success
07/25/2008 15:05:38 | root: Boot 6.1.2.9901-117 Start
07/30/2008 10:08:56 | root: Upgrade 6.1.2.9901-126 Start
07/30/2008 10:46:31 | root: Upgrade 6.1.2.9901-126 Success
07/30/2008 10:46:43 | root: Switch Version 6.1.2.9901-117 to 6.1.2.9901-126 Start
07/30/2008 10:48:39 | root: Switch Version 6.1.2.9901-117 to 6.1.2.9901-126 Success
07/30/2008 10:48:39 | root: Restart 6.1.2.9901-126 Start
07/30/2008 10:51:27 | root: Boot 6.1.2.9901-126 Start
08/01/2008 16:29:31 | root: Restart 6.1.2.9901-126 Start
08/01/2008 16:32:31 | root: Boot 6.1.2.9901-126 Start
CLI Considerations
You can access the system history log by using the CLI file command; for example:
•file view install system-history.log
•file get install system-history.log
Cisco Unified Communications Manager Administration Configuration Tips
No Cisco Unified Communications Manager Administration configuration tips exist for this feature.
GUI Changes
No GUI changes exist for this feature.
Service Parameter and Enterprise Parameter Changes
No service parameter and enterprise parameter changes exist for this feature.
Installation/Upgrade (Migration) Considerations
No installation or upgrade considerations exist for this feature.
Serviceability Considerations
To access the system history log in RTMT, navigate to RTMT Trace Collection:
RTMT > Trace Log Collection
BAT Considerations
No BAT considerations exist for this feature.
CAR/CDR Considerations
No CAR/CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL and CTI considerations exist for this feature.
User Tips
No user tips exist for this feature.
For More Information
For more information about using the CLI, see the Cisco Unified Communications Operating System Administration Guide or the Command Line Interface Reference Guide for Cisco Unified Solutions.
For more information about RTMT, see the Cisco Unified Real-Time Monitoring Tool Administration Guide.
Data Migration Assistant (DMA)
Cisco Unified Communications Manager Release 7.1(2) includes the following Data Migration Assistant (DMA) enhancements. For more details, refer to the documents Data Migration Assistant User Guide 7.1(2) and Upgrading to Cisco Unified Communications Manager Release 7.1(2) from 4.x Releases:
•The platformConfig.xml file that is generated by DMA supports upgrades for the first node (publisher database server) as well as for the subsequent nodes (subscribers). DMA provides a window where you can make detailed configuration specifications. Enter data at the DMA window Export > Answer File Generator.
•DMA provides a window where users can customize the behavior of DMA, by specifying which types of logs to include in the output file. Enter data at the DMA window Export > Custom Options.
•DMA explicitly lists the pre-DMA export tasks. DMA provides both information and the automation of pre-export tasks, when possible, to ensure that you know what tasks you need to complete before running DMA. Enter data at the DMA window Export > Pre-Export Tasks.
•DMA supports the generation of a license file upon successful DMA validation. Go to the DMA window Export > Storage Location and specify a local directory destination for the license file licupgrade.lic Specify the destination in the "Path Name" text box of the "Destination Option for License File" field.
•DMA displays the latest timestamp of the CDR and CAR data. If these timestamps do not match, DMA displays a message that indicates that users must load the latest CDR records into the CAR database for the records to be exported.
•DMA enhances pre-upgrade instructions with regard to the CAR database. DMA displays information from the CAR database, including current number of CAR records, start date, and end date, so users can determine how many records exist and how many records that DMA can export.
•DMA provides options on how to handle CAR data during the DMA export process. The default option specifies that DMA does not export the CAR database. If you want to have this data included in the DMA TAR file, you must choose to include the CAR records in the DMA TAR file. DMA indicates the time (in 30 minute intervals) that DMA requires to migrate the CAR data. DMA displays the approximate number of records that are migrated during this time as well as the total number of CAR records on the server.
DMA does not support manual removal of the C:\DMARoot folder. If the folder is removed during the export process, DMA generates an error.
Allow as much time as possible—preferably several weeks—between the completion of your Data Migration Assistant backup and the beginning of your upgrade to Cisco Unified Communications Manager Release 7.1(2).
For More Information
•Upgrade of CAR Data
Device Name of Cisco Unified Mobile Communicator Must Not Exceed 15 Characters Before 7.1(2) Upgrade
For information on this topic, see the "Device Name of Cisco Unified Mobile Communicator Must Not Exceed 15 Characters Before 7.1(2a) Upgrade" section.
Cisco Unified Communications Operating System Administration
This section describes changes to the Cisco Unified Communications Operating System Administration GUI.
•Customized Log-on Message
•Ethernet IPv6 Configuration Settings
Customized Log-on Message
You can upload a text file that contains a customized log-on message that appears in Cisco Unified Communications Operating System Administration, Cisco Unified Communications Manager Administration, and the command line interface.
To upload a customized log-on message, follow this procedure:
Procedure
Step 1 From the Cisco Unified Communications Operating System Administration window, navigate to Software Upgrades > Customized Logon Message.
The Customized Logon Message window displays.
Step 2 To choose the text file that you want to upload, click Browse.
Step 3 Click Upload File.
Note You cannot upload a file that is larger than 10 KB.
When you next log in to the system, the customized log-on message displays.
Step 4 To revert to the default log-on message, click Delete.
Your customized log-on message gets deleted, and the system displays the default log-on message.
Ethernet IPv6 Configuration Settings
Use the following procedure to enable and configure IPv6 on the server.
Note All Ethernet settings apply only to Eth0. You cannot configure any settings for Eth1. The Maximum Transmission Unit (MTU) on Eth0 defaults to 1500.
Procedure
Step 1 From the Cisco Unified Communications Operating System Administration window, navigate to Settings > IP > Ethernet IPv6.
The Ethernet IPv6 Configuration window displays.
Step 2 To modify the Ethernet settings, enter the new values in the appropriate fields. For a description of the fields on the Ethernet IPv6 Configuration window, see Table 2.
Step 3 To preserve your changes, click Save.
Note If you check the Update with Reboot check box, the system reboots after you click Save. For the IPv6 settings to take effect, you must reboot the system.
Table 2 Ethernet IPv6 Configuration Fields and Descriptions
Field
|
Description
|
Enable IPv6
|
Check this check box to enable IPv6 on the server.
|
Address Source
|
Choose one of the following IP address sources:
•Router Advertisement
•DHCP
•Manual Entry
Be aware that the three IP address sources are mutually exclusive.
Note Unless you specify Manual Entry, the IP Address and Mask fields remain read only.
|
IPv6 Address
|
If you chose Manual Entry, enter the IPv6 address of the server; for example:
fd6:2:6:96:21e:bff:fecc:2e3a
|
IPv6 Mask
|
If you chose Manual Entry, enter the IPv6 mask; for example:
64
|
Update with Reboot
|
If you want the system to reboot immediately after you click Save, check this check box. If you want to reboot later, leave the check box blank.
Note For the IPv6 settings to take effect, you must reboot the system.
|
For More Information
•Internet Protocol Version 6 (IPv6)
Command Line Interface
This section contains information about the Command Line Interface (CLI).
•show memory
•Spaces in File Names
•Relative Paths
•New Commands and Parameters
show memory
The Command Line Interface Reference Guide for Cisco Unified Communications Solutions Release 6.1(3) does not contain updated information for the show memory command. Use the following updated information.
Command Syntax
show memory
count
modules
size
Options
•count—Displays the number of memory modules on the system.
•modules—Displays detailed information about all the memory modules.
•size—Displays the total amount of memory.
Parameters
None
Spaces in File Names
You can use CLI commands to directly work with file names that contain spaces. For example, you could use the file delete command to delete a log file with the name cisco test log in the Platform directory:
file delete activelog platform cisco test log
Relative Paths
When you download a file to your local computer with the file get command, the system prompts you to enter a download directory. You can specify a relative path for the download directory by using the ./ notation, as shown in the following example:
Download directory: ./RepStat
If you specify a download directory that does not exist on your local computer, the file get command creates it for you.
New Commands and Parameters
This section provides information about the new CLI commands for Cisco Unified Communications Manager Release 7.1(2).
For more information about command syntax and parameters, see the Command Line Interface Reference Guide for Cisco Unified Solutions.
•utils auditd {enable|disable|status}
This command enables, disables, and provides the status of audit logging. When audit logging is enabled, the system monitors and records user actions in both Cisco Unified Communications Manager and Cisco Unified Serviceability.
You can also use the CLI file commands to manipulate the audit log, including the following commands:
–file list activelog audit
–file view activelog audit <filename>
–file dump activelog audit <filename>
–file get activelog audit <filename>
–file search activelog audit <filename>
Note Cisco recommends that you retrieve the audit log by using the Cisco Unified Real-Time Monitoring Tool.
•utils create report csa
This command collects all the files that are required for CSA diagnostics and assembles them into a single CSA diagnostics file. You can retrieve this file by using the file get command.
•set password complexity character {enable|disable}
Use this command to enable password complexity rules for the type of characters in a password.
When you enable password complexity, you must follow these guidelines when you assign a password:
–It must have at least one lower-case character.
–It must have at least one uppercase, one digit, and one special character.
–You cannot use adjacent characters on the keyboard.
–You cannot reuse any of the previous 10 passwords.
–You can change the admin user password only once in 24 hours.
•set password complexity minimum-length
Note Use this command only after you enable password character complexity.
Use this command to modify the value for the minimum password length for Cisco Unified Communications Operating System accounts.
Acceptable values must be equal-to or greater-than 6.
•set password age maximum
Use this command to modify the value for maximum password age, in days, for Cisco Unified Communications Operating System accounts.
Be aware that acceptable values must be equal-to or greater-than 90 days.
In the Command Line Interface, the system supports the following commands that are related to enabling and configuring IPv6:
•set network ipv6
This command enables IPv6 and sets system and network options.
•show network ipv6
This command displays IPv6 network routes and network settings.
•utils network ipv6 firewall
This command sets options and displays status for the IPv6 network firewall.
•utils network ipv6 host
This command does an IPv6 host lookup (or IPv6 address lookup) for the specified host name or IPv6 address.
•utils network ipv6 ping
This command allows you to ping an IPv6 address or hostname.
Cisco Unified Communications Manager Administration
This section contains information on the following topics:
•New and Updated Enterprise and System Parameters
•Menu Changes
•Cisco Unified Communications Manager Features and Applications
New and Updated Enterprise and System Parameters
The following sections contain information on new and updated enterprise and service parameters:
•Enterprise Parameters
•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 service parameter, click the name of the enterprise parameter in the window.
•Enable IPv6—See the "Internet Protocol Version 6 (IPv6)" section.
•IP Addressing Mode Preference for Media—See the "Internet Protocol Version 6 (IPv6)" section.
•IP Addressing Mode Preference for Signaling—See the "Internet Protocol Version 6 (IPv6)" section.
•Allow Auto-Configuration for Phones—See the "Internet Protocol Version 6 (IPv6)" section.
•Enable Logical Partitioning—See the "Logical Partitioning" section.
•Default Geolocation—See the "Logical Partitioning" section.
•Logical Partitioning Default Policy—See the "Logical Partitioning" section.
•Logical Partitioning Default Filter—See the "Logical Partitioning" section.
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.
•Party Entrance Tone—This parameter supports the Cisco CallManager service for the Viewing Held Calls on Shared Lines feature.
•Always Use Prime Line—This parameter supports the Cisco CallManager service for the Always Use Prime Line feature.
•Always Use Prime Line for Voice Message—This parameter supports the Cisco CallManager service for the Always Use Prime Line for Voice Message feature.
•Table Out Of Sync—This parameter supports the Cisco CallManager service for the Table Out of Sync Detection feature.
•Send Multicast MOH in H.245 OLC Message—This parameter supports the Cisco CallManager service for the Multicast Music On Hold Over H.323 Intercluster Trunks feature.
•Call Counting CAC Enabled—This parameter supports the Cisco CallManager service for the Internet Protocol Version 6 (IPv6) feature.
•Audio Bandwidth For Call Counting CAC—This parameter supports the Cisco CallManager service for the Internet Protocol Version 6 (IPv6) feature.
•Video Bandwidth For Call Counting CAC—This parameter supports the Cisco CallManager service for the Internet Protocol Version 6 (IPv6) feature.
•Alternate Cisco File Server(s)—This parameter supports the Cisco TFTP service for the Internet Protocol Version 6 (IPv6) feature.
•TFTP IP Address—This parameter for the Cisco TFTP service no longer gets used in Cisco Unified Communications Manager Release 7.1(2). Previously, this parameter determined whether the local IP address would get used. Valid values specified True (use the local IP address) or False (use the IP address that the TFTP IP Address parameter specifies). This parameter got used in conjunction with the TFTP IP Address parameter if the TFTP server possessed multiple NICs. In that case, this parameter got set to False, and the TFTP IP Address parameter got set to the IP address of the NIC to use for serving files via TFTP.
•Server IP Track—This parameter for the Cisco TFTP service no longer gets used as of Cisco Unified Communications Manager Release 7.1(2). Previously, this parameter specified the IPv4 address of the NIC to use for serving files via TFTP. If your TFTP server possessed multiple NICs, this parameter got used in combination with the Server IP Track parameter. This parameter got set to the IP address of the NIC to use for serving files via TFTP, and the Server IP Track would get set to False. When a specific IPv4 address was set for this parameter, it had to match the value that was set in the TFTP Server 1 or TFTP Server 2 settings on the phone, or the TFTP server addresses in the DHCP options if DHCP was used for phone to obtain server addresses.
Menu Changes
This section contains information on the following menus in Cisco Unified Communications Manager Administration:
•Main Window
•System
•Call Routing
•Media Resources
•Voice Mail
•Device
•Application
•User Management
•Bulk Administration
Main Window
The main window contains the following changes:
•After you log in to Cisco Unified Communications Manager Administration, messages may display that indicate the current state of licenses for Cisco Unified Communications Manager. For more information, see the "Licensing Enhancements" section.
•Customized Log-on Message—You can upload a text file that contains a customized log-on message that displays on the initial Cisco Unified Communications Manager Administration window. For more information and the procedure for uploading your customized log-on message, refer to Chapter 7 in the Cisco Unified Communications Operating System Administration Guide.
•Last Successful Logon—When you log in to Cisco Unified Communications Manager Administration, the initial Cisco Unified Communications Manager Administration window displays the date and time of the last successful system logon.
System
The System menu contains the following changes:
•System > Server—The IPv6 Name field displays, as described in the "Internet Protocol Version 6 (IPv6)" section.
•System > Device Pool—For new and updated incoming calling party settings, see the "Calling Party Normalization Enhancements" section. The "Geolocations, Geolocation Filters, and Location Conveyance" section describes the Geolocation and Geolocation Filter fields that are added in the new Geolocation Pane.
•System > Enterprise Parameters—For information on new or updated enterprise parameters, see the "New and Updated Enterprise and System Parameters" section.
•System > Service Parameters —For information on new or updated service parameters, see the "New and Updated Enterprise and System Parameters" section.
•System > LDAP > LDAP System—In the LDAP System Information field, the drop-down list box LDAP Server Type contains the new option, OpenLDAP. For this new option, the associated selections in the drop-down list box, LDAP Attribute for User ID, remain the same as for the Netscape or Sun ONE LDAP Server.
•System > Licensing > License File Upload—This window displays a message that uploading the license file removes the demo licenses for the feature. For more information, see the "Licensing Enhancements" section.
•System > Licensing > License File Upload—This window displays the status of a license file. For example, the Status column for each license type may display Demo, Missing, or Uploaded. For more information, see the "Licensing Enhancements" section.
•System > Geolocation Configuration—This menu option allows configuration of a geolocation. For more information, see the "Geolocations, Geolocation Filters, and Location Conveyance" section.
•System > Geolocation Filter—This menu option allows configuration of a geolocation filter. For more information, see the "Geolocations, Geolocation Filters, and Location Conveyance" section.
Call Routing
The Call Routing menu provides the following new and updated settings.
•Call Routing > SIP Route Pattern—The IPv6 Pattern field displays, as described in the "Internet Protocol Version 6 (IPv6)" section.
•Call Routing > Directory Number—The Log Missed Calls check box displays, as described in the "Logging Missed Calls for Shared Lines" section.
•Call Routing > Logical Partitioning Policy—This window allows configuration of a logical partition policy. For more information, see the "Logical Partitioning" section.
Media Resources
No changes exist for the Media Resources menu.
Voice Mail
No changes exist for the Voice Mail menu.
Device
•Device > CTI Route Point—The Geolocation field displays, as described in the "Geolocations, Geolocation Filters, and Location Conveyance" section.
•Device > Gateway—For new and updated incoming calling party settings, see the "Calling Party Normalization Enhancements" section. The Geolocation and Geolocation Filter fields display, as described in the "Geolocations, Geolocation Filters, and Location Conveyance" section.
•Device > Phone—The Always Use Prime Line drop-down list box displays, as described in the "Always Use Prime Line" section. The Always Use Prime Line For Voice Mail drop-down list box displays, as described in the "Always Use Prime Line for Voice Message" section. The Geolocation field displays, as described in the "Geolocations, Geolocation Filters, and Location Conveyance" section.
•Device > Trunk—The Destination Address IPv6 field displays for SIP trunks, as described in the "Internet Protocol Version 6 (IPv6)" section. For new and updated incoming calling party settings, see the "Calling Party Normalization Enhancements" section. In the Geolocation Configuration pane, the Geolocation and Geolocation Filter fields and the Send Geolocation Information check box display, as described in the "Geolocations, Geolocation Filters, and Location Conveyance" section.
•Device > Device Settings > Default Device Profile—The Always Use Prime Line drop-down list box displays, as described in the "Always Use Prime Line" section. The Always Use Prime Line For Voice Mail drop-down list box displays, as described in the "Always Use Prime Line for Voice Message" section.
•Device > Device Settings > Device Profile—The Always Use Prime Line drop-down list box displays, as described in the "Always Use Prime Line" section. The Always Use Prime Line For Voice Mail drop-down list box displays, as described in the "Always Use Prime Line for Voice Message" section.
•Device > Device Settings > SIP Profile—The Enable ANAT check box displays, as described in the "Internet Protocol Version 6 (IPv6)" section.
•Device > Device Settings > Common Device Configuration—The IP Addressing Mode drop-down list box, the IP Addressing Mode Preference for Signaling drop-down list box, and the Allow Auto-Configuration for Phones drop-down list box display, as described in the "Internet Protocol Version 6 (IPv6)" section.
•Device > Device Settings > Common Phone Profile—The Always Use Prime Line drop-down list box displays, as described in the "Always Use Prime Line" section. The Always Use Prime Line For Voice Mail drop-down list box displays, as described in the "Always Use Prime Line for Voice Message" section.
Application
No updates or new fields exist for this menu.
User Management
The User Management menu displays the following new settings:
•User Management > Role—The Find and List Roles window displays the Standard Audit Log Administration role, as described in the "Standard Audit Log Administration Role" section.
•User Management > User Group—The Find and List User Groups window displays the Standard Audit Users user group, as described in the "Standard Audit Users User Group" section.
Bulk Administration
The Bulk Administration menu displays the following new and updated settings.
•Bulk Administration > Phones > Phone Template—The Always Use Prime Line drop-down list box displays, as described in the "Always Use Prime Line" section. The Always Use Prime Line For Voice Mail drop-down list box displays, as described in the "Always Use Prime Line for Voice Message" section.
•Bulk Administration > User Device Profile > UDP Template—The Always Use Prime Line drop-down list box displays, as described in the "Always Use Prime Line" section. The Always Use Prime Line For Voice Mail drop-down list box displays, as described in the "Always Use Prime Line for Voice Message" section.
•Bulk Administration > Phones > Update Phones—The Always Use Prime Line drop-down list box displays, as described in the "Always Use Prime Line" section. The Always Use Prime Line For Voice Mail drop-down list box displays, as described in the "Always Use Prime Line for Voice Message" section.
•Bulk Administration > Phones > Phone Template. Click Add New DN in the Associated Information Area—Log Missed Calls Check Box displays as described in the "Logging Missed Calls for Shared Lines" section.
•Bulk Administration > User Device Profile > UDP Template. Click Add New DN in the Associated Information Area—Log Missed Calls Check Box displays as described in the "Logging Missed Calls for Shared Lines" section.
•Bulk Administration > Phones > Add/Update Lines > Update Lines—Log Missed Calls Check Box displays as described in the "Logging Missed Calls for Shared Lines" section.
•Bulk Administration > User device Profiles > Add/Update Lines > Update Lines—Log Missed Calls Check Box displays as described in the "Logging Missed Calls for Shared Lines" section.
•Bulk Administration > Phones > Phone Template. Click Add New DN in the Associated Information Area—Party Entrance Tone drop-down list box displays, as described in the "Party Entrance Tone" section.
•Bulk Administration > User Device Profile > UDP Template. Click Add New DN in the Associated Information Area—Party Entrance Tone drop-down list box displays, as described in the "Party Entrance Tone" section.
•Bulk Administration > Gateways > Gateway Template. Click Add New DN in the Associated Information Area—Party Entrance Tone drop-down list box displays, as described in the "Party Entrance Tone" section.
•Bulk Administration > Gateways > Gateway Template—VG202 and VG204 gateways now display in the Gateway Type drop-down list box as described in the "Support for VG202 and VG204 Gateways" section.
•Bulk Administration > Gateways > Insert Gateways—VG202 and VG204 gateways now display in the Gateway Type drop-down list box as described in the "Support for VG202 and VG204 Gateways" section.
•Bulk Administration > Gateways > Insert Gateways—Select Gateway type and click Next. The second Insert Gateways Configuration window displays—Sample insert gateways link now displays VG202 and VG204 sample files along with other BAT-supported gateways as described in the "Support for VG202 and VG204 Gateways" section.
•Bulk Administration > Phone Migration—The Phone Migration window displays, as described in the "Phone Migration in BAT" section.
•Bulk Administration > Phones > Phone Template—The GeoLocation drop-down list box displays, as described in the "Support for Geolocations and Logical Partitioning" section.
•Bulk Administration > Gateways > Gateway Templates. Phone Template Configuration window—The GeoLocation drop-down list box displays, as described in the "Support for Geolocations and Logical Partitioning" section.
•Bulk Administration > Import/Export > Export—The "New fields That Are Supported for Export by Import/Export" section describes the new fields that are supported for export by the Import/Export tool.
•Bulk Administration > Phones > Update Phones—The Apply Config button displays, as described in the "Support for Seamless Integration (Apply Config)" section.
•Bulk Administration > Phones > Reset/Restart Phones—The Apply Config button displays, as described in the "Support for Seamless Integration (Apply Config)" section.
Cisco Unified Communications Manager Features and Applications
This section contains information on the following Cisco Unified Communications Manager Administration features and applications:
•Always Use Prime Line
•Always Use Prime Line for Voice Message
•Barge, cBarge, and Single Button Barge Support for PLAR
•Calling Party Normalization Enhancements
•Cisco Unified Communications Manager Assistant Enhancements for Numeric User ID Login
•Cisco Unified Communications Manager Attendant Console Support in 7.1(2)
•Cisco Web Dialer Configured in Application Server Window
•G.Clear Codec Support on SIP Trunks
•Geolocations, Geolocation Filters, and Location Conveyance
•H.235—Pass-Through Support
•H.329—Extended Video Channel Support
•Internet Protocol Version 6 (IPv6)
•Licensing Enhancements
•Logging Missed Calls for Shared Lines
•Logical Partitioning
•Multicast Music On Hold Over H.323 Intercluster Trunks
•Off-Hook Abbreviated Dial
•OpenLDAP 2.3.41 Can Synchronize with Cisco Unified Communications Manager Database
•Party Entrance Tone
•Phone Migration in Cisco Unified Communications Manager Administration
•QSIG Variant Configuration for a Gateway or Trunk
•Synchronization of Configuration Settings
•Standard Audit Log Administration Role
•Standard Audit Users User Group
•Table Out of Sync Detection
•Unconfigured Device Registration Attempts Restricted
•Viewing Held Calls on Shared Lines
Always Use Prime Line
Tip Cisco Unified Communications Manager Releases 7.1(2) and 6.1(3) introduce this feature.
Description
After you configure the Always Use Prime Line setting in Cisco Unified Communications Manager Administration, when the phone is idle (off hook) and receives a call on any line, the primary line gets chosen for the call.
Tip To configure the Always Use Prime Line feature in previous releases of Cisco Unified Communications Manager [except for 6.1(3)], you configured the Always Use Prime Line service parameter for the Cisco CallManager service, which applied to the entire cluster. In Cisco Unified Communications Manager 7.1(2) and 6.1(3) (or later), you can configure the Always Use Prime Line setting for devices and device profiles.
Cisco Unified Communications Manager Administration Configuration Tips
When you configure this feature, going off hook makes only the first line active, even when a call rings on another line on the phone; that is, the call does not get answered on that line. In this case, the phone user must choose the other line to answer the call.
For more configuration considerations, see Table 3.
GUI Changes
The Always Use Prime Line setting displays in the following windows in Cisco Unified Communications Manager Administration.
•System > Service Parameters (for Cisco CallManager service)
•Device > Phone
•Device > Common Phone Profile
•Device > Device Settings > Default Device Profile
•Device > Device Settings > Device Profile
For information on how the Always Use Prime Line setting works when a phone idle or busy, see Table 3.
Tip If you configure the Always Use Prime Line setting in the Service Parameter, Common Phone Profile, and the Phone Configuration window, Cisco Unified Communications Manager uses the configuration from the Phone Configuration window.
Table 3 Always Use Prime Line Configuration
State of Phone
|
Configuration for Always Use Prime Line
|
How Feature Works
|
Idle
|
On
|
When the phone is idle (off hook) and receives a call on any line, the primary line gets chosen for the call. Calls on other lines continue to ring, and the phone user must select those other lines to answer these calls.
If you choose On for the Always Use Prime Line setting in the Device Profile or Default Device Profile Configuration window, a Cisco Extension Mobility user can use this feature after the user logs in to the device that supports Cisco Extension Mobility; that is, if you configure Cisco Extension Mobility correctly.
|
Idle
|
Off
|
When the phone is idle and receives a call on any line, the phone user answers the call from the line on which the call is received; that is, when the phone is off hook.
|
Idle
|
Default
|
If you choose Default for the Always Use Prime Line setting in the Common Phone Profile, the Device Profile, or the Default Device Profile Configuration window, Cisco Unified Communications Manager uses the configuration from the Always Use Prime Line service parameter when it determines whether a user, including a Cisco Extension Mobility user, can use this feature.
If you choose Default for the Always Use Prime Line setting in the Phone Configuration window, Cisco Unified Communications Manager uses the configuration from the common phone profile.
|
Busy
|
On
|
When the phone already has a call on a line, Cisco Unified Communications Manager uses the configuration for the Maximum Number of Calls and Busy Trigger settings to determine how to route the call.
|
Idle
|
On, but you also configured Auto Answer With Headset or Auto Answer with Speakerphone
|
If you choose the Auto Answer with Headset option or Auto Answer with Speakerphone option from the Auto Answer drop-down list box in Cisco Unified Communications Manager Administration, the Auto Answer configuration overrides the configuration for the Always Use Prime Line setting.
|
Service Parameter and Enterprise Parameter Changes
If you want to configure this feature via the clusterwide service parameter, Always Use Prime Line, which supports the Cisco CallManager service, choose System > Service Parameters in Cisco Unified Communications Manager Administration. Then, choose the server and the Cisco CallManager service. From the Always Use Prime Line drop-down list box, choose True.
Installation/Upgrade (Migration) Considerations
No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 7.1(2), you can configure this feature per device or per device profile.
Serviceability Considerations
This feature relies on the Cisco CallManager service, so activate the service by choosing Tools > Service Activation in Cisco Unified Serviceability. In addition, you can run SDI trace for the Cisco CallManager service. When you view the log in RTMT, you can see the configured value that is used by the device; for example, alwaysPrimeLine=1, which indicates that the device uses On for the configuration.
BAT Considerations
The Bulk Administration GUI includes the following updates to support the Always Use Prime Line feature: Always Use Prime Line drop-down list box—choose one of the following options:
•Off
•On
•Default
Note For details of configuration options for the Always Use Prime Line feature, refer to Table 3.
Note The Always Use Prime Line drop-down list box displays in the Phone Template, UDP Template, and Update Phone windows.
•Insert, Export, and Validate Details support for always use prime line—The following insert, export, and validate details features receive support for the always use prime line feature:
–Insert Phones Specific Details
–Insert Phones All Details
–Export Phones Specific Details
–Export Phones All Details
–Validate Phones All Details
–Validate Phones Specific Details
–Insert UDP All Details
–Insert UDP Specific Details
–Export UDP All Details
–Export UDP Specific Details
–Validate UDP All Details
–Validate UDP Specific Details
–Insert Phones/Users
–Validate Phones/Users
•UDP File Format—UDP File Format Configuration window lists the Always Use Prime Line, and Always Use Prime Line for Voice Message drop-down list boxes in the device fields section.
•Generate User Device Profile Report—The Generate User Device Profile Report Configuration window lists the Always Use Prime Line and Always Use Prime Line for Voice Message fields in the Device Fields section.
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
See the "Always Use Prime Line" section.
User Tips
For a list of phones that support this feature, see the "Line Select" section.
For More Information
•Always Use Prime Line for Voice Message
•Line Select
Always Use Prime Line for Voice Message
Tip Cisco Unified Communications Manager Releases 7.1(2) and 6.1(3) introduce this feature.
Description
After you configure the Always Use Prime Line for Voice Message setting in Cisco Unified Communications Manager Administration, the primary line on the phone becomes the active line for retrieving voice messages when the phone user presses the Messages button on the phone.
Tip To configure the Always Use Prime Line for Voice Message feature in previous releases of Cisco Unified Communications Manager [except for 6.1(3)], you configured the Always Use Prime Line service parameter for the Cisco CallManager service, which applied to the entire cluster. In Cisco Unified Communications Manager 7.1(2) and 6.1(3) (or later), you can configure the Always Use Prime Line for Voice Message setting for devices and device profiles.
Cisco Unified Communications Manager Administration Configuration Tips
For configuration considerations, see Table 4.
GUI Changes
The Always Use Prime Line for Voice Message setting displays in the following windows in Cisco Unified Communications Manager Administration.
•System > Service Parameters (for Cisco CallManager service)
•Device > Phone
•Device > Common Phone Profile
•Device > Device Settings > Default Device Profile
•Device > Device Settings > Device Profile
For information on how the Always Use Prime Line for Voice Message setting works when a phone is idle or busy, see Table 4.
Tip If you configure the Always Use Prime Line for Voice Message setting in the Service Parameter, Common Phone Profile, and in the Phone Configuration window, Cisco Unified Communications Manager uses the configuration from the Phone Configuration window.
Table 4 Always Use Prime Line for Voice Mail Configuration
State of Phone
|
Configuration for Always Use Prime Line for Voice Message
|
How Feature Works
|
Idle
|
On
|
If the phone is idle, the primary line on the phone becomes the active line for retrieving voice messages when the phone user presses the Messages button on the phone.
If you choose On for the Always Use Prime Line for Voice Mail setting in the Device Profile or Default Device Profile Configuration window, a Cisco Extension Mobility user can use this feature after logging in to the device that supports Cisco Extension Mobility; that is, if you configure Cisco Extension Mobility correctly.
|
Idle
|
Off
|
If the phone is idle, pressing the Messages button on the phone automatically dials the voice-messaging system from the line that has a voice message. It will always select the first line that has a VM. If no line has a voice message, the primary line gets used when the phone user presses the Messages button.
|
Idle
|
Default
|
If you choose Default for the Always Use Prime Line for Voice Mail setting in the Phone Configuration, the Common Phone Profile, the Device Profile, or the Default Device Profile Configuration window, Cisco Unified Communications Manager uses the configuration from the Always Use Prime Line service parameter when it determines whether a user, including a Cisco Extension Mobility user, can use this feature.
If you choose Default for the Always Use Prime Line for Voice Mail setting in the Phone Configuration window, Cisco Unified Communications Manager uses the configuration from the common phone profile.
|
Busy
|
On
|
If the device is busy, this feature does not work.
|
Service Parameter and Enterprise Parameter Changes
If you want to configure this feature via the clusterwide service parameter, Always Use Prime Line for Voice Message, which supports the Cisco CallManager service, choose System > Service Parameters in Cisco Unified Communications Manager Administration. Then, choose the server and the Cisco CallManager service. From the Always Use Prime Line for Voice Message drop-down list box, choose True.
Installation/Upgrade (Migration) Considerations
No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 7.1(2), you can configure this feature per device.
Serviceability Considerations
This feature relies on the Cisco CallManager service, so activate the service by choosing Tools > Service Activation in Cisco Unified Serviceability. In addition, you can run SDI trace for the Cisco CallManager service. When you view the log in RTMT, you can see the configured value that is used by the device; for example, alwaysUsePrimeLineForVM=2, which indicates that the device uses the default.
BAT Considerations
The Bulk Administration GUI includes the following updates to support the Always Use Prime Line for Voice Mail feature:
Always Use Prime Line for Voice Message drop-down list box—Choose one of the following options:
•Off
•On
•Default
Note For details of configuration options for the Always Use Prime Line for Voice Mail feature, refer to Table 4.
Note The Always Use Prime Line for Voice Message drop-down list boxes display in the Phone Template, UDP Template, and Update Phone windows.
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
See the "Always Use Prime Line" section.
User Tips
For a list of phones that support this feature, see the "Line Select" section.
For More Information
•Always Use Prime Line
•Line Select
Barge, cBarge, and Single Button Barge Support for PLAR
Tip Cisco Unified Communications Manager Releases 7.1(2) and 6.1(3) introduce this feature.
Description
Barge, cBarge, or single-button barge allow a phone user to get added to a remotely active call that is on a shared line. Private Line Automatic Ringdown (PLAR) allows the phone user to dial a preconfigured number, and only this number, from the PLAR line. In Cisco Unified Communications Manager 7.1(2), a barge, cBarge, or single-button barge initiator can barge into a call via a shared line that is configured for PLAR; that is, the initiator can barge into the call if the barge target uses the preconfigured number that is associated with the PLAR line while on the call.
In previous releases of Cisco Unified Communications Manager [except for 6.1(3)], Cisco Unified Communications Manager sent the cBarge invocation to the PLAR line before it connected the barge call. If the PLAR line was busy in previous releases, the initiator received a busy reorder tone. In Cisco Unified Communications Manager 7.1(2) and 6.1(3) [and later 6.1(x) releases], Cisco Unified Communications Manager does not send the barge invocation to the PLAR line before it connects the barge call, so the barge occurs no matter what the state of the PLAR destination is.
Cisco Unified Communications Manager Administration Configuration Tips
To make barge, cBarge, or single-button barge work with PLAR, you must configure barge, cBarge, or single-button barge as described in the "Barge and Privacy" chapter in the Cisco Unified Communications Manager Features and Services Guide. In addition, you must configure the PLAR destination, a directory number that is used specifically for PLAR. The following examples describe how to enable PLAR functionality for phones that are running SCCP and for phones that are running SIP.
A and A' represent shared-line devices that you configured for barge, cBarge, or single-button barge, and B1 represents the directory number for the PLAR destination. To enable PLAR functionality from A/A', which are running SIP, see the following example:
Tip Step 1 through Step 4 apply if you want to configure PLAR for phones that are running SCCP. For phones that are running SIP, you must perform Step 1 through Step 6.
Example for How to Configure PLAR
Step 1 Create a partition, for example, P1, and a calling search space, for example CSS1, so CSS1 contains P1. (In Cisco Unified Communications Manager Administration, choose Call Routing > Class of Control > Partition or Calling Search Space.)
Step 2 Create a translation pattern, for example, TP1, that contains calling search space CSS1 and partition P1. Create a null pattern (blank pattern), but make sure that you enter the directory number for the B1 PLAR destination in the Called Party Transformation Mask field. (In Cisco Unified Communications Manager Administration, choose Call Routing > Translation Pattern.)
Step 3 Assign the calling search space, CS1, to either A or A'. (In Cisco Unified Communications Manager Administration, choose Device > Phone.)
Step 4 Assign the P1 partition to the directory number for B1, which is the PLAR destination. (In Cisco Unified Communications Manager Administration, choose Call Routing > Directory Number.)
Step 5 For phones that are running SIP, create a SIP dial rule. (In Cisco Unified Communications Manager Administration, choose Call Routing > Dial Rules > SIP Dial Rules. Choose 7940_7960_OTHER. Enter a name for the pattern; for example, PLAR1. Click Save; then, click Add Plar. Click Save.)
Step 6 For phones that are running SIP, assign the SIP dial rule configuration that you created for PLAR to the phones, which, in this example, are A and A'. (In Cisco Unified Communications Manager Administration, choose Device > Phone. Choose the SIP dial rule configuration from the SIP Dial Rules drop-down list box.)
GUI Changes
No new configuration settings display in Cisco Unified Communications Manager Administration for this feature.
Service Parameter and Enterprise Parameter Changes
For parameters that you configure for barge, refer to the "Barge and Privacy" chapter in the Cisco Unified Communications Manager Features and Services Guide and the "Party Entrance Tone" section.
Installation/Upgrade (Migration) Considerations
You can use this feature after you install or upgrade to Cisco Unified Communications Manager 7.1(2).
Serviceability Considerations
No special serviceability considerations exist for this feature.
BAT Considerations
No BAT considerations exist for this feature.
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
No AXL or CTI considerations exist for this feature.
User Tips
By pressing the Barge, cBarge, or Single Button Barge softkey in the remote in use call state, the initiator gets added to the call with all parties, and all parties receive a barge beep tone (if configured).
For a list of phones that support this feature, see the "Barge Tone Enhancements" section.
For More Information
•"Barge and Privacy," Cisco Unified Communications Manager Administration Guide
•Party Entrance Tone
•Barge Tone Enhancements
Calling Party Normalization Enhancements
Description
In Cisco Unified Communications Manager 7.1(2), the names of the Incoming Calling Party settings changed in the Device Pool, Gateway, and Trunk Configuration windows, as shown in Table 5. For information on how Cisco Unified Communications Manager 7.0(x) configuration works after an upgrade to Cisco Unified Communications Manager 7.1(2), see the "Installation/Upgrade (Migration) Considerations" section.
Table 5 Field Updates for Calling Party Normalization
Fields in Cisco Unified Communications Manager 7.0(x)
|
Fields in Cisco Unified Communications Manager 7.1(2)
|
Incoming Calling Party National Number Prefix—Allows you to configure prefixes and strip digits for the calling party number of National type.
|
National Number
•Prefix
•Strip Digits
•Use Device Pool CSS (new support in 7.1(2))
•Calling Search Space (new support in 7.1(2))
In Cisco Unified Communications Manager 7.1(2), you can assign incoming calling party transformation calling search spaces for various calling party number types (Subscriber, International, National, and Unknown). Configuring these calling search spaces in the device pool, for the gateway or for the trunk, allows the device to globalize the calling party number for the various calling party number types.
|
Incoming Calling Party International Number Prefix—Allows you to configure prefixes and strip digits for the calling party number of International type.
|
International Number
•Prefix
•Strip Digits
•Use Device Pool CSS (new support in 7.1(2))
•Calling Search Space (new support in 7.1(2))
|
Incoming Calling Party Subscriber Number Prefix—Allows you to configure prefixes and strip digits for the calling party number of Subscriber type.
|
Subscriber Number
•Prefix
•Strip Digits
•Use Device Pool CSS (new support in 7.1(2))
•Calling Search Space (new support in 7.1(2))
|
Incoming Calling Party Unknown Number Prefix—Allows you to configure prefixes and strip digits for the calling party number of National type.
|
Unknown Number
•Prefix
•Strip Digits
•Use Device Pool CSS (new support in 7.1(2))
•Calling Search Space (new support in 7.1(2))
|
Cisco Unified Communications Manager Administration Configuration Tips
This section contains information on the following topics:
•Considerations for Configuring the Prefix Field
•Considerations for Configuring the Strip Digits Field
Considerations for Configuring the Prefix Field
Before you configure the prefix fields, consider the following information.
•In the Device Pool, Gateways, and Trunk Configuration windows, to delete the prefixes in all incoming calling party settings at the same time, click Clear Prefix Settings; to enter the default value for all incoming calling party settings at the same time, click Default Prefix Settings.
•If the word, Default, displays in the Prefix field in the Gateway or Trunk Configuration window, you cannot configure the Strip Digits field in the Gateway or Trunk Configuration window. In this case, Cisco Unified Communications Manager takes the configuration for the Prefix and Strip Digits fields from the device pool that is applied to the device. If the word, Default, displays in the Prefix field in the Device Pool Configuration window, Cisco Unified Communications Manager applies the service parameter configuration for the incoming calling party prefix, which supports both the prefix and strip digit functionality.
•To configure the Strip Digits field in the Device Pool, Gateway, or Trunk Configuration window, you must leave the Prefix field blank or enter a valid configuration in the Prefix field. To configure the Strip Digits fields in these windows, do not enter the word, Default, in the Prefix field.
•When the prefix gets applied to the incoming calling party number on the device, Cisco Unified Communications Manager includes the prefix in the calling party number field for all additional actions, such as supplementary services, including call forwarding, call park, voice messaging, CDR data, and so on, that pertain to the call.
•If you configure a prefix but the calling party number that arrives is empty, Cisco Unified Communications Manager does not apply the prefix. (For example, the calling party number arrives empty because you chose Restricted from the Calling Line ID Presentation drop-down list box in the Route Pattern, Gateway, or Trunk Configuration windows.)
•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.
•Configure the incoming prefix fields in conjunction with the strip digit fields; that is, if your service provider prepends leading digits (for example, a zero) to the calling party number. For more information on stripping leading digits from the calling party number, see the "Considerations for Configuring the Strip Digits Field" section.
Considerations for Configuring the Strip Digits Field
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 configure the Strip Digits fields to ensure that Cisco Unified Communications Manager strips the leading digits before applying the prefixes to an incoming calling party number.
Before you configure the number of leading digits that Cisco Unified Communications Manager must strip from the calling party number, consider the following information.
•You can either strip digits by configuring the Incoming Prefix service parameters in the Service Parameters window or by configuring the Strip Digits fields in the Device Pool, Gateway, or Trunk Configuration windows. For information on how to configure the service parameters for this functionality, see the "Service Parameter and Enterprise Parameter Changes" section.
•If the word, Default, displays in the Prefix field in the Gateway or Trunk Configuration window, you cannot configure the Strip Digits field in the Gateway or Trunk Configuration window. In this case, Cisco Unified Communications Manager takes the configuration for the Prefix and Strip Digits fields from the device pool that is applied to the device. If the word, Default, displays in the Prefix field in the Device Pool Configuration window, Cisco Unified Communications Manager applies the service parameter configuration for the incoming calling party prefix, which supports both the prefix and strip digit functionality.
•To configure the Strip Digits field in the Device Pool, Gateway, or Trunk Configuration window, you must leave the Prefix field blank or enter a valid configuration in the Prefix field. To configure the Strip Digits fields in these windows, do not enter the word, Default, in the Prefix field.
•Be aware that Cisco Unified Communications Manager can strip up to 24 digits. If you enter a value that is larger than 24 in the field, for example, 26, Cisco Unified Communications Manager Administration does not allow the configuration.
•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.
•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 value for the Strip Digits fields, Cisco Unified Communications Manager does not strip any digits from the calling party number.
•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 settings in Table 5 display in the following windows in Cisco Unified Communications Manager Administration:
•Device Pool (System > Device Pool)—Applies the configuration to all digital gateways and trunks; that is, if you choose the device pool for the device.
•Gateway (Device > Gateway)—Displays settings in the H.323 gateway configuration window and in the port windows (Gateway Configuration window) for MGCP (T1-PRI/BRI) and MGCP (E1-PRI/BRI).
•Trunk (Device > Trunk)—Displays all settings in all trunk configuration windows except the SIP trunk.
Tip The SIP Trunk Configuration window only displays the Unknown Number settings.
For configuration procedures for each configuration window, refer to the following sections:
•Configuring a Device Pool, Cisco Unified Communications Manager Administration Guide
•Gateway Configuration, Cisco Unified Communications Manager Administration Guide
•Configuring a Trunk, Cisco Unified Communications Manager Administration Guide
Service Parameter and Enterprise Parameter Changes
No service or enterprise parameters changes occurred for this feature in 7.1(2).
Tip 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.
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 service parameters 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 service parameters, 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 service parameters 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 service parameters, Cisco Unified Communications Manager does not strip any digits from the calling party number; that is, unless you configure the Strip Digit fields that are listed in Table 5, which support the configuration at the device level.
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 service parameters, 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.
Tip If you configure the incoming fields that display in the device configuration windows and the service parameters, Cisco Unified Communications Manager uses the configuration that you configured in the device configuration window.
•Incoming Calling Party National Number Prefix - MGCP
•Incoming Calling Party International Number Prefix - MGCP
•Incoming Calling Party Subscriber Number Prefix - MGCP
•Incoming Calling Party Unknown Number Prefix - MGCP
Tip If you have a single H.323, MGCP (T1-PRI/BRI), or MGCP (E1-PRI/BRI) gateway in your network, you can configure the prefix service parameters, which support the Cisco CallManager service, for the particular gateway type in the Service Parameter Configuration window. If you configure the prefix service parameters for a particular gateway type, for example, H.323, be aware that all H.323 gateways that you configure in Cisco Unified Communications Manager Administration use the configuration from the service parameter unless you configure the prefix settings for a particular gateway in the Gateway Configuration window.
•Incoming Calling Party National Number Prefix - H.323
•Incoming Calling Party International Number Prefix - H.323
•Incoming Calling Party Subscriber Number Prefix - H.323
•Incoming Calling Party Unknown Number Prefix - H.323
Tip If the incoming prefix service parameters for H.323 use the same prefix as the incoming prefix service parameters for the phone, the prefix gets used twice for the calling party; first, when the incoming call gets to the gateway and again, when the call terminates at the phone.
•Incoming Calling Party Unknown Number Prefix - SIP
Installation/Upgrade (Migration) Considerations
If you upgrade from Cisco Unified Communications Manager 7.0(1) to 7.1(2), be aware that Cisco Unified Communications Manager moves the numbers of digits that you want stripped from the Incoming Prefix 7.0 fields in the Device Pool, Trunk, or Gateway Configuration windows to the Strip Digits fields in the same windows in Cisco Unified Communications Manager Administration 7.1(2). For example, if you configured :12 in the Incoming Calling Party International Number Prefix field in the Trunk Configuration window in 7.0(1), 12 displays in the Strip Digits field for the International Number in the Trunk Configuration window after you upgrade to 7.1(2).
If you configured the Incoming Prefix service parameters in 7.0(1) so Cisco Unified Communications Manager strips leading digits, Cisco Unified Communications Manager 7.1(2) does not change the configuration; that is, Cisco Unified Communications Manager 7.1(2) uses the value, including the : (colon), that you configured in 7.0(1).
Serviceability Considerations
This feature relies on the Cisco CallManager service, so make sure that this service is activated in Cisco Unified Serviceability.
Security Considerations
No security considerations exist for this feature.
AXL and CTI Considerations
See the "Enhancements to Calling Party Number Transformations" section.
User Tips
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
•"Calling Party Normalization" chapter, Cisco Unified Communications Manager Features and Services Guide
Cisco Unified Communications Manager Assistant Enhancements for Numeric User ID Login
Tip Cisco Unified Communications Manager Releases 7.1(2) and 6.1(3) introduce this feature.
Cisco Unified Communications Manager supports numeric user ID login for Cisco Unified Communications Manager Assistants from their Cisco Unified IP Phones.
To configure numeric user ID login, perform the following steps:
Procedure
Step 1 When you are adding a Cisco Unified Communications Manager Assistant user (in Cisco Unified Communications Manager Administration, go to User Management -> End User), assign a User ID that is numeric only.
Step 2 In Cisco Unified Communications Manager Administration, go to the Service Parameters window (System> Service Parameters); then, select your server and select the Cisco IP Manager Assistant service.
In the section "Clusterwide Parameters (Parameters that apply to all servers)" set Alpha Numeric UserID to False.
Step 3 Restart the Cisco IP Manager Assistant service for this configuration change to take effect.
Cisco Unified Communications Manager Attendant Console Support in 7.1(2)
If you are upgrading from a compatible Cisco CallManager 4.X release or a compatible Cisco Unified Communications Manager 5.X, 6.X, or 7.X release to Cisco Unified Communications Manager Release 7.1(2), 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.1(2).
Be aware, however, that Cisco no longer supports the Cisco Unified Communications Manager Attendant Console with new installations of Cisco Unified Communications Manager 7.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(x) plug-in from the Cisco software download site, you can use that plug-in with Cisco Unified Communications Manager 7.1(x) but only for upgrades of a compatible Cisco Unified Communications Manager 5.X, 6.X, or 7.X release to Cisco Unified Communications Manager Release 7.1(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.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.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
•Cisco Unified Communications Manager Attendant Console End of Life and End of Sale Announcement—http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps7046/ps7282/end_of_life_notice_c51-499091.html
•Cisco Unified Communications Manager Software Compatibility Matrix —For information on the versions of Cisco Unified Business Attendant Console, Cisco Unified Enterprise Attendant Console, or Cisco Unified Department Attendant Console that are compatible with Cisco Unified Communications Manager 7.1(2)
•http://www.cisco.com/en/US/products/ps7282/tsd_products_support_series_home.html
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 Communications Manager Attendant Console" chapter, Cisco Unified Communications Manager Features and Services Guide
Cisco Web Dialer Configured in Application Server Window
Tip Cisco Unified Communications Manager Releases 7.1(2) and 6.1(3) introduce this feature.
Description
In previous releases of Cisco Unified Communications Manager [except for 6.1(3)], the List of WebDialers field in the Service Parameter window supported a maximum of 255 characters, which limited the scalability of the Redirector. In Cisco Unified Communications Manager 7.1(2) and 6.1(3), you configure the WebDialer servers in the Application Server Configuration window instead of the Service Parameters Configuration window.
Cisco Unified Communications Manager Administration Configuration Tips and GUI Changes
You can add a Cisco Web Dialer application server through the Application Server Configuration window. You access the Application Server Configuration window by choosing System > Application Server in Cisco Unified Communications Manager Administration. Cisco Web Dialer displays as one of the options in the Application Server Type drop-down list box.
If you add a Cisco Web Dialer application server in the Application Server Configuration window, the server displays in the List of Web Dialers field in the Service Parameter Configuration window for the Cisco WebDialer Web Service.
Service Parameter and Enterprise Parameter Changes
In Cisco Unified Communications Manager 7.1(2), you can configure either the List of WebDialers service parameter or the Cisco Web Dialer application server through the Application Server Configuration window. If you add a Cisco Web Dialer application server in the Application Server Configuration window, the server displays in the List of WebDialers field in the Service Parameter Configuration window for the Cisco WebDialer Web Service. You can access the Service Parameter Configuration window by choosing System > Service Parameters in Cisco Unified Communications Manager Administration.
Installation/Upgrade (Migration) Considerations
If you install Cisco Unified Communications Manager 7.1(2) and plan to use Cisco Web Dialer, configure the Cisco Web Dialer application server in the Application Server Configuration window. You do not need to configure the List of WebDialers field in the Service Parameter Configuration window if you configure the application server in the Application Server Configuration window.
Serviceability Considerations
Cisco Web Dialer relies on the Cisco WebDialer Web Service. If you have not already done so, activate this service in the Service Activation window in Cisco Unified Serviceability.
BAT Considerations
No BAT considerations exist for this feature.
CAR/CDR Considerations
No CAR or CDR considerations exist for this feature.
Security Considerations
No security considerations exist for this feature.
User Tips
For user enhancements for Cisco Web Dialer, see the "Cisco Web Dialer Enhancements" section.
For More Information
•"Cisco Web Dialer" chapter, Cisco Unified Communications Manager Features and Services Guide
•Cisco Web Dialer Enhancements
G.Clear Codec Support on SIP Trunks
Cisco Unified Communications Manager supports limited early offer for G.Clear data calls (also known as clear channel). The Early Offer for G.Clear Calls feature provides support for third-party SIP user agents that can do early offer to negotiate data calls without using a Media Termination Point. MTPs do not support the G.Clear codec.
If you enable both Media Termination Point Required and Early Offer for G.Clear Calls for a SIP device, the system does not allocate the MTP if the G.Clear codec in present in the offer. The system only allocates the MTP if the call is not G.Clear, and the MTP is required.
The Early Offer for G.Clear Calls feature supports both standards-based G.Clear (CLEARMODE) and proprietary Cisco Session Description Protocols (SDP), including CCD, G.nX64, and X-CCD.
To enable or disable Early Offer for G.Clear Calls, navigate to the SIP Profile Configuration window in Cisco Unified Communications Manager Administration (Device Device Settings > SIP Profile) and choose one of the following options for the Early Offer for G.Clear Calls parameter:
•Disabled (default)
•CLEARMODE
•CCD
•G.nX64
•X-CCD
AXL and CTI Considerations
See the "Enhanced Clear Channel (G.clear) Support" section.
Geolocations, Geolocation Filters, and Location Conveyance
This section, which describes geolocations, geolocation filters, and location conveyance for Cisco Unified Communications Manager 7.1(2), contains information on the following topics:
•Description for Geolocations
–Geolocation Usage for Shared Lines and Route Lists
–Geolocation Examples
–Geolocation Identifiers
•Description for Geolocation Filters
–Geolocation Filter Examples
•Description for Location Conveyance
•Interactions for Location Conveyance
•Geolocation Configuration Tips
•Geolocation Filter Configuration Tips
•Location Conveyance Configuration Tips
•GUI Changes for Geolocations and Geolocation Filters
•Service Parameter and Enterprise Parameter Changes for Geolocations and Geolocation Filters
•Installation/Upgrade (Migration) Considerations for Geolocations and Geolocation Filters
•Serviceability and RTMT Considerations
•BAT Considerations
•CAR/CDR Considerations
•Security Considerations
•For More Information
Description for Geolocations
Geographical location information, or geolocation, describes a physical position in the world that may correspond to the past, present, or future location of a person, event, or device.
Cisco Unified Communications Manager Administration allows you to specify a geolocation for every device.
The Request for Comments (RFC) 4119 standard provides the basis for geolocations. Geolocations use the civic location format that specifies the following fields: country, A1, A2, A3, A4, A5, A6, PRD, POD, STS, HNO, HNS, LMK, LOC, FLR, NAM, and PC.
In Cisco Unified Communications Manager Administration, geolocations get configured manually.
Tip Do not confuse locations with geolocations. Locations, which you configure by using the System > Location menu option, allow you to define entities that a centralized call-processing system uses to provide call admission control (CAC). Geolocations, which you configure by using the System > Geolocation Configuration menu option, allow you to specify geographic locations that you use to associate Cisco Unified Communications Manager devices for features such as logical partitioning.
Configuration of geolocations entails provisioning the following elements:
•Configure geolocation identifiers
–You can define sets of geolocations (civic addresses).
–You can assign these geolocations to VoIP phones, VoIP gateways, IP trunks, device pools, and enterprise parameters.
–You can define geolocation filters that select a subset of fields from geolocation and associate with VoIP gateways, IP trunks, device pools, and enterprise parameters.
Cisco Unified Communications Manager administrators must define the following item:
•A geolocation for every device that participates in any feature that requires geolocations. The Request for Comments (RFC) 4119 standard provides the basis for geolocations. Geolocations use the civic location format that specifies the following fields: country, A1, A2, A3, A4, A5, A6, PRD, POD, STS, HNO, HNS, LMK, LOC, FLR, NAM, and PC. Geolocations get configured manually.
Cisco Unified Communications Manager administrators then assign geolocations to devices.
The following entities in a Cisco Unified Communications Manager cluster can have geolocation and geolocation filter values that are assigned:
•Device pools
•CTI route points
•Phones (optional)
•CTI ports
Note Phones do not specify a drop-down list box for associating a phone with a geolocation filter.
•SIP trunks
•Intercluster trunks (ICT)
•H.323 gateways
•MGCP ports of the following types: T1, E1, PRI, FXO
You do not need to associate media devices, such as media termination points (MTP), conference bridges (CFB), annunciators, and music on hold (MOH) servers, with geolocations.
Internally, the device layer of Cisco Unified Communications Manager associates with geolocation values that call processing uses. The following sequence takes place:
1. Devices read the GeolocationPkid and GeolocationFilterPkid for its configuration at device or device pool level.
2. The devices communicate this Pkid and deviceType information in CC (for example, CcRegisterPartyA) and PolicyAndRSVPRegisterReq messages during call signaling.
3. The intercluster trunk (ICT) or SIP trunk device layer that receives this information uses the information for location conveyance.
4. No communication of geolocation from Cisco Unified Communications Manager to a phone takes place.
The following logic determines the geolocation value:
1. Read the value for geolocation from the device window. If it is not configured in the device window, for phone device in roaming, read the device pool (DP) from the roaming configuration. For phone device that is not in roaming, read the DP from the device configuration.
2. For trunk, ICT, or MGCP port device, read the DP from the device configuration.
3. From the selected DP, read the value of geolocation from DP configuration window.
4. If DP is not configured with a value for Geolocation, use blank value.
5. If available geolocation value is blank, call processing uses the configured value that the Default Geolocation enterprise parameter specifies.
The standard record for a geolocation specifies Unspecified. Use this value when no geolocation needs to associate with a device. In such scenarios, any features that are based on geolocations do not execute. Also, devices for which no geolocation gets specified do not participate in geolocation information conveyance across clusters for intercluster calls.
Be aware that the Default Geolocation enterprise parameter can be configured from drop-down list boxes on the Enterprise Parameters Configuration window.
Geolocation Usage for Shared Lines and Route Lists
When the called party specifies a group device, a different geolocation can apply for each device in a group. For the early attended scenarios, you do not know the actual connected device until the device gets answered. Thus, the Geolocation information gets aggregated until the device answers.
•The Call Control and Feature layer receives temporary geolocation information ("MixedDevice") until the device answers.
•When a device answers, the actual geolocation information for the device becomes available and gets communicated to call control and to any features that are involved.
Geolocation Examples
Table 6 specifies examples of geolocations.
Table 6 Geolocation Examples
Geolocation Name
|
Geolocation Data
|
IN-KA-BLR-BLD1
|
(country=IN, A1=KA, A3=Bangalore, A4= A4, A5=12, A6=Langford Road, PRD=12, LOC=BLD1, NAM=unified comm, PC=560001)
|
IN-KA-BLR-BLD2
|
(country=IN, A1=KA, A3=Bangalore, A4= A4, A6=Outer Ring Road, LOC=BLD2, NAM=unified comm, PC=560002)
|
IN-MH-MUM-BLD1
|
(country=IN, A1=MH, A3=Mumbai, A4= A4, LOC=bld1, NAM=unified comm, PC=220001)
|
IN-KA-BLR-ICTtoSJ
|
(country=IN, A1=KA, A3=Bangalore, NAM=ICTToSJ)
|
Geolocation Identifiers
Geolocation identifiers get constructed from a combination of geolocations, geolocation filters, and device types of Cisco Unified Communications Manager devices.
Geolocation filters allow selection of specific fields from the 17 geolocation fields. Use the System > Geolocation Filter menu option in Cisco Unified Communications Manager Administration to configure geolocation filters manually. Specific Cisco Unified Communications Manager features associate the geolocation filters by using drop-down list boxes in the configuration windows of the devices that get configured for a particular feature.
The Cisco Unified Communications Manager device type of a device specifies one of the following values:
•Border—Use this value to specify accessing PSTN trunks, intercluster trunks (ICTs), gateways, and MGCP ports.
•Interior—Use this value for VoIP phones or internal endpoints.
Refer to Table 21 in the "Logical Partitioning" section for a detailed listing of the Cisco Unified Communications Manager devices that associate with the Border and Interior device types.
The following object specifies an example geolocation identifier:
{geolocPkid=9dc76052-3a37-78c2-639a-1c02e8f5d3a2, filterPkid=d5bdda76-6a86-56c5-b5fd-6dff82b37493, geolocVal=, devType=8}
where:
The geolocVal field gets used in cases where the Cisco Unified Communications Manager database does not reference the geolocation record but data for a geolocation comes from another source (for example, location conveyance PIDF-LO XML from a remote cluster).
In such cases, Cisco Unified Communications Manager constructs the name value pair for the geolocation fields.
Example: "country=US:A1=Texas:A3=Richardson:LOC=Building 6" where the value gets communicated through the geolocVal field.
Note In such a case, the geolocPkid gets kept null, and call control or features access the geolocVal field from a geolocation identifier.
The following string specifies the logical representation of a geolocation identifier:
"Border:country=US:A1=Texas:A3=Richardson:LOC=Building 6"
Note This geolocation identifier gets constructed from the member fields of a geolocation identifier.
Description for Geolocation Filters
Cisco Unified Communications Manager administrators define the following item:
•A geolocation filter for every device that participates in a feature that uses geolocation filters. Filters allow selection of specific fields from the 17 geolocation fields for the purpose of creating an identifier from the selected fields. Geolocation filters get configured manually.
Cisco Unified Communications Manager administrators then assign geolocation filters to devices.
The following logic determines the geolocation filter value:
1. For phone device that is in roaming, read the geolocation filter value from DP in roaming configuration. For phone device that is not in roaming, read the geolocation filter value from DP in device configuration.
2. For trunk, intercluster trunk, or MGCP port device, read geolocation filter value from device window. If no value is configured, read from DP.
3. If DP is not configured with a geolocation filter value, use blank value.
4. If available filter is blank, call processing uses the value that the Default Geolocation Filter enterprise parameter specifies.
Geolocation Filter Examples
Table 7 specifies examples of geolocation filters.
Table 7 Geolocation Filter Examples
Geolocation Name
|
Geolocation Filter Data
|
India-Filter1
|
(UseCountry, UseA1, UseA3, UseLOC)
|
India-GW-Filter2
|
(UseCountry, UseA1, UseA3, UseLOC, UseNAM)
|
India-ICT-Trunk-Filter3
|
(UseCountry, UseA1, UseA3, UseNAM)
|
Description for Location Conveyance
Location conveyance involves configuration to make the following behavior possible:
•Communicate geolocation information across clusters
–Allow communication of geolocation information from one cluster to another, at call establishment as well as midcall joins and redirects.
Note Enterprise parameters and logical partitioning configuration do not control location conveyance. If a device that communicates through a trunk associates with geolocation information, check the Send Geolocation Information check box when you configure the trunk (either SIP or ICT) to convey the geolocation information across clusters.
For the logical partitioning feature, the Cisco Unified Communications Manager does not send the configured geolocation information to line devices (phones that are running SIP or SCCP).
Interactions for Location Conveyance
The location conveyance feature interacts as follows:
•Geolocation conveyance across SIP trunks and intercluster trunks
•SIP trunk error handling for geolocation information
•Intercluster trunk error handling for geolocation information
•Handling a received geolocation
•Feature interactions with midcall geolocation change
Geolocation Configuration Tips
Use the System > Geolocation Configuration menu option in Cisco Unified Communications Manager Administration to configure geolocations.
Table 8 provides a checklist for configuring geolocations.
Table 8 Geolocation Configuration Checklist
Configuration Steps
|
Procedures and Related Topics
|
Step 1
|
Define a set of geolocations on a new Geolocation Configuration window.
|
Geolocation Configuration
|
Step 2
|
Assign geolocations to device pools, devices, trunks, gateways, or MGCP ports.
|
Device Pool Configuration Settings, Cisco Unified Communications Manager Administration Guide
Gateway Configuration Settings, Cisco Unified Communications Manager Administration Guide
Displaying the MAC Address of a Phone, Cisco Unified Communications Manager Administration Guide
Trunk Configuration Settings, Cisco Unified Communications Manager Administration Guide
|
Step 3
|
Assign geolocations to the default geolocation that the Default Geolocation enterprise parameter specifies.
|
Geolocation Configuration
Enterprise Parameters Configuration, Cisco Unified Communications Manager Administration Guide
Enterprise Parameters for Logical Partitioning
|
Step 4
|
For devices that do not participate in features that require geolocations, define the geolocation as Unspecified or leave undefined.
Note You can define this lack of association at the individual-device level, the device-pool level, or the enterprise-parameter level.
|
Device Pool Configuration Settings, Cisco Unified Communications Manager Administration Guide
Gateway Configuration Settings, Cisco Unified Communications Manager Administration Guide
Displaying the MAC Address of a Phone, Cisco Unified Communications Manager Administration Guide
Trunk Configuration Settings, Cisco Unified Communications Manager Administration Guide
Enterprise Parameters Configuration, Cisco Unified Communications Manager Administration Guide
|
Geolocation Filter Configuration Tips
Use the System > Geolocation Filter menu option in Cisco Unified Communications Manager Administration to configure geolocation filters.
Table 9 provides a checklist for configuring geolocation filters.
Table 9 Geolocation Configuration Checklist
Configuration Steps
|
Procedures and Related Topics
|
Step 1
|
Define a set of filter rules in a new Geolocation Filter Configuration window.
|
Geolocation Filter Configuration
|
Step 2
|
Assign geolocation filters to device pools, trunks, intercluster trunks, gateways, or MGCP ports.
|
Device Pool Configuration Settings, Cisco Unified Communications Manager Administration Guide
Gateway Configuration Settings, Cisco Unified Communications Manager Administration Guide
Trunk Configuration Settings, Cisco Unified Communications Manager Administration Guide
|
Step 3
|
For the logical partitioning feature, assign geolocation filter to the default filter that the Logical Partitioning Default Filter enterprise parameter specifies.
|
Enterprise Parameters Configuration, Cisco Unified Communications Manager Administration Guide
Enterprise Parameters for Logical Partitioning
|
Location Conveyance Configuration Tips
Table 10 provides a checklist for configuring location conveyance in a multicluster logical partitioning environment.
Table 10 Location Conveyance Configuration Checklist
Configuration Steps
|
Procedures and Related Topics
|
Step 1
|
Define a set of geolocations in a new Geolocation Configuration window.
|
Geolocation Configuration
|
Step 2
|
Assign geolocations to device pools, devices, SIP trunks, intercluster trunks, gateways, or MGCP ports for the devices that need to participate in location conveyance.
|
Device Pool Configuration Settings, Cisco Unified Communications Manager Administration Guide
Gateway Configuration Settings, Cisco Unified Communications Manager Administration Guide
Displaying the MAC Address of a Phone, Cisco Unified Communications Manager Administration Guide
Trunk Configuration Settings, Cisco Unified Communications Manager Administration Guide
|
Step 3
|
Assign geolocations to a default geolocation that the Default Geolocation enterprise parameter specifies.
This assignment allows you to specify a default geolocation for a cluster.
For devices for which no associated geolocation exists at the device or device-pool level, the value that is specified by the Default Geolocation enterprise parameter applies.
|
Geolocation Configuration
Enterprise Parameters Configuration, Cisco Unified Communications Manager Administration Guide
Enterprise Parameters for Logical Partitioning
|
Step 4
|
If geolocation information about devices needs to be communicated across clusters, ensure that location conveyance is configured.
To do so, check the Send Geolocation Information check box in the intercluster trunk (ICT) or SIP trunk for the devices that need to pass geolocation information across clusters as follows:
•Check the Send Geolocation Information check box in the intercluster trunk (ICT) or SIP trunk of the local cluster.
•Check the Send Geolocation Information check box in the ICT or SIP trunk of the remote cluster.
|
Trunk Configuration Settings, Cisco Unified Communications Manager Administration Guide
|
GUI Changes for Geolocations and Geolocation Filters
Use the following new menu options in Cisco Unified Communications Manager Administration to configure the geolocations and geolocation filters:
•System > Geolocation Configuration
•System > Geolocation Filter
The following existing Cisco Unified Communications Manager Administration windows contain new fields for configuring geolocations and geolocation filters:
•Device Pool Configuration—pane: Geolocation Configuration, fields: Geolocation, Geolocation Filter
•CTI Route Point Configuration—field: Geolocation
•Gateway Configuration—pane: Geolocation Configuration; fields: Geolocation, Geolocation Filter
•Cisco Unified IP Phone Configuration— field: Geolocation
•Trunk Configuration—pane: Geolocation Configuration, fields: Geolocation, Geolocation Filter, Send Geolocation Information
Service Parameter and Enterprise Parameter Changes for Geolocations and Geolocation Filters
The following new enterprise parameter affects the configuration of geolocations:
•Default Geolocation
Installation/Upgrade (Migration) Considerations for Geolocations and Geolocation Filters
The following migration considerations that affect the dial plan exist for geolocations and geolocation filters when you are migrating from releases of Cisco Unified Communications Manager that are earlier than Release 7.1(2):
•If the Enable Logical Partitioning enterprise parameter is set to True, ensure geolocations and geolocation filters are configured for the following entities:
–Device pools for all phones
–MGCP ports that access the PSTN
–H.323 gateways that access the PSTN
–Intercluster trunks (ICTs, either gatekeeper-controlled or non-gatekeeper-controlled) to remote clusters
–SIP trunks that access the PSTN or remote clusters
•Ensure that location conveyance is turned on in all clusters to allow end-to-end communication of geolocation information.
To do so, check the Send Geolocation check box on intercluster trunks (ICTs) and SIP trunks.
During upgrade of Cisco Unified Communications Manager Release 7.1(x) or later from an earlier release, the following values get assigned for the entities that associate with configuration of geolocations and geolocation filters:
•Geolocation
–No configured geolocation records exists in the geolocation table.
–Default Geolocation enterprise parameter specifies Unspecified.
–Device pools specify Geolocation value None.
–Devices specify Geolocation value Default.
•Geolocation filter
–No configured geolocation filter records exist in geolocation filter table.
–Logical Partitioning Default Filter enterprise parameter specifies None.
–Device pools specify Geolocation Filter value None.
–Devices specify Geolocation Filter value None.
Serviceability and RTMT Considerations
No serviceability nor RTMT considerations exist for geolocations, geolocation filters, or location conveyance.
BAT Considerations
The Cisco Bulk Administration Tool specifies several new menu items to support geolocations. See the "Support for Geolocations and Logical Partitioning" section for details.
CAR/CDR Considerations
No CAR/CDR considerations exist for geolocations, geolocation filters, or location conveyance.
Security Considerations
No security considerations exist for geolocations, geolocation filters, or location conveyance.
For More Information
•Geolocations and Location Conveyance, Cisco Unified Communications Manager Features and Services Guide
•Logical Partitioning, Cisco Unified Communications Manager Features and Services Guide
•Device Pool Configuration, Cisco Unified Communications Manager Administration Guide
•Enterprise Parameters Configuration, Cisco Unified Communications Manager Administration Guide
•CTI Route Point Configuration, Cisco Unified Communications Manager Administration Guide
•Gateway Configuration, Cisco Unified Communications Manager Administration Guide
•Cisco Unified IP Phone Configuration, Cisco Unified Communications Manager Administration Guide
•Trunk Configuration, Cisco Unified Communications Manager Administration Guide
•Cisco Unified Communications Manager Administration Guide
•Cisco Unified Communications Manager System Guide
•Cisco Unified Serviceability Administration Guide
•Cisco Unified Communications Manager Call Detail Records Administration Guide
•Cisco Unified Real-Time Monitoring Tool Administration Guide
•Cisco Unified Reporting Administration Guide
•Cisco Unified Communications Manager Bulk Administration Guide
•Cisco Unified Communications Solution Reference Network Design (SRND) for Cisco Unified Communications Manager
•Cisco Unified Communications Manager Security Guide
•Cisco Unified Communications Manager Assistant User Guide
H.235—Pass-Through Support
Consider the following:
During a call that employs H.235 encryption, do not invoke mid-call features such as call transfer or hold/resume operations. If you do, the call may become unencrypted.
Cisco Unified Communications Manager does not support H.235 encryption when a media termination point or transcoder gets inserted into a call. If this occurs, the call will become unencrypted.
H.329—Extended Video Channel Support
The extended video channels feature works via H.239 protocol and enables multiple video channel support. Cisco Unified Communications Manager supports negotiating an extended video channel by using the H.239 protocol in direct point-to-point H.323 calls. This also includes calls across the H.323 intercluster trunk.
Cisco Unified Communications Manager supports all H.239 associated support signals and commands that are specified in the H.239 recommendation.
The following characteristics apply to the extended video channels feature:
•Support for Third-Party H.323 Devices
•H.323 Devices Invoke Presentation Feature
•Opening Second Video Channels
•Call Admission Control (CAC) on Second Video Channels
•Number of Video Channels Allowed
•H.239 Commands and Indication Messages
•Topology and Protocol Interoperability Limitation
•Mid-Call feature Limitation
Support for Third-Party H.323 Devices
The extended video channel feature supports H.239 interoperability among third-party video endpoints and Cisco Unified Voice Conferencing. Cisco Unified Communications Manager allows an extended video channel to be used for presentation and live meeting transmission. This feature focuses on multiple video channel support via H.245 signaling. The following presentation applications provide basis for this multichannel support:
•Natural Presenter package by the third-party vendor Tandberg
•People + Content by the third-party vendor Polycom
Both Natural Presenter package and People + Content use the H.239 protocol to negotiate capabilities and define the roles of the additional video channels.
Note Natural Presenter package by Tandberg and People + Content by Polycom only support H.239 for the presentation mode.
Note Be aware that the presentation applications that are offered by Tandberg and Polycom are optional features. You must have one of these options and H.239 enabled in both caller and callee endpoints to negotiate second video channels, or the call will get limited to a single video channel.
H.323 Devices Invoke Presentation Feature
Tandberg and Polycom terminals allow the user to share presentation materials from various components (for example, VCR, Projector, PC, and so on). The components can physically connect with the terminals, and the PC can also run presentation applications that are provided by the vendor to transmit the presentation image. Be aware that the source of presentation and the component connection with the terminal are irrelevant to the mechanism of establishing video channels by using H.239.
Note For details on setting up presentation sources, refer to the video terminal user guide.
When two H.239-enabled terminals attempt to establish a video call, they declare their video capabilities for the main video channel for meeting participants and their extended video capabilities (H.239 capabilities) for the second video channel. The following contents comprise H.239 capability signals:
1. The terminals send signals to indicate that the devices support H.239. They also send associated commands and indication signals for managing the second video channel. This enables both the terminals to be aware that the call is capable of opening multiple video channels.
2. The terminal sends out one or more extended video codec capabilities to express video codec capabilities for second channels. The terminal must specify the role of the second video channel. The defined role labels can be
–Live-video—This channel gets processed normally and is suitable for live video of people.
–Presentation—This channel relays a token-managed presentation that is distributed to the devices.
After the capabilities have been exchanged, both terminals immediately open two-way audio channels and the main video channels as in the traditional video calls.
Opening Second Video Channels
Depending on the third-party terminal implementation, the second video channel gets handled differently among vendors.
Natural Presenter Package by Tandberg
Tandberg initiates the second video channel on demand. A Tandberg device does not open the second video channel immediately after the main video channel is established. The second channel gets opened when one of the callers (the presenter) specifies the source of the presentation and invokes a command to start the presentation.
When a Tandberg user decides to start sharing the presentation, Tandberg requests the other call party to open an extended video channel for receiving the presentation image; therefore, a Tandberg-Tandberg call has only one-way second video channel.
People + Content by Polycom
Unlike Tandberg, a Polycom terminal initiates the second video channel immediately as a part of the default mechanism, after both parties have confirmed that additional video channels can get supported.
Note The channel gets established automatically if both parties support H.239 and have the extended video channel feature enabled; however, the additional channel does not show anything until one of the parties starts to share presentation.
Polycom initiates a request for the second video channel to the other call party regardless of the usage of the second video channel; therefore, in a Polycom-Polycom call, two-way video channels get opened between the devices even if only one of them sends out presentation image/video.
This implementation ensures that both call parties have the second video channel ready for transmission when the call parties decide to take the token to present something. Although one of the two video channels remains idle (not sending anything), the Polycom device controls bandwidth to ensure load efficiency.
Note This difference in handling second video channels does not affect the implementation of H.239. Cisco Unified Communications Manager does not initiate any receiving channel request in an H.323-H.323 call. Cisco Unified Communications Manager simply relays all channel requests from one terminal to another.
Note Cisco Unified Communications Manager does not enforce two-way transmission for the second set of video channels because this does not represent a requirement in the H.239 protocol.
Call Admission Control (CAC) on Second Video Channels
The following call admission control policies of Cisco Unified Communications Manager get applied to the second video channels:
Cisco Unified Communications Manager restricts the bandwidth usage by the second video channels on the basis of location configuration. When the second video channel is being established, Cisco Unified Communications Manager makes sure that enough video bandwidth stays available within the location pool and reserves bandwidth accordingly. If the required bandwidth is not available, Cisco Unified Communications Manager instructs the channel to reduce the available bandwidth to zero.
No change occurs in the region configuration or policies to support the second video channels.
Traditionally, Cisco Unified Communications Manager region policy only supported a call with a single video channel, and the total bandwidth usage of this call never gets larger than what the region configuration specifies.
If the administrator sets a finite region video bandwidth restriction for an H.239 call, Cisco Unified Communications Manager will violate the region policy because the region value will get used against the bandwidth that is requested for each video channel independently.
Example:
If the region video bandwidth is set to 384Kbps and the audio channel uses 64Kb/s, the
maximum allowed bandwidth for each video channel will be (384Kb/s - 64Kb/s)= 320Kb/s.
i.e. the maximum bandwidth to be used by the H.239 call will be (audio bw + 2*(384 - audio
bw)) = 704Kb/s, which goes beyond the 384Kb/s bandwidth that the region specifies.
Note You should consider relaxing both region and location bandwidth restrictions for H.239 calls, so the H.239 devices are allowed to readjust and balance load for both the video channels without Cisco Unified Communications Manager intervention.
Number of Video Channels Allowed
Cisco Unified Communications Manager 7.1(2) supports only a maximum of two video channels due to the following reasons:
•Both Tandberg and Polycom only support two video channels, one of which is for main video, and the other is for presentation.
•H.239 only defines an Additional Media Channel (AMC) for H.320-based system to partition the traditional H.320 video channel for the purpose of presentation.
H.239 Commands and Indication Messages
Command and Indication (C&I) messages get used for H.239 to manage tokens for the Presentation and Live roles and to permit devices to request release of video flow control to enable the operation of additional media channels. Cisco Unified Communications Manager supports all the C & I messages. Whenever Cisco Unified Communications Manager receives C&I messages, it relays them to the call party accordingly.
Be aware that the flow control release request and response messages can be used to request that the far end release flow control, so it allows an endpoint to send the indicated channel at the indicated bit rate.
Note Be aware that the call party may or may not honor the request as is indicated by flow control release response.
The Presentation role token messages allow an H.239 device to acquire the token for presentation. The other call party may accept or reject the request. The presenter device sends out a token release message when it is no longer needed.
Topology and Protocol Interoperability Limitation
Cisco Unified Communications Manager 7.1(2) supports only H.239 in H.323 to H.323 calls. Cisco Unified Communications Manager allows H.239 calls to be established across H.323 intercluster trunk or multiple nodes. If an H.239-enabled device attempts to make a call with a non-H323 end, the H.239 capabilities will get ignore, and the call will get conducted like the traditional video calls that supported Cisco Unified Communications Manager supports.
Cisco Unified Communications Manager does not support a second video channel when a media termination point or transcoder is inserted into the call. If it happens, the call will fall back to normal video calls.
Mid-Call feature Limitation
Cisco Unified Communications Manager supports opening second video channels only in direct H.323 to H.323 calls.
Caution Do not attempt to invoke any mid-call features such as call transfer or hold/resume operations. Doing so can lead to problems, and the second video channel can get disconnected.
Internet Protocol Version 6 (IPv6)
This section, which describes IPv6 support for Cisco Unified Communications Manager 7.1(2), contains information on the following topics:
•Description for IPv6 Support
•Interactions and Restrictions for IPv6
•IPv6 Configuration Tips
•Running IPv6 CLI Commands or Configuring IPv6 in the Ethernet IPv6 Window
•Cisco Unified Communications Manager Administration IPv6 GUI Changes
•Service Parameter and Enterprise Parameter Changes for IPv6
•Installation/Upgrade (Migration) Considerations for IPv6
•Serviceability and RTMT Considerations for IPv6
•CAR/CDR Considerations for IPv6
•Security Considerations for IPv6
•Supported Phone Models for IPv6
•Phone Considerations
•For More Information
Description for IPv6 Support
Internet Protocol version 6 (IPv6), which is the latest version of the Internet Protocol (IP) that uses packets to exchange data, voice, and video traffic over digital networks, increases the number of network address bits from 32 bits in IPv4 to 128 bits. IPv6 support in the Cisco Unified Communications Manager network allows the network to behave transparently in a dual-stack environment and provides additional IP address space and autoconfiguration capabilities to devices that are connected to the network.
The "Internet Protocol Version 6 (IPv6)" chapter in the Cisco Unified Communications Manager Features and Services Guide contains descriptive information on the following topics:
•Cisco Unified Communications Manager and IPv6
•Cisco Unified IP Phones and IPv6
•DHCPv6 and IPv6
•DNS and IPv6
•Gateways and IPv6
•Media Termination Points and IPv6
•SIP Trunks and IPv6
•TFTP Server and IPv6
Tip Before you configure IPv6, review the "Internet Protocol Version 6 (IPv6)" chapter carefully. For example, this chapter describes how to configure the Cisco Unified Communications Manager server and phones in dual-stack mode. It also describes how Cisco Unified Communications Manager uses MTPs to translate IPv4 to IPv6 (or vice versa) and so on.
Interactions and Restrictions for IPv6
Some Cisco Unified Communications Manager features do not work for devices with an IP Addressing Mode of IPv6 Only. Before you configure IPv6 Only for a device, review the following section, which describes Cisco Unified Communications Manager feature interactions and restrictions for IPv6.
•Annunciator—Annunciator supports IPv4; if annunciator connects to a device with an IP Addressing Mode of IPv6 Only, Cisco Unified Communications Manager inserts an MTP that can translate IPv4 to IPv6. If no MTP that can translate IP address versions is available, no announcement plays on the phone.
•Call Detail Records—See the "CAR/CDR Considerations for IPv6" section.
•Cisco Certificate Authority Proxy Function—See the "Security Considerations for IPv6" section.
•Cisco Extension Mobility—Cisco Extension Mobility supports IPv4, so you cannot use phones with an IP Addressing Mode of IPv6 Only for Cisco Extension Mobility. If you want to use Cisco Extension Mobility with the phone, make sure that you configure the phone with an IP Addressing Mode of IPv4 Only or IPv4 and IPv6.
•Cisco Unified Communications Operating System—See the "Running IPv6 CLI Commands or Configuring IPv6 in the Ethernet IPv6 Window" section.
•Cisco Unified Serviceability— See the "Serviceability and RTMT Considerations for IPv6" section.
•Cisco Unity Connection and Cisco Unity—Cisco Unity Connection and Cisco Unity communicate with Cisco Unified Communications Manager by using IPv4.
•Cisco Unified Communications Manager Assistant—Cisco Unified Communications Manager Assistant does not support IPv6, so you cannot use phones with an IP Addressing Mode of IPv6 Only with Cisco Unified Communications Manager Assistant. If you want to use Cisco Unified Communications Manager Assistant with the phone, make sure that you configure the phone with an IP Addressing Mode of IPv4 Only or IPv4 and IPv6.
•Cisco Unified Real-Time Monitoring Tool—See the "Serviceability and RTMT Considerations for IPv6" section.
•Cisco Web Dialer—Cisco Web Dialer supports IPv4, so, to connect to CTI Manager, Cisco Web Dialer uses an IPv4 address. Cisco Web Dialer works with devices with an IP Addressing Mode of IPv4 and IPv6.
•Conferences—Cisco Unified Communications Manager uses IPv4 for conferences, even if the conference bridge uses IPv6. During a conference, Cisco Unified Communications Manager inserts one MTP that can translate IPv4 to IPv6 for each device with an IP Addressing Mode of IPv6 Only, so each phone that uses an IPv6 address can join the conference.
For your MTP device to support security, you must configure the MTP in passthru mode, which means that the MTP does not transform the packets during the call. When you configure an MTP in passthru mode, the MTP gets the encrypted packet on one call leg and sends out the same packet on a different leg of the call. For secure conferences with secure conference bridges and encrypted devices with an IP Addressing Mode of IPv6 Only, Cisco Unified Communications Manager inserts an MTP into the conference to translate IPv4 to IPv6 (and vice versa) when some devices in the conference support IPv4. If you configure the MTP for passthru mode, the encrypted IPv6 phones communicate with the conference bridge via SRTP. If you do not configure the MTP for passthru mode, the media gets downgraded to RTP.
•Device Mobility—Device mobility supports IPv4 addresses only, so you cannot use phones with an IP Addressing Mode of IPv6 Only with device mobility.
•Differentiated Services Control Point (DSCP)—Be aware that Differentiated Services Control Point (DSCP) values are the same for both IPv6 and IPv4.
•H.323 Devices—H.323 clients, gateways, and H.225 intercluster trunks do not support IPv6. To communicate with IPv6 Only devices that connect to these gateways, Cisco Unified Communications Manager inserts an MTP that can translate IPv4 to IPv6 during a call.
•Intercom—Intercom can support phones with an IP Addressing Mode of IPv4 Only or IPv4 and IPv6. During an intercom call, the talkback mode establishes media streams with the same IP version as the media stream that is used when the caller initiated intercom.
•Mobile Connect and Mobile Voice Access—Cisco Unified Mobility features in Cisco Unified Communications Manager, such as Mobile Connect and Mobile Voice Access, support IPv4. On a call, when a mobile phone uses IPv4 and another phone uses IPv6, Cisco Unified Communications Manager inserts an MTP that can translate IPv4 to IPv6 into the call.
•Monitoring and Recording—For monitoring and recording, the phone can handle an IPv4 media stream for customer-to-agent calls while it handles an IPv6 media stream for recording and monitoring (or vice versa).
•Music On Hold—The IP Voice Media Streaming Application supports IPv4. Cisco Unified Communications Manager does not support IPv6 with multicast music on hold, so devices with an IP Addressing Mode of IPv6 Only cannot support multicast music on hold. Under these circumstances, Cisco Unified Communications Manager plays a tone, instead of music, when the phone is on hold. For IPv6 Only devices that uses unicast music on hold, Cisco Unified Communications Manager inserts an MTP that can translate IPv4 to IPv6 (or vice versa) into the media stream.
•QRT—The Quality Report Tool supports IPv6 if the device uses an IP Addressing Mode of IPv4 Only or IPv4 and IPv6 (dual-stack mode); users with phones with an IP Addressing Mode of IPv6 Only cannot report audio and other problems by pressing the QRT softkey on the phone. In addition, the QRT report does not include the streaming statistics for a phone that has an IP Addressing Mode of IPv6 Only.
•RSVP—If you deploy RSVP as the call admission control mechanism in your network, do not deploy IPv6. The RSVP feature does not support IPv6. RSVP calls support IPv4. If RSVP is required for the call and any device in the call is configured for or uses an IPv6 address, Cisco Unified Communications Manager rejects the call, and the caller receives a busy tone.
•SDL—SDL TCP connections support IPv6, but SDL links support IPv4. If you configure a host name in the Server Configuration window in Cisco Unified Communications Manager Administration, SDL queries the DNS A record, which ensures that IPv4 is used. If you specify an IP address, an IPv4 address gets passed down to the SDL layer.
•SIP Phones and TFTP—Phones that run SIP do not support IPv6 addresses. If you configure IPv6 Only as the IP Addressing Mode for a phone that runs SIP, the Cisco TFTP service overrides the IP Addressing Mode configuration and uses IPv4 Only in the configuration file.
•T.38 Fax—Whether a T.38 fax call uses IPv4 or IPv6 depends on the preference of Cisco Unified Communications Manager and the capabilities of the devices in the call. If one device in the call uses IPv6 and the other device can use IPv4 and IPv6, the call uses IPv6, regardless of the configuration for the signaling and media enterprise parameters in Cisco Unified Communications Manager Administration.
Cisco Unified Communications Manager supports the following types of T.38 fax calls:
–SIP-to-SIP call that uses IPv6
–SIP-to-SIP call that uses IPv4
–SIP-to-non-SIP call that uses IPv4
–SIP-to-non-SIP call where the SIP device uses IPv6 and the non-SIP device uses IPv4 with an MTP that can translate IP address versions
During the middle of a T.38 fax call, Cisco Unified Communications Manager does not insert an MTP that converts the IP version types; the MTP must already exist in the call.
•Transfer—The transfer components in Cisco Unified Communications Manager uses the IP Addressing Mode and the IP address of the device to determine how to handle the transfer. If the IP capabilities do not match when you transfer a call, Cisco Unified Communications Manager allocates an MTP that can translate IP version, so the transfer can occur.
•Web Browser on the Phone—On the Cisco Unified IP Phone, the HTTP interface for the web browser supports IPv4 addresses, so the phone does not allow web access to servers that use an IPv6 address.
•Video—Cisco Unified Communications Manager supports video IPv6 calls in the following cases:
–Cisco Unified Video Advantage does not support IPv6, so, when the media preference is IPv6, video uses IPv4.
–The audio and video portions of a call negotiate the same IP type for the initial call; that is, if two dual-stack phones are in a call that uses both audio and video, the call uses IPv4 for both the audio and video portions of the initial call, even when the media preference is IPv6.
–If two dual-stack phones negotiate IPv6 for the audio call based on the media preference and then you add video mid-call, the video portion of the call uses IPv4, even if the media preference is IPv6.
–MTPs do not get allocated for video support. For example, a call occurs between two dual-stack phones over a SIP trunk with an IP Addressing Mode of IPv6 Only; IPv6 gets negotiated for the audio portion of the call, and video cannot occur because the video device does not support IPv6. No MTP gets allocated to support the video portion of the call.
IPv6 Configuration Tips
Table 11 displays the configuration checklist for IPv6, which is documented in the "Internet Protocol Version 6 (IPv6)" chapter in the Cisco Unified Communications Manager Features and Services Guide. Before you configure IPv6 in your network, review Table 11.
Table 11 IPv6 Configuration Checklist
Configuration Steps
|
Related Procedures and Topics
|
Step 5
|
Before you configure IPv6, review all IPv6-related documentation.
|
For example, review the following documents:
•Deploying IPv6 in Unified Communications Networks with Cisco Unified Communications Manager 7.1(x)
•Cisco IOS IPv6 Configuration Library
•Implementing VoIP for IPv6
•"Internet Protocol Version 6 (IPv6)" chapter, Cisco Unified Communications Manager Features and Services Guide
|
Step 6
|
Make sure that you have compatible network hardware and Cisco IOS software that is installed and configured; for example, configure your gateways and Cisco IOS MTP for IPv6.
|
•Implementing VoIP for IPv6
•"Internet Protocol Version 6 (IPv6)" chapter, Cisco Unified Communications Manager Features and Services Guide
|
Step 7
|
Provision a local IPv6-capable DNS and DHCP server.
Caution You can provision your DNS server for IPv6 prior to upgrading from Cisco Unified Communications Manager Release 7.0(1) to Release 7.1(2). However, do not configure the DNS records for Cisco Unified Communications Manager for IPv6 until after you upgrade to Release 7.1(2). Configuring the DNS records for Cisco Unified Communications Manager for IPv6 prior to upgrading to Release 7.1(2) causes the upgrade to fail and causes your system to become nonfunctional after you reboot.
Tip Cisco recommends that the Cisco Unified Communications Manager server use a static non-link-local IPv6 address. If the Cisco Unified Communications Manager server obtains the IPv6 address from the DHCPv6 server or via stateless address autoconfiguration, ensure that the Cisco Unified Communications Manager server only obtains one non-link-local IPv6 address from the DHCPv6 server.
|
Refer to the documentation that supports your DNS and DHCP server(s); for example, Cisco Network Registrar User's Guide, 6.2.
|
Step 8
|
Install Cisco Unified Communications Manager 7.1 (or upgrade to this release).
Before you install subsequent nodes (subscribers) in the cluster, add the IPv4 server information to the Server Configuration window in Cisco Unified Communications Manager Administration.
Caution You can provision your DNS server for IPv6 prior to upgrading from Cisco Unified Communications Manager Release 7.0(1) to Release 7.1(2). However, do not configure the DNS records for Cisco Unified Communications Manager for IPv6 until after you upgrade to Release 7.1(2). Configuring the DNS records for Cisco Unified Communications Manager for IPv6 prior to upgrading to Release 7.1(2) causes the upgrade to fail and causes your system to become nonfunctional after you reboot.
|
•Cisco Unified Communications Manager installation or upgrade 7.1 documentation
•Configuring a Server, Cisco Unified Communications Manager Administration Guide
|
Step 9
|
Enable IPv6 in the Cisco Unified Communications Operating System and ensure that the Cisco Unified Communications Manager server obtains an IPv6 address.
Cisco recommends that the Cisco Unified Communications Manager server use a static non-link-local IPv6 address.
Tip For each server in the cluster, perform these tasks. Performing these tasks requires a reboot of the server.
|
"Internet Protocol Version 6 (IPv6)" chapter, Cisco Unified Communications Manager Features and Services Guide
Running IPv6 CLI Commands or Configuring IPv6 in the Ethernet IPv6 Window
|
Step 10
|
In the Enterprise Parameters Configuration window in Cisco Unified Communications Manager Administration, choose True for the Enable IPv6 enterprise parameter.
Tip After you update this enterprise parameter, restart the Cisco CallManager, CTIManager and the Certificate Authority Proxy Function services in Cisco Unified Serviceability.
|
"Internet Protocol Version 6 (IPv6)" chapter, Cisco Unified Communications Manager Features and Services Guide
Service Parameter and Enterprise Parameter Changes for IPv6
|
Step 11
|
For the server that you are configuring in Cisco Unified Communications Manager Administration, choose System > Server and enter the non-link-local IPv6 address or a host name that can resolve to a IPv6 address in the IPv6 Name field.
Tip For each server in the cluster, perform this task.
Tip Remember to update the DNS server with the appropriate Cisco Unified Communications Manager name and address information.
Caution You can provision your DNS server for IPv6 prior to upgrading from Cisco Unified Communications Manager Release 7.0(1) to Release 7.1(2). However, do not configure the DNS records for IPv6 for Cisco Unified Communications Manager until after you upgrade to Release 7.1(2). Configuring the DNS records for IPv6 for Cisco Unified Communications Manager prior to upgrading to Release 7.1(2) causes the upgrade to fail and causes your system to become nonfunctional after you reboot.
To display the non-link-local IPv6 address, you can run a CLI command or view it in the Ethernet IPv6 window, as described in the "Running IPv6 CLI Commands or Configuring IPv6 in the Ethernet IPv6 Window" section.
|
•"Internet Protocol Version 6 (IPv6)" chapter, Cisco Unified Communications Manager Features and Services Guide
•Cisco Unified Communications Manager Administration IPv6 GUI Changes
|
Step 12
|
In Cisco Unified Communications Manager Administration, configure phone-related and SIP trunk-related IPv6 settings.
For example, configure the IP Addressing Mode and Allow Auto-Configuration of Phones settings in the Common Device Profile Configuration window; then, apply the common device profile configuration to the phone or SIP trunk.
|
•"Internet Protocol Version 6 (IPv6)" chapter, Cisco Unified Communications Manager Features and Services Guide
•Cisco Unified Communications Manager Administration IPv6 GUI Changes
|
Step 13
|
Restart the Cisco CallManager, CTIManager, and Cisco Certificate Authority Proxy services in Cisco Unified Serviceability.
|
Cisco Unified Serviceability Administration Guide
|
Running IPv6 CLI Commands or Configuring IPv6 in the Ethernet IPv6 Window
To enable IPv6 in the Cisco Unified Communications Operating System and to ensure that the Cisco Unified Communications Manager server gets an IPv6 address, you must perform one of the following tasks:
•Run the IPv6 CLI commands in the command line interface.
•Enable IPv6 and configure the IPv6 address in the Ethernet IPv6 window in the Cisco Unified Communications Operating System.
Caution Before you set the Enable IPv6 enterprise parameter to True in Cisco Unified Communications Manager Administration, perform the following procedure. If you set the enterprise parameter to True before you enable IPv6 in the Cisco Unified Communications Operating System, the Cisco CallManager service runs in IPv4, and phones that have IP Addressing Mode of IPv6 Only cannot register with Cisco Unified Communications Manager.
Table 12 provides a description of the Ethernet IPv6 configuration settings and the equivalent CLI commands that support the graphical user interface (GUI) options.
Step 1 In Cisco Unified Communications Operating System, choose Settings > IP > Ethernet IPv6.
The Ethernet IPv6 Configuration window displays.
Step 2 To modify the Ethernet settings, enter the values in the appropriate fields. For a description of the fields on the Ethernet IPv6 Configuration window, see Table 12.
Step 3 Check the Update with Reboot check box. For the IPv6 settings in this window to take effect, you must reboot the server.
Step 4 Click Save. The server reboots immediately after you click Save.
Step 5 Perform this procedure for each server in the cluster.
Table 12 IPv6 CLI Commands and Ethernet IPv6 Configuration Settings
Configuration Setting in Ethernet IPv6 Window
|
Equivalent CLI Command
|
Description
|
Enable IPv6 check box
|
set network ipv6 service enable
|
These settings enable IPv6 in the Cisco Unified Communications Operating System.
Caution For IPv6 to work, you must either check the Ethernet IPv6 check box or issue the equivalent CLI command. You must perform this task before you set the Enable IPv6 enterprise parameter to True.
|
Router Advertisement radio button
|
Not applicable
|
If you want to use stateless address autoconfiguration to obtain a non-link-local IPv6 address for the Cisco Unified Communications Manager server, click the Router Advertisement radio button.
Click this radio button if you do not plan to configure a static non-link-local IPv6 address for the Cisco Unified Communications Manager server or if you do not want DHCPv6 server to issue a non-link-local IPv6 address to the server.
Ensure that the Cisco Unified Communications Manager server only obtains one non-link-local IPv6 address. If the server has more than one IPv6 address, Cisco Unified Communications Manager may not behave as expected.
If the Cisco Unified Communications Manager server obtains an IPv6 address via stateless address autoconfiguration and you also have a static IPv6 address that is configured for the server, Cisco Unified Communications Manager ignores the IPv6 address that is obtained via stateless address autoconfiguration and uses the static address.
|
DHCP radio button
|
set network ipv6 dhcp enable
|
If you want the DHCPv6 server to issue a non-link-local IPv6 address to the Cisco Unified Communications Manager server, click the DHCP radio button or issue the equivalent CLI command.
Ensure that the Cisco Unified Communications Manager server only obtains one non-link-local IPv6 address. If the server has more than one IPv6 address, Cisco Unified Communications Manager may not behave as expected.
|
Manual Entry radio button, IPv6 Address, Subnet Mask
|
set network ipv6 static_address <addr> <mask>
|
These Ethernet IPv6 settings and equivalent CLI command allow you to configure a static IPv6 address for the Cisco Unified Communications Manager server.
Configuring a static non-link-local IPv6 address assumes that you do not want the Cisco Unified Communications Manager server to get the IPv6 address from the DHCPv6 server or via stateless address autoconfiguration.
|
IPv6 Address
|
show network ipv6 settings
|
These settings allow you to view the IPv6 address for the Cisco Unified Communications Manager server.
|
Tip If you decide to run the CLI commands that are described in Table 12 instead of configure the Ethernet IPv6 settings in the Cisco Unified Communications Operating System, you must reboot the server for the changes to take effect. For information on how to run CLI commands and for other IPv6 CLI commands, refer to the Command Line Interface Reference Guide for Cisco Unified Solutions.
Cisco Unified Communications Manager Administration IPv6 GUI Changes
After you configure the phone in Cisco Unified Communications Manager Administration, you can view the IP address for the phone in the Find and List Phones window. For phones that have an IPv4 address only or both IPv4 and IPv6 addresses, the IPv4 address displays in the window. For phones with an IPv6 address only, the IP Address displays as 0.0.0.0 in the IP Address column in the Find and List Phones window. To identify the IPv6 address for the phone, click the Device Name link in the Find and List Phones window, which causes the Phone Configuration window to display. For the IPv6 Only device, the Phone Configuration window displays an IPv4 address of 0.0.0.0, listed as IP Address, above the IPv6 address.
Table 13 describes the IPv6 and IPv4 settings that are in Cisco Unified Communications Manager Administration. For some IPv6 settings in Table 13, equivalent settings for IPv4 display in Cisco Unified Communications Manager Administration; for example, in the SIP Trunk Configuration window, you can configure either the Destination Address IPv6 setting or the Destination Address setting, or both settings, depending on the IP support in your network.
For related configuration procedures, refer to the following sections:
•Service Parameter and Enterprise Parameter Changes for IPv6
•Configuring a Server, Cisco Unified Communications Manager Administration Guide
•Configuring a SIP Route Pattern, Cisco Unified Communications Manager Administration Guide
•Configuring a Common Device Configuration, Cisco Unified Communications Manager Administration Guide
•Configuring a Trunk, Cisco Unified Communications Manager Administration Guide
Table 13 IPv6 Settings in Cisco Unified Communications Manager Administration
Configuration Setting
|
Description
|
System > Server
|
Host Name/IP Address
|
This field supports IPv4. If your network uses DNS that can map to IPv4 addresses, you can enter the host name of the Cisco Unified Communications Manager server. Otherwise, you must enter the full IPv4 address of the server.
Tip If your network supports IPv6 (or IPv4 and IPv6), configure the IPv6 Name field in addition to the Host Name/IP Address field.
|
IPv6 Name
|
This field supports IPv6. If your network uses DNS that can map to IPv6 addresses, you can enter the host name of the Cisco Unified Communications Manager server. Otherwise, enter the non-link-local IP address of the Cisco Unified Communications Manager server; for information on how to obtain the non-link local IP address, see the "Running IPv6 CLI Commands or Configuring IPv6 in the Ethernet IPv6 Window" section.
Phones that run SCCP use this field, which gets included in the TFTP configuration file, to retrieve the IPv6 address of the Cisco Unified Communications Manager server, so phone registration occurs.
Tip You can provision your DNS server for IPv6 prior to upgrading from Cisco Unified Communications Manager Release 7.0(1) to Release 7.1(2). However, do not configure the DNS records for Cisco Unified Communications Manager for IPv6 until after you upgrade to Release 7.1(2). Configuring the DNS records for Cisco Unified Communications Manager for IPv6 prior to upgrading to Release 7.1(2) causes the upgrade to fail and causes your system to become nonfunctional after you reboot.
Tip In addition to configuring the IPv6 Name field, you must configure the Host Name/IP Address field, so Cisco Unified Communications Manager can support features/devices that use IPv4 (or IPv4 and IPv6).
|
Call Routing > SIP Route Patterns
|
IPv4 Pattern
|
Enter the domain, sub-domain, IPv4 address or IP subnetwork address.
Tip For the IP subnetwork address, in Classless Inter-Domain Routing (CIDR) notation, enter X.X.X.X/Y, where Y equals the network prefix that denotes the number of bits in the address that will be the network address.
Tip If the SIP trunk supports IPv6 or both IPv4 and IPv6 (dual-stack mode), configure the IPv6 Pattern in addition to the IPv4 pattern.
|
IPv6 Pattern
|
Cisco Unified Communications Manager uses SIP route patterns to route or block both internal and external calls. The IPv6 address in this field provides the basis for routing internal and external calls to SIP trunks that support IPv6.
Tip If the SIP trunk supports both IPv4 and IPv6, configure the IPv4 Pattern in addition to the IPv6 Pattern.
|
Device > Device Settings > Common Device Configuration
|
IP Addressing Mode
|
Choose the version of IP address that the device (SIP trunk or phone that runs SCCP) uses to connect to Cisco Unified Communications Manager. From the drop-down list box, choose one of the following options:
•IPv4 Only—For both media and signaling events, the device uses an IPv4 address to connect to Cisco Unified Communications Manager. If an IPv4 address is not available for the device, the call fails.
If you choose this option, the phone releases an IPv6 address. If you choose this option, the SIP trunk uses an IPv4 address to connect to the peer device.
•IPv6 Only—For both media and signaling events, the device uses an IPv6 address to connect to Cisco Unified Communications Manager. If an IPv6 address is not available for the device, the call fails.
If you choose this option, the phone releases an IPv4 address. If you choose this option, the SIP trunk uses an IPv6 address to connect to the peer device.
Phones that run SIP do not support IPv6, so do not choose this option for these phones. If you configure IPv6 Only as the IP Addressing Mode for phones that run SIP, the Cisco TFTP service overrides the IP Addressing Mode configuration and uses IPv4 Only in the configuration file.
•IPv4 and IPv6 (Default)—Choose this option for dual-stack devices, which can have both an IPv4 and IPv6 address. For both media and signaling events, the dual-stack device uses either an IPv4 or an IPv6 address to connect to Cisco Unified Communications Manager.
If only an IPv4 or IPv6 is available for a device (not both types of IP addresses), the device uses the available IP address to negotiate the call. If the device has both IP address types for both signaling and media events, Cisco Unified Communications Manager uses the configuration for IP Addressing Mode Preference for Signaling setting for signaling events and the IP Addressing Mode Preference for Media enterprise parameter for media events.
|
IP Addressing Mode Preference for Signaling
|
For dual-stack phones, which support both IPv4 and IPv6 addresses, choose the version of IP address that the phone prefers to establish a connection to Cisco Unified Communications Manager during a signaling event. For dual-stack SIP trunks, choose the version of IP address that the SIP trunk uses to connect to the peer device for signaling events.
From the drop-down list box, choose one of the following options:
•IPv4—The dual-stack device prefers to establish a connection via an IPv4 address during a signaling event.
•IPv6—The dual-stack device prefers to establish a connection via an IPv6 address during a signaling event.
•Use System Default—The configuration for the enterprise parameter, IP Addressing Mode Preference for Signaling, applies.
|
Allow Auto-Configuration for Phones
|
This drop-down list box supports IPv6 for dual-stack Cisco Unified IP Phones that run SCCP. From the drop-down list box, choose one of the following options:
•On—Depending on how the M bit is set via stateless address autoconfiguration on the router, the phone can use the IPv6 Network ID that is advertised in the Router Advertisements (RAs) to autoconfigure its IPv6 address.
Phones also require a TFTP server address to register with Cisco Unified Communications Manager. You can manually configure the TFTP server address via the interface on the phone, or you can obtain it from a DHCPv6 server.
Tip To indicate to the phone that it needs to use the DHCPv6 server to obtain other information, ensure that the O bit is set via stateless address autoconfiguration on the router.
•Off—The phone obtains its IPv6 address and TFTP server address from the DHCPv6 server.
•Default—To use the configuration for the Allow Auto-Configuration for Phones enterprise parameter, choose this option.
Although Cisco Unified Communications Manager does not use this configuration, the TFTP file that the phone obtains includes this information.
|
Device > SIP Trunk
|
Destination Address
|
The Destination Address, which supports IPv4, represents the remote SIP peer with which this trunk will communicate. The allowed values for this field specify a valid V4 dotted IP address, fully qualified domain name (FQDN), or DNS SRV record only if the Destination Address is an SRV check box is checked.
SIP trunks only accept incoming requests from the configured Destination Address and the specified incoming port that is specified in the SIP Trunk Security Profile that is associated with this trunk.
If the remote end is a Cisco Unified Communications Manager cluster, DNS SRV represents the recommended choice for this field. The DNS SRV record should include all Cisco Unified Communications Managers within the cluster.
Tip For SIP trunks that can support IPv6 or IPv6 and IPv4 (dual-stack mode), configure the Destination Address IPv6 field in addition to the Destination Address field.
|
Destination Address IPv6
|
The Destination IPv6 Address represents the remote SIP peer with which this trunk will communicate. Enter one for the following values in the field:
•A valid IPv6 address (global unicast, unique local, or a host name)
•A fully qualified domain name (FQDN)
•A DNS SRV record, but only if you check the Destination Address is an SRV check box.
SIP trunks only accept incoming requests from the configured Destination IPv6 Address and the specified incoming port that is specified in the SIP Trunk Security Profile that is associated with this trunk.
If the remote end is a Cisco Unified Communications Manager cluster, consider entering the DNS SRV record in this field. The DNS SRV record should include all Cisco Unified Communications Managers within the cluster.
Tip For SIP trunks that run in dual-stack mode or that support an IP Addressing Mode of IPv6 Only, configure this field. If the SIP trunk runs in dual-stack mode, you must also configure the Destination Address field.
|
Device > Device Settings > SIP Profile
|
Enable ANAT
|
This option allows a dual-stack SIP trunk to offer both IPv4 and IPv6 media.
When you check both the Enable ANAT and the Media Termination Point Required check boxes, Cisco Unified Communications Manager inserts a dual-stack MTP and sends out an offer with two m-lines, one for IPv4 and another for IPv6. If a dual- stack MTP cannot be allocated, Cisco Unified Communications Manager sends an INVITE without SDP.
When you check the Enable ANAT check box and the Media Termination Point Required check box is unchecked, Cisco Unified Communications Manager sends an INVITE without SDP.
When both the Enable ANAT and Media Termination Point Required check boxes display as unchecked (or when an MTP cannot be allocated), Cisco Unified Communications Manager sends an INVITE without SDP.
When you uncheck the Enable ANAT check box but you check the Media Termination Point Required check box, consider the information, which assumes that an MTP can be allocated:
•Cisco Unified Communications Manager sends an IPv4 address in the SDP for SIP trunks with an IP Addressing Mode of IPv4 Only.
•Cisco Unified Communications Manager sends an IPv6 address in the SDP for SIP trunks with an IP Addressing Mode of IPv6 Only.
•For dual-stack SIP trunks, Cisco Unified Communications Manager determines which IP address type to send in the SDP based on the configuration for the IP Addressing Mode Preference for Media enterprise parameter.
|
Service Parameter and Enterprise Parameter Changes for IPv6
Table 14 describes the enterprise and service parameters that you can configure for IPv6. To configure enterprise parameters in Cisco Unified Communications Manager Administration, choose System > Enterprise Parameters. To configure service parameters in Cisco Unified Communications Manager Administration, choose System > Service Parameters.
Tip For a step-by-step procedure on how to configure enterprise parameters, refer to the "Enterprise Parameters Configuration" chapter in the Cisco Unified Communications Manager Administration Guide. For a step-by-step procedure on how to configure service parameters, refer to the "Service Parameters Configuration" chapter in the Cisco Unified Communications Manager Administration Guide.
Table 14 Enterprise and Service Parameters for IPv6
Parameter
|
Description
|
Enable IPv6
|
This enterprise parameter specifies whether Cisco Unified Communications Manager can negotiate calls by using IPv6 and whether phone can advertise an IPv6 address. Before you set this parameter to True, make sure that you enabled IPv6 in the Cisco Unified Communications Operating System on all servers in the cluster.
Setting this parameter to True causes the Cisco CallManager service to run in dual-stack mode, which is required for interacting with devices that support IPv6.
The default value equals False, which means that Cisco Unified Communications Manager cannot negotiate calls by using IPv6 and phones cannot advertise an IPv6 address.
After you update this enterprise parameter, restart the Cisco CallManager, CTIManager, and the Certificate Authority Proxy Function services in Cisco Unified Serviceability.
|
IP Addressing Mode Preference for Media
|
This enterprise parameter, which applies only to dual-stack devices, specifies the addressing mode that Cisco Unified Communications Manager uses for media events when both IPv4 and IPv6 addresses are available from each device on the call. The default value equals Prefer IPv4.
|
IP Addressing Mode Preference for Signaling
|
This enterprise parameter, which applies only to dual-stack devices, specifies how the dual-stack phone connects to Cisco Unified Communications Manager for signaling events and how the dual-stack SIP trunk connects to the peer device for signaling events.
The default value equals Prefer IPv4.
|
Allow Auto-Configuration for Phones
|
This parameter determines whether the phone is allowed to obtain an address through stateless autoconfiguration. Valid values specify On (the phone obtains its address as specified by the router advertisements, which may be stateless or stateful, depending on the router configuration) or Off (the phone always uses DHCPv6 to obtain its IPv6 address).
|
Call Counting CAC Enabled
|
This service parameter, which supports the Cisco CallManager service, determines whether Cisco Unified Communications Manager uses call counting as part of the locations-based call admission control (CAC) feature. Call counting uses a fixed bandwidth value to reserve and adjust bandwidth per call, regardless of the codec or media payload or the Internet Protocol Version (IPv6 or IPv4) that is used for each call. Call counting may potentially oversubscribe or undersubscribe bandwidth because a fixed-value bandwidth gets reserved per call no matter what the actual bandwidth is for the call. Cisco recommends you leave this parameter set to the default value of False (disabled) unless your network requires the call counting feature. To enable call counting for CAC, choose True for the parameter; to disable call counting for CAC, choose False.
This service parameter applies to IPv4 and IPv6 calls.
|
Audio Bandwidth For Call Counting CAC
|
This service parameter, which supports the Cisco CallManager service, specifies the amount of bandwidth to deduct from the available bandwidth for audio calls after you set the Call Counting CAC Enabled parameter to True. For each audio call, the amount of bandwidth that you enter in this field gets deducted, regardless whether more or less bandwidth is actually used for the call.
This service parameter applies to IPv4 and IPv6 calls.
|
Video Bandwidth For Call Counting CAC
|
This service parameter, which supports the Cisco CallManager service, specifies the units of bandwidth to deduct from the available bandwidth for video calls after you set the Call Counting CAC Enabled parameter to True. For each video call, the available bandwidth gets reduced by the number of units that are required to account for the actual bandwidth usage. For example, if you specify 512 kb/s as the bandwidth unit in this parameter, and a video call utilizes 384 kb/s, then one unit, 512 kb/s, gets deducted from available bandwidth. Likewise, if you specify 512 kb/s in this parameter and a video call negotiated 768 kb/s, then two units of bandwidth (1064 kb/s) get deducted from the available bandwidth.
This service parameter applies to IPv4 and IPv6 calls.
|
Alternate Cisco File Server(s)
|
These service parameters, which support the Cisco TFTP service, allow you to configure alternate Cisco file servers, which are TFTP servers that are on a different cluster. These parameters, which support either IPv4 or IPv6 addresses or host names that resolve to an IP address, determine the IP stack that the TFTP uses to communicate between primary and alternate file servers. If an alternate file server supports dual-stack mode and you want to set both IPv4 and IPv6 addresses for the same server in these parameter fields, you must add both IP addresses, one per field, and the TFTP server tries each address in the order that you configure.
|
Installation/Upgrade (Migration) Considerations for IPv6
Cisco Unified Communications Manager supports IPv6 after you install 7.1(2) or upgrade to 7.1(2).
Caution You can provision your DNS server for IPv6 prior to upgrading from Cisco Unified Communications Manager Release 7.0(1) to Release 7.1(2). However, do not configure the DNS records for Cisco Unified Communications Manager for IPv6 until after you upgrade to Release 7.1(2). Configuring the DNS records for Cisco Unified Communications Manager for IPv6 prior to upgrading to Release 7.1(2) causes the upgrade to fail and causes your system to become nonfunctional after you reboot.
For additional considerations, see Table 11.
Serviceability and RTMT Considerations for IPv6
Alarms that report IPv4 addresses may also report IPv6 addresses, depending on the configuration in your network. For information on how to configure alarms and view alarm definitions in Cisco Unified Serviceability, refer to the Cisco Unified Serviceability Administration Guide. The following alarms may provide IPv6 information.
•kCtiProviderOpenFailure (Updated)
–The alarm indicates that the CTI application failed to open provider. If your network supports IPv6, this alarm may contain an IPv6 address.
–Alarm Catalog—Choose CallManager > CtiManagerAlarmCatalog.
–Severity—Error (3)
–New Parameter—IPV6Address(String)
•kCtiProviderClosed (Updated)
–The alarm indicates that the CTI application connection is closed. If your network supports IPv6, this alarm may contain an IPv6 address.
–Alarm Catalog—Choose CallManager > CtiManagerAlarmCatalog.
–Severity—Informational (6)
–New Parameter—IPV6Address(String)
•kCtiProviderOpened (Updated)
–The alarm indicates that the CTI application connection opened. If your network supports IPv6, this alarm may contain an IPv6 address.
–Alarm Catalog—Choose CallManager > CtiManagerAlarmCatalog.
–Severity—Informational (6)
–New Parameter—IPV6Address(String)
•kCtiIncompatibleProtocolVersion (Updated)
–The alarm indicates that the JTAPI/TAPI application version is not compatible with this version of CTIManager. If your network supports IPv6, this alarm may contain an IPv6 address.
–Alarm Catalog—Choose CallManager > CtiManagerAlarmCatalog.
–Severity—Error (3)
–New Parameter—IPV6Address(String)
•DeviceRegistered (Updated)
–A device successfully registered with Cisco Unified Communications Manager.
–Alarm Definition Catalog—Choose CallManager Alarm Catalog > CallManager.
–Severity—Informational (6)
–New Parameters—IPV6Address[Optional].[String], IPAddressAttributes[Optional].[Enum], IPV6AddressAttributes [Optional].[Enum], ActiveLoadId [Optional].[String]
–New Enum Definitions for IPAddrAttributes: 0—Unknown; 1—Administrative only; 2—Signal only; 3—Administrative and signal
–New Enum Definitions for IPV6AddrAttributes: 0—Unknown; 1—Administrative only; 2—Signal only; 3—Administrative and signal
•DeviceUnregistered (Updated)
–A device that was previously registered with Cisco Unified Communications Manager has unregistered. This event may get issued as part of normal unregistration event or due to some other reason such as loss of keepalives. In cases of normal unregistration, if the Reason Code is CallManagerReset, CallManagerRestart, or DeviceInitiatedReset, the alarm severity gets lowered to Informational (6).
–Alarm Definition Catalog—Choose CallManager Alarm Catalog > CallManager.
–Severity—Error (3)
–New Parameters—IPV6Address [Optional].[String], IPAddressAttributes [Optional].[Enum], IPV6AddressAttributes [Optional].[Enum]
–New Enum Definitions for IPAddrAttributes: 0—Unknown; 1—AdministrativeOnly; 2—SignalOnly; 3—AdministrativeAndSignal
–New Enum Definitions for IPV6AddrAttributes: 0—Unknown; 1—Administrative only; 2—Signal only; 3—Administrative and signal
•DeviceTransientConnection (Updated)
–A transient connection attempt occurred. A connection got established and immediately dropped before completing registration. Incomplete registration may indicate a device is rehoming in the middle of registration. The alarm could also indicate a device misconfiguration, database error, or an illegal/unknown device trying to attempt a connection.
–Alarm Definition Catalog—CallManager Alarm Catalog > CallManager
–Severity—Error (3)
–New Parameters—IPV6Address [Optional].[String], IPAddressAttributes [Optional].[Enum], IPV6AddressAttributes [Optional].[Enum]
–Enum Definitions for IPAddrAttributes: 0—Unknown; 1—AdministrativeOnly; 2—SignalOnly; 3—AdministrativeAndSignal
–Enum Definitions for IPV6AddrAttributes: 0—Unknown; 1—AdministrativeOnly; 2—SignalOnly; 3—AdministrativeAndSignal
SNMP supports IPv4, although the CISCO-CCM-MIB includes columns and storage for IPv6 addresses, preferences, and so on.
With Release 7.1(2), the CTI InetAddress ccmCTIDeviceInetAddressType and ccmCTIDeviceInetAddress fields get deprecated. Two new IPv4/IPv6 fields get added to improve the SNMP query performance when a huge number of entries exist in the table.
The new fields that are added to the ccmCTIDeviceTable in CISCO-CCM-MIB comprise ccmCTIDeviceInetAddressIPv4 and ccmCTIDeviceInetAddressIPv6.The definitions follow:
ccmCTIDeviceInetAddressIPv4 OBJECT-TYPE
SYNTAX InetAddressIPv4
MAX-ACCESS read-only
STATUS current
DESCRIPTION—This object identifies the last known primary IPv4 address of the CTI device. This object contains value zero if IPV4 address is not available.
::= { ccmCTIDeviceEntry 14 }
ccmCTIDeviceInetAddressIPv6 OBJECT-TYPE
SYNTAX InetAddressIPv6
MAX-ACCESS read-only
STATUS current
DESCRIPTION—This object identifies the last known primary IPv6 address of the CTI device. This object contains value zero if IPV6 address is not available.
::= { ccmCTIDeviceEntry 15 }
With these changes, the ccmCTIDeviceEntry looks like the following example:
CcmCTIDeviceEntry ::= SEQUENCE {
ccmCTIDeviceIndex CcmIndex,
ccmCTIDeviceName SnmpAdminString,
ccmCTIDeviceType INTEGER ,
ccmCTIDeviceDescription SnmpAdminString,
ccmCTIDeviceStatus CcmDeviceStatus,
ccmCTIDevicePoolIndex CcmIndexOrZero,
ccmCTIDeviceInetAddressType InetAddressType,
ccmCTIDeviceInetAddress InetAddress,
ccmCTIDeviceAppInfo SnmpAdminString,
ccmCTIDeviceStatusReason CcmDevFailCauseCode,
ccmCTIDeviceTimeLastStatusUpdt DateAndTime,
ccmCTIDeviceTimeLastRegistered DateAndTime,
ccmCTIDeviceProductTypeIndex CcmIndexOrZero,
ccmCTIDeviceInetAddressIPv4 InetAddressIPv4,
ccmCTIDeviceInetAddressIPv6 InetAddressIPv6
}
In RTMT, you can search for and monitor CTI applications, CTI devices, and CTI lines that use IPv6 addresses. When you search for the application, device, or line, enter the IPv6 address and check the AppIpv6Addr check box in the attribute window.
In addition, you can perform a device search for phones or SIP trunks that use IPv6 addresses. When you choose CallManager > Device Search > Open Device Search > Phones (or SIP Trunks), make sure that you specify an IPv6 address and check the IPv6Address check box in the attributes window.
Tip IP Subnet does not apply for IPv6 search criteria.
Log files may display IPv4 and IPv6 addresses, depending on the configuration in your network.
CAR/CDR Considerations for IPv6
Cisco Unified Communications Manager 7.1(2) supports the new IPv6-related CDR fields in Table 15.
Table 15 IPv6 CDR Field Descriptions
Field Name
|
Range of Values
|
Description
|
origIpv4v6Addr
|
Text string
|
This field comprises an alphanumeric string of up to 64 characters.
This field identifies the IP address of the device that originates the call signalling. The field represents either IPv4 or IPv6 format depending on the type of IP address that gets used for the call.
For Cisco Unified IP Phones, this field specifies the address of the Cisco Unified IP Phone. For PSTN calls, this field specifies the address of the gateway. For intercluster calls, this field specifies the address of the remote Cisco Unified Communications Manager.
The IP address displays either in dotted decimal format or in colon-separated hexadecimal format.
Default - This field represents the IP address of the originating device as reported by the device or used for the call after media negotiation.
|
destIpv4v6Addr
|
Text string
|
This field comprises an alphanumeric string of up to 64 characters.
This field identifies the IP address of the device that terminates the call signalling. The field can represent either IPv4 or IPv6 format depending on the type of IP address that gets used for the call.
For Cisco Unified IP Phones, this field specifies the address of the Cisco Unified IP Phone. For PSTN calls, this field specifies the address of the gateway. For intercluster calls, this field specifies the address of the remote Cisco Unified Communications Manager.
The IP address displays either in dotted decimal format or in colon-separated hexadecimal format.
Default - Empty String "" or null represents the default. If the destination does not get reached, this field stays empty.
|
Security Considerations for IPv6
CAPF can issue and upgrade certificates to a phone that uses an IPv4, an IPv6, or both types of addresses. Table 16 describes how a phone that has an IPv4, IPv6, or both types of addresses connects to CAPF.
Table 16 How IPv6 or IPv4 Phone Connects to CAPF
IP Mode of Phone
|
IP Addresses on Phone
|
CAPF IP Address
|
How Phone Connects to CAPF
|
Dual-stack
|
IPv4 and IPv6 available
|
IPv4, IPv6
|
Phone uses an IPv6 address to connect to CAPF; if the phone cannot connect via an IPv6 address, it attempts to connect by using an IPv4 address.
|
Dual-stack
|
IPv4
|
IPv4, IPv6
|
Phone uses an IPv4 address to connect to CAPF.
|
Dual-stack
|
IPv6
|
IPv4, IPv6
|
Phone uses an IPv6 address to connect to CAPF. If the attempt fails, the phone uses an IPv4 address to connect to CAPF.
|
Dual-stack
|
IPv4
|
IPv4
|
Phone uses an IPv4 address to connect to CAPF.
|
Dual-stack
|
IPv4 and IPv6 available
|
IPv6
|
Phone uses and IPv6 address to connect to CAPF.
|
Dual-stack
|
IPv4 and IPv6 available
|
IPv4
|
Phone uses an IPv4 address to connect to CAPF.
|
Dual-stack
|
IPv4
|
IPv6
|
Phone cannot connect to CAPF.
|
Dual-stack
|
IPv6
|
IPv4
|
Phone cannot connect to CAPF.
|
Dual-stack
|
IPv6
|
IPv6
|
Phone uses an IPv6 address to connect to CAPF.
|
IPv4
|
IPv4
|
IPv4, IPv6
|
Phone uses an IPv4 address to connect to CAPF.
|
IPv6
|
IPv6
|
IPv4, IPv6
|
Phone uses an IPv6 address to connect to CAPF.
|
IPv4
|
IPv4
|
IPv4
|
Phone uses an IPv4 address to connect to CAPF.
|
IPv4
|
IPv4
|
IPv6
|
Phone cannot connect to CAPF.
|
IPv6
|
IPv6
|
IPv6
|
Phone uses an IPv6 address to connect to CAPF.
|
IPv6
|
IPv6
|
IPv4
|
Phone cannot connect to CAPF.
|
AXL and CTI Considerations
See the following sections:
•IPv6 Support
•IPv6 Support
•IPv6 Support
•IPv6 Support
Supported Phone Models for IPv6
The following Cisco Unified IP Phones that run SCCP support IPv6:
•Cisco Unified IP Phone 7975G
•Cisco Unified IP Phone 7971G-GE
•Cisco Unified IP Phone 7970G
•Cisco Unified IP Phone 7965G
•Cisco Unified IP Phone 7962G
•Cisco Unified IP Phone 7961G
•Cisco Unified IP Phone 7961G-GE
•Cisco Unified IP Phone 7945G
•Cisco Unified IP Phone 7942G
•Cisco Unified IP Phone 7941G
•Cisco Unified IP Phone 7941G-GE
•Cisco Unified IP Phone 7931G
•Cisco Unified IP Phone 7911G
•Cisco Unified IP Phone 7906G
Phone Considerations
The Cisco Unified IP Phone uses the internet protocol to provide voice communication over the network. Previous to Cisco Unified Communications Manager Release 7.1(x), only the internet protocol version 4 (IPv4) got supported. Because it uses a 32-bit address, IPv4 cannot meet the increased demands for unique IP addresses for all devices that can connect to the Internet. Internet Protocol version 6 (IPv6) represents an updated version of the current Internet Protocol, IPv4. IPv6 uses a 128-bit address and provides end-to-end security capabilities, enhanced Quality of Service (QoS), and increased number of available IP addresses.
The Cisco Unified IP Phone can support an IP Addressing Mode of IPv4 Only, IPv6 Only, or IPv4 and IPv6 in dual stack mode, as configured in Cisco Unified Communications Manager Administration. In IPv4, you can enter each octet of the IP address on the phone in dotted decimal notation; for example, 192.240.22.5. In IPv6, you can enter each octet of the IP address in hexadecimal notation with each octet separated by a colon; for example, 2005:db8:0:1:ef8:9876:ba72:dc9a. The phone truncates and removes leading zeros when it displays the IPv6 address.
Cisco Unified IP Phones support both IPv4 and an IPv6 address transparently, so users can handle all calls on the phone to which they are accustomed. Cisco Unified IP Phones support the use of IPv6 only with Cisco Unified Communications Manager Release 7.1(x) and only with the Skinny Call Control Protocol (SCCP).
Cisco Unified IP Phones do not support URLs with IPv6 addresses in the URL. This affects all IP Phone Service URLs, including services, directories, messages, help, and any restricted web services that require the phone to use HTTP to validate the credentials with the Authentication URL. If you configure Cisco Unified IP Phone services for Cisco Unified IP Phones, you must configure the phone and the servers that support the phone service with IPv4 addresses.
If you configure IPv6 Only as the IP Addressing Mode for phones that are running SIP, the Cisco TFTP service overrides the IP Addressing Mode configuration and uses IPv4 Only in the configuration file.
Table 17 describes the networking protocols on the Cisco Unified IP Phone and whether the protocols support IPv6.
Table 17 Supported Networking Protocols on the Cisco Unified IP Phone
Networking Protocol
|
Purpose
|
Usage Notes
|
Hypertext Transfer Protocol (HTTP)
|
HTTP represents the standard way of transferring information and moving documents across the Internet and the web.
|
Cisco Unified IP Phones use HTTP for the XML services and for troubleshooting purposes.
Cisco Unified IP Phones do not support the use of IPv6 addresses in the URL. You cannot use a literal IPv6 address in the URL or a hostname that maps to an IPv6 address.
|
Internet Protocol (IP)
|
IP, a messaging protocol, addresses and sends packets across the network.
|
To communicate by using IP, network devices must have an assigned IP address, subnet, and gateway.
IP addresses, subnets, and gateways identifications automatically get assigned if you are using the Cisco Unified IP Phone with Dynamic Host Configuration Protocol (DHCP).
If you are not using DHCP, you must manually assign these properties to each phone locally.
The Cisco Unified IP Phone supports concurrent IPv4 and IPv6 addresses. Configure the IP addressing mode (IPv4 only, IPv6 only, and both IPv4 and IPv6) in Cisco Unified Communications Manager Administration. For more information, refer to the "Internet Protocol Version 6 (IPv6)" chapter in the Cisco Unified Communications Manager Features and Services Guide.
|
Session Initiation Protocol (SIP)
|
SIP represents the Internet Engineering Task Force (IETF) standard for multimedia conferencing over IP. SIP, an ASCII-based application-layer control protocol (defined in RFC 3261), can get used to establish, maintain, and terminate calls between two or more endpoints.
|
SIP addresses the functions of signaling and session management within a packet telephony network. Signaling allows call information to get carried across network boundaries. Session management provides the ability to control the attributes of an end-to-end call.
You can configure the Cisco Unified IP Phone to use either SIP or Skinny Client Control Protocol (SCCP).
Cisco Unified IP Phones do not support SIP when the phones are operating in IPv6 address mode.
|
The following section provides information on how DHCP and Autoconfiguration affects the network settings on the phone. You can choose to configure the IP address and other network settings, such as the TFTP server, DNS server, domain, name, and so on, on an IP phone manually or by using a router and/or a DHCP server to automatically assign the IP address and other network information. For more information on how the Auto IP Configuration and DHCPv6 settings determine where the IP phone acquires its IPv6 address and other network settings, see Table 18.
Tip If you are not using DHCP in your network, you must configure these network settings on the Cisco Unified IP Phone after you install the phone on the network:
IP address
IP subnet information (subnet mask for IPv4 and subnet prefix length for IPv6)
Table 18 Determining Where a Phone Acquires Its Network Settings
DHCPv6
|
Auto IP Configuration
|
How the Phone Acquires Its IP address and Network Settings
|
Disabled
|
Disabled
|
You must manually configure an IP address and the other network settings.
Note When DHCPv6 is disabled, the Auto IP Configuration setting gets ignored.
|
Disabled
|
Enabled
|
You must manually configure an IP address and the other network settings.
Note When DHCPv6 is disabled, the Auto IP Configuration setting gets ignored.
|
Enabled
|
Disabled
|
The DHCP server assigns the IP address and the other network settings to the phone.
|
Enabled
|
Enabled
|
When the M-bit is set on the router, the O-bit gets ignored. The phone can set its IPv6 address based on an IPv6 address that it received from a DHCPv6 server, or the phone can acquire its IPv6 address through stateless address autoconfiguration.
When the M-bit is not set, you should set the O-bit on the router. The phone will then acquire its IPv6 address through stateless address autoconfiguration. It will not request an IPv6 address from the DHCPv6 server, but it will request other network configuration information.
|
Table 19 describes the phone menus that relate to IPv4 and IPv6. When you edit the value of an option setting on the phone, follow these guidelines:
•To enter a period (for example, in an IP address under IPv4 Configuration), press the . (period) softkey or press * on the keypad.
•To enter a colon (for example, in an IP address under IPv6 Configuration), press the : (colon) softkey or press * on the keypad.
Table 19 IPv4 and IPv6 Settings in Cisco Unified IP Phone Menus
Configuration Setting
|
Purpose
|
Description
|
Settings > Network Configuration Menu
|
IPv4 Configuration
|
Internet Protocol v4 address menu.
In the IPv4 Configuration menu, you can do the following tasks:
•Enable or disable the phone to use the IPv4 address that is assigned by the DHCPv4 server.
•Manually set the IPv4 Address, Subnet Mask, Default Routers, DNSv4 Server, and Alternate TFTP servers for IPv4.
For more information on the IPv4 address fields, refer to the specific field within this table.
|
1. Unlock network configuration options by pressing **#.
Note Pressing **# either locks or unlocks the options, depending on the previous state.
2. Scroll to IPv4 Configuration and press the Select softkey.
|
IPv6 Configuration
|
Internet Protocol v6 address menu. In the IPv6 Configuration menu, you can do the following tasks:
•Enable or disable the phone to use the IPv6 address that is assigned by the DHCPv6 server or to use the IPv6 address that it acquires through Stateless Address Autoconfiguration (SLAAC).
•Manually set the IPv6 Address, Subnet Prefix Length, DNSv6 Server, and IPv6 TFTP servers.
For more information on the IPv6 address fields, refer to the specific field within this table.
For more information on SLAAC, refer to Deploying IPv6 in Unified Communications Networks with Cisco Unified Communications Manager 7.1(x).
|
1. Unlock network configuration options by pressing **#.
Note Pressing **# either locks or unlocks the options, depending on the previous state.
2. Scroll to IPv6 Configuration and press the Select softkey.
|
Domain Name
|
Name of the Domain Name System (DNS) domain in which the phone resides.
Note If the phone receives different domain names from the DHCPv4 and DHCPv6 servers, the domain name from the DHCPv6 server will take precedence.
|
1. Unlock network configuration options by pressing **#.
Note Pressing **# either locks or unlocks the options, depending on the previous state.
2. Disable DHCP.
If the IP Addressing mode is configured for IPv4 only, set the DHCP option to No.
If the IP Addressing mode is configured for IPv6 only, set the DHCPv6 option to No.
If the IP Addressing mode is configured for both IPv4 and IPv6, set both DHCP option and DHCPv6 to No.
3. Scroll to the Domain Name option, press the Edit softkey, and then enter a new domain name.
4. Press the Validate softkey and then press the Save softkey.
|
Settings > Network Configuration Menu > IPv4 Configuration Menu
|
DHCP
|
Indicates whether the phone has DHCP enabled or disabled.
When DHCP is enabled, the DHCP server assigns the phone anIPv4 address. When DHCP is disabled, the administrator must manually assign an IPv4 address to the phone.
|
1. Unlock network configuration options by pressing **#.
Note Pressing **# either locks or unlocks the options, depending on the previous state.
2. Scroll to the DHCP option and press the No softkey to disable DHCP or press the Yes softkey to enable DHCP.
3. Press the Save softkey.
|
IP Address
|
Internet Protocol version 4 (IPv4) address of the phone.
If you assign an IPv4 address with this option, you must also assign a subnet mask and default router. See the Subnet Mask and Default Router options in this table.
|
1. Unlock network configuration options by pressing **#.
Note Pressing **# either locks or unlocks the options, depending on the previous state.
2. Set the DHCP option to No.
3. Scroll to the IP Address option, press the Edit softkey, and then enter a new IP Address.
4. Press the Validate softkey and then press the Save softkey.
|
Subnet Mask
|
Subnet mask that the phone uses.
|
1. Unlock network configuration options by pressing **#.
Note Pressing **# either locks or unlocks the options, depending on the previous state.
2. Set the DHCP option to No.
3. Scroll to the Subnet Mask option, press the Edit softkey, and then enter a new subnet mask.
4. Press the Validate softkey and then press the Save softkey.
|
Default Router 1
Default Router 2
Default Router 3
Default Router 4
Default Router 5
|
Default router that the phone uses (Default Router 1) and optional backup routers (Default Router 2-5).
|
1. Unlock network configuration options by pressing **#.
Note Pressing **# either locks or unlocks the options, depending on the previous state.
2. Set the DHCP option to No.
3. Scroll to the appropriate Default Router option, press the Edit softkey, and then enter a new router IP address.
4. Press the Validate softkey.
5. Repeat Steps 3 and 4 as needed to assign backup routers.
6. Press the Save softkey.
|
DNS Server 1
DNS Server 2
DNS Server 3
DNS Server 4
DNS Server 5
|
Primary Domain Name System (DNS) server (DNS Server 1) and optional backup DNS servers (DNS Server 2-5) that the phone uses.
|
1. Unlock network configuration options by pressing **#.
Note Pressing **# either locks or unlocks the options, depending on the previous state.
2. Set the DHCP option to No.
3. Scroll to the appropriate DNS Server option, press the Edit softkey, and then enter a new DNS server IP address.
4. Press the Validate softkey.
5. Repeat Steps 3 and 4 as needed to assign backup DNS servers.
6. Press the Save softkey.
|
DHCP Server
|
IP address of the Dynamic Host Configuration Protocol (DHCP) server from which the phone obtains its IPv4 address.
|
Display only—Cannot configure.
|
DHCP Address Released
|
Releases the IPv4 address that the DHCP server assigned.
|
1. Unlock network configuration options by pressing **#.
Note Pressing **# either locks or unlocks the options, depending on the previous state.
2. Scroll to the DHCP Address Released option and press the Yes softkey to release the IP address that is assigned by DHCP or press the No softkey if you do not want to release this IP address.
3. Press the Save softkey.
|
Alternate TFTP
|
Indicates whether the phone is using an alternate TFTP server.
|
1. Unlock network configuration options by pressing **#.
Note Pressing **# either locks or unlocks the options, depending on the previous state.
2. Scroll to the Alternate TFTP option and press the Yes softkey if the phone should use an alternate TFTP server.
3. Press the Save softkey.
|
TFTP Server 1
|
Primary Trivial File Transfer Protocol (TFTP) server that is used by the phone with an IPv4 address.
If you are not using DHCPv4 in your network and you want to change this server, you must use the TFTP Server 1 option.
If you set the Alternate TFTP option to Yes or disable DHCP, you must enter a nonzero value for the TFTP Server 1 option.
If neither the primary TFTP server nor the backup TFTP server is listed in the CTL file on the phone, you must unlock the CTL file before you can save changes to the TFTP Server 1 option. In this case, the phone will delete the CTL file when you save changes to the TFTP Server 1 option. A new CTL file will get downloaded from the new TFTP Server 1 address.
When the phone looks for its TFTP server, it gives precedence to manually assigned TFTP servers, regardless of the protocol. If your configuration includes both IPv6 and IPv4 TFTP servers, the phone prioritizes the order in which it looks for its TFTP server by giving priority to manually assigned IPv6 TFTP servers and IPv4 TFTP servers. The phone looks for its TFTP server in the following order:
1. Any manually assigned IPv6 TFTP Servers
2. Any manually assigned IPv4 TFTP Servers
3. DHCPv6 assigned TFTP servers
4. DHCP assigned TFTP servers
For information about unlocking the CTL file, refer to the "Security Configuration Menu" section in the corresponding Cisco Unified IP Phone Administration Guide.
|
1. Unlock the CTL file, if necessary.
2. If DHCP is enabled, set the Alternate TFTP option to Yes.
3. Scroll to the TFTP Server 1 option, press the Edit softkey, and then enter a new TFTP server IP address.
4. Press the Validate softkey and then press the Save softkey.
|
TFTP Server 2
|
Optional backup TFTP server that the phone with an IPv4 address uses if the primary TFTP server is unavailable.
If neither the primary TFTP server nor the backup TFTP server is listed in the CTL file on the phone, you must unlock the CTL file before you can save changes to the TFTP Server 2 option. In this case, the phone will delete the CTL file when you save changes to the TFTP Server 2 option. A new CTL file will get downloaded from the new TFTP Server 2 address.
When the phone looks for its TFTP server, it gives precedence to manually assigned TFTP servers, regardless of the protocol. If your configuration includes both IPv6 and IPv4 TFTP servers, the phone prioritizes the order in which it looks for its TFTP server by giving priority to manually assigned IPv6 TFTP servers and IPv4 TFTP servers. The phone looks for its TFTP server in the following order:
1. Manually assigned IPv6 TFTP servers
2. Manually assigned IPv4 TFTP servers
3. DHCPv6 assigned TFTP servers
4. DHCP assigned TFTP servers
For information about the CTL file, refer to Cisco Unified Communications Manager Security Guide.
For information about unlocking the CTL file, refer to the "Security Configuration Menu" section in the corresponding Cisco Unified IP Phone Administration Guide.
|
1. Unlock the CTL file, if necessary.
2. Unlock network configuration options.
3. Enter an IP address for the TFTP Server 1 option.
4. Scroll to the TFTP Server 2 option, press the Edit softkey, and then enter a new backup TFTP server IP address.
5. Press the Validate softkey and then press the Save softkey.
|
BOOTP Server
|
Indicates whether the phone obtains its configuration from a Bootstrap Protocol (BootP) server instead of from a DHCP server.
|
Display only—Cannot configure.
|
Settings > Network Configuration Menu > IPv6 Configuration Menu
|
DHCPv6
|
Indicates whether the phone has DHCPv6 enabled or disabled.
When DHCPv6 is enabled, the DHCPv6 server assigns an IPv6 address to the phone. When DHCP v6 is disabled, the administrator must manually assign an IPv6 address to the phone.
The DHCPv6 setting, along with the Auto IP Configuration setting, determine how the phone obtains its network settings. For more information on how these two settings affect the network settings on the phone, see Table 18 (Determining Where a Phone Acquires its Network Settings).
|
1. Unlock network configuration options by pressing **#.
Note Pressing **# either locks or unlocks the options, depending on the previous state.
2. Scroll to the DHCPv6 option and press the No softkey to disable DHCPv6 or press the Yes softkey to enable DHCP.
3. Press the Save softkey.
|
IPv6 Address
|
Internet Protocol version 6 (IPv6) address of the phone. The IPv6 address comprises a 128-bit address.
If you assign an IP address with this option, you must also assign the IPv6 prefix length. See the IPv6 Subnet Prefix options in this table.
|
1. Unlock network configuration options by pressing **#.
Note Pressing **# either locks or unlocks the options, depending on the previous state.
2. Set the DHCPv6 option to No.
3. Scroll to the IP Address option, press the Edit softkey, and then enter a new IP Address.
4. Press the Validate softkey and then press the Save softkey.
|
IPv6 Prefix Length
|
Subnet prefix length that the phone uses. The subnet prefix length specifies a decimal value from 1-128, which specifies the portion of the IPv6 address that comprises the subnet.
|
1. Unlock network configuration options by pressing **#.
Note |
