Avaya BCM 2.0 IP Telephony Manual de usuario descargar pdf (Pagina 24)

24 Engineering guidelines

Enterprise Edge 2.0 IP Telephony Configuration Guide P0911590 Issue 02

Determining network loading caused by IP telephony traffic

At this point, the installer or administrator has enough information to load the IP

telephony traffic on the intranet.

Consider the intranet has the topology as shown Figure 3 Calculating network load

with IP telephony traffic on page 24, and the installer or administrator wants to

know in advance the amount of traffic on a specific link, R4-R5. Consider there are

four IP telephony ports per site.

With the Enterprise Edge VoIP Gateway bandwidth engineering section on page 17

and Traceroute measurements, the R4-R5 link is expected to support the Santa

Clara/Richardson, Santa Clara/Tokyo and the Ottawa/Tokyo traffic flows. The

other IP telephony traffic flows do not route over R4-R5. A peak of eight calls can

be made over R4-R5 for the four IP telephony ports per site. R4-R5 needs to support

the incremental bandwidth of 8 x 12 = 96 kbit/s.

To complete this exercise, the traffic flow from every site pair needs to be summed

to calculate the load on each route and loaded to the link.

Figure 3 Calculating network load with IP telephony traffic

Enough link capacity

Table 3 Link capacity on page 25 sorts the computations so that for each link, the

available link capacity is compared against the additional IP telephony load. For

example, on link R4-R5, there is capacity (568 kbit/s) to allow for the additional 96

kbit/s of IP telephony traffic.

Enterprise Edge IP telephony

Router

Santa Clara/Richardson traffic

Ottawa/Tokyo traffic

Santa Clara/Tokyo traffic

Richardson

Santa Clara

Tokyo

Ottawa

1 2 ... 19 20 21 22 23 24 25 26 27 28 29 ... 75 76

Sin comentarios

Avaya BCM 2.0 IP Telephony Manual de usuario Pagina 24