103
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
Routing calls via the Advanced Media Gateway
VCS and the Advanced Media Gateway
Overview
The TANDBERG Advanced Media Gateway (AM gateway) provides support for transcoding between
standard codecs (such as H.264) and Microsoft RT Video to allow high definition calls between
Microsoft Office Communicator (MOC) clients and TANDBERG endpoints.
Configuring the VCS to use the AM gateway
A VCS Control can be configured to route calls to or from a Microsoft Office Communications Server
(OCS) zone via the AM gateway.
To use the AM gateway you must first configure at least two zones:
•
An OCS zone (a zone with a
Zone profile
set to
Microsoft Office Communications Server 2007
).
•
An AM gateway zone (a zone with a
Zone profile
set to
TANDBERG Advanced Media Gateway
).
Note that an AM gateway zone can be configured with up to six AM gateway peers for load
balancing purposes. Also, AM gateway zones do not require any associated search rules.
To start using the AM gateway to transcode calls:
1. Go to the
Advanced Media Gateway configuration
page (
VCS configuration > Advanced Media
Gateway > Configuration
).
2. Choose the required AM gateway zone from the
Advanced Media Gateway zone
drop-down. Note
that only zones configured with a
Zone profile
of
TANDBERG Advanced Media Gateway
appear
in this list. After a zone is selected, calls to or from the OCS are routed via the AM gateways
connected to that zone.
By default, all OCS calls are routed via the AM gateway but if you want to control which calls
go through the AM gateway you have to set up policy rules. To do this, set
Policy mode
to
On
and then follow the related task link to
Configure Advanced Media Gateway policy rules
.
To configure the required AM gateway zone using the CLI:
•
xConfiguration Services AdvancedMediaGateway Zone Name
For more information on configuring VCS and OCS, refer to the
Microsoft OCS 2007 (R1 and
R2) and VCS Control Deployment Guide [24]
.
Usage features and limitations
•
If the AM gateway reaches its capacity, any calls that would normally route via the AM gateway
will not fail; the call will still connect as usual but will not be transcoded.
•
The OCS zone must be inside any firewall; the TANDBERG endpoint receiving or making the call
can be outside the firewall.
•
The VCS shows calls routed via the AM gateway as two calls: one from the endpoint via the VCS
to the AM gateway which will be a local or traversal call as appropriate, and then a separate call
back from the AM gateway via the VCS to the OCS which will always be a local call.
•
Bandwidth controls can be applied to the leg of the call between the TANDBERG endpoint and the
AM gateway zone, but cannot be applied to the AM gateway zone to OCS zone leg of the call.
Controlling which calls to route via the AM gateway
By default, when an
Advanced Media Gateway zone
has been selected, all OCS calls are routed via
the AM gateway.
If you want to control which calls go through the AM gateway you have to set up policy rules. To do
this:
1. Go to the
Advanced Media Gateway configuration
page (
VCS configuration > Advanced Media
Gateway > Configuration
).
2. Set
Policy mode
to
On
and click
Save
.
3. You now need to
configure your policy rules
.
Either follow the related task link to
Configure Advanced Media Gateway policy rules
or go to
VCS configuration > Advanced Media Gateway > Policy rules
.
To enable AM gateway policy using the CLI:
•
xConfiguration Services AdvancedMediaGateway Policy Mode