Table of Contents
Advertisement
Grey Headline (continued)
Registration control
About alias registration
Once the
authentication
process (if required) has been
completed, the endpoint will then attempt to register its alias(es)
with the VCS.
H.323
When registering, the H.323 endpoint presents the VCS with one
or more of the following:
•
one or more H.323 IDs
•
one or more E.164 aliases
•
one or more URIs.
Users of other registered endpoints can then call the endpoint
by dialing any of these aliases.
We recommended that you register your H.323 endpoints
using a URI. This facilitates interworking between SIP
and H.323, as SIP endpoints register using a URI as
standard.
We recommended that you do not use aliases that reveal
sensitive information. Due to the nature of H.323, call
setup information is exchanged in an unencrypted form.
SIP
When registering, the SIP endpoint presents the VCS with its
contact address (IP address) and logical address (Address of
Record). The logical address is considered to be its alias, and
will generally be in the form of a URI.
Overview and
Introduction
Getting started
status
D14049.05
February 2009
Registering aliases
Attempts to register using an existing alias
An endpoint may attempt to register with the VCS using an alias that is already registered to the system. How this is managed
depends on how the VCS is configured and whether the endpoint is SIP or H.323.
H.323
An H.323 endpoint may attempt to register with the VCS using an alias that has already been registered on the VCS from another IP
address. The reasons for this could include:
•
two endpoints at different IP addresses are attempting to register using the same alias
•
a single endpoint has previously registered using a particular alias. The IP address allocated to the endpoint, or the port the
endpoint uses to communicate with the VCS, then changes, and the endpoint is attempting to re-register using the same alias.
You can determine how the VCS will behave in this situation by configuring the
•
VCS configuration > Protocols > H.323
You will be taken to the
xConfiguration H323 Gatekeeper Registration ConflictMod
•
The options are:
Reject:
The registration from the new IP address will be rejected. This is useful if your priority is to prevent two users registering with
the same alias.
Overwrite:
The existing registration will be overwritten using the new IP address. This is useful if your network is such that endpoints
are often allocated new IP addresses, because it will prevent unwanted registration rejections.
The default is Reject.
SIP
A SIP endpoint will always be allowed to register using an alias that is already in use from another IP address. When a call is received
for this alias, all endpoints registered using that alias will be called simultaneously. This SIP feature is known as "forking".
Blocking registrations
If you have
configured the VCS to use a Deny
a Name; or
Status > Registrations > by Alias
option to block the registration. This will add the all the aliases used by that endpoint to the Deny List.
System
VCS
Zones and
configuration
configuration
neighbors
H.323
page.
List, from the
Registration Details
and click an Alias; or
Status > Registration History
Call
Bandwidth
processing
control
69
TANDBERG
VIDEO COMMUNICATIONS SERVER
Registration Conflict
Mode, using either:
e
page
(Status > Registrations > by Device
and click an Alias) you will have an
Firewall
Applications
Maintenance
traversal
ADMINISTRATOR GUIDE
and click
Appendices
Advertisement
Table of Contents
