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 14 of 35
Mode
Alias pattern match
Pattern type
Regex
Pattern string
<MCU service prefix>(<Conference prefix>\d+@MCU.domain)(:.*)?
e.g. 555(77\d+@example.com)(:.*)?
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:
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.
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
(48 in this example) as the priority for the Local Zone search rule that takes the received conference
URI and converts it to an E164 number.
(48 in this example) as the priority for the Local Zone search rule that takes the received conference
URI and converts it to an E164 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.
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.
To support both SIP and H.323 conferencing, the MCU must be running version 3 or later software.
Cisco VCS with H.323 endpoints initiating a Multiway conference
The Multiway Conference Factory functionality is SIP based. To allow H.323 endpoints to initiate a
Multiway conference:
Multiway conference:
1. Go to
VCS configuration > Protocols > Interworking
.
2. Set H.323 <-> SIP interworking mode to Registered only (or On is also acceptable).
SIP endpoints with SIP MCU
No special configuration is required beyond that of setting up the Cisco VCS to work with a SIP MCU.
SIP endpoints with H.323 MCU
An H.323 MCU registers with E164 service prefixes, therefore, for a SIP call to be placed onto an
H.323 MCU, the dialed URI must be converted to an E.164 number and the leading digits of that
number must match the service prefix. This is carried out using the local zone match and transform
defined in the “Cisco VCS and H.323 MCU” section above.
H.323 MCU, the dialed URI must be converted to an E.164 number and the leading digits of that
number must match the service prefix. This is carried out using the local zone match and transform
defined in the “Cisco VCS and H.323 MCU” section above.
To enable the Cisco VCS to perform the SIP to H.323 interworking:
1. Go to
VCS configuration > Protocols > Interworking
.
2. Set H.323 <-> SIP interworking mode to Registered only (or On is also acceptable).