Thomas_Karlshoj | 2019-01-24 15:09:54 UTC | #1
Hi,
Recently we have gained access to Mos score and rFactor for call conversations. We can see several scores under each conversation. We are having a hard time sorting these as we dont know the endpoints for each score.
We can have five scores i a single call where four of them are above 4 an one is 1,2, Is there any way for us to find out which one is 1.2? I cant really see what we can use this tool for if we dont have any endpoints on each score, It just tells me there is a problem somewhere in the stream but not when and where,
anon53977128 | 2019-01-24 16:24:45 UTC | #2
Mean Opinion Score (MOS) is a measure of audio quality at a specific measurement point of a voice interaction. Potential measurement points are on-premise or cloud-based Edge devices. Values in the MOS column are estimated average MOS scores. The estimated average MOS score for a stream is based on codec type, average jitter, latency, and packet loss. Each MOS score is a number between 1 (unacceptable) and 5 (excellent). Scores below 3.5 generally indicate unacceptable quality. Scores between 4.3 and 5 indicate high quality.
R-Factor: A value derived from metrics such as latency, jitter, and packet loss per ITU‑T Recommendation G.107, the R-Factor value helps you quickly assess the quality-of-experience for VoIP calls on your network. Typical scores range from 50 (bad) to 90 (excellent).
More information can be found here: https://www.genesys.com/blog/post/measure-audio-quality-to-reduce-management-headaches
Thomas_Karlshoj | 2019-01-25 07:38:19 UTC | #3
Im not sure you understood my question. I am familiar with MOS and rfactor.
My question is:
How can i see the endpoints (ip adresses) for the different mos scores and rfactor scores i get out of /api/v2/analytics/conversations/{conversationId}/details ?
Im getting this:
"mediaEndpointStats": [ { "codecs": [ "audio/opus" ], "minMos": 4.880436897277832, "minRFactor": 92.35778045654297, "maxLatencyMs": 30, "receivedPackets": 1484, "invalidPackets": 0, "discardedPackets": 0, "duplicatePackets": 0, "overrunPackets": 0, "underrunPackets": 0 }, { "codecs": [ "audio/opus" ], "minMos": 4.874748706817627, "minRFactor": 92.11344146728516, "maxLatencyMs": 30, "receivedPackets": 1936, "invalidPackets": 0, "discardedPackets": 0, "duplicatePackets": 0, "overrunPackets": 0, "underrunPackets": 0 }, { "codecs": [ "audio/opus" ], "minMos": 4.878721714019775, "minRFactor": 92.28360748291016, "maxLatencyMs": 30, "receivedPackets": 453, "invalidPackets": 0, "discardedPackets": 0, "duplicatePackets": 0, "overrunPackets": 0, "underrunPackets": 0 }, { "codecs": [ "audio/PCMA" ], "minMos": 1.2382124662399292, "minRFactor": 19.525653839111328, "maxLatencyMs": 65526, "receivedPackets": 10044, "invalidPackets": 0, "discardedPackets": 125, "duplicatePackets": 0, "overrunPackets": 0, "underrunPackets": 0 }, { "codecs": [ "audio/opus" ], "minMos": 4.4420270919799805, "minRFactor": 79.31442260742188, "maxLatencyMs": 21829, "receivedPackets": 6233, "invalidPackets": 0, "discardedPackets": 1, "duplicatePackets": 0, "overrunPackets": 0, "underrunPackets": 0 } ],
Zachary_Hinkle | 2019-01-25 13:51:29 UTC | #4
@Thomas_Karlshoj - We don't expose IPs as a part of this feature. That's an enhancement we plan on delivering in the future. We will be generating a PCAP for signaling very soon though.
Thomas_Karlshoj | 2019-01-25 14:03:13 UTC | #5
Can anything be said about the order of these MOS scores in my previous post? Are they in any order compared to a timeline?
system | 2019-02-24 14:03:15 UTC | #6
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 4416