ACS, CISCO IP Phone Extension Mobility Troubleshooting

www.fcsltd.com

BUSINESS PROCESSES | COL LLABORATIVE PLATFORMS | ENTERPRISE INTERFACES IN

Confidential Propr rietary Information. Do not copy or distribute without permission

Contents
Common Problems ................................................................ ................................................................................................................................ ................................................... 3 When a user reverts back to default profile, services are no longer available. ................................................................ ..................................................... 3 Extension Mobility logs out user after a few minutes, before the configured time. ................................................................ ............................................. 3 After ter login, the user does not have any services available. ................................................................................................ .................................................. 3 'Host not found' Error in IP Phone................................ ................................................................................................................................ ........................................................ 3 After a login or logout is performed, the phone resets instead of restarting. ................................................................ ........................................................ 4 Services return HTTP [8] error................................. ................................................................................................................................ ............................................................ 4 "Login ogin Unsuccessful:[101]" error returned on login. ................................................................................................ ........................................................... 4 Services do not appear when "services" is pressed. pressed................................................................................................. .............................................................. 4 After a user logs in, the phone does not have any services. ................................................................................................ ................................................. 4 After the username and password are entered, the phone returns to the login screen. ................................................................ ......................................... 4 Users are unable to log in to Extension Mobility and receive the login unsuccessful error 6. ............................................................. ................................ 5 "Login unsuccessful [9]" error message is generated on the phone. ................................................................ .................................................................... 5 Login unsuccessful Error [12] ................................ ................................................................................................................................ .............................................................. 5 Error [18]- Another User logged in ................................ ................................................................................................................................ ...................................................... 5 Extension Mobility service returns error [100] login unsuccessful when the service to login to Extention Moblity is chosen. .......... 6 Login unsuccessful error: [11]................................ ................................................................................................................................ .............................................................. 6 Unable to o apply the Extension Mobility feature to an IP phone and receive the error "Already logged in to another phone" ............ 6 "Warning 7" Appears ars During Login to Extension Mobility IP Phone ................................................................ ................................................................. 6 Extension Mobility Access is Slow ................................ ................................................................................................................................ ...................................................... 7 IP Phones Stuck in "Registering" or "Configuring IP" Status After Log Out ................................................................ ...................................................... 7 Extension Mobility Users Automatically Logged Out in Short Intervals ................................................................ ............................................................. 7 No Results when Searching ching the DN Assigned to the Device Profile ................................................................ ................................................................... 7 Unable to Logout an Entire Group of Users from Extension Mobility ................................................................ ................................................................ 7 Error: "Device does not exist" ................................ ................................................................................................................................ .............................................................. 7 Error: "Update failed" ................................................................ ................................................................................................................................ .......................................... 9 201 Authentication Error ................................................................ ................................................................................................ .................................................................... 10 [6]-Database Error ................................................................ ................................................................................................................................ .............................................. 10 Once logged in, there is no option to log out from the EM Service ................................................................ ................................................................... 11 Unable to log in to 7945 phone using 7965 profile ................................................................................................ ............................................................ 11 Error: Fatal error encountered while validating report XML with schema ................................................................ ........................................................ 12 Error: No Services Configured ................................ ................................................................................................................................ ........................................................... 12 Error: Host Not Found ................................................................ ................................................................................................................................ ........................................ 12 Cisco IP Phone Extension Mobility Host Error................................ ................................................................................................ .................................................................. 13 Error: Login is unavailable (205) ................................ ................................................................................................................................ ....................................................... 13 Error: Login is unavailable (208) Login is Unsuccessful ................................................................................................ ................................................... 14 No Display of Caller Name and Caller Number ................................................................................................ ................................................................. 14 Error: login is unavailable (210)................................ ................................................................................................................................ ......................................................... 15

BUSINESS PROCESSES | COL LLABORATIVE PLATFORMS | ENTERPRISE INTERFACES IN

Confidential Propr rietary Information. Do not copy or distribute without permission

Common Problems
When a user reverts back to default profile, services are no longer available.
Problem: After the services are added to the phone, the Update button is not pressed and the Auto Generated Default Profile is out of sync with the phone. Solution: Reselect the phone, add the services on the phone and update the phone configuration.

