Table of Contents
Advertisement
Grey Headline (continued)
Conference Factory
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 or later) and MXP range (software version F8.0 or 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:
1. The endpoint calls a pre-configured alias which routes to the Conference Factory on the VCS.
2. The VCS replies to the endpoint with the alias that the endpoint should use for the Multiway
conference. This alias will route to an MCU.
3. The endpoint then places the call to the MCU using the given alias, and informs the other
participating endpoints to do the same.
Refer to the
TANDBERG Multiway Deployment Guide [25]
individual components of your network (endpoints, MCUs and VCSs) in order to use Multiway
in your deployment.
Overview and
System
Introduction
status
configuration
D14049.07
March 2010
Overview
for full details on how to configure
VCS
Zones and
configuration
neighbors
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 multiway@example.com.
Template
The alias that the VCS tells the endpoint to dial to create a Multiway conference on the MCU.
To ensure that each conference has a different alias, you should use %% as a part of the template.
The %% will be replaced by a unique number each time the VCS receives a new conference request.
Number range start / end
The first and last numbers in the range that replaces %% in the template used to generate a
conference alias.
For example, your Template could be 563%%@example.com with a range of 10 - 999. The first
conference will use the alias 563010@example.com, the next conference will use 563011@example.
com and so on up to 563999@example.com., after which it will loop round and start again at
563010@example.com. (Note that the %% represents a fixed number of digits based upon the upper
range limit.)
You must use a different Template on each VCS in your network that has the Conference
Factory application 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) for the
Conference Factory application to function. If you want 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).
Clustering and
Call
Bandwidth
peers
processing
control
140
TANDBERG
VIDEO COMMUNICATION SERVER
Configuration
Firewall
Applications
Maintenance
traversal
ADMINISTRATOR GUIDE
Appendices
Advertisement
Table of Contents
