We currently run a pair of (about to be) clustered VCS-Controls that all our endpoints register to - we'll call these EndpointVCS1 and Endpoint VCS2. Our endpoints can then use DNS SRV to lookup SIP and H323 details for ourcompany.com, giving details for EndpointVCS1 and EndpointVCS2 with different weight/priority etc.
We also run a second set of VCS-Controls that our Telepresence Servers register to - we'll call these MCU-VCS1 and MCU-VCS2. Currently they are not clustered. As we can only have a single SRV entry for our domain, Currently, MCU1 can only use MCU-VCS1 and MCU2 can only use MCU-VCS2, as we can't make seperate SRV records for the MCU-VCS's.
So my quesiton is this - how can I achieve redundancy with two seperate VCS clusters in the same domain? Are there any plans to improve clustering and redundancy for VCS/Telepresence server, such as the way CUCM/CTMS works where you can enter multiple hosts?
When reading your post the first question that comes to mind is: why do you have four separate VCS installations? Have you really grown beyond the capacity of a single cluster; or is there some other architectual reason why you're forced to retain both Endpoint-VCS1 and -VCS2? The second question is why are your TPS registered to separate VCS Control servers?
The traditional way VCS was designed when you had multiple clusters was to use subdomains. For example, if the clusters serve different continents they could become na.domain.com and emea.domain.com. VCS follows the DNS heirarchy-based naming principals fairly well. There are methods of using FindMe accounts on a VCS Expressway cluster to front-end multiple Control clusters for single "public" identities; however, this is extremely manual since you have to configure it manually per-user (e.g. firstname.lastname@example.org is a FindMe account with email@example.com as a device).
My opinion is that you should not expect the basic design concepts of VCS itself to change. Without getting into product roadmaps - which require NDA signature - Cisco UC Manager is likely the way to solve this when URI Dialing eventually gets added. Yes, that's a tightrope you see me walking.
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...