Registration Control; About Registrations; Finding A Vcs With Which To Register; Registrations On A Vcs Expressway - Cisco TelePresence Video Communication Server Administrator's Manual

Registration control

This section provides information about the pages that appear under the
Registration menu.
It includes the following information:
an overview of the VCS's registration policies
n
how to control registrations using
n

About registrations

For an endpoint to use the VCS as its H.323 gatekeeper or SIP registrar, the endpoint must first
register with the VCS. The VCS can be configured to control which devices are allowed to register
with it by using the following mechanisms:
a device authentication
n
a registration restriction policy
n
directory service or an external policy service to specify which aliases can and cannot register with
the VCS
restrictions based on IP addresses and subnet ranges through the specification of subzone
n
membership rules and
You can use these mechanisms together. For example, you can use authentication to verify an
endpoint's identity from a corporate directory, and registration restriction to control which of those
authenticated endpoints may register with a particular VCS.
For specific information about how registrations are managed across peers in a cluster, see the
Sharing registrations across peers

Finding a VCS with which to register

Before an endpoint can register with a VCS, it must determine which VCS it can or should be
registering with. This setting is configured on the endpoint, and the process is different for
H.323.

Registrations on a VCS Expressway

If a traversal-enabled endpoint registers directly with a VCS Expressway, the VCS Expressway will
provide the same services to that endpoint as a VCS Control, with the addition of firewall traversal.
Traversal-enabled endpoints include all Cisco TelePresence Expressway™ endpoints and third-party
endpoints which support the ITU H.460.18 and H.460.19 standards.
Endpoints that are not traversal-enabled can still register with a VCS Expressway, but they may not
be able to make or receive calls through the firewall successfully. This will depend on a number of
factors:
whether the endpoint is using SIP or H.323
n
the endpoint's position in relation to the firewall
n
whether there is a NAT in use
n
whether the endpoint is using a public IP address
n
For example, if an endpoint is behind a NAT or firewall, it may not be able to receive incoming calls and
may not be able to receive media for calls it has initiated. SIP endpoints can also work behind a NAT
but can only receive video if they send it as well.
To ensure firewall traversal will work successfully for H.323 endpoints behind a NAT, the endpoint
must be traversal-enabled.
Cisco VCS Administrator Guide (X6.1)
Allow Lists and Deny Lists
process based on the username and password supplied by the endpoint
that uses either Allow Lists or Deny
subzone registration policies
section.
Registration control
VCS configuration >
Lists, the VCS's on-box
SIP and
Page 64 of 401