Cisco Cisco TelePresence Video Communication Server Expressway
Cisco Multiway without Conductor
Cisco VCS Deployment Guide: Multiway™ (Cisco VCS X7)
Page 11 of 35
Prerequisites for system configuration
the Cisco VCS must be running X5 or later code
The MCU must be running code version 3.1 or later
Before configuring the Cisco VCS Control and the MCU, ensure that:
you can access the VCS via a web browser
the VCS is configured such that calls between video endpoints can be made
Cisco VCS configuration
To configure Multiway on the Cisco VCS:
Go to
Applications > Conference Factory
and configure the fields as follows:
Mode
On
Alias
URI of this Conference Factory
(this is the Multiway™ ID that is configured into endpoints, that they call to initiate a
Multiway™ conference)
(this is the Multiway™ ID that is configured into endpoints, that they call to initiate a
Multiway™ conference)
Template
A template for a URI that will route calls to an MCU ad hoc conference.
It typically takes the form:
<MCU service prefix><Conference prefix>%%@MCU.domain
for example 55577%%@example.com
where %% is replaced by an incrementing number, 1, 2, .., 9, 10, 11, .., 99, 100..65535 etc
each time Conference Factory is called. Note that the %% represents a fixed number of
digits – with leading zeroes where required – based upon the length of the Number range
end limit.
It typically takes the form:
<MCU service prefix><Conference prefix>%%@MCU.domain
for example 55577%%@example.com
where %% is replaced by an incrementing number, 1, 2, .., 9, 10, 11, .., 99, 100..65535 etc
each time Conference Factory is called. Note that the %% represents a fixed number of
digits – with leading zeroes where required – based upon the length of the Number range
end limit.
Number
range start
and end
range start
and end
You are recommended to leave these settings as their default values.
These settings control the first and last numbers of the range used to replace %% in the
Template. The maximum range is 1 to 65535. When the last value in the range has been
used the system will loop round and start again at the first value in the range.
These settings control the first and last numbers of the range used to replace %% in the
Template. The maximum range is 1 to 65535. When the last value in the range has been
used the system will loop round and start again at the first value in the range.
The Conference Factory Alias will be registered as a SIP registration on the Cisco VCS, so must not
match any other registered devices.
match any other registered devices.
Note that:
The Conference Factory Alias must be a SIP URI that is routable to this Cisco VCS by every
endpoint that wants to initiate a Multiway conference.
endpoint that wants to initiate a Multiway conference.
The Conference Factory Alias will be registered to the Cisco VCS.
The Conference Factory Template must result in a SIP URI that is routable by every endpoint that
may be asked to join a conference – whether it is a SIP device or an H.323 device.
In an integrated environment where IP PBXs may be requested to join a conference, these IP
PBXs must be able to route calls to this URI.
may be asked to join a conference – whether it is a SIP device or an H.323 device.
In an integrated environment where IP PBXs may be requested to join a conference, these IP
PBXs must be able to route calls to this URI.
If the Template is creating a URI that will be routed to an H.323 MCU, typically the name part of
the URI (name@domain) must produce a numeric only ID, as H.323 MCUs typically only support
E.164 dialing.
the URI (name@domain) must produce a numeric only ID, as H.323 MCUs typically only support
E.164 dialing.
If calls are to be made to an MCU that supports SIP, 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.
prefix>%%@MCU.domain … make sure that <Conference prefix> is unique for SIP calls, so that
it does not match other dialable SIP destinations.
Make sure that the Template cannot generate URIs which match existing endpoint URIs or other
Multiway conference URIs – otherwise calls may end up ringing endpoints or joining another
conference.
Multiway conference URIs – otherwise calls may end up ringing endpoints or joining another
conference.