New and Changed Information for Cisco Unified Communications Manager 8.0(x)
Cisco Unified Communications Manager Administration
Downloads: This chapterpdf (PDF - 2.92MB) The complete bookPDF (PDF - 11.5MB) | Feedback

Cisco Unified Communications Manager Administration

Table Of Contents

Cisco Unified Communications Manager Administration

Revision History

Documentation Changes

Search Documentation Link Added to Cisco Unified Communications Manager Administration

Supported Browsers

New and Updated Service and Enterprise Parameters

Menu Changes

Cisco Unified Communications Manager Features and Applications

Announcements Configuration

Assisted Directed Call Park

Audio Codec Preference By Sound Quality

Call Control Discovery

Call Waiting

Caller ID Support on MGCP FXO Gateways

Cancel Call Waiting

Cisco Unified Communications Manager Attendant Console No Longer Supported in Cisco Unified Communications Manager 8.0(1)

Cisco Extension Mobility Change PIN

Cisco Extension Mobility Cross Cluster

Cisco Unified Mobility Dial-Via-Office Forward

Cisco Unified Mobility Intelligent Session Control

Cisco Unified Mobility Session Handoff

External Call Control

Feature Control Policy

Hotline

Hunt List Enhancements

Improved Phone Administration

Incoming Called Party Settings for H.323 Gateways and Trunks

Incoming Number Setting Replaces Unknown Setting on SIP Trunk Page

iSAC Codec Support

LDAP Custom Filters

Licensing—Invalid Status Added to License Unit Report Page

Microsoft Active Directory Application Mode LDAP Server Support

Park Monitoring

SIP Trunk End-To-End RSVP Support

Supplementary Services Support for SCCP Gateway Endpoints


Cisco Unified Communications Manager Administration


This chapter contains information on the following topics:

Revision History

Documentation Changes

Search Documentation Link Added to Cisco Unified Communications Manager Administration

Supported Browsers

New and Updated Service and Enterprise Parameters

Menu Changes

Cisco Unified Communications Manager Features and Applications

Revision History

Table 2-1 describes the revisions that have been made to this chapter since the chapter was first posted to www.cisco.com.

Table 2-1 Revision History for This Chapter

Date Revision Made
What Has Changed Since The Chapter Was First Published

04/02/2010

Made updates to the following sections to address CSCtf47303:

Audio Codec Preference By Sound Quality

Renamed heading, Audio Codec Bandwidth G.722.1 Added To Region Configuration Page, to "iSAC Codec Support" section; moved section in alphabetical order

Added the section, "Search Documentation Link Added to Cisco Unified Communications Manager Administration" section

Updated the "Cisco Unified Communications Manager Attendant Console No Longer Supported in Cisco Unified Communications Manager 8.0(1)" section to include the URL for the End of Sale/End of Life notice


Documentation Changes

This section highlights some documentation changes for the Cisco Unified Communications Manager Administration Guide, Cisco Unified Communications Manager Features and Services Guide, and the Cisco Unified Communications Manager System Guide; for example, this section highlights new chapters in guides and information that moved from one document to another document.

Cisco Unified Communications Manager Administration Guide

The following chapters were removed from the Cisco Unified Communications Manager Administration Guide:

License Unit Report

License Unit Calculator

License File Upload

Cisco Unified Communications Manager Attendant Console Pilot Point Configuration

Cisco Unified Communications Manager Attendant Console User Configuration

Cisco Unified Communications Manager Attendant Console User File Upload

The following chapters are new for the Cisco Unified Communications Manager Administration Guide:

LDAP Custom Filter Configuration

Announcement Configuration (See "Announcements Configuration" section.)

Feature Control Policy Configuration (See "Feature Control Policy" section)

Cisco Unified Communications Manager System Guide

The following chapters were removed from the Cisco Unified Communications Manager System Guide:

Cisco Unified Communications Manager Attendant Console

Licensing

Cisco Unified Communications Manager Features and Services Guide

The "Cisco Unified Communications Manager Attendant Console" chapter was removed from the Cisco Unified Communications Manager Features and Services Guide.

The following chapters are new for the Cisco Unified Communications Manager Features and Services Guide:

Call Control Discovery (See "Call Control Discovery" section.)

Cisco Extension Mobility Cross Cluster (See "Cisco Extension Mobility Cross Cluster" section.)

External Call Control (See "External Call Control" section.)

Hotline (See "Hotline" section.)

Licensing (includes information that was in the Cisco Unified Communications Manager Administration Guide and Cisco Unified Communications Manager System Guide in previous releases)

Search Documentation Link Added to Cisco Unified Communications Manager Administration

Located in the upper, right corner of Cisco Unified Communications Manager Administration, the Search Documentation link, which is new for 8.0(1), allows you to search on topics across Cisco Unified Communications Manager documentation that is provided for 8.0(x). To filter your search results based on a particular document type for Cisco Unified Communications Manager or Cisco Unified Communications Manager Business Edition, click the appropriate tab after you execute your search.

For example, if you search on Call Control Discovery, the search returns links to the Cisco Unified Communications Manager Features and Services Guide, Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, and Cisco Unified Communications Manager Managed Services Guide.

The Search Documentation link also displays in Cisco Unified Communications Operating System, Disaster Recovery System, and Cisco Unified Reporting.


Tip This search engine does not display results for all Cisco Unified Communications Manager documentation. For example, tech notes, data sheets, field notices, and so on do not display in the results.



Tip Your browser or browser security settings may impact the search capabilities. For example, if you use Microsoft Internet Explorer 8, click No if you are asked whether you want to display only secure webpage content. If you click Yes, the search results do not load.


Supported Browsers

Cisco Unified Communications Manager Administration supports the following operating system browsers:

Microsoft Internet Explorer (IE) 7 when running on Microsoft Windows XP SP3

Microsoft Internet Explorer (IE) 8 when running on Microsoft Windows XP SP3 or Microsoft Vista SP2

Firefox 3.x when running on Microsoft Windows XP SP3, Microsoft Vista SP2 or Apple MAC OS X

Safari 4.x when running on Apple MAC OS X

From any user PC in your network, browse into a server that is running Cisco Unified Communications Manager Administration and log in with administrative privileges.


Note Simultaneous logon to Cisco Unified Communications Manager Administration by a large number of users can cause performance to suffer. Try to limit the number of users and administrators that are logged on simultaneously.



Note Cisco Unified Communications Manager Administration does not support the browser controls in your browser. Do not use the browser buttons (for example, the Back button) when you perform configuration tasks.


New and Updated Service and Enterprise 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.

Cluster ID—This enterprise parameter supports the Cisco Extension Mobility Cross Cluster feature.

Prepare Cluster for Rollback to pre-8.0—This enterprise parameter prepares the cluster to revert to a pre-8.0 release of Cisco Unified Communications Manager, as described in the"Rolling Back the Cluster to a Pre-8.0 Release" section on page 3-8.

Secured Authentication URL—This enterprise parameter supports HTTPS, as described in "HTTPS" section on page 3-27.

Secured Directory URL—This enterprise parameter supports HTTPS, as described in "HTTPS" section on page 3-27.

Secured Idle URL—This enterprise parameter supports HTTPS, as described in "HTTPS" section on page 3-27.

Secured Information URL—This enterprise parameter supports HTTPS, as described in "HTTPS" section on page 3-27.

Secured Messaged URL—This enterprise parameter supports HTTPS, as described in "HTTPS" section on page 3-27.

Secured Services URL—This enterprise parameter supports HTTPS, as described in "HTTPS" section on page 3-27.

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.

Default Intraregion Max Audio Bit Rate and Default Interregion Max Audio Bit Rate—Formerly called the Intraregion Audio Codec Default and Interregion Audio Codec Default service parameters. (See the "Audio Codec Preference By Sound Quality" section.)

Default Intraregion Max Video Call Bit Rate and Default Interregion Max Video Call Bit Rate—Formerly called the Intraregion Video Call Bandwidth Default and Interregion Video Call Bandwidth Default service parameters. (See the "Audio Codec Preference By Sound Quality" section.)

Default Intraregion and Interregion Link Loss Type—Formerly called the Link Loss Type Default service parameter. (See the "Audio Codec Preference By Sound Quality" section.)

Park Monitoring Reversion Timer—This service parameter supports the Cisco CallManager service, as described in the "Park Monitoring" section.

Park Monitoring Periodic Reversion Timer—This service parameter supports the Cisco CallManager service, as described in the "Park Monitoring" section.

Park Monitoring Forward No Retrieve Timer—This service parameter supports the Cisco CallManager service, as described in the "Park Monitoring" section.

External Call Control Diversion Maximum Hop Count—This service parameter supports the Cisco CallManager service, as described in the "External Call Control" section.

Maximum External Call Control Diversion Hops to Pattern or DN—This service parameter supports the Cisco CallManager service, as described in the "External Call Control" section.

External Call Control Routing Request Timer —This service parameter supports the Cisco CallManager service, as described in the "External Call Control" section.

External Call Control Fully Qualified Role And Resource—This service parameter supports the Cisco CallManager service, as described in the "External Call Control" section.

External Call Control Initial Connection Count To PDP —This service parameter supports the Cisco CallManager service, as described in the "External Call Control" section.

External Call Control Maximum Connection Count To PDP —This service parameter supports the Cisco CallManager service, as described in the "External Call Control" section.

Route Class Trunk Signaling Enabled — This service parameter supports the Cisco CallManager service, as described in the "Hotline" section.

SIP Satellite Avoidance Route Class Label — This service parameter supports the Cisco CallManager service, as described in the "Hotline" section.

SIP Hotline Voice Route Class Label — This service parameter supports the Cisco CallManager service, as described in the "Hotline" section.

SIP Hotline Data Route Class Label — This service parameter supports the Cisco CallManager service, as described in the "Hotline" section.

Pass Inbound T1 CAS MLPP Precedence Digits to Dial Plan — This service parameter supports the Cisco CallManager service, as described in the "Hotline" section.

Allow Calls to be picked up from Line Group Members — This service parameter supports the Cisco CallManager service, as described in the "Hunt List Enhancements" section.

Incoming Called Party National Number Prefix - H.323 (click Advanced.)—This service parameter supports the Cisco CallManager service, as described in the "Incoming Called Party Settings for H.323 Gateways and Trunks" section.

Incoming Called Party International Number Prefix - H.323 (click Advanced.)—This service parameter supports the Cisco CallManager service, as described in the "Incoming Called Party Settings for H.323 Gateways and Trunks" section.

Incoming Called Party Subscriber Number Prefix - H.323 (click Advanced.)—This service parameter supports the Cisco CallManager service, as described in the "Incoming Called Party Settings for H.323 Gateways and Trunks" section.

Incoming Called Party Unknown Number Prefix - H.323 (click Advanced.)—This service parameter supports the Cisco CallManager service, as described in the "Incoming Called Party Settings for H.323 Gateways and Trunks" section.

Enforce Intra-cluster Maximum Login Time—This service parameter, formerly known as Enforce Maximum Login Time, supports the Cisco Extension Mobility service.

Intra-cluster Maximum Login Time—This service parameter, formerly known as Maximum Login Time, supports the Cisco Extension Mobility service.

Inter-cluster Maximum Login Time—This service parameter supports the Cisco Extension Mobility service. See the "Cisco Extension Mobility Cross Cluster" section for more information.

Intra-cluster Multiple Login Behavior—This service parameter, formerly known as Multiple Login Behavior, supports the Cisco Extension Mobility service.

Clear Call Logs on Intra-Cluster EM—This service parameter, formerly known as Clear Call Log, supports the Cisco Extension Mobility service.

EMCC Allow Proxy—This service parameter supports the Cisco Extension Mobility service. See the "Cisco Extension Mobility Cross Cluster" section for more information.

Reroute Remote Destination Calls to Enterprise Number—This service parameter supports the Cisco CallManager service, as described in the "Cisco Unified Mobility Intelligent Session Control" section.

Log Mobile Number in CDR for Rerouted RD Calls—This service parameter supports the Cisco CallManager service, as described in the "Cisco Unified Mobility Intelligent Session Control" section.

Ignore Call Forward All on Enterprise DN—This service parameter supports the Cisco CallManager service, as described in the "Cisco Unified Mobility Intelligent Session Control" section.

Session Handoff Alerting Timer—This service parameter supports the Cisco CallManager service, as described in the "Cisco Unified Mobility Session Handoff" section.

Enterprise Feature Access Code for Session Handoff—This service parameter supports the Cisco CallManager service, as described in the "Cisco Unified Mobility Session Handoff" section.

Prepare Cluster for Rollback to pre-8.0—This enterprise parameter prepares the cluster to revert to a pre-8.0 release of Cisco Unified Communications Manager, as described in the "Rolling Back the Cluster to a Pre-8.0 Release" section on page 3-8.

Menu Changes

This section contains information on the following menus in Cisco Unified Communications Manager Administration:

Main Window

System

Call Routing

Media Resources

Advanced Features (formerly Voice Mail menu)

Device

Application

User Management

Bulk Administration

Main Window

No changes were made to the main window.

System

The System menu contains the following changes:

System > Region—Changed the name of the Audio Codec setting to the Max Audio Bit Rate setting; changed the name of the Video Bandwidth setting to the Max Video Call Bit Rate (Includes Audio) setting, as described in the "Audio Codec Preference By Sound Quality" section.

System > Device Pool—Added incoming called party settings for H.323, as described in the "Incoming Called Party Settings for H.323 Gateways and Trunks" section.

System > Device Pool—Added Adjunct CSS setting for Cisco Extension Mobility Cross Cluster feature, as described in the "Adjunct Calling Search Space Functionality" section.

System > LDAP—Added LDAP custom filters, as described in the "LDAP Custom Filters" section.

System > Security > Certificate—Added new window to support certificate configuration, as described in "Certificate Configuration" section on page 3-26.

System > Licensing > License Unit Report—Added the Invalid Status message, as described in the "Licensing—Invalid Status Added to License Unit Report Page" section.

Call Routing

The Call Routing menu provides the following new and updated settings.

Call Routing > Translation Pattern—Added External Call Control Profile drop-down list box, as described in the "External Call Control" section.

Call Routing > Directory Number—For the external call control feature, added the Device Invoked Call Recording Enabled option in the Recording Option drop-down list box, as described in the "External Call Control" section.

Call Routing > Directory Number—For the Park Monitoring feature for Cisco Unified IP Phones 8961, 9951, and 9971, added the following options, which are described in the "Park Monitoring" section:

Park Monitoring Forward No Retrieve Destination External

Park Monitoring Forward No Retrieve Destination Internal

Park Monitoring Reversion Timer

Call Routing > Route/Hunt > Hunt Pilot —For the Park Monitoring feature for Cisco Unified IP Phones 8961, 9951, and 9971, added the Park Monitoring Forward No Retrieve Destination option, as described in the "Park Monitoring" section.

Call Routing > Call Control Discovery —Add the following windows for Call Control Discovery.

Hosted DN Group

Hosted DN Pattern

Advertising Service

Partition

Requesting Service

Blocked Learned Patterns

See the "Call Control Discovery" section.

Call Routing > External Call Control Profile—Added new window to support the external call control feature, as described in the "External Call Control" section.

Media Resources

The Media Resources menu displays the following new and updated settings.

Media Resources > Announcement—Added new window to support uploading of customized announcements, as described in the "Announcements Configuration" section.

Advanced Features (formerly Voice Mail menu)

The Advanced Features menu displays the following new and updated settings.

Advanced Features > Voice Mail > ....—Moved the voice mail configuration window under the Advanced Features menu.

Advanced Features > SAF > SAF Security Profile (or SAF Forwarder)—Added new windows to support the call control discovery feature. See the "Call Control Discovery" section.

Advanced Features > EMCC > EMCC Feature Configuration—Added new window to support the Cisco Extension Mobility Cross Cluster feature, as described in the "Configuring EMCC Feature Configuration Settings" section.

Advanced Features > EMCC > EMCC Intercluster Service Profile—Added new window to support the Cisco Extension Mobility Cross Cluster feature, as described in "EMCC Intercluster Service Profile Configuration Settings" section.

Advanced Features > EMCC > EMCC Remote Cluster—Added new window to support the Cisco Extension Mobility Cross Cluster feature, as described in "Remote Cluster Configuration Settings" section.

Advanced Features > VPN > VPN Profile—Added new window to support the Virtual Private Networks for Cisco Cisco Unified IP Phones feature, as described in "Configuring a VPN Gateway" section on page 3-17.

Advanced Features > VPN > VPN Group—Added new window to support the Virtual Private Networks for Cisco Cisco Unified IP Phones feature, as described in "Configuring a VPN Group" section on page 3-20.

Advanced Features > VPN > VPN Gateway—Added new window to support the Virtual Private Networks for Cisco Cisco Unified IP Phones feature, as described in "Configuring a VPN Gateway" section on page 3-17.

Advanced Features > VPN > VPN Feature Configuration—Added new window to support the Virtual Private Networks for Cisco Cisco Unified IP Phones feature, as described in "Configuring a VPN Profile" section on page 3-22.

Device

The Device menu displays the following new and updated settings.

Device > Gateway—Added the incoming called party settings for H.323 gateways, as described in the "Incoming Called Party Settings for H.323 Gateways and Trunks" section.

Device > Trunk—Added the following settings:

Trunk Service Type drop-down list box for SIP trunks (for Cisco Extension Mobility Cross Cluster, Call Control Discovery, or Cisco IME).

Incoming called party settings for H.323 trunks, as described in the "Incoming Called Party Settings for H.323 Gateways and Trunks" section.

Changed the Unknown Calling Party setting to Incoming Number (for SIP trunks)

Enabled SAF for H.323 (non-gatekeeper controlled) trunks (for Call Control Discovery feature)

Device > Phone—Added the following settings:

Standard Chaperone option from the Softkey Template drop-down list box to support the external call control feature, as described in the "External Call Control" section.

Device > Device Settings > Device Profile—Added the Extension Mobility Cross Cluster CSS setting on the Device Profile Configuration window to support the Cisco Extension Mobility Cross Cluster feature.

Application

The following windows were removed from the Applications menu.

Application > Cisco Unified Communications Manager Attendant Console Pilot Point

Application > Cisco Unified Communications Manager Attendant Console User

Application > Cisco Unified Communications Manager Attendant Console User File Upload

User Management

The User Management menu displays the following new settings:

User > User Management—Added the Enable Extension Mobility Cross Cluster check box on the End User Configuration window to support the Cisco Extension Mobility Cross Cluster feature.

Bulk Administration

The Bulk Administration menu displays the following new and updated settings.

Bulk Administration > EMCC > EMCC—New submenu to add Extension Mobility Cross Cluster templates as described in the "Extension Mobility Cross Cluster" section on page 4-1.

Bulk Administration > EMCC > Insert/Update EMCC—New submenu to insert Extension Mobility Cross Cluster as described in the "Extension Mobility Cross Cluster" section on page 4-1.

Bulk Administration > EMCC > Delete EMCC—New submenu to delete Extension Mobility Cross Cluster as described in the "Extension Mobility Cross Cluster" section on page 4-1

Bulk Administration > Phones > Phone Template—The following new fields are added to this page:

Feature Control Policy—New drop-down list box, as described in the "New Fields in Bulk Administration" section on page 4-6.

Hotline Device—New check box, as described in the "New Fields in Bulk Administration" section on page 4-6.

Secure Authentication URL—New field, as described in the "New Fields in Bulk Administration" section on page 4-6.

Secure Directory URL—New field, as described in the "New Fields in Bulk Administration" section on page 4-6.

Secure Idle URL—New field, as described in the "New Fields in Bulk Administration" section on page 4-6.

Secure Information URL—New field, as described in the "New Fields in Bulk Administration" section on page 4-6.

Bulk Administration > Phones > Add a new DN—the following new fields are added to this page:

Park Monitoring Forward No Retrieve Destination External—New field, as described in the "New Fields in Bulk Administration" section on page 4-6.

Park Monitoring Forward No Retrieve Destination Internal—New field, as described in the "New Fields in Bulk Administration" section on page 4-6.

Park Monitoring Reversion Timer—New field, as described in the "New Fields in Bulk Administration" section on page 4-6.

Park Monitoring Forward No Retrieve Internal Voice Mail—New field, as described in the "New Fields in Bulk Administration" section on page 4-6.

Park Monitoring Forward No Retrieve External Voice Mail—New field, as described in the "New Fields in Bulk Administration" section on page 4-6.

Park Monitoring Forward No Retrieve External CSS—New field, as described in the "New Fields in Bulk Administration" section on page 4-6.

Park Monitoring Forward No Retrieve Internal CSS—New field, as described in the "New Fields in Bulk Administration" section on page 4-6.

Bulk Administration > User Device Profiles > User Device Profile Template—The following new fields are added to the User Device Profile Template Configuration page:

Park Monitoring Forward No Retrieve Destination External—New field, as described in the "New Fields in Bulk Administration" section on page 4-6.

Park Monitoring Forward No Retrieve Destination Internal—New field, as described in the "New Fields in Bulk Administration" section on page 4-6.

Park Monitoring Reversion Timer—New field, as described in the "New Fields in Bulk Administration" section on page 4-6.

Park Monitoring Forward No Retrieve Internal Voice Mail—New field, as described in the "New Fields in Bulk Administration" section on page 4-6.

Park Monitoring Forward No Retrieve External Voice Mail—New field, as described in the "New Fields in Bulk Administration" section on page 4-6.

Park Monitoring Forward No Retrieve External CSS—New field, as described in the "New Fields in Bulk Administration" section on page 4-6.

Park Monitoring Forward No Retrieve Internal CSS—New field, as described in the "New Fields in Bulk Administration" section on page 4-6.

Bulk Administration > Gateways > Gateway Template—The following field has been added to the Gateway FXS/FXO Port Configuration Settings page:

Hotline Device—New check box, as described in the "New Fields in Bulk Administration" section on page 4-6.

Bulk Administration > Import/Export > Export—The following new and updated fields can now be exported through the Export Data page under System Data:

Certificate

LDAP Custom Filter

Bulk Administration > Import/Export > Export—The following new and updated fields can now be exported through the Export Data page under Call Routing Data:

CCD Requesting Service

Hosted DN Group

Block Learned Patterns

Hosted DN Patterns

CCD Advertising Service

External Call Control Profile

Transformation Profile

Bulk Administration > Import/Export > Export—The following new and updated fields can now be exported through the Export Data page under User Data:

End User CAPF Profile

Bulk Administration > Import/Export > Export—The following new and updated fields can now be exported through the Export Data page under Advanced Features:

SAF Forwarder

SAF Security Profile

EMCC Remote Cluster

EMCC Intercluster Service Profile

VPN Profile

VPN Gateway

VPN Group

EMCC Feature Configuration

Cisco Unified Communications Manager Features and Applications

This section contains information on the following topics:

Announcements Configuration

Assisted Directed Call Park

Audio Codec Preference By Sound Quality

Call Control Discovery

Call Waiting

Caller ID Support on MGCP FXO Gateways

Cancel Call Waiting

Cisco Unified Communications Manager Attendant Console No Longer Supported in Cisco Unified Communications Manager 8.0(1)

Cisco Extension Mobility Change PIN

Cisco Extension Mobility Cross Cluster

Cisco Unified Mobility Dial-Via-Office Forward

Cisco Unified Mobility Intelligent Session Control

Cisco Unified Mobility Session Handoff

External Call Control

Hotline

Hunt List Enhancements

Improved Phone Administration

Incoming Called Party Settings for H.323 Gateways and Trunks

Incoming Number Setting Replaces Unknown Setting on SIP Trunk Page

iSAC Codec Support

LDAP Custom Filters

Licensing—Invalid Status Added to License Unit Report Page

Microsoft Active Directory Application Mode LDAP Server Support

Park Monitoring

SIP Trunk End-To-End RSVP Support

Supplementary Services Support for SCCP Gateway Endpoints

Announcements Configuration

This section contains information on the following topics:

Announcements Description

Cisco Unified Communications Manager Administration Configuration Tips for Announcements

GUI Changes for Announcements

Service Parameter and Enterprise Parameter Changes for Announcements

Installation/Upgrade (Migration) and Backup Considerations for Announcements

Serviceability Considerations for Announcements

BAT Considerations for Anointments

CAR/CDR Considerations for Announcements

Security Considerations for Announcements

AXL and CTI Considerations for Announcements

User Tips for Announcements

For More Information on Announcements

Announcements Description

When you install Cisco Unified Communications Manager, Cisco-provided announcements and tones install, and the Find and Lists Announcements window in Cisco Unified Communications Manager Administration displays these announcements and tones, which can be used for basic calls, external call control, or MLPP, depending on the announcement. (Media Resources > Announcements) Cisco Unified Communications Manager allows you to use the Cisco-provided announcements as is, insert custom announcement .wav files, assign the locale for the announcement, change the description for the announcement, or change the message or tone that you want an announcement to play.


Tip For a description of each announcement that displays in the Find and List Announcements window, refer to the "Announcements Configuration" chapter in the Cisco Unified Communications Manager Administration Guide.

Be aware that external call control supports every announcement that displays in the window. For more information, see the "Announcement Support for Routing Rules" section.


Cisco Unified Communications Manager Administration Configuration Tips for Announcements

Be aware that a custom announcement uses the same announcement identifier as a Cisco-provided announcement; that is, when you upload a custom announcement, you choose an existing announcement identifier that you want to use for the custom announcement; therefore, the Cisco-provided announcement and customized announcement use the same announcement identifier. After you insert the custom announcement, Cisco Unified Communications Manager automatically plays the custom announcement, unless you uncheck the Enable check box in the Announcements Configuration window (which indicates that you want Cisco Unified Communications Manager to play the Cisco-provided announcement that is associated with the announcement identifier).

If you want to do so, you can change the description for the announcement for any Cisco-provided or customized announcement without changing the announcement itself. The description is used to identify various announcements in Cisco Unified Communications Manager Administration.

Like music on hold audio source files, the recommended format for announcements includes the following specifications:

16-bit PCM wav file

Stereo or mono

Sample rates of 48 kHz, 44.1 kHz, 32 kHz, 16 kHz, or 8 kHz

If you upload customized announcements, you must upload the announcement on each node in the cluster; that is, the announcement files do not get propagated between servers in a cluster, so you must browse into Cisco Unified Communications Manager Administration on each server in the cluster and repeat the upload process.

If you upload customized announcements, you must configure annunciator to handle the announcements.


Tip With early media cut through, a greeting gets played to the caller before the called party is alerted about the call. Trunks and gateways must support early media cut through for the greeting to get played in such a way. Cisco PRI/MGCP gateways, H.323 gateways and trunks support early media cut through. For SIP trunk to support early media cut through, you must enable PRACK. Be aware that a greeting may not get played if the device does not support early media cut through.


You cannot update announcements that are not hyperlinked in the Find and List Announcements window. You can insert customized announcements for Cisco-provided announcements that are underlined with a hyperlink in the Find and List Announcements window; for example, Custom_5001, Custom_5014, MLPP-ICA_00120, or MonitoringWarning_00055.

You cannot delete any announcements that display in Cisco Unified Communications Manager Administration.

The following procedure describes how to upload a custom announcement:


Step 1 In Cisco Unified Communications Manager Administration, choose Media Resources > Announcements.

The Find and List Announcements window displays.

Step 2 Perform one of the following tasks:

In the Find and List Announcements window, click the hyperlink for the announcement; for example, Custom_5006; when the Announcements window displays, click Upload File.

In the Find and List Announcements window, click Upload File; continue with Step 3.

Step 3 In the Upload File pop-up window, choose the announcement identifier, update the announcement description, choose the locale, and click Upload File. For more info on the settings that display, see Table 2-2.

The upload process begins, and a message displays that the Audio Translator Utility is processing the request.

Step 4 If you want to change the message or tone that gets played during the announcement, choose a different announcement from the Default Announcement drop-down list box in the Announcements window.

Step 5 If you want Cisco Unified Communications Manager to play the customized announcement instead of playing the Cisco-provided announcement, make sure that the Enable check box displays as checked in the Announcement by Locale pane in the Announcements Configuration window. If the Enable check box displays as unchecked, Cisco Unified Communications Manager plays the Cisco-provided announcement.

Step 6 After you make the changes in the Announcements Configuration window, click Save.

Step 7 You must upload the announcement on each node in the cluster; that is, the announcement files do not get propagated between servers in a cluster, so you must browse into Cisco Unified Communications Manager Administration on each server in the cluster and repeat the upload process.

Step 8 Configure annunciator to handle the customized announcements.


GUI Changes for Announcements

Table 2-2 describes the announcement configuration settings.

Table 2-2 Announcement Configuration Settings 

Field
Description
Announcement Configuration and Upload File Windows

Announcement Identifier

The Announcement Identifier drop-down list box displays all announcement IDs that you can associate with customized announcements. Consider these announcement identifiers as placeholders for inserting customized announcements.

For a customized announcement that you are inserting, choose the announcement identifier that you want to associate with the customized announcement.

Features, such as external call control, use the announcement identifier to ensure that Cisco Unified Communications Manager plays the announcement.

Customized Description

For customized announcements that you are inserting, enter a description for the announcement; for example, enter the text from the customized announcement. You can enter any characters in this field.

When you click the Upload File button in the Find and List window, this field displays as blank. When you click the Upload File button in the Announcements Configuration window, the Cisco-provided (default) description for the announcement displays.

If you do not update this field in the Announcements Configuration window, the Cisco-provided (default) description displays. After you update this customized description field, the Cisco-provided default description displays in the Find and Lists Announcements window; see the Default Description column in the Find and Lists window for the default description.

You can enter up to 50 characters.

Locale

This setting displays in the Upload File window. From the Locale drop-down list box, choose the locale that you want to associate with the announcement.

In this drop-down list box, the None option means that no option has been chosen.

By default, all Cisco-provided announcements support English_United States.

Tip For a locale to display in the Locale drop-down list box in the Upload File Configuration window, you must install the Cisco Unified Communications Locale Installer that is specific to your locale. For more information, refer to the Cisco Unified Communications Operating System Administration Guide.

Default Announcement

From the drop-down list box, choose the Cisco-provided announcement that you want to play when the custom announcement is not used.

Announcement by Locale Pane in the Announcements Configuration Window

Enable

This setting displays after you insert a customized announcement.

When the Enable check box is checked, Cisco Unified Communications Manager plays the customized announcement for the locale that is shown. If you want Cisco Unified Communications Manager to play the Cisco-provided announcement that is associated with the announcement identifier, uncheck the Enable check box.

Customized Locale Description

This setting displays after you insert a customized announcement.

This field, which is read-only, displays the description for the customized announcement for the displayed locale. You enter this description when you upload the customized announcement.

Locale

This setting displays after you insert a customized announcement.

This field, which is read-only, displays the locale that you chose for the customized announcement when you uploaded the .wav file.

Each locale is associated with an uploaded custom announcement. You can upload another wav file for the same announcement, but you assign it to a different locale. In this case, two rows display, one for each locale. If you want to update/replace a custom announcement for a locale, you can upload a new wav file with the same locale you want to replace.

Default Cisco Announcement

This field indicates the last uploaded customized announcement.


Service Parameter and Enterprise Parameter Changes for Announcements

No service or enterprise parameters changes occurred to support this feature.

Installation/Upgrade (Migration) and Backup Considerations for Announcements

After you install Cisco Unified Communications Manager 8.0(1) and activate the Cisco IP Voice Media Streaming App service, the Disaster Recovery System automatically backs up custom announcements.

When you upgrade to Cisco Unified Communications Manager 8.0(1) or later from a compatible release, such as 6.1(x) or 7.X, be aware that the custom announcements component in Cisco Unified Communications Manager 8.0(x) may not automatically register with the Disaster Recovery System, especially if the Cisco IP Voice Media Streaming App service was activated when you were running the previous release; in this case, custom announcements do not automatically get backed up through the Disaster Recovery System. To ensure that custom announcements get backed up after an upgrade to Cisco Unified Communications Manager 8.0(1), deactivate and reactivate the Cisco IP Voice Media Streaming App service in Cisco Unified Serviceability under Service Activation. You must perform this task for each node in the cluster that runs the Cisco IP Voice Media Streaming App service. (You must perform this task once on the 8.0(x) train; for example, if you deactivate and reactivate the service after an upgrade to 8.0(1), you do not need to do it again if you upgrade to a later 8.0(x) release.)

Serviceability Considerations for Announcements

Make sure that the Cisco IP Voice Media Streaming App service is activated in Cisco Unified Serviceability under Service Activation.

If no announcement is played, the Media Streaming App issues the following alarms:

kANNAudioUndefinedAnnID - Undefined custom announcement identifier or locale identifier exists. The alarm contains the numeric identifiers for these identifiers.

kANNAudioFileMissing- A custom and/or Cisco-provided announcement .wav file is not found. The alarm contains file name, Announcement ID, user locale, and network locale.

For these alarms, verify that the ANN (annunciator) device is registered. Verify that the ANN device is in the media resource group if media resource groups are being used. Verify Announcement ID is correct, if you are using external call control. Verify that the locale is installed, if you are not using United States_English locale.

BAT Considerations for Anointments

No BAT considerations exist for this feature.

CAR/CDR Considerations for Announcements

No CAR or CDR considerations exist for this feature.

Security Considerations for Announcements

No security considerations exist for this feature.

AXL and CTI Considerations for Announcements

No AXL or CTI considerations exist for this feature.

User Tips for Announcements

No user tips exist for this feature.

For More Information on Announcements

