Cisco Cisco TelePresence Video Communication Server Expressway
Cisco Multiway without TelePresence Conductor
Cisco TelePresence Multiway Deployment Guide (Cisco VCS X7.2 and Conductor XC2.2)
Page 15 of 41
Authentication policy
Configure the authentication settings according to your 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
Protocol
Any
Source
Any
Request must be 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+@example.com)(:.*)?
Pattern behavior
Replace
Replace string
\1
On successful match
Continue
Target zone
Zone created above, for example Multiway - SIP
Note:
n
When a SIP conference is set up, it will register <Conference prefix>%%@MCU.domain.
n
Make sure that <Conference prefix> is unique for SIP calls, so that it does not match other dialable SIP
destinations.
destinations.
VCS and MCU supporting both H.323 and SIP
Follow the processes above and set up the VCS to work with an H.323 MCU and also to work with a SIP
MCU.
MCU.
It is very important that the priority of the neighbor zone search rule for the SIP MCU is the same value (48 in
this example) as the priority for the Local Zone search rule that takes the received conference URI and
converts it to an E.164 number.
this example) as the priority for the Local Zone search rule that takes the received conference URI and
converts it to an E.164 number.
When the VCS is routing calls, at any particular match priority value, it routes the call in native protocol in
preference to interworking the call. By setting a priority of 48 for both the SIP route to the MCU and the H.323
route to the MCU, SIP calls will be routed using the SIP neighbor zone, and only if that were to fail would the
VCS try to interwork the call to H.323. Similarly H.323 calls are routed to the H.323 registration in preference
to being interworked to SIP.
preference to interworking the call. By setting a priority of 48 for both the SIP route to the MCU and the H.323
route to the MCU, SIP calls will be routed using the SIP neighbor zone, and only if that were to fail would the
VCS try to interwork the call to H.323. Similarly H.323 calls are routed to the H.323 registration in preference
to being interworked to SIP.
To support both SIP and H.323 conferencing, the MCU must be running version 3 or later software.