After the CRS is installed in the Cisco CallManager Subscriber Server of a cluster, unable to start the JTAPI subsystem and user receives the "CTIERR_UNSPECIFIED[0x0]" error message

[TCC_2]

Core Issue

In the Cisco CallManager 4.x Cluster, after the Customer Response Solution (CRS) is installed on a subscriber server, the JTAPI subsystem fails to start. The log located at c:\ program files\wfavvid\log\ciscomivr.log contains the unspecified errorcom.cisco.jtapi.CiscoRegistrationExceptionImpl: At least one media capability must be specified error message.

A restart of the CRS Engine has no effect on this issue.

Resolution

This error message in the log indicates that it is a failed install, and that the codec does not get set in the registry for some reason. Check this location in the CRS server registry:

HKEY_LOCAL_MACHINE\SOFTWARE\CiscoSystems,Inc.\CRS\Properties\application.MIVR.properties.com.cisco.dialog.cod
ec = G711ULAW64K,G711ALAW64K

If it is not there, add the G711 codec with these steps:

1. Stop Node Manager on the CRS server.
   
   
2. Choose Cisco CallManager > LDAP > CCN Apps > Clusters > Custer Specific > Properties.Files
   
   
3. On the right, locate the application.mivr.properites key, and delete it.
   
   
4. Choose CRS Registry > HK LM > Software > Cisco Systems INC > CRS > Properties, and choose application.medt/MADM/MCVD.properties.
   
   
5. Locate com.cisco.dialog.code, and copy the value string.
   
   
6. Choose application.MIVR.properties, and change the com.cisco.dialog.codec value to the one copied in the previous step.
   
   
7. Restart the Node Manager service in Microsoft Windows services.
   

If the JTAPI subsystem still fails to come into service, complete these steps:

1. Use the media in order to uninstall the CRS.
   
   
2. Make sure that these registry keys are removed:
   
   HKEY_LOCAL_MACHINE\SOFTWARE\CiscoSystems,Inc.\CRS\Properties\application.MADM.properties
   HKEY_LOCAL_MACHINE\SOFTWARE\CiscoSystems,Inc.\CRS\Properties\application.MCVD.properties
   HKEY_LOCAL_MACHINE\SOFTWARE\CiscoSystems,Inc.\CRS\Properties\application.MEDT.properties
   HKEY_LOCAL_MACHINE\SOFTWARE\CiscoSystems,Inc.\CRS\Properties\application.properties
   HKEY_LOCAL_MACHINE\SOFTWARE\CiscoSystems,Inc.\CRS\Properties\application.MIVR.properties
   
   
3. Use a new cluster profile name in order to reinstall CRS.
   
   
4. Run the JTAPI Update Utility in order to verify the JTAPI client.
   
   
5. Confirm the codec is now installed.

Refer to these documents for more information:

• Install and Upgrade Guides
  
  
• Troubleshooting JTAPI Subsystem Startup Problems

[Stephen Keller]

I had similar issue on UCCX 8.5.1 SU2 in HA configuration where the CTI RP would register fine but the CTI Ports would not. They would get created and associated correctly with the Application USer but would not register. the MIVR logs showed the following error :

com.cisco.jtapi.CiscoRegistrationExceptionImpl: At least one media capability must be specified

the resolution ended up being that in UCCX under service parameters we changed the codec from g.711 to g.729 and then restarted CCX engine. the ports registered immediately. of course, we changed it back to g.711 and they all re-registered. it took me about 4 hours to get there so i hope this could help someone else out there one day. For whatever reason the CCCX engine was not recognizing the 711 coded and bouncing this resolved that issue. Best of Luck out there!