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

Engineering guidelines 53

P0911590 Issue 02 Enterprise Edge 2.0 IP Telephony Configuration Guide

When operating IP telephony services, a customer’s organization must have or

include processes to monitor, analyze, and perform design changes to the IP

telephony and the corporate intranet. These processes ensure that both networks

continue to conform to internal quality of service standards and that QoS objectives

are always met.

Setting IP telephony QoS objectives

The installer or administrator needs to state the design objective of IP telephony, the

purpose of which sets the standard for evaluating compliance to meeting users'

needs. When IP telephony is first installed, set the design objectives based on the

work done in Measuring Intranet QoS on page 27.

The QoS objective is to ensure that for each destination pair, the mean+σ of one-

way delay and packet loss is below a threshold value so that calls between those site

pairs have a accurate QoS level. The graphs in Setting QoS on page 26, with the

QoS measurements, can help the installer or administrator determine what threshold

levels are appropriate. The Table 11 IP telephony QoS objectives describes

examples of IP telephony QoS objectives:

Table 11 IP telephony QoS objectives

In following design cycles, the QoS objective is reviewed and improved, based on

data collected from monitoring of intranet QoS. Having decided on a set of QoS

objectives, the installer or administrator determines the planning threshold. The

planning thresholds are based on the QoS objectives. These thresholds used to

trigger the network implementation decisions when the prevailing QoS is within

range of the affected values. This gives time for implementation processes to follow

through. The planning thresholds can be set 5% to 15% below the QoS objectives,

depending on the implementation lag time.

Intranet QoS monitoring

To monitor the one-way delay and packet loss statistics, install delay and route

monitoring tools such as Ping and Traceroute on the LAN of each gateway site.

See Measuring Intranet QoS on page 27 for guidelines describing the

implementation of Ping hosts, the use of scripting, and information about other

delay monitoring tools. Delay monitoring tool runs continuously, adding probe

packets to each gateway about every minute. The load generated by the probe

packets is not considered a large amount. At the end of the month, the hours with

the highest one-way delay are indicated; within those hours, the packet loss and

standard deviation statistics can be calculated.

Site pair Enterprise Edge IP telephony QoS objective Fallback

threshold setting

Santa Clara/

Richardson

Mean (one-way delay) +

(one-way delay) < 120 ms

Mean (packet loss) +

(packet loss) < 0.3%

Excellent

Santa Clara/Ottawa Mean (one-way delay) +

(one-way delay) < 150 ms

Mean (packet loss) +

(packet loss) < 1.1%

Excellent

1 2 ... 48 49 50 51 52 53 54 55 56 57 58 ... 75 76

Comentarios a estos manuales

Sin comentarios

Avaya BCM 2.0 IP Telephony Manual de usuario Pagina 53

Comentarios a estos manuales

Relacionado con productos y manuales para Gateways / Controladores Avaya BCM 2.0 IP Telephony