Cisco Cisco TelePresence Video Communication Server Expressway
Appendix 5: Deployment with TelePresence
Conductor connected to Unified CM
Conductor connected to Unified CM
Deployment scenario
The following alternative deployment scenario is supported:
A VCS is connected to a Unified CM via a SIP trunk, and a TelePresence Conductor with its conference
bridges is connected to the Unified CM via another SIP trunk. Endpoints can be registered to both VCS and
Unified CM.
bridges is connected to the Unified CM via another SIP trunk. Endpoints can be registered to both VCS and
Unified CM.
Limitations
n
Only endpoints registered to the VCS can initiate a Multiway conference. Unified CM-registered endpoints
can be joined to the Multiway conference, but cannot initiate or add other participants into an existing
Multiway conference.
can be joined to the Multiway conference, but cannot initiate or add other participants into an existing
Multiway conference.
n
The join/conference button on Unified CM-registered endpoints initiates an ad hoc conference - this works
independently from Multiway and cannot add participants to Multiway calls.
independently from Multiway and cannot add participants to Multiway calls.
Conference creation process
The process of creating a Multiway conference involving the devices in the deployment scenario described
above, is:
above, is:
1. When a VCS-registered endpoint creates a Multiway conference, the VCS will generate a new conference
ID with a particular prefix.
Cisco TelePresence Multiway™ Deployment Guide (X8.2, XC2.4)
Page 38 of 42
Appendix 5: Deployment with TelePresence Conductor connected to Unified CM