Cdr Fields For Sbc Local Storage - AudioCodes Mediant 4000 SBC User Manual

User's Manual
CDR Field
RTPdelay
RTPjitter
TxRTPssrc
RxRTPssrc
LocalRFactor
RemoteRFactor
LocalMosCQ
RemoteMosCQ
TxRTPIPDiffServ
LatchedRtpIp
LatchedRtpPort
LatchedT38Ip
LatchedT38Port

52.2.1.3 CDR Fields for SBC Local Storage

The CDR fields for SBC calls that are stored locally (history) on the device are listed in the
table below. For storing CDRs locally, see ''Storing CDRs on the Device'' on page 747.
Version 7.2
Range
information is unavailable)
0 to 10000 ms (-1 if
information is unavailable)
0 to 40000 samples (-1 if
unavailable)
0 to 0xFFFFFFFF
0 to 0xFFFFFFFF
0 to 120 (127 if information is
unavailable)
0 to 120 (127 if information is
unavailable)
10 to 46 (127 if information is
unavailable)
10 to 46 (127 if information is
unavailable)
0 to 63
0 to 0xFFFF
0 to 0xFFFF
741
52. Reporting Information to External Party
Description
Average RTP delay of the entire stream
RTP jitter
Tx RTP SSRC
Local RTP SSRC
Local conversation quality
Note: If the RTCP XR feature is
unavailable (not licensed or disabled),
this R-factor VoIP metric is not provided.
Instead, the device sends the CDR field
with the value 127, meaning that
information is unavailable.
Remote conversation quality
Note: If the RTCP XR feature is
unavailable (not licensed or disabled),
this R-factor VoIP metric is not provided.
Instead, the device sends the CDR field
with the value 127, meaning that
information is unavailable.
Local MOS for conversation
Remote MOS for conversation
Media IP DiffServ
Remote IP address of the incoming RTP
stream that the device "latched" on to as
a result of the RTP latching mechanism
for NAT traversal.
Remote RTP port of the incoming RTP
stream that the device "latched" on to as
a result of the RTP latching mechanism
for NAT traversal.
Latching of a new T.38 stream - new IP
address
Latching of a new T.38 stream - new
port
Mediant 4000 SBC