143
D14049.05
February 2009
Grey Headline
(continued)
TANDBERG
VIDEO COMMUNICATIONS SERVER
ADMINISTRATOR GUIDE
Introduction
Getting started
Overview and
status
System
configuration
VCS
configuration
Zones and
neighbors
Call
processing
Bandwidth
control
Firewall
traversal
Appendices
Applications
Maintenance
Conference Factory
Overview
Configuration
The Conference Factory application allows the VCS to support TANDBERG's Multiway™ feature.
Multiway enables endpoint users to create a conference while in a call even if their endpoint does
not have this functionality built in. Multiway is supported in TANDBERG endpoints including the E20
(software version TE1.0 and later) and MXP range (software version F8.0 and later).
Check with your TANDBERG representative for an up-to-date list of the TANDBERG endpoints and
infrastructure products that support Multiway.
Process
When the Multiway feature is activated from the endpoint:
The endpoint calls a pre-configured alias which routes to the Conference Factory on the VCS.
1.
The VCS replies to the endpoint with the alias that the endpoint should use for the Multiway
2.
conference. This alias will route to an MCU.
The endpoint then places the call to the MCU using the given alias, and informs the other
3.
participating endpoints to do the same.
Refer to the
TANDBERG Multiway Deployment Guide [25]
for full details on how to configure
individual components of your network (endpoints, MCUs and VCSs) in order to use Multiway
in your deployment.
The Conference Factory application is enabled and configured using the
Conference Factory
page
(
Applications > Conference Factory
).
Mode
The
Mode
option allows you to enable or disable the Conference Factory application.
Alias
The alias that will be dialed by the endpoints when the Multiway feature is activated. This must
also be configured on all endpoints that may be used to initiate the Multiway feature. An example
could be
.
Template
The alias that the VCS will tell the endpoint to dial in order to create a Multiway conference on the
MCU. You can use
%%
as a part of the template, in which case the
%%
will be replaced by a unique
number (starting from 1 and incrementing by 1) each time the VCS receives a new conference
request. An example could be
563%%@example.com
. (Note that the number of digits generated by
the
%%
will increase as the number increments, e.g. from 9 to 10 and from 99 to 100.)
You must use a different
Template
on each VCS in your network that has the Conference
Factory feature enabled. If your VCS is part of a cluster, the
Template
must be different for
each peer in the cluster.
The alias generated by the
Template
must be a fully-qualified SIP alias and must route to
the MCU. The MCU must be configured to process this alias. No other special
configuration is required on the MCU in order to support the Conference Factory application.
SIP mode
must be set to
On
(
VCS configuration > Protocols > SIP > Configuration
) in order
for the Conference Factory application to function. If you wish to be able to initiate calls to
the Conference Factory from H.323 endpoints, you must also set
H.323 mode
to
On
(
VCS
configuration > Protocols > H.323
), and ensure that
H.323 <-> SIP interworking mode
is set to
RegisteredOnly
or
On
(
VCS configuration > Protocols > Interworking
).
