extension mobility cross cluster - cisco · extension mobility cross cluster...

Extension Mobility Cross Cluster

This chapter provides information about Cisco Extension Mobility Cross Cluster feature which allows anenterprise user of one Cisco Unified CommunicationsManager cluster (the home cluster) to log in to a CiscoUnified IP Phone of another Cisco Unified Communications Manager cluster (the visiting cluster) duringtravel as if the user is using the IP phone at the home office.

If a user remains in a single cluster, configuration of the Cisco Extension Mobility feature suffices toprovide the user with extension mobility capabilities. See the ExtensionMobility chapter for a descriptionand configuration details of the Cisco Extension Mobility feature.

Note

• Configure EMCC, page 1

• EMCC Feature, page 8

• System Requirements for EMCC, page 31

• Interactions and Restrictions, page 31

• Install and Activate EMCC, page 36

• Configure EMCC, page 36

• Provide Information to Users, page 45

• Troubleshooting EMCC, page 45

Configure EMCCPerform the following steps to configure Cisco Extension Mobility Cross Cluster in your network. Use thefollowing procedure in conjunction with the Extension Mobility Cross Cluster, on page 1.

Procedure

Step 1 In Cisco Unified Serviceability, choose Tools > Service Activation.Step 2 Choose a server and activate the following CMServices by checking the check box next to each service name:

Cisco Unified Communications Manager Features and Services Guide, Release 9.0(1) OL-24921-01 1

CUCM_BK_CEF0C471_00_cucm-features-and-services-guide_chapter_01010.pdf#unique_18

• Cisco CallManager

• Cisco Tftp

• Cisco Extension Mobility

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

Step 3 Click Save, click OK in response to the popup window, and wait for the services to get activated.Step 4 Create an Extension Mobility phone service:

a) In Cisco Unified Communications Manager Administration, choose Device > Device Settings > PhoneServices.

b) 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#

Change the IP address in both the Service URL and Secure-Service URL fields, unless youdo 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 MobilityIP phone service for the first time, you will set up this IP phone service as an enterprise subscriptionservice. If you do this, all phones and device profiles in the enterprise will automatically subscribeto this IP phone service without needing to subscribe individually.

Note

c) Click Save to save the Extension Mobility phone service.

Step 5 Add a device profile for users who need Extension Mobility. The device profile gets used to overlay with areal device when the user logs in (both for Extension Mobility and Extension Mobility Cross Cluster). Followthese steps:a) In Cisco Unified Communications Manager Administration, choose Device > Device Settings > Device

Profile.b) Add a new device profile for a specific device type with a specific protocol, assigning a meaningful name

to the new device profile.Example: 7975 SCCP Device Profile

c) 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 anduses an IP phone of a different (visiting) cluster. Configure this field as if setting the Calling Search Spacefield in the Phone Configuration window of a local IP phone.

d) Add a directory number (DN) to the new device profile.Example: 4001

e) In the Directory Number Configuration window, choose the Configure Device (<your new device profilename>) option in the Related Links drop-down list box, then click Go.You return to the Device Profile Configuration window.

Cisco Unified Communications Manager Features and Services Guide, Release 9.0(1)2 OL-24921-01

Extension Mobility Cross ClusterConfigure EMCC

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

g) In the popup window that displays, choose the ExtensionMobility service in the Select a Service drop-downlist box.

h) Click Next, then click Subscribe.i) Click Save and close the popup window.j) In the Device Profile Configuration window, click Save.

Step 6 Add users for Cisco Extension Mobility Cross Cluster:a) In Cisco Unified Communications Manager Administration, choose User Management > End User.b) Click Add New to add a new end user.c) In the End User Configuration window that displays, configure at least the following fields:

• User ID

• Password

• PIN

• Last name

• First name

d) In the Extension Mobility pane, check the Enable Extension Mobility Cross Cluster check box.e) Choose the device profile that you configured from the Available Profiles list pane in the Extension

Mobility pane.f) Use the Down arrow to move the device profile to the Controlled Profiles list pane.g) Click Save to save the end user configuration.

Step 7 Enable Extension Mobility on the devices:a) In Cisco Unified Communications Manager Administration, choose Device > Phone.b) Find the phone on which users can perform Extension Mobility or Extension Mobility Cross Cluster.c) For this device, check the Enable Extension Mobility check box in the Extension Information pane.d) In the Phone Configuration window, choose the Subscribe/Unsubscribe Services option in the Related

Links drop-down list box, then click Go.e) In the popup window that displays, choose the ExtensionMobility service in the Select a Service drop-down

list box.f) Click Next, then click Subscribe.g) Click Save and close the popup window.h) In the Phone Configuration window, click Save. If indicated, clickOK in the popup window that displays.

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

Note

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

Note

Step 8 Configure Bulk Certificate Management:a) In Cisco Unified Communications Operating SystemAdministration, choose Security >Bulk Certificate

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

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



This is the centralized secure FTP server that all participating clusters mustshare.

Note

• 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)

c) Click Save.

Step 9 Configure Bulk Certificate Export:a) In Cisco Unified Communications Operating SystemAdministration, choose Security >Bulk Certificate

Management.b) Click the Export icon.c) In the Bulk Certificate Export window that displays, configure the following field: Certificate Type: Alld) 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, TFTP, or Capf certificate(s) gets regenerated onany of its nodes.

Step 10 Consolidate certificates:a) In Cisco Unified Communications Operating SystemAdministration, choose Security >Bulk Certificate

Management > Consolidate > Bulk Certificate Consolidate.Consolidate certificates when all participating clusters have exported their certificates. This option isavailable only if two or more clusters have exported their certificates to the SFTP server.

b) In the window that displays, configure the following field: Certificate Type: Allc) 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 topick up the newly exported certificates.

Step 11 Import certificates:a) In Cisco Unified Communications Operating SystemAdministration, choose Security >Bulk Certificate

Management > Import > Bulk Certificate Import.b) In the window that displays, configure the following field: Certificate Type: Allc) Click Import.

