Re: [Astlinux-devel] Call completion in queuelog problem with Asterisk 13.29.2

[Michael K. <mic...@ip...>]

Ok another heads up, I'm pretty confident this is not a bug but more how I do my dial plan.
I am actually getting the COMPLETECALLER or COMPLETEAGENT records in the queue_log file however the Unique ID is different to the rest of the queue call which is confusing QueueMetrics.
After looking through CDR records, the final Unique ID matches my initial IVR call. The way I have my dial plan set up is that I use Local channels between subroutines for each dial plan function e.g. IVR, Queue. All local channels are currently set up to optimise out which from memory causes additional CDR records with different Unique ID's when this happens.
I suspect this problem may be resolved by not optimising out my Local channels. Time to test in the lab.

Regards
Michael Knill

From: Michael Knill <mic...@ip...>
Reply to: AstLinux Developers Mailing List <ast...@li...>
Date: Tuesday, 26 May 2020 at 7:37 am
To: AstLinux Developers Mailing List <ast...@li...>
Subject: [Astlinux-devel] Call completion in queuelog problem with Asterisk 13.29.2

Just a heads up. Since upgrading to Asterisk 13.29.2, this has fixed my Asterisk crash problem but now has caused a problem with QueueMetrics whereby the COMPLETEAGENT or
COMPLETECALLER records are not in the queuelog. This means that QueueMetrics now does not know when the call has been completed and you end up with long duration calls until it removes them as erroneous.

I cant find any bugs on this and have posted on the Asterisk Community.

Grrr

Regards
Michael Knill