voice quality monitoring report (sip publish)

Panasonic Corporation

Voice Quality Monitoring Report(SIP Publish)

18th June 2020

Rev 1.21

2

Revision history

Date Revision Changes

30th July 2018 Rev 1.0 Initial Release

17th December 2018 Rev 1.1

Improvement added- SSRC/Codec/Network condition changes - Receiving out-of-band DTMF- MOS score in VM access

23rd December 2019 Rev 1.2 Added TGP700/HDV340

18th June 2020 Rev 1.21 Format change to 16:9

TGP700 TGP600 HDV130 HDV230 HDV330 HDV340 HDV430

All version1.084 or

later2.000 or

later1.019 or

later1.002 or

laterAll version All version

Support Model

3

Contents

OverviewCalculate MOS score Voice Quality Monitoring ReportImprovement• SSRC/Codec/Network condition changes• Receiving out-of-band DTMF• Calculate MOS score in case Voice Mail access

4

Overview1.Abstract

Voice Quality Monitoring Report (VQMR) is a remote monitoring feature for QoS of

RTP voice communication.

VQMR is outputted to Collector with SIP Publish method.

Our phones support RFC3611 and RFC6035.

RTP

VQMR(SIP Publish)

Collector

5

Calculate MOS score

2. Spec of calculation MOS score and R score: - MOS score and R score indicate voice quality during conversation, and they are contained in the each RTCP packet.- The phone calculates average of MOS score and R score, and add them to “Message Body” of SIP-PUBLISH packet as “QualityEst” data.- Regarding more details, refer following pages.

Setting sample for sending SIP-PUBLISH:

# Panasonic SIP Phone Standard Format File #

RTCP_ENABLE_1="Y"RTCPXR_ENABLE_1="Y"

VQREPORT_COLLECTOR_ADDRESS="sip:xxxxx:5700"VQREPORT_COLLECTOR_PORT="5700"VQREPORT_SEND="1"

You can specify the destination of sending SIP-PUBLISH.

<case1. Destination: collector server>It sends SIP-PUBLISH to the collector server.Required setting:VQREPORT_COLLECTOR_ADDRESS="xxxxx"

<case2. Destination: proxy server>It sends SIP-PUBLISH to the proxy server, even if collector server is specified.Required setting:VQREPORT_COLLECTOR_ADDRESS=“sip:xxxxx:5700"VQREPORT_COLLECTOR_PORT="5700"

“sip:” and your port number are needed.

6

Calculate MOS score (VQREPORT_SEND=“1”)

TALK

INVITE

100 trying

Server Other phoneTGP600

180 ringing

200 OK

1.Initialize.Start loggingMOS score, R score

2.Stop loggingMOS score, R score

3.Calculate average ofMOS score, R score.Its target period is between 1 and 2.

BYE

4.Send PUBLISH which contains averaged MOS score and R score.

PUBLISH-MOS score-R score

<internal processing>

VQREPORT_SEND=“1” : Report is sent when the session of each call is terminated .

7


VQREPORT_SEND=“2” : Interval report Using PUBLISH


200 OK

1.Initialize.Start loggingMOS score, R score

3.Calculate average ofMOS score, R score.Its target period is between 1 and 2.

BYE4.Send PUBLISH which contains averaged MOS score and R score.

PUBLISH ( MOS score, R score )

<internal processing>

2.Stop loggingMOS score, R score

RTCP-XR ( MOS, R Factor )


RTCP_INTVL_n( default value is 5 seconds. )

RTCP-XR ( MOS, R Factor )


RTCP_INTVL_n( default value is 5 second. )

MOS and R Factor which are contained in RTCP-XRare calculated for specified each period.

PUBLISHs are sent at intervals of the same as RTCP-XR,if you set VQREPORT_SEND as “2”.MOS score and R score which are contained in PUBLISHare the same as RTCP-XR’s values.(These values are not averaged.)

TALK

PUBLISH which contains averaged MOS score and R scoreis also sent at the end of the conversation.

8


< Additional alert setting >( sample )ALERT_REPORT_TRIGGER=“1” : CriticalALERT_REPORT_MOSQ_CRITICAL=“30” : This means that threshold of MOS value is 3.0.

VQREPORT_SEND=“3” : Alert Report Using PUBLISH


200 OK

BYE

RTCP-XR ( MOS=4.0, R Factor )

RTCP_INTVL_n( default value is 5 seconds. )

