The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The extension mobility cross cluster (EMCC) feature provides users with the same functionality as extension mobility, but also allows them to move from one cluster (the home cluster) and log in to a temporary phone on another remote cluster (the visiting cluster). From there, they can access their phone settings from any location as if they were using an IP Phone at the home office.
Other call-control entities that support and use the extension mobility cross cluster (EMCC) configuration; for example, other Cisco Unified Communications Manager clusters, EMCC intercluster service profiles, and EMCC remote cluster services
Clusters that are set to nonsecure or mixed mode. See Extension Mobility Cross Cluster and Security Mode for Different Cluster Versions for more information.
Supported phones in secure or nonsecure mode
Review Extension Mobility Cross Cluster Interaction and Restriction
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
Generate a report to identify devices that support the extension mobility cross cluster feature. |
|
|
Step 2 |
To Configure Extension Mobility, perform the following subtasks: |
Configure extension mobility to allow users to temporarily access their phone settings, such as line appearances, services, and speed dials, from other phones in one cluster. Perform this task flow on both home and remote clusters, so that users will be able to access settings from either a home or visiting cluster. |
|
Step 3 |
To Configure Certificates for Extension Mobility Cross Cluster, perform the following subtasks: |
To configure the home and remote clusters properly, you must export certificates on each cluster to the same SFTP server and SFTP directory and consolidate them on one of the participating clusters. This procedure ensures that trust is established between the two clusters. |
|
Step 4 |
To Configure Extension Mobility Cross Cluster Devices and Templates, perform the following subtasks: |
|
|
Step 5 |
Configure a Geolocation Filter for Extension Mobility Cross Cluster |
Configure a geolocation filter to specify criteria for device location matching, such as country, state, and city values. Geolocations are used to identify the location of a device, and the filter indicates what parts of the geolocation are significant. |
|
Step 6 |
Configure Feature Parameters for Extension Mobility Cross Cluster |
Select values for the feature parameters that you configured, such as the geolocation filter. |
|
Step 7 |
Configure Intercluster SIP Trunk for Extension Mobility Cross Cluster |
Configure trunks to process inbound or outbound traffic for intercluster PSTN access and RSVP agent services. You can configure one trunk for both PSTN access and RSVP agent services or one trunk for each service. You do not need more than two SIP trunks for extension mobility cross cluster. |
|
Step 8 |
Configure an Intercluster Service Profile for Extension Mobility Cross Cluster |
Configure the intercluster service profile to activate extension mobility cross cluster. The profile collects all the configuration that precedes and provides a results report. |
|
Step 9 |
Configure the remote cluster for extension mobility cross cluster. This step completes the link between the home cluster with remote (visiting) cluster. |
Configure extension mobility to allow users to temporarily access their phone settings, such as line appearances, services, and speed dials, from other phones in one cluster. Perform this task flow on both home and remote clusters, so that users will be able to access settings from either a home or visiting cluster.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
||
|
Step 2 |
Create the Extension Mobility phone service to which you can subscribe your users. |
|
|
Step 3 |
Configure a Device Profile for Extension Mobility Cross Cluster |
Create a device profile to map settings onto a real device when a user logs in to Extension Mobility cross cluster. |
|
Step 4 |
||
|
Step 5 |
Enable Extension Mobility on devices and subscribe to the service if you have not set up an enterprise subscription for all devices. |
|
Step 1 |
From Cisco Unified Serviceability, choose . |
|
Step 2 |
From the Server drop-down list, choose the requried node. |
|
Step 3 |
Activate the following services: |
|
Step 4 |
Click Save. |
|
Step 5 |
Click OK. |
Create the Extension Mobility phone service to which you can subscribe your users.
|
Step 1 |
From Cisco Unified CM Administration, choose . |
||
|
Step 2 |
Click Add New. |
||
|
Step 3 |
In the Service Name field, enter a name for the service. For example, enter a name such as Extension Mobility or EM. For Java MIDlet services, the service name must exactly match the name that is defined in the Java Application Descriptor (JAD) file. |
||
|
Step 4 |
In the Service URL field, enter the service URL in the following format: http://<IP Address>:8080/emapp/EMAppServlet?device=#DEVICENAME#&EMCC=#EMCC#. |
||
|
Step 5 |
(Optional) If you want to create a secure URL using HTTPS, enter the secure service URL in the following format: https://<IP Address>:8443/emapp/EMAppServlet?device=#DEVICENAME#&EMCC=#EMCC# |
||
|
Step 6 |
(Optional) If you want to configure more sign-in options, append the
The |
||
|
Step 7 |
Use the default values for the Service Category and Service Type fields. |
||
|
Step 8 |
Check the Enable check box. |
||
|
Step 9 |
(Optional) Check the Enterprise Subscription check box to subscribe all phones and device profiles to this phone service.
|
||
|
Step 10 |
Click Save. |
Create a device profile to map settings onto a real device when a user logs in to Extension Mobility cross cluster.
|
Step 1 |
From Cisco Unified CM Administration, choose . |
|
Step 2 |
Perform one of the following tasks:
|
|
Step 3 |
Configure the fields on the Device Profile Configuration window. See Device Profile Fields for Extension Mobility Cross Cluster for more information about the fields and their configuration options. |
|
Step 4 |
Click Save. |
|
Step 5 |
Add a directory number (DN) to the new device profile. |
|
Field |
Description |
||
|---|---|---|---|
|
Product Type |
Displays the product type to which this device profile applies. |
||
|
Device Protocol |
Displays the device protocol to which this device profile applies. |
||
|
Device Profile Name |
Enter a unique name. This name can comprise up to 50 characters in length. |
||
|
Description |
Enter a description of the device profile. For text, use anything that describes this particular user device profile. |
||
|
User Hold MOH Audio Source |
Specifies the audio source that plays when a user initiates a hold action, choose an audio source from the User Hold MOH Audio Source drop-down list. If you do not choose an audio source, Unified Communications Manager uses the audio source that is defined in the device pool or the system default if the device pool does not specify an audio source ID.
|
||
|
User Locale |
From the drop-down list, choose the locale that is associated with the phone user interface. The user locale identifies a set of detailed information, including language and font, to support users. Unified Communications Manager makes this field available only for phone models that support localization.
|
||
|
Phone Button Template |
From the Phone Button Template drop-down list, choose a phone button template.
|
||
|
Softkey Template |
From the Softkey Template drop-down list, choose the softkey template from the list that displays. |
||
|
Privacy |
From the Privacy drop-down list, choose On for each phone on which you want privacy. For more information, see the Feature Configuration Guide for Cisco Unified Communications Manager. |
||
|
Single Button Barge |
From the drop-down list, choose from the following options:
For more information, see the Feature Configuration Guide for Cisco Unified Communications Manager. |
||
|
Join Across Lines |
From the drop-down list, choose from the following options:
For more information, see the System Configuration Guide for Cisco Unified Communications Manager. |
||
|
Always Use Prime Line |
From the drop-down list, choose one of the following options:
|
||
|
Always Use Prime Line for Voice Message |
From the drop-down list, choose one of the following options:
|
||
|
Ignore Presentation Indicators (internal calls only) |
To configure call display restrictions and ignore any presentation restriction that is received for internal calls, check the "Ignore Presentation Indicators (internal calls only)" check box.
|
||
|
Do Not Disturb |
Check this check box to enable Do Not Disturb. |
||
|
DND Option |
When you enable DND on the phone, this parameter allows you to specify how the DND feature handles incoming calls:
|
||
|
DND Incoming Call Alert |
When you enable the DND Ringer Off or Call Reject option, this parameter specifies how a call displays on a phone. From the drop-down list, choose one of the following options:
|
||
|
Extension Mobility Cross Cluster CSS |
From the drop-down list, choose an existing Calling Search Space (CSS) to use for this device profile for the Extension Mobility Cross Cluster feature. (To configure a new CSS or modify an existing CSS, choose in Unified Communications Manager.) Default value specifies None. The home administrator specifies this CSS, which gets used as the device CSS that gets assigned to the phone when the user logs in to this remote phone. For more information, see the Feature Configuration Guide for Cisco Unified Communications Manager. |
||
|
Module 1 |
You can configure one or two expansion modules for this device profile by choosing phone templates from the expansion module drop-down list in the expansion module fields.
Choose the appropriate expansion module or None. |
||
|
Module 2 |
Choose the appropriate expansion module or None. |
||
|
MLPP Domain |
If this user device profile will be used for MLPP precedence calls, choose the MLLP Domain from the drop-down list.
|
||
|
MLPP Indication |
If this user device profile will be used for MLPP precedence calls, assign an MLPP Indication setting to the device profile. This setting specifies whether a device that can play precedence tones will use the capability when it places an MLPP precedence call. From the drop-down list, choose a setting to assign to this device profile from the following options:
|
||
|
MLPP Preemption |
If this user device profile will be used for MLPP precedence calls, assign an MLPP Preemption setting to the device profile. This setting specifies whether a device that can preempt calls in progress will use the capability when it places an MLPP precedence call. From the drop-down list, choose a setting to assign to this device profile from the following options:
|
||
|
Login User Id |
From the Login User ID drop-down list, choose a valid login user ID.
|
|
Step 1 |
From Cisco Unified CM Administration, choose . |
|
Step 2 |
Perform one of the following tasks:
|
|
Step 3 |
In the Extension Mobility pane, check the Enable Extension Mobility Cross Cluster check box. |
|
Step 4 |
Choose the device profile from the Available Profiles list pane in the Extension Mobility pane. |
|
Step 5 |
Move the device profile to the Controlled Profiles list pane. |
|
Step 6 |
Click Save. |
Enable Extension Mobility on devices and subscribe to the service if you have not set up an enterprise subscription for all devices.
|
Step 1 |
From From Cisco Unified CM Administration, choose . |
|
Step 2 |
Find the phone on which users can use Extension Mobility Cross Cluster. |
|
Step 3 |
For this device, check the Enable Extension Mobility check box in the Extension Information pane. |
|
Step 4 |
In the Phone Configuration window, choose the Subscribe/Unsubscribe Services option in the Related Links drop-down list. |
|
Step 5 |
Click Go. |
|
Step 6 |
In the popup window that opens, choose the Extension Mobility service in the Select a Service drop-down list. |
|
Step 7 |
Click Next. |
|
Step 8 |
Click Subscribe. |
|
Step 9 |
From the popup window, click Save, and then close the window. |
|
Step 10 |
In the Phone Configuration window, click Save. |
|
Step 11 |
Click OK if prompted. |
To configure the home and remote clusters properly, you must export certificates on each cluster to the same SFTP server and SFTP directory and consolidate them on one of the participating clusters. This procedure ensures that trust is established between the two clusters.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
||
|
Step 2 |
Configure Bulk Certificate Management and Export Certificates |
Configure bulk certificate management in Cisco Unified OS Administration to export the certificates from both the home and remote clusters. |
|
Step 3 |
Consolidate certificates when all participating clusters have exported their certificates. This option is available only if two or more clusters exported their certificates to the SFTP server. |
|
|
Step 4 |
Import the certificates back into the home and remote (visiting) clusters. |
|
Step 1 |
From Cisco Unified Serviceability, choose . |
|
Step 2 |
From the Server drop-down list, choose the publisher node. |
|
Step 3 |
Check the Cisco Bulk Provisioning Service check box. |
|
Step 4 |
Click Save. |
|
Step 5 |
Click OK. |
Configure bulk certificate management in Cisco Unified OS Administration to export the certificates from both the home and remote clusters.
This procedure exports the certificates to an SFTP server.
 Note |
