Field / section
Description
Registration
policy
When an endpoint registers with the VCS, its IP address and alias is checked against the
subzone membership rules and it is assigned to the appropriate subzone. If no subzones have
been created, or the endpoint’s IP address or alias does not match any of the subzone
membership rules, it is assigned to the Default Subzone.
In addition to using a
registration restriction policy
to control whether an endpoint can register
with the VCS, you can also configure a subzone's
Registration policy
as to whether it will
accept registrations assigned to it via the subzone membership rules.
This provides additional flexibility when defining your registration policy. For example you can:
n
Deny registrations based on IP address subnet. You can do this by creating a subzone with
associated membership rules based on an IP address subnet range, and then setting that
subzone to deny registrations.
n
Configure the Default Subzone to deny registrations. This would cause any registration
requests that do not match any of the subzone membership rules, and hence fall into the
Default Subzone, to be denied.
Note that registration requests have to fulfill any registration restriction policy rules before any
subzone membership and subzone registration policy rules are applied.
Authentication
policy
The
Authentication policy
setting controls how the VCS challenges incoming messages to the
Default Subzone. See
Authentication policy configuration options [p.105]
for more information.
Media
encryption
mode
The
Media encryption mode
setting controls the media encryption capabilities for SIP calls
flowing through the subzone. See
Configuring media encryption policy [p.135]
for more
information.
Note that if H.323 is enabled and the subzone has a media encryption mode of
Force encrypted
or
Force unencrypted
, any H.323 and SIP to H.323 interworked calls through this subzone will
ignore this mode.
ICE support
for media
Controls whether ICE messages are supported by the devices in this subzone.
Bandwidth
controls
When configuring your subzones you can apply bandwidth limits to:
n
individual calls between two endpoints within the subzone
n
individual calls between an endpoint within the subzone and another endpoint outside of the
subzone
n
the total of calls to or from endpoints within the subzone
See
Applying bandwidth limitations to subzones [p.228]
for information about how bandwidth
limits are set and managed.
Configuring subzone membership rules
The
Subzone membership rules
page (
Configuration > Local Zone > Subzone membership rules
) is
used to configure the rules that determine, based on the address of the device, to which
subzone
an endpoint
is assigned when it registers with the VCS.
The page lists all the subzone membership rules that have been configured on the VCS, and lets you create,
edit, delete, enable and disable rules. Rule properties include:
n
rule name and description
n
priority
Cisco VCS Administrator Guide (X8.1.1)
Page 226 of 507
Bandwidth control
About subzones