PUBLISH ( MOS score=2.9, R score )










PUBLISHs are sent at intervals of the same as RTCP-XRduring MOS value falls below the specified threshold value,if you set VQREPORT_SEND as “3”.MOS score and R score which are contained in PUBLISHare the same as RTCP-XR’s values.(These values are not averaged.)

TALK

9

Voice Quality Monitoring Report

Number Item Support

1 Call Term Y

2 SessionInfo Y

2.1 CallID Y

2.2 LocalID Y

2.3 RemoteID Y

2.4 OrigID Y

2.5 LocalAddr Y

2.6 RemoteAddr Y

2.7 LocalGroupID Y

2.8 RemoteGroupID Y

2.9 LocalMacAddr N

2.10 RemoteMacAddr N

3 LocalMetrics Y

3.1 TimeStamps Y

3.2 SessionDescription Y

3. Report item

(1) Session report (Final report)

Number Item Support

3.2.1 PayloadTypeY

3.2.2 PayloadDescY

3.2.3 SamplerateY

3.2.4 PacketPerSecondY

3.2.5 FrameDurationY

3.2.6 FrameOctetsY

3.2.7 FramesPerPacketY

3.2.8 FmtpOptionsY

3.2.9 PacketLossConcealmentY

3.2.10 SilenceSuppressionStateY

3.3 JitterBufferY

3.3.1 JitterBufferAdaptiveY

3.3.2 JitterBufferRateY

3.3.3 JitterBufferNominalY

3.3.4 JitterBufferMaxY

10


Number Item Support

3.3.5 JitterBufferAbsMax Y

3.4 PaketLoss Y

3.4.1 NetworkPacketLossRate Y

3.4.2 JitterBufferDiscardRate Y

3.5 BurstGapLoss Y

3.5.1 BurstLossDensity Y

3.5.2 BurstDuration Y

3.5.3 GapLossDensity Y

3.5.4 GapDuration Y

3.5.5 MinimumGapThreshold Y

3.6 Delay Y

3.6.1 RoundTripDelay N

3.6.2 EndSystemDelay Y

3.6.3 OneWayDelay N

3.6.4 SymmOneWayDelay N

3.6.5 InterarrivalJitter N

3.6.6 MeanAbsoluteJitter N

Number Item Support

3.7 Signal Y

3.7.1 SignalLevel Y

3.7.2 NoiseLevel Y

3.7.3 ResidualEchoReturnLoss Y

3.8 QualityEstimates Y

3.8.1 ListeningQualityR Y

3.8.2 RLQEstAlg N

3.8.3 ConversationalQualityR N

3.8.4 RCQEstAlg N

3.8.5 ExternalR-In Y

3.8.6 ExtRInEstAlg N

3.8.7 ExternalR-Out N

3.8.8 ExtROutEstAlg N

3.8.9 MOS-LQ Y

3.8.10 MOSLQEstAlg N

3.8.11 MOS-CQ Y

3.8.12 MOSCQEstAlg N

11


Number Item Support

3.8.13 QoEEstAlg N

4 RemoteMetrics N

5 Dialog N

Number Item Support

4.5 LocalAddr Y

4.6 RemoteAddr Y

4.7 LocalGroupID Y

4.8 RemoteGroupID Y

4.9 LocalMacAddr N

4.10 RemoteMacAddr N

5 LocalMetrics Y

5.1 TimeStamps Y

5.2 SessionDescription Y

5.2.1 PayloadType Y

5.2.2 PayloadDesc Y

5.2.3 Samplerate Y

5.2.4 PacketPerSecond Y

5.2.5 FrameDuration Y

5.2.6 FrameOctets Y

5.2.7 FramesPerPacket Y

5.2.8 FmtpOptions Y

(2) Interval report

It is same as Session report

(3) Alert report

Number Item Support

1 MetricTypeY

2 DirectionY

3 SeverityY

4 SessionInfo Y

4.1 CallID Y

4.2 LocalID Y

4.3 RemoteID Y

4.4 OrigID Y

12


Number Item Support

5.2.9 PacketLossConcealment Y

5.2.10 SilenceSuppressionState Y

5.3 JitterBuffer Y

5.3.1 JitterBufferAdaptive Y

5.3.2 JitterBufferRate Y

5.3.3 JitterBufferNominal Y

5.3.4 JitterBufferMax Y

