Cisco Cisco TelePresence Video Communication Server Expressway
Appendix 4: Impact of clustering on other VCS
applications
applications
Conference Factory (Multiway™)
When using Conference Factory (Multiway) in a cluster, note that:
n
The Conference Factory application configuration is NOT replicated across a cluster.
n
The Conference Factory template MUST be DIFFERENT on each of the VCS peers.
When configuring a cluster to support Multiway:
1. Set up the same Conference Factory alias (the alias called by the endpoint to initiate a Multiway
conference) on each peer.
2. Set up a different Conference Factory template on each peer (so that each peer generates unique
Multiway conference IDs).
For example, if the MCU service prefix for ad hoc conferences is 775 then the Master VCS may have a
template of 775001%%@domain, peer 2 a template of 775002%%@domain, and peer 3 a template of
775003%%@domain
template of 775001%%@domain, peer 2 a template of 775002%%@domain, and peer 3 a template of
775003%%@domain
. In this way, whichever VCS serves the conference ID, it cannot serve a conference ID
that any other VCS could have served.
The same applies across a network. If there is more than one VCS or VCS cluster that provides Conference
Factory functionality in a network, each and every VCS must provide values in a unique range, so that no two
VCSs can serve the same conference ID.
Factory functionality in a network, each and every VCS must provide values in a unique range, so that no two
VCSs can serve the same conference ID.
Microsoft Lync
Cisco TelePresence VCS Cluster Creation and Maintenance Deployment Guide (X8.5)
Page 37 of 49
Appendix 4: Impact of clustering on other VCS applications