[asterisk-bugs] [JIRA] (ASTERISK-26703) PJSIP Opus jitter rating incorrect over AMI

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-26703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234501#comment-234501 ] 

Asterisk Team commented on ASTERISK-26703:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> PJSIP Opus jitter rating incorrect over AMI
> -------------------------------------------
>
>                 Key: ASTERISK-26703
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26703
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.13.1
>         Environment: Centos x64
>            Reporter: Luke Escude
>            Severity: Minor
>
> In the following console readout, x101 is a device using Opus. You can see that asterisk is correctly measuring jitter (the audio quality was flawless, so jitter is close to 0).
> {quote}
> testbed3*CLI> pjsip show channelstats
>           100-00000001       00:20:20 ulaw    61001       2    0   0.000  61000       0    0   0.005 999.999
>           101-00000003       00:01:20 ulaw      932       0    0   0.000   3890       0    0   0.003 999.999
> testbed3*CLI> pjsip show channelstats
>           100-00000001       00:20:20 ulaw    61034       2    0   0.000  61033       0    0   0.006 999.999
>           101-00000003       00:01:20 ulaw      965       0    0   0.000   3923       0    0   0.003 999.999
> testbed3*CLI> pjsip show channelstats
>           100-00000001       00:20:21 ulaw    61075       2    0   0.000  61074       0    0   0.007 999.999
>           101-00000003       00:01:21 ulaw     1007       1    0   0.000   3965       0    0   0.006 999.999
> testbed3*CLI> pjsip show channelstats
>           100-00000001       00:20:22 ulaw    61105       2    0   0.000  61104       0    0   0.004 999.999
>           101-00000003       00:01:22 ulaw     1036       1    0   0.000   3994       0    0   0.004 999.999
> testbed3*CLI> pjsip show channelstats
>           100-00000001       00:20:22 ulaw    61138       2    0   0.000  61137       0    0   0.005 999.999
>           101-00000003       00:01:22 ulaw     1069       1    0   0.000   4027       0    0   0.005 999.999
> {quote}
> However, the AMI is receiving values that are insanely off:
> {quote}
> 253.0
> 172.0
> 237.0
> etc.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.2#6252)