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 15 of 35
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
template: 55577001%%@example.com, VCS 2 would have a template
55577002%%@example.com.
ID could be used, such as 001 for the first VCS, 002 for the second. Thus VCS 1 would have a
template: 55577001%%@example.com, VCS 2 would have a template
55577002%%@example.com.
Cisco VCS configuration: in a network of VCSs
If the VCS is in a network with other VCSs, one or more VCSs may have Conference Factory enabled.
Each 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 VCS that has
Conference Factory enabled must have a unique template. Use a unique VCS ID after the
<Conference prefix> to ensure that conference IDs are unique for each VCS.
must generate a unique ad hoc conference ID. Therefore, just as with clusters, every VCS that has
Conference Factory enabled must have a unique template. Use a unique VCS ID after the
<Conference prefix> to ensure that conference IDs are unique for each VCS.
Cisco VCS configuration: with OCS/Lync
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”.
OCS R2/Lync
Multiway is supported with OCS R2/Lync.
F8.1 or later must be used for MXP endpoints.
Version TE1.0.1 or later must be used for E20 endpoints.
Note that:
If there is no camera attached to MOC/Lync, E20 may not connect a call to that MOC/Lync as it
needs to see video traffic to complete the connection.
needs to see video traffic to complete the connection.
OCS/Lync must have a static domain route to allow OCS/Lync to be able to route calls to the
Multiway MCU’s domain (the domain specified in the Conference Factory’s Template). OCS/Lync
needs to be able to route calls to the MCU’s domain to allow OCS/Lync to make a call to the ad
hoc conference that is defined in the REFER which is initiated when “Merge” is pressed.
Multiway MCU’s domain (the domain specified in the Conference Factory’s Template). OCS/Lync
needs to be able to route calls to the MCU’s domain to allow OCS/Lync to make a call to the ad
hoc conference that is defined in the REFER which is initiated when “Merge” is pressed.
For further details see Microsoft Lync 2010 and Cisco VCS Deployment Guide.