Wrong MOS calculation about homer-api HOT 7 CLOSED

from homer-api.

It's reasonable to estimate RTT with jitter value.

The problem is homer use count of packet loss instead of percentage of packet loss in the calculation, in this way the loss of packet loss is exaggerated, finally the mos value become irregularly low.

From the code we can tell the impact factor of packet loss is 2.5, which means packet loss of 40% should be regarded as unacceptable. But in this issue, after the conversation lost 40 packets, the mos value was considered to be unacceptable no matter how many packets had been transferred in total.

from homer-api.

Thanks for your comments @lishubing please feel free to submit a PR for discussion and testing

from homer-api.

This seems related to sipcapture/homer#258

@lishubing , any thoughts regarding using packet loss delta instead of cumulative?

from homer-api.

let us know if we can close the ticket. The PR has been merged.

from homer-api.

@mtryfoss In my own MOS calculation, the packet-loss factor is:

$data['report_blocks']['packets_lost'] / $data['sender_information']['packets'] * 100

It seems reasonable for me, do you have any suggestion?

from homer-api.

http://github.com/sipcapture/homer-app

from homer-api.