Reporting Information To External Party; Configuring Rtcp Xr - AudioCodes Mediant 3000 User Manual

Gateway & enterprise sbc, family of media gateways & session border controllers
Hide thumbs Also See for Mediant 3000:
Table of Contents

Advertisement

User's Manual
45

Reporting Information to External Party

This section describes features for reporting various information to an external party.
45.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. This 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.
Notes:
The RTCP XR feature is available only if the device is installed with a Software
License Key that includes this feature. For installing a Software License Key, see
''Software License Key'' on page 607.
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.
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 using SNMP.
You can configure the device to send RTCP XR to an Event State Compositor (ESC)
server or for Gateway calls, to a specific IP Group (using the PublicationIPGroupID ini file
parameter). If you configure it to send RTCP XR to an IP Group, the RTCP XR is sent to
the address configured for the Proxy Set associated with the IP Group.
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 SEM 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"
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).
Version 6.8
45. Reporting Information to External Party
665
Mediant 3000

Advertisement

Table of Contents
loading

Table of Contents