Cisco Cisco TelePresence Video Communication Server Expressway
Cisco Multiway without Conductor
Cisco VCS Deployment Guide: Multiway™ (Cisco VCS X7)
Page 16 of 35
template: 55577001%%@example.com, VCS 2 would have a template
55577002%%@example.com.
55577002%%@example.com.
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/Lync
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/Lync
Multiway is supported with OCS R2/Lync.
F8.1 or later must be used for MXP endpoints.
Version TE1.0.1 or later must be used for E20 endpoints.
Note that:
If there is no camera attached to MOC/Lync, E20 may not connect a call to that MOC/Lync as it
needs to see video traffic to complete the connection.
needs to see video traffic to complete the connection.
OCS/Lync must have a static domain route to allow OCS/Lync to be able to route calls to the
Multiway MCU’s domain (the domain specified in the Conference Factory’s Template). OCS/Lync
needs to be able to route calls to the MCU’s domain to allow OCS/Lync to make a call to the ad
hoc conference that is defined in the REFER which is initiated when “Merge” is pressed.
Multiway MCU’s domain (the domain specified in the Conference Factory’s Template). OCS/Lync
needs to be able to route calls to the MCU’s domain to allow OCS/Lync to make a call to the ad
hoc conference that is defined in the REFER which is initiated when “Merge” is pressed.
For further details see Microsoft OCS 2007, Lync 2010 and Cisco VCS Deployment Guide.
Cisco VCS configuration: with CUCM
For details about the configuration needed in CUCM to support Multiway, see the “Cisco
TelePresence Multiway and CUCM” appendix in the Cisco VCS and Cisco Unified Communications
Manager Deployment Guide CUCM 6.1, 7, 8 and X7.0.
TelePresence Multiway and CUCM” appendix in the Cisco VCS and Cisco Unified Communications
Manager Deployment Guide CUCM 6.1, 7, 8 and X7.0.
Note that the CUCM must be configured to allow dialing to the Cisco VCS domain to which Multiway
aliases are registered – this is documented in the “Allow dialing to Cisco VCS domain from Cisco
phones” appendix in the same deployment guide.
aliases are registered – this is documented in the “Allow dialing to Cisco VCS domain from Cisco
phones” appendix in the same deployment guide.
Cisco TelePresence MCU configuration
Although many MCUs will support basic 3 way Multiway when used as an H.323 or SIP only MCU, for
full Multiway functionality the use of Cisco TelePresence MCUs is strongly recommended.
full Multiway functionality the use of Cisco TelePresence MCUs is strongly recommended.
Use of software 3.1 or later is also recommended.
1. Go to
Settings > Conferences, Advanced settings
and configure the following fields:
Incoming calls to unknown
conferences or auto attendants
conferences or auto attendants
Create new ad hoc conference
Require H.323 gatekeeper
callers to enter PIN
callers to enter PIN
Ensure this option is not selected