Cisco Unified Communications Manager Features and Services Guide, Release 9.1(1)
Extension Mobility Cross cluster
Download this chapter
Extension Mobility Cross clusterExtension Mobility Cross cluster
Download the complete book
Cisco Unified Communications Manager Features and Services Guide, Release 9.1(1)Cisco Unified Communications Manager Features and Services Guide, Release 9.1(1) (PDF - 22 MB)
 Feedback

Contents

Extension Mobility Cross cluster

This chapter provides information about Cisco Extension Mobility Cross Cluster feature which 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 Extension Mobility chapter for a description and configuration details of the Cisco Extension Mobility feature.

Configure EMCC

Perform the following steps to configure Cisco Extension Mobility Cross Cluster in your network. Use the following procedure in conjunction with the Extension Mobility Cross cluster.

Procedure
    Step 1   In Cisco Unified Serviceability, choose Tools > Service Activation.
    Step 2   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)
    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:
    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.
    Step 5   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: 7975 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.
    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.
    Step 6   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 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.
    Step 7   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.

    Step 8   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.
    Step 9   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, TFTP, or Capf certificate(s) gets regenerated on any of its nodes.

    Step 10   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.

    Step 11   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.

    Step 12   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 and check the Override Common Settings checkbox. (Although this setting may be enabled by default per cluster, it may be necessary to check the Override Common Settings checkbox and save the change)

    Step 13   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.
    Step 14   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.
    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.
    Step 15   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 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:
    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.

    Step 17   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.

    Step 18   Configure one or two intercluster SIP trunks for EMCC.
    Note   

    You may configure one trunk for both PSTN Access and RSVP Agent services 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.
    Step 19   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.
    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.
      Note   

      If you configured only one trunk, 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.
    Step 20   Configure EMCC remote cluster services:
    1. In Cisco Unified Communications Manager Administration, choose Advance Features > Cluster View.
    2. Click Find to display a list of known remote clusters.
    3. If the remote cluster that you want configure appears, click on the remote cluster and verify the settings.
    4. If the remote cluster that you want to configure does not appear, click Add New and 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.
        Note   

        During EMCC, TFTP check box should always be disabled.

    Step 21   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.

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

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

    Related Tasks
    Related References
    Related Information

    EMCC feature

    This section contains information about the EMCC feature and configuration, supported phones, login instructions and summaries, call processing, and phone security.

    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.

    Cisco Extension Mobility Cross Cluster Interactions

    See the EMCC interactions for a list of the interactions between the Cisco Extension Mobility Cross 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
    • 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).

    EMCC login

    This section provides information about EMCC login.

    EMCC login terminology

    The following figure illustrates the visiting cluster versus a home cluster in Cisco Extension Mobility Cross Cluster.

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

    The following figure illustrates Cisco Extension Mobility Cross Cluster login when extension mobility finds the home cluster.

    Figure 2. EMCC Login - Extension Mobility Finds Home Cluster

    The following figure illustrates Cisco Extension Mobility Cross Cluster login when extension mobility authenticates, 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 Extension Mobility Cross Cluster login when extension mobility modifies the 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 home cluster after login.

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

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

    Determine 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 Cisco Extension Mobility 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 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, see the Cisco Unified Reporting Administration Guide.

    EMCC configuration

    See topics related to configuring EMCC 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.

    Related Information

    View 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:

    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 Communications Manager Administration Guide.
      Step 3   In any cluster, the administrator can view a list of the cluster devices that have been 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 Cisco Unified Communications Manager Administration Guide.

      EMCC call processing

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

      EMCC call processing overview

      The following figure provides an overview of EMCC call processing.

      Figure 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

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

      Match the Roaming Device Pool

      The 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 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

      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
      • Device Security Mode

      EMCC call processing

      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.

      Configure visiting cluster emergency pattern

      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 of EMCC

      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 using EMCC SIP trunk

      The 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 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 EMCC solution 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

      The following figure illustrates Cisco Extension Mobility Cross Cluster for an RSVP Agent-based Call Admission Control (CAC) basic call.

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

      RSVP agent CAC hold/resume by home phone

      The following figure illustrates Cisco Extension Mobility Cross Cluster for an RSVP Agent-based Hold/Resume call 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 phone

      The following figure illustrates Cisco Extension Mobility Cross Cluster for an RSVP Agent-based Hold/Resume call by the visiting phone.

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

      EMCC 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).

      Help for EMCC call processing issues

      Take 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:
        1. 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 provides information about phone behaviors in an EMCC environment, such as during a WAN network failure.

        WAN network failure

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

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

        The following figure illustrates EMCC failure when registration rejection occurs.

        The phone reregisters with the visiting cluster.

        Figure 14. EMCC Failure - Registration Rejection

        EMCC failure-home CUCM unavailable/interoffice failure

        The following figure illustrates EMCC failure when the home Cisco Unified Communications Manager is unavailable 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 failure

        The following figure 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 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 is unavailable, an inter-cluster failure occurs, and no visiting SRST applies.

        The phone reregisters with the visiting cluster.

        Figure 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 clusters, EMCC intercluster service profiles, and EMCC remote cluster services

        Interactions and restrictions

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

        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 and security mode for different cluster versions

        This section lists the interactions of the Cisco Extension Mobility Cross Cluster with different versions and security modes.


        Note

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

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

        Table 1 Supported security modes when both visiting cluster and home cluster are in 9.x versions

        Home Cluster Version

        Home Cluster Mode

        Visiting Cluster Version

        Visiting Cluster Mode

        Visiting Phone Mode

        EMCC Status

        9.x

        Mixed

        9.x

        Mixed

        Secure

        Secure EMCC

        9.x

        Mixed

        9.x

        Mixed

        Non-secure

        Non-secure EMCC

        9.x

        Mixed

        9.x

        Non-secure

        Non-secure

        Non-secure EMCC

        9.x

        Non-secure

        9.x

        Mixed

        Secure

        Login fails

        9.x

        Non-secure

        9.x

        Non-secure

        Non-secure

        Non-secure EMCC

        During EMCC login, if the visiting cluster version is 8.x and the home cluster version is 9.x, the phone will behave 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 Cluster Version

        Home Cluster Mode

        Visiting Cluster Version

        Visiting Cluster Mode

        Visiting Phone Mode

        EMCC Status

        9.x

        Mixed

        8.x

        Mixed

        Secure

        Not supported

        9.x

        Mixed

        8.x

        Mixed

        Non-secure

        Non-secure EMCC

        9.x

        Mixed

        8.x

        Non-secure

        Non-secure

        Non-secure EMCC

        9.x

        Non-secure

        8.x

        Mixed

        Secure

        Not supported

        9.x

        Non-secure

        8.x

        Non-secure

        Non-secure

        Non-secure EMCC

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

        Table 3 Supported security modes when visiting cluster is in 9.x and home cluster is in 8.x version

        Home Cluster Version

        Home Cluster Mode

        Visiting Cluster Version

        Visiting Cluster Mode

        Visiting Phone Mode

        EMCC Status

        8.x

        Mixed

        9.x

        Mixed

        Secure

        Login fails

        8.x

        Mixed

        9.x

        Mixed

        Non-secure

        Non-secure EMCC

        8.x

        Mixed

        9.x

        Non-secure

        Non-secure

        Non-secure EMCC

        8.x

        Non-secure

        9.x

        Mixed

        Secure

        Login fails

        8.x

        Non-secure

        9.x

        Non-secure

        Secure

        Non-secure EMCC

        EMCC restrictions

        This section lists the restrictions and limitations of the Cisco Extension Mobility Cross Cluster with other Cisco Unified Communications Manager Administration components.

        EMCC logout limitations

        Observe the following EMCC logout limitations:
        • 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.
        • In the visiting cluster, the current Phone Configuration window has a Log Out button for intracluster EM. This button is also used by the visiting cluster administrator to logout an EMCC phone. Because the 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 remain registered with the home Cisco Unified Communications Manager until it comes back to the visiting cluster due to a reset or a logout from the home cluster by other means.

        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 CAC

        Location CAC does not get supported.

        RSVP-based CAC does get supported.

        EMCC limitations and configuration requirements with local route groups

        See the following sections for details of EMCC limitations and configuration requirements in routing EMCC calls with local route groups:

        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

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

        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

        Install and activate EMCC

        After you install Cisco Unified Communications Manager, 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 Configure EMCC.

        Configure EMCC

        This section contains information about configuring EMCC.

        Configure EMCC feature configuration

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

        Table 4 EMCC Feature Parameter 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

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

        Remote cluster configuration

        In Cisco Unified Communications Manager Administration, use the Advanced Features > Cluster View menu 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 not locate the clusters that belong to the enterprise automatically.

        Using the GUI

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

        Configuration Settings Table

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

        Table 6 Remote Cluster Configuration Settings

        Field

        Description

        Remote Cluster Information

        Cluster Id

        Enter the cluster ID of the remote cluster.

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

        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.

        TFTP

        For the TFTP service, the following column headings detail the configuration 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.
          Note   

          The value of the Remote Activated column is set to true whenever remote IP addresses are configured either manually or dynamically.

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

          When you upgrade from Cisco Unified Communications Manager 8.6 (1) to Cisco Unified Communications Manager 8.6 (2) or later, Address 1 is automatically updated by the system. However, if this field is blank after the upgrade due to some reason such as DNS lookup failure, you must manually update it with the appropriate IP address of the TFTP 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.

        Provide information to users

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

        Troubleshooting EMCC

        This section provides information about error codes for EMApp and EMService.

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

        Error codes for EMApp

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

        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)

        Blank 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 EMService

        The following table lists and describes the error codes that apply to the Cisco Extension Mobility service (EMService).

        Table 8 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 Extension Mobility Cross Cluster 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 Extension Mobility Cross Cluster 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.

        Note   

        This error code does not apply for Cisco Unified Communications Manager Release 9.x and above.

        45

        Login is unsuccessful(45)

        Remote Cluster version not supported

        Occurs during EMCC login when the visiting cluster version is 9.x and is in mixed mode, the phone is in secure mode, and the home cluster version is 8.x.

        46

        Login is unsuccessful(46)

        Remote Cluster security mode not supported

        Occurs during EMCC login when the visiting cluster security mode is in mixed mode, the phone is in secure mode, and the home cluster is in non-secure mode.