Extension Mobility logs out user after a few minutes, before the configured time.
Problem: When the user is logged in using Extension Mobility, the user is logged out after a few minutes, even though the Default maximum time for the login is set to 8 hours. Solution: If you do not need to specify the maximum time the user is allowed to be logged into Extension Mobility, always keep the Enforce Maximum Login Time* parameter to False. In order to do this, complete these steps: 1. Go to the Cisco Call Manager Administration page 2. Choose Service > Service Parameters and select Cisco Extension Mobility. 3. Make sure that the Enforce Maximum Login Time* parameter is set to False. 4. Click Update.

After login, the user does not have any servi services available.
Problem: The User Profile did not have any services associated with it when loaded on the phone. Solution: 1. Change the User Profile to include the login/logout services. 2. Change the phone the user is logged in on to include the login/logout services. Once updated, the user gets the logout service.

'Host not found' Error in IP Phone

Problem: The IP phone displays the "Host not found" error when the Services button is pressed. Solution: Choose System > Enterprise Parameters. Check the URL services, and if it is set to the Call Manager Server name, replace the Call Manager Server name with the IP address as shown in this example. Example: http://10.10.10.1/CCMCIP/ http://10.10.10.1/CCMCIP/getservicesmenu.asp, where 10.10.10.1 is the Cisco Call Manager IP address. Stop/start the TFTP, Internet Information Server (IIS), and Computer Telephony Integration (CTI) services and reboot the phones for the change to take effect. BUSINESS PROCESSES | COL LLABORATIVE PLATFORMS | ENTERPRISE INTERFACES IN
Confidential Propr rietary Information. Do not copy or distribute without permission

After a login or logout is performed, the phone resets instead of restarting.

Problem: The phone uses DNS to resolve the Cisco Call Manager name. Solution: Change System > Server name to an IP address. Reset the phone and try the login/logout procedure again.

Services return HTTP [8] error.

Problem: The phone is attacked by the Code Red Virus and the HTTP services no longer function. Solution: Apply the latest phone loads from the Cisco Web site to correct this problem.

"Login Unsuccessful:[101]" error returned on login.

When you launch the Extension ion Mobility (EM) service on the IP phone, this error message appears: Login Unsuccessful Error:[101]. Note: This error can be related to one of these problems. Problem: The username entered is not found in the DC Directory which can be also due to DC Directory Di replication Issues. Solution: Add the user through the Cisco Call Manager global directory. Also verify that DC Directory replicates between Servers. For more information on how to resolve DC Directory replication problems between DC Directory server services that run on Cisco Call Ma Manager nager servers involved in a Cisco Call Manager cluster, refer to Fixing Problems with DC Directory.

Services do not appear when "services" is pressed.

Problem: The phone device used does not have the services selected. Solution: Reselect the services on the phone and update the phone page.

After a user logs in, the phone does not have any services.
Problem: The user that has logged in does not have any services associated with their User Device Profile. Solution: Either through gh the Cisco Call Manager User page or the User Device configuration page, add the desired services to the User Device table.

After the username and password are entered, the phone returns to the login screen.
Problem: The form.jsp that is sent to the pho phone ne for the login is not able to resolve the port to be used for the login. As a result, the login request is never seen by the application. Solution: Download form.jsp. Replace the existing C: C:\Program files\wfaavvid\tomcat\webapps webapps\ROOT\form.jsp with the downloaded ownloaded file. This new form hard sets the service port number to 8080.

BUSINESS PROCESSES | COL LLABORATIVE PLATFORMS | ENTERPRISE INTERFACES IN

Confidential Propr rietary Information. Do not copy or distribute without permission

When logging in on a Cisco 7940 phone, the phone displays the error "Device profile does not exist"
Problem: Extension Mobility requests a fixed name for the device template that must be used on a Cisco 7940 phone when logging in. The name of the device template for the 7940 must exist and have the exact name of the template when the server is installed. Solution: Make sure the device template for the Cisco 7940 is 7940 1 1-Line or 7940 2-Line. Line. Ensure that a dash is used and the capitalization is correct.

Users are unable to log in to Extension Mobility and receive the login unsuccessful error 6.
Problem: User receives the login unsuccessful error: [6] error when pressing Select for the Extension Mobility service on the phone. Solution: Error 6 indicates an error when communicating with the database. This can be caused by many different things depending on n whether DC Directory or Active Directory is used. In the case of Active Directory, this issue can be resolved when you run the Active Directory plug plug-in in again. For more information on the Active Directory installation, refer to Active Directory 2000 Plug Plug-in in Installation for Cisco Call Manager. This issue can also occur if there is no device profile associated with the user that attempts to log in. Check if the users have device profiles associated with them under the User Configuration > Extension Mobility Mobilit page. If not, update users with device profiles for Extension Mobility login.