After you import all the certificates on each cluster, for each cluster, you need to restart CiscoCallManager 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 reconsolidatecertificates.

Note

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.



Step 12 To enable EMCC for video calls, configure Common Phone Profile (Device > Device Settings > CommonPhone 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 and check the Override CommonSettings checkbox. (Although this setting may be enabled by default per cluster, it may be necessary to checkthe Override Common Settings checkbox and save the change)

Step 13 Add EMCC devices - Add EMCC Templates:a) In Cisco Unified Communications Manager Administration, choose Bulk Administration > EMCC >

EMCC Template.b) Click Add New.c) 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

d) Click Save.

Step 14 Add EMCC devices - Set default EMCC template.a) In Cisco Unified Communications Manager Administration, choose Bulk Administration > EMCC >

Insert/Update EMCC.b) Click Update EMCC Devices.c) In the Default EMCCTemplate drop-down list box, choose the EMCCDevice Template that you configured.d) Click Run Immediately.e) Click Submit.f) Verify whether the job ran successfully:

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

Step 15 Add EMCC devices - Insert the EMCC Devices:a) In Cisco Unified Communications Manager Administration, choose Bulk Administration > EMCC >

Insert/Update EMCC.b) Click Insert EMCC Devices.c) Change the value in the Number of EMCC Devices to be added field (for example, to 5).d) Click Run Immediately and click Submit.e) Refresh this window and check that the Number of EMCCDevices already in database value now displays

the number of devices that you added (for example, 5).f) 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 Business Edition 5000 systems specify a MaxPhones value of 700.



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

Step 16 Configure enterprise parameters and add a geolocation filter:a) In Cisco Unified Communications Manager Administration, choose System > Enterprise Parameters.b) For the Cluster ID enterprise parameter, configure a unique cluster ID for every participating cluster.c) In Cisco Unified Communications Manager Administration, choose System > Geolocation Filter.d) Click Add New.e) Create a new geolocation filter.

Example name: EMCC Geolocation Filter.

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

Step 17 Configure EMCC feature parameters:a) In Cisco Unified Communications Manager Administration, choose Advanced Features > EMCC >

EMCC Feature Configuration.b) 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

Each feature parameter must be previously configured before you can choose them in the drop-downlist 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.Note

Step 18 Configure one or two intercluster SIP trunks for EMCC.You may configure one trunk for both PSTN Access and RSVP Agent services or one trunk for eachservice. You need no more than two EMCC SIP trunks.

Note

a) In Cisco Unified Communications Manager Administration, choose Device > Trunk.b) Click Add New.c) Specify the following settings:

• Trunk Type: SIP Trunk

• Trunk Service Type: Extension Mobility Cross Clusters

d) Click Next.e) 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.

EMCC trunkmust specify SendGeolocation as True, MTPRequired as False, and UnattendedPortas False.

Note

f) Click Save to save the intercluster SIP trunk for EMCC.

Step 19 Configure EMCC intercluster service profile:a) In CiscoUnified CommunicationsManager Administration, chooseAdvance Features >EMCC >EMCC

Intercluster Service Profile.b) Check the Active check box in the EMCC pane.c) Check the Active check box in the PSTN Access pane.d) In the PSTN Access SIP Trunk drop-down list box, choose a SIP trunk that you configured.e) Check the Active check box in the RSVP Agent pane.f) In the RSVP Agent SIP Trunk drop-down list box, choose another SIP trunk that you configured.

If you configured only one trunk, you can choose the same trunk for RSVP Agent SIP Trunk asfor PSTN Access SIP Trunk.

Note

g) Click Validate to validate your settings.h) If no failure messages display in the popup window, click Save.

Step 20 Configure EMCC remote cluster services:a) In Cisco Unified Communications Manager Administration, choose Advance Features > Cluster View.b) Click Find to display a list of known remote clusters.c) If the remote cluster that you want configure appears, click on the remote cluster and verify the settings.d) If the remote cluster that you want to configure does not appear, clickAddNew and configure the following

settings:

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

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

During EMCC, TFTP check box should always bedisabled.

Note

Step 21 Configure service parameters:a) In Cisco Unified Communications Manager Administration, choose System > Service Parameters.b) From the Server drop-down list box, choose a server.c) From the Service drop-down list box, choose the Cisco Extension Mobility service.d) Click the Advanced button at the top of the window.e) 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.

For EMCC, the call logs always getcleared.

Note

For EMCC, multiple logins are alwaysallowed.

Note



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

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

Related Topics

Extension Mobility Cross Cluster, on page 1EMCC Call Routing, on page 20Configure EMCC, on page 1Configure EMCC Feature Configuration, on page 36EMCC Intercluster Service Profile Configuration, on page 40Remote Cluster Configuration, on page 42Set the Service ParametersCisco Extension Mobility Service Parameters

EMCC FeatureThis section contains information about the EMCC feature and configuration, supported phones, logininstructions and summaries, call processing, and phone security.

EMCC vs. Cisco Extension MobilityRelease 3.1 of Cisco CallManager first offered the Cisco ExtensionMobility feature. Cisco ExtensionMobilitycontinues 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, andfeatures.

• 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 bothclusters.


Extension Mobility Cross ClusterEMCC Feature

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

EMCC SolutionThe 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-registerswith home cluster Cisco Unified Communications Manager.

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

Cisco Extension Mobility Cross Cluster Interactions

See the EMCC Interactions, on page 32 for a list of the interactions between the Cisco Extension MobilityCross Cluster feature and other features.

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 secure and nonsecure phone security profiles are 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


Extension Mobility Cross ClusterEMCC Solution

• 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 acrossthe 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 CiscoExtension 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).

EMCC LoginThis section provides information about EMCC login.

EMCC Login TerminologyThe following figure illustrates the visiting cluster versus a home cluster in Cisco Extension Mobility CrossCluster.

Figure 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.


Extension Mobility Cross ClusterEMCC Login

• 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 clusterthat 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 adevice record that is combined with the end user Extension Mobility (EM) profile in the home cluster, thendirecting the phone to register directly with the home cluster Cisco Unified Communications Manager.