5.3.5 JitterBufferAbsMax Y

5.4 PaketLoss Y

5.4.1 NetworkPacketLossRate Y

5.4.2 JitterBufferDiscardRate Y

5.5 BurstGapLoss Y

5.5.1 BurstLossDensity Y

5.5.2 BurstDuration Y

5.5.3 GapLossDensity N

5.5.4 GapDuration N

5.5.5 MinimumGapThreshold N

Number Item Support

5.6 Delay Y

5.6.1 RoundTripDelay N

5.6.2 EndSystemDelay Y

5.6.3 OneWayDelay N

5.6.4 SymmOneWayDelay N

5.6.5 InterarrivalJitter N

5.6.6 MeanAbsoluteJitter N

5.7 Signal Y

5.7.1 SignalLevel Y

5.7.2 NoiseLevel Y

5.7.3 ResidualEchoReturnLoss Y

5.8 QualityEstimates Y

5.8.1 ListeningQualityR Y

5.8.2 RLQEstAlg N

5.8.3 ConversationalQualityR N

5.8.4 RCQEstAlg N

5.8.5 ExternalR-In Y

13


Number Item Support

5.8.6 ExtRInEstAlg N

5.8.7 ExternalR-Out N

5.8.8 ExtROutEstAlg N

5.8.9 MOS-LQ Y

5.8.10 MOSLQEstAlg N

5.8.11 MOS-CQ Y

5.8.12 MOSCQEstAlg N

5.8.13 QoEEstAlg N

6 RemoteMetrics N

7 Dialog N

14


Parameter Name Value RangeDefaultValue

Explanation

RTCP_ENABLE_nY/NY: Enable RTCPN: Disable

N Selects whether to enable or disable RTCP

RTCPXR_ENABLE_nY/NY: Enable RTCP-XRN: Disable

N Selects whether to enable or disable RTCP-XR

VQREPORT_COLLECTOR_ADDRESS Up to 256 characters NULL

Specifies the IP address or FQDN of the collector server.

If you want to send PUBLISH to the proxy even though the collector server address is set, you should this parameter as follows.

VQREPORT_COLLECTOR_ADDRESS=“sip:xxxxx:pppp”- xxxxx: the collector server address- pppp: port of the collector server

VQREPORT_COLLECTOR_PORT 1 to 65535 5060 Specifies the port of the collector server.

VQREPORT_SEND

0 to 30 : Disable1 : End of Session Report Using PUBLISH2 : Interval report Using PUBLISH3 : Alert Report Using PUBLISH

0 Specifies the sending type of the VQ report using PUBLISH.

VQREPORT_SIGNAL_COMPRESSION Y/N N Specifies whether to use signal compression for sending VQ report.

ALERT_REPORT_TRIGGER0,10: Warning1: Critical

0 Specifies the trigger to notify the VQ report.

ALERT_REPORT_MOSQ_CRITICAL 0 to 40 0 Specifies the critical's criteria to send VQ report at the time of occurring the MOSQ.

ALERT_REPORT_MOSQ_WARNING 0 to 40 0 Specifies the warning's criteria to send VQ report at the time of occurring the MOSQ.

ALERT_REPORT_DELAY_CRITICAL 0 to 2000 0 Specifies the critical's criteria to send VQ report at the time of occurring the delay.

ALERT_REPORT_DELAY_WARNING 0 to 2000 0 Specifies the warning's criteria to send VQ report at the time of occurring the delay.

3. Configuration parameters

15


4. Simplified Example of the Configuration Parameters

# Panasonic SIP Phone Standard Format File #

# This is a simplified sample configuration file for Voice Quality Monitoring.

## RTP/RTCP/RTCP-XR Settings

RTCP_ENABLE_1=“Y"

RTCPXR_ENABLE_1=“Y“

## VQ Report by PUBLISH

VQREPORT_COLLECTOR_ADDRESS=“[email protected]"

VQREPORT_COLLECTOR_PORT="5060"

VQREPORT_SEND=“3"

ALERT_REPORT_TRIGGER=“1"

ALERT_REPORT_MOSQ_CRITICAL=“15"

ALERT_REPORT_MOSQ_WARNING=“20"

ALERT_REPORT_DELAY_CRITICAL=“400"

ALERT_REPORT_DELAY_WARNING=“300"

VQREPORT_SIGNAL_COMPRESSION="N"

# Other setting uses a default value

16