"Login unsuccessful [9]" error message is generated on the phone.

Problem: The user is unable to login to a phone, and receives a Login unsuccessful [9] error message when trying to login using Extension Mobility. Solution: This is normally a directory integration error. This could be LDAP, Active Directory, or DC Directory for example. Based on what method of directory integration is used, troubleshooting can vary. Check that the Active Directory server is running. If there is an issue here, run the Directory plug-in, plug and Adminutility from Cisco Call Manager. This issue can also occur if there is no device profile associated with the user that attempts to login. Check if the users have device profiles associated with them under the User Configuration > Extension Mobility page. If not, update users with device profiles for Extension Mobility login.

Login unsuccessful Error [12]

Problem: When logging into an IP phone enabled with Extension Mobility, the login fails and the phone displays Error[12]. Solution:This error occurs when the User Device Profile is improperly configured. Either the Device Profile does not exist, is mis-configured, configured, or is not associated with the user profile. Check all the User Device Profile settings, and ensure that there is a properly specified device profile, and a correct association with the user profile.

Error [18]- Another User logged in

Problem: When you try to log in to the IP phone using Extension Mobility, the error message error [18] - Another user logged in is received even though no user is logged in. The userid of the Extension Mobility user logged in is shown as None. When you try to dele delete te the phone, it fails with the error Delete Failed [438] User defined Device Profile cannot be deleted if it is in use. BUSINESS PROCESSES | COL LLABORATIVE PLATFORMS | ENTERPRISE INTERFACES IN
Confidential Propr rietary Information. Do not copy or distribute without permission

Solution: This issue can occur if any application user has control of the phone and the Application User ID is shown as none. Go to User er Management, select Application User, and unassociated it. You are now able to delete the phone.

Extension Mobility service returns error [100] login unsuccessful when the service to login to Extention Moblity is chosen.
Problem: When a user presses the e Services button, the phone displays Error [100]. Solution:This error occurs if the URL for the Cisco Extension Mobility service does not include the last parameter (shown in bold): http://<IPAddressofCallManager>/emapp/EMAppServlet?device=#DEVICENAME# <IPAddressofCallManager> specifies the IP address of the Cisco Call Manager server where Cisco Call Manager Extension Mobility is installed. Make sure that the URL is correct and complete. For example, http://10.45.67.89/emapp/EMAppServlet?device=#DEVICE http://10.45.67.89/emapp/EMAppServlet?device=#DEVICENAME#: NAME#: the URL is case-sensitive; case make sure that you enter the name exactly as described.

Login unsuccessful error: [11]

Problem: When a user tries to login to Extention Mobility, the IP phone displays: Login Unsuccessful Error:[11]. Solution:This error occurs if the URL for the Cisco Extension Mobility service is not entered correctly in the IP phone service parameter. On CCMAdmin, go to Feature > IP Phone services. Then do a search for your Extension Mobility service. Make sure that the URL matches this one: http://<IPAddressofCallManager>/emapp/EMAppServlet ?device=#DEVICENAME#

Unable to apply the Extension Mobility feature to an IP phone and receive the error "Already logged in to another phone"
Problem: When you try to apply the Extension Mob Mobility ility feature to an IP phone, the request is denied with an error thatsays you are already logged in to another IP phone. This situation arises when you are already logged in to an IP phone and want to log in to a new IP phone before you log out from the p previous revious phone. Solution: The best way to log out from the previous phone and log in to the new one is to change several service parameters in the Cisco CallManager Administration page as shown: 1. In the Cisco CallManager Administration window, go to Service > Service Parameters. 2. Choose the Extension Mobility service, and, in the Multiple Login Behavior box, change it to Auto Logout. Click Update. Auto Logout: After a user logs in to a second device, the Cisco CallManager automatically logs the user out of the first device.

"Warning 7" Appears During Login to Extension Mobility IP Phone

Problem: When you log into Extension Mobility IP phone, the Warning 7 message appears. Solution: Complete these steps in order to resolve this issue: 1. You can see all the the applications served by Tomcat at http://<IPAddr of the server>/manager/list. Determine whether Extension Mobility is listed here and running. BUSINESS PROCESSES | COL LLABORATIVE PLATFORMS | ENTERPRISE INTERFACES IN
Confidential Propr rietary Information. Do not copy or distribute without permission

2. Restart the Extension Mobility and Tomcat services during the off off-peak hours.

Extension sion Mobility Access is Slow

Problem: Extension Mobility Access is slow in Callmanager. Solution: Low memory resource on the Callmanager could cause this issue. Make sure that your CallManager server meets the minimum hardware requirements when you upgra upgrade to higher version.

IP Phones Stuck in "Registering" or "Configuring IP" Status After Log Out

If the IP phone stays in Registering or Configuring IP status after the user logs out of Extension Mobility, check to see if the Logout Profile is assigned to t the he device. Also, restart the Cisco Tomcat service. Note: If you use Cisco CallManager 6.x, you can restart the Cisco Tomcat service from the CLI with this command: admin: utils service restart Cisco Tomca Tomcat

Extension Mobility Users Automatically Logged Out in Short Intervals

Extension Mobility users are kicked out of the system every 5 minutes and the event log shows the Error: DeviceTransientConnection - Transient connection attempt error message. This issue can occur if the time on the Cisco CallManager Publisher and Subscriber are out of sync. In order to resolve this issue, you need synchronize the clock on all servers or configure ntp in the cluster for time synchronization. Also, change the Extension Mobility Service Parameter Multiple Login Behavior to Multiple Login's Not Allowed and restart the Extension Mobility Service.

No Results when Searching the DN Assigned to the Device Profile

When an Extension Mobility user logs into a phone, searching the directory number (DN) assigned to the device profile yields no results. 1. Go to Device > Phone. The Find and List Phones window appears. 2. Choose Actively Logged In Device Report from the drop-down list, and click Go. The Find and List Actively Logged In Device window appears. 3. Choose the directlry number, and click Find.

Unable to Logout an Entire Group of Users from Extension Mobility

Complete these steps in order to log out an entire group of users from Extension Mobility: 1. Disable the Extension Mobility service under Serviceability > Tools > Control Center. 2. Reset the device pool that contains all the phones that needs to be logged out. This will log out all the users that currently use Extension Mobility.

Error: "Device does not exist"

Problem: When the user tries to login to the Cisco IP phone in order to get the configured user profile information from Cisco Unified Communications Manager, this error message is received: BUSINESS PROCESSES | COL LLABORATIVE PLATFORMS | ENTERPRISE INTERFACES IN
Confidential Propr rietary Information. Do not copy or distribute without permission

LoginService: Dev: SEP<IP Phone MAC Address> Address>- Error# 11-Policy Policy Violation: Device does not exist: Device, 'SEP<IP Phone MAC Address>' does not exist

Or
Login Unsuccessful [11] "Device does not exist"

This issue can occur due to these reasons: Incorrect Extension Mobility Services URL. Refer to Solution 1 in order to make sure that the correct Extension Mobility Services UR URL is used. The IP phone is not subscribed for the Extension Mobility Services. Refer to Solution 2 in order to make sure that the IP phone is enabled with Extension Mobility service and is subscribed to the Extension Mobility service.

Solution 1

hese steps in order to make sure that the correct Extension Mobility Services URL is used: Perform these 1. Choose Device > Device Settings > Phone Services from Cisco Unified Communications Manager Administration. The Find and List IP Phone Services window appears. 2. Select the IP Phone service that you are using for Extension Mobility. The IP Phone Services Configuration window appears. 3. Ensure that the Service URL* field entry matches this format of URL:
http://<IP Address of Extension Mobility server>:8080/emapp/ EMAppServlet?device=#DEVICENAME# let?device=#DEVICENAME#

Correct the URL and save the service if it is not correct. Solution 2 Perform these steps in order to ensure that the IP phone is enabled with Extension Mobility service and is subscribed to the Extension Mobility service: 1. Choose Device > Phone from Cisco Unified Communications Manager Administration. The Find and List Phones window appears. 2. Select the phone that you want to verify if it is subscribed to the Extension Mobility service. The Phone Configuration window appears. 3. Go to the Extension Information section of this Configuration window. Make sure the Enable Extension Mobility check box is selected. If not selected, select the check box to enable Extension Mobility for this phone. BUSINESS PROCESSES | COL LLABORATIVE PLATFORMS | ENTERPRISE INTERFACES IN
Confidential Propr rietary Information. Do not copy or distribute without permission

4. On the top right of the Phone Configuration Page, choose Subscribe/Unsubscribe Services from the Related Links drop down menu. This opens the Subscribed Cisco IP Phone Services window. Here you can ensure that the phone is subscribed to the Extension Mobililty service.

Error: "Update failed"

Problem: While configuring Extension Mobility, this error message is received:
Update failed. One of the required fields on the page has the same value as an entry that already exists in the database. Please check the corresponding Find List page to verify your entry does not exist.