EMCC Login ProgressThe following figure illustrates Cisco Extension Mobility Cross Cluster login when extension mobility findsthe home cluster.

Figure 2: EMCC Login - Extension Mobility Finds Home Cluster



The following figure illustrates Cisco Extension Mobility Cross Cluster login when extension mobilityauthenticates, gives information to home cluster, and prepares home cluster.

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



The following figure illustrates Cisco ExtensionMobility Cross Cluster login when extensionmobility modifiesthe visiting cluster and initiates reregistration.

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

Mini-config specifies a small configuration file built by the visiting cluster to redirect the phone to the homecluster after login.



The following figure illustrates Cisco Extension Mobility Cross Cluster login when extension mobility loginservices complete processing and the phone reregisters.

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

Determine EMCC Supported PhonesThe list of devices that support the Cisco Extension Mobility Cross Cluster varies per version and devicepack.

Use the Cisco Unified Reporting application to generate a complete list of devices that support Cisco ExtensionMobility Cross Cluster 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 webapplication. You can access the application

• by choosing Cisco Unified Reporting in the Navigation menu in Cisco Unified CommunicationsManager 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 thenentering 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.


Extension Mobility Cross ClusterDetermine EMCC Supported Phones

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

5 To generate a report of all devices that support Cisco Extension Mobility Cross Cluster, choose thesesettings 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 ExtensionMobility Cross Clusterfeature. You can click on the Up and Down arrows next to the column headers (Product or Protocol) tosort the list.

For additional information about the Cisco Unified Reporting application, see the Cisco Unified ReportingAdministration Guide.

EMCC ConfigurationSee topics related to configuring EMCC for an overview of the configuration steps to configure Cisco ExtensionMobility Cross Cluster, both in Cisco Unified Communications Manager Administration and in the otherCisco Unified Communications components, such as Cisco Unified Serviceability and the Cisco UnifiedCommunications Operating System.

Related Topics

Configure EMCC, on page 36

View EMCC Active and Remote Login SummaryIn the user home cluster, the administrator can view a list of the cluster users who have logged in from remotedevices.

To do so, the administrator performs the following steps:

Procedure

Step 1 In Cisco Unified Communications Manager Administration, execute Device > Phone.The Find and List Phones window displays.

Step 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 Cisco Unified CommunicationsManager Administration Guide.

Step 3 In any cluster, the administrator can view a list of the cluster devices that have been logged in to either CiscoExtension Mobility or Cisco Extension Mobility Cross Cluster To do so, the administrator performs thefollowing steps:.a) In Cisco Unified Communications Manager Administration, execute Device > Phone.

The Find and List Phones window displays.b) 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 Cisco UnifiedCommunications Manager Administration Guide.


Extension Mobility Cross ClusterEMCC Configuration

EMCC Call ProcessingThis section contains information about EMCC call processing and includes how to obtain help for callprocessing issues.

EMCC Call Processing OverviewThe following figure provides an overview of EMCC call processing.

Figure 6: EMCC Call Processing

EMCC Call Processing CharacteristicsEMCC 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


Extension Mobility Cross ClusterEMCC Call Processing

• 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 interclustertrunk.

◦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 RequirementsCisco 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 emergencypattern gets dialed.

• RSVP agent based CAC

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

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

Note



EMCC Call Processing for Emergency CallsThe following figure illustrates Cisco Extension Mobility Cross Cluster call processing for emergency calls.

Figure 7: EMCC Call Processing for an Emergency Call

Find the Roaming Device PoolFinding 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 geolocationcharacterizing 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 visitingcluster.

• 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 roamingdevice pool while phone registers in home cluster.



Match the Roaming Device PoolThe following figure illustrates matching the roaming device pool by using the geolocation in the home cluster.

Figure 8: Match Roaming Device Pool Using Geolocation in Home Cluster

EMCC Call Processing ConfigurationVisiting cluster configures geolocation for phones that are enabled for extension mobility. This configurationtakes place in the Geolocation field of the Phone Configuration window (Device >Phone) or in the Geolocationfield of the Geolocation Configuration pane of the Device Pool Configuration window (System > DevicePool).

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

• 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 theAdvanced Features > EMCC > EMCC FeatureConfiguration 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 poolas the roaming device pool when the phones log in.



List EMCC PhonesThe home cluster administrator can list all remote devices that are currently registered to this cluster. To doso, executeDevice > Phone. From the Related Links drop-down list box, chooseRemotely 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

• Device Security Mode

EMCC Call ProcessingLogged-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 RoutingCall 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 UScluster will normally not recognize. Home cluster=US, visiting cluster=UK.

• May skip Adjunct CSS configuration if home cluster and visiting cluster share the same emergencypattern.



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 staticdevice CSS.

Adjunct Calling Search Space Functionality

To configure the adjunct CSS, execute System > Device Pool and configure the Adjunct CSS field in theDevice 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 EmergencyPartition for UK.

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

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

Configure Visiting Cluster Emergency PatternConfigure 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 pattern9.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 of EMCCThe 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 connectto 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 tovisiting cluster via PSTN access SIP trunk (EMCC Configuration).

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

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

Local Route Group Using EMCC SIP TrunkThe following figure illustrates local route group routing that uses an EMCC SIP trunk.

Figure 9: Local Route Group Routing Using EMCC SIP Trunk

EMCC Calling Search Space in Device ProfileThe ExtensionMobility 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 userselects this device profile during EMCC login.

Region Configuration for EMCC PhonesRegion 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 (AdvancedFeatures > EMCC > EMCC Feature Configuration) that overrides normal region configuration.

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

• The following EMCC feature parameters for regions apply:

◦EMCC Region Max Audio Bit Rate (See the EMCC Solution, on page 9 for a details of asuggested 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 PhonesRSVP 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 getsdisabled.

◦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 theRSVP 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 CommunicationsManager allocatemedia resources based on the media resource group list that is configured in the home cluster.



RSVP Agent-Based CACThe following figure illustrates Cisco Extension Mobility Cross Cluster for an RSVP Agent-based CallAdmission Control (CAC) basic call.

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

RSVP Agent CAC Hold/Resume by Home PhoneThe following figure illustrates Cisco ExtensionMobility Cross Cluster for an RSVPAgent-basedHold/Resumecall by the home phone.

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



RSVP Agent CAC Hold/resume by Visiting PhoneThe following figure illustrates Cisco ExtensionMobility Cross Cluster for an RSVPAgent-basedHold/Resumecall by the visiting phone.

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

EMCC Call Processing IssuesThis 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 chooseRemotely 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 phonemedia resourcegroup list in visiting cluster).

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

• Cannot make emergency call.

◦EMCC phone does not bind to the correct roaming device pool (Device > Phone, then chooseRemotely 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.



◦Checkwhether all clusters have the same value in EMCCRegion configuration window (AdvancedFeatures > EMCC > EMCC Feature Configuration).

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

Help for EMCC Call Processing IssuesTake the following steps to obtain help for call processing issues:

Procedure

Step 1 Collect detailed traces from both home cluster and visiting cluster.Step 2 Provide detailed description of the call scenario:

a) Identify the EMCC device and the non-EMCC device and its cluster. For example, the EMCC phone doesnot bind to the correct roaming device pool. Use theDevice > Phonemenu option, then chooseRemotelyLogged In Device from the Related Links drop-down list box.

Phone Behavior with EMCCThis section provides information about phone behaviors in an EMCC environment, such as during a WANnetwork failure.

WAN Network FailureThe following figure illustrates WAN network failure when the configuration file is unavailable.


Extension Mobility Cross ClusterPhone Behavior with EMCC

The phone reregisters with the visiting cluster.

Figure 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 reestablishconnection to the home cluster. After several failed attempts, such as failures due to WAN failure, the phoneissues a logout request to the visiting cluster automatically, then the phone reregisters with the visiting clusteras logged out.

EMCC Failure - Registration RejectionThe following figure illustrates EMCC failure when registration rejection occurs.




Figure 14: EMCC Failure - Registration Rejection

EMCC Failure - Home CUCM Unavailable/Interoffice FailureThe following figure illustrates EMCC failure when the home Cisco Unified Communications Manager isunavailable and an interoffice failure occurs.



The phone fails over to SRST.

Figure 15: EMCC Failure - Home Cisco Unified Communications Manager Unavailable/Interoffice Failure

EMCC Failure - Home CUCM Unavailable/inter-Cluster FailureThe following figure illustrates EMCC failure when the home Cisco Unified Communications Manager isunavailable and an inter-cluster failure occurs.




Figure 16: EMCC Failure - Home Cisco Unified Communications Manager Unavailable/Inter-Cluster Failure

EMCC Failure - Home CUCM Unavailable/Inter-Cluster Failure (No Visiting SRST)The following figure illustrates EMCC failure when the home Cisco Unified Communications Manager isunavailable, an inter-cluster failure occurs, and no visiting SRST applies.




Figure 17: EMCC Failure - Configuration File Unavailable, Inter-Cluster Failure Occurs, and No Visiting SRST Applies

Phone Security with EMCCSee the Cisco Unified Communications Manager Security Guide for details of phone security issues in anEMCC environment.

System Requirements for EMCCThe 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 ExtensionMobility Cross Cluster configuration;for example, other Cisco Unified CommunicationsManager clusters, EMCC intercluster service profiles,and EMCC remote cluster services

Interactions and RestrictionsThis section provides the details of interactions and restrictions for Cisco Extension Mobility Cross Cluster.


Extension Mobility Cross ClusterPhone Security with EMCC

EMCC InteractionsThis section lists the interactions of the Cisco Extension Mobility Cross Cluster with other Cisco UnifiedCommunications Manager Administration components.

With the Cisco ExtensionMobility Cross Cluster cross-registration solution, user features function as expectedacross 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 and Security Mode for Different Cluster VersionsThis section lists the interactions of the Cisco Extension Mobility Cross Cluster with different versions andsecurity modes.

Phone configuration files can be encrypted only if both the home cluster and visiting cluster versions arein 9.x, and when the TFTP encryption configuration flag is enabled.

Note

During EMCC login, if both the visiting cluster and home cluster versions are in 9.x, the phone will behavein various modes as shown in the following table.


Extension Mobility Cross ClusterEMCC Interactions

Table 1: Supported Security Modes When Both Visiting Cluster and Home Cluster Are In 9.x Versions

EMCC StatusVisiting PhoneMode

Visiting ClusterMode

Visiting ClusterVersion

Home ClusterMode

HomeClusterVersion

Secure EMCCSecureMixed9.xMixed9.x

Non-secureEMCC

Non-secureMixed9.xMixed9.x

Non-secureEMCC

Non-secureNon-secure9.xMixed9.x

Login failsSecureMixed9.xNon-secure9.x

Non-secureEMCC

Non-secureNon-secure9.xNon-secure9.x

During EMCC login, if the visiting cluster version is 8.x and the home cluster version is 9.x, the phone willbehave in various modes as shown in the following table.

Table 2: Supported Security Modes When Visiting Cluster Is In 8.x and Home Cluster Is In 9.x Version




Home ClusterMode

HomeClusterVersion

Not supportedSecureMixed8.xMixed9.x

Non-secureEMCC


Non-secureEMCC


Not supportedSecureMixed8.xNon-secure9.x

Non-secureEMCC

Non-secureNon-secure8.xNon-secure9.x

During EMCC login, if the visiting cluster version is 9.x and the home cluster version is 8.x, the phone willbehave in various modes as shown in the following table.


Extension Mobility Cross ClusterEMCC and Security Mode for Different Cluster Versions

Table 3: Supported Security Modes When Visiting Cluster Is In 9.x and Home Cluster Is In 8.x Version




Home ClusterMode

HomeClusterVersion

Login failsSecureMixed9.xMixed8.x

