Cisco Cisco TelePresence Video Communication Server Expressway

Cisco VCS configuration 

IP address of MCU 

 

3. Go 

to 

VCS configuration> Search rules > Rules. 

4.  Configure a search rule as follows: 

 

48 

Pattern type 

<MCU service prefix>(<Conference prefix>\d+@MCU.domain) 

e.g. 555(77\d+@mycompany.com) 

Zone created above, for example Multiway - SIP 

 

Note: When a SIP ad hoc conference is set up, it will register 
<Conference prefix>%%@MCU.domain. Make sure that <Conference prefix> is unique for SIP 
calls, so that it does not match other dialable SIP destinations. 

Follow the processes above and set up the Cisco VCS to work with an H.323 MCU and also to work 
with a SIP MCU: 

 

It is very important that the priority of the Neighbor zone search rule for the SIP MCU is the same 
value as the priority for the Local zone search rule that takes the received conference URI and 
converts it to an E164 number (i.e. 48). 

When Cisco VCS is routing calls, at any particular match priority value, it routes the call in native 
protocol in preference to interworking the call. By making both the SIP route to the MCU and the 
H.323 route to the MCU priority 48, then SIP calls will be routed using the SIP neighbor zone, and only 
if that were to fail would Cisco VCS try to interwork the call to H.323. Similarly H.323 calls will be 
routed to the H.323 registration in preference to being interworked to SIP. 

Note: To support both SIP and H.323 conferencing the MCU must be running version 3 or later 
software. 

The Multiway™ Conference Factory functionality is SIP based. To allow H.323 endpoints to initiate a 
Multiway™ conference: 
1. Go 

to 

VCS configuration > Protocols > Interworking 

2. Set 

H.323 <-> SIP interworking mode to RegisteredOnly (or On is also acceptable). 

No special configuration is required beyond that of setting up the Cisco VCS to work with a SIP MCU. 
 

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

Page 9 of 25