|
|
Step 1 |
From Cisco Unified OS Administration, choose . |
||
|
Step 2 |
Configure the settings for a TFTP server that both the home and remote clusters can reach. See the online help for information about the fields and their configuration options. |
||
|
Step 3 |
Click Save. |
||
|
Step 4 |
Click Export. |
||
|
Step 5 |
In the Bulk Certificate Export window, choose All for the Certificate Type field. |
||
|
Step 6 |
Click Export. |
||
|
Step 7 |
Click Close.
|
Consolidate certificates when all participating clusters have exported their certificates. This option is available only if two or more clusters exported their certificates to the SFTP server.
This procedure consolidates all PKCS12 files in the SFTP server to form a single file.
Note |
If you export new certificates after consolidation, you must perform this procedure again to include the newly exported certificates. |
|
Step 1 |
From From Cisco Unified OS Administration, choose . |
||
|
Step 2 |
In the Certificate Type field, choose All. |
||
|
Step 3 |
Click Consolidate.
|
Import the certificates back into the home and remote (visiting) clusters.
Note |
After an upgrade, these certificates are preserved. You do not need to reimport or reconsolidate certificates. |
Note |
Ensure that you retain all the files that are created to ensure smooth consolidation between different Unified Communications Manager versions. |
 Caution |