Non-secureEMCC


Non-secureEMCC


Login failsSecureMixed9.xNon-secure8.x

Non-secureEMCC

SecureNon-secure9.xNon-secure8.x

EMCC RestrictionsThis section lists the restrictions and limitations of the Cisco Extension Mobility Cross Cluster with otherCisco Unified Communications Manager Administration components.

EMCC Logout LimitationsObserve the following EMCC logout limitations:

• If the home cluster administrator disables the EMCC capability of an end user while the end user islogged in with EMCC, the system does not automatically log this end user out. (In this scenario, theadministrator unchecks the Enable Extension Mobility Cross Cluster check box in the End UserConfiguration window for the end user.) Instead, the system only fails future EMCC attempts by thisend user. The current EMCC session continues until the end user logs out.

• In the visiting cluster, the current Phone Configuration window has a Log Out button for intraclusterEM. This button is also used by the visiting cluster administrator to logout an EMCC phone. Becausethe EMCC phone is not currently registered with the visiting Cisco Unified Communications Manager,this operation is equivalent to a DB cleanup in the visiting cluster. The EMCC phone will remainregistered with the home Cisco Unified Communications Manager until it comes back to the visitingcluster due to a reset or a logout from the home cluster by other means.

EMCC Does Not Support Intercom FeatureIntercom configuration specifies configuration to a static device, so Cisco Extension Mobility Cross Clusterdoes not support the Intercom feature.


Extension Mobility Cross ClusterEMCC Restrictions

EMCC Does Not Support Location-Based CACLocation CAC does not get supported.

RSVP-based CAC does get supported.

EMCC Limitations and Configuration Requirements with Local Route GroupsSee the following sections for details of EMCC limitations and configuration requirements in routing EMCCcalls with local route groups:

• EMCC Call Processing Configuration, on page 19

• Configure Visiting Cluster Emergency Pattern, on page 21

• Local Route Group of EMCC, on page 21

• Local Route Group Using EMCC SIP Trunk, on page 22

EMCC Device Cannot Be Provisioned in More Than One ClusterCisco Systems recommends that autoregistration be disabled (to avoid accidental provisioning).

EMCC and Security Mode Among ClustersAll clusters must specify the same security mode; either

• Clusters can be non-secure or mixed-mode clusters.

• Phones that allow Cisco Extension Mobility Cross Cluster can be in secure and non-secure mode.

Visiting Phone Login LimitationThe Cisco Extension Mobility service in participating clusters performs a periodic remote cluster update. TheEMCC 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 ascluster B) for this update, the Remote Cluster window for cluster A shows that Remote Activated service isset to false for cluster B.

In this case, the visiting cluster does not receive any response from the home cluster and sets the RemoteActivated 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 receivesthe 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 homecluster Cisco Unified Communications Manager from out-of-service to in-service.


Extension Mobility Cross ClusterEMCC Restrictions

Detection of status change of remote clusters is based on the value of the Remote Cluster Update IntervalEMCC feature parameter and on when the visiting Cisco Extension Mobility service performed the lastquery/update.

You can also click the Update Remote Cluster Now button on the Remote cluster Service Configurationwindow (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 visitingphones will return to normal.

EMCC and Product Specific Configuration Layout

Install and Activate EMCCAfter you install Cisco Unified Communications Manager, your network can support the Cisco ExtensionMobility Cross Cluster feature if you perform the necessary configuration tasks. For information onconfiguration tasks that you must perform, see the Configure EMCC, on page 1.

Configure EMCCThis section contains information about configuring EMCC.

Configure EMCC Feature ConfigurationThe following table provides detailed descriptions of the EMCC feature parameters that you configure in theEMCC Feature Configuration window (Advanced Features > EMCC > EMCC Feature Configuration).

Table 4: EMCC Feature Parameter Configuration Settings

DescriptionEMCC Parameter

Choose the computer name or IP address of the default TFTPserver that devices logging into EMCC from a remote clustershould use.

Default TFTP Server for EMCC LoginDevice

Choose the computer name or IP address of the backup TFTPserver that devices logging into EMCC from a remote clustershould use.

Backup TFTP Server for EMCC LoginDevice


Extension Mobility Cross ClusterInstall and Activate EMCC


Specify the number of minutes that elapse between checks ofthe system for expired EMCC devices.

An expired EMCC device specifies a device that logged in toEMCC from a remote cluster, but that, due to WAN failure ora connectivity issue, the phone logged out of the visiting clusterand, when connectivity was restored, logged back into thevisiting cluster.

During this maintenance job, the Cisco Extension Mobilityservice checks the Cisco Unified Communications Managerdatabase for any expired EMCC devices and automaticallylogs such devices out.

Default value specifies 1440 minutes. Valid values range from10 minutes to 1440 minutes.

Default Interval for Expired EMCC DeviceMaintenance

Choose whether you want all services on a new remote clusterto be automatically enabled when you add a new cluster.

Valid values specify True (enable all services on the remotecluster automatically) or False (manually enable the serviceson the remote cluster via the Remote Cluster Configurationwindow in Cisco Unified Communications ManagerAdministration). You may prefer to enable the servicesmanually so that you have time to configure the EMCC featurecompletely before enabling the remote services.

Default value specifies False.

Enable All Remote Cluster Services WhenAdding A New Remote Cluster

Choose the calling search space (CSS) that the PSTN AccessSIP trunk for processing EMCC calls uses.

The PSTN Access SIP trunk specifies the SIP trunk that hasbeen configured for PSTN access in the Intercluster ServiceProfile window in Cisco Unified Communications ManagerAdministration. Calls over this trunk are intended for and onlyget routed to the local PSTN that is co-located with the EMCClogged-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 emergencyservice calls)

• Use phone's original device CSS (PSTN calls get routedusing the configured calling search space on the remotephone; that is, the CSS that is used when the phone isnot logged into EMCC).

Default value specifies Use trunk CSS.

CSS for PSTN Access SIP Trunk


Extension Mobility Cross ClusterConfigure EMCC Feature Configuration


