136
D14049.07
March 2010
Grey Headline
(continued)
TANDBERG
VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
Introduction
Overview and
status
System
configuration
VCS
configuration
Zones and
neighbors
Clustering and
peers
Call
processing
Bandwidth
control
Firewall
traversal
Appendices
Applications
Maintenance
Configuring the VCS as a traversal server
Overview
The VCS Expressway can act as a firewall
traversal server. This feature means you can:
•
Allow your VCS to act as a traversal server
for other VCSs and TANDBERG Gatekeepers.
You do this by adding a new traversal server
zone on the VCS, and configuring it with
details of the traversal client.
•
Provide firewall traversal for any traversal-
enabled endpoints (i.e. TANDBERG MXP
endpoints and any other endpoints that
support the ITU H.460.18 and H.460.19
standards) registered directly with it. You
can configure the protocols and ports that
will be used.
•
Enable and configure TURN services.
•
Configure the ports used specifically for
firewall traversal services.
The following sections describe how to
configure each of the above options.
To enable your VCS Expressway to act as a
traversal server for a traversal client (e.g. a
TANDBERG VCS Control or Gatekeeper) you
must create a connection between it and the
client system.
You do this by adding a new traversal server
zone on the VCS server and configuring it with
the details of the traversal client.
To add a new traversal server zone:
•
VCS configuration > Zones
.
You are taken to the
Zones
page.
Click
New
.
You are taken to the
Create zone
page.
•
xCommand ZoneAdd
To edit an existing traversal server zone:
•
VCS configuration > Zones
.
You are taken to the
Zones
page.
Click on the name of the zone you want to
configure.
You are taken to the
Edit zone
page.
•
xConfiguration Zones Zone
•
xConfiguration Zones Zone [1..1000]
TraversalServer
For details on the configuration options
available for traversal server zones, see the
Configuring traversal server zones
section.
Adding and configuring a traversal
server zone
Configuring traversal for endpoints
Overview
Traversal-enabled H.323 endpoints can register
directly with the VCS Expressway and use it for
firewall traversal.
To configure the options for these endpoints:
•
VCS configuration > Expressway> Locally
registered endpoints
You are taken to the
Locally registered
endpoints
page.
•
xConfiguration Zones LocalZone
Traversal H323
The options available are:
H.323 Assent mode
Determines whether or not H.323 calls using
Assent mode for firewall traversal are allowed.
H.460.18 mode
Determines whether or not H.323 calls using
H.460.18/19 mode for firewall traversal are
allowed.
H.460.19 demux mode
Determines whether the VCS Expressway
operates in demultiplexing mode for calls from
locally registered endpoints.
On
: allows use of the same two ports for all
calls.
Off
: each call will use a separate pair of ports
for media.
H.323 preference
If an endpoint supports both Assent and
H.460.18 protocols, this setting determines
which the VCS Expressway uses.
UDP probe retry interval
Sets the frequency (in seconds) with which
locally registered endpoints send a UDP probe
to the VCS Expressway.
UDP probe retry count
Sets the number of times locally registered
endpoints attempt to send a UDP probe to the
VCS Expressway.
UDP probe keep alive interval
Sets the interval (in seconds) with which locally
registered endpoints send a UDP probe to the
VCS Expressway after a call is established, in
order to keep the firewall’s NAT bindings open.
TCP probe retry interval
Sets the frequency (in seconds) with which
locally registered endpoints send a TCP probe
to the VCS Expressway.
TCP probe retry count
Sets the number of times locally registered
endpoints attempt to send a TCP probe to the
VCS Expressway.
TCP probe keep alive interval
Sets the interval (in seconds) with which locally
registered endpoints send a TCP probe to the
VCS Expressway after a call is established, in
order to keep the firewall’s NAT bindings open.
