Cisco TelePresence Administrator's Manual page 93

H.350 directory authentication and registrations
If the VCS is using an H.350 directory service to authenticate registration requests, the Source of aliases
for registration setting is used to determine which aliases the endpoint is allowed to attempt to register with.
See Using an H.350 directory service lookup via LDAP
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
n
registered on the VCS from another IP address. You can control how the VCS behaves in this situation by
configuring the Registration conflict mode, on the
H.323).
SIP: a SIP endpoint will always be allowed to register using an alias that is already in use from another IP
n
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
add all the aliases used by that endpoint to the Deny List.
Removing existing registrations
After a restriction policy has been activated, it controls all registration requests from that point forward.
However, any existing registrations may remain in place, even if the new list would otherwise block them.
Therefore, you are recommended to manually remove all existing unwanted registrations after you have
implemented a restriction policy.
To manually remove a registration, go to
want to remove, and click Unregister.
If the registered device is in an active call and its registration is removed (or expires), the effect on the call is
dependent on the protocol:
H.323: the call is taken down.
n
SIP: the call stays up by default. This SIP behavior can be changed but only via the CLI by using the
n
command xConfiguration SIP Registration Call Remove.
Re-registrations
All endpoints must periodically re-register with the VCS in order to keep their registration active. If you do not
manually delete the registration, the registration could be removed when the endpoint attempts to re-register,
but this depends on the protocol being used by the endpoint:
H.323 endpoints may use "light" re-registrations which do not contain all the aliases presented in the initial
n
registration, so the re-registration may not get filtered by the restriction policy. If this is the case, the
registration will not expire at the end of the registration timeout period and must be removed manually.
SIP re-registrations contain the same information as the initial registrations so will be filtered by the
n
restriction policy. This means that, after the list has been activated, all SIP registrations will disappear at
the end of their registration timeout period.
Cisco VCS Administrator Guide (X7.2)
for more information.
H.323 page
Deny List, you will have an option to block the registration. This will
Status > Registrations > By
Registration control
(VCS configuration > Protocols >
device, select the registrations you
Page 93 of 498