Avaya G430 - Page 369

Label Description From the trap example
to the same conference call can usually be
identified by a common conference ID.
Notes:
• The phone string data is received from Avaya
Aura
®
Communication Manager if VMON is
configured.
• If you are not running VMON, you can cause
Avaya Aura
®
Communication Manager to send
the phone string data by configuring a dummy
RTCP-server for the region, with a 'localhost' IP
address (127.x.x.x).
11 An arbitrary index number for the session in the
session table
avRtpSessionDebugStr.0 =
STRING: Id{35}
12 The total number of sent traps since the application
was enabled
Traps{24
11
/0}
13 The number of traps that were dropped by the trap
rate limiter since the application was enabled. This
item can be used, when analyzing received traps
logs, to identify missing traps (due to network
conditions or the rate limiter). This is also displayed
by the show rtp-stat summary command.
Traps{24/0
12
}
14 The number of times the application sampled the
VoIP engine (RTP receiver) statistics
Stats{S 54}
15 The total number of received RTCP packets
Stats{S 54 RTCP 54
14
RX
9236}
16 The total number of received RTP packets Stats{S 54 RTCP 54 RX
9236
15
}
17 The codec used for the session g723
18 The codec packet size, in bytes 62B
19 The encryption method encryptionOff
20 The received silence suppression method
SSup disabled
19
/disabled
21 The transmitted silence suppression method
SSup disabled/disabled
20
22 The average of all codec loss values sampled
during the session
Loss 0.1%
21
#1
23 The codec loss event counter
Loss 0.1% #1
22
24 The average of all codec round trip time values
sampled during the session
RTT 570mS
23
#38
25 The codec round trip time event counter
RTT 570mS #38
24
Monitoring applications
Administering Avaya G430 Branch Gateway October 2013 369