Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
■
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.
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 restriction
policy. This means that, after the list has been activated, all SIP registrations will disappear at the end of their
registration timeout period.
policy. This means that, after the list has been activated, all SIP registrations will disappear at the end of their
registration timeout period.
Note:
By reducing the registration time to live too much, you risk flooding the VCS with registration requests, which
will severely impact performance. This impact is proportional to the number of endpoints, so you should balance the
need for occasional quick failover against the need for continuous good performance.
need for occasional quick failover against the need for continuous good performance.
About Allow and Deny Lists
When an endpoint attempts to register with the VCS it presents a list of aliases. One of the methods provided by the
VCS to control which endpoints are allowed to register is to set the Restriction policy (on the
VCS to control which endpoints are allowed to register is to set the Restriction policy (on the
page) to Allow List or Deny List and then to include any one of the
endpoint’s aliases on the Allow List or the Deny List as appropriate. Each list can contain up to 2,500 entries.
When an endpoint attempts to register, each of its aliases is compared with the patterns in the relevant list to see if it
matches. Only one of the aliases needs to appear in the Allow List or the Deny List for the registration to be allowed or
denied.
matches. Only one of the aliases needs to appear in the Allow List or the Deny List for the registration to be allowed or
denied.
For example, if the Restriction policy is set to Deny List and an endpoint attempts to register using three aliases, one
of which matches a pattern on the Deny List, that endpoint’s registration will be denied. Likewise, if the Restriction
policy is set to Allow List, only one of the endpoint’s aliases needs to match a pattern on the Allow List for it to be
allowed to register using all its aliases.
of which matches a pattern on the Deny List, that endpoint’s registration will be denied. Likewise, if the Restriction
policy is set to Allow List, only one of the endpoint’s aliases needs to match a pattern on the Allow List for it to be
allowed to register using all its aliases.
Allow Lists and Deny Lists are mutually exclusive: only one may be in use at any given time. You can also control
registrations at the
registrations at the
level. Each subzone's registration policy can be configured to allow or deny registrations
assigned to it via the subzone membership rules.
Configuring the Registration Allow List
The Registration Allow List page (Configuration > Registration > Allow List) shows the endpoint aliases and alias
patterns that are allowed to register with the VCS. Only one of an endpoint's aliases needs to match an entry in the
Allow List for the registration to be allowed.
patterns that are allowed to register with the VCS. Only one of an endpoint's aliases needs to match an entry in the
Allow List for the registration to be allowed.
page.
The configurable options are:
Field
Description
Usage tips
Description An optional free-form description
of the entry.
103
Cisco TelePresence Video Communication Server Administrator Guide