1 Using RADIUS with the OCSBC
RTP Traffic Reporting per Call
The SBC reports total RTP traffic counts, both received and transmitted for calls through standard accounting interfaces on stop record generation. This traffic is reported in Packets and Octets, sent and received, for flow-sets 1 and 2. The QoS feature set must be enabled to report on RTP traffic, otherwise the values will be reported as 0
These statics are captured for the following scenarios
- RTP pass-thru sessions
- transcoded/transrated/inband (audio) DTMF-interworked RTP sessions
- RTP sessions where one or both call legs is encrypted (SRTP)
RTP traffic reporting does not capture MSRP B2BUA and MSRP NAT traffic.
The quick way to decipher these 16 statistics are as follows:
- Calling/Called - call-leg the static reports on
- Octets/Packets - counter unit for traffic
- FS1/FS2 - flow set 1 or flow set 2
- blank/transmitted - traffic received (blank) or transmitted by the SBC
Counter Definition | RADIUS/Local CDR (VSA #) output | AVP in Acme-Packet-Specific-Rf-QoS(37) |
---|---|---|
Number of Octets (8 bits) of RTP traffic, received by the SBC, from the calling party, for flow-set 1 | Acme-Calling-Octets-FS1 (28) | RTP-Calling-Octets-FS1 (38) |
Number of RTP Packets, sent from the SBC, to the calling UA, for flow-set 1 | Acme-Calling-Packets-FS1 (29) | RTP-Calling-Packets-FS1(40) |
Number of Octets (8 bits) of RTP traffic, sent from the SBC, to the called UA, for flow-set 1 | Acme-Called-Octets-FS1 (44) | RTP-Called-Octets-FS1 (62) |
Number of RTP Packets, sent from the SBC, to the called UA, for flow-set 1 | Acme-Called-Packets-FS1 (45) | RTP-Called-Packets-FS1 (64) |
Number of Octets (8 bits) of RTP traffic, received by the SBC, from the calling party, for flow-set 2 | Acme-Calling-Octets-FS2 (102) | RTP-Calling-Octets-FS2 (39) |
Number of RTP Packets, sent from the SBC, to the calling UA, for flow-set 2 | Acme-Calling-Packets-FS2 (103) | RTP-Calling-Packets-FS2(41) |
Number of Octets (8 bits) of RTP traffic, sent from the SBC, to the called UA, for flow-set 2 | Acme-Called-Octets-FS2 (124) | RTP-Called-Octets-FS2 (63) |
Number of RTP Packets, sent from the SBC, to the called UA, for flow-set 2 | Acme-Called-Packets-FS2 (125) | RTP-Called-Packets-FS2 (65) |
Number of Octets (8 bits) of RTP traffic, transmitted by the SBC, to the calling party, for flow-set 1 | Acme-Calling-RTP-Octet-Transmitted-FS1 (240) | RTP-Calling-Octets-Transmitted-FS1 (42) |
Number of RTP Packets, transmitted by the SBC, to the calling UA, for flow-set 1 | Acme-Calling-RTP-Packets-Transmitted-FS1 (241) | RTP-Calling-Packets-Transmitted-FS1 (44) |
Number of Octets (8 bits) of RTP traffic, transmitted by the SBC, to the called UA, for flow-set 1 | Acme-Called-RTP-Octet-Transmitted-FS1 (242) | RTP-Called-Octets-Transmitted-FS1 (66) |
Number of RTP Packets, transmitted by the SBC, to the called UA, for flow-set 1 | Acme-Called-RTP-Packets-Transmitted-FS1 (243) | RTP-Called-Packets-Transmitted-FS1 (68) |
Number of Octets (8 bits) of RTP traffic, transmitted by the SBC, to the calling party, for flow-set 2 | Acme-Calling-RTP-Octets-Transmitted-FS2 (244) | RTP-Calling-Octets-Transmitted-FS2 (43) |
Number of RTP Packets, transmitted by the SBC, to the calling UA, for flow-set 2 | Acme-Calling-RTP-Packets-Transmitted-FS2 (245) | RTP-Calling-Packets-Transmitted-FS1 (45) |
Number of Octets (8 bits) of RTP traffic, transmitted by the SBC, to the called UA, for flow-set 2 | Acme-Called-RTP-Octet-Transmitted-FS2 (246) | RTP-Called-Octets-Transmitted-FS2 (67) |
Number of RTP Packets, transmitted by the SBC, to the called UA, for flow-set 2 | Acme-Called-RTP-Packets-Transmitted-FS2 (247) | RTP-Called-Packets-Transmitted-FS2 (69) |