Cisco Cisco TelePresence Video Communication Server Expressway
Cisco VCS configuration
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 E164 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 E164 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
1. Go
to
VCS configuration > Protocols > Interworking.
2. Set
H.323 <-> SIP interworking mode to RegisteredOnly (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 Cisco VCS is in a cluster, each Cisco VCS in the cluster must be configured with the same alias,
but, each template must be unique.
but, each 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 Cisco 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 Cisco 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 Cisco VCS, 002 for the second. Thus VCS 1 would have a
template: 55577001%%@mycompany.com, VCS 2 would have a template
55577002%%@maycompany.com.
ID could be used, such as 001 for the first Cisco VCS, 002 for the second. Thus VCS 1 would have a
template: 55577001%%@mycompany.com, VCS 2 would have a template
55577002%%@maycompany.com.
Cisco VCS configuration: in a network of Cisco VCSs
If the Cisco VCS is in a network with other Cisco VCSs, one or more Cisco VCSs may have
Conference Factory enabled.
Conference Factory enabled.
Each Cisco VCS with Conference Factory enabled, whether it has the same or different alias
configured, must generate a unique ad hoc conference ID. Therefore, just as with clusters, every
Cisco VCS that has Conference factory enabled must have a unique template. As for clusters, using a
unique VCS ID after the <Conference prefix> can be used to ensure that conference IDs are unique
for each Cisco VCS.
configured, must generate a unique ad hoc conference ID. Therefore, just as with clusters, every
Cisco VCS that has Conference factory enabled must have a unique template. As for clusters, using a
unique VCS ID after the <Conference prefix> can be used to ensure that conference IDs are unique
for each Cisco VCS.
Cisco VCS configuration: with OCS
OCS R1
Multiway™ is not supported with OCS R1.
OCS R1 does not accept being invited to join a Multiway conference — OCS invalidly rejects the
INVITE to put it on hold before joining the conference with “421 Bad Extension – timer”.
INVITE to put it on hold before joining the conference with “421 Bad Extension – timer”.
Cisco VCS Deployment Guide: Multiway™ (Cisco VCS X5)
Page 10 of 25