Cisco Cisco TelePresence Video Communication Server Expressway
Cisco VCS configuration
Cisco VCS Deployment Guide: Multiway™ (Cisco VCS X6)
Page 11 of 28
Cisco VCS configuration: in a network of VCSs
If the VCS is in a network with other VCSs, one or more VCSs may have Conference Factory enabled.
Each VCS with Conference Factory enabled, whether it has the same or different alias configured,
must generate a unique ad hoc conference ID. Therefore, just as with clusters, every VCS that has
Conference Factory enabled must have a unique template. Use a unique VCS ID after the
<Conference prefix> to ensure that conference IDs are unique for each VCS.
must generate a unique ad hoc conference ID. Therefore, just as with clusters, every VCS that has
Conference Factory enabled must have a unique template. Use a unique VCS ID after the
<Conference prefix> to ensure that conference IDs are unique for each VCS.
Cisco VCS configuration: with OCS
OCS R1
Multiway™ is not supported with OCS R1.
OCS R1 does not accept being invited to join a Multiway conference — OCS invalidly rejects the
INVITE to put it on hold before joining the conference with “421 Bad Extension – timer”.
INVITE to put it on hold before joining the conference with “421 Bad Extension – timer”.
OCS R2
Multiway™ is supported with OCS R2.
F8.1 or later must be used for MXP endpoints.
Version TE1.0.1 or later must be used for E20 endpoints.
Note:
If there is no camera attached to MOC, E20 may not connect a call to that MOC as it needs to
see video traffic to complete the connection.
see video traffic to complete the connection.
OCS must have a static domain route to allow OCS to be able to route calls to the Multiway™
MCU’s domain (the domain specified in the Conference Factory’s Template). OCS needs to be
able to route calls to the MCU’s domain to allow OCS to make a call to the ad hoc conference
that is defined in the REFER which is initiated when “Join” is pressed.
MCU’s domain (the domain specified in the Conference Factory’s Template). OCS needs to be
able to route calls to the MCU’s domain to allow OCS to make a call to the ad hoc conference
that is defined in the REFER which is initiated when “Join” is pressed.
For further details about configuration with OCS, see the “Cisco VCS deployment guide for Microsoft
OCS 2007 and Cisco VCS”.
OCS 2007 and Cisco VCS”.
Cisco VCS configuration: with CUCM
To enable CUCM registered endpoints to be joined into a Multiway™ conference set the Conference
Factory Template to use the IP address of the VCS as the domain, for example
55501%%@<IPofVCS>.
Factory Template to use the IP address of the VCS as the domain, for example
55501%%@<IPofVCS>.
Also configure a SIP Route pattern in CUCM that routes the domain @<IPofVCS> to the SIP trunk
connecting to VCS.
connecting to VCS.