Cisco Cisco TelePresence Video Communication Server Expressway
Cisco VCS configuration
Cisco VCS Deployment Guide: Multiway™ (Cisco VCS X7)
Page 12 of 30
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%%@mycompany.com, VCS 2 would have a template
55577002%%@maycompany.com.
ID could be used, such as 001 for the first 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 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
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
Multiway is supported with OCS R2.
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, E20 may not connect a call to that MOC as it needs to see
video traffic to complete the connection.
video traffic to complete the connection.
OCS must have a static domain route to allow OCS to be able to route calls to the Multiway™
MCU’s domain (the domain specified in the Conference Factory’s Template). OCS needs to be
able to route calls to the MCU’s domain to allow OCS to make a call to the ad hoc conference that
is defined in the REFER which is initiated when “Join” is pressed.
MCU’s domain (the domain specified in the Conference Factory’s Template). OCS needs to be
able to route calls to the MCU’s domain to allow OCS to make a call to the ad hoc conference that
is defined in the REFER which is initiated when “Join” is pressed.
For further details about configuration with OCS, see Microsoft OCS 2007 and Cisco VCS Deployment
Guide.
Guide.
Cisco VCS configuration: with CUCM
For details about the configuration needed in CUCM to support Multiway, see the “Cisco
TelePresence Multiway and CUCM” appendix in the Cisco VCS and Cisco Unified Communications
Manager Deployment Guide CUCM 6.1, 7, 8 and X7.0.
TelePresence Multiway and CUCM” appendix in the Cisco VCS and Cisco Unified Communications
Manager Deployment Guide CUCM 6.1, 7, 8 and X7.0.
Note that the CUCM must be configured to allow dialing to the Cisco VCS domain to which Multiway
aliases are registered – this is documented in the “Allow dialing to Cisco VCS domain from Cisco
phones” appendix in the same deployment guide.
aliases are registered – this is documented in the “Allow dialing to Cisco VCS domain from Cisco
phones” appendix in the same deployment guide.