Cisco Cisco TelePresence Video Communication Server Expressway
Connecting multiple MCUs to a single Cisco VCS
Cisco VCS Deployment Guide: Connecting MCUs to Cisco VCSs for resilience and capacity
Page 4 of 10
Connecting multiple MCUs to a single Cisco
VCS
VCS
Requirements
When connecting multiple MCUs to a single Cisco VCS, it is important that:
all connected MCUs are used to host conferences
calls made by different people for the same conference ID must be directed to the same MCU
if there is an imbalance of callers on one or more MCUs and it or they approach their capacity
(reporting “out of resources”), new conferences should be created on a less busy MCU
(reporting “out of resources”), new conferences should be created on a less busy MCU
Operation
Each MCU is configured to register the same conference service prefix(es) on the Cisco VCS. When a
call for a conference arrives, the Cisco VCS will check to see whether that conference ID is already
registered.
call for a conference arrives, the Cisco VCS will check to see whether that conference ID is already
registered.
If the conference ID is registered (i.e. the conference has already been initiated), the call will be
routed to that MCU.
routed to that MCU.
If the conference ID is not registered by any of the MCUs, but the required conference service
prefix is registered by one or more MCUs, then the Cisco VCS will check to see whether another
call has been made for this conference ID recently
prefix is registered by one or more MCUs, then the Cisco VCS will check to see whether another
call has been made for this conference ID recently
•
If there has been no other recent call to this conference ID (i.e. this is the first), the Cisco
VCS will randomly choose one of the MCUs that has registered a matching service prefix and
will use that MCU for this conference ID. The Cisco VCS will route the call to that MCU so
that the conference may be set up.
VCS will randomly choose one of the MCUs that has registered a matching service prefix and
will use that MCU for this conference ID. The Cisco VCS will route the call to that MCU so
that the conference may be set up.
.
•
If there has been a recent call to this conference ID, the Cisco VCS will route this call to the
same MCU to which the other call to this conference ID was routed. (This handles the
situation where one or more callers dial in at almost the same time as the initiator, and so
require their call(s) to be routed to the correct MCU before the MCU has had time to register
the new conference ID.)
same MCU to which the other call to this conference ID was routed. (This handles the
situation where one or more callers dial in at almost the same time as the initiator, and so
require their call(s) to be routed to the correct MCU before the MCU has had time to register
the new conference ID.)
1 recently = within 1 minute. 1 minute gives the MCU plenty of time to register the full conference ID of the ad hoc conference
that it has been requested to create.
that it has been requested to create.