Announcements Configuration, Cisco Unified Communications Manager Administration Guide

External Call Control

Assisted Directed Call Park

This section contains information on the following topics:

Description

Cisco Unified Communications Manager Administration Configuration Tips

GUI Changes

Service Parameter and Enterprise Parameter Changes

Installation/Upgrade (Migration) Considerations

Serviceability Considerations

BAT Considerations

CAR/CDR Considerations

Security Considerations

AXL and CTI Considerations

User Tips

For More Information

Description

Assisted directed call park is supported only on Cisco Unified IP Phones 8961, 9951, or 9971 (SIP phones only). Assisted directed call park means that the end user only needs to press one button to direct-park a call. This requires you to configure a BLF Directed Call Park button. Then, when the user presses an idle BLF Directed Call Park feature button for an active call, the active call will be immediately parked at the Dpark slot associated with the Directed Call Park feature button.

Cisco Unified Communications Manager Administration Configuration Tips

For assisted directed call park to work, you must configure a BLF Directed Call Park button.

GUI Changes

There are no GUI changes for this feature.

Service Parameter and Enterprise Parameter Changes

No service or enterprise parameter changes exist for this feature.

Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 8.0(1), you can use this feature.

Serviceability Considerations

No 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

Only the Cisco Unified IP Phones 8961, 9951, and 9971 (SIP phones only) support assisted directed call park.

For More Information

Cisco Unified Communications Manager Features and Services Guide

Audio Codec Preference By Sound Quality

Description

Regions provide capacity controls for Cisco Unified Communications Manager multisite deployments where you may need to limit the bandwidth for individual calls that are sent across a WAN link, but where you want to use a higher bandwidth for internal calls. Additionally, the system uses regions also for applications that only support a specific codec; for example, an application that only uses G.711. Use regions to specify the maximum transport-independent bit rate that is used for audio and video calls within a region and between regions; in this case, codecs with higher bit rates do not get used for the call.

Cisco Unified Communications Manager prefers codecs with better audio quality. For example, despite having a maximum bit rate of 32 kb/s, G.722.1 sounds better than some codecs with higher bit rates, such as G.711, which has a bit rate of 64 kb/s.

The audio codec preference feature orders the audio preference table (Table 2-3) for the default low-loss case by sound quality, and the table adds a separate preference list for the lossy case. For audio and video calls, Cisco Unified Communications Manager uses the preference order of codecs in Table 2-3. When you configure the maximum audio bit rate setting in the Region Configuration window (or use the service parameter in the Service Parameter Configuration window), this setting serves as a filter. When an audio codec is selected for a call, Cisco Unified Communications Manager takes the matching codecs from both sides of a call leg, filters out the codecs that exceed the configured maximum audio bit rate, and then picks the preferred codec among the codecs that are remaining in the list.

Table 2-3 Audio Codec Preference Order for Cisco Unified Communications Manager 8.0(1) 

If Low Loss Is Configured for Link Loss Type
If Lossy Is Configured for Link Loss Type

AAC-LD—256 kb/s

AAC-LD—256 kb/s

L16—256 kb/s

L16—256 kb/s

G.722 64k—64 kb/s

iSAC—32 kb/s

iSAC—32 kb/s

G.722 64k—64 kb/s

G.722.1 32k—32 kb/s

G.722.1 32k—32 kb/s

G.722 —56 kb/s

G.722 —56 kb/s

G.722.1—24 kb/s

G.722.1—24 kb/s

G.722—48 kb/s

G.722—48 kb/s

G.711 mu-law 64 k—64 kb/s

G.711 mu-law 64 k—64 kb/s

G.711 A-law 64k—64 kb/s

G.711 A-law 64k—64 kb/s

G.711 mu-law 56k—56 kb/s

G.711 mu-law 56k—56 kb/s

G.711 A-law 56k—56kb/s

G.711 A-law 56k—56kb/s

iLBC—16 kb/s

iLBC—16 kb/s

G.728—16 kb/s

G.728—16 kb/s

GSM Enhanced Full Rate—13 kb/s

GSM Enhanced Full Rate—13 kb/s

GSM Full Rate—13 kb/s

GSM Full Rate—13 kb/s

G.729b—8 kb/s

G.729b—8 kb/s

G.729ab—8 kb/s

G.729ab—8 kb/s

G.729—8 kb/s

G.729—8 kb/s

G.729a—8 kb/s

G.729a—8 kb/s

GSM Half Rate—7 kb/s

GSM Half Rate—7 kb/s

G.723.1—7 kb/s

G.723.1—7 kb/s


For calls made between Cisco Unified Communications Manager and previous versions of Cisco Unified Communications Manager over SIP intercluster trunks, the Cisco Unified Communications Manager that makes the SDP Answer chooses the codec. Because of SIP Delayed Offer support, the Cisco Unified Communications Manager that initiates or resumes the call is the one that makes the SDP Answer, and hence, it is the one that determines the codec for the call.

For audio calls that involve H.323 intercluster trunks, Cisco Unified Communications Manager uses the preference list of codecs in Table 2-3 only if both sides of the call run Cisco Unified Communications Manager 8.0(1). If at least one side of the call runs a previous version of Cisco Unified Communications Manager, the codec list from Table 2-4 is used.

Table 2-4 Audio Codec Preference Order for previous versions of Cisco Unified Communications Manager 

If Low Loss Is Configured for Link Loss Type
If Lossy Is Configured for Link Loss Type

---

iLBC—16 kb/s

AAC-LD—256 kb/s

AAC-LD—256 kb/s

L16—256 kb/s

L16—256 kb/s

G.722.1 24k—24 kb/s

G.722.1 24k—24 kb/s

G.722.1 32k—32 kb/s

G.722.1 32k—32 kb/s

G.722 64k—64 kb/s

G.722 64k—64 kb/s

G.711 mu-law 64k—64 kb/s

G.711 mu-law 64k—64 kb/s

G.711 A-law 64k—64 kb/s

G.711 A-law 64k—64 kb/s

G.722 56k—56 kb/s

G.722 56k—56 kb/s

G.711 mu-law 56k—56 kb/s

G.711 mu-law 56k—56 kb/s

G.711 A-law 56k—56 kb/s

G.711 A-law 56k—56 kb/s

G.722 48k—48 kb/s

G.722 48k—48 kb/s

iLBC—16 kb/s

---

G.728—16 kb/s

G.728—16 kb/s

GSM Enhanced Full Rate—13 kb/s

GSM Enhanced Full Rate—13 kb/s

GSM Full Rate—13 kb/s

GSM Full Rate—13 kb/s

G.729b—8 kb/s

G.729b—8 kb/s

G.729ab—8kb/s

G.729ab—8kb/s

G.729—8 kb/s

G.729—8 kb/s

G.729a—8 kb/s

G.729a—8 kb/s

GSM Half Rate—7 kb/s

GSM Half Rate—7 kb/s

G.723.1—7 kb/s

G.723.1—7 kb/s


Cisco Unified Communications Manager Administration Configuration Tips

When you configure the maximum audio bit rate setting in the Region Configuration window (or use the service parameter in the Service Parameter Configuration window), this setting serves as a filter. When an audio codec is selected for a call, Cisco Unified Communications Manager takes the matching codecs from both sides of a call leg, filters out the codecs that exceed the configured maximum audio bit rate, and then picks the preferred codec among the codecs that are remaining in the list.

Ensure that your devices are configured to only advertise codecs that they support, with the expectation that any one of the codecs may be negotiated.

GUI Changes

In the Region Configuration window, the Audio Codec setting has been renamed to the Max Audio Bit Rate setting. When you configure the maximum audio bit rate setting in the Region Configuration window (or use the service parameter in the Service Parameter Configuration window), this setting serves as a filter. When an audio codec is selected for a call, Cisco Unified Communications Manager takes the matching codecs from both sides of a call leg, filters out the codecs that exceed the configured maximum audio bit rate, and then picks the preferred codec among the codecs that are remaining in the list.

In the Region Configuration window, the Video Call Bandwidth setting has been changed to the Max Video Call Bit Rate (Includes Audio) setting.

Service Parameter and Enterprise Parameter Changes

The Intraregion Audio Codec Default and Interregion Audio Codec Default service parameters have changed to the Default Intraregion Max Audio Bit Rate and Default Interregion Max Audio Bit Rate service parameters.

The Intraregion Video Call Bandwidth Default and Interregion Video Call Bandwidth Default service parameters have changed to the Default Intraregion Max Video Call Bit Rate and Default Interregion Max Video Call Bit Rate service parameters.

The Link Loss Type Default service parameter has changed to the Default Intraregion and Interregion Link Loss Type service parameter.

Installation/Upgrade (Migration) Considerations

In releases before Cisco Unified Communications Manager 8.0(1), Cisco Unified Communications Manager used the audio codec configuration for the region pair to choose the preferred audio codec for the call by identifying the highest bit rate codecs available after bandwidth filtering. In releases before Cisco Unified Communications Manager 8.0(1), this practice was acceptable for older codecs because the higher the bit rate, the higher the quality. With the support of additional codecs, such as G.722.1 and iLBC, Cisco Unified Communications Manager cannot rely exclusively on the codec type specified because codecs with lower bit rates may provide better sound quality for a call.

If you configured the Audio Codec or Video Call Bandwidth settings in a previous release, the values that you configured automatically migrate to an equivalent value for the Max Audio Bit Rate and the Max Video Call Bit Rate (Includes Audio) settings.

After an upgrade, be aware of the following codec changes:

The preference list in Table 2-3 is new for 8.0(1). The codec, iSAC, which is new for 8.0(1), is added to Table 2-3.

G.722 64k is promoted above G.722.1.

G.722 is always promoted over G.711.

iLBC is no longer the top choice for the Lossy case.

Serviceability Considerations

No 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

No user tips exist for this feature.

For More Information

iSAC Codec Support

Region Configuration, Cisco Unified Communications Manager Administration Guide

System-Level Configuration Settings, Cisco Unified Communications Manager System Guide

Call Control Discovery

This section contains information on the following topics:

Description for Call Control Discovery

Cisco Unified Communications Manager Administration Configuration Tips for Call Control Discovery

Configuration Checklist for Call Control Discovery

Feature Parameter Changes for Call Control Discovery

GUI Changes

Installation/Upgrade (Migration) Considerations

Serviceability Considerations for Call Control Discovery

CAR/CDR Considerations for Call Control Discovery

Security Considerations for Call Control Discovery

User Tips for Call Control Discovery

For More Information on Call Control Discovery

Description for Call Control Discovery

The call control discovery feature leverages the Service Advertisement Framework (SAF) network service, a proprietary Cisco service, to facilitate dynamic provisioning of inter-call agent information. By adopting the SAF network service, the call control discovery feature allows Cisco Unified Communications Manager to advertise itself along with other key attributes, such as directory number patterns that are configured in Cisco Unified Communications Manager Administration, so other call control entities that also use SAF network can use the advertised information to dynamically configure and adapt their routing behaviors; likewise, all entities that use SAF advertise the directory number patterns that they own along with other key information, so other remote call-control entities can learn the information and adapt the routing behavior of the call.

Table 2-5 provides a brief overview of terminology that is associated with the call control discovery feature.

Table 2-5 Call Control Discovery Terminology 

Terminology
Description

Call control discovery (CCD) advertising service

Resides in Cisco Unified Communications Manager

Advertises the PSTN failover configuration and hosted DN patterns along with the SAF trunk access information for the local Cisco Unified Communications Manager cluster to the remote call-control entities that use the SAF network.

Configured under Call Routing > Call Control Discovery > Advertising Service in Cisco Unified Communications Manager Administration

Call control discovery (CCD) requesting service

Resides in Cisco Unified Communications Manager

Allows the local Cisco Unified Communications Manager to listen for advertisements from remote call-control entities that use the SAF network.

Ensures that learned patterns (hosted DN patterns from remote call-control entities) get inserted into digit analysis on the local Cisco Unified Communications Manager

Performs load balancing for calls to learned patterns

Handles withdrawals for Cisco Unified Communications Manager from the SAF network

Configured under Call Routing > Call Control Discovery > Requesting Service in Cisco Unified Communications Manager Administration.

Hosted DN patterns

Directory number patterns that belong to the local call-control entity

Tip For example, hosted DN patterns that you configure in Cisco Unified Communications Manager Administration under Call Routing > Call Control Discovery > Hosted DN Pattern are directory numbers pattern ranges for the local Cisco Unified Communications Manager cluster that you want to advertise to remote call-control entities.

For the local Cisco Unified Communications Manager, published by the CCD advertising service to the SAF forwarder.

Learned patterns

Patterns that are inserted into digit analysis by the CCD requesting service

Can be manually purged or blocked on the local Cisco Unified Communications Manager

Viewed in RTMT

SAF forwarder

Cisco IOS router

Notifies the local Cisco Unified Communications Manager when remote call-control entities advertise their hosted DNs patterns.

Receives publish requests from the local Cisco Unified Communications Manager cluster so that Cisco Unified Communications Manager can advertise the hosted DN patterns for the cluster.

SAF-enabled trunks

SAF-enabled trunks that are assigned to the CCD advertising service handle inbound calls from remote call-control entities that use the SAF network

SAF-enabled trunks that are assigned to the CCD requesting service handle outgoing calls to learned patterns


Cisco Unified Communications Manager Administration Configuration Tips for Call Control Discovery

Review the following considerations before you configure the call control discovery feature:

SAF Forwarders

Hosted DN Patterns and Hosted DN Groups

CCD Advertising and Requesting Services

SAF-Enabled Trunks


Tip This section does not describe all configuration considerations. This section provides high-level considerations that you should review before you configure the CCD configuration settings. Use this section in conjunction with the sections that are highlighted under the "Configuring Call Control Discovery" section in the Cisco Unified Communications Manager Features and Services Guide.


SAF Forwarders

Cisco recommends that you configure a primary and backup SAF forwarder for redundancy.

When you configure a SAF forwarder or SAF security profile, some configuration in Cisco Unified Communications Manager Administration must match the configuration that you entered on the Cisco IOS router.

Cisco Unified Communications Manager supports the following deployment models for SAF forwarders: clusterwide or node-specific. Before you configure SAF forwarders, review the "Call Control Discovery" chapter in the Cisco Unified Communications Manager Features and Services Guide, which describes these deployment models.

You can only configure IPv4 for SAF forwarders.

Each SAF forwarder must have a unique IP address.

Cisco recommends that you do not update the SAF forwarder configuration when the Cisco Unified Communications Manager cannot connect to the SAF forwarder.

Hosted DN Patterns and Hosted DN Groups

Be aware that the PSTN Failover Strip Digits, PSTN Failover Prepend Digits, and Use HostedDN as PSTN Failover settings display in both the Hosted DN Group and Hosted DN Patterns Configuration windows. If you do not configure these settings in the Hosted DN Patterns Configuration window, the Hosted DN Group configuration applies to the hosted DN patterns.

Each hosted DN group covers one geophysical location advertising DN range.

In the Find and List window for Hosted DN Patterns, you can download a .cvs file so that you can add or update multiple hosted DN patterns for the call control discovery feature at the same time. Then, you can upload the patterns in the same window. (You can also add or update multiple hosted DN patterns in BAT.)

If you choose to replace the patterns when you upload the patterns, you lose all hosted DN patterns.

If invalid or bad data exists in the .csv file, the data gets ignored by Cisco Unified Communications Manager.

Cisco Unified Communications Manager allows you to configure up to 2,000 hosted DN patterns per cluster.

Each hosted DN pattern must be unique. Each hosted DN pattern can only exist in one hosted DN group.

The Find and List Hosted DN Patterns window allows you to identify which hosted DN patterns belong to a Hosted DN group.

CCD Advertising and Requesting Services

You cannot name any CCD advertising service and the CCD requesting service the same name in Cisco Unified Communications Manager Administration.

You must enable SAF on the trunk in Cisco Unified Communications Manager Administration and assign SAF-enabled trunks to the CCD advertising and requesting services in Cisco Unified Communications Manager Administration. Be aware that SAF-enabled SIP trunks only support UDP or TCP. If you want to do so, you can use the same SAF-enabled trunks for the CCD advertising service and CCD requesting service.

You can configure one CCD requesting service. You can configure as many CCD advertising services as you want.

Only one hosted DN group can be associated with one CCD advertising service.

The call control discovery feature relies on a route partition, which you configure in the CCD Partition window (Call Routing > Call Control Discovery > Partition). This route partition gets used exclusively by the call control discovery to ensure that all learned patterns get placed in digit analysis under the route partition. You assign this partition to the CCD requesting service.

Be aware that the CCD partition does not display under Call Routing > Class of Control > Partition in Cisco Unified Communications Manager Administration.


Tip Updating the Learned Pattern Prefix field or Route Partition field in the CCD Requesting Service Configuration window may impact system performance because the digit-analysis master routing table automatically gets updated when these fields are changed. To avoid system performance issues, Cisco recommends that you update these fields during off-peak hours.


After you make changes to the configuration for the CCD advertising and requesting services, click Save. You do not need to click the Reset button in these windows unless you want the following events to occur:

For the CCD Advertising Service—The Reset button in the CCD Advertising Service Configuration window triggers the call control discovery advertising service to withdraw existing publishing requests and to publish all the related information again.

For the CCD Requesting Service—The Reset button in the CCD Requesting Service Configuration window causes the requesting service to remove the learned patterns from the local cache and for the requesting service to subscribe to the SAF network again. By clicking the Reset button in the CCD Requesting Service Configuration window, Cisco Unified Communications Manager can learn patterns again.

To minimize the impact to your network, Cisco recommends that you click the Reset button in the CCD Advertising or CCD Requesting Configuration windows during off-peak hours.

Be aware that clicking Reset in the CCD Advertising and Requesting Service Configuration windows does not reset the trunk. You reset the trunk in the Trunk Configuration window.

When you delete a CCD advertising service, all hosted DN patterns that are advertised with each assigned trunk get unpublished.

When you delete the CCD requesting service, all learned patterns get unregistered from the local cache and digit analysis.

If you want a user to make outbound calls to learned patterns that are advertised by remote call-control entities, ensure that the calling search space that you assign to the device contains the route partition that is assigned to the CCD requesting service.

When the Cisco Unified Communications Manager cannot connect to the SAF forwarder, Cisco recommends that you do not update the configuration for the CCD requesting service or CCD advertising service, unless these services are inactive; that is, the Activated Feature check box is unchecked in Cisco Unified Communications Manager Administration. If you update the services when Cisco Unified Communications Manager cannot connect to the SAF network and these services are active, problems may occur; for example, patterns may not be classified correctly as unreachable or reachable, duplicate or stale patterns may exist, and so on.

Make sure that the call-control entities do not advertise the same hosted DN patterns.

If the call-control entities advertise the same hosted DN patterns, problems may occur; for example, a call routing loop may occur between advertising clusters when these clusters make calls to learned patterns by using a calling search space where the learned pattern partition is in front of the locally configured static partition.

SAF-Enabled Trunks

One configured SAF-enabled H.323 trunk and one configured SAF-enabled SIP trunk can serve all SIP and H.323 calls to learned patterns for one cluster.

Make sure that you apply the configuration to the SAF-enabled trunk before you assign the trunk to the CCD advertising or requesting service. You apply the configuration in the Trunk Configuration window.

If you do not select/assign a SAF-enabled trunk when you configure the CCD requesting service, the CCD requesting service does not get created and patterns do not get learned.

If you assign both a H.323 and a SIP SAF-enabled trunk to the CCD requesting service, make sure that the same Cisco Unified Communications Manager group exists in the device pool that is assigned to the trunk.

To support clustering over WAN deployments, configure different Cisco Unified Communications Manager groups to associate with sets of SAF-enabled trunks.

To ensure redundancy and reduce call-processing traffic, Cisco recommends that no more than two nodes exist in the Cisco Unified Communications Manager group for the device pool that you assign to the SAF-enabled trunk.

If a trunk is assigned to a route group or associated with a route pattern, you cannot enable SAF on the trunk. Likewise, if you enable SAF on the trunk, you cannot assign the trunk to a route group or associate the trunk with a route pattern.

Verify that the SIP trunk has a security profile of Nonsecure before you enable SAF on the trunk. You cannot enable SAF on SIP trunks that use authenticated or encrypted security profiles.

Resetting a SAF-enabled trunk that is assigned to the CCD advertising service causes the CCD advertising service to unpublish the hosted DN patterns and republish with a different service ID for that trunk.

If different SAF-enabled trunks are configured to use different Cisco Unified Communications Manager groups, the inbound and outbound SAF-related call traffic gets distributed among different Cisco Unified Communications Manager nodes.

If a Cisco Unified Communications Manager group changes for the SAF-enabled trunk, the CCD advertising service sends unpublish requests to the SAF network; in addition, the CCD requesting service removes the learned patterns from the local cache and digit analysis because no trunk runs on this Cisco Unified Communications Manager node. After the CCD advertising service and/or requesting service start on the new nodes, the advertising service sends a publish request to the SAF network, and the requesting service sends a subscribe request to the SAF network.

If you change the device pool of the SAF-enabled trunk, the CCD advertising service sends unpublish requests to the SAF network; in addition, the CCD requesting service removes the learned patterns from the local cache and digit analysis because no trunk runs on this Cisco Unified Communications Manager node. After the CCD advertising service and/or requesting service start on the new nodes, the advertising service sends a publish request to the SAF network, and the requesting service sends a subscribe request to the SAF network.

If you want to delete a SAF-enabled trunk from Cisco Unified Communications Manager Administration, you must unassign the trunk from the CCD advertising service and/or CCD requesting service before you delete it from the Trunk Configuration window.

Be aware that resetting a SAF-enabled trunk or changing the Cisco Unified Communications Manager group for the trunk impacts the CCD advertising and requesting services. For example, if you reset a trunk and the CCD requesting service cannot access the trunk after 10 seconds have passed, all learned patterns get purged from digit analysis and from the local cache, and the requesting process stops.

Miscellaneous Considerations

To ensure PSTN failover, configure a route pattern and assign the route pattern to the gateway.

If your cluster does not support E.164, you must configure translation patterns so that your users can dial E.164 numbers.

You can view purged and blocked learned patterns in the Find and List Blocked Learned Patterns window in Cisco Unified Communications Manager Administration. If you delete a blocked pattern from Cisco Unified Communications Manager Administration, Cisco Unified Communications Manager can relearn those patterns if they are still available in the SAF network (and if the maximum number of learned patterns has not been reached for the cluster).

Learned patterns are viewed in RTMT.

Configuration Checklist for Call Control Discovery

Table 2-6 provides a checklist on how to configure call control discovery.

Table 2-6 Call Control Discovery Configuration Checklist 

Configuration Steps
Related Procedures and Topics

Step 1 

If you have not already done so, configure the Cisco IOS router as the SAF forwarder.

Refer to the documentation that supports your Cisco IOS router; for example, refer to the Cisco IOS Service Advertisement Framework Configuration Guide or the Cisco IOS Service Advertisement Framework Command Reference.

Cisco Feature Navigator allows you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn.

Step 2 

Configure the SAF security profile for the SAF forwarder (Advanced Features > SAF > SAF Security Profile). You can configure more than one SAF security profile in Cisco Unified Communications Manager Administration.

A SAF forwarder, which is a Cisco IOS router that you configured for SAF, handles the publishing requests for the local Cisco Unified Communications Manager cluster and the service advertisements from remote call-control entities.

Description for Call Control Discovery

Table 2-8

Cisco Unified Communications Manager Administration Configuration Tips for Call Control Discovery

Step 3 

Configure the SAF forwarders in Cisco Unified Communications Manager Administration (Advanced Features > SAF > SAF Forwarder). Cisco recommends that you configure a primary and backup SAF forwarder for failover support.

Description for Call Control Discovery

Table 2-9

Cisco Unified Communications Manager Administration Configuration Tips for Call Control Discovery

Step 4 

Configure SAF-enabled SIP and/or H.323 intercluster (non-gatekeeper controlled) trunks (Device > Trunk).

The local Cisco Unified Communications Manager cluster uses SAF-enabled trunks that are assigned to the CCD requesting service to route outbound calls to remote call-control entities that use the SAF network.

The Cisco Unified Communications Manager cluster advertises the SAF-enabled trunks that are assigned to the CCD advertising service along with the range of hosted DNs; therefore, when a user from a remote call-control entity makes an inbound call to a learned pattern on this Cisco Unified Communications Manager, this Cisco Unified Communications Manager receives the inbound call from this SAF-enabled trunk and routes the call to the correct DN.

Description for Call Control Discovery

Cisco Unified Communications Manager Administration Configuration Tips for Call Control Discovery

Step 5 

Configure the Hosted DN groups. Cisco recommends that you group the hosted DN patterns by location; for example, hosted DN patterns that represent different zip codes for a city may get grouped together. (Call Routing > Call Control Discovery > Hosted DN Group)

Hosted DN groups are a collection of hosted DN patterns that you group together in Cisco Unified Communications Manager Administration. You assign a hosted DN group to a CCD advertising service in Cisco Unified Communications Manager Administration, and the CCD advertising service publishes all the hosted DN patterns that are a part of the hosted DN group.

You can only assign one Hosted DN group to one call control discovery advertising service.

Description for Call Control Discovery

Table 2-10

Cisco Unified Communications Manager Administration Configuration Tips for Call Control Discovery

Step 6 

Configure the Hosted DN patterns. (Call Routing > Call Control Discovery > Hosted DN Pattern)

Hosted directory number (DN) patterns are patterns that represent directory numbers that belong to a call-control entity; for example, hosted DN patterns that you configure in Cisco Unified Communications Manager Administration are a range of directory numbers that belong to the local Cisco Unified Communications Manager cluster that you want to advertise to remote call-control entities. The CCD advertising service publishes the hosted DN patterns to the active SAF forwarder.

Description for Call Control Discovery

Table 2-11

Cisco Unified Communications Manager Administration Configuration Tips for Call Control Discovery

Step 7 

To publish the hosted DNs for the local Cisco Unified Communications Manager cluster, configure the Call Control Discovery Advertising service. (Call Routing > Call Control Discovery > Advertising Service) You can configure as many CCD advertising services as you want.

The call control discovery advertising service, which resides in Cisco Unified Communications Manager, allows the local Cisco Unified Communications Manager cluster to advertise its hosted DNs and the PSTN failover configuration to the remote call-control entities that use the SAF network.

Description for Call Control Discovery

Table 2-12

Cisco Unified Communications Manager Administration Configuration Tips for Call Control Discovery

Step 8 

Configure a partition that is used specifically for call control discovery. (Call Routing > Call Control Discovery > Partition)

This route partition gets used exclusively by the CCD requesting service to ensure that all learned patterns get placed in digit analysis under the route partition.

You assign the partition to the CCD Requesting Service in Cisco Unified Communications Manager Administration.

Tip The partition that you assign to the CCD requesting service must belong to a calling search space that the devices can use for calling the learned patterns, so assign the partition to the calling search space that you want the devices to use. If you do not assign a calling search space that contains the partition to the device, the device cannot call the learned patterns.

Description for Call Control Discovery

Table 2-13

Cisco Unified Communications Manager Administration Configuration Tips for Call Control Discovery

Step 9 

To ensure that the local Cisco Unified Communications Manager cluster can listen for advertisements from the SAF network, configure one call control discovery requesting service. (Call Routing > Call Control Discovery > Requesting Service) You can only configure one CCD requesting service.

The call control discovery requesting service, which resides in the local Cisco Unified Communications Manager, allows the local Cisco Unified Communications Manager to listen for hosted DN advertisements from remote call-control entities that use the SAF network.

Description for Call Control Discovery

Table 2-14

Cisco Unified Communications Manager Administration Configuration Tips for Call Control Discovery

Step 10 

If you have not already done so, configure your remote call-control entity to use the SAF network; for example, configure Cisco Unified Communications Manager Express or other Cisco Unified Communications Manager clusters for the SAF network.

Refer to the documentation that supports your remote call-control entity; for example, the Cisco Unified Communications Manager Express documentation.

Step 11 

After you configure call control discovery, you may block learned patterns that remote call-control entities send to the local Cisco Unified Communications Manager. (Call Routing > Call Control Discovery > Blocked Learned Patterns)

Description for Call Control Discovery

Table 2-15

Cisco Unified Communications Manager Administration Configuration Tips for Call Control Discovery

Feature Parameter Changes for Call Control Discovery

To access the feature parameters that support the call control discovery feature, choose Call Routing > Call Control Discovery > Feature Configuration. Table 2-7 describes the service parameters for the call control discovery feature.

Table 2-7 Call Control Discovery Feature Parameters 

Feature Parameter
Description

CCD Maximum Number of Learned Patterns

This parameter specifies the number of patterns that this Cisco Unified Communications Manager cluster can learn from the SAF network. The higher the number of allowed learned patterns, the more memory and CPU processing power is required for your server. When Cisco Unified Communications Manager attempts to learn more patterns than is specified in the parameter configuration, the alarm, CCDLearnedPatternLimitReached, gets issued.

You can enter a number from 1 to 20000, which is the default.

CCD Learned Pattern IP Reachable Duration

This parameter specifies the number of seconds that learned patterns stay active (reachable) before Cisco Unified Communications Manager marks those patterns as unreachable. For example, you configure 20 seconds for this parameter; when Cisco Unified Communications Manager cannot communicate with the SAF forwarder after 20 seconds, all calls to learned patterns fail over to the PSTN until IP connectivity to the SAF forwarder gets restored. During the PSTN failover, Cisco Unified Communications Manager cannot learn new patterns. After the time that you specified for this parameter elapses, Cisco Unified Communications Manager marks the learned patterns as unreachable. Use this parameter with the CCD PSTN Failover Duration parameter, which allows patterns that have been marked as unreachable to be reached through PSTN failover.

You can enter a number (seconds) from 0 to 300; the default equals 60 seconds.

CCD PSTN Failover Duration

This parameter specifies the number of minutes that calls to unreachable/inactive learned patterns are routed through the PSTN gateway and then purged from the system. The configuration for this parameter does not take effect until after the timer expires for the CCD Learned Pattern IP Reachable Duration parameter. The expiration of the CCD Learned Pattern IP Reachable Duration parameter indicates that IP connectivity fails between the SAF forwarder and Cisco Unified Communications Manager, and all learned patterns get marked as unreachable. Then, when the duration expires for CCD PSTN Failover Duration parameter, all learned patterns get purged from the system and calls to purged patterns are rejected (caller hears reorder tone or "number is unavailable" announcement).

Setting this parameter to 0 means that PSTN failover cannot occur; that is, if the SAF forwarder cannot be reached for the number of seconds that you defined in the CCD Learned Pattern IP Reachable Duration parameter, no failover option is provided over the PSTN, and calls to learned patterns immediately fail. Setting this parameter to 525600 means that PSTN failover never expires and learned patterns never get purged because of IP connectivity issues.

You can enter a number (minutes) from 0 to 525600; the default equals 2880.

Issue Alarm for Duplicate Learned Patterns

This parameter determines whether Cisco Unified Communications Manager issues the alarm, DuplicateLearnedPattern, when it learns duplicate patterns from different remote call-control entities on the SAF network. The default equals False.

CCD Stop Routing On Unallocated Unassigned Number

This parameter determines whether Cisco Unified Communications Manager continues to route calls to a remote call-control entity, such as a Cisco Unified Communications Manager cluster or Cisco Unified Communications Manager Express, when the remote call-control entity rejects the call with the cause code for Unallocated/Unassigned Number. Be aware that an unallocated number represents a hosted DN that does not exist in the current call control entity. The default equals True.

If the parameter is set to True, the call is released as soon as Cisco Unified Communications Manager receives the cause code from the remote call-control entity. If the parameter is set to False, when Cisco Unified Communications Manager extends the call to the learned pattern and the remote call-control entity sends the unallocated number cause value, Cisco Unified Communications Manager attempts to find another reachable IP address for the remote cluster for this learned pattern. If any reachable remote destination is available, Cisco Unified Communications Manager tries to extend the call to the IP address of the available reachable remote cluster.


GUI Changes

The following GUI changes support the call control discovery feature.

System > Device Pool—Added incoming called party settings for H.323 gateways and trunks.

Advanced Features > SAF > SAF Security Profile—See Table 2-8.

Advanced Features > SAF > SAF Forwarder—See Table 2-9.

Call Routing > Call Control Discovery > Hosted DN Group—See Table 2-10.

Call Routing > Call Control Discovery > Hosted DN Patterns—See Table 2-11.

Call Routing > Call Control Discovery > Advertising Service—See Table 2-12.

Call Routing > Call Control Discovery > Partition—See Table 2-13.

Call Routing > Call Control Discovery > Requesting Service—See Table 2-14.

Call Routing > Call Control Discovery > Blocked Learned Patterns—See Table 2-15.

Device > Trunk—Added incoming called party settings for H.323 trunks. Added Enable SAF check box for H.323 (non-gatekeeper controlled) trunks. Added Trunk Service Type drop-down list box for SIP trunks.

Table 2-8 SAF Security Profile Configuration Settings 

Field
Description

Name

Enter the name of the SAF security profile. The name that you enter displays in the Find and List Security Profile window and in the SAF Security Profile drop-down list box in the SAF Forwarder Configuration window. Valid entries include alphanumeric characters, hyphen, period, underscore, and blank spaces.

You can configure up to 50 characters.

Description

Enter a description for the SAF security profile. You can enter all characters except for \, ", < >, &, and %.

You can configure up to 128 characters.

User Name

