Hi,
That's true.
But just for completeness, know that there is also another ITU-T recommendation, "G.107 - The E-model, a computational model for use in transmission planning" (not freely available from ITU-T though), which describes how to calculate a MOS from objectively measured parameters.
These include network- (loss, delay, jitter) as well as device- (TELR, ELR etc.) and environment- (noise etc.) specific parameters.
At least for the network related impairments, a network analysis tool like Wireshark could help in principle in that it could provide these calculation, assuming the other parameters stay constant and can be used with reasonable default values.
Regards,
Lars Ruoff
> -----Original Message-----
> From: wireshark-users-bounces@xxxxxxxxxxxxx
> [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Guy Harris
> Sent: lundi 12 avril 2010 20:40
> To: Community support list for Wireshark
> Subject: Re: [Wireshark-users] mean opinion score
>
>
> On Apr 12, 2010, at 8:16 AM, ankur aggarwal wrote:
>
> > Can anybody help me in finding MOS through wireshark or any
> other s/w which work on my intranet. (offline mode).
>
> Wireshark is software, not a human being, and thus cannot
> itself generate a mean opinion score; the same applies to any
> other software.
>
> The mean opinion score is calculated based on *subjective*
> evaluations of sound quality by human listeners; see the
> Wikipedia article:
>
> http://en.wikipedia.org/wiki/Mean_opinion_score
>
> and the ITU-T recommendation to which it refers, P.80:
>
> http://www.itu.int/rec/T-REC-P.800-199608-I/en
>
> You could, at best, have Wireshark play back the audio and
> have various listeners evaluate it, and then calculate the
> MOS based on their evaluations.
> ______________________________________________________________
> _____________
> Sent via: Wireshark-users mailing list
> <wireshark-users@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
>
> mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
>