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

[Michael K. <li...@mk...>]

When you enable full logging in logger.conf and set verbosity to 3 or higher and then analyse the full log file, the calls have a unique call-id „C-xxxxxxxx“. With that you should figure out dialplan issues.

Sent from a mobile device.

Michael Keuter

> Am 26.05.2020 um 01:36 schrieb Michael Knill <mic...@ip...>:
> 
> I have. They are the ones that have told me it's a problem with the queue_log file which I can see it is.
> I'm thinking the problem may be dialplan related rather than Asterisk version related. The COMPLETE records seem to have a different ID to the rest of the call.
> 
> Regards
> Michael Knill
> 
> On 26/5/20, 9:29 am, "Lonnie Abelbeck" <li...@lo...> wrote:
> 
>    Michael, I would try the QueueMetrics folks.
> 
>    https://www.queuemetrics.com/support.jsp
> 
>    Lonnie
> 
> 
>> On May 25, 2020, at 4:36 PM, Michael Knill <mic...@ip...> wrote:
>> 
>> 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
>> _______________________________________________
>> Astlinux-devel mailing list
>> Ast...@li...
>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> 
> 
> 
>    _______________________________________________
>    Astlinux-devel mailing list
>    Ast...@li...
>    https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> 
> 
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel