D 14049.01
07.2007 39
TANDBERG VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
Text goes here
Introduction Getting
Started
System
Overview
System
Configuration
H.323 & SIP
Configuration
Registration
Control
Zones and
Neighbors
Call
Processing
Firewall
Traversal
Bandwidth
Control Maintenance Appe ndices
TANDBERG VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
Registration
Control
Endpoint Registration
In order for an endpoint to use the TAND BERG VCS, the
endpoint must first register w ith the VCS. The VCS can be
configured to control which d evices are allowed to register wit h
it. Two separate mechanisms are prov ided:
an authentication proces s based on the username and
password supplied by the endpo int
a simple Registration Restric tion Policy that uses Allow
Lists or Deny Lists to specify w hich aliases can and cannot
register with the VCS.
It is possible to use both mechanis ms together. For example,
you can use authentication to ver ify an endpoint’s identit y from
a corporate directory, and re gistration restriction to c ontrol
which of those authenticated e ndpoints may register with a
particular VCS.
This section gives an overvi ew of how endpoints and other
devices register with the VCS, an d then describes the two
mechanisms by which registra tions can be restricted.
•
•
Registration Control
Registration OverviewMCU, Gateway and Content Server Registration
H.323 systems such as gateways, MCUs and C ontent Servers
can also register with a VCS. They are k nown as locally
registered services. Th ese systems are configured wit h their
own prefix, which they provi de to the VCS when registering. T he
VCS will then know to route all calls that b egin with that prefix
to the gateway, MCU or Content Server a s appropriate. These
prefixes can also be used to contr ol registrations.
SIP devices cannot register p refixes. If your dial plan dicta tes
that a SIP device should be reac hed via a particular pref ix, then
you should add the device as a neig hbor zone with a pattern
match equal to the prefix to be use d.
Registrations on a VCS Border Controller
If a traversal-enabl ed endpoint registers direc tly with
a VCS Border Controller, the VCS Bord er Controller will
provide VCS services to tha t endpoint in addition to firew all
traversal. Traversal-en abled endpoints include all TAND BERG
Expressway™ endpoints and t hird party endpoints w hich
support the ITU H.460.18 and H.46 0.19 standards.
Endpoints that are not travers al-enabled can still r egister with a
VCS Border Controller, but they may no t be able to make and/or
receive calls through the fir ewall successfully. This will depe nd
on a number of factors:
whether the endpoint is using SI P or H.323
the endpoint’s position in relatio n to the firewall
whether there is a NAT in use
whether the endpoint is using a pu blic IP address
For example, if an endpoint is behind a N AT and/or firewall. it
may not be able to receive incomin g calls and may not be able
to receive media for calls they have in itiated.
•
•
•
•