Enter a value that you want Cisco Unified Communications Manager to include in requests when it contacts the SAF forwarder.

Tip To ensure that the Cisco Unified Communications Manager can register with the SAF forwarder, enter the same user name that you entered on the router (SAF forwarder). The user name is case sensitive, so enter the user name exactly as you entered it on the SAF forwarder.

The value that you enter represents the shared secret for message integrity checks between Cisco Unified Communications Manager and the SAF forwarder. The user name gets included in any request from Cisco Unified Communications Manager that contains the MESSAGE-INTEGRITY attribute.

User Password

Enter a value that you want Cisco Unified Communications Manager to include in requests when it contacts the SAF forwarder.

Tip To ensure that the Cisco Unified Communications Manager can register with the SAF forwarder, enter the same password that you entered on the router (SAF forwarder). The password is case sensitive, so enter the password exactly as you entered it on the SAF forwarder.

Table 2-9 SAF Forwarder Configuration Settings 

Field
Description

Name

Enter the name of the SAF forwarder. Valid entries include alphanumeric characters, hyphen, period, and underscore. You can enter up to 50 characters.

The value that you enter in this field gets used to classify SAF forwarder records in the database. The value that you enter displays in the Find and List SAF Forwarder window when you perform a search.

Description

Enter a description for the SAF forwarder. You can enter all characters except for \, ", < >, &, and %. You can enter up to 128 characters.

Client Label

The client label allows the SAF forwarder to identify the Cisco Unified Communications Manager node. Valid entries include alphanumeric characters, underscore, and @. You can enter up to 50 characters.

Each Cisco Unified Communications Manager node that you select to interact with this SAF forwarder includes its unique client label in the registration message that it sends to the SAF forwarder. When the SAF forwarder receives the registration message, it verifies whether you configured the client label on the SAF forwarder.

When you configure a single SAF forwarder for the entire cluster, all nodes in the cluster use the same SAF forwarder configuration and register to the same SAF forwarder. To create a unique client label for the nodes in the cluster, you can append @ to the client label value, which ensures that the registration message includes the basename followed by @<nodeid>. For example, you enter abcde_ny@ for the client label for a two-node cluster that connects to one SAF forwarder, so the registration message includes abcde_ny@1 for node 1 or abcde_ny@2 for node 2.

If you do not append the @ to the client label value, you do not need to configure the basename parameter for the client label on the router, but you do need to configure the client label on the router. If you append the @ to the client label value, you must configure the basename parameter with the client label on the router.

Tip If more than one Cisco Unified Communications Manager node displays in the Selected Cisco Unified Communications Managers pane under the Showed Advanced section, append @ to the client label value; otherwise, errors may occur because each node uses the same client label to register with the SAF forwarder.

SAF Security Profile

Choose the SAF security profile that you want to apply to this SAF forwarder. The username and password from the security profile get sent to the SAF forwarder, so choose a security profile that contains a username and password that the SAF forwarder will accept. (The SAF forwarder must be configured to use the same username and password.)

SAF Forwarder Address

Enter the IPv4 address of the SAF forwarder.

SAF Forwarder Port

Enter the port number that Cisco Unified Communications Manager uses to establish a connection with the SAF forwarder. The default setting is 5050.

The port that you enter must match the port number that you configure on the SAF forwarder. The port range on the SAF forwarder is 1024 to 65535.

Enable TCP Keep Alive

Check the Enable TCP Keep Alive check box to ensure that Cisco Unified Communications Manager gets notified if the TCP connection between the SAF forwarder and Cisco Unified Communications Manager fails. If this check box is unchecked, the Cisco Unified Communications Manager does not get notified that the TCP connection fails until the SAF forwarder keepalive timer expires (configured on the SAF forwarder).

Cisco recommends that this check box remains checked.

Show/Hide Advanced

SAF Reconnect Interval

Enter the time (in seconds) that Cisco Unified Communications Manager allows to pass before it attempts to reconnect to the SAF forwarder after a connection failure. Enter a value between 0 and 500. The default value is 20.

SAF Notifications Window Size

Enter the number of outstanding Notify requests that the SAF forwarder can maintain at the same time to the Cisco Unified Communications Manager. The default value is 7. You can enter a number between 0 to 255.

If you enter 0 in this field, the SAF forwarder does not send any notification to this Cisco Unified Communications Manager, but the Cisco Unified Communications Manager can still publish hosted DNs to the SAF network if the CCD advertising service is configured and active.

Available Cisco Unified Communications Managers

This setting works with the Selected Cisco Unified Communications Managers pane.

Every node in the Available Cisco Unified Communications Managers pane can connect to the SAF forwarder that you configure in the SAF Forwarder Configuration window.

If you want to do so, you can assign a particular node to this SAF forwarder so that the node prioritizes this SAF forwarder over other configured SAF forwarders. You assign the node to the SAF forwarder by moving the node to the Selected Cisco Unified Communications Managers pane. To move a node to or from the Available Cisco Unified Communications Managers pane, highlight the node and click the up or down arrow.

If you have assigned a node to two SAF forwarders, the assigned node does not display in the pane because you can only assign a node to two SAF forwarders. For example, three SAF forwarders exist—forwarder1, forwarder2, and forwarder3. You assign node_2 to forwarder1 and forwarder3, which means that node_2 does not display in the Available Cisco Unified Communications Managers pane for forwarder2.

Selected Cisco Unified Communications Managers

Use this pane for cluster over WAN (COW) configurations.

This pane displays the nodes that prioritize this SAF forwarder over other configured SAF forwarders. For example, if node_1 and node_2 display in this pane for forwarder1, then node_1 and node_2 always choose forwarder1 first, even though you may have configured other SAF forwarders.

To move a node to or from the Selected Cisco Unified Communications Managers pane, highlight the node and click the up or down arrow below the Available Cisco Unified Communications Managers pane. To order the nodes in the pane, highlight the node and click the up or down arrow to the right of the pane.


Table 2-10 Hosted DN Group Configuration Settings 

Field
Description

Name

Enter the name of the hosted DN group. Valid entries include alphanumeric characters, hyphen, period, underscore, and blank space. You can enter up to 50 characters.

The value that you enter displays in the Find and List Hosted DN Group window, the Find and List Hosted DN Group window, the Hosted DN Group Configuration window, the Hosted DN Pattern Configuration window, and the CCD Advertising Service Configuration window,

Description

Enter a description for the hosted DN group. You can enter all characters except for \, ", < >, &, and %. You can enter up to 128 characters.

PSTN Failover Strip Digits

Enter the number of digits that you want stripped from the hosted DN if the call fails over to the PSTN. You can enter a value between 0 and 16.

PSTN Failover Prepend Digits

Enter the international escape character, +, or digits (0-9) that you want to add to the beginning of the directory number if the call fails over to the PSTN. You can enter up to 16 characters.

For example, enter an access or area code.

Use HostedDN as PSTN Failover

If you check this check box, Cisco Unified Communications Manager ignores the configuration that you entered in the PSTN Failover Strip Digits or PSTN Failover Prepend Digits.

If you do not need to strip digits from or prepend digits to the hosted DN when the call fails over to the PSTN, check the Use Hosted DN as PSTN Failover check box. When you check the check box, the PSTN Failover Strip Digits or PSTN Failover Prepend Digits fields display as disabled.

If you check the check box, the entity that makes the outbound call uses the original hosted DN range for PSTN failover.


Table 2-11 Hosted DN Pattern Configuration Settings 

Field
Description

Hosted Pattern

Enter the value for the hosted DN pattern, which can contain a maximum of 50 characters. The value that you enter in this field gets advertised by the CCD advertising service to remote call-control entities.

You can enter the international escape character + followed by pattern or dialable digits (0-9A-Da-d), pattern ([6-9]), wildcard character (X), or (^) with optional % or ! at the end of the entry.

Description

Enter a description for the hosted DN pattern. You can enter all characters except for \, ", < >, &, and %. You can enter up to 128 characters.

Hosted DN Group

Choose the Hosted DN group that you want to associate with this hosted DN pattern. If both of the following conditions are met, Cisco Unified Communications Manager applies the PSTN failover configuration for the hosted DN group to the hosted DN pattern:

In the Hosted DN Patterns window, you do not configure the PSTN Failover Strip Digits or PSTN Failover Prepend Digits fields (or you use the defaults).

In the Hosted DN Patterns window, you uncheck the Use HostedDN as PSTN Failover check box.

PSTN Failover Strip Digits

Enter the number of digits that you want to strip from the beginning of the directory number when an IP connection is not available and the call fails over to the PSTN. You can enter a value between 0 and 16.

When all of the following conditions are met, the hosted DN group configuration applies:

When you enter 0 in this field (or leave it blank)

When you leave the PSTN Failover Prepend Digits field blank

When the Use Hosted DN or PSTN Failover check box is unchecked

If the value that you enter in this field is longer than the hosted DN pattern, all digits in the pattern get stripped before any digits are prepended.

PSTN Failover Prepend Digits

Enter the international escape character, +, or the digits that you want to add to the beginning of the directory number if the call fails over to the PSTN. You can enter up to 16 characters.

When all of the following conditions are met, the hosted DN group configuration applies:

When you enter 0 in this field (or leave it blank)

When you leave the PSTN Failover Strip Digits field blank

When the Use Hosted DN or PSTN Failover check box is unchecked

Use HostedDN as PSTN Failover

If you do not need to strip digits from or prepend digits to the hosted DN when the call fails over to the PSTN, check the Use Hosted DN as PSTN Failover check box. When you check the check box, the PSTN Failover Strip Digits or PSTN Failover Prepend Digits fields display as disabled.

If you check the check box, the entity that makes the outbound call uses the original hosted DN range for PSTN failover.

If you are modifying the .csv file for hosted DN patterns, enter TRUE, which indicates that you want to use the Hosted DN exactly as is during PSTN failover, or FALSE, which indicates that you plan to strip digits from and prepend digits to the directory number during PSTN failover.


Table 2-12 CCD Advertising Service Configuration Settings 

Field
Description

Name

Enter the name of the CCD advertising service. Valid entries include alphanumeric characters, hyphen, period, underscore, and blank space. You can enter up to 50 characters.

You cannot name any CCD advertising service and the CCD requesting service the same name in Cisco Unified Communications Manager Administration, so ensure that the name is unique.

Description

Enter a description for the CCD advertising service. You can enter all characters except for \, ", < >, &, and %. You can enter up to 128 characters.

SAF SIP Trunk

Choose the SIP trunk that you want to use with this CCD advertising service. For inbound calls to the Cisco Unified Communications Manager, the call gets routed to the appropriate trunk that is advertised by the CCD advertising service.

If a trunk does not display in the drop-down list box, you did not choose Call Control Discovery from the Trunk Service Type drop-down list box when you first configured the trunk.

SAF H323 Trunk

Choose the H.323 trunk that you want to use with the CCD advertising service. For inbound calls to the Cisco Unified Communications Manager, the call gets routed to the appropriate trunk that is advertised by the CCD advertising service.

If a trunk does not display in the drop-down list box, verify that you checked the Enable SAF check box in the Trunk Configuration window for H.323 (non-gatekeeper controlled) trunks.

HostedDN Group

Choose the Hosted DN group that you want to associate with this CCD advertising service. The CCD advertising service advertises the hosted DN patterns that are a part of the hosted DN group.

You can only assign the hosted DN group to one CCD advertising service, so only unassigned hosted DN groups display in this drop-down list box.

Activated Feature

Ensure the Activated Feature check box is checked. If the Activated Feature check box is not checked, the CCD advertising service does not work.


Table 2-13 Partition Configuration Settings for Call Control Discovery 

Field
Description

Name

Enter the name of the partition that you plan to assign to the CCD requesting service. You can enter alphanumeric characters, underscore (_), hyphen (-), or space. You can enter up to 50 characters.

Description

Enter a description for the partition. You can enter all characters except for \, ", < >, &, and %. You can enter up to 128 characters.

Time Schedule

From the drop-down list box, choose a time schedule to associate with this CCD partition. The associated time schedule specifies when the partition is available to make outgoing calls to learned patterns for this cluster.

The default value specifies None, which implies that time-of-day routing is not in effect and the partition remains active at all times.

In combination with the Time Zone value in the following field, association of a partition with a time schedule configures the partition for time-of-day routing. The system checks outgoing calls to learned patterns under this partition against the specified time schedule.

Time Zone

Choose one of the following options to associate a CCD partition with a time zone:

Originating Device—If you choose this option, the system checks the partition against the associated time schedule with the time zone of the calling device.

Specific Time Zone—If you choose this option, choose a time zone from the drop-down list box. The system checks the partition against the associated time schedule at the time that is specified in this time zone.

When an outgoing call to a CCD learned pattern occurs, the current time on the Cisco Unified Communications Manager gets converted into the specific time zone set when one option is chosen. The system validates this specific time against the value in the Time Schedule field.


Table 2-14 CCD Requesting Service Configuration Settings 

Field
Description

Name

Enter the name of the CCD requesting service. Valid entries include alphanumeric characters, hyphen, period, underscore, and blank space. You can enter up to 50 characters.

You cannot name any CCD advertising service and the CCD requesting service the same name in Cisco Unified Communications Manager Administration, so ensure that the name is unique.

Description

Enter a description for the CCD requesting service. You can enter all characters except for \, ", < >, &, and %. You can enter up to 128 characters.

Route Partition

From the drop-down list box, choose the partition where you want the learned patterns to belong. The Route Partition field only supports the call control discovery feature; that is, all learned patterns automatically belong to the partition that you choose. This route partition gets used exclusively by the CCD requesting service to ensure that all learned patterns get placed in digit analysis under the route partition.

If you choose a partition besides None from the drop-down list box, the partition that you choose must belong to a calling search space that the devices can use for calling the learned patterns. In this case, if you do not assign a calling search space that contains the partition to the device, the device cannot call the learned patterns.

Tip Cisco strongly recommends that you configure a unique partition and assign it to the CCD requesting service. If you choose None from the Route Partition drop-down list box, all devices can call the learned patterns.
Tip Updating the Learned Pattern Prefix field or Route Partition field may impact system performance because the digit-analysis master routing table automatically gets updated when these fields are changed. To avoid system performance issues, Cisco recommends that you update these fields during off-peak hours.

Learned Pattern Prefix

The learned pattern prefix gets applied to the hosted DN pattern before the CCD requesting service registers with digit analysis. For outgoing calls to learned patterns, the learned pattern prefix gets stripped. Enter the prefix that you want to apply to the hosted DN pattern before the hosted DN pattern registers with digit analysis.

To make calls to the learned patterns, the phone user must dial the prefix followed by the learned pattern.

You can enter numbers, *, #, or +. You can enter up to 24 characters.

Tip Updating the Learned Pattern Prefix field or Route Partition field may impact system performance because the digit-analysis master routing table automatically gets updated when these fields are changed. To avoid system performance issues, Cisco recommends that you update these fields during off-peak hours.

PSTN Prefix

Enter the digits that will get prepended to the learned patterns when PSTN failover occurs. You can enter numbers, *, #, or +. You can enter up to 24 characters.

When calls to learned patterns fail over to the PSTN, the PSTN prefix gets added to the learned pattern after the PSTN failover settings that are advertised by the remote call-control entity for that learned pattern get applied.

Available SAF Trunks

A list of SAF-enabled trunks that are not assigned to the CCD requesting service display in the Available SAF Trunks pane. To assign the trunk to the CCD requesting service, highlight the service and click the down arrow to move the trunk to the Selected SAF Trunks pane.

Selected SAF Trunks

Cisco Unified Communications Manager routes outbound calls over SAF-enabled SIP or H.323 intercluster (non-gatekeeper controlled) trunks to remote call-control entities that use the SAF network; that is, the SAF-enabled trunks that you assign to the CCD requesting service manage outgoing calls to the learned DN patterns.

A list of SAF-enabled trunks that are assigned to the CCD requesting service display in the Selected SAF Trunks pane. You can assign as many SAF-enabled trunks as you want. Outbound calls get managed in a round-round fashion; that is, if the learned pattern supports both SIP and H.323 protocol, then outbound calls alternate between the trunk types.

To unassign the trunk from the CCD requesting service, highlight the service and click the up arrow to move the trunk to the Available SAF Trunks pane. To order the trunks in the pane, highlight the trunk and click the up and down arrows to the right of the pane.

Tip At least one SAF-enabled trunk must exist in the Selected SAF Trunks pane; otherwise, the CCD requesting service does not get started for the local cluster, and patterns do not get learned.

Activated Feature

Ensure the Activated Feature check box is checked. If the Activated Feature check box is not checked, the CCD requesting service does not work.


Table 2-15 Blocked Learned Pattern Configuration Settings 

Field
Description

Learned Pattern

Tip If you want Cisco Unified Communications Manager to block all patterns based on a prefix that gets prepended to the directory number, do not configure this field; instead, configure the Learned Pattern Prefix field.
Tip If you want to block all learned patterns from a particular remote call-control entity, do not configure this field; instead, configure the Remote Call Control Entity field or the Remote IP field.

For this field, enter the exact learned pattern that you want to block. Cisco Unified Communications Manager blocks a pattern based on exact match, so you must enter the exact pattern that you want Cisco Unified Communications Manager to block. For example, if you enter 235XX, Cisco Unified Communications Manager blocks 235XX patterns.

Learned Pattern Prefix

Tip If you configured the Learned Pattern field, do not configure the Learned Pattern Prefix field.

If you want to block a learned pattern based on the prefix that is prepended to the pattern, enter the prefix in this field. For example, if you want to block learned patterns that use +1, enter +1 in this field.

If you configure the Remote Call Control Entity or Remote IP fields, Cisco Unified Communications Manager blocks the learned patterns that use the particular prefix from the remote call-control entity that you configure (not from all remote call-control entities that advertise patterns with the prefix). If you do not enter a remote call-control entity or remote IP address, then all patterns that use the prefix get blocked.

Remote Call Control Entity

Enter the name of the remote call-control entity that advertises the pattern that you want to block. For example, you may enter the name of a cluster or a site.

If you leave this field and the Remote IP field blank, Cisco Unified Communications Manager blocks the learned pattern for all remote call-control entities that advertise the pattern.

Remote IP

Enter the IP address for the remote call-control entity where you want to block the learned pattern.

If you want to block a particular learned pattern from all remote call-control entities, you do not need to configure this field. Configure this field when you want to block a particular learned pattern from a specific remote call-control entity.


Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 8.0(1), you can configure this feature.

Serviceability Considerations for Call Control Discovery

The Learned Patterns and SAF Forwarders reports display in RTMT, as described in the "Learned Patterns and SAF Forwarder Reports" section on page 5-2. In addition, performance monitoring counters display for SAF, as described in the "Performance Monitoring Counters" section on page 5-6.

New alarms exist for call control discovery, as described in the "New SAF and CCD Alarms" section on page 5-64.

CAR/CDR Considerations for Call Control Discovery

New CDR support exists for call control discovery, as described in the "New CDR Fields to Support Call Control Discovery" section on page 5-15.

Security Considerations for Call Control Discovery

Cisco Unified Communications Manager uses digest authentication (without TLS) to authenticate to the SAF forwarder. When Cisco Unified Communications Manager sends a message to the SAF forwarder, Cisco Unified Communications Manager computes the SHA1 checksum and includes it in the MESSAGE-INTEGRITY field in the message.

You must configure a SAF security profile before you configure the SAF forwarder in Cisco Unified Communications Manager Administration.

AXL and CTI Considerations for Call Control Discovery

See the "Cisco Unified TAPI Developers Guide" section on page 6-1 and the "New APIs" section on page 6-3.

User Tips for Call Control Discovery

This feature does not directly impact the phone user.

For More Information on Call Control Discovery

Call Control Discovery, Cisco Unified Communications Manager Features and Services Guide

Incoming Called Party Settings for H.323 Gateways and Trunks

Call Waiting

This section contains information on the following topics:

Description

Service Parameter and Enterprise Parameter Changes

Installation/Upgrade (Migration) Considerations

Serviceability Considerations

BAT Considerations

CAR/CDR Considerations

Security Considerations

AXL and CTI Considerations

User Tips

For More Information

Description

The Call Waiting feature allows users to receive a second incoming call on the same line without disconnecting the first call. When the second call arrives, the user receives a brief call-waiting indicator tone, which is configured by using the Ring Setting (Phone Active) in the Directory Number Configuration window.

Configure call waiting in the Directory Number Configuration window in Cisco Unified Communications Manager Administration by setting the busy trigger (greater than 2) and maximum number of calls.

Service Parameter and Enterprise Parameter Changes

No service parameter or enterprise parameter changes exist for this feature.

Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 8.0(1), you can configure this feature.

Serviceability Considerations

No 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

No user tips exist for this feature.

For More Information

Cisco Unified Communications Manager Features and Services Guide

Caller ID Support on MGCP FXO Gateways

This section contains information on the following topics:

Description

Cisco Unified Communications Manager Administration Configuration Tips

GUI Changes

Service Parameter and Enterprise Parameter Changes

Installation/Upgrade (Migration) Considerations

Serviceability Considerations

BAT Considerations

CAR/CDR Considerations

Security Considerations

AXL and CTI Considerations

User Tips

For More Information

Description

Caller ID is now supported on MGCP FXO gateways. The new fields described in Table 2-31 configure Caller ID on MGCP FXO gateways.

Table 2-16 FXS/FXO Port Configuration Settings 

Field
Description
Device Information

Enable Caller ID
(for FXS ports)

To enable caller ID on this port, check this check box. Caller ID enables the port to report caller ID information, which can display on the destination phone when an incoming call arrives.

Ring Number
(for FXS ports)

Enter the number of rings after which the port will answer an incoming call. The valid values are 1 or 2 rings. The default value is 1 ring.

Timing Guard-out

Enter the timing guard-out value, in milliseconds. This setting is a time window after a call is disconnected that no outgoing call is allowed. The range of valid values is 300 ms to 3000 ms. The default value is 1000 ms. Caller ID support requires a value of 1000 ms or less.

Incoming Calling Party Settings

Clear Prefix Settings

To delete all prefixes for all calling party number types, click Clear Prefix Settings.

Default Prefix Settings

To enter the default value for all prefix fields at the same time, click Default Prefix Settings.

Strip Digits

Enter the number of preceding calling party number digits to remove. This value can also get configured by the device's device pool setting or the service parameter Incoming Calling Party Unknown Number Prefix - MGCP, depending on the port's Prefix setting.

To configure the service parameter Incoming Calling Party Unknown Number Prefix - MGCP to strip digits, enter a value in the format prefix:stripdigits, where prefix is the digits to prepend and stripdigits is the number of digits to strip.

Prefix

Enter the digits to prepend to the stripped calling party number. If you enter Default, the Strip Digits and Prefix settings get configured by the device pool Prefix setting. If the device pool Prefix setting is also set to Default, the Strip Digits and Prefix settings get configured by the service parameter Incoming Calling Party Unknown Number Prefix - MGCP.

Calling Search Space

Select a calling search space (CSS) from the drop-down list box that gets used to perform calling party number transformation. This setting can get overridden by the Use Devices Pool CSS field.

Use Device Pool CSS

Check this check box to use the device pool Unknown Number CSS to perform calling party number transformation. If this box is unchecked, the setting in the Calling Search Space field gets used.


Cisco Unified Communications Manager Administration Configuration Tips

No configuration tips exist for this feature.

GUI Changes

The settings in Table 2-16 display in the FXS/FXO Port Configuration window. For information about configuring gateway ports, refer to the "Gateway Configuration" chapter of the Cisco Unified Communications Manager Administration Guide.

Service Parameter and Enterprise Parameter Changes

No service parameter or enterprise parameter changes exist for this feature.

Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 8.0(1), you can configure this feature.

Serviceability Considerations

No 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

No user tips exist for this feature.

For More Information

Gateway Configuration, Cisco Unified Communications Manager Administration Guide

Understanding Route Plans, Cisco Unified Communications Manager System Guide

Cancel Call Waiting

This section contains information on the following topics:

Description

Service Parameter and Enterprise Parameter Changes

Installation/Upgrade (Migration) Considerations

Serviceability Considerations

BAT Considerations

CAR/CDR Considerations

Security Considerations

AXL and CTI Considerations

User Tips

For More Information

Description

The Cancel Call Waiting feature allows the user to cancel the call waiting service when a call is active. This feature enables the user to block the operation of call waiting for one call. To invoke this feature, the user dials the cancel call waiting code, obtains recall dial tone, and places a call normally. During this call, the Call Waiting service is rendered inactive, so that anyone calling the user receives the normal busy treatment, and no call waiting tones interrupt the call.


Note This feature is available on both IP and analog phones.


The administrator can enable the Cancel Call Waiting feature by using the Cancel Call Waiting softkey in Cisco Unified Communications Manager, which adds a new softkey to non-standard softkey templates. The administrator then assigns the template to supported devices.

Service Parameter and Enterprise Parameter Changes

No service parameter or enterprise parameter changes exist for this feature.

Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 8.0(1), you can configure this feature.

Serviceability Considerations

No 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

No user tips exist for this feature.

For More Information

Softkey Templates, Cisco Unified Communications Manager Features and Services Guide

Cisco Unified Communications Manager Attendant Console No Longer Supported in Cisco Unified Communications Manager 8.0(1)

In Cisco Unified Communications Manager 8.0(1), Cisco no longer supports the Cisco Unified Communications Manager Attendant Console. All related configuration windows and settings have been removed. In addition, you cannot run the Cisco Unified Communications Manager Attendant Console on an attendant PC in Cisco Unified Communications Manager 8.0(1). You can obtain the End of Sale and End of Life notice for Cisco Unified Communications Manager Attendant Console at the following URL:

http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps7046/ps7282/end_of_life_notice_c51-499091.html

For attendant console support, Cisco recommends that you use one of the following applications, depending on the needs of your company:

Cisco Unified Business Attendant Console

Cisco Unified Department Attendant Console

Cisco Unified Enterprise Attendant Console

You can locate the product documentation for these applications at the following URL: http://www.cisco.com/en/US/products/ps7282/prod_maintenance_guides_list.html

Cisco Extension Mobility Change PIN

Description

If the user phone is subscribed to the Change Credential IP Phone service, the user can use the Change Credential IP Phone service to change the user PIN.

Cisco Unified Communications Manager Administration Configuration Tips

To allow a Cisco Extension Mobility end user to change the user PIN on the phone, configure the Change Credential Cisco Unified IP Phone service (Device > Device Settings > Phone Services) and associate the user (User Management > End User), the user device profile (Device > Device Settings > Device Profile), or the Cisco Unified IP Phone (Device > Phone) with the Change Credential phone service.

Configure the Change Credential IP Phone service and associate this phone service with a user, a user device profile, or a Cisco Unified IP Phone, so that a Cisco Extension Mobility user can change the user PIN on the Cisco Unified IP Phone to which they have logged in.

The Change Credential IP phone service allows an end user to change the user PIN on the Cisco Unified IP Phone with both Cisco Extension Mobility and Cisco Extension Mobility Cross Cluster.

Prerequisite

You must configure the Cisco Unified IP Phones in Cisco Unified Communications Manager before you subscribe the phones to Cisco Extension Mobility. To configure the phones, refer to the "Cisco Unified IP Phone Configuration" chapter in the Cisco Unified Communications Manager Administration Guide.

For a review of device profiles, refer to the "Understanding Device Profiles" section of the "Cisco Extension Mobility" chapter in the Cisco Unified Communications Manager Features and Services Guide.

To add the Change Credential IP Phone service, perform the following procedure.

Procedure


Step 1 From Cisco Unified Communications Manager Administration, choose Device > Device Settings > Phone Services.

Step 2 Click Add New.

The IP Phone Services Configuration window displays.

Step 3 In the Service Name field, enter Change Credential.


Note For descriptions of all fields, refer to the "IP Phone Service Configuration Settings" section in the Cisco Unified Communications Manager Administration Guide.


Step 4 In the Service URL field, enter the following value, where server designates the server where the Change Credential IP phone service runs:

http://server:8080/changecredential/ChangeCredentialServlet?device=#DEVICENAME#

Step 5 In the Secure-Service URL field, enter the following value, where server designates the server where the Change Credential IP phone service runs:

https://server:8443/changecredential/ChangeCredentialServlet?device=#DEVICENAME#

Step 6 Configure the remaining fields in the IP Phone Services Configuration window, and click Save.

You must now subscribe the Change Credential IP phone service to both the IP phone target device and to the user device profile that you created in the "Creating the Device Profile for a User" section of the "Cisco Extension Mobility" chapter of the Cisco Unified Communications Manager Features and Services Guide.

Step 7 To subscribe the Cisco Unified IP Phone to the Change Credential IP phone service, display the Phone Configuration window for the phone (Device > Phone).

Step 8 In the Phone Configuration window, go to the Related Links drop-down list box in the upper, right corner of the window and choose Subscribe/Unsubscribe Services; then, click Go.

A separate Subscribed Cisco IP Phone Services window displays.

Step 9 From the Select a Service drop-down list box, choose the Change Credential IP phone service.

Step 10 Click Next.

Step 11 Click Subscribe.

Step 12 The Change Credential IP phone service displays under Subscribed Services.

Step 13 Click Save.


Note To subscribe/unsubscribe services to a user device profile, see the "Creating the Device Profile for a User" section of the "Cisco Extension Mobility" chapter in the Cisco Unified Communications Manager Features and Services Guide.



Note To subscribe/unsubscribe services to an end user, see the "End User Configuration" chapter in the Cisco Unified Communications Manager Administration Guide.



GUI Changes

No GUI changes exist for this feature.

Service Parameter and Enterprise Parameter Changes

No service parameter nor enterprise parameter changes exist for this feature.

Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 8.0(1), you can configure this feature.

Serviceability Considerations

No serviceability considerations exist for this feature.

BAT Considerations

No Bulk Administration Tool considerations exist for this feature.

CAR/CDR Considerations

No CAR or CDR considerations exist for this feature.

Security Considerations

For information about the security considerations that exist for this feature, see the "Security" section on page 3-1.

AXL and CTI Considerations

No AXL or CTI considerations exist for this feature.

User Tips

For a list of phones that support this feature, see the "Extension Mobility Change PIN" section on page 7-4.

For More Information

"Cisco Extension Mobility," Cisco Unified Communications Manager Features and Services Guide

"Cisco Unified IP Phone Configuration," Cisco Unified Communications Manager Administration Guide

"IP Phone Service Configuration," Cisco Unified Communications Manager Administration Guide

"Device Profile Configuration," Cisco Unified Communications Manager Administration Guide

"End User Configuration," Cisco Unified Communications Manager Administration Guide

Cisco Unified Communications Manager Security Guide

Extension Mobility Change PIN, page 7-4

Security, page 3-1

Cisco Extension Mobility Cross Cluster

Description

The Cisco Extension Mobility Cross Cluster feature allows an enterprise user of one Cisco Unified Communications Manager cluster (the home cluster) to log in to a Cisco Unified IP Phone of another Cisco Unified Communications Manager cluster (the visiting cluster) during travel as if the user is using the IP phone at the home office.


Note If a user remains in a single cluster, configuration of the Cisco Extension Mobility feature suffices to provide the user with extension mobility capabilities. See the "Cisco Extension Mobility" chapter in the Cisco Unified Communications Manager Features and Services Guide for a description and configuration details of the Cisco Extension Mobility feature.


Cisco Unified Communications Manager Administration Configuration Tips

For configuration procedures that apply to the Cisco Extension Mobility Cross Cluster feature, see the following topics:

Configuration Checklist for EMCC

EMCC Login

EMCC Configuration

Configuring EMCC

Configuring EMCC Feature Configuration Settings

EMCC Intercluster Service Profile Configuration Settings

Configuring a Remote Cluster

GUI Changes

The Cisco Extension Mobility Cross Cluster feature entails the following changes to the Cisco Unified Communications Manager Administration GUI:

New menu option, Advanced Features > EMCC > EMCC Feature Configuration

New menu option, Advanced Features > EMCC > EMCC Intercluster Service Profile

New menu option, Advanced Features > EMCC > EMCC Remote Cluster

New setting, Adjunct CSS, on Device Pool Configuration window (System > Device Pool)

New setting, Extension Mobility Cross Cluster CSS, on Device Profile Configuration window (Device > Device Settings > Device Profile)

New drop-down list box, Trunk Service Type, on Trunk Configuration window for SIP trunks (Device > Trunk)

New check box, Enable Extension Mobility Cross Cluster, on End User Configuration window (User > User Management)

Service Parameter and Enterprise Parameter Changes

The Cluster ID enterprise parameter gets added to support the Cisco Extension Mobility Cross Cluster feature.

The following service parameters are new or modified and support the Cisco Extension Mobility Cross Cluster feature:

Enforce Intra-cluster Maximum Login Time—This service parameter, formerly known as Enforce Maximum Login Time, supports the Cisco Extension Mobility service.

Intra-cluster Maximum Login Time—This service parameter, formerly known as Maximum Login Time, supports the Cisco Extension Mobility service.

Inter-cluster Maximum Login Time—This service parameter supports the Cisco Extension Mobility service.

Intra-cluster Multiple Login Behavior—This service parameter, formerly known as Multiple Login Behavior, supports the Cisco Extension Mobility service.

Clear Call Logs on Intra-Cluster EM—This service parameter, formerly known as Clear Call Log, supports the Cisco Extension Mobility service.

EMCC Allow Proxy—This service parameter supports the Cisco Extension Mobility service.

Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 8.0(1), you can configure this feature.

Serviceability Considerations