Choose the geolocation filter that you have configured for usewith the Cisco Extension Mobility Cross Cluster feature. Youmust previously configure the EMCC geolocation filters to beable to choose a value in this drop-down list box.

Based on the information in the geolocation that associateswith a phone that is logged in via extension mobility fromanother cluster as well as the selected EMCC geolocation filter,Cisco Unified CommunicationsManager places the phone intoa roaming device pool.

Cisco Unified Communications Manager determines whichroaming device pool to use by evaluating which device poolbest matches the phone geolocation information after theEMCC geolocation filter gets applied.

EMCC Geolocation Filter

This parameter specifies the maximum audio bit rate for allEMCC calls, regardless of the region associated with the otherparty.

Default value specifies 8 kbps (G.729).

Communicate your EMCC Region Max Audio BitRate to the other clusters with which your clusterinteracts. All participating EMCC clusters mustspecify the same EMCCRegionMaxAudio Bit Rate.

Note

EMCC Region Max Audio Bit Rate

This parameter specifies the maximum video call bit rate forall EMCC video calls, regardless of the maximum video callbit rate of the region associated with the other party.

Default value specifies 384. Valid values range from 0 to 8128.

Communicate your EMCC Region Max Video CallBit Rate to the other clusters with which your clusterinteracts. All participating EMCC clusters mustspecify the same EMCC Region Max Video Call BitRate.

Note

EMCC Region Max Video Call Bit Rate(Includes Audio)




This parameter specifies the link loss type between any EMCCphone and devices in any remote cluster.

Communicate your EMCC Region Link Loss Typeto the other clusters with which your cluster interacts.To allow two-way audio on EMCC calls, allparticipating EMCC clusters must use the sameEMCC Region Link Loss Type.

Note

Based on the option chosen, Cisco Unified CommunicationsManager attempts to use the optimal audio codec for the EMCCcall while observing the configured EMCCRegionMaxAudioBit 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, forexample, T1).

When this parameter is set to Lossy, Cisco UnifiedCommunications Manager chooses the optimal codec withinthe limit that is set by the EMCC Region Max Audio Bit Rate,based on audio quality, given the assumption that some packetloss will occur.

When this parameter is set to Low Loss, Cisco UnifiedCommunications Manager chooses the optimal codec withinthe limit that is set by the EMCC Region Max Audio Bit Rate,based on audio quality, given the assumption that little or nopacket loss will occur.

The only difference in the audio codec preference orderingbetween the Low Loss and Lossy options is that G.722 ispreferred over iSAC (Internet Speech Audio Codec) when theLink Loss Type is set as Low Loss, whereas iSAC is preferredover G.722 when the Link Loss Type is set as Lossy.

Default value specifies Low Loss.

EMCC Region Link Loss Type




Specify the number of seconds that Cisco UnifiedCommunicationsManager waits between sending or receivingKeepAlivemessages or acknowledgments between two clustersover EMCC RSVP SIP trunks.

An EMCCRSVP SIP trunk specifies a SIP trunk that has CiscoExtension Mobility Cross Cluster configured as the TrunkService Type and that has been selected as the SIP Trunk forRSVPAgent in the Intercluster Service Profile window.Whentwo of these intervals elapse without receipt of a KeepAlivemessage or an acknowledgment, Cisco UnifiedCommunications Manager releases the RSVP resources withthe remote cluster.

Default value specifies 15 seconds. Valid values range from1 second to 600 seconds.

RSVP SIP Trunk KeepAlive Timer

Choose the default server name or IP address of the primaryCisco Unified Communications Manager node in this localcluster that has the Cisco ExtensionMobility service activated.The remote cluster accesses this node to get information aboutthis local cluster.

Default Server For Remote Cluster Update

Choose the default server name or IP address of the secondaryCisco Unified Communications Manager node in this localcluster that has the Cisco ExtensionMobility service activated.The remote cluster accesses this node when the primary nodeis down to get information about this local cluster.

Backup Server for Remote Cluster Update

Specify an interval, in minutes, during which the CiscoExtension Mobility service on the local Cisco UnifiedCommunicationsManager node collects information about theremote EMCC cluster. Collected information includes suchdetails as the remote cluster Cisco Unified CommunicationsManager version and service information.

Default value specifies 30. Valid values range from 15minutesto 10,080 minutes.

Remote Cluster Update Interval

EMCC Intercluster Service Profile ConfigurationIn the Intercluster Service Profile Configuration window, you configure an EMCC intercluster service profile.In Cisco Unified CommunicationsManager Administration, use theAdvanced Features >EMCC >EMCCIntercluster Service Profile menu option to display this window.


Extension Mobility Cross ClusterEMCC Intercluster Service Profile Configuration

Table 5: EMCC Intercluster Service Profile Configuration Settings

DescriptionField

EMCC

Check this check box to activate the Cisco ExtensionMobility Cross Cluster feature.

Active

PSTN Access

Check this box to activate PSTN access.Active

From the drop-down list box, choose the SIP trunkto use for PSTN access.

You must first specify a SIP trunk (Device > Trunk)and configure it for PSTN access

SIP trunk

RSVP Agent

Click this box to activate RSVP Agent.Active

From the drop-down list box, choose the SIP trunkto use for RSVP Agent.

You must first specify a SIP trunk (Device >Trunk).

SIP trunk

EMCC Setup Validation Report

After you click Save, this pane displays the EMCCSetup Validation Report.

If you click Validate, a popup window, displays theEMCC Setup Validation Report. ClickClose to closethe popup window.

The Configuration(s) column of the report displaysthe following entities that get validated:

• EMCC PSTN Access Service

• Default TFTP Server for EMCC Login Device

• EMCC Geolocation Filter

• EMCC Service Default Server for RemoteCluster

• EMCC Devices

• ClusterId

Configuration(s)


Extension Mobility Cross ClusterEMCC Intercluster Service Profile Configuration

DescriptionField

This column displays the status of each configurationupon validation of the EMCC intercluster serviceprofile. For each entity, valid values include Successand Failure.

