This topic describes the functions of zones in the Cisco TelePresence Video Communication Server (VCS).
Cisco VCS uses a zone concept for CAC and registration policies:
- Default zone
- Local zone
- Default subzone
- Traversal subzone
Each subzone can have different CAC parameters:
Cisco VCS uses a zone concept for CAC and registration policies.
By default, a local zone contains one default subzone and one traversal subzone, and it may have user-defined subzones. No devices can register directly to a local zone. They must register to the subordinate default subzone or to a user-defined subzone.
Endpoints that do not match the criteria of a user-defined subzone register in the default subzone when they are not denied by the registration Restriction Policy setting.
A subzone is a logical collection of devices, such as endpoints, multipoint control units, and gateways. When a device registers with Cisco VCS, it is assigned to a specific subzone based on its IP address or pattern match. If there is no match, then the endpoints register to the default subzone. Each subzone can have a bandwidth restriction for calls within the subzone.
Each subzone can have CAC limits configured. These limits apply to calls within the zone and they are configured as follows:
- Within: This parameter defines the maximum allowed bandwidth of all calls within the subzone. If two devices are registered to the same subzone, the call between these two devices is classified as a call within the subzone.
- In&Out: This parameter defines the maximum allowed bandwidth of all calls that are established out of and into a subzone. If one device of a call is registered in the subzone and the other device is not registered in the same subzone, then the In&Out limit of the subzone applies to the call.
- Total: This parameter defines the maximum allowed bandwidth of all calls that involve a subzone: calls within the subzone and calls that involve one device within the subzone and one device that is located outside the subzone.
Local Zone Example
The figure shows an example of a local zone.
In the figure, the local zone represents the superior zone that by default contains one default subzone and one traversal subzone. In addition, the local zone includes user-defined subzones (NY, SL, and SJ). Endpoints register to the subzones based on their suffix, prefix, or IP address. The figure also shows an endpoint that does not match any configured subzone matching criteria. This endpoint is associated with the default subzone.
The matching criteria that can be configured are IP addresses, suffix patterns, prefix patterns, and subnet masks.