[asterisk-bugs] [JIRA] (ASTERISK-25446) Warnings with jitter buffer enabled and transcoding from G722 to ulaw

[Eli Hunter (JIRA)]

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

Eli Hunter commented on ASTERISK-25446:
---------------------------------------

I've found that removing the jbforce=1 line stops the warnings from showing.  I did have reports of call quality issues from multiple users while this was enabled however I'm not sure it was this. It's producing somewhere around 40-50 warnings per second for each active call which seems excessive.

I'll work on getting a debug of this.

> Warnings with jitter buffer enabled and transcoding from G722 to ulaw
> ---------------------------------------------------------------------
>
>                 Key: ASTERISK-25446
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25446
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Codecs/General
>    Affects Versions: 11.19.0
>         Environment: Centos 6.5 x64
>            Reporter: Eli Hunter
>            Assignee: Eli Hunter
>            Severity: Minor
>         Attachments: codecs.conf, sample_sip.conf
>
>
> This is the same as ASTERISK-24424. 
> I'm seeing this issue with Polycom endpoints using G722 with ulaw at the other end after enabling the jitter buffer on Asterisk 11.19.
> WARNING[11984][C-0000076d]: abstract_jb.c:284 ast_jb_put: SIP/18-RST-000019c7 received frame with invalid timing info: has_timing_info=0, len=20, ts=17140, src=slin 8000khz -> 16000khz
> The only options in my rtp.conf are
> rtpstart=10000
> rtpend=20000
> sip.conf and codecs.conf are attached



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