Cisco Cisco TelePresence Video Communication Server Expressway

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.  

Use of software 3.1 or later is also recommended. 
1. Go 

to 

Settings > Conferences, Advanced settings and configure the following fields: 

 

Ensure this option is not selected 

Time to wait for ad hoc 
conference PIN set up 

 

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) 
Go to Settings > Encryption and configure the following fields: 

 

Encryption required for new 
ad hoc conferences 

 

1. Go 

to 

Settings > Gatekeeper and configure the following fields: 

 

Set to the IP address of the Cisco VCS 

Gatekeeper registration type 

Select both entries (ensures that MCU uses Cisco VCS 
as the gatekeeper for all calls) 

The H.323 ID can be any unique alphanumeric ID – it 
will be registered onto the Cisco VCS 

This is where <Prefix for MCU registrations> is 
configured e.g. 555 (same as MCU service prefix) 

This is where <MCU service prefix> <is configured e.g. 
555 (same as Prefix for MCU registrations) 

Select this check box 

Set these based on the capacity of the MCU being 
configured, and expected ad hoc conference sizes 

 

2.  Configure conference settings: 

 

From MCU version 4.1 

i. Go 

to 

Conferences > Templates and select Ad hoc template Ad hoc conferences. 

Cisco VCS Deployment Guide: Multiway™ (Cisco VCS X5) 

Page 12 of 25