[asterisk-bugs] [JIRA] (ASTERISK-27385) channel.c: Exceptionally long queue length queuing

[Benjamin Keith Ford (JIRA)]

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

Benjamin Keith Ford commented on ASTERISK-27385:
------------------------------------------------

Hey [~agupta], I just tested adding 2 channels that called into the application via Stasis to a simple bridge and the bridge type changes to native_rtp. Both users can hear one another and no WARNING message appears. This was done on 13 branch. I created the bridge with client.bridges.create(bridgeId='bridgeName'). This is what you are doing to produce the WARNING message, correct?
If you enter 'module show like bridge' on the Asterisk CLI, what is the output? Before and after the interaction with ARI?

> channel.c: Exceptionally long queue length queuing
> --------------------------------------------------
>
>                 Key: ASTERISK-27385
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27385
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Bridging
>    Affects Versions: 13.17.2
>         Environment: Ubuntu 16.04 with asterisk 13.17.2 using Staisis 
>            Reporter: Abhay Gupta
>            Assignee: Unassigned
>         Attachments: abhay.txt, asterisk logs.txt, asterisk_top.png, core-asterisk-running-2017-11-08T12-30-19+0530-brief.txt, core-asterisk-running-2017-11-08T12-30-19+0530-full.txt, core-asterisk-running-2017-11-08T12-30-19+0530-locks.txt, core-asterisk-running-2017-11-08T12-30-19+0530-thread1.txt, full, gdb.txt, pjsip_settings.txt, server_info.txt, stasis.conf, stucked_call.txt, task_noproblem.txt, taskprocessors
>
>
> Asterisk becomes unstable with message like 
> [Oct 31 10:37:37] WARNING[5608][C-00001b6b] channel.c: Exceptionally long queue length queuing to Local/2048 at sxxxxxxg-000016ba;1
> There are two staisis customer-dial and agent-dial . The steps seems to be as follows 
> 1. A Sip channel is added in customer-dial 
> 2. A manager originate command adds a channel between customer-dial and agent-dial while the existing channel is hanging up in customer-dial 
> 3. Both channels of customer-dial are bridged while some clearing is happening on the channel which is getting hangup / deleted .
> This problem appears 



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