Configuring the RTP statistics application
To configure the RTP statistics application, work through the following sections, in order:
Viewing RTP statistics thresholds
●
Configuring RTP statistics thresholds
●
Enabling and resetting the RTP statistics application
●
Viewing application configuration
●
Configuring QoS traps
●
Configuring QoS fault and clear traps
●
Configuring the trap rate limiter
●
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 Communication Manager, where it is called "RTCP Report Period". For
information about configuring the RTCP interval (RTCP report period), see Administrator Guide
for Avaya Communication Manager, 03-300509. The RTCP interval is typically 5 to 8 seconds.
Thresholds types
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.
Configuring and analyzing RTP statistics
Issue 3 February 2007
335