5. Voice Quality Monitoring Report settings on Web GUI

Login to Web with administrator authority

“Network tab” ->“VoIP Settings”

17


RTCP and RTCP-XR settings from Web GUI

Login to Web with administrator authority

“VoIP tab” ->“Line n”

18

- Improvement -

SSRC/Codec/Network condition changes

19

Improvement of SIP-PUBLISH

SIP Product Models Affected:KX-TGP600 V01.129 or earlier

Carrier request:The endpoint sends SIP-PUBLISH after SSRC/Codec/Network condition changes.

Current spec: The endpoint does not send above situation.

New spec:The endpoint sends SIP-PUBLISH after SSRC/Codec/Network condition changes.

Firmware version:KX-TGP600 V01.139

20

Improvement of SIP-PUBLISH (SSRC changed)(1/2)

SSRC changed (finished)


200 OK

BYE

TALK

HOLD

re-INVITE

re-INVITE



average

average

RTP session using the SSRC finished.

TALK

SSRC=0xXXXXXXX

SSRC=0xYYYYYYYY

< RTP >

VQREPORT_SEND=“1” (End of Session Report Using PUBLISH)

The endpoint sends SIP-PUBLISH for each SSRC.

21

ServerOther phone(TGP600)TGP600

200 OK

BYE

TALK

HOLD

re-INVITE

re-INVITE



average

TALK

PushingHOLD key

PushingHOLD key

TALK

Held

Resumed

Status Codec SSRC

Talking

Talking

Held.(Hearing

MoHmusic)

PCMU

PCMU

PCMU

0xaaaaaaaa

0xbbbbbbbb

0xcccccccc

Focus this phone


average

average

UserOperation

SSRC changed (finished) VQREPORT_SEND=“1” (End of Session Report Using PUBLISH)



average

average

The endpoint sends SIP-PUBLISH for each SSRC.

Improvement of SIP-PUBLISH (SSRC changed)(2/2)

22

Improvement of SIP-PUBLISH (CODEC changed)(1/1)

CODEC changed


200 OK

BYE

TALK

re-INVITE(SDP)



average

average

CODEC changed

G.729

G.711

< RTP >

In case of using call recording function of 8x8

VQREPORT_SEND=“1” (End of Session Report Using PUBLISH)VQREPORT_SEND_OPT_CODEC_ENABLE=“Y”

The endpoint sends SIP-PUBLISH for each CODEC.

23

Improvement of SIP-PUBLISH (Network condition changed)(1/3)


200 OK

BYE

TALK



average

average

Network conditionChanged.MOS score falls below specified threshold value.

( just sample )ALERT_REPORT_TRIGGER=“1” : CriticalALERT_REPORT_MOSQ_CRITICAL=“25” : This setting means that threshold of MOS value is 2.5.

Network conditionChanged.MOS score gets well again.


average

MOS = 4.0MOS = 4.1MOS = 4.0MOS = 3.9MOS = 2.4

< RTCP-XR >

MOS = 2.4MOS = 2.1MOS = 2.0MOS = 2.2MOS = 3.1

MOS = 3.1MOS = 3.5MOS = 4.0

VQREPORT_SEND=“1” (End of Session Report Using PUBLISH)VQREPORT_SEND_OPT_NW_CHANGE=“1”

The endpoint sends SIP-PUBLISH for each Network condition.

Network condition changed

You can specify the condition to detect network change.

New config parameter:VQREPORT_SEND_OPT_NW_CHANGE

Related config parameters:ALERT_REPORT_TRIGGERALERT_REPORT_MOSQ_CRITICALALERT_REPORT_MOSQ_WARNING

Following settings are needed.VQREPORT_SEND="1"

24

VQREPORT_SEND=“1” (End of Session Report Using PUBLISH)Network condition changed


200 OK

BYE

TALK



average

MOS = 3.0

MOS = 2.1

MOS = 2.6

MOS = 2.3

MOS = 2.9

MOS = 3.0::

< RTCP-XR >




“1”

“1”

“1”

“1”

average

High -> Low

High

High

Low -> High

High -> Low

Low -> High

Detect Network condition change

ex) VQREPORT_SEND_OPT_NW_CHANGE=“1”



25

MOS = 3.0

MOS = 2.1

MOS = 2.6

MOS = 2.3

MOS＝2.2

MOS＝2.2

MOS = 2.9

MOS = 3.0

