I set it up using a System PG, the difference being I didn't have to configure the device targets. The one issue I had originally was the CM device names didn't match and JTAPI showed an error that the LCP couldn't find it's RCP match. The device names in CM must be the same except for either LCP or RCP at the beginning. So in your case if the port is 10001 it should be LCP500910001 and RCP500910001, and not the 11001 you said the RCP is currently
What I used is, (if 10001 is your agent extention)
/devtype CiscoPhone /dn 10001
This at least, makes agent login work.
However my problem is, how to define label for this device target, if i used label 10001, this label will be returned to egress gateway, and cause error.
My understand is, the returning label shall be the full number which agent inputs in Mobile agent login screen, ICM shall convert 10001 to the full number of agent, and return it as label. It doesn't happen so far.
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...