The current design guidance for remote JTAPI over the WAN is "don't do it." It has not been tested officially and is not supported -- these connections are designed to be "local" on a layer two switch -- not a routed connection. Although it's only call control, the messaging protocol is very time sensitive and needs to see messaging in a particular order, so if the network dropped a "call answered" event, it would not be re-sent and the PG wouldn't know it happened.
Other components, like the Agent Desktop and the CTI OS Server are also fine to be remote from each other over a WAN. They aren't tagged like the PG traffic, but the messaging protocol isn't as fussy and can self-heal from dropped packets. Likewise the AW's can be remote from the ICM Central Controller but I'd make the note that if the AW is an HDS, there is additional data being sent to it from the Logger as part of the HDS replication, so you may need to factor in additional bandwidth to handle this data flow over the WAN -- better to be safe than sorry as I found at a large enterprise customer (12 sites and 6,000 agents) they needed a T-1 just to keep the HDS up to date across their WAN link.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...