Cisco Cisco TelePresence Video Communication Server Expressway
Cisco VCS configuration
Cisco VCS Deployment Guide: Multiway™ (Cisco VCS X6)
Page 9 of 28
SIP mode
On
SIP port
5060
SIP transport
TCP (or TLS – depending on how MCU is configured)
H.323 mode
Off
Authentication
Configure the authentication settings according to your
authentication policy
authentication policy
Peer IP address
IP address of MCU
Zone profile
Default
3. Go to VCS configuration > Dial plan > Search rules.
4. Configure a search rule as follows:
Priority
48
Source
Any
Request must be
authenticated
authenticated
Configure this setting according to your authentication policy
Mode
Alias pattern match
Pattern type
Regex
Pattern string
<MCU service prefix>(<Conference prefix>\d+@MCU.domain)
e.g. 555(77\d+@mycompany.com)
e.g. 555(77\d+@mycompany.com)
Pattern behavior
Replace
Replace string
\1
On successful match
Continue
Target zone
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.
<Conference prefix>%%@MCU.domain. Make sure that <Conference prefix> is unique for SIP
calls, so that it does not match other dialable SIP destinations.
Cisco VCS and MCU supporting both H.323 and SIP
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:
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).
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.
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.
software.