The Cisco Extension Mobility Cross Cluster feature requires the addition of new performance monitoring counters and a new alarm. See the following sections for details:

Performance Monitoring Counters, page 5-6

New Alarms in CallManager Alarm Catalog, page 5-33

BAT Considerations

For the Bulk Administration Tool (BAT) considerations that apply to the Cisco Extension Mobility Cross Cluster feature, see the "Extension Mobility Cross Cluster" section on page 4-1 in the "Bulk Administration Tool" chapter.

CAR/CDR Considerations

No CAR or CDR considerations exist for this feature.

Security Considerations

For information about the security considerations that exist for this feature, see the "Security" section on page 3-1.

AXL and CTI Considerations

For information about the AXL and CTI considerations that exist for this feature, see the "APIs" section on page 6-1.

User Tips

For a list of phones that support this feature, see the "EMCC Supported Phones" section.

Configuration Checklist for EMCC

Table 2-17 provides a checklist for configuring Cisco Extension Mobility Cross Cluster in your network.

Table 2-17 Cisco Extension Mobility Cross Cluster Configuration Checklist 

Configuration Steps
Related Procedures and Topics

Step 1 

In Cisco Unified Serviceability, choose Tools > Service Activation.

Choose a server, and activate the following CM Services by checking the check box next to each service name:

Cisco CallManager

Cisco Tftp

Cisco Extension Mobility

Cisco Bulk Provisioning Service (can activate only on the publisher)

Click Save, click OK in response to the popup window, and wait for the services to get activated.

See the Cisco Unified Serviceability Administration Guide for additional details.

Step 2 

Create an Extension Mobility phone service:

1. In Cisco Unified Communications Manager Administration, choose Device > Device Settings > Phone Services.

2. Click Add New, and fill in the fields in the IP Phone Services Configuration window as follows:

Service Name: Extension Mobility

ASCII Service Name: Extension Mobility

Service Description: Extension Mobility

Service URL: http://10.89.80.19:8080/emapp/EMAppServlet?device=#DEVICENAME#&EMCC=#EMCC#


Note Change the IP address in both the Service URL and Secure-Service URL fields, unless you do not want the secure-service URL, in which case you can omit the https:// URL that follows.


Secure-Service URL: https://10.89.80.19:8443/emapp/EMAppServlet?device=#DEVICENAME#&EMCC=#EMCC#

Check the Enable check box.


Note If you click on the Enterprise Subscription check box when configuring the Extension Mobility IP phone service for the first time, you will set up this IP phone service as an enterprise subscription service. If you do this, all phones and device profiles in the enterprise will automatically subscribe to this IP phone service without needing to subscribe individually.


3. Click Save to save the Extension Mobility phone service.

IP Phone Services ConfigurationCisco Unified Communications Manager Administration Guide

Step 3 

Add a device profile for users who need Extension Mobility. The device profile gets used to overlay with a real device when the user logs in (both for Extension Mobility and Extension Mobility Cross Cluster). Follow these steps:

1. In Cisco Unified Communications Manager Administration, choose Device > Device Settings > Device Profile.

2. Add a new device profile for a specific device type with a specific protocol, assigning a meaningful name to the new device profile.

Example: 7971 SCCP Device Profile

3. In the new device profile, configure the Extension Mobility Cross Cluster CSS field.

This calling search space (CSS) gets applied to the real device configuration when the user travels and uses an IP phone of a different (visiting) cluster.

Configure this field as if setting the Calling Search Space field in the Phone Configuration window of a local IP phone.

Refer to "EMCC Call Routing" section for more details about the Extension Mobility Cross Cluster CSS field.

4. Add a directory number (DN) to the new device profile.

Example: 4001

5. In the Directory Number Configuration window, choose the Configure Device (<your new device profile name>) option in the Related Links drop-down list box, then click Go.

You return to the Device Profile Configuration window.

6. In the Device Profile Configuration window, choose the Subscribe/Unsubscribe Services option in the Related Links drop-down list box, then click Go.

7. In the popup window that displays, choose the Extension Mobility service in the Select a Service drop-down list box.

8. Click Next, then click Subscribe.

9. Click Save and close the popup window.

10. In the Device Profile Configuration window, click Save.

Device Profile Configuration, Cisco Unified Communications Manager Administration Guide

Directory Number Configuration, Cisco Unified Communications Manager Administration Guide

Step 4 

Add users for Cisco Extension Mobility Cross Cluster:

1. In Cisco Unified Communications Manager Administration, choose User Management > End User.

2. Click Add New to add a new end user.

3. In the End User Configuration window that displays, configure at least the following fields:

User ID, Password, PIN, Last name, First name

4. In the Extension Mobility pane, check the Enable Extension Mobility Cross Cluster check box.

5. Choose the device profile that you configured in Step 3 from the Available Profiles list pane in the Extension Mobility pane.

6. Use the Down arrow to move the device profile to the Controlled Profiles list pane.

7. Click Save to save the end user configuration.

End User Configuration, Cisco Unified Communications Manager Administration Guide

Step 5 

Enable Extension Mobility on the devices:

1. In Cisco Unified Communications Manager Administration, choose Device > Phone.

2. Find the phone on which users can perform Extension Mobility or Extension Mobility Cross Cluster.

3. For this device, check the Enable Extension Mobility check box in the Extension Information pane.

4. In the Phone Configuration window, choose the Subscribe/Unsubscribe Services option in the Related Links drop-down list box, then click Go.

5. In the popup window that displays, choose the Extension Mobility service in the Select a Service drop-down list box.

6. Click Next, then click Subscribe.

7. Click Save and close the popup window.

8. In the Phone Configuration window, click Save. If indicated, click OK in the popup window that displays.

Note This step completes the configuration necessary for a user to perform intra-cluster extension mobility login.

Note The Phone Configuration window provides a Secure Services URL. If left blank, the URL Services enterprise parameter gets used.

Cisco Unified IP Phone Configuration, Cisco Unified Communications Manager Administration Guide

Step 6 

Configure Bulk Certificate Management:

1. In Cisco Unified Communications Operating System Administration, choose Security > Bulk Certificate Management.

2. In the Bulk Certificate Management window that displays, configure the fields as follows:

IP Address: Specify the IP address of the SFTP server.


Note This is the centralized secure FTP server that all participating clusters must share.


Port: 22 (for SSH default port)

User ID: User ID of user that has write access

Password: Password of user that has write access

Directory: Directory of user that has write access
(Example: /tmp)

3. Click Save.

See the Cisco Unified Communications Operating System Administration Guide for details.

Step 7 

Configure Bulk Certificate Export:

1. In Cisco Unified Communications Operating System Administration, choose Security > Bulk Certificate Management.

2. Click the Export icon.

3. In the Bulk Certificate Export window that displays, configure the following field:

Certificate Type: All

4. Click Export, then click Close.

This step creates a PKCS12 file that contains certificates for all nodes in the cluster.

Every participating cluster must export certificates to the same SFTP server and SFTP directory.

A cluster must export its certificates whenever the Tomcat or TFTP certificate(s) gets regenerated on any of its nodes.

See the Cisco Unified Communications Operating System Administration Guide for details.

Step 8 

Consolidate certificates:

1. In Cisco Unified Communications Operating System Administration, choose Security > Bulk Certificate Management > Consolidate > Bulk Certificate Consolidate.

Consolidate certificates when all participating clusters have exported their certificates. This option is available only if two or more clusters have exported their certificates to the SFTP server.

2. In the window that displays, configure the following field:

Certificate Type: All

3. Click Consolidate.

This step consolidates all PKCS12 files in the SFTP server to form a single file.

Only one of the participating clusters needs to perform consolidation.

If new certificates are exported after they are consolidated, consolidation needs to be performed again to pick up the newly exported certificates.

See the Cisco Unified Communications Operating System Administration Guide for details.

Step 9 

Import certificates:

1. In Cisco Unified Communications Operating System Administration, choose Security > Bulk Certificate Management > Import > Bulk Certificate Import.

2. In the window that displays, configure the following field:

Certificate Type: All

3. Click Import.

Note After you import all the certificates on each cluster, for each cluster, you need to restart Cisco CallManager service and Cisco Tomcat service to activate the services for each node on each cluster.

Note After an upgrade, these certificates are preserved. Users do not need to reimport or reconsolidate certificates.

This step imports the consolidated PKCS12 file from the SFTP server into the local cluster.

All clusters should re-import when any participating cluster makes an export.

Perform import after a central administrator consolidates the certificates as explained in Step 8.

See the Cisco Unified Communications Operating System Administration Guide for details.

Step 10 

To enable EMCC for video calls, configure Common Phone Profile (Device > Device Settings > Common Phone Profile) or configure Enterprise Phone Configuration (System > Enterprise Phone Configuration) to enable video calls.

In either window, set the Video Capabilities drop-down list box as Enabled. (This setting may be enabled by default per cluster.)

Common Phone Profile Configuration, Cisco Unified Communications Manager Administration Guide

Enterprise Phone Configuration, Cisco Unified Communications Manager Administration Guide

Step 11 

Add EMCC devices—Add EMCC Templates:

1. In Cisco Unified Communications Manager Administration, choose Bulk Administration > EMCC > EMCC Template.

2. Click Add New.

3. In the EMCC Template Configuration window, configure the fields as follows:

Template Name: EMCC Device Template

Device Pool: Default

SIP Profile: Standard SIP Profile

Common Device Configuration: Default Common Device Configuration

4. Click Save.

See the Cisco Unified Communications Manager Bulk Administration Guide for details.

Step 12 

Add EMCC devices—Set default EMCC template.

1. In Cisco Unified Communications Manager Administration, choose Bulk Administration > EMCC > Insert/Update EMCC.

2. Click Update EMCC Devices.

3. In the Default EMCC Template drop-down list box, choose the EMCC Device Template that you configured in Step 11.

4. Click Run Immediately.

5. Click Submit.

6. Verify whether the job ran successfully:

Choose Bulk Administration > Job Scheduler and look for the Job ID of your job. Check that your job ran successfully.

See the Cisco Unified Communications Manager Bulk Administration Guide for details.

Step 13 

Add EMCC devices—Insert the EMCC Devices:

1. In Cisco Unified Communications Manager Administration, choose Bulk Administration > EMCC > Insert/Update EMCC.

2. Click Insert EMCC Devices.

3. Change the value in the Number of EMCC Devices to be added field (for example, to 5).

4. Click Run Immediately and click Submit.

5. Refresh this window and check that the Number of EMCC Devices already in database value now displays the number of devices that you added (for example, 5).

6. Alternately, choose Bulk Administration > Job Scheduler to check on whether the job completed successfully.

Maximum Number of EMCC Base Devices To Add

Include EMCC in the total number of devices that get supported in the cluster, using the following calculation:

phones + (2 x EMCC devices) <= MaxPhones

Cisco Unified Communications Manager systems specify a MaxPhones value of 60,000.

Cisco Unified Communications Manager Business Edition systems specify a MaxPhones value of 700.

EMCC login does not affect the number of licenses that get used in the home cluster.

See the Cisco Unified Communications Manager Bulk Administration Guide for details.

Step 14 

Configure enterprise parameters and add a geolocation filter:

1. In Cisco Unified Communications Manager Administration, choose System > Enterprise Parameters.

2. For the Cluster ID enterprise parameter, configure a unique cluster ID for every participating cluster.

3. In Cisco Unified Communications Manager Administration, choose System > Geolocation Filter.

4. Click Add New.

5. Create a new geolocation filter.

Example name: EMCC Geolocation Filter.

Specify criteria for matching, such as Country, State, and City.

Enterprise Parameters Configuration, Cisco Unified Communications Manager Administration Guide

Geolocation Filter Configuration, Cisco Unified Communications Manager Features and Services Guide

Step 15 

Configure EMCC feature parameters:

1. In Cisco Unified Communications Manager Administration, choose Advanced Features > EMCC > EMCC Feature Configuration.

2. In the EMCC Feature Configuration window that displays, configure the following feature parameters:

Default TFTP Server for EMCC Login Device

EMCC Geolocation Filter

Default Server for Remote Cluster Update

Note Each feature parameter must be previously configured before you can choose them in the drop-down list box that associates with each feature parameter.

Note You can keep the default values for other EMCC feature parameters or you can change as needed.

Configuring EMCC Feature Configuration Settings

Step 16 

Configure one or two intercluster SIP trunks for EMCC.

Note You may configure one trunk for both PSTN Access and RSVP Agent services (in Step 17) or one trunk for each service. You need no more than two EMCC SIP trunks.

1. In Cisco Unified Communications Manager Administration, choose Device > Trunk.

2. Click Add New.

3. Specify the following settings:

Trunk Type: SIP Trunk

Trunk Service Type: Extension Mobility Cross Clusters

4. Click Next.

5. In the Trunk Configuration window that displays, specify the following settings in the Device Information pane. The following values show example values.

Name: EMCC-ICT-SIP-Trunk-1

Device Pool: Default

In the SIP Information pane, specify the following example settings:

SIP Trunk Security Profile: Non Secure SIP Trunk Profile

SIP Profile: Standard SIP Profile

In the Geolocation Configuration pane, specify the following setting:

Send Geolocation Information: Check this check box.


Note EMCC trunk must specify SendGeolocation as True, MTPRequired as False, and UnattendedPort as False.


6. Click Save to save the intercluster SIP trunk for EMCC.

Trunk Configuration, Cisco Unified Communications Manager Administration Guide

Step 17 

Configure EMCC intercluster service profile:

1. In Cisco Unified Communications Manager Administration, choose Advance Features > EMCC > EMCC Intercluster Service Profile.

2. Check the Active check box in the EMCC pane.

3. Check the Active check box in the PSTN Access pane.

4. In the PSTN Access SIP Trunk drop-down list box, choose a SIP trunk that you configured in Step 16.

5. Check the Active check box in the RSVP Agent pane.

6. In the RSVP Agent SIP Trunk drop-down list box, choose another SIP trunk that you configured in Step 16.


Note If you configured only one trunk in Step 16, you can choose the same trunk for RSVP Agent SIP Trunk as for PSTN Access SIP Trunk.


7. Click Validate to validate your settings.

8. If no failure messages display in the popup window, click Save.

EMCC Intercluster Service Profile Configuration Settings

Step 18 

Configure EMCC remote cluster services:

1. In Cisco Unified Communications Manager Administration, choose Advance Features > EMCC > EMCC Remote Cluster.

2. Click Add New.

3. In the Remote Cluster Configuration window that displays, configure the following settings:

Cluster ID: Ensure that this cluster ID matches the enterprise parameter value of the cluster ID of the other cluster(s).

Fully Qualified Name: Use the IP address of the remote cluster or a domain name that can resolve to any node on the remote cluster.

Configuring a Remote Cluster

Step 19 

Configure service parameters:

1. In Cisco Unified Communications Manager Administration, choose System > Service Parameters.

2. From the Server drop-down list box, choose a server.

3. From the Service drop-down list box, choose the Cisco Extension Mobility service.

4. Click the Advanced button at the top of the window.

5. As needed, configure the following service parameters in the Clusterwide Parameters (Parameters that apply to all servers) pane:

Inter-cluster Maximum Login Time

EMCC Allow Proxy: Set this value as True.

Note For EMCC, the call logs always get cleared.

Note For EMCC, multiple logins are always allowed.

Service Parameters Configuration, Cisco Unified Communications Manager Administration Guide

"Setting the Service Parameters" in "Cisco Extension Mobility" chapter, Cisco Unified Communications Manager Features and Services Guide

"Comparing Cisco Extension Mobility Service Parameters" section in "Cisco Extension Mobility" chapter, Cisco Unified Communications Manager Features and Services Guide

Step 20 

EMCC does not require any special configuration for SRST to function.

If SRST configuration is required for your system, configure as usual.

Survivable Remote Site Telephony Configuration, Cisco Unified Communications Manager Administration Guide

EMCC vs. Cisco Extension Mobility

Release 3.1 of Cisco CallManager first offered the Cisco Extension Mobility feature. Cisco Extension Mobility continues to apply only to intra-cluster users and devices. Customers, however, want a seamless experience, no matter where they log in:

User wants the same set of features and services: all lines, speed dials, message button, MWI, and features.

Administrator wants security, CAC, local gateway access, local media resources, and serviceability.

EMCC Challenges

With intra-cluster Cisco Extension Mobility, the following characteristics apply:

Device information is available in the local database.

User information is available in the local database.

Global information is available in the local database.

With inter-cluster Cisco Extension Mobility, the following characteristics apply:

Device information is in one cluster database.

User information is in another cluster database.

Global information, such as routing configuration and service parameters, is in the database of both clusters.

Cisco Extension Mobility presents the following challenge: either device information needs to be moved to the cluster that manages user information or vice-versa.

EMCC Solution

The solution to address the problem of extension mobility across clusters specifies cross-registration. Cross-registration implies the following characteristics:

User from home cluster logs in to a phone at visiting cluster.

Login procedure conveys the device information into the home cluster database.

Home cluster database builds a temporary device with user device profile.

Home cluster TFTP server builds the phone configuration file.

After login, visiting cluster directs the phone to home cluster TFTP server.

Phone downloads its TFTP configuration from home cluster (HC) TFTP server and then cross-registers with home cluster Cisco Unified Communications Manager.


Note Clusters are designated as home or visiting relative to the login user.


Scope of EMCC

Cisco Extension Mobility Cross Cluster supports the following features:

Cisco Extension Mobility login and logout

User authentication takes place across clusters.

Security

Cross-cluster security gets provided by default.

Cisco Unified IP Phones with nonsecure security profiles get supported.

PSTN access is suitable for the visiting phone.

Routing E911 to the right part of the PSTN (that is, to local gateways) takes place.

Routing local calls to the right part of the PSTN takes place.

Calls terminating to local route groups route to local gateways in the visiting cluster.

Media resources suitable for the visiting phone get presented, such as the following:

RSVP Agent, TRP, Music On Hold (MOH), MTP, transcoder, conference bridge

Call Admission Control (CAC)

Home cluster remains ignorant of visiting cluster locations and regions.

The system cannot apply Cisco Unified Communications Manager locations and regions across the cluster boundaries.

RSVP agent-based CAC using RSVP agents in the visiting cluster

Call features and services that home cluster can reasonably support

Example restriction: Intercom configuration specifies configuration to a static device, so Cisco Extension Mobility Cross Cluster does not support the Intercom feature.

Default max audio bit-rate for EMCC login device is set to 8 kbps (G.729).


Note If home cluster uses software conference bridge that supports only the G.711 codec and if no transcoder is configured in the visiting cluster, conference will fail. As a workaround, change the EMCC feature parameter, EMCC Region Max Audio Bit Rate, to 64 kbps (G.711).


EMCC Login

This section presents the following topics:

EMCC Login Terminology

EMCC Login Progress

EMCC Login Terminology

Figure 2-1 illustrates the visiting cluster versus a home cluster in Cisco Extension Mobility Cross Cluster.

Figure 2-1 Visiting Cluster vs. Home Cluster

Visiting Cluster

For the visiting cluster, the following characteristics apply:

Phone is geographically present here.

Phone configuration resides here in the visiting Cisco Unified Communications Manager database.

The resources that the phone needs reside here, such as gateways and RSVP agents.

The visiting phone normally registers with the visiting Cisco Unified Communications Manager cluster that manages this geographic location (prior to EMCC login).

CCMCIP specifies the Cisco CallManager Cisco IP Phone service.

Home Cluster

For the home cluster, the following characteristics apply:

End user configuration resides here.

User device profile (lines, speed dials, features, and many more user characteristics) reside here.

User dialing habits make sense in the home context.

User locale resides here.

Cross-registration specifies the process of importing the device data into the home cluster and building a device record that is combined with the end user Extension Mobility (EM) profile in the home cluster, then directing the phone to register directly with the home cluster Cisco Unified Communications Manager.

EMCC Login Progress

Figure 2-2 illustrates Cisco Extension Mobility Cross Cluster login when extension mobility finds the home cluster.

Figure 2-2 EMCC Login—Extension Mobility Finds a Home Cluster

Figure 2-3 illustrates Cisco Extension Mobility Cross Cluster login when extension mobility authenticates, gives information to home cluster, and prepares home cluster.

Figure 2-3 EMCC Login—Extension Mobility Authenticates, Gives Information to Home, Prepares Home

Figure 2-4 illustrates Cisco Extension Mobility Cross Cluster login when extension mobility modifies the visiting cluster and initiates reregistration.

Figure 2-4 EMCC Login—Extension Mobility Modifies Visiting and Initiates Reregistration

Figure 2-5 illustrates Cisco Extension Mobility Cross Cluster login when extension mobility login services complete processing and the phone reregisters.

Figure 2-5 EMCC Login—Extension Mobility Login Services Complete Processing and the Phone Reregisters

EMCC Supported Phones

The list of devices that support the Cisco Extension Mobility Cross Cluster varies per version and device pack.

Use the Cisco Unified Reporting application to generate a complete list of devices that support monitoring and recording for a particular release and device pack. To do so, follow these steps:

1. Start Cisco Unified Reporting by using any of the methods that follow.

The system uses the Cisco Tomcat service to authenticate users before allowing access to the web application. You can access the application

by choosing Cisco Unified Reporting in the Navigation menu in Cisco Unified Communications Manager Administration and clicking Go.

by choosing File > Cisco Unified Reporting at the Cisco Unified Real Time Monitoring Tool (RTMT) menu.

by entering https://<server name or IP address>:8443/cucreports/ and then entering your authorized username and password.

2. Click System Reports in the navigation bar.

3. In the list of reports that displays in the left column, click the Unified CM Phone Feature List option.

4. Click the Generate a new report link to generate a new report, or click the Unified CM Phone Feature List link if a report already exists.

5. To generate a report of all devices that support Cisco Extension Mobility Cross Cluster, choose these settings from the respective drop-down list boxes and click the Submit button:

Product: All

Feature: Extension Mobility Cross Cluster

The List Features pane displays a list of all devices that support the Cisco Extension Mobility Cross Cluster feature. You can click on the Up and Down arrows next to the column headers (Product or Protocol) to sort the list.

For additional information about the Cisco Unified Reporting application, refer to the Cisco Unified Reporting Administration Guide, which you can find at this URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.

EMCC Configuration

See the "Configuration Checklist for EMCC" section for an overview of the configuration steps to configure Cisco Extension Mobility Cross Cluster, both in Cisco Unified Communications Manager Administration and in the other Cisco Unified Communications components, such as Cisco Unified Serviceability and the Cisco Unified Communications Operating System.

For details of configuring menu options that apply exclusively to EMCC, see the "Configuring EMCC" section and its subsections.

EMCC Active and Remote Login Summary

In the user home cluster, the administrator can view a list of the cluster users who have logged in from remote devices.

To do so, the administrator performs the following steps:

1. In Cisco Unified Communications Manager Administration, execute Device > Phone.

The Find and List Phones window displays.

2. From the Related Links drop-down list box, choose Remotely Logged In Device, then click Go.

For additional information about the remotely logged-in devices report, see the "Finding a Remotely Logged-In Device" section in the Cisco Unified Communications Manager Administration Guide.

In the user home cluster, the administrator can view a list of the cluster users who have logged in to either Cisco Extension Mobility or Cisco Extension Mobility Cross Cluster.

To do so, the administrator performs the following steps:

1. In Cisco Unified Communications Manager Administration, execute Device > Phone.

The Find and List Phones window displays.

2. From the Related Links drop-down list box, choose Actively Logged In Device Report, then click Go.

For additional information about the actively logged-in devices report, see the "Finding an Actively Logged-In Device" section in the Cisco Unified Communications Manager Administration Guide.

EMCC Call Processing

This section presents the following topics:

EMCC Call Processing Overview

EMCC Call-Processing Characteristics

EMCC Call-Processing Requirements

EMCC Call-Processing for Emergency Calls

Finding the Roaming Device Pool

Matching the Roaming Device Pool By Using Geolocation in Home Cluster

EMCC Call-Processing Configuration

List EMCC Phones and Their Roaming Device Pools in Home Cluster

EMCC Call Processing in Home Cluster

EMCC Call Routing

Configuring Visiting Cluster Emergency Pattern in Home Cluster

Local Route Group Routing of EMCC Visiting Phone in Home Cluster

Local Route Group Routing Using EMCC SIP Trunk

EMCC Calling Search Space in Device Profile

Region Configuration for EMCC Phones

RSVP Configuration for EMCC Phones

RSVP Agent-Based CAC Basic Call

RSVP Agent CAC Hold/Resume by Home Phone

RSVP Agent CAC Hold/Resume by Visiting Phone

EMCC Common Call-Processing Issues

Obtaining Help for EMCC Call-Processing Issues

EMCC Call Processing Overview

Figure 2-6 provides an overview of EMCC call processing.

Figure 2-6 EMCC Call Processing

EMCC Call-Processing Characteristics

EMCC call processing exhibits the following characteristics:

Call control on the home cluster

Visiting phone registers with home cluster.

RSVP Agent gets allocated from visiting cluster but is indirectly controlled by home cluster.

Visiting phone registers with home cluster.

Follows home cluster policy for RSVP-based CAC.

Codec selection by both home cluster and visiting cluster

Media processes on both home cluster and visiting cluster.

Codec selected based on EMCC region configuration of both clusters

Emergency call routing is visiting phone/visiting cluster dependent.

Home cluster supports both home cluster and visiting cluster emergency pattern.

Route emergency calls back to visiting cluster with local route group via EMCC SIP intercluster trunk.

Uses local route group of visiting phone that is configured in visiting cluster.

Device-dependent PSTN access in visiting cluster

Route call from SIP trunk to local gateway colocated with visiting phone

EMCC Call-Processing Requirements

Cisco Extension Mobility Cross Cluster fulfills the following call-processing requirements:

Emergency call routing

Allows user to dial either home cluster emergency pattern or visiting cluster emergency pattern (for example, 999 in the United Kingdom or 911 in the United States).

Call must route to the local gateway in the visiting cluster no matter which cluster emergency pattern gets dialed.

RSVP agent based CAC

RSVP Agents in the visiting cluster must get allocated based on the visiting phone media resource group list (MRGL) in the visiting cluster.


Note Whereas the phone registers with the home cluster, moving the phone location in the visiting cluster may cause incorrect association to the local gateway or media resource group list (MRGL) in the visiting cluster.


EMCC Call-Processing for Emergency Calls

Figure 2-7 illustrates Cisco Extension Mobility Cross Cluster call processing for emergency calls.

Figure 2-7 EMCC Call Processing for an Emergency Call

Finding the Roaming Device Pool

Finding the roaming device pool exhibits the following characteristics:

EMCC phone finds roaming-sensitive attributes from its roaming device pool in home cluster.

Home cluster configures one roaming device pool per remote cluster, with distinct geolocation characterizing that cluster, for example:

DPforUKCluster (country=UK)

DPforSJCluster (country=US, A1=CA, A3=SJ)

Phone that is enabled for extension mobility in visiting cluster configures its geolocation in visiting cluster.

Login process sends phone geolocation from visiting cluster to home cluster.

EMCC geolocation filter that is configured in home cluster filters phone geolocation.

Home cluster uses filtered phone geolocation to find the most suitable device pool as phone roaming device pool while phone registers in home cluster.

Matching the Roaming Device Pool By Using Geolocation in Home Cluster

Figure 2-8 illustrates matching the roaming device pool by using the geolocation in the home cluster.

Figure 2-8 Match Roaming Device Pool Using Geolocation in Home Cluster

EMCC Call-Processing Configuration

Visiting cluster configures geolocation for phones that are enabled for extension mobility. This configuration takes place in the Geolocation field of the Phone Configuration window (Device > Phone) or in the Geolocation field of the Geolocation Configuration pane of the Device Pool Configuration window (System > Device Pool).

Configuration of the following entities is also required for extension mobility enabled phones in the visiting cluster:

Local route group in the associated Device Pool Configuration window (System > Device Pool)

RSVP device (transcoder or MTP) in the phone media resource group list if RSVP policy is enabled.

Home cluster configures EMCC geolocation filter. Use the Advanced Features > EMCC > EMCC Feature Configuration menu option to configure the EMCC Geolocation Filter setting.

One device pool per remote cluster serves as the roaming device pool for login phones.

Example

Device pool specifies EMCC Device Pool for UK Cluster.

Geolocation for this device pool specifies UK Geolocation.

The UK Geolocation geolocation in this device pool allows UK phones to match and choose this device pool as the roaming device pool when the phones log in.

List EMCC Phones and Their Roaming Device Pools in Home Cluster

The home cluster administrator can list all remote devices that are currently registered to this cluster. To do so, execute Device > Phone. From the Related Links drop-down list box, choose Remotely Logged In Device; then, click Go.

The Remotely Logged-In Device Report displays the following information:

Device Name

Logged In Profile

User ID

Remote Cluster ID

Roaming Device Pool

EMCC Call Processing in Home Cluster

Logged-in EMCC phones in home cluster acquire the following attributes and preferences:

Shared attributes from EMCC base device (Bulk Administration)

Roaming-sensitive attributes from its roaming device pool

One roaming device pool per remote cluster

EMCC phones of same visiting cluster choose the same roaming DP

Allows country-specific emergency dialing plan (for example, 999 for UK)

User preferences from User Device Profile (lines and speed dials)

Feature-specific attributes from EMCC Feature Configuration

Codec preference for all EMCC phone of all clusters

RSVP policy for EMCC phones

EMCC Call Routing

Call routing gets based on calling search space (CSS) home cluster builds for the phone.

Home cluster concatenates the CSS in the following priority order:

1. Adjunct CSS (new)

