Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_docset_workflow
APPRJIDSYM-20603
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ced70caa, userName='null'}
DEV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c7f0006a, userName='null'}
LDEV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ced70caa, userName='null'}
SVT1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cba30625, userName='null'}
LSVT1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ced70caa, userName='null'}
AUTHJIDSYM-20602

Panel

In this section:

Table of Contents

Overview

The

Spacevars
0product
 acts as an analyzer element with an integrated Nectar solution to derive session-level media quality statistics.

The Voice Quality (VQ) reporting feature enables statistics reporting to a Nectar Unified Communication Diagnostics (UCD) server to provide quality monitoring. The information collected helps administrators to understand the media quality that users experience. With VQ monitoring, the administrators can:

  • Gather statistics on media quality at individual locations or based on a grouping of subnets.
  • Proactively monitor and troubleshoot media quality of experience issues.
  • Perform diagnostics in response to VoIP user complaints. 
  • View trends that can help them with post-deployment growth and measure results against the service level agreement.

By introducing this feature to the

Spacevars
0product
, all the SIP legs of a call can now report audio metrics.

Note

The SIP Voice Quality reporting is a licensed feature. To enable this feature, you should obtain the feature license. For more information, see Node-Locked Licensing. 


Note

The voice metrics will be collected only in the DSP mode; audio metrics will not be collected for any call routed in the Proxy or Direct Media mode.

Configuring SIP Voice Quality Server Settings

To configure the SIP Voice Quality server:

  1. In the WebUI, click the Settings tab.

  2. In the left navigation pane, go to SIP > SIP Voice Quality Server.
    The following window appears. 

    Anchor
    SIP Voice Quality Server Settings
    SIP Voice Quality Server Settings

  3. Select Enable from the SIP Voice Quality Reporting drop-down menu. For detailed information on the fields, see SIP Voice Quality Server Settings - Field Definitions.

  4. Enter the IP Address or Fully Qualified Domain Name (FQDN) of the UCD server that receives the NOTIFY.

  5. Enter the port of the server that receives NOTIFY.

  6. Select an entry from the Transport Protocol field. The available options are: TCP, UDP, and TLS.
    When the selected Transport Protocol is TLS, then the default TLS Profile is Default TLS Profile.

  7. Enter the Reporting Interval value field.

  8. Enter the Impairment Threshold value.

  9. Select the SIP Signaling group(s). To select a SIP Signaling group, click Add/Edit button.
    The following window appears. 

    Anchor
    Selecting IP SG
    Selecting IP SG

    1. Select the SIP Signaling group(s) from the list.
    2. Click OK.
  10. Click Apply.

Anchor
Definitions
Definitions

SIP Voice Quality Server Settings - Field Descriptions 

Field NameValue/RangeDefault ValueMandatoryDescription
Server Address

Valid IP Address
(IPv4, IPv6, or FQDN)

None(tick)

Specifies the IP Address or Fully Qualified Domain Name (FQDN) of the UCD server that receives the NOTIFY.

Server Port1024–655355061(tick)Specifies the port of the server to receive NOTIFY.
Transport Protocol0–2TLS(tick)

Specifies the transport protocol used for sending the NOTIFY. Following are the available options.

  • TCP=2
  • UDP=1
  • TLS=4

When the selected Transport Protocol is TLS, then the default TLS Profile is Default Profile (1).

Reporting interval30–3600 seconds300(tick)Minimum value is 30 seconds.
Maximum value is 3600 seconds.

Impairment Threshold

0.0–4.93.0(tick)

If the MOS value of the call is lower than the value specified in this field, the impairment NOTIFY is reported immediately.

SIP Signaling Groups

List of SIP Signaling GroupNone(tick)

UX report the audio metrics of the calls initiating from or terminating to the SIP Signaling Groups configured in this field.

SIP Voice quality Server Counter

To view the SIP VQ server counters, click the Voice Quality Counter option on top of the SIP Voice Quality Server Settings window.