Status

For each failed configuration, an error messageexplains the configuration that must take place inorder to achieve success.

Error Message

Remote Cluster ConfigurationIn Cisco Unified Communications Manager Administration, use the Advanced Features > Cluster Viewmenu path to configure remote clusters.

Tips About Finding Remote Clusters

The Find operation locates only those remote clusters that you added previously. The Find operation does notlocate the clusters that belong to the enterprise automatically.

Using the GUI

For instructions on how to use the Cisco Unified Communications Manager Administration Graphical UserInterface (GUI) to find, delete, configure, or copy records, see the Cisco Unified Communications ManagerAdministration Guide and its subsections, which explain how to use the GUI and detail the functions of thebuttons and icons.

Configuration Settings Table

The following table provides detailed descriptions of the remote cluster configuration settings that you configurein the Remote Cluster Configuration window (Advanced Features > Cluster View).

Table 6: Remote Cluster Configuration Settings

DescriptionField

Remote Cluster Information

Enter the cluster ID of the remote cluster.

Valid values include alphanumeric characters, period (.), and hyphen(-).

Cluster Id

Enter a description for the remote cluster.

This field accepts up to 128 characters. You may use all charactersexcept quotes (“), close angle bracket (>), open angle bracket (<),backslash (\), dash (-), ampersand (&), and percent sign (%).

Description


Extension Mobility Cross ClusterRemote Cluster Configuration

DescriptionField

Enter the fully qualified name of the remote cluster.

This field accepts up to 50 characters and allows the followingcharacters: alphanumeric (a through z, A through Z, and 0 through 9),period (.), dash (-), asterisk (*), and space ( ).

Fully Qualified Name

Remote Cluster Service Information

For the EMCC service, the following column headings detail theconfiguration 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.

EMCC

For PSTN access, the following column headings detail the configurationfor this service:

• Enabled - If PSTN access is enabled, this box gets checked.

• Service - This entry specifies PSTN access.





PSTN Access

For the RSVP Agent, the following column headings detail theconfiguration for this service:

• Enabled - If RSVP Agent is enabled, this box gets checked.

• Service - This entry specifies RSVP Agent.





RSVP Agent



DescriptionField

For the TFTP service, the following column headings detail theconfiguration for this service:

• Enabled—If the TFTP service is enabled, this box gets checked.

• Service—This entry specifies the EMCC service.

• Remote Activated—Valid values specify true or false.

The value of the Remote Activated column is set to truewhenever remote IP addresses are configured eithermanually or dynamically.

Note

• Address 1—This column lists the first address for this service.

When you upgrade fromCisco Unified CommunicationsManager 8.6 (1) to Cisco Unified CommunicationsManager 8.6 (2) or later, Address 1 is automaticallyupdated by the system. However, if this field is blankafter the upgrade due to some reason such as DNS lookupfailure, you must manually update it with the appropriateIP address of the TFTP service.

Note

• Address 2—This column lists the second address for this service.

• Address 3—This column lists the third address for this service.

TFTP

This check box toggles remote cluster lookup for User Data Services(UDS) on the remote cluster.

• Enabled - If UDS is enabled, this box is checked.

• Service - This entry specifies UDS.





Consider the following example configuration:

• A three node cluster (A, B, C), with node A having entries for Band C in cluster view

• UDS is checked for B and unchecked for C.

•When you search for user B on node A using the HTTPS GETmethod, the search result is a user found on cluster B.

•When you search for user C on node A using the HTTPS GETmethod, the search result is a no user found on cluster B.

UDS

Click this button to enable all services.Enabled All Services



DescriptionField

Click this button to disable all services.Disabled All Services

Click this button to update the remote cluster immediately.Update Remote Cluster Now

Provide Information to UsersEnd users log in and out of Extension Mobility Cross Cluster feature just as they do from the ExtensionMobility feature, and they receive no indication of which cluster they are using.

Troubleshooting EMCCThis section provides information about error codes for EMApp and EMService.

For information on troubleshooting Cisco Extension Mobility Cross Cluster, refer to the Cisco UnifiedCommunications Manager Troubleshooting Guide.

Error Codes for EMAppThe following table lists and describes the error codes that apply to the Cisco Extension Mobility application(EMApp).

Table 7: Error Codes for the Cisco Extension Mobility Application (EMApp)

DescriptionQuick DescriptionPhone DisplayErrorCode

If the user is an EMCC user, this errorcan occur if “EMCC” is not activatedin the Inter-cluster Service Profilepage.

Authentication ErrorPlease try to login again(201)

201

User enters blank user ID or PIN.Blank userid or pinPlease try to login again(202)

202

EMApp sends this error to phonewhen IMS could not authenticate theuser with the given PIN.

Directory server errorLogin is unavailable (204)204

Occurs when the user profileinformation could not be retrievedeither from the cache or from thedatabase.

User Profile AbsentLogin is unavailable (205)

Logout is unavailable(205)

205


Extension Mobility Cross ClusterProvide Information to Users


Occurs when device or name tag ismissing in the request URI. Thiscannot happen with real devices andcan occur only if request is sent fromthird-party applications.

Device Name EmptyLogin is unavailable(207)


207

Visiting EMApp could not connectto any Visiting EMService. (Serviceis down or not activated.)

Visiting EMService could not connectto Home EMService (WAN is downor certificates are not trusted.)

EMService ConnectionError

Login is unavailable(208)


208

Some error (like database connectionfailure) occurred while initializingEMApp. The errormay occur becauseof failure in connecting to thedatabase during startup. Thisrepresents a catastrophic error.

Init Fail-Contact AdminLogin is unavailable(210)


210

Occurs when PSTN is not activatedin the Intercluster Service Profilewindow of the visiting cluster.

EMCC Not ActivatedLogin is unavailable(211)


211

Occurs when a remote cluster updated(keep-alive) fails by sending anincorrect cluster ID to remote cluster.

Cluster ID is invalidLogin is unavailable(212)212