Configured in roaming device pool to support country-specific emergency dialing plan (for example, UK phone remotely registers back to US cluster; user dials 9.999 (UK emergency number) that US cluster will normally not recognize. Home cluster=US, visiting cluster=UK.

May skip Adjunct CSS configuration if home cluster and visiting cluster share the same emergency pattern.

2. Line CSS

3. Device CSS

Device-specific; gets configured in Phone Configuration window or its static device pool.

Allows phone to perform normal dialing in home cluster.

Visiting phone does not have phone device configured in home cluster.

Home cluster takes EMCC CSS (new) from user login device profile and uses this CSS as its static device CSS.

Adjunct Calling Search Space Functionality

To configure the adjunct CSS, execute System > Device Pool and configure the Adjunct CSS field in the Device Pool Settings pane.

In this example, the following configuration applies:

Adjunct CSS specifies Adjunct CSS for UK Cluster.

Selected Partitions (in Route Partitions for this Calling Search Space) specifies EMCC Emergency Partition for UK.

The adjunct CSS, which you configure in the device pool, enables UK emergency dialing from UK phone that registers to US cluster after login and binding to the roaming device pool. US cluster specifies the home cluster.

Calling search space specifies only one member partition, EMCC Emergency Partition for UK.

Configuring Visiting Cluster Emergency Pattern in Home Cluster

Configure a visiting cluster emergency pattern in the home cluster.

Example

Configure the route for 9.999/{EMCC emergency partition for UK}. This route contain only one member, Standard LRG.

If visiting phone (in UK) that registers to home cluster (in US) dials 9.999, this pattern matches route pattern 9.999/{EMCC emergency partition for UK} because of the adjunct CSS in the phone roaming device pool. As a result, home cluster (US cluster) routes the call to the device local route group.

Local Route Group Routing of EMCC Visiting Phone in Home Cluster

The local route group of EMCC visiting phone in the home cluster specifies the following:

Local route group of a device comprises gateways to the device local PSTN.

Calls that terminate to Standard LRG get directed to calling device LRG (that is, to gateways that connect to the local PSTN).

A normal phone and its local route group register to the same cluster.

EMCC visiting phone and its local route group register to different clusters.

Home cluster has no configured local route group of visiting phone.

Home cluster has no direct access to local PSTN gateways of visiting phone.

Calls that terminate to Standard LRG of EMCC visiting phone in home cluster get directed to visiting cluster via PSTN access SIP trunk (EMCC Configuration).

Visiting cluster finds local route group that is configured for visiting phone. (Remember that any phone that is enabled for extension mobility must configure its local route group in the visiting cluster.)

Visiting cluster routes the call to gateways in that local route group like a normal phone.

Local Route Group Routing Using EMCC SIP Trunk

Figure 2-9 illustrates local route group routing that uses an EMCC SIP trunk.

Figure 2-9 Local Route Group Routing Using EMCC SIP Trunk

EMCC Calling Search Space in Device Profile

The Extension Mobility Cross Cluster CSS field, which you define in the Device Profile Configuration window (Device > Device Settings > Device Profile), gets used as the device CSS of the remote phone when the user selects this device profile during EMCC login.

Region Configuration for EMCC Phones

Region configuration for EMCC phones specifies the following:

EMCC login phones do not have region configured in home cluster.

All EMCC login phones, from any cluster, are assigned with common region configuration (Advanced Features > EMCC > EMCC Feature Configuration) that overrides normal region configuration.

EMCC feature parameters for regions must get configured with identical values in all clusters. If EMCC feature parameters for regions are set with different values, the Remote Cluster Update operation disables RSVP Agent for the cluster in question.

The following EMCC feature parameters for regions apply:

EMCC Region Max Audio Bit Rate (See the "Scope of EMCC" section for a details of a suggested workaround configuration that involves this feature parameter.)

EMCC Region Max Video Call Bit Rate (includes Audio)

EMCC Region Link Loss Type

RSVP Configuration for EMCC Phones

RSVP configuration for EMCC phones presents the following characteristics:

In home cluster, RSVP policy for EMCC phones follow the same configuration steps as normal phones:

Configure a common location (for example, Remote-cluster-location) or cluster-specific location (for example, UK-location).

Set Unlimited audio and video bandwidth for the location(s) such that location-based CAC gets disabled.

Set RSVP policy for location pairs (no reservation, optional, mandatory).

In visiting cluster, add RSVP devices to the media resource group list (MRGL) of the visiting phone.

When allocating RSVP agent, home cluster Cisco Unified Communications Manager recognizes the RSVP agent is for EMCC phone and redirects the request to visiting cluster over RSVP SIP trunk.

When allocating all other media resources, home cluster Cisco Unified Communications Manager allocate media resources based on the media resource group list that is configured in the home cluster.

RSVP Agent-Based CAC Basic Call

Figure 2-10 illustrates Cisco Extension Mobility Cross Cluster for an RSVP Agent-based Call Admission Control (CAC) basic call.

Figure 2-10 EMCC for RSVP Agent-Based CAC Basic Call

RSVP Agent CAC Hold/Resume by Home Phone

Figure 2-11 illustrates Cisco Extension Mobility Cross Cluster for an RSVP Agent-based Hold/Resume call by the home phone.

Figure 2-11 EMCC for an RSVP Agent-Based CAC Hold/Resume Call by the Home Phone

RSVP Agent CAC Hold/Resume by Visiting Phone

Figure 2-12 illustrates Cisco Extension Mobility Cross Cluster for an RSVP Agent-based Hold/Resume call by the visiting phone.

Figure 2-12 EMCC for an RSVP Agent-Based CAC Hold/Resume Call by the Visiting Phone

EMCC Common Call-Processing Issues

This section discusses the following common call processing issues that EMCC can present:

Cannot make normal call.

EMCC phone does not bind to the correct roaming device pool (Device > Phone, then choose Remotely Logged In Device).

Login device profile does not set EMCC CSS (Device > Device Setting > Device Profile).

RSVP reservation fails if configured (for example, no RSVP device in visiting phone media resource group list in visiting cluster).

EMCC login phone does not support G.729 codec and no transcoder is configured for the phone in the visiting cluster.

Cannot make emergency call.

EMCC phone does not bind to the correct roaming device pool (Device > Phone, then choose Remotely Logged In Device).

Adjunct CSS in roaming device pool of EMCC phone is missing.

Verify routing configuration in home cluster based on Adjunct CSS.

Local route group configuration is missing in phone static device pool in visiting cluster.

No media or one-way media is present.

Check whether all clusters have the same value in EMCC Region configuration window (Advanced Features > EMCC > EMCC Feature Configuration).

Check RSVP policy in home cluster (only RSVP policy in home cluster matters).

Obtaining Help for EMCC Call-Processing Issues

Take the following steps to obtain help for call processing issues:

Collect detailed traces from both home cluster and visiting cluster.

Provide detailed description of the call scenario:

Identify the EMCC device and the non-EMCC device and its cluster. For example, the EMCC phone does not bind to the correct roaming device pool. Use the Device > Phone menu option, then choose Remotely Logged In Device from the Related Links drop-down list box.

Phone Behavior With EMCC

This section presents the following phone behaviors in an EMCC environment:

WAN Network Failure—Configuration File Unavailable

EMCC Failure—Registration Rejection

EMCC Failure—Home Cisco Unified Communications Manager Unavailable/Interoffice Failure

EMCC Failure—Home Cisco Unified Communications Manager Unavailable/Inter-cluster Failure

EMCC Failure—Home Cisco Unified Communications Manager Unavailable/Inter-cluster Failure (No Visiting SRST)

WAN Network Failure—Configuration File Unavailable

Figure 2-13 illustrates WAN network failure when the configuration file is unavailable.

The phone reregisters with the visiting cluster.

Figure 2-13 WAN Network Failure—Configuration File Unavailable

In EMCC login mode, if the phone detects a connection failure to the home cluster, the phone tries to reestablish connection to the home cluster. After several failed attempts, such as failures due to WAN failure, the phone issues a logout request to the visiting cluster automatically, then the phone reregisters with the visiting cluster as logged out.

EMCC Failure—Registration Rejection

Figure 2-14 illustrates EMCC failure when registration rejection occurs.

The phone reregisters with the visiting cluster.

Figure 2-14 EMCC Login Failure—Registration Rejection

EMCC Failure—Home Cisco Unified Communications Manager Unavailable/Interoffice Failure

Figure 2-15 illustrates EMCC failure when the home Cisco Unified Communications Manager is unavailable and an interoffice failure occurs.

The phone fails over to SRST.

Figure 2-15 EMCC Failure—Home Cisco Unified Communications Manager Unavailable/Interoffice Failure

EMCC Failure—Home Cisco Unified Communications Manager Unavailable/Inter-cluster Failure

Figure 2-16 illustrates EMCC failure when the home Cisco Unified Communications Manager is unavailable and an inter-cluster failure occurs.

The phone reregisters with the visiting cluster.

Figure 2-16 EMCC Failure—Home Cisco Unified Communications Manager Unavailable/Inter-cluster Failure

EMCC Failure—Home Cisco Unified Communications Manager Unavailable/Inter-cluster Failure (No Visiting SRST)

Figure 2-17 illustrates EMCC failure when the home Cisco Unified Communications Manager is unavailable, an inter-cluster failure occurs, and no visiting SRST applies.

The phone reregisters with the visiting cluster.

Figure 2-17 EMCC Failure—Configuration File Unavailable, Inter-cluster Failure Occurs, and No Visiting SRST Applies

Phone Security With EMCC

See the Cisco Unified Communications Manager Security Guide for details of phone security issues in an EMCC environment.

System Requirements for EMCC

The following system requirements exist for Cisco Unified Communications Manager:

Cisco Unified Communications Manager, Release 8.0(1) or higher

Cisco Extension Mobility service

Cisco Unified Communications Operating System

Cisco Bulk Provisioning service

Other call-control entities that support and use the Cisco Extension Mobility Cross Cluster configuration; for example, other Cisco Unified Communications Manager 8.0(1) clusters, EMCC intercluster service profiles, and EMCC remote cluster services

EMCC Interactions and Restrictions

This section provides the details of interactions and restrictions for Cisco Extension Mobility Cross Cluster. See the following topics:

EMCC Interactions

EMCC Restrictions

EMCC Interactions

This section lists the interactions of the Cisco Extension Mobility Cross Cluster with other Cisco Unified Communications Manager Administration components.

With the Cisco Extension Mobility Cross Cluster cross-registration solution, user features function as expected across clusters. The following list specifies some of the user features that function across clusters:

Shared lines

Hunt lists

Transfer/Conference/Hold

Call Forward

Cisco Unified Mobility

Barge/cBarge

iDivert

Applications

Speed dials

Services

Address book

Device labels

Line appearance management

MWI

Voice mail

Do Not Disturb

Monitoring and Recording

Callback Busy/NR

Multilevel Precedence and Preemption (MLPP)

EMCC Restrictions

This section lists the restrictions and limitations of the Cisco Extension Mobility Cross Cluster with other Cisco Unified Communications Manager Administration components. The section covers the following topics:

EMCC Logout Limitation

EMCC Does Not Support Intercom Feature

EMCC Does Not Support Location-based Call Admission Control

EMCC Limitations and Configuration Requirements With Local Route Groups

EMCC Duplicate User ID Limitation

EMCC Device Cannot Be Provisioned in More Than One Cluster

EMCC and Security Mode Among Clusters

Visiting Phone Login Limitation After Cisco CallManager Service Goes Down

EMCC and Product-Specific Configuration Layout in Phone Configuration Window

EMCC Logout Limitation

If the home cluster administrator disables the EMCC capability of an end user while the end user is logged in with EMCC, the system does not automatically log this end user out. (In this scenario, the administrator unchecks the Enable Extension Mobility Cross Cluster check box in the End User Configuration window for the end user.) Instead, the system only fails future EMCC attempts by this end user. The current EMCC session continues until the end user logs out.

EMCC Does Not Support Intercom Feature

Intercom configuration specifies configuration to a static device, so Cisco Extension Mobility Cross Cluster does not support the Intercom feature.

EMCC Does Not Support Location-based Call Admission Control

Location CAC does not get supported.

RSVP-based CAC does get supported.

EMCC Limitations and Configuration Requirements With Local Route Groups

Refer to the following sections for details of EMCC limitations and configuration requirements in routing EMCC calls with local route groups:

EMCC Call-Processing Configuration

Configuring Visiting Cluster Emergency Pattern in Home Cluster

Local Route Group Routing of EMCC Visiting Phone in Home Cluster

Local Route Group Routing Using EMCC SIP Trunk

EMCC Duplicate User ID Limitation

Duplicate user ID does not get supported (for either the same or different PIN), because the behavior is unpredictable.

EMCC Device Cannot Be Provisioned in More Than One Cluster

Cisco Systems recommends that autoregistration be disabled (to avoid accidental provisioning).

EMCC and Security Mode Among Clusters

All clusters must specify the same security mode; either

All clusters specify nonsecure clusters or mixed-mode clusters.

Clusters with different security modes cannot be mixed.

Phones that allow Cisco Extension Mobility Cross Cluster must be non-secure mode (that is, they must associate with a nonsecure Device Security Profile).

RTP streams only

Calls not secure (TCP only, no TLS connection)

Visiting Phone Login Limitation After Cisco CallManager Service Goes Down

The Cisco Extension Mobility service in participating clusters performs a periodic remote cluster update. The EMCC Feature Configuration feature parameter, Remote Cluster Update Interval, controls the update interval, for which the default value specifies 30 minutes.

If the Cisco Extension Mobility service on cluster A does not get back a reply from a remote cluster (such as cluster B) for this update, the Remote Cluster window for cluster A shows that Remote Activated service is set to false for cluster B.

In this case, the visiting cluster does not receive any response from the home cluster and sets the Remote Activated values for the home cluster as false.

During this interval, a visiting phone may not be able to log in by using EMCC. The visiting phone receives the Login is unavailable (23) message.

At this point, trying to log in EMCC from a visiting phone may fail with the error, Login is unavailable (23), which displays on the phone. This occurs because the visiting cluster has not yet detected the change of home cluster Cisco Unified Communications Manager from out-of-service to in-service.

Detection of status change of remote clusters is based on the value of the Remote Cluster Update Interval EMCC feature parameter and on when the visiting Cisco Extension Mobility service performed the last query/update.

You can also click the Update Remote Cluster Now button on the Remote cluster Service Configuration window (Advanced Features > EMCC > EMCC Remote Cluster) to change Remote Activate values to true, which also allows EMCC logins. Otherwise, after the next periodic update cycle, EMCC logins by visiting phones will return to normal.

EMCC and Product-Specific Configuration Layout in Phone Configuration Window

When a user uses a phone in a visiting cluster to log into the user Extension Mobility profile, the phone inherits the default provisioning, network, and security settings (specifically, the configuration in the Product Specific Configuration Layout section of the Phone Configuration window) from the home cluster. This behavior may override local security and network settings that are in place in the visiting cluster. Some of the parameters have firmware defaults that the system administrator cannot change until a fix is provided.

Installing and Activating EMCC

After you install Cisco Unified Communications Manager 8.0(1), your network can support the Cisco Extension Mobility Cross Cluster feature if you perform the necessary configuration tasks. For information on configuration tasks that you must perform, see the "Configuration Checklist for EMCC" section.

Configuring EMCC

This section contains information on the following topics:

Configuring EMCC Feature Configuration Settings

EMCC Intercluster Service Profile Configuration Settings

Finding a Remote Cluster

Configuring a Remote Cluster

Remote Cluster Configuration Settings

Configuring EMCC Feature Configuration Settings

Table 2-18 provides detailed descriptions of the EMCC service parameters that you configure in the EMCC Feature Configuration window (Advanced Features > EMCC > EMCC Feature Configuration).

Table 2-18 EMCC Feature Configuration Settings 

EMCC Parameter
Description

Default TFTP Server for EMCC Login Device

Choose the computer name or IP address of the default TFTP server that devices logging into EMCC from a remote cluster should use.

Backup TFTP Server for EMCC Login Device

Choose the computer name or IP address of the backup TFTP server that devices logging into EMCC from a remote cluster should use.

Default Interval for Expired EMCC Device Maintenance

Specify the number of minutes that elapse between checks of the system for expired EMCC devices.

An expired EMCC device specifies a device that logged in to EMCC from a remote cluster, but that, due to WAN failure or a connectivity issue, the phone logged out of the visiting cluster and, when connectivity was restored, logged back into the visiting cluster.

During this maintenance job, the Cisco Extension Mobility service checks the Cisco Unified Communications Manager database for any expired EMCC devices and automatically logs such devices out.

Default value specifies 1440 minutes. Valid values range from 10 minutes to 1440 minutes.

Enable All Remote Cluster Services When Adding A New Remote Cluster

Choose whether you want all services on a new remote cluster to be automatically enabled when you add a new cluster.

Valid values specify True (enable all services on the remote cluster automatically) or False (manually enable the services on the remote cluster via the Remote Cluster Configuration window in Cisco Unified Communications Manager Administration). You may prefer to enable the services manually so that you have time to configure the EMCC feature completely before enabling the remote services.

Default value specifies False.

CSS for PSTN Access SIP Trunk

Choose the calling search space (CSS) that the PSTN Access SIP trunk for processing EMCC calls uses.

The PSTN Access SIP trunk specifies the SIP trunk that has been configured for PSTN access in the Intercluster Service Profile window in Cisco Unified Communications Manager Administration. Calls over this trunk are intended for and only get routed to the local PSTN that is co-located with the EMCC logged-in phone that initiates the call.

Valid values specify the following:

Use Trunk CSS (PSTN calls use the local route group, which can prove useful for properly routing emergency service calls)

Use phone's original device CSS (PSTN calls get routed using the configured calling search space on the remote phone; that is, the CSS that is used when the phone is not logged into EMCC).

Default value specifies Use trunk CSS.

EMCC Geolocation Filter

Choose the geolocation filter that you have configured for use with the Cisco Extension Mobility Cross Cluster feature. You must previously configure the EMCC geolocation filters to be able to choose a value in this drop-down list box.

Based on the information in the geolocation that associates with a phone that is logged in via extension mobility from another cluster as well as the selected EMCC geolocation filter, Cisco Unified Communications Manager places the phone into a roaming device pool.

Cisco Unified Communications Manager determines which roaming device pool to use by evaluating which device pool best matches the phone geolocation information after the EMCC geolocation filter gets applied.

EMCC Region Max Audio Bit Rate

This parameter specifies the maximum audio bit rate for all EMCC calls, regardless of the region associated with the other party.

Default value specifies 8 kbps (G.729).

Note Communicate your EMCC Region Max Audio Bit Rate to the other clusters with which your cluster interacts. All participating EMCC clusters must specify the same EMCC Region Max Audio Bit Rate.

EMCC Region Max Video Call Bit Rate (Includes Audio)

This parameter specifies the maximum video call bit rate for all EMCC video calls, regardless of the maximum video call bit rate of the region associated with the other party.

Default value specifies 384. Valid values range from 0 to 8128.

Note Communicate your EMCC Region Max Video Call Bit Rate to the other clusters with which your cluster interacts. All participating EMCC clusters must specify the same EMCC Region Max Video Call Bit Rate.

EMCC Region Link Loss Type

This parameter specifies the link loss type between any EMCC phone and devices in any remote cluster.

Note Communicate your EMCC Region Link Loss Type to the other clusters with which your cluster interacts. To allow two-way audio on EMCC calls, all participating EMCC clusters must use the same EMCC Region Link Loss Type.

Based on the option chosen, Cisco Unified Communications Manager attempts to use the optimal audio codec for the EMCC call while observing the configured EMCC Region Max Audio Bit Rate.

Valid values specify the following:

Lossy (a link where some packet loss can or may occur, for example, DSL)

Low Loss (a link where low packet loss occurs, for example, T1).

When this parameter is set to Lossy, Cisco Unified Communications Manager chooses the optimal codec within the limit that is set by the EMCC Region Max Audio Bit Rate, based on audio quality, given the assumption that some packet loss will occur.

When this parameter is set to Low Loss, Cisco Unified Communications Manager chooses the optimal codec within the limit that is set by the EMCC Region Max Audio Bit Rate, based on audio quality, given the assumption that little or no packet loss will occur.

The only difference in the audio codec preference ordering between the Low Loss and Lossy options is that G.722 is preferred over iSAC (Internet Speech Audio Codec) when the Link Loss Type is set as Low Loss, whereas iSAC is preferred over G.722 when the Link Loss Type is set as Lossy.

Default value specifies Low Loss.

RSVP SIP Trunk KeepAlive Timer

Specify the number of seconds that Cisco Unified Communications Manager waits between sending or receiving KeepAlive messages or acknowledgments between two clusters over EMCC RSVP SIP trunks.

An EMCC RSVP SIP trunk specifies a SIP trunk that has Cisco Extension Mobility Cross Cluster configured as the Trunk Service Type and that has been selected as the SIP Trunk for RSVP Agent in the Intercluster Service Profile window. When two of these intervals elapse without receipt of a KeepAlive message or an acknowledgment, Cisco Unified Communications Manager releases the RSVP resources with the remote cluster.

Default value specifies 15 seconds. Valid values range from 1 second to 600 seconds.

Default Server For Remote Cluster Update

Choose the default server name or IP address of the primary Cisco Unified Communications Manager server in this local cluster that has the Cisco Extension Mobility service activated. The remote cluster accesses this server to get information about this local cluster.

Backup Server for Remote Cluster Update

Choose the default server name or IP address of the secondary Cisco Unified Communications Manager server in this local cluster that has the Cisco Extension Mobility service activated. The remote cluster accesses this server when the primary server is down to get information about this local cluster.

Remote Cluster Update Interval

Specify an interval, in minutes, during which the Cisco Extension Mobility service on the local Cisco Unified Communications Manager node collects information about the remote EMCC cluster. Collected information includes such details as the remote cluster Cisco Unified Communications Manager version and service information.

Default value specifies 30. Valid values range from 15 minutes to 10,080 minutes.


EMCC Intercluster Service Profile Configuration Settings

In the Intercluster Service Profile Configuration window, you configure an EMCC intercluster service profile. In Cisco Unified Communications Manager Administration, use the Advanced Features > EMCC > EMCC Intercluster Service Profile menu option to display this window.

Table 2-19 EMCC Intercluster Service Profile Configuration Settings 

Field
Description
EMCC

Active

Check this check box to activate the Cisco Extension Mobility Cross Cluster feature.

PSTN Access

Active

Check this box to activate PSTN access.

SIP trunk

From the drop-down list box, choose the SIP trunk to use for PSTN access.

You must first specify a SIP trunk (Device > Trunk) and configure it for PSTN access

RSVP Agent

Active

Click this box to activate RSVP Agent.

SIP trunk

From the drop-down list box, choose the SIP trunk to use for RSVP Agent.

You must first specify a SIP trunk (Device > Trunk).

EMCC Setup Validation Report

Configuration(s)

After you click Save, this pane displays the EMCC Setup Validation Report.

If you click Validate, a popup window, displays the EMCC Setup Validation Report. Click Close to close the popup window.

The Configuration(s) column of the report displays the following entities that get validated:

EMCC PSTN Access Service

Default TFTP Server for EMCC Login Device

EMCC Geolocation Filter

EMCC Service Default Server for Remote Cluster

EMCC Devices

ClusterId

Status

This column displays the status of each configuration upon validation of the EMCC intercluster service profile. For each entity, valid values include Success and Failure.

Error Message

For each failed configuration, an error message explains the configuration that must take place in order to achieve success.


Finding a Remote Cluster

Because you might have several remote clusters in your network, Cisco Unified Communications Manager Administration lets you locate specific remote clusters on the basis of specific criteria. Use the following procedure to locate remote clusters.


Note The Find operation locates only those remote clusters that you added previously. The Find operation does not locate the clusters that belong to the enterprise automatically.



Note During your work in a browser session, Cisco Unified Communications Manager Administration retains your search preferences. If you navigate to other menu items and return to this menu item, Cisco Unified Communications Manager Administration retains your search preferences until you modify your search or close the browser.


Procedure


Step 1 Choose Advanced Features > EMCC > EMCC Remote Cluster.

The Find and List window displays. Records from an active (prior) query may also display in the window.

Step 2 To find all records in the database, ensure the dialog box is empty; go to Step 3.

To filter or search records

From the first drop-down list box, select a search parameter.

From the second drop-down list box, select a search pattern.

Specify the appropriate search text, if applicable.


Note To add additional search criteria, click the + button. When you add criteria, the system searches for a record that matches all criteria that you specify. To remove criteria, click the - button to remove the last added criterion or click the Clear Filter button to remove all added search criteria.


Step 3 Click Find.

All matching records display. You can change the number of items that display on each page by choosing a different value from the Rows per Page drop-down list box.


Note You can delete multiple records from the database by checking the check boxes next to the appropriate record and clicking Delete Selected. You can delete all configurable records for this selection by clicking Select All and then clicking Delete Selected.


Step 4 From the list of records that display, click the link for the record that you want to view.


Note To reverse the sort order, click the up or down arrow, if available, in the list header.


The window displays the item that you choose.


Configuring a Remote Cluster

This section describes how to add, copy, or update a remote cluster in Cisco Unified Communications Manager Administration.

Procedure


Step 1 Choose Advanced Features > EMCC > EMCC Remote Cluster.

The Find and List window displays.

Step 2 Perform one of the following tasks:

To add a new remote cluster, click the Add New button and continue with Step 3.

To update an existing remote cluster, locate the appropriate remote cluster as described in the "Finding a Remote Cluster" section and continue with Step 3.

Step 3 Enter information for the appropriate fields as described in Table 2-9.

Step 4 To save the remote cluster information to the database, click Save.


Remote Cluster Configuration Settings

Table 2-20 provides detailed descriptions of the remote cluster configuration settings that you configure in the Remote Cluster Configuration window (Advanced Features > EMCC > EMCC Remote Cluster).

Table 2-20 Remote Cluster Configuration Settings 

Field
Description
Remote Cluster Information

Cluster Id

Enter the cluster ID of the remote cluster.

Description

Enter a description for the remote cluster.

This field accepts up to 128 characters. You may use all characters except quotes ("), close angle bracket (>), open angle bracket (<), backslash (\), dash (-), ampersand (&), and percent sign (%).

Fully Qualified Name

Enter the fully qualified name of the remote cluster.

This field accepts up to 50 characters and allows the following characters: alphanumeric (a through z, A through Z, and 0 through 9), period (.), dash (-), asterisk (*), and space ( ).

Remote Cluster Service Information

EMCC

For the EMCC service, the following column headings detail the configuration for this service:

Enabled—If the EMCC service is enabled, this box gets checked.

Service—This entry specifies the EMCC service.

Remote Activated—Valid values specify true or false.

Address 1—This column lists the first address for this service.

Address 2—This column lists the second address for this service.

Address 3—This column lists the third address for this service.

PSTN Access

For PSTN access, the following column headings detail the configuration for this service:

Enabled—If PSTN access is enabled, this box gets checked.

Service—This entry specifies PSTN access.

Remote Activated—Valid values specify true or false.

Address 1—This column lists the first address for this service.

Address 2—This column lists the second address for this service.

Address 3—This column lists the third address for this service.

RSVP Agent

For the RSVP Agent, the following column headings detail the configuration for this service:

Enabled—If RSVP Agent is enabled, this box gets checked.

Service—This entry specifies RSVP Agent.

Remote Activated—Valid values specify true or false.

Address 1—This column lists the first address for this service.

Address 2—This column lists the second address for this service.

Address 3—This column lists the third address for this service.

Enabled All Services

Click this button to enable all services (EMCC, PSTN Access, and RSVP Agent).

Disabled All Services

Click this button to disable all services (EMCC, PSTN Access, and RSVP Agent).

Update Remote Cluster Now

Click this button to update the remote cluster immediately.


Error Codes for the Cisco Extension Mobility Application (EMApp)

Table 2-21 lists and describes the error codes that apply to the Cisco Extension Mobility application (EMApp).

Table 2-21 Error Codes for the Cisco Extension Mobility Application (EMApp) 

Error Code
Phone Display
Quick Description
Description

201

Please try to login again (201)

Authentication Error

If the user is an EMCC user, this error can occur if "EMCC" is not activated in the Inter-cluster Service Profile page.

202

Please try to login again (202)

Black userid or pin

User enters blank user ID or PIN.

204

Login is unavailable (204)

Directory server error

EMApp sends this error to phone when IMS could not authenticate the user with the given PIN.

205

Login is unavailable (205)

Logout is unavailable (205)

User Profile Absent

Occurs when the user profile information could not be retrieved either from the cache or from the database.

207

Login is unavailable(207)

Logout is unavailable(207)

Device Name Empty

Occurs when device or name tag is missing in the request URI. This cannot happen with real devices and can occur only if request is sent from third-party applications.

208

Login is unavailable(208)

Logout is unavailable(208)

EMService Connection Error

Visiting EMApp could not connect to any Visiting EMService. (Service is down or not activated.)

Visiting EMService could not connect to Home EMService (WAN is down or certificates are not trusted.)

210

Login is unavailable(210)

Logout is unavailable(210)

Init Fail-Contact Admin

Some error (like database connection failure) occurred while initializing EMApp. The error may occur because of failure in connecting to the database during startup. This represents a catastrophic error.

211

Login is unavailable(211)

Logout is unavailable(211)

EMCC Not Activated

Occurs when PSTN is not activated in the Intercluster Service Profile window of the visiting cluster.

212

Login is unavailable(212)

Cluster ID is invalid

Occurs when a remote cluster updated (keep-alive) fails by sending an incorrect cluster ID to remote cluster.

213

Login is unavailable(213)

Logout is unavailable(213)

Device does not support EMCC

Occurs when a device (phone load) does not have EMCC capability (for example, for legacy phones or for TNP phones with older phone load).


Error Codes for the Cisco Extension Mobility Service (EMService)

Table 2-22 lists and describes the error codes that apply to the Cisco Extension Mobility service (EMService).

Table 2-22 Error Codes for the Cisco Extension Mobility Service (EMService) 

Error Code
Phone Display
Quick Description
Description

0

Login is unavailable(0)

Logout is unavailable(0)

Unknown Error

EMService failed in some totally unexpected scenario. It is catastrophic.

1

Login is unavailable(1)

Logout is unavailable(1)

Error on parsing

When EMService could not parse the XML request from EMApp/EMService. This happens when 3rd party applications sends an incorrect query/login XML (EM API) or it can occur because of mis-match in version between home and visiting CUCM versions (for EMCC).

2

Login is unavailable(2)

EMCC Authentication Error

EMCC user credentials could not be authenticated as the user has entered wrong pin.

3

Login is unavailable(3)

Logout is unavailable(3)

Invalid App User

Invalid application user. This can be seen commonly when using EM API.

4

Login is unavailable(4)

Logout is unavailable(4)

Policy Validation error

EM Service sends this error when it could not validate the login/logout request due to some unknown reason (Error while querying the database or error while retrieving info from cache).

5

Login is unavailable(5)

Logout is unavailable(5)

Dev. logon disabled

EM / EMCC Login is requested for a device which has "Enable extension mobility" unchecked in phone configuration page.

6

Login is unavailable(6)

Logout is unavailable(6)

Database Error

Whenever database throws an exception while executing the query or stored procedure requested by EM Service (login/logout or device/user query), EM Service sends this error code to EM App.

8

Login is unavailable(8)

Logout is unavailable(8)

Query type undetermined

No Valid query has been sent to the EMService (DeviceUserQuery & UserDeviceQuery are valid ones). This is ideally seen when using EM API with incorrect XML input.

9

Login is unavailable(9)

Logout is unavailable(9)

Dir. User Info Error

This error is displayed in two cases:

1. IMS throws an exception when it tries to authenticate a particular user.

2. When information about a particular user could not be retrieved either from cache or database.

10

Login is unavailable(10)

Logout is unavailable(10)

User lacks app proxy rights

User tries to do login/query on behalf of some other user (By default, only CCMSysUser has the admin rights.)

11

Login is unavailable(11)

Logout is unavailable(11)

Device Does not exist

Phone record entry is absent in the device table.

12

Phone record entry is absent in the device table

Dev. Profile not found

No Device profile is associated with the remote user (EMCC Login)

18

Login is unavailable(18)

Another user logged in

Another user is already logged in on that particular phone

19

Logout is unavailable(19)

No user logged in

Trying to logout a user which has not logged in. This can ideally happen when sending logout requests from the 3rd party applications (EM API).

20

Login is unavailable(20)

Logout is unavailable(20)

Hoteling flag error

"Enable extension mobility" is unchecked in phone configuration page.

21

Login is unavailable(21)

Logout is unavailable(21)

Hoteling Status error

Current user status could not be retrieved from either local cache or database (when PolicyValidator tried to check current login User or login time).

22

Login is unavailable(22)

Dev. logon disabled

Occurs when EM is not enabled on device and the request is sent via EM API or when the services button is pressed on phone.

23

Login is Unavailable (23)

Logout is Unavailable (23)

User does not exist

Occurs when the given user ID is not found (in any of the remote clusters).

25

Login is unavailable(25)

User logged in elsewhere

User has currently logged in on some other phone

26

Login is unavailable(26)

Logout is unavailable(26)

Busy, please try again

When EMService has currently reached the threshold level of "Maximum Concurrent Requests" service parameter

28

Login is unavailable(28)

Logout is unavailable(28)

Untrusted IP Error

When "Validate IP Address" service parameter is set to true and user tries to login/logout from a machine whose IP address is not trusted (for example, 3rd party app / EM API from a machine which is not listed in Trusted List of Ips service parameter).

29

Login is unavailable(29)

Logout is unavailable(29)

ris down-contact admin

RISDC Cache has not been created and initialized and EMService is unable to connect to RISDC

30

Login is unavailable(30)

Logout is unavailable(30)

Proxy not allowed

When login/logout comes through proxy ("Via" is set in HTTP header) and "Allow Proxy" service parameter is set to "false."

31

Login is unavailable(31)

Logout is unavailable(31)

EMCC Not Activated for the user

Occurs when Enable EMCC check box is not checked in the End User window of the home cluster.

32

Login is unavailable(32)

Logout is unavailable(32)

Device does not support EMCC

Occurs when a device model does not have EMCC capability (for example, legacy phones)

33

Login is unavailable(33)

Logout is unavailable(33)

No free EMCC dummy device

Occurs when all the EMCC dummy devices are in use by other EMCC logins.

35

Login is unavailable(35)

Logout is unavailable(35)

Visiting Cluster Information is not present in Home Cluster

Occurs when the home cluster does not have an entry for this visiting cluster.

36

Login is unavailable(36)

Logout is unavailable(36)

No Remote Cluster

Occurs when the administrator has not added any remote cluster.

37

Login is Unavailable (37)

Logout is Unavailable (37)

Duplicate Device Name

Occurs when the same device name exists in both home cluster and visiting cluster.

38

Login is unavailable(38)

Logout is unavailable(38)

EMCC Not Allowed

Occurs when home cluster does not want to allow EMCC login (Enable EMCC check box is not checked in the home cluster).

42

Login is unavailable(42)

Logout is unavailable(42)

Invalid ClusterID

Occurs when the remote cluster ID is not valid (happens during remote cluster update)

43

Login is unavailable(43)

Device Security mode error

Device Security Profile associated to the EMCC device should be Non Secure for its Device Security Mode.


For More Information

"Cisco Extension Mobility Cross Cluster,"Cisco Unified Communications Manager Features and Services Guide

"Cisco Extension Mobility," Cisco Unified Communications Manager Features and Services Guide

Cisco Unified Communications Manager Security Guide

Cisco Unified Communications Manager Bulk Administration Guide

Disaster Recovery System Administration Guide

Cisco Extension Mobility Cross Cluster, page 7-3

Cisco Unified Serviceability, RTMT, CAR, and CDRs, page 5-1

Security, page 3-1

Cisco Unified Mobility Dial-Via-Office Forward

Description

The Dial-via-Office Forward feature resembles Mobile Voice Access, except that the request comes through data channel instead of from IVR. From the Cisco Unified Mobile Communicator (CUMC) client, using the data channel, the phone initiates the Dial-via-Office Forward feature. Cisco Unified Communications Manager then returns the Enterprise Feature Access (EFA) Number through the data channel. The mobility identity (MI) calls the Enterprise Feature Access number, and Cisco Unified Communications Manager calls the destination number.

Users that have Cisco Mobile, a Cisco Unified Mobile Communicator application, installed on their mobile devices can take advantage of the Dial-via-Office Forward feature. Cisco Unified Mobile Communicator invokes the Dial-via-Office Forward feature from the mobile device through SIP signaling over the data channel between Cisco Unified Mobile Communicator-Cisco Unified Mobility Advantage and Cisco Unified Mobility Advantage-Cisco Unified Communications Manager to initiate calls to a final target. Because the calls are anchored at the enterprise, the feature offers a cost-saving solution to Cisco Unified Mobile Communicator mobile users.


Note Only Cisco Unified Mobile Communicator devices with the Cisco Mobile client can invoke the Dial-via-Office Forward feature.


Cisco Unified Communications Manager returns the Dial-via-Office Forward (DVO-F) service access number, if the DVO-F service access number has been configured, or the Enterprise Feature Access (EFA) directory number (DN) through the data channel. The Cisco Unified Mobile Communicator client that runs on the mobile phone calls the number that it receives from Cisco Unified Communications Manager. The phone number of the mobile device that makes the DVO-F call gets matched against configured Mobility Identities (MI), thus ensuring that the system places only those calls that authorized users make. If a match occurs, the call request gets sent to the target party. Both complete match and partial match get supported, depending on the setting of the Matching Caller ID with Remote Destination service parameter.

This section covers the following topics for the Dial-via-Office Forward feature:

Configuration of Dial-via-Office Forward in Cisco Unified Communications Manager Administration

Dial-via-Office Forward Service Access Number

Globalization Support for EFA DN and DVO-F Service Access Number

Dial-via-Office Forward Call Characteristics

Example of Dial-via-Office Forward

Dial-via-Office Forward Configuration Tips

Dial-via-Office Forward Limitations

Dial-via-Office-Related SIP Error Codes

Use Case Scenarios for Dial-via-Office Forward

Configuration of Dial-via-Office Forward in Cisco Unified Communications Manager Administration

The following configuration must take place in Cisco Unified Communications Manager Administration for the Dial-via-Office Forward feature to be enabled:

Call Routing > Mobility Configuration

The value of the Enterprise Feature Access Directory Number setting should match the called number and should belong to the correct partition.

System > Service Parameters

The Dial-via-Office Service Access Number can specify an alternate number.

Dial-via-Office Forward Service Access Number

The Dial-via-Office Forward Service Access Number service parameter provides customers the option to set up a dedicated number for Cisco Unified Mobile Communicator users to dial DVO-F while Cisco Unified Communications Manager receives the calls on a different number (for example, through 1-800 support). The DVO-F service access number can specify a toll-free 1-800 number, which the service provider can map to a local number that reaches the enterprise or to any other alternative number for Cisco Mobile clients to invoke DVO-F calls.

The Dial-via-Office Forward Service Access Number service parameter has the following characteristics:

Length specifies up to 24 dialable digits.

Does not specify a partition.

The Dial-via-Office Service Access Number service parameter interacts with the existing Enterprise Feature Access (EFA) DN as follows:

The EFA DN must be configured to invoke the DVO-F feature. Whether DVO-F service access number is configured or not, the EFA DN terminates the inbound call from the Cisco Unified Mobile Communicator device.

For the 183 Session in progress message response, the following rules apply:

If the Dial-via-Office Forward Service Access Number service parameter number is configured, Cisco Unified Communications Manager sends this alternative number to Cisco Unified Mobility Advantage in SDP.

If only EFA DN is configured, Cisco Unified Communications Manager sends the EFA DN to Cisco Unified Mobility Advantage.

For incoming PSTN calls, the following matching takes place:

Called party number gets matched against either the EFA DN or the DVO-F service access number. Either Partial Match or Complete Match takes place. The Partial/Complete Match matches the calling number with the calling number in the original SIP INVITE message that the Cisco Unified Mobility Advantage forwarded to Cisco Unified Communications Manager.

Actually this isn't accurate. Certainly, the system expects the inbound DVO-F call leg from CUMC to be to (called number) EFA DN or DVO-F service access number. But once the call is received on that number, called number is no longer important. The Partial/Complete Match portion is matching the calling number and the match is not made against the EFA/DVO-F service access number, but the calling number specified in the original SIP INVITE forwarded to Unified CM by CUMA.

If a match is found, the voice call correlates with the original SIP Invite, and the Call Await Timer gets stopped. Next, a call gets extended to the called number or target number that the user originally dialed and that the SIP Invite that the Cisco Unified Communications Manager received from Cisco Unified Mobility Advantage contains.

If no match is found, after the Call Await Timer expires, the call disconnects, and the 503 Service Unavailable message gets sent.

Globalization Support for EFA DN and DVO-F Service Access Number

Both the Enterprise Feature Access Directory Number and the Dial-via-Office Forward Service Access Number support the following dialable digits:

0 through 9

+, which must be preceded by backslash (\). Because backslash is not a dialable digit, it does not count toward the maximum length of 24 digits.

* and #

A through D

The preceding special characters can occur in any position.

Dial-via-Office Forward Call Characteristics

Using the preceding example, the following characteristics apply to a Dial-via-Office Forward call:

Based on the INVITE SDP parameter "a=setup:active," Cisco Unified Communications Manager determines that the Cisco Mobile client wants to initiate a DVO-F call.

The Call Await Timer, which is set to 30 seconds, starts when Cisco Unified Communications Manager sends the 183 Session In Progress message to Cisco Unified Mobility Advantage.

If the Cisco Unified Communications Manager does not receive a PSTN call from Cisco Unified Mobile Communicator before the Call Await Timer expires, Cisco Unified Communications Manager sends a "503 Service Unavailable" message and clears resources that are associated with the DVO-F Invite.

When a PSTN call arrives, the following attempts at matching take place:

Cisco Unified Communications Manager tries to match the calling party number against known Mobility Identities (MIs) to determine whether the call will get anchored. Cisco Unified Communications Manager performs the match based on the option that is set for the Matching Caller ID with Remote Destination service parameter (either Partial Match or Complete Match).

Cisco Unified Communications Manager also tries to match the called party number against the EFA DN or DVO-F service access number and determines whether the call is a DVO-F call.

After the call gets established, the user can invoke other Cisco Unified Mobility features, such as hold, resume, conference, transfer, and desk pickup.

Example of Dial-via-Office Forward

The following example illustrates the sequence of events that takes place in an instance of Dial-via-Office Forward (DVO-F):

1. User launches the Cisco Unified Mobile Communicator application and enters 2000 as target number.

2. Cisco Unified Mobile Communicator sends SIP Invite message with target number as 2000.

3. Cisco Unified Communications Manager sends back 183 Session In Progress via the data channel. The SDP parameter specifies the Dial-via-Office Forward service access number or EFA DN.

4. Cisco Unified Mobile Communicator autodials the number that the SDP specifies.

5. Cisco Unified Communications Manager correlates this voice call with the SIP data channel call by comparing the calling party number with the Mobility Identity and by comparing the called party number with the EFA DN or the DVO-F service access number.

6. The call then progresses normally.

Dial-via-Office Forward Configuration Tips

The following configuration tips apply when you are configuring the Dial-via-Office Forward feature:

Cisco Unified Mobile Communicator device must get provisioned with a valid Mobility Identity (MI).

Cisco Unified Mobile Communicator device must register with Cisco Unified Communications Manager.

If the Cisco Unified Mobile Communicator caller ID that the Cisco Unified Communications Manager receives does not match the provisioned MI completely, perform the following configuration:

Set the Matching Caller ID with Remote Destination service parameter to Partial Match.

Specify the number of matched digits in the Number of Digits for Caller ID Partial Match service parameter.

Make sure the ingress gateway gets configured properly, so the called party number matches either the EFA DN or the DVO-F Service Access Number service parameter.

If the called party number is expected to match the EFA DN, ensure that the Inbound Calling Search Space for Remote Destination service parameter is set properly as follows:

If the Trunk or Gateway Inbound Calling Search Space option is chosen, the EFA DN partition must belong to the trunk or gateway calling search space.

If the Remote Destination Profile + Line Calling Search Space option is chosen, the EFA DN partition must belong to the calling search spaces of the Cisco Unified Mobile Communicator device and its enterprise DN.

Dial-via-Office Forward Limitations

The Dial-via-Office Forward (DVO-F) feature specifies these limitations:

DVO-F cannot support simultaneous calls from a single Cisco Unified Mobile Communicator device.

DVO-F relies on caller ID to correlate a PSTN call with the SIP call:

If the called party number cannot go through the GSM network, the DVO-F call fails. A standard service provider announcement will play. Cisco Unified Communications Manager sends a 503 Service Unavailable message after the Call Await Timer expires.

If Cisco Unified Communications Manager does not receive the calling party number (that is, the Cisco Unified Mobile Communicator user blocks his or her caller ID), the DVO-F call fails. A reorder tone will play. Cisco Unified Communications Manager sends the 503 Service Unavailable message after the Call Await Timer expires.

Dial-via-Office-Related SIP Error Codes

Cisco Unified Communications Manager provides specific SIP error codes when a dial-via-office call does not succeed. The following table provides the SIP error codes for unsuccessful dial-via-office calls.

Call Scenario
SIP Error Code

Target number is not routable.

404 Not Found

Target is busy.

486 Busy Here

Cisco Unified Mobile Communicator hangs up before target answers.

487 Request Terminated

Cisco Unified Mobile Communicator sends SIP CANCEL.

487 Request Terminated

Cisco Unified Mobile Communicator tries to make a call without successful registration.

503 Service Unavailable

Cisco Unified Mobile Communicator tries to make a call when there are already two outstanding calls on the enterprise line.

486 Busy Here

Cisco Unified Mobile Communicator tries to make a DVO-F call when there is an outstanding pending DVO-F call (awaiting PSTN call).

487 Request Terminated (on the first call)


Use Case Scenarios for Dial-via-Office Forward

The Dial-via-Office Forward feature supports the following use case scenarios:

1. Enterprise has configured EFA DN only.

The DVO-F feature succeeds only when the Cisco Unified Mobile Communicator client automatically dials the exact EFA DN and Cisco Unified Communications Manager also receives the identical call party number.

Example

EFA DN = 1239876

DVO-F Service Access Number service parameter = EMPTY

Cisco Unified Communications Manager sends 1239876 in 183 message and receives PSTN call to 1239876.

2. Enterprise provides a 1-800 toll-free number for DVO-F calls.

Enterprise sets up a toll-free number, which may be mapped to an actual number (ring-to number) when the service provider receives the call.

If the ring-to number gets applied, administrator must configure the toll-free number (for example, 18008889999) by using the Dial-via-Office Forward Service Access Number service parameter and the ring-to number (for example, 4081239876) as the EFA DN.

Example

EFA DN = 1239876 (localized format, depending on service provider)

DVO-F Service Access Number service parameter = 18008889999

Cisco Unified Communications Manager sends 18008889999 in 183 Session in progress message and receives PSTN call, which maps to 1239876.

3. Enterprise provides globalized number for DVO-F calls

Enterprise sets up a globalized access number, which allows its Cisco Unified Mobile Communicator users to invoke the DVO-F calls anywhere in the world without the need to know the international escape code for the country where they are located.

If the service provider delivers only a localized number, administrator must configure the globalized number (for example, \+14081239876) as the DVO-F Service Access Number service parameter and the localized number that Cisco Unified Communications Manager receives (for example, 1239876) as the EFA DN.

Example

EFA DN = 1239876 (localized format, depending on service provider)

DVO-F Service Access Number service parameter = \+14081239876 (requires backslash as escape for + character)

Cisco Unified Communications Manager sends +14081239876 in message 183 Session in progress and receives PSTN call, which maps to 1239876.

GUI Changes

No GUI changes exist for this feature.

Service Parameter and Enterprise Parameter Changes

No service parameter nor enterprise parameter changes exist for this feature.

Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 8.0(1), you can configure this feature.

Serviceability Considerations

No serviceability considerations exist for this feature.

BAT Considerations

No Bulk Administration Tool 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 nor CTI considerations exist for this feature.

Phones That Support This Feature

The list of devices that support the Dial-via-Office Forward capability within the Cisco Unified Mobility feature varies per version and device pack.

Use the Cisco Unified Reporting application to generate a complete list of devices that support Mobility for a particular release and device pack. To do so, follow these steps:

1. Start Cisco Unified Reporting by using any of the methods that follow.

The system uses the Cisco Tomcat service to authenticate users before allowing access to the web application. You can access the application

by choosing Cisco Unified Reporting in the Navigation menu in Cisco Unified Communications Manager Administration and clicking Go.

by choosing File > Cisco Unified Reporting at the Cisco Unified Real Time Monitoring Tool (RTMT) menu.

by entering https://<server name or IP address>:8443/cucreports/ and then entering your authorized username and password.

2. Click System Reports in the navigation bar.

3. In the list of reports that displays in the left column, click the Unified CM Phone Feature List option.

4. Click the Generate a new report link to generate a new report, or click the Unified CM Phone Feature List link if a report already exists.

5. To generate a report of all devices that support Cisco Unified Mobility, choose these settings from the respective drop-down list boxes and click the Submit button:

Product: All

Feature: Mobility

The List Features pane displays a list of all devices that support the Cisco Unified Mobility feature. You can click on the Up and Down arrows next to the column headers (Product or Protocol) to sort the list.

For additional information about the Cisco Unified Reporting application, refer to the Cisco Unified Reporting Administration Guide, which you can find at this URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.

For More Information

For more information about configuring Cisco Unified Mobility Advantage and the Cisco Unified Mobile Communicator to operate with Cisco Unified Communications Manager, see the following documents:

"Configuring Cisco Unified Communications Manager for Use With Cisco Unified Mobility Advantage" chapter in Installing and Configuring Cisco Unified Mobility Advantage at http://www.cisco.com/en/US/products/ps7270/prod_installation_guides_list.html.

Configuring Features in Cisco Unified Mobility Advantage: Dial Via Office at http://www.cisco.com/en/US/products/ps7270/products_installation_and_configuration_guides_list.html.

For more information about configuring Cisco Unified Communications Manager Administration for the Dial-via-Office Forward feature, see the following chapters in the Cisco Unified Communications Manager Features and Services Guide:

"Cisco Unified Mobility"

"Cisco Unified Mobility Advantage and Cisco Unified Mobile Communicator Integration"

Cisco Unified Mobility Intelligent Session Control

Description

This feature modifies the behavior of outgoing calls placed from the enterprise directly to mobile phones and anchors such calls to the user desktop number. (Prior to the implementation of this feature, if an enterprise user made a direct call to a mobile phone, the call was treated like a normal outgoing PSTN call: the call got directed to the mobile phone only, the call was not anchored to the user desk phone, and the mobile user could not invoke any mobility features.)

An outgoing call from the enterprise to a remote destination exhibits the following behavior:

Mobile user can use DTMF to invoke midcall features, such as Hold, Resume, Transfer, and Conference.

Mobile user can hang up the call from the mobile phone and pick the call up from the user desk phone.

A direct call to a remote destination from the enterprise gets anchored to the user desk phone; and the time-of-day access, Do Not Disturb, and Delay Before Ringing settings that are configured in the associated remote destination profile get ignored. The direct call goes immediately to the mobile user.

Direct calls to remote destinations behave similarly to calls incoming to Cisco Unified Communications Manager from mobile users. Mobile users have access to the following mobility features:

Midcall features (Hold, Resume, Transfer, Conference)

Session Handoff

Call anchoring

Cisco Unified Communications Manager Administration Configuration Tips

Basic configuration of the Intelligent Session Control feature requires that the administrator configure the value of the Reroute Remote Destination Calls to Enterprise Number service parameter as True.

To access the service parameters in question, execute System > Service Parameters in Cisco Unified Communications Manager Administration. In the Service Parameter Configuration window that displays, specify a server and the Cisco CallManager service. The following service parameters are found in the Clusterwide Parameters (Feature - Reroute Remote Destination Calls to Enterprise Number) pane:

Reroute Remote Destination Calls to Enterprise Number—To enable the feature, specify the value for this service parameter as True. When this parameter is enabled, all outgoing calls to a remote destination get anchored in the enterprise number with which the remote destination associates.

Log Mobile Number in CDR for Rerouted RD Calls—This service parameter determines whether to log the mobile number or the enterprise number in the call detail record (CDR) when outgoing calls to the remote destination get anchored. If set to False, the enterprise number gets logged. If set to True, the mobile number gets logged.

Ignore Call Forward All on Enterprise DN—This service parameter determines whether to ignore the call forward all (CFA) setting that is configured on the enterprise number when outgoing calls to the remote destination get anchored. If set to True, the CFA gets ignored; if set to False, the CFA setting gets applied.

The following service parameters, found in the Clusterwide Parameters (System - Mobility) pane, also affect the behavior of the Intelligent Session Control feature:

Matching Caller ID with Remote Destination—If this service parameter is set to Complete Match, all digits of the calling number must match for the call to connect to the remote destination. If this service parameter is set to Partial Match, partial matches are allowed and the Number of Digits for Caller ID Partial Match service parameter applies.

Number of Digits for Caller ID Partial Match—The number of digits that this service parameter specifies applies to partial matches if the Matching Caller ID with Remote Destination service parameter is set to Partial Match.


Note For each service parameter, click the service parameter name in Cisco Unified Communications Manager Administration for a complete definition of that service parameter.


Additional Call Processing Details for Intelligent Session Control

If more than one line is configured for the matching remote destination profile for the dialed number, Cisco Unified Communications Manager uses the first matched line to route the call. Because the direct call to mobile number gets matched against the enterprise number, all enterprise number intercepts are honored, including Call Intercept on enterprise number when Call Intercept gets supported for enterprise number. The forward all intercept on enterprise number gets ignored based on the service parameter, Ignore Forward All on Enterprise DN. If this service parameter is set to true, Cisco Unified Communications Manager ignores forward all intercept on enterprise number and still directs the call to the mobile phone. If this service parameter is set to false, Cisco Unified Communications Manager still enables CFA setting on enterprise number and, if configured, sends the call to CFA destination.

This feature does not anchor direct calls to mobile number if the call to mobile number gets sent via an overlap-sending-enabled trunk or gateway. In this case, the call to mobile number does not get anchored.

Refer to the "EMCC Restrictions" section for additional restrictions that apply to this feature.

Troubleshooting the Intelligent Session Control Feature

Perform the following checks if the Intelligent Session Control feature does not function as expected:

Ensure that the Reroute Remote Destination Calls to Enterprise Number service parameter is set to True in the Service Parameter Configuration window.

Ensure that the caller ID matches the remote destination number as specified by the Matching Caller ID with Remote Destination setting (either complete match or partial match).

Ensure that a trace line such as the following prints in the Cisco Unified Communications Manager SSI log after the number gets dialed:

10/14/2008 15:09:26.507 CCM|Digit analysis: getDaRes - Remote Destination [9725782583]|*^*^*

Ensure that the enterprise number Line Association check box is checked in the Remote Destination Configuration window (Device > Remote Destination).

Ensure that the route pattern partition is part of the calling search space (CSS) that is configured as Rerouting CSS in the Remote Destination Profile Configuration window (Device > Device Settings > Remote Destination Profile).

Use Case Scenarios for Intelligent Session Control

The Intelligent Session Control feature supports these use case scenarios:

The Reroute Remote Destination Calls to Enterprise Number service parameter is set to False.

The Reroute Remote Destination Calls to Enterprise Number service parameter is set to True.

The Ignore Call Forward All on Enterprise DN service parameter is set to False.

The following sections discuss the configuration that takes place in order to demonstrate each user case for the Intelligent Session Control feature.

Use Case 1: Reroute Remote Destination Calls to Enterprise Number service parameter is set to False

In this use case, the following configuration takes place prior to the placement of the direct call from Cisco Unified Communications Manager to the remote destination:

1. Reroute Remote Destination Calls to Enterprise Number service parameter is set to False.

2. Number of Digits for Caller ID Partial Match service parameter specifies 7 digits for partial match.

3. Phone A DN specifies 5137000.

4. Phone B DN specifies 5135282 with owner user ID gbuser1 and remote destination (RD) specifies 9725782583.

5. Route pattern 9.XXXXXXXXXX with DDI as PreDot.

6. Route pattern points to the rcdn-gw gateway.

Figure 2-18 illustrates the setup for the direct call to the remote destination when the Reroute Remote Destination Calls to Enterprise Number service parameter is set to False.

Figure 2-18 Use Case 1: Reroute Remote Destination Calls to Enterprise Number Service Parameter Is Set to False

The following action initiates the feature behavior in this use case:

Phone A DN 5137000 user calls the mobile phone by dialing 05782583.

The following call processing takes place:

1. The translation pattern gets matched and the called number gets transformed to 99725782583.

2. The route pattern 9.XXXXXXXXXX gets matched.

3. After the route pattern removes the leading (PreDot) 9, the number specifies 9725782583.

4. No remote destination mapping to enterprise number occurs.

5. The call extends only to the mobile user via the gateway: the call does not get anchored at the enterprise number with which this remote destination associates.

Use Case 2: Reroute Remote Destination Calls to Enterprise Number service parameter is set to True

In this use case, the following configuration takes place prior to the placement of the direct call from Cisco Unified Communications Manager to the remote destination:

1. Reroute Remote Destination Calls to Enterprise Number service parameter is set to True.

2. Number of Digits for Caller ID Partial Match service parameter specifies 7 digits for partial match.

3. Phone A DN specifies 5137000.

4. Phone B DN specifies 5135282 with owner user ID gbuser1 and remote destination (RD) specifies 9725782583.

5. Route pattern 9.XXXXXXXXXX with DDI as PreDot.

6. Translation pattern 0.XXXXXXX with DDI as PreDot and prefix digits specify 9972.

7. Route pattern points to the rcdn-gw gateway.

The following action initiates the feature behavior in this use case:

Phone A DN 5137000 user calls the mobile phone by dialing 05782583.

The following call processing takes place:

1. The translation pattern gets matched and the called number gets transformed to 99725782583.

2. The route pattern 9.XXXXXXXXXX gets matched.

3. After the route pattern removes the leading (PreDot) 9, the number specifies 9725782583.

4. Remote destination mapping to enterprise number matches the configured remote destination for phone B.

5. The call gets anchored at the enterprise number of the called user and the call extends to the user remote destination.

6. Phone B enters Remote In Use (RIU) state after the mobile user answers the call.

Use Case 3: Ignore Call Forward All on Enterprise DN service parameter is set to False

In this use case, the following configuration takes place prior to the placement of the direct call from Cisco Unified Communications Manager to the remote destination:

1. Reroute Remote Destination Calls to Enterprise Number service parameter is set to True.

2. Ignore Call Forward All on Enterprise DN service parameter is set to False.

3. Number of Digits for Caller ID Partial Match service parameter specifies 7 digits for partial match.

4. Phone A DN specifies 5137000.

5. Phone B DN specifies 5135282 with owner user ID gbuser1 and remote destination (RD) specifies 9725782583. Call Forward All setting for phone B specifies forwarding to phone C with DN 5138000.

6. Route pattern 9.XXXXXXXXXX with DDI as PreDot.

7. Translation pattern 0.XXXXXXX with DDI as PreDot and prefix digits specify 9972.

8. Route pattern points to the rcdn-gw gateway.

The following action initiates the feature behavior in this use case:

Phone A DN 5137000 user calls the mobile phone by dialing 05782583.

The following call processing takes place:

1. The translation pattern gets matched and the called number gets transformed to 99725782583.

2. The route pattern 9.XXXXXXXXXX gets matched.

3. After transformation, the number specifies 9725782583.

4. Remote destination mapping to enterprise number matches the configured remote destination for phone B.

Restrictions With Intelligent Session Control

The following restrictions apply to this feature as it interacts with other features:

Overlap sending patterns do not get supported for the Intelligent Session Control feature.

The Intelligent Session Control feature does not support direct URI dialing. Therefore, calls made to a SIP URI cannot be anchored to an enterprise number.

If Do Not Disturb (DND) is enabled on a desk phone, the desk phone cannot be placed in the Remote In Use (RIU) state and the call does not get anchored in these cases:

DND is enabled with the call reject option—The call cannot get anchored.

DND is activated by pressing the DND softkey on the desk phone—The call cannot get anchored.

If DND is enabled with the ring off option, however, the call does get anchored.

GUI Changes

No GUI changes to Cisco Unified Communications Manager Administration exist for this feature.

Service Parameter and Enterprise Parameter Changes

No enterprise parameter changes exist for this feature.

The following new service parameters exist for this feature:

Reroute Remote Destination Calls to Enterprise Number

Log Mobile Number in CDR for Rerouted RD Calls

Ignore Call Forward All on Enterprise DN

See the "Cisco Unified Communications Manager Administration Configuration Tips" section for details about accessing and configuring these service parameters for the Intelligent Session Control feature.

Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 8.0(1), you can configure this feature.

Serviceability Considerations

No serviceability considerations exist for this feature.

BAT Considerations

No Bulk Administration Tool considerations exist for this feature.

CAR/CDR Considerations

No CAR nor CDR considerations exist for this feature.

Security Considerations

No security considerations exist for this feature.

AXL and CTI Considerations

No AXL nor CTI considerations exist for this feature.

User Tips

For a list of phones that support this feature, see the "Intelligent Session Control" section on page 7-8.

For More Information

"Cisco Unified Mobility," Cisco Unified Communications Manager Features and Services Guide

"Service Parameters Configuration," Cisco Unified Communications Manager Administration Guide

Cisco Unified Mobility Session Handoff

Description

This feature leverages the existing Cisco Unified Communications Manager experience by allowing the user to move voice, video, and meeting sessions and conversations between different Unified Communications clients, such as Cisco Unified Personal Communicator (running on a PC in Softphone as well as CTI control mode), Cisco Unified Mobile Communicator (running on a mobile phone), and Cisco Unified IP Phone Series 9900 and legacy phones that are running SIP.

The conversation can be moved from mobile phone to any other Unified Communications client. All devices that the user owns and that share the same line ring or show a toast, and the call gets answered by whichever device picks it up first. Upon answer, all the other shared-line devices enter Remote in Use mode.

Note that the only client that can actually hand off a session (because it is the only client that has an anchored DTMF path back to Cisco Unified Communications Manager) is Cisco Unified Mobile Communicator. Neither Cisco Unified Personal Communicator nor 9900 series Cisco Unified IP Phones can initiate a session handoff. These devices can, however, handle an incoming session handoff.

The complete Session Handoff feature can move a single call, a conference, and session collaboration among mobile phone, PC, and desk phone. Session Handoff enables a user to move conversations from user mobile phone to user desk phone. Two-touch Session Handoff uses two user inputs: one at the initiating party to hand off and the other at the terminating party to accept.

The major benefit of the Session Handoff feature over Desktop Pickup is that the original conversation can be continued until the handed off call gets answered.

Cisco Unified Communications Manager Administration Configuration Tips

Configuration of the Session Handoff feature entails configuration of specific service parameters and configuration of the mobile device that will hand off calls. See the following topics:

Session Handoff Service Parameters

Mobility Device Configuration for Session Handoff Feature

Session Handoff Service Parameters

To configure service parameters in Cisco Unified Communications Manager Administration, choose the System > Service Parameters menu option. From the Server drop-down list box, choose a server. From the Service drop-down list box, choose the Cisco CallManager service.

The following service parameters must be configured to enable the Session Handoff feature:

Session Handoff Alerting Timer—This service parameter, found in the Clusterwide Parameters (Device - General) pane, determines the length of time that the call that was handed off flashes. The default value specifies 10 seconds, and valid values range from 1 to 999 seconds.

Enterprise Feature Access Code for Session Handoff—This service parameter, found in the Clusterwide Parameters (System - Mobility) pane, specifies the DTMF feature code to trigger session handoff. The default value specifies *74.

For additional details about these service parameters, click the name of the service parameter in the Service Parameter Configuration window in Cisco Unified Communications Manager Administration, which provides a hyperlink to a complete definition of the service parameter.

Mobility Device Configuration for Session Handoff Feature

Perform the following configuration for the mobility device to enable the Session Handoff feature:

Configure the directory number in remote destination profile and the desk phone shared line so that line level directory number and partition match.

Assign the same mobility user ID on the remote destination profile as the desk phone owner user ID to allow session handoff.

To configure the Session Handoff feature for basic Cisco Unified Mobility users, the User ID field setting in the Remote Destination Configuration window should match the Owner User ID field on the (desk) phone configuration window.

To configure the Session Handoff feature for Cisco Unified Mobile Communicator users, both the Owner User ID and the Mobility User ID fields in the Cisco Unified Mobile Communicator device configuration window must match the Owner User ID field on the desk phone configuration window.

Impact of Session Handoff on Other Features

When the user hands off a call, a new call gets presented on the desk phone. While the desk phone is flashing, the following features do not get triggered on the desk phone for the call that was handed off:

iDivert

Call Forward All

DND

Call Forwarding

If the user hands off a call and does not answer from the desk phone within the time that the Session Handoff Alerting Timer service parameter specifies, the existing Remote In Use state on the desk phone gets lost.

Troubleshooting Information for Session Handoff Feature

If a call that is handed off from a mobile phone does not flash the desk phone, perform the following checks:

Check whether Owner User ID for the desk phone matches the User ID of Remote Destination Profile.

In service parameters, check whether Enable Enterprise Feature Access is set to True; also, check whether other DTMF features (Hold [*81], Resume [*83]) are working.

Check the Session Handoff DTMF code (default specifies *74) and Session Handoff Alerting Timer (default specifies 10 seconds) values.

Use Case Scenarios for Session Handoff

The Session Handoff feature supports the following use case scenarios:

Session Handoff using DTMF Tones (*74)

Session Handoff using "Move" Softkey Event

Session Handoff Using DTMF Tones (*74)

For session handoff using DTMF tones (default specifies *74), the following sequence of events takes place:

1. User A calls user B desk phone. Using the Single Number Reach feature, user B answers the call on mobile phone and his desk phone goes into Remote In Use state.

2. User B presses *74 (Session Handoff DTMF code). User B desk phone (a supported phone that is running SCCP or SIP) flashes. User B still talks with user A from user B mobile phone.

3. To move conversation to the desk phone, user B must answer the call from desk phone before the Session Handoff Alerting Timer service parameter (default 10s) expires. After the timer expires, the desk phone stops flashing. User B can still continue conversation from the mobile phone.

Session Handoff Using Move Softkey Event

For session handoff using the Move softkey event, the following sequence of events takes place:

1. Session Handoff gets triggered by using a Move softkey event message that gets embedded inside the SIP Refer message.

2. When Cisco Unified Communications Manager receives the Refer message, Cisco Unified Communications Manager triggers session handoff.


Note If user mobile device disconnects a call for which Session Handoff has been initiated, the call can still be continued by resuming the call at the desk phone prior to the expiration of the Session Handoff Alerting Timer. These cases can occur when a user moves to an area that does not have mobile connectivity, such as an elevator or dead zone/spot.


Restrictions for the Session Handoff Feature

The following restrictions apply to the Session Handoff feature:

Session Handoff can take place only from mobile phone to desk phone. For the other direction, the current Remote Destination Pickup method specifies using Send Call to Mobile Phone.

Only audio call session handoff gets supported.

GUI Changes

No GUI changes exist for this feature.

Service Parameter and Enterprise Parameter Changes

No enterprise parameter changes exist for this feature.

The following new service parameters exist for this feature:

Session Handoff Alerting Timer

Enterprise Feature Access Code for Session Handoff

See the "Session Handoff Service Parameters" section for details of accessing and configuring these service parameters.

Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 8.0(1), you can configure this feature.

Serviceability Considerations

No serviceability considerations exist for this feature.

BAT Considerations

No Bulk Administration Tool considerations exist for this feature.

CAR/CDR Considerations

No CAR nor CDR considerations exist for this feature.

Security Considerations

No security considerations exist for this feature.

AXL and CTI Considerations

No AXL nor CTI considerations exist for this feature.

User Tips

For a list of phones that support this feature, see the "Session Handoff" section on page 7-15.

For More Information

"Cisco Unified Mobility," Cisco Unified Communications Manager Features and Services Guide

"Service Parameters Configuration," Cisco Unified Communications Manager Administration Guide

External Call Control

This section contains information on the following topics:

Description

Chaperone Support for Routing Rules

Announcement Support for Routing Rules

Interactions and Restrictions

Cisco Unified Communications Manager Administration Configuration Tips

Configuration Checklist

GUI Changes

Service Parameter and Enterprise Parameter Changes

Installation/Upgrade (Migration) Considerations

Serviceability Considerations

CAR/CDR Considerations

Security Considerations

AXL and CTI Considerations

User Tips

For More Information

Description

Cisco Unified Communications Manager 8.0(1) supports the external call control feature, which enables an adjunct route server to make call-routing decisions for Cisco Unified Communications Manager by using the 8.0(1) Cisco Unified Routing Rules Interface. When you configure external call control, Cisco Unified Communications Manager issues a route request that contains the calling party and called party information to the adjunct route server. The adjunct route server receives the request, applies appropriate business logic, and returns a route response that instructs Cisco Unified Communications Manager on how the call should get routed, along with any additional call treatment that should get applied.

The adjunct route server can instruct Cisco Unified Communications Manager to allow, divert, or deny the call, modify calling and called party information, play announcements to callers, reset call history so adjunct voice mail and IVR servers can properly interpret calling/called party information, and log reason codes that indicate why calls were diverted or denied. The following examples show how external call control can work:

Best Quality Voice Routing—The adjunct route server monitors network link availability, bandwidth usage, latency, jitter, and MOS scores to ensure calls are routed through voice gateways that deliver the best voice quality to all call participants.

Least Cost Routing—The adjunct route server is configured with carrier contract information such as Lata and Inter-Lata rate plans, trunking costs, and burst utilization costs to ensure calls are routed over the most cost effective links.

Ethical Wall—The adjunct route server is configured with corporate policies that determine reachability; for example, Is user 1 allowed to call user 2?. When Cisco Unified Communications Manager issues a route request, the route server sends a response that indicates whether the call should be allowed, denied, or redirected to another party.

For more information on the Cisco Unified Routing Rules interface, refer to the Cisco Unified Communications Manager XML Developers Guide for Release 8.0(1) at http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_programming_reference_guides_list.html.

In Cisco Unified Communications Manager Administration, you enable external call control on translation patterns by assigning a configured external call control profile to the translation pattern. The following example demonstrates how external call control works in your network:

1. Cisco Unified Communications Manager receives an incoming call, and the digit analysis engine in Cisco Unified Communications Manager selects the best matching translation pattern.

2. If you assigned a configured external call control profile to the translation pattern, Cisco Unified Communications Manager does not extend the call to the device. Instead, Cisco Unified Communications Manager sends a call-routing query by using XACML (eXtensible Access Control Markup Language) over http or https using the POST method to the route server.

Cisco Unified Communications Manager may include the calling number, transformed calling number, called number or dialed digits, transformed called number, and the trigger point information (string for translation pattern) in the query.

3. Routing rules and business logic on the route server determine how to route the call. The route server sends a call routing directive to Cisco Unified Communications Manager, and Cisco Unified Communications Manager follows the directive to handle the call. When the route server responds to Cisco Unified Communications Manager, the route server sends a XACML directive that consists of a route decision and an obligation. The route decision may include the following values for the decision:

Permit—Call is allowed.

Deny—Call is denied.

Indeterminate—No call routing rule is determined. (usually related to a configuration issue)

Not applicable—No call routing rule matches the request.

The obligation, which contain instructions that are specifically customized for Cisco Unified Communications Manager, gets encoded in Call Instruction XML (CIXML). The obligation must be consistent with the route decision. If it is not consistent, Cisco Unified Communications Manager obeys the route decision. Additionally, the obligation may contain parameters, which provide a reason code or additional tasks that Cisco Unified Communications Manager must perform when handling the call. Table 2-23 describes the obligations and related parameters for the obligation.

Table 2-23 Obligations for External Call Control

Obligation
Description
Parameters for Obligation

Reject

The adjunct route server may issue a Reject obligation for a Permit or Deny decision.

Cisco Unified Communications Manager rejects the call, and the caller receives a fast busy tone.

If the route decision is Deny and no obligation gets sent, Cisco Unified Communications Manager treats the call as if a Reject obligation is issued.

The reject obligation may contain the following parameters:

Announce—Cisco Unified Communications Manager plays a specified announcement, identified by [id], to the caller that indicates that the call is rejected.

Reason—A string indicates why the call was rejected; the reason string is used for alarm and logging purposes. When the reason indicates that a route violation occurred, the alarm, CallAttemptBlockedByPolicy, gets raised for the event.

Continue

The route decision must be Permit for the Continue obligation to be used. If the decision is Deny, then the obligation is ignored.

Cisco Unified Communications Manager routes the call to the current destination; that is, Cisco Unified Communications Manager manipulates the digits as expected and routes the call.

Modified calling/called numbers in the continue obligation override the result of the transformation on the translation pattern and may change the destination of the call.

If the adjunct route server issues a Permit decision and no obligation gets sent, Cisco Unified Communications Manager treats the call as if a Continue obligation is issued.

The continue obligation may contain the following parameters, which are optional:

Greeting—Cisco Unified Communications Manager plays an announcement, identified by [id], to the caller before connecting the caller to the called party.

Modify—The adjunct route server overwrites the calling and called party transformation that is configured for the translation pattern. Cisco Unified Communications Manager changes the calling or called number(s) to the numbers that are provided in the directive. If the number is not included in the directive, the configuration for the route pattern or translation pattern applies.

Divert

The route decision must be Permit for the Divert obligation to be used.

Cisco Unified Communications Manager redirects the call to another destination, which is represented by the destination parameter, a mandatory parameter of the divert obligation.

Call diversions by the adjunct route server may result in multiple diversion hops or a diversion loop. To control the number of hops or to prevent diversion hops, configure the Maximum External Call Control Diversion Hops to Pattern or DN or External Call Control Diversion Maximum Hop Count service parameters.

The divert obligation may contain the following parameters:

Destination (mandatory parameter)—Cisco Unified Communications Manager diverts the call to the provided number or to the voice mailbox of the original called party.

Reason—The reason indicates that a chaperone must monitor and/or record the call.

Modify—For the current hop of the call, the adjunct route server includes updated calling or called numbers. If the number is not included in the directive, the configuration for the route pattern or translation pattern applies. Be aware that updated numbers may display on the phone, and the modified values get written to the CDRs.

Reset Call History—Cisco Unified Communications Manager redirects the call, and the last or all previous call hops get deleted from the call history.


Chaperone Support for Routing Rules

If routing rules from the adjunct route server state that a chaperone must be present on a call, you must configure chaperone support in Cisco Unified Communications Manager Administration. In this case, the adjunct route server sends the following routing directive to Cisco Unified Communications Manager:

Permit decision

Divert obligation that contains reason = chaperone.

A chaperone is a designated phone user who can announce company policies to the call, monitor the call, and record the call, if required. Cisco Unified Communications Manager provides the following capabilities to support chaperone functionality, as directed by the adjunct route server:

Cisco Unified Communications Manager can redirect an incoming call to a chaperone or hunt group/list of chaperones.

Cisco Unified Communications Manager can provide a chaperone with the ability to record a call.

When the chaperone is connected to the caller or when the chaperoned conference is established, the Record softkey or PLK (depending on the phone model) becomes active on the phone so that the chaperone can invoke call recording. Call recording occurs for the current call only, and call recording stops when the current call ends. Messages that indicate the status of recording may display on the phone when the chaperone presses the recording softkey/PLK.


Tip For a list of configuration tasks that you must perform in Cisco Unified Communications Manager Administration to set up chaperon support, see the "Configuration Checklist for EMCC" section.


Chaperone restrictions exist so that the parties that are involved in the call cannot converse without the presence of the chaperone. The following restrictions exist for chaperones:

The chaperone cannot use the phone to put the conference call on hold.

The chaperone cannot use the phone to add parties to a conference after the conference begins because the call must be put on hold for the chaperone to add parties.

After the chaperone creates a conference, the conference softkey gets disabled on the phone; that is, if the phone uses the conference softkey.

Be aware that the other parties on the conference may be able to add additional parties to the conference. The configuration for the Advanced Ad Hoc Conference Enabled service parameter, which supports the Cisco CallManager service, determines whether other parties can add participants to the conference. If the service parameter is set to True, other parties can add participants to the conference.

The chaperone cannot use the phone to transfer the conference call to another party.

When the chaperone leaves the conference, the entire conference drops.

If the chaperone starts recording before making a consultative call to the party that should join the conference, Cisco Unified Communications Manager suspends recording while the chaperone makes the consultative call; recording resumes after the conference is established.

Announcement Support for Routing Rules

Routing rules on the route server may require that Cisco Unified Communications Manager play an announcement for the call; for example, an announcement that states that the call is rejected or an announcement that issues a greeting to the caller before connecting the caller to the called party. When you install Cisco Unified Communications Manager, Cisco-provided announcements and tones install, and the Find and Lists Announcements window in Cisco Unified Communications Manager Administration displays these announcements and tones, which can be used for external call control. (Media Resources > Announcements) All announcements that display in the window support external call control, but the obligation that the route server issues determines which announcement Cisco Unified Communications Manager plays; for example, the obligation from the route server indicates that Cisco Unified Communications Manager must reject the call and play the Custom_05006 announcement.


Tip If you want to use customized announcements, not the Cisco-provided announcements, you can upload the customized announcements in the Announcements Configuration window. For more information on announcements, see the "Announcements Configuration" section.


Interactions and Restrictions

Annunciator—If your routing rules require that an announcement get played for calls, upload or customize the standard announcements in the Announcements window; that is, if you do not want to use the Cisco-provided announcements. (Media Resources > Announcements)

In you upload customized announcements, configure annunciator so that you can use the announcements. (Media Resources > Annunciator)

Best Call Quality Routing for Cisco Unified Communications Manager Calls—If you want to do so, you can set up routing rules on the adjunct route server that determine which gateway should be used for a call when voice quality is a consideration; for example, gateway A provides the best voice quality, so it gets used for the call. In this case, the adjunct route server monitors network link availability, bandwidth usage, latency, jitter, and MOS scores to ensure calls are routed through voice gateways that deliver the best voice quality to all call participants.

Call Forward—External call control intercepts calls at the translation pattern level, while call forward intercepts calls at the directory number level. External call control has higher priority; that is, for calls that where call forward is invoked, Cisco Unified Communications Manager sends a routing query to the adjunct route server if the translation pattern has an external call control profile assigned to it. Call forwarding gets triggered only when the adjunct route server sends a Permit decision with a Continue obligation to the Cisco Unified Communications Manager.

Be aware that the call diversion hop count service parameter that supports external call control and the call forward call hop count service parameter that supports call forwarding are independent; that is, they work separately.

Call Pickup—When Cisco Unified Communications Manager recognizes that a phone user is trying to pick up a call by using the call pickup feature, external call control does not get invoked; that is, Cisco Unified Communications Manager does not send a routing query to the adjunct route server for that portion of the call.

Chaperones—A chaperone is a designated phone user who can announce company policies to the call, monitor the call, and record the call, if required. Chaperone restrictions exist so that the parties that are involved in the call cannot converse without the presence of the chaperone.

Cisco Unified Mobility—Cisco Unified Communications Manager honors the route decision from the adjunct route server for the following Cisco Unified Mobility features:

Mobile Connect

Mobile Voice Access

Enterprise Feature Access

Dial-via-Office Reverse Callback

Dial-via-Office Forward


Tip To invoke Mobile Voice Access or Enterprise Feature Access, the end user must dial a feature directory number that is configured in Cisco Unified Communications Manager Administration. When the Cisco Unified Communications Manager receives the call, Cisco Unified Communications Manager does not invoke external call control because the called number, in this case, is the feature DN. After the call is anchored, the Cisco Unified Communications Manager asks for user authentication, and the user enters the number for the target party. When Cisco Unified Communications Manager tries to extend the call to the target party, external call control gets invoked, and Cisco Unified Communications Manager sends a call routing query to the adjunct route server to determine how to handle the call.


Cisco Unified Communications Manager does not send a routing query for the following Cisco Unified Mobility features:

Cell pickup

Desk pickup

Session handoff

Conferences—When a phone user creates a conference, external call control may get invoked for the primary call and consultative call.

Directory Numbers—When you configure directory numbers as 4- or 5- digit extensions (enterprise extensions), you need to configure 2 translation patterns if on-net dialing supports 4 or 5 digits. One translation pattern supports globalizing the calling/called numbers, and a second translation pattern supports localizing the calling/called numbers. Assign external call control profile on the translation pattern that is used for globalizing the calling/called numbers.

Do Not Disturb—By default, the DND setting for the user takes effect when the user rule on the adjunct route server indicates that the adjunct route server send a continue obligation. For example, if the adjunct route server sends a continue obligation, and the user has DND-R enabled, Cisco Unified Communications Manager rejects the call.

Emergency Call Handling (for example, 911 or 9.11)—The following caution describes how to handle emergency call handling if you configure external call control.


Caution Cisco strongly recommends that you configure a very explicit set of patterns for emergency calls (for example, 911 or 9.911) so that the calls route to their proper destination (for example, to Cisco Emergency Responder or a gateway) without having to contact the route server for instructions on how to handle the call.

For example, if you configure your system so that all calls that originate from a group of phones use the external call control feature, all calls, including emergency calls, get routed to the route server. In this case, how the calls get handled depends on the rules configuration on the route server. If the route server does not issue a Permit directive (or if the route server does not have a rule or business logic for handling emergency calls), an emergency call may be denied (or there may be a delay in processing the call).

Transfer—When a phone user transfers a call, external call control may get invoked for both the primary call and consultative call. However, Cisco Unified Communications Manager cannot enforce any routing rules from the adjunct route server between the party that transfers and the target of the transfer.

Cisco Unified Communications Manager Administration Configuration Tips

Be aware that routing rules on the route server determine how the call is handled. If your configuration in Cisco Unified Communications Manager Administration conflicts with the routing rule, the routing rule gets used for the call.

See the "Configuration Checklist" section.

Configuration Checklist

Table 2-24 describes the steps that you perform to configure external call control.

Table 2-24 External Call Control Configuration Checklist 

Configuration Steps
Related Procedures and Topics

Step 21 

Set up the Cisco Unified Routing Rules Interface so that the route server can direct Cisco Unified Communications Manager on how to handle calls.

Cisco Unified Communications Manager XML Developers Guide

Routing Rules API, page 6-8

Step 22 

Configure a calling search space that Cisco Unified Communications Manager uses when the route server sends a divert obligation to Cisco Unified Communications Manager. (Call Routing > Call Control > Calling Search Space)

You assign this calling search space to the external call control profile when you configure the profile.

Calling Search Space Configuration, Cisco Unified Communications Manager Administration Guide

Step 23 

Configure the external call control profile(s). (Call Routing > External Call Control Profile)

GUI Changes

Step 24 

For the translation patterns that you want to use with external call control, assign an external call control profile to the pattern. (Call Routing > Translation Pattern)

Description

Step 25 

If the route server uses https, import the certificate for the route server into the trusted store on the Cisco Unified Communications Manager server. (In Cisco Unified Communications Operating System, choose Security > Certificate Management.)

For Cisco Unified Communications Manager systems, you must perform this task on each node in the cluster that can send routing queries to the route server.

GUI Changes

Step 26 

If the route server uses https, export the Cisco Unified Communications Manager self-signed certificate to the route server. (In Cisco Unified Communications Operating System, choose Security > Certificate Management.)

For Cisco Unified Communications Manager systems, you must perform this task for each node in the cluster that can send routing queries to the route server.

Security Considerations

Step 27 

If your routing rules from the route server state that a chaperone must monitor and/or record a call, configure chaperone functionality in Cisco Unified Communications Manager Administration.

For phones where you want to enable recording, set the Built-in-Bridge to On in the Phone Configuration window.

Create a recording profile. Choose Device > Device Settings > Recording Profile, and create a Call Recording Profile for the phones that can record chaperoned conferences.

Apply the recording profile to the line appearance.

Add a SIP trunk to point to the recorder, and create a route pattern that points to the SIP Trunk.

Configure the Play Recording Notification Tone to Observed Target and Play Recording Notification Tone to Observed Connected Target service parameters.

Assign the Standard Chaperone Phone softkey template to the phone that the chaperone uses.

Make sure that the chaperone phone does not have shared lines or multiple directory numbers/lines configured for it. Configure only one directory number for the chaperone phone. (Call Routing > Directory Number or Device > Phone if the phone is already configured)

For the directory number on the chaperone phone, choose Device Invoked Call Recording Enabled from the Recording Option drop-down list box. (Call Routing > Directory Number or Device > Phone if the phone is already configured)

For the directory number on the chaperone phone, enter 2 for the Maximum Number of Calls setting, and enter 1 for the Busy Trigger setting. (Call Routing > Directory Number or Device > Phone if the phone is already configured)

For Cisco Unified IP Phones that support the Record softkey, make sure that the Standard Chaperone Phone softkey template is configured so that only the conference, record, and end call softkeys display on the phone in a connected state.

For Cisco Unified IP Phones that support the Record programmable line keys (PLK), configure the PLK in the Phone Button Template Configuration window.

If you have more than one chaperone in your cluster, add the chaperone DN to the chaperone line group that you plan to assign to the chaperone hunt list. Adding the chaperone to the line group, which belongs to the hunt list, ensures that an available chaperone monitors the call.

Chaperone Support for Routing Rules

Step 28 

If your routing rules require that an announcement get played for some calls and you do not want to use the Cisco-provided announcements, overwrite the Cisco-provided announcements with your customized announcements in the Announcements window. (Media Resources > Announcements)

If you do not use the Cisco-provided announcements, configure annunciator so that you can use your customized announcements. (Media Resources > Annunciator)

Announcement Support for Routing Rules

GUI Changes

Table 2-25 describes the settings that display in the External Call Control Profile window (Call Routing > External Call Control Profile).

Before you configure the external call control profile, configure a calling search space that Cisco Unified Communications Manager uses when the route server sends a divert obligation to Cisco Unified Communications Manager. (Call Routing > Class of Control > Calling Search Space)

After you configure the external call control profile, assign the profile to the translation pattern. (Call Routing > Translation Pattern)


Tip For GUI changes that are related to chaperones, see the "Configuration Checklist" section. For GUI changes for announcements, see the "Announcements Configuration" section.


Table 2-25 External Call Control Profile Configuration Settings 

Field
Description

Name

Enter the name of the external call control profile. Valid entries include alphanumeric characters, hyphen, period, underscore, and blank spaces.

The name that you enter displays in the Find and List External Call Control Profile window and in the External Call Control Profile drop-down list box in the Translation Pattern Configuration window.

Primary Web Service

Enter the URI for the primary adjunct route server, which is the adjunct route server where Cisco Unified Communications Manager sends routing queries to determine how to handle the call.

You can enter http or https in this field. If you enter https, you must import a self-signed certificate from the adjunct route server, and you must export a Cisco Unified Communications Manager self-signed certificate to the adjunct route server.

Enter the URI by using the following formula:

https://<hostname or IPv4 address of primary route server>:<port that is configured on primary route server>/path from route server configuration

For example, enter https://primaryrouteserver:8443/pdp/AuthenticationEndPoint

If you use https, make sure that you enter the hostname that exists in the certificate in this field. (for example, the CN or Common Name in the certificate)

Secondary Web Service

Enter the URI for the redundant adjunct route server, which is the redundant adjunct route server where Cisco Unified Communications Manager sends routing queries to determine how to handle the call. The secondary web service is optional and gets used for load balancing between the primary and secondary route servers if you check the Enable Load Balancing check box. Configuring a secondary web service also ensures redundancy; that is, that an active/standby link is available.

You can enter http or https in this field. If you enter https, you must import a self-signed certificate from the adjunct route server, and you must export a Cisco Unified Communications Manager self-signed certificate to the adjunct route server. If you use https, make sure that you enter the hostname that exists in the certificate in this field.

Enter the URI by using the following formula:

https://<hostname or IPv4 address of secondary route server>:<port that is configured on secondary route server>/path from route server configuration

For example, enter https://secondaryrouteserver:8443/pdp/AuthenticationEndPoint

If you use https, make sure that you enter the hostname that exists in the certificate in this field (for example, the CN or Common Name in the certificate)

Enable Load Balancing

If you want load balancing to occur between the primary and redundant adjunct route server, check this check box. If checked, load balancing occurs in a round robin fashion.

Routing Request Timer

This parameter specifies the maximum time, in milliseconds, that Cisco Unified Communications Manager should wait for the call routing directive from the adjunct route server before allowing or blocking the call, as configured in the Call Treatment on Failures setting in the external call control profile.

The default is 2000; the minimum value is 1000, and the maximum value is 5000.

If this field is left blank, Cisco Unified Communications Manager uses the configuration for the External Call Control Routing Request Timer service parameter, which supports the Cisco CallManager service.

Diversion Rerouting Calling Search Space

From the drop-down list box, choose the calling search space that Cisco Unified Communications Manager uses when the adjunct route server sends a divert obligation to Cisco Unified Communications Manager.

Call Treatment on Failure

From the drop-down list box, choose whether Cisco Unified Communications Manager allows or blocks calls under the following circumstances:

When the adjunct route server does not send the call routing directive to Cisco Unified Communications Manager

When Cisco Unified Communications Manager cannot contact the adjunct route server

When Cisco Unified Communications Manager fails to parse the routing directive (or supplements of the routing directive)

When Cisco Unified Communications Manager receives a 4xx or 5xx message from the adjunct route server

Choosing Allow Calls routes the call to the current destination, as if the adjunct route server issued a Permit decision with Continue obligation.

Choosing Block Calls causes Cisco Unified Communications Manager to clear the call, as if the adjunct route server issued a Deny decision with a Reject obligation.

When failure occurs, an alarm gets logged.


Service Parameter and Enterprise Parameter Changes

To access the service parameters that support the external call control feature, choose System > Service Parameters. Choose the server and the Cisco CallManager service. Then, locate the Clusterwide Parameters (Feature - External Call Control) pane. Table 2-26 describes the service parameters for the external call control feature. For additional information, you can click the question mark help in the Service Parameters window.

Table 2-26 External Call Control Service Parameters 

Service Parameter
Description

External Call Control Diversion Maximum Hop Count

This parameter specifies the maximum number of times the adjunct route server can issue a divert obligation for a single call. The default equals 12. The minimum value is 1, and the maximum value is 500.

Maximum External Call Control Diversion Hops to Pattern or DN

This parameter specifies the maximum number of times that the adjunct route server can issue the divert obligation for a call to a directory number, route pattern, translation pattern, or hunt pilot.

The default is 12; the minimum is 1, and the maximum is 60.

External Call Control Routing Request Timer

This parameter specifies the maximum time, in milliseconds, that Cisco Unified Communications Manager should wait for the call routing directive from the adjunct route server before allowing or blocking the call, as configured in the Call Treatment on Failures setting in the external call control profile.

The default is 2000; the minimum value is 1000, and the maximum value is 5000.

External Call Control Fully Qualified Role And Resource

This parameter specifies the fully qualified role and the resource that Cisco Unified Communications Manager sends to the adjunct route server in the XACML call routing request. The value that you enter matches your configuration on the adjunct route server, and it ensures that the Cisco Unified Communications Manager query points to the correct routing rules on the adjunct route server.

The default equals CISCO:UC:UCMPolicy:VoiceOrVideoCall, where CISCO:UC:UCMPolicy represents the role on the adjunct route server and VoiceOrVideoCall represents the resource on the adjunct route server.

You can enter up to 100 characters, which include alphanumeric characters (A-Z,a-z,0-9) or colons (:). Colons are only allowed between alphanumeric characters.

External Call Control Initial Connection Count To PDP

This parameter specifies the initial number of connections that Cisco Unified Communications Manager establishes to a adjunct route server for handling call routing requests. Ensure that the value for this parameter is less than or equal to the External Call Control Maximum Connection Count To PDP value. If it is not less than or equal to the External Call Control Maximum Connection Count To PDP value, the External Call Control Maximum Connection Count To PDP value gets ignored. This setting applies to each URI that is configured in each external call control profile.

The default is 2; the minimum value is 2, and the maximum value is 20.

External Call Control Maximum Connection Count To PDP

This parameter specifies the maximum number of connections that Cisco Unified Communications Manager establishes to a adjunct route server for handling call routing requests. Ensure that the value for this parameter is greater than or equal to the External Call Control Initial Connection Count To PDP value. If it is not greater than the External Call Control Initial Connection Count To PDP value, the value gets ignored. This setting applies to each URI that is configured in each external call control profile.

The default is 4; the minimum value is 2, and the maximum value is 20.


Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 8.0(1), you can configure this feature.

Serviceability Considerations

New alarms exist for external call control, as described in the "New Alarms in External Call Control" section on page 5-72. New performance counters display, as described in the "Performance Monitoring Counters" section on page 5-6.

CAR/CDR Considerations

New CDR support exists for external call control, as described in the "New CDR Fields to Support External Call Control" section on page 5-15.

Security Considerations

If the route server uses https, import the certificate for the route server into the trusted store on the Cisco Unified Communications Manager server. (In Cisco Unified Communications Operating System, choose Security > Certificate Management.) You must perform this task on each node in the cluster that can send routing queries to the route server.

If the route server uses https, export the Cisco Unified Communications Manager self-signed certificate to the route server. (In Cisco Unified Communications Operating System, choose Security > Certificate Management.) You must perform this task for each node in the cluster that can send routing queries to the route server.

AXL and CTI Considerations

The route server runs a third-party application that uses the Cisco Unified Routing XML interface to communicate with Cisco Unified Communications Manager. For more information on the Cisco Unified Routing XML Interface, see the "Routing Rules API" section on page 6-8.

User Tips

Messages display on the phone when a chaperone records a call. For more information on chaperones, see the "Chaperone Support for Routing Rules" section. For a list of phones that support external call control, see the "External Call Control and Call Chaperone" section on page 7-5.

For More Information

Cisco Unified Communications Manager XML Developers Guide

External Call Control and Call Chaperone, page 7-5

Routing Rules API, page 6-8

Feature Control Policy

This section contains information on the following topics:

"Description" section

"Cisco Unified Communications Manager Administration Configuration Tips and GUI Changes" section

"Service Parameter and Enterprise Parameter Changes" section

"Installation/Upgrade (Migration) Considerations" section

"Serviceability Considerations" section

"BAT Considerations" section

"CAR/CDR Considerations" section

"Security Considerations" section

"User Tips" section

"For More Information" section

Description

Feature Control Policy allows you to enable or disable a particular feature and thereby control the appearance of certain features and softkeys that display on the phone. When you disable a feature, the softkeys for the disabled feature do not appear in any call state.

Feature Control Policies only apply on the following phones:

Cisco Unified IP Phone 9971

Cisco Unified IP Phone 9951

Cisco Unified IP Phone 8961


Note You can customize the appearance of softkeys on other Cisco IP Phones by using softkey templates.


Cisco Unified Communications Manager Administration Configuration Tips and GUI Changes

You can define multiple feature control policies in the system. Once you configured a feature control policy, you must associate the Feature Control Policy to an individual phone, a group of phones, or to all phones in the system.

For information about using Feature Control Policy, see the "Feature Control Policy" chapter of the Cisco Unified Communications Manager Administration Guide.

Service Parameter and Enterprise Parameter Changes

After you have configured a feature control policy, you can apply the policy to all phones on the system. Use the Enterprise Parameters Configuration window to select the Feature Control Policy.

Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature.

Serviceability Considerations

Cisco Unified Serviceability added the following alarms in the BuildStat alarm in the TFTP Alarm Catalog:

FeatureControlPolicyCount

FeatureControlPolicyTime

You can monitor the following performance counters in RTMT.

BuildFeaturePolicyCount—This counter identifies the number of FCP files that were built.

FeaturePolicyChangeNotifications—This counter identifies the number of FCP change notifications that were handled.

BAT Considerations

BAT supports the assignment of a feature control policy when phones are added or updated.

CAR/CDR Considerations

No CAR or CDR considerations exist for this feature.

Security Considerations

No security considerations exist for this feature.

User Tips

No User considerations exist for this feature.

For More Information

"Enterprise Parameters Configuration," Cisco Unified Communications Manager Administration Guide.

"Common Phone Profile Configuration," Cisco Unified Communications Manager Administration Guide.

"Performance Objects and Counters for Cisco Unified Communications Manager," Cisco Unified Real-Time Monitoring Tool Administration Guide

Hotline

This section contains information on the following topics:

Description

Cisco Unified Communications Manager Administration Configuration Tips

GUI Changes

Service Parameter and Enterprise Parameter Changes

Installation/Upgrade (Migration) Considerations

Serviceability Considerations

BAT Considerations

CAR/CDR Considerations

Security Considerations

AXL and CTI Considerations

User Tips

For More Information

Description

The Hotline feature extends the Private Line Automatic Ringdown (PLAR) feature, which allows you to configure a phone so that when the user goes off hook (or the NewCall softkey or line key gets pressed), the phone immediately dials a preconfigured number. The Hotline feature adds the additional restriction that a Hotline phone can only connect to other Hotline phones.

Hotline phones typically have a restricted feature set. You can restrict the features on a Hotline phone by applying a softkey template to the phone. You can configure a Hotline phone to originate calls only, terminate calls only, or originate and terminate calls.

Hotline uses Route Class Signalling to allow Hotline phones to connect only to other Hotline phones. Hotline also provides configurable call screening based on caller ID, which allows a receiving Hotline phone to screen calls and allow only callers in the screening list to connect.

Cisco Unified Communications Manager Administration Configuration Tips

The Hotline feature uses the existing features translation patterns, route patterns, CSS, partitions, and softkey templates. For information about using these features with the Hotline feature, see the "Hotline" chapter of the Cisco Unified Communications Manager Features and Services Guide.

GUI Changes

This feature includes the following GUI changes:

The Hotline Device check box displays in the phone configuration window (Device > Phone). Check this check box to make this device a Hotline device.

The Route Class Signaling Enabled check box displays in the configuration windows of SIP trunks (Device > Trunk), MGCP PRI gateways, and MGCP T1/CAS gateways (Device > Gateway). From the drop-down list, enable or disable route class signaling for the port. Choose one of the following values:

Default—If you choose this value, the device uses the setting from the Route Class Signaling service parameter.

Off—Choose this value to enable route class signaling. This setting overrides the Route Class Signaling service parameter.

On—Choose this value to disable route class signaling. This setting overrides the Route Class Signaling service parameter.

Route class signaling communicates special routing or termination requirements to receiving devices. It must be enabled for the port to support the Hotline feature.

The Encode Voice Route Class drop-down list displays in the configuration window of MGCP T1/CAS gateways. Check this check box to encode voice route class for voice calls. If this is disabled, the port will not encode the voice route class. The voice route class can get used by downstream devices to identify a call as voice.

The Route Class drop-down list displays in the Translation Pattern Configuration (Call Routing > Translation Pattern) and Route Pattern Configuration (Call Routing > Route/Hunt > Route Pattern) windows. Choose a route class setting for this translation pattern from the drop-down list box:

Default

Voice

Data

Satellite Avoidance

Hotline voice

Hotline data

The route class is a DSN code that identifies the class of traffic for a call. The route class informs downstream devices about special routing or termination requirements.

The Route Next Hop By Calling Party Number check box displays in the Translation Pattern Configuration (Call Routing > Translation Pattern) window. Check this box to enable routing based on the calling party number, which is required for call screening based on caller ID information to work between clusters.

Service Parameter and Enterprise Parameter Changes

Table 2-27 describes the enterprise and service parameters that you can configure for hotline. 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.

Table 2-27 Enterprise and Service Parameters for Hotline

Parameter
Description

Route Class Trunk Signaling Enabled

This parameter determines whether Cisco Unified Communications Manager processes (inbound) and sends (outbound) route class signaling on trunks that support it. Route class trunk signaling enables interworking between IP and TDM switches that use route class. Set it to True to enable route class trunk signaling, or to False to disable it.

This field is required. The default equals True.

SIP Satellite Avoidance Route Class Label

This parameter specifies a label representing the Satellite Avoidance route class in SIP signaling, as defined by the owner of the domain name specified in the SIP Route Class Naming Authority service parameter. Cisco Unified Communications Manager combines the value in this parameter with the value in the SIP Route Class Naming Authority parameter to create the complete signaling syntax for the SIP satellite avoidance route class value. This label proves useful when interworking with TDM networks that make routing decisions based on satellite avoidance route class. You can change this parameter based on your own vendor- specific or deployment-specific requirements. Make certain that the far-end switch expects to receive the same value that you configure in this parameter. Refer to the help text for the service parameter SIP Route Class Naming Authority for additional information pertinent to this parameter.

The following rules apply to values that you specify for this parameter:

Maximum of 64 characters.

Only alphanumeric (A-Z, a-z,0-9) or dash (-) characters are allowed.

Dashes are only allowed between alphanumeric characters.

This field is required and hidden. The default equals nosat.

SIP Hotline Voice Route Class Label

This parameter specifies a label representing the Hotline Voice route class in SIP signaling, as defined by the owner of the domain name specified in the SIP Route Class Naming Authority service parameter. Cisco Unified Communications Manager combines the value in this parameter with the value in the SIP Route Class Naming Authority parameter to create the complete signaling syntax for the SIP Hotline Voice route class value. This label proves useful when interworking with TDM networks that make routing decisions based on Hotline Voice route class. You can change this parameter based on your own vendor-specific or deployment-specific requirements. Make certain that the far-end switch expects to receive the same value that you configure in this parameter. Refer to the help text for the service parameter SIP Route Class Naming Authority for additional information pertinent to this parameter.

The following rules apply to values that you specify for this parameter:

Maximum of 64 characters.

Only alphanumeric (A-Z, a-z,0-9) or dash (-) characters are allowed.

Dashes are only allowed between alphanumeric characters.

This field is required. The default equals hotline.

SIP Hotline Data Route Class Label

This parameter specifies a label representing the Hotline Data route class in SIP signaling, as defined by the owner of the domain name specified in the SIP Route Class Naming Authority service parameter. Cisco Unified Communications Manager combines the value in this parameter with the value in the SIP Route Class Naming Authority parameter to create the complete signaling syntax for the SIP Hotline Data route class value. This label proves useful when interworking with TDM networks that make routing decisions based on Hotline Data route class. You can change this parameter based on your own vendor-specific or deployment-specific requirements. Make certain that the far-end switch expects to receive the same value that you configure in this parameter. Refer to the help text for the service parameter SIP Route Class Naming Authority for additional information pertinent to this parameter.

The following rules apply to values that you specify for this parameter:

Maximum of 64 characters.

Only alphanumeric (A-Z, a-z,0-9) or dash (-) characters are allowed.

Dashes are only allowed between alphanumeric characters.

This field is required. The default equals hotline-ccdata.


Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 8.0(1), you can configure this feature.

Serviceability Considerations

No 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

No user tips exist for this feature.

For More Information

Hotline, Cisco Unified Communications Manager Features and Services Guide

Hunt List Enhancements

This section contains information on the following topics:

Description

Cisco Unified Communications Manager Administration Configuration Tips

GUI Changes

Service Parameter and Enterprise Parameter Changes

Installation/Upgrade (Migration) Considerations

Serviceability Considerations

BAT Considerations

CAR/CDR Considerations

Security Considerations

AXL and CTI Considerations

User Tips

For More Information

Description

This feature adds the following enhancements to hunt lists and hunt pilots:

You can assign a hunt pilot an alerting name, which gets displayed on phones that the hunt pilot dials when it receives an incoming call.

You can include hunt pilots in call pickup groups.

Line group members can pick up an alerting call if they are included in a call pickup group even though the hunt pilot is not in a call pickup group.

Cisco Unified Communications Manager Administration Configuration Tips

No configuration tips exist for this feature.

GUI Changes

This feature adds the fields described in Table 2-28 to the Hunt Pilot Configuration window (Call Routing > Route/Hunt > Hunt Pilot).

Table 2-28 SIP Trunk Profile New Fields 

Field
Description

Alerting Name

Enter an alerting name for the hunt pilot in UNICODE format. This name gets displayed on phones that the hunt pilot dials when it receives an incoming call. Calling party information also gets displayed on the phones. The phone users can use this information to answer the call accordingly.

ASCII Alerting Name

Enter an alerting name for the hunt pilot in ASCII format. This name gets displayed on phones that the hunt pilot dials when it receives an incoming call. Calling party information also gets displayed on the phones. The phone users can use this information to answer the call accordingly.


Service Parameter and Enterprise Parameter Changes

Table 2-29 describes the enterprise and service parameters that you can configure for hotline. 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.

Table 2-29 Enterprise and Service Parameters for Hunt List Enhancements

Parameter
Description

Allow Calls to be picked up from Line Group Members

Default specifies False. When this parameter is set to True, any call pickup group configuration at the hunt pilot gets ignored. Alerting calls at the hunt list will neither get notified for pick up to hunt pilot's call pickup group, nor will those calls get picked up. When this parameter is set to False, any call pickup group configuration at the line group members gets ignored.


Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 8.0(1), you can configure this feature.

Serviceability Considerations

No serviceability considerations exist for this feature.

BAT Considerations

No BAT considerations exist for this feature.

CAR/CDR Considerations

For new CDR fields, see the "New CDR Fields for Hunt List Support" section on page 5-17.

Security Considerations

No security considerations exist for this feature.

AXL and CTI Considerations

No AXL or CTI considerations exist for this feature.

User Tips

No user tips exist for this feature.

For More Information

Hunt Pilot Configuration, Cisco Unified Communications Manager Administration Guide

Call Pickup, Cisco Unified Communications Manager Features and Services Guide

Improved Phone Administration

This section contains information on the following topics:

Description

Cisco Unified Communications Manager Administration Configuration Tips

GUI Changes

Service Parameter and Enterprise Parameter Changes

Installation/Upgrade (Migration) Considerations

Serviceability Considerations

BAT Considerations

CAR/CDR Considerations

Security Considerations

AXL and CTI Considerations

User Tips

For More Information

Description

The following changes to Cisco Unified Communications Manager Administration improve phone administration:

Administrators can customize the End User, Phone, DN, and LA Configuration window.

When you add a new phone, you can choose a phone template that was created by the Bulk Administration Tool to configure automatically some of the phone configuration settings, based on the template.

Cisco Unified Communications Manager Administration Configuration Tips

No configuration tips exist for this feature.

GUI Changes

Fields in the End User, Phone, DN, and LA Configuration window have the following check boxes next to them, which you can use to customize those fields:

Default—Enter a value in the field, then check the Default check box to make that value the default value. Other users can edit the default value, unless the Read Only check box is checked.

Hidden—Check the Hidden check box to hide the field.

Read Only—Check the Read Only check box to make the field read only.

To save your customization changes, click the Save Settings button. The customizations are system-wide, so all other users will see customizations that you save.

When you add a new phone (Device > Phone), you can choose a phone template that was created by the Bulk Administration Tool to configure automatically some of the phone configuration settings, based on the template.

Service Parameter and Enterprise Parameter Changes

No service parameter or enterprise parameter changes exist for this feature.

Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 8.0(1), you can configure this feature.

Serviceability Considerations

No 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

No user tips exist for this feature.

For More Information

"Cisco Unified IP Phone Configuration" chapter, Cisco Unified Communications Manager Administration Guide

"User and Device Configuration Settings" chapter, Cisco Unified Communications Manager System Guide

Incoming Called Party Settings for H.323 Gateways and Trunks

Description

The H.323 protocol does not support the international escape character, +. To ensure that correct prefixes, including the international escape character, +, get applied for inbound calls over H.323 gateways/trunks, you must configure the incoming called party settings in the service parameter, device pool, H.323 gateway, or H.323 trunk windows; that is, configuring the incoming called party settings ensures that when a inbound call comes from a H.323 gateway or trunk, Cisco Unified Communications Manager transforms the called party number back to the value that was originally sent over the trunk/gateway.

For example, a caller places a call to +19721230000 to Cisco Unified Communications Manager A.

Cisco Unified Communications Manager A receives +19721230000 and transforms the number to 55519721230000 before sending the call to the H.323 trunk. In this case, your configuration indicates that the international escape character + should be stripped and 555 should be prepended for calls of International type.

For this inbound call from the trunk, Cisco Unified Communications Manager B receives 55519721230000 and transforms the number back to +19721230000 so that digit analysis can use the value as it was sent by the caller. In this case, your configuration for the incoming called party settings indicates that you want 555 to be stripped and +1 to be prepended to called party numbers of International type.

Cisco Unified Communications Manager Administration Configuration Tips

If you configure call control discovery and you use H.323 SAF-enabled trunks, you must configure the incoming called party settings to ensure that the correct DN patterns get used with SAF/call control discovery.

GUI Changes

You can configure the incoming called party settings in the service parameter, device pool, H.323 gateway, or H.323 trunk windows. Table 2-30 describes the incoming called party settings.

Table 2-30 Incoming Called Party Number Settings for Device Pools, Gateways, and Trunks 

Setting
Description

Clear Prefix Setting

To delete all prefixes for all called party number types, click Clear Prefix Settings.

Default Prefix Setting

To enter the default value for all prefix fields at the same time, click Default Prefix Settings.

National Number

Configure the following settings to transform incoming called party numbers that use National for the Called Party Number Type.

Prefix—Cisco Unified Communications Manager applies the prefix that you enter in this field to called party numbers that use National for the Called Party Numbering Type. You can enter up to 16 characters, which include digits, the international escape character (+), asterisk (*), or the pound sign (#). You can enter the word, Default, instead of entering a prefix.

Tip 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 called party prefix, which supports both the prefix and strip digit functionality.
Tip 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.

Strip Digits—Enter the number of digits that you want Cisco Unified Communications Manager to strip from the called party number of National type before it applies the prefixes.

Use Device Pool CSS—This setting displays in the Gateway and Trunk Configuration windows, not the Device Pool Configuration window. Check this check box to use the calling search space for the National Number field that is configured in the device pool that is applied to the device.

Calling Search Space—This setting allows you to transform the called party number of National called party number type on the device. If you choose None, no transformation occurs for the incoming called party number. Make sure that the calling search space that you choose contains the called party transformation pattern that you want to assign to this device.

International Number

Configure the following settings to transform incoming called party numbers that use International for the Called Party Number Type.

Prefix—Cisco Unified Communications Manager applies the prefix that you enter in this field to called party numbers that use International for the Called Party Numbering Type. You can enter up to 16 characters, which include digits, the international escape character (+), asterisk (*), or the pound sign (#). You can enter the word, Default, instead of entering a prefix.

Tip 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 called party prefix, which supports both the prefix and strip digit functionality.
Tip 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.

Strip Digits—Enter the number of digits that you want Cisco Unified Communications Manager to strip from the called party number of International type before it applies the prefixes.

Use Device Pool CSS—This setting displays in the Gateway and Trunk Configuration windows, not the Device Pool Configuration window. Check this check box to use the calling search space for the International Number field that is configured in the device pool that is applied to the device.

Calling Search Space—This setting allows you to transform the called party number of International called party number type on the device. If you choose None, no transformation occurs for the incoming called party number. Make sure that the calling search space that you choose contains the called party transformation pattern that you want to assign to this device.

Subscriber Number

Configure the following settings to transform incoming called party numbers that use Subscriber for the Called Party Number Type.

Prefix—Cisco Unified Communications Manager applies the prefix that you enter in this field to called numbers that use Subscriber for the Called Party Numbering Type. You can enter up to 16 characters, which include digits, the international escape character (+), asterisk (*), or the pound sign (#). You can enter the word, Default, instead of entering a prefix.

Tip 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 called party prefix, which supports both the prefix and strip digit functionality.
Tip 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.

Strip Digits—Enter the number of digits that you want Cisco Unified Communications Manager to strip from the called party number of Subscriber type before it applies the prefixes.

Use Device Pool CSS—This setting displays in the Gateway and Trunk Configuration windows, not the Device Pool Configuration window. Check this check box to use the calling search space for the Subscriber Number field that is configured in the device pool that is applied to the device.

Calling Search Space—This setting allows you to transform the called party number of Subscriber called party number type on the device. If you choose None, no transformation occurs for the incoming called party number. Make sure that the calling search space that you choose contains the called party transformation pattern that you want to assign to this device.

Unknown Number

Configure the following settings to transform incoming called party numbers that use Unknown for the Called Party Number Type.

Prefix—Cisco Unified Communications Manager applies the prefix that you enter in this field to called numbers that use Unknown for the Called Party Numbering Type. You can enter up to 16 characters, which include digits, the international escape character (+), asterisk (*), or the pound sign (#). You can enter the word, Default, instead of entering a prefix.

Tip 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 called party prefix, which supports both the prefix and strip digit functionality.
Tip 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.

Strip Digits—Enter the number of digits that you want Cisco Unified Communications Manager to strip from the called party number of Unknown type before it applies the prefixes.

Use Device Pool CSS—This setting displays in the Gateway and Trunk Configuration windows, not the Device Pool Configuration window. Check this check box to use the calling search space for the Unknown Number field that is configured in the device pool that is applied to the device.

Calling Search Space—This setting allows you to transform the called party number of Unknown called party number type on the device. If you choose None, no transformation occurs for the incoming called party number. Make sure that the calling search space that you choose contains the called party transformation pattern that you want to assign to this device.


Service Parameter and Enterprise Parameter Changes

The service parameters support the Cisco CallManager service. To configure the service parameters, click Advanced in the Service Parameter Configuration window for the Cisco CallManager service; then, locate the H.323 pane for the following parameters:

Incoming Called Party National Number Prefix - H.323

Incoming Called Party International Number Prefix - H.323

Incoming Called Party Subscriber Number Prefix - H.323

Incoming Called Party Unknown Number Prefix - H.323

These service parameters allow you to prefix digits to the called number based on the Type of Number field for the inbound offered call. You can also strip a specific number of leading digits before the prefix gets applied. To prefix and strip digits by configuring these parameter fields, use the following formula, x:y, where x represents the exact prefix that you want to add to called number and y represents the number of digits stripped; be aware that the colon separates the prefix and the number of stripped digits. For example, enter 91010:6 in the field, which means that you want to strip 6 digits and then add 901010 to the beginning of the called number. In this example, a national call of 2145551234 becomes 910101234. You can strip up to 24 digits and prefix/add up to than 16 digits.

Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 8.0(1), you can configure this feature.

Serviceability Considerations

No serviceability 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

No user tips exist for this feature.

For More Information

Call Control Discovery

Incoming Number Setting Replaces Unknown Setting on SIP Trunk Page

For the calling party normalization feature, the Incoming Number calling party setting displays in the SIP Trunk page, instead of displaying the Unknown calling party setting. For the calling party normalization feature, the functionality remains the same. If you configured the Unknown settings in a previous release, the values automatically migrate to the Incoming Number setting after an upgrade to Release 8.0(1).

iSAC Codec Support

This section contains information on the following topics:

Description

Service Parameter and Enterprise Parameter Changes

Installation/Upgrade (Migration) Considerations

Serviceability Considerations

BAT Considerations

CAR/CDR Considerations

Security Considerations

AXL and CTI Considerations

User Tips

For More Information

Description

Support for Internet Speech Audio Codec (iSAC) has been added to the system for SIP and SCCP devices, allowing interoperability between SIP and SCCP for this codec. A new option, 32 kbps (iSAC, G.722.1), displays in the Max Audio Bit Rate drop-down list box on the Region Configuration page.


Note This does not include support for H.323 and MGCP devices.


iSAC is an adaptive wideband speech and audio codec, specially designed to deliver wideband sound quality with less delay in both low and medium-bit rate applications.

Use the iSAC codec if you have SCCP or SIP endpoints that support it, and if there are only SCCP or SIP devices in the call path. End users experience high speech audio quality if the iSAC codec is used.

Service Parameter and Enterprise Parameter Changes

No service parameter or enterprise parameter changes exist for this feature.

Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 8.0(1), you can configure this feature.

Serviceability Considerations

No 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

No user tips exist for this feature.

For More Information

Region Configuration, Cisco Unified Communications Manager Administration Guide

System-Level Configuration Settings, Cisco Unified Communications Manager System Guide

Audio Codec Preference By Sound Quality

LDAP Custom Filters

This section contains information on the following topics:

Description

Cisco Unified Communications Manager Administration Configuration Tips

GUI Changes

Service Parameter and Enterprise Parameter Changes

Installation/Upgrade (Migration) Considerations

Serviceability Considerations

CAR/CDR Considerations

Security Considerations

AXL and CTI Considerations

User Tips

For More Information

Description

An LDAP filter filters the results of LDAP searches. The new fields described in Table 2-31 configure LDAP filters.

Table 2-31 LDAP Custom Filter Settings 

Field
Description
LDAP Custom Filter Information

Filter Name

Enter a name for the LDAP filter. The name can contain a maximum of 64 UTF-8 characters.

Filter

Enter a filter. The filter can contain a maximum of 1024 UTF-8 characters. Enclose the filter text within parentheses ().

The LDAP filter filters the results of LDAP searches. LDAP users that match the filter get imported into the Cisco Unified Communications Manager database, while LDAP users that do not match the filter do not get imported.

The filter text that you enter must comply with the regular LDAP search filter standards specified in RFC 4515. It is recommended that you verify the LDAP search filter against the LDAP directory/searchbase by using the ldapsearch command.

You apply LDAP filters to LDAP directories. For more information, see the "LDAP Directory Configuration" chapter in the Cisco Unified Communications Manager Administration Guide. You can apply an LDAP filter to multiple LDAP directories, and to all LDAP directory types for which the filter is valid.


Cisco Unified Communications Manager Administration Configuration Tips

No configuration tips exist for this feature.

GUI Changes

The settings in Table 2-31 display in the new window LDAP Custom Filter (System > LDAP > LDAP Custom Filter).

Service Parameter and Enterprise Parameter Changes

No service parameter or enterprise parameter changes exist for this feature.

Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 8.0(1), you can configure this feature.

Serviceability Considerations

No 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

No user tips exist for this feature.

For More Information

LDAP Custom Filters, Cisco Unified Communications Manager Administration Guide

Understanding the Directory, Cisco Unified Communications Manager System Guide

Licensing—Invalid Status Added to License Unit Report Page

The License Unit Report window displays the status of a license file. For example, the Status column for each license type may display Demo, Missing, Invalid, or Uploaded. If the status is Invalid, verify that the license files have been obtained with a correct license MAC; that is, issue the show status cli command from the command line interface to obtain the license MAC and compare that value to the value that displays in the contents of the license file, which you view in the License File Upload window. If the values do not match, obtain license files for the correct license MAC and upload in the License File Upload window. For more information on cli commands, refer to the Command Line Interface Reference Guide for Cisco Unifed Communications Solutions.

Microsoft Active Directory Application Mode LDAP Server Support

This section contains information on the following topics:

Description

Cisco Unified Communications Manager Administration Configuration Tips

GUI Changes

Service Parameter and Enterprise Parameter Changes

Installation/Upgrade (Migration) Considerations

Serviceability Considerations

BAT Considerations

CAR/CDR Considerations

Security Considerations

AXL and CTI Considerations

User Tips

Description

Cisco Unified Communications Manager can synchronize with Microsoft Active Directory Application Mode LDAP server, in addition to the previously supported LDAP servers (Microsoft Active Directory, iPlanet, SunOne, and OpenLDAP).

Microsoft Active Directory Application Mode support is limited to those directory topologies already supported with a native Active Directory connection. No additional topologies, such as multi-forest, multi-tree single forest, or global catalog are supported.

Follow these steps to synchronize with a Microsoft Active Directory Application Mode LDAP server:


Step 1 Log into Cisco Unified Communications Manager Administration.

Step 2 Choose System > LDAP > LDAP System.

Step 3 Select the Enable Synchronizing from LDAP Server check box.

Step 4 From the LDAP Server Type list, choose Microsoft Active Directory Application Mode.

Step 5 From the LDAP Attribute for User ID list, choose an LDAP attribute value for the user ID.

Step 6 Click the Save button.

Step 7 Choose System > LDAP > LDAP Directory.

Step 8 Click the Add New button.

Step 9 Enter the appropriate settings as described in Table 2-31.

Step 10 Click the Save button.


Table 2-32 LDAP Directory Configuration Settings 

Field
Description
LDAP Directory Information

LDAP Configuration Name

Enter a unique name (up to 40 characters) for the LDAP directory.

LDAP Manager Distinguished Name

Enter the user ID (up to 128 characters) of the LDAP Manager, who is an administrative user that has access rights to the LDAP directory in question.

LDAP Password

Enter a password (up to 128 characters) for the LDAP Manager.

Confirm Password

Reenter the password that you provided in the LDAP Password field.

LDAP User Search Base

Enter the location (up to 256 characters) where all LDAP users exist. This location acts as a container or a directory. This information varies depending on customer setup.

LDAP Directory Synchronization Schedule

Perform Sync Just Once

If you want to perform synchronization of the data in this LDAP directory with the data in the Cisco Unified Communications Manager database only once, check this check box.

Perform a Re-sync Every

If you want to perform synchronization of the data in this LDAP directory with the data in the Cisco Unified Communications Manager database at a regular interval, use these fields.

In the left field, enter a number. In the drop-down list box, choose a value:

hours

days

weeks

months

Cisco Unified Communications Manager can synchronize directory information every 6 hours, which is the minimum value allowed for this field.

Note This field remains active only if you do not check the Perform Sync Just Once check box.

Next Re-sync Time
(YYYY-MM-DD hh:mm)

Specify a time to perform the next synchronization of Cisco Unified Communications Manager directory data with this LDAP directory. Use a 24-hour clock to specify the time of day. For example, 1:00 pm equals 13:00.

User Fields To Be Synchronized
Cisco Unified Communications Manager User Fields
LDAP User Fields
 

User ID

One of the following:

uid

userprincipalName

mail

employeeNumber

telephoneNumber

For these fields, the Cisco Unified Communications Manager data in the field specified at left gets synchronized with the LDAP user data in the field specified at right.

Middle Name

(drop-down list box)

For these fields, the Cisco Unified Communications Manager data in the field specified at left gets synchronized with the LDAP user data in the field specified at right.

For the LDAP User field, choose one of the following values:

middleName

initials

Manager ID

manager

For these fields, the Cisco Unified Communications Manager data in the field specified at left gets synchronized with the LDAP user data in the field specified at right.

Phone Number

(drop-down list box)

For these fields, the Cisco Unified Communications Manager data in the field specified at left gets synchronized with the LDAP user data in the field specified at right.

For the LDAP User field, choose one of the following values:

telephoneNumber

ipPhone

First Name

givenName

For these fields, the Cisco Unified Communications Manager data in the field specified at left gets synchronized with the LDAP user data in the field specified at right.

Last Name

sn

For these fields, the Cisco Unified Communications Manager data in the field specified at left gets synchronized with the LDAP user data in the field specified at right.

Department

departmentnumber

For these fields, the Cisco Unified Communications Manager data in the field specified at left gets synchronized with the LDAP user data in the field specified at right.

Mail ID

(drop-down list box)

For these fields, the Cisco Unified Communications Manager data in the field specified at left gets synchronized with the LDAP user data in the field specified at right.

For the LDAP User field, choose one of the following values:

mail

uid

LDAP Server Information

Host Name or IP Address for Server

Enter the host name or IP address of the server where the data for this LDAP directory resides.

LDAP Port

Enter the port number on which the corporate directory receives the LDAP requests.

Use SSL

Check this check box to use Secured Sockets Layer (SSL) encryption for security purposes.

Note If LDAP over SSL is required, the corporate directory SSL certificate must be loaded into Cisco Unified Communications Manager. The Cisco Unified Communications Operating System Administration Guide documents the certificate upload procedure in the Security chapter.

Add Another Redundant LDAP Server

Click this button to add another row for entry of information about an additional server.


In addition to the user fields that appear in Cisco Unified Communications Manager Administration, the user fields described in Table 33 also get synchronized.

Table 33 Additional Synchronized User Fields

Cisco Unified Communications Manager User Fields
LDAP User Fields

UniqueIdentifier

ObjectGUID

Pager

pager

Mobile

mobile

Title

title

Homephone

homephone


Cisco Unified Communications Manager Administration Configuration Tips

No configuration tips exist for this feature.

GUI Changes

The list of LDAP servers in the LDAP System page (System > LDAP > LDAP System) now includes Microsoft Active Directory Application Mode.

Service Parameter and Enterprise Parameter Changes

No service parameter or enterprise parameter changes exist for this feature.

Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 8.0(1), you can configure this feature.

Serviceability Considerations

No 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

No user tips exist for this feature.

For More Information

LDAP System Configuration, Cisco Unified Communications Manager Administration Guide

LDAP Directory Configuration, Cisco Unified Communications Manager Administration Guide

Park Monitoring

This section contains information on the following topics:

Description

Cisco Unified Communications Manager Administration Configuration Tips

GUI Changes

Service Parameter and Enterprise Parameter Changes

Installation/Upgrade (Migration) Considerations

Serviceability Considerations

BAT Considerations

CAR/CDR Considerations

Security Considerations

AXL and CTI Considerations

User Tips

For More Information

Description

Park monitoring is supported only when a Cisco Unified IP Phone 8961, 9951, or 9971 (SIP phones only) parks a call. Park monitoring then monitors the status of a parked call. The park monitoring call bubble is not cleared until the parked call gets retrieved or is abandoned by the parkee. This parked call can be retrieved using the same call bubble on the parker's phone.


Note Configuring call park numbers and settings are the same procedures as for other phone models.


Cisco Unified Communications Manager Administration Configuration Tips

Cisco Unified Communications Manager provides three clusterwide service timer parameters for park monitoring: Park Monitoring Reversion Timer, Park Monitoring Periodic Reversion Timer, and Park Monitoring Forward No Retrieve Timer. Each service parameter includes a default and requires no special configuration. These timer parameters are for park monitoring only; the Call Park Display Timer and Call Park Reversion Timer are not used for park monitoring. See Table 2-34 for descriptions of these parameters.

Table 2-34 Service Parameters for Park Monitoring

Field
Description

Park Monitoring Reversion Timer

Default is 60 seconds. For Cisco Unified Communications Manager systems, set this timer for each server in a cluster that has the Cisco CallManager service and call park configured. This parameter determines the number of seconds that Cisco Unified Communications Manager waits before prompting the user to retrieve a call that the user parked. This timer starts when the user presses the Park softkey on the phone, and a reminder is issued when the timer expires.

You can override the value specified in this service parameter on a per-line basis in the Directory Number Configuration window (Call Routing > Directory Number), in the Park Monitoring section. Specify a value of 0 to immediately utilize the periodic reversion interval specified in the Park Monitoring Periodic Reversion Timer service parameter (see below). For example, if this parameter is set to zero and the Park Monitoring Periodic Reversion Timer is set to 15, the user will be immediately prompted about the parked call and every 15 seconds thereafter until the Park Monitoring Forward No Retrieve Timer (see below) expires.

Park Monitoring Periodic Reversion Timer

Default is 30 seconds. For Cisco Unified Communications Manager systems, set this timer for each server in a cluster that has the Cisco CallManager service and call park configured. This parameter determines the interval (in seconds) that Cisco Unified Communications Manager waits before prompting the user again that a call has been parked. To be connected to the parked call, the user can simply go off-hook during one of these prompts. Cisco Unified Communications Manager continues to prompt the user about the parked call as long as the call remains parked and until the time specified in the Park Monitoring Forward No Retrieve Timer (see below) expires. Specify a value of 0 to disable periodic prompts about the parked call.

Park Monitoring Forward No Retrieve Timer

Default is 300 seconds. For Cisco Unified Communications Manager systems, set this timer for each server in a cluster that has the Cisco CallManager service and call park configured. This parameter determines the number of seconds that park reminder notifications occur before the parked call is forwarded to the Park Monitoring Forward No Retrieve destination specified in the parker Directory Number Configuration window. (If no forward destination is provided in Cisco Unified Communications Manager Administration, the call is returned to the line that parked the call.) This parameter starts when the time specified in the Park Monitoring Reversion Timer service parameter has expired. When the Park Monitoring Forward No Retrieve Timer expires, the call is removed from park and forwarded to the specified destination or returned to the parker line.



Note To set the timers, choose System > Service Parameters and update the Park Monitoring Reversion Timer, Park Monitoring Periodic Reversion Timer, and Park Monitoring Forward No Retrieve Timer fields in the Clusterwide Parameters (Feature-General) pane.


The Directory Number Configuration window (Call Routing > Directory Number) contains an area called "Park Monitoring," where you can configure the three parameters shown in Table 2-35.

Table 2-35 Park Monitoring Parameters in Directory Number Configuration Window  

Field
Description

Park Monitoring Forward No Retrieve Destination External

When the parkee is an external party, then the call will be forwarded to the specified destination in the parker's Park Monitoring Forward No Retrieve Destination External parameter. If the Forward No Retrieve Destination External field value is empty, the parkee will be redirected to the parker's line.

Park Monitoring Forward No Retrieve Destination Internal

When the parkee is an internal party, then the call will be forwarded to the specified destination in the parker's Park Monitoring Forward No Retrieve Destination Internal parameter. If the Forward No Retrieve Destination Internal is empty, the parkee will be redirected to the parker's line.

Park Monitoring Reversion Timer

This parameter determines the number of seconds that Cisco Unified Communications Manager waits before prompting the user to retrieve a call that the user parked. This timer starts when the user presses the Park softkey on the phone, and a reminder is issued when the timer expires.

Default: 60 seconds

Note If you configure a non-zero value, this value overrides the value of this parameter set in the Service Parameters window. However, if you configure a value of 0 here, then the value in the Service Parameters window will be used.


When a call that was routed via the hunt list is parked, the Hunt Pilot Park Monitoring Forward No Retrieve Destination parameter value is used (unless it is blank) when the Park Monitoring Forward No Retrieve Timer expires. This value is configured in the Hunt Pilot Configuration window (Call Routing > Route/Hunt > Hunt Pilot). If the Hunt Pilot Park Monitoring Forward No Retrieve Destination parameter value is blank, then the call will be forwarded to the destination configured in the Directory Number Configuration window when the Park Monitoring Forward No Retrieve Timer expires.

GUI Changes

Park Monitoring-related fields have been added to the following windows in Cisco Unified Communications Manager administration:

System > Service Parameters

Call Routing > Directory Number

Call Routing > Route/Hunt > Hunt Pilot

Service Parameter and Enterprise Parameter Changes

The following new service parameters have been added for this feature.

Park Monitoring Reversion Timer

Park Monitoring Periodic Reversion Timer

Park Monitoring Forward No Retrieve Timer

Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 8.0(1), you can configure this feature.

Serviceability Considerations

No serviceability considerations exist for this feature.

BAT Considerations

For information on park monitoring configuration in BAT, see the "New Fields in Bulk Administration" section on page 4-6.

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

No user tips exist for this feature.

For More Information

Call Park and Directed Call Park, Cisco Unified Communications Manager Features and Services Guide

SIP Trunk End-To-End RSVP Support

This section contains information on the following topics:

Description

Cisco Unified Communications Manager Administration Configuration Tips

GUI Changes

Service Parameter and Enterprise Parameter Changes

Installation/Upgrade (Migration) Considerations

Serviceability Considerations

BAT Considerations

CAR/CDR Considerations

Security Considerations

AXL and CTI Considerations

User Tips

For More Information

Description

End-to-end RSVP configuration between clusters is available if the clusters are connected by a SIP trunk. This feature supports intercluster RSVP agents. End-to-end RSVP uses RSVP on the entire connection between the end points, and uses only one RSVP agent per cluster.

Consider the following scenario:

endpoint A — agentA — ICT1 — ICT2 — agentB — endpoint B

where A specifies an endpoint in cluster 1, B specifies an endpoint in cluster 2, ICT1 and ICT2 specify the intercluster trunks within clusters 1 and 2, and the RSVP Agents associate with the respective end points.

In this scenario, Cisco Unified Communications Manager establishes an end-to-end RSVP connection between agentA and agentB.

Cisco Unified Communications Manager Administration Configuration Tips

RSVP configuration on a SIP trunk is determined by the SIP profile that is applied to the trunk. To enable end-to-end RSVP on a SIP trunk, configure the trunk's SIP profile as follows:

From the RSVP Over SIP drop-down list, choose E2E.

Set the Fall back to local RSVP field to your preference.

From the SIP Rel1XX Options drop-down list, choose an option other than Disabled.

For more information about SIP trunk configuration, see the "SIP Profile Configuration" chapter of the Cisco Unified Communications Manager Administration Guide.

GUI Changes

This feature adds the fields described in Table 2-36 to the SIP Trunk Profile window (Device > Device Settings  > SIP Profile):

Table 2-36 SIP Trunk Profile New Fields

Field
Description

RSVP Over SIP

This field configures RSVP over SIP trunks. From the drop-down list box, choose the method that Cisco Unified Communications Manager uses to configure RSVP over SIP trunks:

Local RSVP—In a local configuration, RSVP occurs within each cluster, between the end point and the local SIP trunk, but not on the WAN link between the clusters.

E2E—In an end-to-end (E2E) configuration, RSVP occurs on the entire path between the end points, including within the local cluster and over the WAN.

Fall back to local RSVP

Check this box if you want to allow failed end-to-end RSVP calls to fall back to local RSVP to establish the call. If this box is not checked, end-to-end RSVP calls that cannot establish an end-to-end connection will fail.

SIP Rel1XX Options

This field configures SIP Rel1XX, which determines whether all SIP provisional responses (other than 100 Trying messages) get sent reliably to the remote SIP endpoint. Valid values follow:

Disabled—Disables SIP Rel1XX.

Send PRACK if 1XX contains SDP—Acknowledges a 1XX message with PRACK, only if the 1XX message contains SDP.

Send PRACK for all 1XX messages—Acknowledges all1XX messages with PRACK.

If you set the RSVP Over SIP field to E2E, you cannot choose Disabled.


Service Parameter and Enterprise Parameter Changes

No service parameter or enterprise parameter changes exist for this feature.

Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 8.0(1), you can configure this feature.

Serviceability Considerations

No 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

No user tips exist for this feature.

For More Information

Resource Reservation Protocol, Cisco Unified Communications Manager System Guide

Supplementary Services Support for SCCP Gateway Endpoints

This section contains information on the following topics:

Description

Service Parameter and Enterprise Parameter Changes

Installation/Upgrade (Migration) Considerations

Serviceability Considerations

BAT Considerations

CAR/CDR Considerations

Security Considerations

AXL and CTI Considerations

User Tips

For More Information

Description

These updates bring together Supplementary Services support for SCCP gateway endpoints and MLPP support for basic call on SCCP gateways.


Note This feature is supported on analog phones only.


The Supplementary Services support update incorporates the following functionalities:

Call Hold—Users can use the following function during Call Hold interaction with MLPP on SCCP gateways:

Preemption if the new call is higher precedence than both held and active calls.


Note Be aware that Preemption preempts both the held calls, and the active call.


Precedence Call Waiting- Users can use the following functions during Call Waiting interaction with MLPP on SCCP gateways:

Precedence Call Waiting tone support on the gateway

For single active call, new higher precedence call preemption rather than play Precedence Call Waiting

On a phone with ringing precedence calls, an inbound call preempts the lower precedence ringing calls.


Note If the user chooses to invoke the Cancel Call Waiting feature while making a call, Precedence Call Waiting settings get overridden for that call. The Cancel Call Waiting settings apply only on the phone from which it is invoked, and do not affect the phones calling it.
For more information on the Cancel Call Waiting feature, refer to the Cisco Unified Communications Manager Administration Guide.


Allow Call Waiting During an In-Progress Outbound Analog Call Service Parameter—A new service parameter is added to Cisco Unified Communications Manager. This parameter determines whether Cisco Unified Communications Manager allows an inbound call to be presented to a call-waiting-enabled SCCP gateway analog phone, when the analog phone is involved in an outbound call but may be unable to play the call waiting tone. The analog phone may not be able to play the call waiting tone until the outbound call gets to the alerting or connected state. Valid values specify True and False:

True-The call-waiting-eligible analog phone is presented with the inbound call regardless of the phone's ability to play call waiting tone, and the standard call answer time limit applies.

False-Cisco Unified Communications Manager treats this as a normal analog line appearance reaching its Busy Trigger call limit; this treatment could involve forwarding actions, tones, or any other features applicable to the trigger.


Note For information on working with service parameters, refer to the "Configuring Service Parameters for a Service on a Server" section in Cisco Unified Communications Manager Administration Guide.


Service Parameter and Enterprise Parameter Changes

Allow Call Waiting During an In-Progress Outbound Analog Call Service Parameter.

Installation/Upgrade (Migration) Considerations

No special installation or upgrade considerations exist for this feature. After you install or upgrade to Cisco Unified Communications Manager 8.0(1), you can configure this feature.

Serviceability Considerations

No 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

No user tips exist for this feature.

For More Information

Configuring Service Parameters for a Service on a Server, Cisco Unified Communications Manager Administration Guide.