Cisco Cisco Expressway Maintenance Manual
Note that:
■
B2BUA routed calls are identified in the call history by a component type of B2BUA.
■
An RMS call license is consumed when a call goes via the encryption B2BUA.
■
) that can be routed via the B2BUA.
About the Local Zone and Subzones
The collection of all devices registered with the Expressway makes up its Local Zone.
The Local Zone is divided into subzones. These include an automatically created Default Subzone and up to 1000
manually configurable subzones.
manually configurable subzones.
When an endpoint registers with the Expressway, it is allocated to an appropriate subzone based on subzone
membership rules. These rules specify the range of IP addresses or alias pattern matches for each subzone. If an
endpoint’s IP address or alias does not match any of the membership rules, it is assigned to the Default Subzone.
membership rules. These rules specify the range of IP addresses or alias pattern matches for each subzone. If an
endpoint’s IP address or alias does not match any of the membership rules, it is assigned to the Default Subzone.
The Local Zone may be independent of network topology, and may comprise multiple network segments. The
Expressway also has two special types of subzones:
Expressway also has two special types of subzones:
■
, which is always present
■
, which is always present but only used when your Expressway is part of a cluster
Bandwidth management
The Local Zone’s subzones are used for bandwidth management. After you have set up your subzones you can apply
bandwidth limits to:
bandwidth limits to:
■
individual calls between two endpoints within the subzone
■
individual calls between an endpoint within the subzone and another endpoint outside of the subzone
■
the total of calls to or from endpoints within the subzone
For full details of how to create and configure subzones, and apply bandwidth limitations to subzones including the
Default Subzone and Traversal Subzone, see the
Default Subzone and Traversal Subzone, see the
section.
Registration, authentication and media encryption policies
In addition to bandwidth management, subzones are also used to control the Expressway's registration,
authentication and media encryption policies.
authentication and media encryption policies.
for more information about how to configure these settings.
Local Zone searches
One of the functions of the Expressway is to route a call received from a locally registered endpoint or external zone
to its appropriate destination. Calls are routed based on the address or alias of the destination endpoint.
to its appropriate destination. Calls are routed based on the address or alias of the destination endpoint.
The Expressway searches for a destination endpoint in its Local Zone and its configured external zones. You can
prioritize the order in which these zones are searched, and filter the search requests sent to each zone, based on the
address or alias being searched for. This allows you to reduce the potential number of search requests sent to the
Local Zone and out to external zones, and speed up the search process.
prioritize the order in which these zones are searched, and filter the search requests sent to each zone, based on the
address or alias being searched for. This allows you to reduce the potential number of search requests sent to the
Local Zone and out to external zones, and speed up the search process.
The Default Zone
The Default Zone represents any incoming calls from endpoints or other devices that are unregistered or not
recognized as belonging to any of the existing configured zones.
recognized as belonging to any of the existing configured zones.
between it and the Traversal Subzone.
Note that the Default Zone cannot be deleted.
129
Cisco Expressway Administrator Guide
Zones and Neighbors