Occurs when a device (phone load)does not have EMCC capability (forexample, for legacy phones or forTNP phones with older phone load).

Device does not supportEMCC

Login is unavailable(213)


213

Error Codes for EMServiceThe following table lists and describes the error codes that apply to the Cisco Extension Mobility service(EMService).


Extension Mobility Cross ClusterError Codes for EMService

Table 8: Error Codes for the Cisco Extension Mobility Service (EMService)


EMService failed in some totallyunexpected scenario. It is catastrophic.

Unknown ErrorLogin is unavailable(0)

Logout isunavailable(0)

0

When EMService could not parse theXML request from EMApp/EMService.This happens when 3rd partyapplications sends an incorrectquery/login XML (EM API) or it canoccur because of mis-match in versionbetween home and visiting CUCMversions (for EMCC).

Error on parsingLogin is unavailable(1)


1

EMCC user credentials could not beauthenticated as the user has enteredwrong pin.

EMCCAuthentication ErrorLogin is unavailable(2)2

Invalid application user. This can be seencommonly when using EM API.

Invalid App UserLogin is unavailable(3)


3

EM Service sends this error when itcould not validate the login/logoutrequest due to some unknown reason(Error while querying the database orerror while retrieving info from cache).

Policy Validation errorLogin is unavailable(4)


4

EM / EMCC Login is requested for adevice which has “Enable extensionmobility” unchecked in phoneconfiguration page.

Dev. logon disabledLogin is unavailable(5)


5

Whenever database throws an exceptionwhile executing the query or storedprocedure requested by EM Service(login/logout or device/user query), EMService sends this error code to EMApp.

Database ErrorLogin is unavailable(6)


6

No Valid query has been sent to theEMService (DeviceUserQuery &UserDeviceQuery are valid ones). Thisis ideally seen when using EMAPI withincorrect XML input.

Query type undeterminedLogin is unavailable(8)


8




This error is displayed in two cases:

1 IMS throws an exception when ittries to authenticate a particular user.

2 When information about a particularuser could not be retrieved eitherfrom cache or database.

Dir. User Info ErrorLogin is unavailable(9)


9

User tries to do login/query on behalf ofsome other user (By default, onlyCCMSysUser has the admin rights.)

User lacks app proxy rightsLogin isunavailable(10)


10

Phone record entry is absent in thedevice table.

Device Does not existLogin isunavailable(11)


11

No Device profile is associated with theremote user (EMCC Login)

Dev. Profile not foundPhone record entry isabsent in the devicetable

12

Another user is already logged in on thatparticular phone

Another user logged inLogin isunavailable(18)

18

Trying to logout a user which has notlogged in. This can ideally happen whensending logout requests from the 3rdparty applications (EM API).

No user logged inLogout isunavailable(19)

19

“Enable extensionmobility” is uncheckedin phone configuration page.

Hoteling flag errorLogin isunavailable(20)


20

Current user status could not be retrievedfrom either local cache or database(when PolicyValidator tried to checkcurrent login User or login time).

Hoteling Status errorLogin isunavailable(21)


21

Occurs when EM is not enabled ondevice and the request is sent via EMAPI or when the services button ispressed on phone.

Dev. logon disabledLogin isunavailable(22)

22




Occurs when the given user ID is notfound (in any of the remote clusters).

User does not existLogin is Unavailable(23)

Logout is Unavailable(23)

23

User has currently logged in on someother phone

User logged in elsewhereLogin isunavailable(25)

25

When EMService has currently reachedthe threshold level of “MaximumConcurrent Requests” service parameter

Busy, please try againLogin isunavailable(26)


26

When “Validate IP Address” serviceparameter is set to true and user tries tologin/logout from a machine whose IPaddress is not trusted (for example, 3rdparty app / EM API from a machinewhich is not listed in Trusted List of Ipsservice parameter).

Untrusted IP ErrorLogin isunavailable(28)


28

RISDC Cache has not been created andinitialized and EMService is unable toconnect to RISDC

ris down-contact adminLogin isunavailable(29)


29

When login/logout comes through proxy(“Via” is set in HTTP header) and “AllowProxy” service parameter is set to “false.”

Proxy not allowedLogin isunavailable(30)


30

Occurs when Enable ExtensionMobilityCross Cluster check box is not checkedin the End User window of the homecluster.

EMCCNotActivated for theuser

Login isunavailable(31)


31

Occurs when a device model does nothave EMCC capability (for example,legacy phones)

Device does not supportEMCC



32

Occurs when all the EMCC dummydevices are in use by other EMCClogins.

No free EMCC dummydevice



33




Occurs when the home cluster does nothave an entry for this visiting cluster.

Visiting Cluster Informationis not present in HomeCluster



35

Occurs when the administrator has notadded any remote cluster.

No Remote ClusterLogin isunavailable(36)


36

Occurs when the same device nameexists in both home cluster and visitingcluster.

Duplicate Device NameLogin is Unavailable(37)

Logout is Unavailable(37)

37

Occurs when home cluster does not wantto allow EMCC login (Enable ExtensionMobility Cross Cluster check box is notchecked in the home cluster).

EMCC Not AllowedLogin isunavailable(38)


38

Occurs when the remote cluster ID is notvalid (happens during remote clusterupdate)

Invalid ClusterIDLogin isunavailable(42)


42

Device Security Profile associated to theEMCC device should be Non Secure forits Device Security Mode.

This error code does not applyfor Cisco UnifiedCommunications ManagerRelease 9.x and above.

Note

Device Security mode errorLogin isunavailable(43)

43

Occurs during EMCC login when thevisiting cluster version is 9.x and is inmixed mode, the phone is in securemode, and the home cluster version is8.x.

Remote Cluster version notsupported

Login isunsuccessful(45)

45

Occurs during EMCC login when thevisiting cluster security mode is in mixedmode, the phone is in secure mode, andthe home cluster is in non-secure mode.

Remote Cluster securitymode not supported

Login isunsuccessful(46)

46



extension mobility cross cluster - cisco · extension mobility cross cluster...

Documents