After you import the certificates, the phones on the cluster will automatically restart. |
|
Step 1 |
From From Cisco Unified OS Administration, choose . |
||||
|
Step 2 |
From the Certificate Type drop-down list, choose All. |
||||
|
Step 3 |
Choose Import.
|
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
Configure a common device configuration to specify the services or features that will be associated with a particular user. |
|
|
Step 2 |
Create an extension mobility cross cluster template to link the common device configuration with this feature. |
|
|
Step 3 |
Set the extension mobility cross cluster template that you created as the default template. |
|
|
Step 4 |
Insert extension mobility cross cluster device entries into your system database. Each device is identified with a unique name in the format EMCC1, EMCC2, and so on. The Bulk Administration Tool assigns device numbers by obtaining the last one used. |
Configure a common device configuration to specify the services or features that will be associated with a particular user.
|
Step 1 |
From Cisco Unified CM Administration, choose . |
|
Step 2 |
Perform one of the following tasks:
|
|
Step 3 |
Configure the fields on the Common Device Configuration window. For more information on the fields and their configuration options, see Online Help. |
|
Step 4 |
Click Save. |
Create an extension mobility cross cluster template to link the common device configuration with this feature.
|
Step 1 |
From Cisco Unified CM Administration, choose . |
|
Step 2 |
Click Add New. |
|
Step 3 |
Configure the fields on the EMCC Template Configuration window. For more information on the fields and their configuration options, see Online Help. |
|
Step 4 |
Click Save. |
Set the extension mobility cross cluster template that you created as the default template.
|
Step 1 |
From Cisco Unified CM Administration, choose . |
|
Step 2 |
Click Update EMCC Devices. |
|
Step 3 |
From the Default EMCC Template drop-down list, choose the extension mobility cross cluster device template that you configured. |
|
Step 4 |
Click Run Immediately. |
|
Step 5 |
Click Submit. |
|
Step 6 |
Verify the success of the job:
|
Insert extension mobility cross cluster device entries into your system database. Each device is identified with a unique name in the format EMCC1, EMCC2, and so on. The Bulk Administration Tool assigns device numbers by obtaining the last one used.
|
Step 1 |
From From Cisco Unified CM Administration, choose . |
|
Step 2 |
Click Insert EMCC Devices. |
|
Step 3 |
Enter the number of devices you are adding in the Number of EMCC Devices to be added field. |
|
Step 4 |
Click Run Immediately and click Submit. |
|
Step 5 |
Refresh the window and verify that the Number of EMCC Devices already in database value shows the number of devices that you added. |
Configure a geolocation filter to specify criteria for device location matching, such as country, state, and city values. Geolocations are used to identify the location of a device, and the filter indicates what parts of the geolocation are significant.
|
Step 1 |
From Cisco Unified CM Administration, choose . |
|
Step 2 |
Click Add New. |
|
Step 3 |
Configure the fields on the Geolocation Filter Configuration window. For more information on the fields and their configuration options, see Online Help. |
|
Step 4 |
Click Save. |
Select values for the feature parameters that you configured, such as the geolocation filter.
|
Step 1 |
From Cisco Unified CM Administration, choose . |
|
Step 2 |
Configure the fields on the EMCC Feature Configuration window. See Feature Parameter Fields for Extension Mobility Cross Cluster for more information about the fields and their configuration options. |
|
Step 3 |
Click Save. |
|
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 extension mobility cross cluster (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 system checks for expired EMCC devices. An expired EMCC device is a device that logged in to EMCC from a remote cluster, but that, because of a WAN failure or a connectivity issue, the phone logged out of the visiting cluster. When connectivity was restored, the device logged back into the visiting cluster. During this maintenance job, the Cisco Extension Mobility service checks the Unified Communications Manager database for any expired EMCC devices and automatically logs them out. The default value is 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 are 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 Unified Communications Manager). You can enable the services manually so that you have time to configure the EMCC feature completely before enabling the remote services. The default value is 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 is the SIP trunk that you configured for PSTN access in the Intercluster Service Profile window. Calls over this trunk are intended for and are routed to only the local PSTN that is co-located with the EMCC logged-in phone that initiates the call. Valid values are the following:
The default value is Use trunk CSS. |
||
|
EMCC Geolocation Filter |
Choose the geolocation filter that you have configured for use EMCC. Based on the information in the geolocation that associates with a phone that is logged in through 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 is 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. The default value is 8 kbps (G.729).
|
||
|
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. The default value is 384. Valid values range from 0 to 8128.
|
||
|
EMCC Region Link Loss Type |
This parameter specifies the link loss type between any EMCC phone and devices in any remote cluster.
Based on the option that you choose, 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 are the following:
When you set this parameter 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. 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. 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 Internet Speech Audio Codec (iSAC) 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. The default value is Low Loss. |
||
|
RSVP SIP Trunk KeepAlive Timer |
Specify the number of seconds that 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 is 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, Unified Communications Manager releases the RSVP resources with the remote cluster. The default value is 15 seconds. Valid values range from 1second to 600 seconds. |
||
|
Default Server For Remote Cluster Update |
Choose the default server name or IP address of the primary node in this local cluster that has the Cisco Extension Mobility service activated. The remote cluster accesses this node to get information about this local cluster. |
||
|
Backup Server for Remote Cluster Update |
Choose the default server name or IP address of the secondary node in this local cluster that has the Cisco Extension Mobility service activated. The remote cluster accesses this node when the primary node is down to retrieve information about this local cluster. |
||
|
Remote Cluster Update Interval |
Specify an interval, in minutes, during which the Cisco Extension Mobility service on the local node collects information about the remote EMCC cluster. Collected information includes such details as the remote cluster Unified Communications Manager version and service information. The default value is 30. Valid values range from 15 minutes to 10,080 minutes. |
Configure trunks to process inbound or outbound traffic for intercluster PSTN access and RSVP agent services. You can configure one trunk for both PSTN access and RSVP agent services or one trunk for each service. You do not need more than two SIP trunks for extension mobility cross cluster.
|
Step 1 |
From Cisco Unified CM Administration, choose . |
|
Step 2 |
Click Add New. |
|
Step 3 |
From the Trunk Type drop-down list, choose SIP Trunk. |
|
Step 4 |
From the Trunk Service Type drop-down list, choose Extension Mobility Cross Clusters. |
|
Step 5 |
Click Next. |
|
Step 6 |
Configure the fields in the Trunk Configuration window. For more information on the fields and their configuration options, see Online Help. |
|
Step 7 |
Click Save. |
Configure the intercluster service profile to activate extension mobility cross cluster. The profile collects all the configuration that precedes and provides a results report.
|
Step 1 |
From Cisco Unified CM Administration, choose . |
|
Step 2 |
Configure the fields on the EMCC Intercluster Service Profile Configuration window. For more information on the fields and their configuration options, see Online Help. |
|
Step 3 |
If no failure messages appear in the popup window, click Save. |
Configure the remote cluster for extension mobility cross cluster. This step completes the link between the home cluster with remote (visiting) cluster.
|
Step 1 |
From From Cisco Unified CM Administration, choose . |
||
|
Step 2 |
Click Find to show a list of known remote clusters. |
||
|
Step 3 |
Perform one of the following steps:
|
| Feature | Interaction |
|---|---|
| Audio |
The default maximum audio bit-rate for EMCC login device is set to 8 kbps (G.729). |
|
Call Admission Control (CAC) |
|
| Call Forwarding | EMCC supports call forwarding. |
|
Cisco Extension Mobility login and logout |
User authentication takes place across clusters. |
| Media resources for the visiting phone |
Examples include RSVP agent, TRP, music on mold (MOH), MTP, transcoder, and conference bridge. Media resources are local to the visiting phone (other than RSVP agents). |
| PSTN access for the visiting phone |
|
| Other call features and services |
Example restriction: Intercom configuration specifies configuration to a static device, so EMCC does not support the intercom feature. |
|
Security |
|
| Restriction | Description | ||
|---|---|---|---|
| Unsupported Features |
|
||
| EMCC Device Cannot Be Provisioned in More Than One Cluster |
For EMCC to function properly, you cannot configure the same phone (device name) in two clusters. Otherwise, login fails due to the duplicate device error (37). Therefore, for cluster that is deployed with EMCC you should disable Autoregistration on all Unified Communication Manager nodes to prevent a new device being created in the home cluster after EMCC logout. |
||
| Number of EMCC Devices |
Cisco Unified Communications Manager can support a MaxPhones value of 60,000. Include EMCC in the total number of devices that are supported in the cluster by using the following calculation: Phones + (2 x EMCC devices) = MaxPhones
|
||
| Visiting Device Logout Limitations |
|
||
| Visiting Device Login Limitations |
The extension mobility service in participating clusters performs a periodic remote cluster update. The Remote Cluster Update Interval feature parameter controls the update interval. The default interval is 30 minutes. If the extension mobility service on clusterA does not receive a reply from a remote cluster (such as clusterB) for this update, the Remote Cluster window for clusterA shows that the Remote Activated service is set to False for clusterB. 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 to 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" error message. At this point, a login attempt to EMCC from a visiting phone can fail; the phone displays the "Login is unavailable" error message. This error occurs because the visiting cluster has not yet detected the change of the home cluster from out-of-service to in-service. Remote cluster status change is based on the value of the Remote Cluster Update Interval EMCC feature parameter and on when the visiting extension mobility service performed the last query or update. You can select Update Remote Cluster Now in the Remote Cluster Service Configuration window () 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. |
The following table shows the login result of the Extension Mobility Cross Cluster feature for different cluster versions
when the loginType parameter is used in the service URL.
|
Visiting Cluster Version |
Home Cluster Version |
|
EMCC Login Result |
|---|---|---|---|
|
12.0 |
12.0 |
Not mentioned (Default URL) |
Success |
|
12.0 |
12.0 |
UID, SP, or DN |
Success |
|
12.0 |
11.5 and below |
Not mentioned (Default URL) |
Success |
|
12.0 |
11.5 and below |
UID, SP, or DN |
Fail Fail with error code - 1 ** |
|
11.5 and below |
12.0 |
Not mentioned (Default URL) |
Success |
|
11.5 and below |
12.0 |
UID, SP, or DN *** |
Success |
Note |
|
Note |
Phone configuration files can be encrypted only if both the home cluster and visiting cluster versions are 9.x or later, 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 or later, the phone will behave in various modes as shown in the following table.
|
Home Cluster Version |
Home Cluster Mode |
Visiting Cluster Version |
Visiting Cluster Mode |
Visiting Phone Mode |
EMCC Status |
|---|---|---|---|---|---|
|
9.x or later |
Mixed |
9.x or later |
Mixed |
Secure |
Secure EMCC |
|
9.x or later |
Mixed |
9.x or later |
Mixed |
Non-secure |
Non-secure EMCC |
|
9.x or later |
Mixed |
9.x or later |
Non-secure |
Non-secure |
Non-secure EMCC |
|
9.x or later |
Non-secure |
9.x or later |
Mixed |
Secure |
Login fails |
|
9.x or later |
Non-secure |
9.x or later |
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 or later, the phone will behave in various modes as shown in the following table.
|
Home Cluster Version |
Home Cluster Mode |
Visiting Cluster Version |
Visiting Cluster Mode |
Visiting Phone Mode |
EMCC Status |
|---|---|---|---|---|---|
|
9.x or later |
Mixed |
8.x |
Mixed |
Secure |
Not supported |
|
9.x or later |
Mixed |
8.x |
Mixed |
Non-secure |
Non-secure EMCC |
|
9.x or later |
Mixed |
8.x |
Non-secure |
Non-secure |
Non-secure EMCC |
|
9.x or later |
Non-secure |
8.x |
Mixed |
Secure |
Not supported |
|
9.x or later |
Non-secure |
8.x |
Non-secure |
Non-secure |
Non-secure EMCC |
During EMCC login, if the visiting cluster version is 9.x or later and the home cluster version is 8.x, the phone will behave in various modes as shown in the following table.
|
Home Cluster Version |
Home Cluster Mode |
Visiting Cluster Version |
Visiting Cluster Mode |
Visiting Phone Mode |
EMCC Status |
|---|---|---|---|---|---|
|
8.x |
Mixed |
9.x or later |
Mixed |
Secure |
Login fails |
|
8.x |
Mixed |
9.x or later |
Mixed |
Non-secure |
Non-secure EMCC |
|
8.x |
Mixed |
9.x or later |
Non-secure |
Non-secure |
Non-secure EMCC |
|
8.x |
Non-secure |
9.x or later |
Mixed |
Secure |
Login fails |
|
8.x |
Non-secure |
9.x or later |
Non-secure |
Secure |
Non-secure EMCC |
|
Error Code |
Phone Display |
Quick Description |
Reason |
|---|---|---|---|
|
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 on the Intercluster Service Profile window. |
|
202 |
Please try to login again (202) |
Blank userid or pin |
The user enters a blank user ID or PIN. |
|
204 |
Login is unavailable (204) |
Directory server error |
The EMApp sends this error to the 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 cannot be retrieved from the cache or the database. |
|
207 |
Login is unavailable(207) Logout is unavailable(207) |
Device Name Empty |
Occurs when the device or name tag is missing in the request URI. This cannot happen with real devices and can occur only if the request is sent from third-party applications. |
|
208 |
Login is unavailable(208) Logout is unavailable(208) |
EMService Connection Error |
The visiting EMApp cannot connect to any Visiting EMService. (The service is down or not activated.) The visiting EMService cannot connect to the Home EMService (the WAN is down or certificates are not trusted.) |
|
210 |
Login is unavailable(210) Logout is unavailable(210) |
Init Fail-Contact Admin |
An error (such as a database connection failure) occurred while initializing EMApp. The error can occur because of a failure to connect to the database during startup. |
|
211 |
Login is unavailable(211) Logout is unavailable(211) |
EMCC Not Activated |
Occurs when the 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 update fails by sending an incorrect cluster ID to the remote cluster. |
|
213 |
Login is unavailable(213) Logout is unavailable(213) |
Device does not support EMCC |
Occurs when a device does not support EMCC. |
|
215 |
LoginType invalid(215) |
Login Type is invalid |
Occurs when
|
|
216 |
DN has multiple users(216) |
DN has multiple users |
Occurs when the Extension used for EM login is assigned for multiple users as Primary. |
|
Error Code |
Phone Display |
Quick Description |
Reason |
||
|---|---|---|---|---|---|
|
0 |
Login is unavailable(0) Logout is unavailable(0) |
Unknown Error |
The EMService failed for an unknown reason. |
||
|
1 |
Login is unavailable(1) Logout is unavailable(1) |
Error on parsing |
When the EMService cannot parse the XML request from the EMApp or EMService. This error occurs when third-party applications send an incorrect query to login XML (EM API). The error can also occur because of a version mismatch between home and visiting clusters. |
||
|
2 |
Login is unavailable(2) |
EMCC Authentication Error |
The EMCC user credentials cannot be authenticated because the user entered an incorrect PIN. |
||
|
3 |
Login is unavailable(3) Logout is unavailable(3) |
Invalid App User |
Invalid application user. This error commonly occurs because of the EM API. |
||
|
4 |
Login is unavailable(4) Logout is unavailable(4) |
Policy Validation error |
The EM Service sends this error when it cannot validate the login or logout request because of an unknown reason, an error while querying the database or an error while retrieving information from the cache. |
||
|
5 |
Login is unavailable(5) Logout is unavailable(5) |
Dev. logon disabled |
A user logs into a device that has Enable Extension Mobility unchecked in the Phone Configuration window. |
||
|
6 |
Login is unavailable(6) Logout is unavailable(6) |
Database Error |
Whenever the database returns an exception while executing the query or stored procedure that the EM Service requests (login/logout or device/user query), the EM Service sends this error code to EMApp. |
||
|
8 |
Login is unavailable(8) Logout is unavailable(8) |
Query type undetermined |
No valid query was sent to the EMService (DeviceUserQuery and UserDeviceQuery are valid ones). This error occurs because of the EM API or incorrect XML input. |
||
|
9 |
Login is unavailable(9) Logout is unavailable(9) |
Dir. User Info Error |
This error appears in two cases:
|
||
|
10 |
Login is unavailable(10) Logout is unavailable(10) |
User lacks app proxy rights |
The user tries to log in on behalf of another user. By default, a CCMSysUser has administrative rights. |
||
|
11 |
Login is unavailable(11) Logout is unavailable(11) |
Device Does not exist |
The 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. |
||
|
18 |
Login is unavailable(18) |
Another user logged in |
Another user is already logged in on the phone. |
||
|
19 |
Logout is unavailable(19) |
No user logged in |
The system attempted to log out a user who has not logged in. This error occurs when sending logout requests from third-party applications (EM API). |
||
|
20 |
Login is unavailable(20) Logout is unavailable(20) |
Hoteling flag error |
Enable Extension Mobility is unchecked in the Phone Configuration window. |
||
|
21 |
Login is unavailable(21) Logout is unavailable(21) |
Hoteling Status error |
The current user status was not retrieved from either the local cache or database. |
||
|
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 |
Multi-Login Not Allowed (25) |
User logged in elsewhere |
The user is currently logged in to some other phone either in the local cluster or remote cluster. |
||
|
26 |
Login is unavailable(26) Logout is unavailable(26) |
Busy, please try again |
Occurs when the 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 |
Occurs when the Validate IP Address service parameter is set to True and the user tries to log in or log out from a machine whose IP address is not trusted. For example, a third-party application or EM API from a machine is not listed in the Trusted List of Ips service parameter. |
||
|
29 |
Login is unavailable(29) Logout is unavailable(29) |
ris down-contact admin |
The Real-Time Information Server Data Collector (RISDC) cache is not created or initialized, and the EMService is unable to connect to RISDC. |
||
|
30 |
Login is unavailable(30) Logout is unavailable(30) |
Proxy not allowed |
When login and logout occur through proxy ("Via" is set in HTTP header) and the 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 the Enable Extension Mobility Cross Cluster check box is not checked in the End User Configuration 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. |
||
|
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 a remote cluster. |
||
|
37 |
Login is Unavailable (37) Logout is Unavailable (37) |
Duplicate Device Name |
Occurs when the same device name exists in both the home cluster and visiting cluster. |
||
|
38 |
Login is unavailable(38) Logout is unavailable(38) |
EMCC Not Allowed |
Occurs when the home cluster does not want to allow EMCC login (The Enable Extension Mobility Cross Cluster check box is not checked in the home cluster). |
||
|
39 |
Please try to login again (201) |
Configuration Issue |
Occurs when the Default TFTP Server and Backup TFTP Server for EMCC login device are not set properly in EMCC Feature Configuration Page.
|
||
|
40 |
Please try to login again (23) |
No Response from Remote Host |
Occurs when response not getting from Remote Host.
|
||
|
41 |
PIN change is required |
PIN change is required |
Occurs when admin enables User Must Change at Next Login for PIN. In that case user is redirected to Change credentials page.
|
||
|
42 |
Login is unavailable(42) Logout is unavailable(42) |
Invalid ClusterID |
Occurs when the remote cluster ID is not valid. This error can occur during a remote cluster update. |
||
|
43 |
Login is unavailable(43) |
Device Security mode error |
The Device Security Profile that is associated to the EMCC device should be set to Nonsecure for its Device Security Mode. |
||
|
44 |
Please try to login again (201) |
Configuration Issue |
Occurs when the cluster ID is not valid.
|
||
|
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 nonsecure mode. |
||
|
47 |
DN has multiple users(47) |
DN has multiple users |
Occurs during EMCC login when the Extension used for login is assigned for multiple users as Primary. |
Feedback