12-07-2006 11:39 AM - edited 03-18-2019 06:42 PM
Can you tell accomplish the task below?
I'm getting JTAPI Loging Failed Error while determining CCM version -1
CUCM is 4.2(3)
CUE is 2.3(2)
Another forum user explained this would solve my issue?
http://<callmanager>/CCMPluginsServer/CiscoJTAPIClient.exe on port 80. IIS in the CallManager is configured to "require SSL" in the CCMPluginsServer directory. After disabling that requirement in IIS, the CUE setup was able to continue.
12-13-2006 12:22 PM
This implies that we probably have a license file for CallManager Express, rather than CallManger.Refer URL
http://www.cisco.com/univercd/cc/td/doc/product/voice/unityexp//rel2_1/cmecligd/ch2a_upg.htm#wp1122572 for more information.
12-13-2006 01:32 PM
Actually, if you have the wrong license, it won't even ask you for the JTAPI/CallManager integration stuff. I'm not sure about the original question. You do have to disable SSL for that directory for it to work properly.
12-13-2006 04:53 PM
I had a problem with UnityExpress accessing jtapi.jar. I changed the Anonymous user for the default web site to CCMUser and everything works fine. There is a bug that say's to turn off SSL in the web site directories but that didn't work. Everything is working great now.
12-17-2006 07:08 AM
Calude,
Have you expereince a problem were IP communicator is not able to stay connected to CUE or messages saved to CUE are never recorded completely?
12-17-2006 12:31 PM
Just started using this, I'm a Unity person myself. The original issue Cisco has opened a Bug on with a service release for fix. I am having MWI issues with Communicator right now, but that is across VPN (IPSEC) tunnel.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide