Cisco Cisco TelePresence Video Communication Server Expressway
Cisco Multiway without Conductor
Cisco VCS Deployment Guide: Multiway™ (Cisco VCS X7)
Page 15 of 35
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).
H.323 endpoints with H.323 MCU
No special configuration is required beyond that of setting up the Cisco VCS to work with an H.323
MCU, and setting up the configuration for “Cisco VCS with H.323 endpoints initiating a Multiway
conference”.
MCU, and setting up the configuration for “Cisco VCS with H.323 endpoints initiating a Multiway
conference”.
H.323 endpoints with SIP MCU
No special configuration is required beyond that of setting up the Cisco VCS to work with a SIP MCU,
and setting up the configuration for “Cisco VCS with H.323 endpoints initiating a Multiway conference”.
and setting up the configuration for “Cisco VCS with H.323 endpoints initiating a Multiway conference”.
Cisco VCS configuration: in a cluster
If the VCS is in a cluster, each VCS in the cluster will be configured with the same alias, but, each
template must be unique.
template must be unique.
The %% value is not shared between cluster peers, so each peer must generate a unique ad hoc
conference ID (so that if conferences are set up by different VCS peers, they cannot issue the same
conference ID). This is most easily done by adding a VCS ID between the <Conference prefix> and
the %%.
conference ID (so that if conferences are set up by different VCS peers, they cannot issue the same
conference ID). This is most easily done by adding a VCS ID between the <Conference prefix> and
the %%.
For example, if the <MCU service prefix> is 555 and <Conference prefix> is 77, then a 3 digit VCS
ID could be used, such as 001 for the first VCS, 002 for the second. Thus VCS 1 would have a
ID could be used, such as 001 for the first VCS, 002 for the second. Thus VCS 1 would have a