52
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
System configuration
The
IP
page allows you to configure the IP
protocols and settings of the VCS.
To go to the
IP
page
System configuration > IP
•
To configure these settings using the CLI:
xConfiguration I
•
P
xConfiguration IPProtoco
•
l
xConfiguration Etherne
•
t
You must save your changes and restart
the system for changes to take effect.
About IP protocols
You can configure the VCS to use
IPv4
,
IPv6
or
Both
protocols. The default is
Both
.
IPv4:
The VCS will only accept registrations
from endpoints using an IPv4 address, and
will only take calls between two endpoints
communicating via IPv4. It will communicate
with other systems via IPv4 only.
IPv6:
The VCS will only accept registrations
from endpoints using an IPv6 address, and
will only take calls between two endpoints
communicating via IPv6. It will communicate
with other systems via IPv6 only.
Both:
The VCS will accept registrations from
endpoints using either an IPv4 or IPv6 address,
and will take calls using either protocol. If a
call is between an IPv4-only and an IPv6-only
endpoint, the VCS will act as an IPv4 to IPv6
gateway. It can communicate with other systems
via either protocol.
Some endpoints support both IPv4 and
IPv6, however an endpoint can use only
one protocol when registering with the
VCS. Whether the endpoint uses IPv4 or IPv6
will be determined by the IP addressing scheme
used on the endpoint to specify the IP address
of the VCS. Once the endpoint has registered
using either IPv4 or IPv6, the VCS will only send
calls to it using this addressing scheme. Calls
made to that endpoint from another device
using the other addressing scheme will be
converted (gatewayed) by the VCS.
About IPv4 to IPv6 gatewaying
The VCS can act as a gateway for calls between
IPv4 and IPv6 devices. To enable this feature,
select an
IP protocol
of
Both.
Calls for which the VCS is acting as an
IPv4 to IPv6 gateway are traversal calls.
They will therefore require a traversal
call licence.
About LAN configuration
LAN 1 is the primary network port on the VCS.
You can configure the
IPv4 address
and
subnet
mask,
and
IPv6 address
for this port. For VCS
Expressway boxes behind a static NAT, you can
also configure the NAT's IP address.
In addition, if you have the Dual Network
Interface option key installed, you will also be
able to configure these options for the LAN 2
port.
If you have Dual Network Interfaces
enabled but only wish to configure one of
the ethernet ports, you must use LAN 1.
The VCS is shipped with a default IP
address of 192.168.0.100 (for both LAN
ports). This allows you to connect the
VCS to your network and access it via the
default address so that you can configure it
remotely.
You should configure the LAN 1 port and
restart the VCS before configuring the
LAN 2 port.
About Dual Network Interfaces
The Dual Network Interface option key enables
the LAN 2 port on the VCS Expressway for both
management and call signaling. This allows you
to have a second IP address for your VCS.
This configuration is intended for high-security
deployments where the VCS is located in a DMZ
between two separate firewalls on separate
network segments. In such deployments,
routers prevent devices on the internal network
from being able to route IP traffic to the public
internet, and instead the traffic must pass
through an application proxy such as the VCS.
To enable this feature you must purchase and
install the appropriate option key. Contact your
TANDBERG representative for information.
You should configure the LAN 1 port and
restart the VCS before configuring the
LAN 2 port.
If you have Dual Network Interfaces
enabled but only wish to configure one of
the ethernet ports, you must use LAN 1.
About static NAT
It is possible to deploy a VCS Expressway
behind a static NAT device, allowing it to have
separate public and private IP addresses. This
feature is intended for use in deployments
where the VCS Expressway is located in a DMZ,
and has the Dual Network Interfaces feature
enabled (see the previous section
About Dual
Network Interfaces
).
In these deployments, the externally-facing
LAN port has static NAT enabled in order to
use both a private and public IPv4 address; the
internally facing LAN port does not have static
NAT enabled and uses a single IPv4 (or IPv6)
address.
In such a deployment, when configuring
traversal clients to use the VCS Expressway as
a traversal server, it is the latter internally-facing
IP address of the VCS Expressway that should
be used.
To enable the use of a static NAT:
ensure that the Dual Network Interfaces
•
option key is installed
on the
•
IP
page (
System Configuration > IP
),
for the externally-facing LAN port:
in the
•
IPv4 address
field, enter the VCS
Expressway's private IP address
select an
•
IPv4 static NAT mode
of
On
in the
•
IPv4 static NAT
field, enter the VCS
Expressway's public IP address - this is the
IP address of the outside of the NAT.
The static NAT configuration options are
only available on VCS Expressway
systems which have the Dual Network
Interfaces option key installed.
About IP routes (static routes)
The options on the
IP
page allow you to set the
default IPv4 and IPv6 gateways used by the
VCS. This is the gateway to which IP requests
are sent for IP addresses that do not fall within
the VCS’s local subnet. However, you can also
configure additional IP routing information (static
routes) on the VCS. This is sometimes required
when using the Dual Network Interfaces option
and occasionally required in other complex
network deployments. You can configure routes
for up to 50 networks and host combinations.
IP routes are configured using the CLI only
using:
xConfiguration IP Route
•
xCommand RouteAd
•
d
IP
