We went from CM 4.x to CM 6.1.2. We have several people that use IP Communicator. If they are on the LAN, works fine. If they are connected via a site-to-site VPN, works fine. If they connect through an SSL VPN and then Network Connect (it is a Juniper SA 4000 SSL VPN), it is unpredictable. Sometime, we start it and it sits there for 15-20 minutes, and then it finally works. Sometimes, it doesn't ever work. Very rarely, it works right away. People had no problem with IP Communicator through the SSL VPN when we were using CM 4.x.
We did have IPC set up to use SCCP, but we changed it to SIP, and that seems to work, although we are doing more testing.
The new servers are on the same VLAN as the old systems were, so I don't think it is a firewall or routing issue. Does anyone out there have any ideas? I opened a TAC case, but so far we have had no luck in fixing it.
I got it working. It was something on the firewall. Why it would work using CM 4 but not CM 6, I'm not sure. But there were SCCP Invalid Message/Invalid Length messages, so I looked on the firewall and found an application layer gateway setting that needed changed.
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...