[asterisk-dev] AMI events in Asterisk 16.1 happening 26+ seconds after parking a call.

[Kevin Harwell]

On Fri, Dec 28, 2018 at 3:56 PM Steve Sether <ssether at usinternet.com> wrote:

> On Thur, Dec 20, 2018 at 10:57 AM Kevin Harwell <kharwell at digium.com> <kharwell at digium.com>
>
> > Have you tested, or currently running with the exact same setup but with
> > another version of Asterisk and you are not seeing the delay?
>
> I tested Asterisk 13.20 under the same dialplan and config, and I couldn't replicate the problem after a good 10-15 attempts. When I switched back to 16.1 I could replicate it multiple times after 2-3 attempts.
>
> Asterisk 11 is problematic since parking is of course quite different, but we've had no problems like this in several years of using the same dialplan, and some minor config changes with 16.
>
> Sounds like a possible bug could have been introduced. Does this happen at
all under 13 (like a more recent version, 13.24.0 for instance)? Or just in
16? If you are willing and able you could try using 'git bisect' on the
branch in question to try and track down exactly what patch introduced the
problem.

> What's the exact test scenario you are running?
>
> Probably more complicated than is worth getting into.  By simple, I meant merely monitoring AMI output, not the dialplan or Asterisk config.  So the delay isn't being caused by the component connected to the AMI.  I'll work on trying to provide a simple scenario with a simple dialplan next week that's easy to replicate, or at least figure out if there's something specific to our setup that causes this.
>
> A basic scenario and/or simple description on how to replicate it would be
most helpful.


> > After 'n' seconds of park time are you sending the call back to the dialplan
>
> We do do this, but I set the timeout to 10 minutes so it wouldn't interfere with my testing.  The delays I'm seeing are more like 30 seconds to a minute, and happen before the call gets sent back to the return_context I set in ParkAndAnnounce.
>
>
Based on the fact it was working before in a previous version with no
change to configuration makes it sound like a bug to me. If you'd like you
can file a bug report on the Asterisk issue tracker [1]. Please read over
the guidelines [2] on how to do that if you haven't already, and be sure to
include a full debug log [3], along with the AMI output. Also any relevant
configuration you can share would be helpful as well.

[1] https://issues.asterisk.org/
[2] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines
[3] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

Thanks!
-- 
Kevin Harwell
Digium - A Sangoma Company | Senior Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
Check us out at: https://digium.com & https://asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20190107/a22e7946/attachment.html>