Realtime Queue Ringall Strategy Calls With HANGUPCAUSE is 26 and DIALSTATUS is CANCEL

Vinayak · August 3, 2022, 10:42am

What is mean by HANGUPCAUSE is 26 and DIALSTATUS is CANCEL
i have created a ringall strategy queue with 7 members with Local Channel to external mobile number.and im using realtime queue.
Call are not ringing to all members simultaneously , and in queue log the call with HANGUPCAUSE = 26 and DIALSTATUS = CANCEL is not logged. i have logged this manually for every call in dial plan h extension.Pls help me to find a solution

david551 · August 3, 2022, 11:00am

Asterisk queues will cancel all the remaining outgoing calls when one of them answers, or the timeout is reached. In the latter case, depending on the settings, it will typically try to call them again after the configured delay.

For cause codes, see:

https://support.digium.com/s/article/Detailed-ISDN-Cause-Code-List

or any other list of ISDN cause codes.

There are options for CDRs that cause CDRs to be generated for unproductive calls.

github.com

asterisk/asterisk/blob/master/configs/samples/cdr.conf.sample#L21


      
          
          
; Define whether or not to use CDR logging.  Setting this to "no" will override
          ; any loading of backend CDR modules.  Default is "yes".
          ;enable=yes
          
          
; Define whether or not to use CDR logging on new channels by default.
          ; Setting this to "no" will disable CDR on channels unless it is explicitly
          ; enabled. Default is "yes".
          ;channeldefaultenabled=yes
          
          
; Define whether or not to log unanswered calls that don't involve an outgoing
          ; party. Setting this to "yes" will make calls to extensions that don't answer
          ; and don't set a B side channel (such as by using the Dial application)
          ; receive CDR log entries. If this option is set to "no", then those log
          ; entries will not be created. Unanswered Calls which get offered to an
          ; outgoing line will always receive log entries regardless of this option, and
          ; that is the intended behaviour.
          ;unanswered = no
          
          
; Define whether or not to log congested calls. Setting this to "yes" will
          ; report each call that fails to complete due to congestion conditions. Default

Vinayak · August 3, 2022, 11:57am

Im using SIP trunk and i have added

channeldefaultenabled=yes
in cdr.conf, let me check and will reply

Vinayak · August 3, 2022, 12:03pm

Hi,
I missed to mention this.
Reason_Tech is SIP 180 Ringing and Reason_Ast is Normal Clearing

Vinayak · August 3, 2022, 12:12pm

Hi David,
call log is in the cdr table but not in the queue_log table.how can i enable this? any solution.

InterLinked · August 3, 2022, 12:31pm

channeldefaultenabled is a relatively new option that controls whether CDR is done at all, not whether CDRs are generated for “unproductive calls”. If set to no, it will completely disable all CDR unless explicitly enabled on a channel.

I think you are thinking of either the unanswered or congestion settings?

david551 · August 3, 2022, 1:14pm

I slipped up linking to the actual line. I actually intended to point to the unanswered and congestion ones.

Vinayak · August 3, 2022, 3:12pm

Hi,
Both are already enabled, im getting the cdr reports but this is ringall queue and this type of calls are not logged in queue_log table. (agent report)

Vinayak · August 4, 2022, 5:43pm

Hi David,
Any suggestion to resolve this issue?

david551 · August 4, 2022, 5:52pm

I’m not 100% clear what the problem is. The headline issue appears to be normal behaviour to me.

Vinayak · August 4, 2022, 7:25pm

Realtime Queue Ringall Strategy Calls With HANGUPCAUSE is 26 and DIALSTATUS is CANCEL

This type of calls are not inserted into queue_log table as this call is dialed to a queue member in ringall strategy. But these are inserted into the cdr table, why these calls not logging in queue logs for agent reports

david551 · August 4, 2022, 7:52pm

The ones resulting from the timeout and retry cycle are artefacts of how the system works. I think including them would be considered noise. As to the agents who lost the race to answer the call, I think the queue log concentrates more on the client experience than the reaction times of agents. You can infer lazy agents from the lack of calls that they do answer.

Vinayak · August 7, 2022, 4:00am

i have manually logged this into queue_log database using

QueueLog(queuename,uniqueid,agent,event,[additionalinfo])