Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
Registration control
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.
address (Address of Record). The logical address is considered to be its alias, and will generally be in
the form of a URI.
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.
system. How this is managed depends on how the VCS is configured and whether the endpoint is SIP
or H.323.
n
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. You can control how the VCS behaves in this
situation by configuring the Registration conflict mode, on the
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
page (
VCS configuration >
Protocols > H.323
).
n
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”.
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
, you will have an option to block the registration.
This will 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.
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
Status > Registrations > By device
, select the
registrations you 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:
call is dependent on the protocol:
n
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 command xConfiguration SIP Registration Call Remove.
the 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:
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:
n
H.323 endpoints may use "light" re-registrations which do not contain all the aliases presented in
the initial 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.
the initial 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.
n
SIP re-registrations contain the same information as the initial registrations so will be filtered by the
restriction policy. This means that, after the list has been activated, all SIP registrations will
disappear at the end of their registration timeout period.
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 (X6.1)
Page 67 of 401