EasyManua.ls Logo

AudioCodes Mediant 500L - 59 Reporting Information to External Party; Configuring RTCP XR

AudioCodes Mediant 500L
1260 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Version 7.2 909 Mediant 500L Gateway & E-SBC
User's Manual 59. Reporting Information to External Party
59 Reporting Information to External Party
This section describes features for reporting various information to an external party.
59.1 Configuring RTCP XR
RTP Control Protocol Extended Reports (RTCP XR) is a VoIP management control that
defines a set of metrics containing information for assessing VoIP call quality and for
diagnosing problems. RTCP XR (RFC 3611) extends the RTCP reports defined in RFC
3550 by providing additional VoIP metrics (Quality of Experience). RTCP XR information
publishing is implemented in the device according to RFC 6035. The draft defines how a
SIP User Agent (UA) publishes the detailed information to a defined collector. RTCP XR
measures VoIP call quality such as packet loss, delay, signal / noise / echo levels,
estimated R-factor, and mean opinion score (MOS). RTCP XR measures these parameters
using metrics as listed in the table below. RTCP XR messages containing key call-quality-
related metrics are exchanged periodically (user-defined) between the device and the SIP
UA. This allows an analyzer to monitor these metrics midstream, or a device to retrieve
them through SNMP.
Note:
The RTCP XR feature is available only if the device is installed with a License Key
that includes this feature. For installing a License Key, see ''License Key'' on page
817.
If the RTCP XR feature is unavailable (not licensed or disabled), the R-factor VoIP
metrics are not provided in CDRs (CDR fields, Local R Factor and Remote R
Factor) generated by the device. Instead, these CDR fields are sent with the value
127, meaning that information is unavailable.
You can configure the device to send RTCP XR to a specific IP Group. In addition, you
can configure the stage of the call at which you want the device to send RTCP XR:
End of the call.
Periodically, according to a user-defined interval between consecutive reports.
(Gateway Application Only) End of a media segment. A media segment is a change in
media, for example, when the coder is changed or when the caller toggles between
two called parties (using call hold/retrieve). The RTCP XR sent at the end of a media
segment contains information only of that segment. For call hold, the device sends
RTCP XR each time the call is placed on hold and each time it is retrieved. In addition,
the Start timestamp in the RTCP XR indicates the start of the media segment; the End
timestamp indicates the time of the last sent periodic RTCP XR (typically, up to 5
seconds before reported segment ends).
The device sends RTCP XR in SIP PUBLISH messages. The PUBLISH message contains
the following RTCP XR related header values:
From and To: Telephone extension number of the user.
Request-URI: IP address and port of the OVOC server when sent to the ESC server.
When sent to an IP Group, the Request-URI value contains the name of the IP Group
as configured by the 'IP Group Name' parameter (IPGroup_Name).
Event: "vq-rtcpxr"
Content-Type: "application/vq-rtcpxr"
The type of RTCP XR report event (VQReportEvent) supported by the device is
VQSessionReport (SessionReport). The device can include local and remote metrics in the

Table of Contents

Other manuals for AudioCodes Mediant 500L

Related product manuals