MOS = 2.1

MOS = 3.0

MOS = 3.0

MOS = 3.0

MOS = 3.0

::

MOS = 3.0

MOS = 2.1

MOS = 2.6

MOS = 2.3

MOS＝2.2

MOS＝2.2

MOS = 2.9

MOS = 3.0

MOS = 2.1

MOS = 3.0

MOS = 3.0

MOS = 3.0

MOS = 3.0

::

VQREPORT_SEND=“1” (End of Session Report Using PUBLISH) Network condition changed

TGP600

BYE

TALK


average

< RTCP-XR >



average

average


TGP600

BYE

TALK


average

< RTCP-XR >



average

average


High -> Low

Low -> High

High

Low

High

High -> Low

Low -> High

High

Low

High


“1”

“1”

“2”

“1”

“2”

“1”

“1”

“1”

“2”

“3”

“1”

“2”

“1”

“2”

“3”




- Improvement -

Receiving out-of-band DTMF

27





Receive out-of-band DTMF during conversation

TALK

<Current spec>Server Other phoneTGP600

200 OK1.Initialize.Start logging MOS score, R score

2.Stop logging MOS score, R score



BYE3.Calculate average ofMOS score, R score.Its target period is between 1 and 2.

Receiving out-of-band DTMF causes decrease of the MOS value of PUBLISH which is sent at the end of conversation.

receiveout-of-band

DTMFinstead of RTP

for conversation.Receive out-of-band DTMF instead of the RTP stream for conversation.TGP600 recognizes it as packet loss.It causes decrease of MOS score and R score.

MOS score is average of them.

28





Receive out-of-band DTMF during conversation

TALK

<New proposal spec>Server Other phoneTGP600

200 OK1.Initialize.Start logging MOS score, R score

2.Stop logging MOS score, R score



BYE3.Calculate average ofMOS score, R score.Its target period is between 1 and 2.

Decrease of MOS value does not appear, even if it receives out-of-band DTMF.

receiveout-of-band

DTMFinstead of RTP

for conversation.

Receive out-of-band DTMF instead of the RTP stream for conversation.


<Improvement point>If TGP600 detects receiving out-of-band DTMF instead of the RTP stream,it copies the MOS value contained in just before RTCP-XR to the next RTCP-XR instead of actual value.

copy

copy

29

- Improvement -

Calculate MOS score in case Voice Mail access

30

New Configuration parameter

Parameter Name Value RangeDefaultValue

Reboot Explanation

VQREPORT_PACKET_LOSS_DETECTIONY/NY: Enable to modified calculationN: Disable (current calculation)

N YesSpecify whether to improve the MOS value in case ofVM access

31

<Current spec>TGP600



Start VM access

Guidance : Welcome to Voice Mail portal ,,, please enter your pass code,,,



RTP


NoRTP

RTCP-XR ( MOS=1.0, R Factor )RTP

IVR server stop sending RTP packet

[Background]

MOS score is calculated by using R score.

This logic is based on ITU-T G.107 Annex B - page15.

le,eff stands for packet loss

[Current spec]

Since the phone can not understand whether it occurs "packet loss" or "server stop sending RTP packet", the phone handles as "packet loss“.

le,eff value becomes bigger, and then reflected in the MOS value.

MOS value is bad.

End VM access

VM Server

Improvement of calculate MOS score in case Voice Mail access

32

[New spec]

The phone monitor the sequence number and time stamp of RTP packet.

a) In case sequence number is continuously and Time stamp is suitable, the phone does NOT handles as "packet loss“(handles as silent packet).

b) In case sequence number is NOT continuously or Time stamp is NOT suitable, the phone handles as packet loss.

[New spec]

Since the phone can not understand whether it occurs "packet loss" or "server stop sending RTP packet", the phone does NOT handles as "packet loss“(handles as silent packet).

le,eff value does not becomes bigger, and then reflected in the MOS value.

MOS value is good.

<New spec>VM ServerTGP600



Start VM access



RTP


NoRTP

RTCP-XR ( MOS=4.0, R Factor )RTP

IVR server stop sending RTP packet

End VM access

RTP : sequence number =X, Time stamp

RTP : sequence number =X+1, Time stamp

Improvement of calculate MOS score in case Voice Mail access

Guidance : Welcome to Voice Mail portal ,,, please enter your pass code,,,

voice quality monitoring report (sip publish)

Documents