Grey Headline (continued)
Registration Control
TANDBERG VIDEO COMMUNICATIONS SERVER ADMINISTRATOR GUIDE
Allow and Deny Lists
About Allow and Deny Lists
When an endpoint attempts to register with the VCS it presents a list of aliases. You can control which endpoints are allowed to register by setting the Restriction Policy to AllowList or DenyList and then including 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.
For example, If the Registration Restriction policy is set to DenyList 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 Registration Restriction policy is set to AllowList, 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.
Patterns and Pattern Types
Entries on the Allow List and Deny List are a combination of Pattern and Type. The Pattern specifies the string to be matched; the Type determines whether that string;
•must match the Pattern exactly (Exact)
•must appear at the start of the alias (Prefix)
•must appear at the end of the alias (Suffix)
•is in the form of a Regular Expression (Regex).
Activating use of Allow or Deny Lists
To activate the use of Allow or Deny lists to determine which aliases are allowed to register with the VCS:
•VCS Configuration > Registration > Configuration.
You will be taken to the Registration Configuration page.
•xConfiguration Registration RestrictionPolicy
Removing existing registrations
Once an Allow List or Deny List has been activated, it will be used to control all registration requests from that point forward. However, any existing registrations will remain in place, even if the new list would otherwise block them. For
this reason we recommend that you manually remove all existing unwanted registrations after you have implemented an Allow List or Deny List.
To manually remove a registration; navigate to Status > Registrations, select the registration(s) you wish to remove, and click Unregister.
Restriction policy
Specifies the policy to be used when determining which endpoints may register with the VCS.
None: Any endpoint may register.
AllowList: Only those endpoints with an alias that matches an entry in the Allow List may register.
DenyList: All endpoints may register, unless they match an entry on the Deny List.
The default is None.
Save
Click here to save your changes.
Allow Lists and Deny Lists are mutually exclusive: only one may be in use at any given time.
Introduction | Getting Started |
| Overview and |
| System | VCS | Zones and |
| Call |
| Bandwidth |
| Firewall |
| Applications |
| Maintenance |
| Appendices |
| Status |
| Configuration | Configuration | Neighbors |
| Processing |
| Control |
| Traversal |
|
|
| |||||
|
|
|
|
|
|
|
|
|
|
|
|
| |||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
D14049.04 |
|
|
|
|
|
| 80 |
|
|
|
|
|
|
|
|
|
| ||
JULY 2008 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||
