He is setup in call manager. His AD username is associated to his phone. His phone is associated to the rmjtapi user. He is setup as both a supervisor and an agent in IPCC. He can successfully launch his Supervisor Desktop. I've gone so far as to completely delete and rebuild his phone and re-register it. He still gets the same error. Any suggestions?
To resolve this issue, choose from one of these options:
Share the Program Files\Cisco\Desktop_Config\Desktop folder on the CRS server and provide sufficient rights for the agent. This enables the Cisco Agent Desktop to automatically update the JTAPI client with the correct version when it attempts to log in.
Manually copy the JTAPI client from the CRS server Program Files\Cisco\Desktop_Config\Desktop\Agentins\JTAPI\jtapi.jar and overwrite it onto the agent desktop Program Files\Cisco\Desktop\bin\CiscoJTAPIClient\Lib\jtapi.jar.
Run this Java Update utility on the CRS server: Start > Programs > CRA Admin > JTAPI Update utility. Whenever a client logs in, this verifies and updates the JTAPI.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...