Login to Extension Mobility on the IP phone fails, and the "Login Unsuccessful Error:[6]" error message appears

[TCC_2]

Core Issue

When the Extension Mobility (EM) service is launched on the IP phone, the immediate response is the appearance of the Login Unsuccessful Error:[6] error message. The Cisco CallManager currently runs version 4.1(3).

Resolution

Complete these steps in order to resolve the issue, if the data connection (DC) Directory is used:

1. Make sure the C:\dcdsrvr\DirectoryConfiguration.ini file is populated and that this file is identical on all the Cisco CallManager servers in the cluster.
   
   If this file is absent or not populated in any of the servers in the cluster, the login fails.
   
   
2. Change the UserSSL setting in the C:\dcdsrvr\DirectoryConfiguration.ini file from True to False.

In order to resolve this issue if active directory (AD) is used, compete these steps:

1. Reinstall the AD plugin.
   
   
2. Make sure the C:\dcdsrvr\DirectoryConfiguration.ini file is populated and that this file is identical on all the Cisco CallManager servers in the cluster.
   
   
3. Change the UserSSL setting in the C:\dcdsrvr\DirectoryConfiguration.ini file from True to False.
   
   
4. Reinstall the AD.

If AD is not used, complete these steps:

1. Verify that the virtual directory login password is correct.
   
   
2. Make sure that the DC Directory Service runs. If not, start the service.
   
   
3. See if the users have device profiles associated with them under the User Configuration > Extension Mobility page.
   
   If not, update the users with device profiles for Extension Mobility login.
   

Refer to these documents for more information:

• The Integrating Microsoft Active Directory with Cisco CallManager section of Installing the Cisco Customer Directory Configuration Plugin for Cisco CallManager Release 4.1(2)
  
  
• Cisco CallManager Extension Mobility