[asterisk-bugs] [JIRA] (ASTERISK-21144) One way audio after channels are AMI Bridged out of a ConfBridge that has jitterbuffer=yes

[Rusty Newton (JIRA)]

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

Rusty Newton commented on ASTERISK-21144:
-----------------------------------------

ASTERISK-23812 is likely a duplicate of this issue, but occurring in a different scenario.

> One way audio after channels are AMI Bridged out of a ConfBridge that has jitterbuffer=yes
> ------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21144
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21144
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_confbridge, Core/Bridging, Resources/res_rtp_asterisk
>    Affects Versions: 11.2.1, 11.3.0
>         Environment: CentOS6 2.6.32-279.19.1.el6.x86_64
>            Reporter: William luke
>         Attachments: debug-jitter.rar
>
>
> confbridge.conf has "jitterbuffer=yes"
> To reproduce this issue, redirect two channels into a ConfBridge, using the above profile.
> All is fine, audio flows correctly.
> Now use the AMI to Bridge these channels. One way audio. "rtp set debug on", agrees and only shows rtp being processed in one direction.
> If "jitterbuffer=no" is set, then two way audio after the Bridge.
> Seems that the jitterbuffer is preventing rtp frames from passing accross the bridge.
> In my case the two channels are SIP. There are no SIP reinvites etc going on. directmedia=no is set.
> I've tried with same codec (so it uses the sip native bridge), and also with different codecs (the generic bridge?); same results.



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