The SIP Voice Quality Server Counters window displays the counters.


Notify Message Examples

The following are examples of NOTIFY messages.

Code Block
themeConfluence
titleA NOTIFY sample with multiple audio metrics of various active call as payload.
NOTIFY sip:ucd-p.nectar.com:5060 SIP/2.0
Allow: INVITE, ACK, CANCEL, BYE, UPDATE, NOTIFY, OPTIONS, REFER, REGISTER
Call-ID: call-D6877400-0000-0010-1B19-35@134.56.227.59
Contact: <sip: ucd-p.nectar.com;transport=TLS>
Content-Length: 1234
Content-Type: multipart/mixed;boundary="boundary1"
CSeq: 1 NOTIFY
Event: vq-rtcpxr
From:  <sip:sbc.sonusnet.com:5060>;tag=8638e33b-15c
Max-Forwards: 70
Supported: replaces,update,100rel
To:  <sip: ucd-p.nectar.com:5060>
User-Agent: SONUS SBC1000 QOE2v3 Sonus SBC; Interval=30
Via: SIP/2.0/TLS 134.56.227.59;branch=z9hG4bK-UX-8638-e33b-03a4
 
--boundary1
rtcp-xr-30-second-report-1
--boundary1
rtcp-xr-30-second-report-2
--boundary1
rtcp-xr-30-second-report-3
--boundary1
rtcp-xr-30-second-report-4
--boundary1
rtcp-xr-30-second-report-5
--boundary1
rtcp-xr-30-second-report-6
--boundary1
rtcp-xr-30-second-report-7
--boundary1
rtcp-xr-30-second-report-8
--boundary1
rtcp-xr-30-second-report-9
--boundary1
rtcp-xr-30-second-report-10
--boundary1--


Code Block
languagenone
titlertcp-xr-30-second-report sample:
Content-Type: application/vq-rtcpxr
 
VQIntervalRepor
LocalGroup: SONUS SBC1000 QOE2v3 UX
RemoteGroup: PolycomSoundPointIP-SPIP_430-UA/1.6.6.0042
LocalAddr: IP=134.56.227.59 PORT=16510 SSRC=0
RemoteAddr:IP=134.56.225.102 PORT=2232 SSRC=1
LocalMetrics:
Timestamps: START=T1 STOP=T2
JitterBuffer: JBR=v1 JBM=v2
PacketLoss: BSEQ=v1 ESEQ=v2 LPK=v3 NLR=v4 JDR=v5
BurstGapLoss: BLD=v1 BD=v2 GLD=v3 GD=v4
Delay: RTD=v1
Signal: SL=v1 NL=v2 RERL=v3
QualityEst: RLQ=v1 EXTRI=v2 MOSLQ=v3 MOSCQ=v4
RemoteMetrics:
Timestamps: START=T1 STOP=T2
JitterBuffer: JBR=v1 JBM=v2
PacketLoss: BSEQ=v1 ESEQ=v2 LPK=v3 NLR=v4 JDR=v5
BurstGapLoss: BLD=v1 BD=v2 GLD=v3 GD=v4
Delay: RTD=v1
Signal: SL=v1 NL=v2 RERL=v3
QualityEst: RLQ=v1 EXTRI=v2 MOSLQ=v3 MOSCQ=v4
DialogID:29e0b53-4cea9d14-4287c345@134.56.225.102;to-tag=8638e33b-159 ;from-tag=B116EE6-FA2D00F7


Code Block
languagenone
titleA NOTIFY sample with multiple sip msgs as payload.
NOTIFY sip:ucd-p.nectar.com:5060 SIP/2.0
Allow: INVITE, ACK, CANCEL, BYE, UPDATE, NOTIFY, OPTIONS, REFER, REGISTER
Call-ID: call-D6877400-0000-0010-1B19-35@134.56.227.59
Contact: <sip: ucd-p.nectar.com;transport=TLS>
Content-Length: 1234
Content-Type: multipart/mixed;boundary="boundary1"
CSeq: 1 NOTIFY
Event: call-info.sip-msg
From:  <sip:sbc.sonusnet.com:5060>;tag=8638e33b-15c
Max-Forwards: 70
Supported: replaces,update,100rel
To:  <sip: ucd-p.nectar.com:5060>
User-Agent: SONUS SBC1000 QOE2v3 Sonus SBC; Interval=2
Via: SIP/2.0/TLS 134.56.227.59;branch=z9hG4bK-UX-8638-e33b-03a4
 
