Specifications

Bandwidth, Codecs and Compression
177
This non-meshed configuration is a little different, as it requires that data be forced to travel
back through the central control node. This configuration requires that the “Media Anchor”
function be used, and that all outlying nodes be treated as independent units. This is similar to
a large deployment, for example, a business with multiple corporate HQ in different countries.
To achieve this forced routing, the topology diagram is a little more complex and is shown below.
The tree is divided into three independent trees. Dummy nodes are added as perimeter nodes
and delineate the boundary of each tree with the network.
Figure 25: Topology for Non-meshed Configuration
The fundamental point with this configuration is to force all internode bandwidth monitoring
back through zone 11 and then back through Zone 1. The effect of the call traffic between Zone
2 and Zone 3 going in and out of the link to Zone 1 is simulated by defining Zone 1 to be the
“Media Anchor” zone for Zone 11. In this way, any traffic that flows between Zones 12 and 13
must go through Zone 11 and up and down to Zone 1. The bandwidth monitors A, B, and C will
be located in Zones 1, 2, and 3 respectively. Thus the bandwidth monitor in Zone 1 will monitor
both incoming and outgoing WAN traffic, as required.
Table 53: Non-meshed WAN
Zone Parent
1 Root (1)
2 Root (1)
3 Root (1)