Find answers to your technical questions and learn how to use our products
Search suggestions:
Find answers to your technical questions and learn how to use our products
Search suggestions:
The following table describes the fields in the QoS trap according to the numbered labels in the example.
Label |
Description |
From the trap example |
|---|---|---|
1 |
The date on which the trap was received |
Oct 20 |
2 |
The time at which the trap was received |
11:13:40 |
3 |
The IP address of the local MGP |
135.8.118.252 |
4 |
The Branch Gateway up time |
sysUpTime.0 = Timeticks: (43147723) 4 days, 23:51:17.23 |
5 |
The trap name, which indicates that this is a QoS trap |
snmpTrapOID.0 = OID: av RtpQoSTrap |
6 |
The local gateway PMI |
avRtpSessionLocAddrV4.0 = IpAddress: 135.8.118.252 |
7 |
The remote VoIP engine, gateway PMI, or IP phone address |
avRtpSessionRemAddrV4.0 = IpAddress: 135.8.76.107 |
8 |
The duration of the RTP session |
Duration: 00:04:33 |
9 |
Format: gwt@<MGP-address> |
avRtpSessionCname.0 = STRING: gwp@135.8.118.252 |
10 |
The local extension number and conference ID in format <conference ID>:<extension number>. Conference calls can involve more than one entry in the session table. Multiple sessions belonging to the same conference call can usually be identified by a common conference ID. Notes:
|
avRtpSessionPhone.0 = STRING: 69:2011 |
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{2411/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/012} |
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 5414 RX 9236} |
16 |
The total number of received RTP packets |
Stats{S 54 RTCP 54 RX 923615} |
17 |
The codec used for the session |
g729 |
18 |
The codec packet size, in bytes |
62B |
19 |
The encryption method |
encryptionOff |
20 |
The received silence suppression method |
SSup disabled19/disabled |
21 |
The transmitted silence suppression method |
SSup disabled/disabled20 |
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% #122 |
24 |
The average of all codec round trip time values sampled during the session |
RTT 570mS23 #38 |
25 |
The codec round trip time event counter |
RTT 570mS #3824 |
26 |
The percentage contribution of jitter-buffer underruns to the average codec loss |
Jbuf 0.1%25/0.0% |
27 |
The percentage contribution of jitter-buffer overruns to the average codec loss |
Jbuf 0.1%/0.0%26 |
28 |
The average of all network RTP packet loss values sampled during the session |
Loss 0.0%27 #0 |
29 |
The network RTP packet loss event counter |
Loss 0.0% #028 |
30 |
The average of all network RTT values during the session |
RTT 376mS29 #38 |
31 |
The network RTT event counter |
RTT 376mS #3830 |
32 |
The network jitter at the RTP receiver |
Jtr #0 |
33 |
The minimum and maximum TTL values sampled in the session |
TTL 63-63 |
34 |
A counter that increments each time two consecutive RTP packets with the sample RTP sequence number are received |
Dup 0 |
35 |
A counter that increments each time an RTP packet with a sequence number less than the last known sequence is received |
Fall 0 |
36 |
The average network loss experienced by the remote RTP receiver |
Rem{Loss 0.0%36 #0 Jtr #0} |
37 |
A counter that increments each time the remote loss is sampled over its threshold |
Rem{Loss 0.0% #037 Jtr #0} |
38 |
A counter that increments each time the network jitter experienced by the remote RTP receiver is sampled over its threshold |
Rem{Loss 0.0% #0 Jtr #038} |
39 |
The echo cancellation loss on the TDM bus. A high value (that is, a low absolute value) may indicate impairment of DCP terminals. |
EC{Loss 45dB} |