Cisco Cisco TelePresence Video Communication Server Expressway
Cisco Multiway without Conductor
Cisco TelePresence Multiway Deployment Guide (Cisco VCS X7.2 and Conductor XC1.2)
Page 16 of 35
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.2.
TelePresence Multiway and CUCM” appendix in the Cisco 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 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
enter PIN
Ensure this option is not selected
Time to wait when setting up ad hoc
conference PIN
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
b. Go to
Conferences > Templates
, select the Top level template and configure the following
field:
Encryption
Optional
c.
Go to
Conferences > Templates
select the Ad hoc conferences template and configure
the following field:
Encryption
Optional
H.323 settings
1. Go to
Settings > H.323
and configure the following fields:
H.323 gatekeeper usage
Required
H.323 gatekeeper address
Set to the IP address of the Cisco VCS
Gatekeeper registration type
MCU (standard)
Ethernet port association
Select both entries (ensures that MCU uses Cisco VCS
as the gatekeeper for all calls)
as the gatekeeper for all calls)
(Mandatory) H.323 ID to register
The H.323 ID can be any unique alphanumeric ID – it will
be registered onto the Cisco VCS
be registered onto the Cisco VCS
Password
Select Use password and enter the relevant Password
if the VCS has authentication enabled.
if the VCS has authentication enabled.
Prefix for MCU registrations
This is where <Prefix for MCU registrations> is