on page 353
Viewing application configuration
on page 354
on page 355
on page 357
Configuring QoS fault and clear traps
on page 357
Configuring the trap rate limiter
on page 358
Viewing RTP statistics thresholds
The RTP statistics application uses a system of thresholds to evaluate levels of QoS during
RTP sessions. The thresholds are configured on several QoS metrics. Your configuration of
the thresholds determines when the application evaluates a session as having bad QoS
conditions.
This section describes the thresholds that you can configure, how you can view the thresholds
that are currently configured, and the metrics on which you can configure them.
The RTP statistics application samples the VoIP engine every RTCP interval, which is
configured in Avaya Aura
®
Communication Manager, where it is called “RTCP Report
Period”. The RTCP interval is typically 5 to 8 seconds. For information about configuring the
RTCP interval (RTCP report period), see
Administrator Guide for Avaya Aura
®
Communication
Manager
.
Related topics:
on page 350
Viewing the configured thresholds
on page 351
Thresholds types
About this task
A threshold on a metric:
For example, you can configure a threshold on the metric ‘packet
loss’. The application samples the metric every RTP interval and increments a counter (event
counter) if the sampled value is over the threshold. Hence, the 'event-counter' represents the
number of times the metric was sampled over its threshold.
An event threshold:
An event threshold is a threshold on an event counter. If QoS traps are
configured, the application generates a QoS trap when, at the end of a session, one or more
event counters are over their event thresholds. For example, if the event threshold for packet
loss is 2, the application generates a QoS trap if packet loss is sampled over its threshold two
or more times.
Thresholds on metric averages:
The application calculates averages of some of the metrics.
When an RTP session terminates, the application evaluates the average metrics and
generates a QoS trap (if QoS traps are configured) if one of them is over its corresponding
threshold.
Monitoring applications
350 Administering Avaya G430 Branch Gateway
October 2013
Содержание G430
Страница 1: ...Administering Avaya G430 Branch Gateway Release 6 3 03 603228 Issue 5 October 2013 ...
Страница 12: ...12 Administering Avaya G430 Branch Gateway October 2013 ...
Страница 214: ...Ethernet ports 214 Administering Avaya G430 Branch Gateway October 2013 Comments infodev avaya com ...
Страница 232: ...System logging 232 Administering Avaya G430 Branch Gateway October 2013 Comments infodev avaya com ...
Страница 246: ...VoIP QoS 246 Administering Avaya G430 Branch Gateway October 2013 Comments infodev avaya com ...
Страница 250: ...Modems and the Branch Gateway 250 Administering Avaya G430 Branch Gateway October 2013 Comments infodev avaya com ...
Страница 302: ...Emergency Transfer Relay ETR 302 Administering Avaya G430 Branch Gateway October 2013 Comments infodev avaya com ...
Страница 556: ...IPSec VPN 556 Administering Avaya G430 Branch Gateway October 2013 Comments infodev avaya com ...
Страница 604: ...Policy based routing 604 Administering Avaya G430 Branch Gateway October 2013 Comments infodev avaya com ...
Страница 610: ...Synchronization 610 Administering Avaya G430 Branch Gateway October 2013 Comments infodev avaya com ...
Страница 668: ...Traps and MIBs 668 Administering Avaya G430 Branch Gateway October 2013 Comments infodev avaya com ...