MOS Scores in CDR

[Josh Robbins]

Darren mentioned MOS scores may be added to CDR a few months ago. Anyone here anything about this? Would love to get some idea on customer call quality.

[Logicwrath]

This would be great!

[esoare]

Interesting. 

That would be interesting...

Would the RTP logs from the phone be uploaded to the server...

 

[Darren Schreiber]

I swear we added this. It's been discussed like 50 times internally. That said, I don't see it. grumble grumble.

I'll bring it up at our next product roadmap meeting.

 

[Darren Schreiber]

:-) This is why we have a forum now. I forget things.

(For those of you not aware of what Chris is doing, he just publicly shamed me in our company meeting for forgetting to nominate this feature. It has now been nominated).

[safarov]

You also can add RTCP feature

[Josh Robbins]

So when does this sweet new feature launch?

[esoare]

On 10/3/2017 at 8:10 AM, safarov said:

You also can add RTCP feature

Is RTCP how MOS can be figured out? 

[safarov]

If peer host is supports, then FS daemon can receive RTP statistics from remote end.

This will allow you get RTP statistic for both direction. For inbound RTP stream FS count statistic by self. For outbound RTP stream FS use statistic from remote end.

You can get RTCP statistic by catching channel reporting FS event. Part of example of RTCP FS stat (used mod_format_cdr) 

  <call-stats>
    <audio>
      <inbound>
        <raw_bytes>219128</raw_bytes>
        <media_bytes>219128</media_bytes>
        <packet_count>1274</packet_count>
        <media_packet_count>1274</media_packet_count>
        <skip_packet_count>2</skip_packet_count>
        <jitter_packet_count>0</jitter_packet_count>
        <dtmf_packet_count>0</dtmf_packet_count>
        <cng_packet_count>0</cng_packet_count>
        <flush_packet_count>0</flush_packet_count>
        <largest_jb_size>0</largest_jb_size>
        <jitter_min_variance>0.99</jitter_min_variance>
        <jitter_max_variance>2.15</jitter_max_variance>
        <jitter_loss_rate>0.00</jitter_loss_rate>
        <jitter_burst_rate>0.00</jitter_burst_rate>
        <mean_interval>20.00</mean_interval>
        <flaw_total>0</flaw_total>
        <quality_percentage>100.00</quality_percentage>
        <mos>4.50</mos>
      </inbound>
      <outbound>
        <raw_bytes>219300</raw_bytes>
        <media_bytes>219300</media_bytes>
        <packet_count>1275</packet_count>
        <media_packet_count>1275</media_packet_count>
        <skip_packet_count>0</skip_packet_count>
        <dtmf_packet_count>0</dtmf_packet_count>
        <cng_packet_count>0</cng_packet_count>
        <rtcp_packet_count>11528</rtcp_packet_count>
        <rtcp_octet_count>1844480</rtcp_octet_count>
      </outbound>
    </audio>
  </call-stats>

 But I think this report have mistake and need to fix it. Look to rtcp_packet_count and packet_count.

[safarov]

@esoare homer use RTCP stat to count MOS.

But same functionality not implemented on FS side. You may use HOMER reports to import MOS statistic to kazoo CDR.
Or need to implement similar functionality on FS side.