Resource Sizing; Overview - Avaya Application Solutions Deployment Manual

Table of Contents

Advertisement

Traffic engineering
A seven-site COI matrix analogous to the three-site matrix in
community of interest (COI) matrix
Figure 55: Network of Avaya systems and system sites
seven-site, expanded COI matrix, similar to the one in
three-site system
networked together, the additional step of engineering the tie trunk groups must be performed.
To do this, the COI matrices are used to determine the traffic flow between each pair of Avaya
systems.
In the network that is shown in
page 161, IP Trunk Group 1 carries calls between Sites 1 and 3, Sites 1 and 4, Sites 2 and 3,
and Sites 2 and 4, in addition to a presumably small amount of overflow traffic that involves
other sites. The traffic load that is associated with such calls is used to size that trunk group. Tie
trunk groups are typically sized at either P01 (1% blocking) or P03 (3% blocking). In a system
such as the one in
traffic engineer must account for overflow traffic. The traditional Wilkinson model is an effective
tool for doing so. However, for systems that have larger numbers of systems in the network,
there can be many possible paths between a given pair of systems. In such cases, determining
the hierarchy of paths to consider for calls between two systems is not always straightforward.
The analysis involved in sizing the tie trunk groups in topologies such as those can be quite
complex.

Resource sizing

Overview

The primary Communication Manager resources that have the potential to be bottlenecks are
the TN799 C-LAN (Control LAN) circuit packs, the port network TDM bus pairs, the TN2302
Media Processing circuit packs, the TN2312 IPSI circuit packs, the server's processing
capacity, and IP bandwidth. This section of the document provides a description of each of
these resources, and a discussion about how to engineer them. This is the final stage of the
design process.
162 Avaya Application Solutions IP Telephony Deployment Guide
on page 148 can be constructed for the network shown in
on page 156, can also be constructed. However, when multiple systems are
Figure 55: Network of Avaya systems and system sites
Figure 55: Network of Avaya systems and system sites
Table 21: 3-site standalone
on page 161. A corresponding
Table 25: Expanded COI matrix for a
on page 161, the
on

Advertisement

Table of Contents
loading

Table of Contents