Avaya Media Gateway G250, Administration Manual

Page: 411 / 840

Configuring and analyzing RTP statistics
Issue 5 June 2008 411
For a description of each metric, see Table 107 . The Codec metrics, Codec loss and Codec
RTT are useful for evaluating the actual user experience. The other metrics are useful for
identifying network problems that contribute to QoS problems experienced by the user. For
example, the Codec RTT metric indicates the overall delay experienced by the user. If you
configure a meaningful threshold on the Codec RTT metric, metrics such as Local Jitter,
Remote Jitter, and rtt metrics may help you identify causes when Codec RTT exceeds its
threshold.
Configuring RTP statistics thresholds
1. Use the
rtp-stat thresholds
command to set thresholds on QoS indicators. For
example:
With this example configuration, if echo-return-loss is sampled higher than 5 dB during an
RTP session, the echo-return-loss event counter increments.
2. Use the
rtp-stat event-threshold
command to set thresholds on QoS events. For
example:
With this example configuration, if echo-return-loss is sampled over its threshold more
than twice during an RTP session, the application considers the session to have QoS
faults.
Enabling and resetting the RTP statistics application
When you enable the RTP statistics application on the gateway, the application starts to collect
QoS data from the VoIP engine(s) and stores the data in the gateway RAM, which holds a
limited history of RTP session entries. The VoIP engine also starts to perform and report UDP
traceroutes.
Session data and automatic session traceroute results can be viewed using the CLI.
Enabling the RTP statistics application
1. Enter
rtp-stat-service
. For example:
G350-001(super)#
rtp-stat thresholds echo-return-loss 5
Done!
G350-001(super)# rtp-stat event-threshold echo-return-loss 2
Done!
G350-001# rtp-stat-service
The RTP statistics service is enabled (default: disabled)