Odd registration behaviour with Jabber when enabling "Public Multiple Server Connections" in the TMSPE provisiong temaplate for VCS-E cluster
TMS - v14.2
TMSPE - v1
Jabber - 4.6
VCS-C/E - x7.1
We have a cluster of VCS-Es, but only one VCS-C per traversal zone. I had thought after reading the Jabber Admin Guide that the "Multiple Server Connections" options allow just that when you have a cluster of VCSs. So essentially Jabber would firstly register with with one of the VCS-E in the cluster, then be told about the others and then register with them, so maintain multiple connections to all available VCSs in the cluster.
Se, I have set the "Public Multiple Server Connections" parameter to "On". The user can now log on externally to the VCS-E and I can see multiple registrations to all peers. Great.
However, when the user come to register internally to the VCS-C, I get all sorts of weird problems. The user almost registers then fails.I see Presence cannot be update message in the system tray, but most annoyingly I see multiple phantom registrations on the VCS-C that I then have to de-register manually. So, does anyone knwo what goes on here?
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...