Solution Perform these steps in order to resolve this issue: 1. Delete the impacted phone from the database using CLI with this command:
run sql delete from device where name = 'SEPXXXXXXXXXXXX'

Note: SEPXXXXXXXXXXXX will be the Name of the phone. 2. Add it again in Cisco CallManager using the administrator webpage. 3. Configure Extension mobility again. BUSINESS PROCESSES | COL LLABORATIVE PLATFORMS | ENTERPRISE INTERFACES IN
Confidential Propr rietary Information. Do not copy or distribute without permission

201 Authentication Error

Problem: When the credential policy for a user is set to "User Must Change at Next Login," the user is prompted to change their PIN with the message [209]-Change PIN. . However, when the user enters the new PIN, the [201]Authenticaiton Error message displays and the user is not able to log in. Solution 1 Reset the user password/PIN in order to resolve the issue. Go to t the he user page and click the Edit Credentials button located near the password. Also, make sure the locked by the administrator field is unchecked. This isssue can also occur if the end users are using the alphanumeric characters to log in to extension mobility mobil since it is configured to use only numeric characters during log in. Go to the Extension Mobility service parameter Alphanumeric User ID and check if it is set to False. If it is, make sure that the end users are using only numeric characters during log g in. Solution 2 When the user tries to log in to Extension Mobility, the userid and PIN are validated through the Identity Management System (IMS). If the IMS returns a Change PIN error, the current implementation of Extension Mobility displays an error message essage on the phone to change the PIN. Users must change their PIN though the ccmuser pages and then attempt to log in. It is not possible to change the PIN from the phone.

[6]-Database Error
Problem: When you try to log in to Extension Mobility, this erro error r message is received after the username/password is entered and submit is clicked:
[6]-Database Error

The logs indicate this error:

<error code='6'>DB Request Error: Couldn't submit login request to DBL: 380

Solution 1 This issue can occur when the Tracemonitor thread dies, which causes the ADP synchronization issue. Restart the DBLmonitor service and the Tracemonitor thread in order to reslove the issue. Solution 2 Issue this command:
run sql update device set ikdevice_defaultprofile = NULL where name = 'SEPXXXXXXXX'

Where SEPXXXXXXXX is the proper device name. Solution 3 On the phone configuration page for the device, remove the check from the extension mobility check box and save the configuration, and then check again the extension mobility check box.

BUSINESS PROCESSES | COL LLABORATIVE PLATFORMS | ENTERPRISE INTERFACES IN

Confidential Propr rietary Information. Do not copy or distribute without permission

Once logged in, there is no option to log out from the EM Service
Problem The Extension Mobility service is configured and, after successfully logging in to the service, it appears that there is no option to log out of the service. Solution In order to resolve this problem, make sure that both the device and the device profile are subscribed to the Extension Mobility service.

Unable to log in to 7945 phone using 7965 profile

Problem After the Cisco Unified CM upgrade from version 6.1(4) to 6.1(5), wh when en the user tries to log in using a 7965 device-profile profile on a 7945 phone, the Extension Mobility login is successful, but the phone resets afterwards and gets stuck in a "restarting" and then "Registering" loop. This was possible before, when the customer was running 6.1.4.1190-3. Note: The phones are all on a SIP load. Initially, there were two extension mobility profiles for 7965 and 7945. The 7965 profile has 1 Directory Number and 5 Speed Dial buttons configured and was working fine. Solution This issue occurs only with SIP profile phones. The workaround is to reduce the number of Speed Dials on the 7965 profile to two or less, thereby enabling the user to log into the 7945 device using that profile. Perform these steps in order to reduce the number of Sp Speed Dials: 1. Log in to http://<server_name:portnumber>/ccmuser/, where server_name is the host on which the web server is installed. 2. Enter the user ID and password of the user whom's speed dial you want to remove. 3. Navigate to User Options > Device.

BUSINESS PROCESSES | COL LLABORATIVE PLATFORMS | ENTERPRISE INTERFACES IN

Confidential Propr rietary Information. Do not copy or distribute without permission

4. Choose Speed Dials.

5. Reduce the number of Speed Dials to two numbers by removing the other speed dial numbers. 6. Click the Save icon in order to save your changes. 7. Click Apply Config in the Speed Dial and Abbreviated Dial Configuration toolbar in order to apply the changes to your phone. 8. An Apply Configuration dialog box displays, confirming the device you are configuring. Click OK in order to confirm the changes. This issue is documented in Cisco bug ID CSCth32906 (registered customers only) .

