Exceptionally long voice queue length queuing to
![exceptionally long voice queue length queuing to exceptionally long voice queue length queuing to](https://www.mog-technologies.com/wp-content/uploads/2021/09/pr-crowd-journalism-mog-swisstxt.png)
(AST_CONTROL_SRCCHANGE), and at 50pps this builds up a lot of events fast and so if the Wait is high the issue pops up (I agree having a channel on Wait for too long is not a good practice but noone is perfect…). The problem with 2 streams is that each RTP package of the new stream generates a source change frame I could not find any ticket for such bug, but version 16.8.0 does not have this problem and instead seems to inject the Music on Hold in the existing RTP stream so there aren’t 2 streams at the same time to the same destination.
![exceptionally long voice queue length queuing to exceptionally long voice queue length queuing to](https://www.mdpi.com/sensors/sensors-21-03568/article_deploy/html/images/sensors-21-03568-g018-550.jpg)
This happens when an old Asteriskġ3.13.0 receives a hold REINVITE and starts a new RTP stream (with different SSRC) towards some other victim Asterisk with the Music on Hold while still sending the original caller RTP (so at this point 2 RTP streams with different SSRCs are sent to the destination that happens to be a channel currently on Wait). My production case is a little more complex and happens while on Wait and with the AST_CONTROL_SRCCHANGE event. It is not really common to get a lot of “deferrable frames” (see ast_is_deferrable_frame) but we can have that by simply putting on hold and off hold while the channel is on “wait”. So, what I discovered is that in case the diaplan has a Wait() and during this wait period many “deferrable frames” are received, the final piece of the Wait function (ast_safe_sleep_conditional) can throw the “Exceptionally long queue length queuing” error message. I’ve also recently faced this “Exceptionally long queue length queuing”Įrror in some servers running 16.8.0 and after A LOT of investigation, I’ve discovered what is causing it in my case (not sure if is the same case as initially reported by Dovid)
![exceptionally long voice queue length queuing to exceptionally long voice queue length queuing to](https://media.springernature.com/lw785/springer-static/image/chp%3A10.1007%2F978-0-387-73699-0_4/MediaObjects/978-0-387-73699-0_4_Fig11_HTML.jpg)
I am going to open a ticket for this issue but I found it useful to already explain it here. Sorry for the long email but I tried to explain all I’ve seen regarding this issue….