The Cisco Unity Express CTI ports do not register with the Cisco CallManager, and the "JTAPI login failed. Error while determining CCM version -1" error message appears

[TCC_2]

Core Issue

After the Cisco CallManager is upgraded to version 4.2(3), the Cisco Unity Express reports that it is unable to determine the Cisco CallManager version when it verifies the Web and Java Telephony API (JTAPI) username and password information.

Cisco CallManager disables non-secure access to the http://x.x.x.x/CCMPluginsServer/CiscoJTAPIClient.exe URL in versions 4.2(3) and later. The Cisco Unity Express relies on this URL in order to determine the Cisco CallManager version. As a result, it fails to detect the correct Cisco CallManager version. But, the default Cisco Unity Express JTAPI jar (skate, 4.1) registers successfully to a Cisco CallManager 4.2(3), and it is not possible to make calls.

This issue is found in Cisco CallManager version 4.2(3) with these supported versions of Cisco Unity Express:

• 2.3(1)
  
  
• 2.3(2)

All functionality remains. The Computer Telephony Integration (CTI) ports and route points register with Cisco CallManager. The voicemail (VM) and auto attendant (AA) route points are functional and able to be dialed.

Resolution

This issue is documented in Cisco bug ID CSCsg11684

The workaround for this problem is to disable Secure HTTP (HTTPS) for the URL. Complete these steps on the Cisco CallManager:

1. Choose Start > Programs > Administrative tools > Internet Services Manager.
   
   
2. Click the server name and expand it.
   
   
3. Expand Default web site.
   
   
4. Right-click CCMPluginsServer, and choose properties.
   
   
5. Choose Directory security.
   
   
6. Click edit under Secure Communications.
   
   
7. Uncheck the require secure channel checkbox at the top.
   
   
8. Click OK, and close the two dialog boxes.