Error: Fatal error encountered while validating report XML with schema
Problem When you try to generate the extension mobility report on Cisco Unified Reporting, this error message is received:
Fatal error encountered while validating report XML with schema: The reference to entity must end with the ';' delimiter.

Solution This issue can happen if there is some special character in the name field. Remove the special character in order to resolve the issue.

Error: No Services Configured

Problem After you upgrade CUCM from version 7.1.1 to version 7.1.5 , you receive this error when you try to access acce services: No Services Configured Solution Check the services for the phone or user profile selected. Also, ensure that voice VLAN is configured correctly. Restart the Cisco Extension Mobility and Tomcat service.

Error: Host Not Found

Problem When you select lect extension mobility on the Cisco IP Phone, the host not found error message is received. Solution BUSINESS PROCESSES | COL LLABORATIVE PLATFORMS | ENTERPRISE INTERFACES IN
Confidential Propr rietary Information. Do not copy or distribute without permission

Restart the Cisco Tomcat service in order to resolve this issue.

Cisco IP Phone Extension Mobility Host Error

Problem When you press the Services button a and nd select the extension mobility service, you receive this error: Host not found. Note: There were two servers and the issue started since the publisher relocation. Solution Complete these steps in order to resolve this issue: 1. On the CUCM Administration p page, choose Device > Device Settings > Phone Services. 2. Click Find, and select Extension Mobility service. 3. Point the extension mobility service to the new IP address on the Service URL. 4. Click Update Subscriptions. 5. For Secure-Service Service URL, change the port to 8443, and reset the phone in order to submit the changes.

Error: Login is unavailable (205)

Problem You receive this error message when you try to log in to Extension Mobility:
Login is unavailable (205)

Solution BUSINESS PROCESSES | COL LLABORATIVE PLATFORMS | ENTERPRISE INTERFACES IN

Confidential Propr rietary Information. Do not copy or distribute without permission

In order to resolve this issue, associate the phone to the Extension Mobility Controlled Profile.

Error: Login is unavailable (208) Login is Unsuccessful

Problem After the gateway IP address on Cisco Unified Communications Manager is changed and the IP phones are updated to CUCM, you receive this error when you press Login service:
Login is unavailable (208) Login is Unsuccessful

Solution This issue might occur if the Extension Mobility service is unable to reach the Tomcat certificate. In order to resolve this issue, regenerate the Tomcat certifi certificate cate and then restart the Tomcat and EM service.

No Display of Caller Name and Caller Number

Problem You do not receive caller name and caller number when logged in to Extension Mobility. However, when not using extension mobility, caller Information is di displayed. Solution The problem occurs when a configuration error is received while creating a User Device Profile for a User. Complete these steps in order to create the User Device Profile: 1. Choose Device > Device Settings > Device Profile, and click Add New. 2. From the drop-down down list, select the phone model to be configured (for example, Cisco 7960). 3. Click Next. 4. Enter a Device Profile Name (for example, "Your Name"). 5. From the Phone Button Template field, select Standard 7960 SCCP. 6. Click Save. 7. On the left-hand nd side of the screen, click the Line [1] - Add a new DN link. 8. Choose a valid DN from your NIP, and enter that DN in the Directory Number field. 9. Under Route Partition, select the required Partition. 10. Under Directory Number Settings, choose a CSS of appropri appropriate access. 11. Enter any Call Forward and Call Pickup Settings as necessary. 12. In the Display (Internal Caller ID), enter the User's name (if required). 13. Click Save. 14. From the Related Links: menu, select Subscribe/Unsubscribe Services. 15. Under Select a Service, select Extension Mobility, and click Next. BUSINESS PROCESSES | COL LLABORATIVE PLATFORMS | ENTERPRISE INTERFACES IN
Confidential Propr rietary Information. Do not copy or distribute without permission

16. Click Subscribe. 17. Click Save. You are now able to see the caller information.

Error: login is unavailable (210)

Problem The error login is unavailable (210) is received when you try to log in to Extension Mobility. The Extension Mobility App fails to initialize. Eventually this causes the database to block access. Solution In order to resolve the issue, complete these steps: 1. Ensure that the EM URL is correct. 2. Create a new device profile for the IP phone. 3. Restart the EM service.

BUSINESS PROCESSES | COL LLABORATIVE PLATFORMS | ENTERPRISE INTERFACES IN

Confidential Propr rietary Information. Do not copy or distribute without permission