Cisco Cisco TelePresence Video Communication Server Expressway
Cisco Multiway without TelePresence Conductor
Cisco TelePresence Multiway Deployment Guide (Cisco VCS X7.2 and Conductor XC2.0)
Page 17 of 35
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.
that conference IDs are unique for each VCS.
VCS configuration: with Lync
n
Multiway is supported with Lync.
n
F8.1 or later must be used for MXP endpoints.
n
Version TE1.0.1 or later must be used for E20 endpoints.
Note that:
n
If there is no camera attached to Lync, E20 may not connect a call to that Lync as it needs to see video
traffic to complete the connection.
traffic to complete the connection.
n
Lync must have a static domain route to allow Lync to be able to route calls to the Multiway MCU’s domain
(the domain specified in the Conference Factory’s Template). Lync needs to be able to route calls to the
MCU’s domain to allow Lync to make a call to the ad hoc conference that is defined in the REFER which is
initiated when “Merge” is pressed.
(the domain specified in the Conference Factory’s Template). Lync needs to be able to route calls to the
MCU’s domain to allow 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 Lync 2010 and VCS Deployment Guide.
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 VCS and Cisco Unified Communications Manager Deployment Guide
CUCM 6.1, 7, 8 and X7.2.
Multiway and CUCM” appendix in the VCS and Cisco Unified Communications Manager Deployment Guide
CUCM 6.1, 7, 8 and X7.2.
Note that the CUCM must be configured to allow dialing to the VCS domain to which Multiway aliases are
registered – this is documented in the “Allow dialing to VCS domain from Cisco phones” appendix in the
same deployment guide.
registered – this is documented in the “Allow dialing to 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.
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
Create new ad hoc conference
Require H.323 gatekeeper callers to enter PIN
Ensure this option is not selected
Time to wait when setting up ad hoc conference PIN
<never configure PIN>
2. Optional (these are recommended settings, but can be configured as required for the installation – they are
only applicable if the Encryption option is installed on the MCU):
a. Go to
Settings > Encryption
and configure the following fields:
Encryption status
Enabled
SRTP encryption
Secure transports (TLS) only