--boundary1
sip-msg-2-second-report-1
--boundary1
sip-msg-2-second-report-2
--boundary1
sip-msg-2-second-report-3
--boundary1--


Code Block
languagenone
titlesip-signaling-2-second-report sample:
Content-Type: message/sip
 
INVITE sip:bob@biloxi.com SIP/2.0
Via: SIP/2.0/UDP pc33.atlanta.com;branch=z9hG4bKnashds8
To: Bob <bob@biloxi.com>
From: Alice <alice@atlanta.com>;tag=1928301774
Call-ID: a84b4c76e66710
CSeq: 314159 INVITE
Max-Forwards: 70
Date: Thu, 21 Feb 2002 13:02:03 GMT
Contact: <sip:alice@pc33.atlanta.com>
Content-Type: application/sdp
Content-Length: 147
 
v=0
o=UserA 2890844526 2890844526 IN IP4 here.com
s=Session SDP
c=IN IP4 pc33.atlanta.com
t=0 0
m=audio 49172 RTP/AVP 0
a=rtpmap:0 PCMU/8000


Code Block
languagenone
title An impairment NOTIFY sample:
NOTIFY sip:2408881602_1@10.160.147.107:5060 SIP/2.0^M
Call-ID: a3d8539f-66d34d86-d020c835@10.160.147.107^M
Content-Length: 0
CSeq: 1 NOTIFY
Event: call-info.mos-low
From:  <sip:2408881602_1@as.iop1.sonus.net:5060>;tag=aa0932b-5
To:  <sip:2408881602_1@as.iop1.sonus.net>;tag=7D3BD2E8-EF598287
User-Agent: SONUS SBC2000 BSFT_REGv20 Sonus SBC
Via: SIP/2.0/UDP 10.160.147.43:5060;branch=z9hG4bK-UX-0aa0-932b-0005
Content-Type: text/plain
Content-Length: 90
 
DialogID:call-D6877400-0000-0010-0A1B-35@134.56.227.59;to-tag=B8CDB3E8-E1407421 ;from-tag=8638e33b-f5


Code Block
languagenone
title A BYE sample with the X-Sonus-Diagnostics header
BYE sip:4001@192.168.2.221;transport=TCP SIP/2.0
Via: SIP/2.0/TCP 192.168.2.196:5060;branch=z9hG4bK50f68aedc666
Max-Forwards: 70
To: <sip:4001@192.168.2.221;user=phone>;sgid=6;tag=a38e1dd-715
From: "ux196user602" <sip:+15101966002 FREE@192.168.2.196;user=phone>;tag=708f1653
Call-ID: 5715-cf720150903203542358@192.168.2.196
CSeq: 950104510 BYE
Allow: INVITE, ACK, BYE, CANCEL, REGISTER, NOTIFY, OPTIONS, PRACK, REFER, SUBSCRIBE, UPDATE
Supported: 100rel
User-Agent: SHOUT 4.7.2v104
Reason: Q.850; cause=16; text="normal clearing"
Content-Length: 0
X-Sonus-Diagnostics: SBCInternal;moscq=4.9; moslq=4.9


Cloak

To enable Voice Quality server reporting in the Lync SIP Signaling Group:

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to System > Signaling Groups > your Lync signaling group.
  3. In the SIP Channels and Routing Panel, select Enabled from the list box.
  4. Click Apply.

This SIP Signaling Group is used to send QoE Information to the server.  You can track the statistic by looking at the counter.