[asterisk-bugs] [JIRA] (ASTERISK-17776) No CDR record is generated if caller hangs up while in Queue and members are busy. Reproduced in 1.8 and 1.6 as well.

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-17776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198984#comment-198984 ] 

Matt Jordan commented on ASTERISK-17776:
----------------------------------------

A patch is going to be committed to Asterisk trunk (which will become version 12) that modifies the behaviour of CDRs to account for some of the situations described in this issue.  We debated doing this in Asterisk 1.8, but in general modifying the behaviour of CDRs in release branches has caused more problems than its solved.

The behaviour in Asterisk 12+ will be:
* If no queue members are paused, the CDR result is whatever the result was prior to going into app_queue.  If the call was answered, this is ANSWERED; otherwise, it is NO ANSWER.
* If some queue members are paused and the caller is never answered, the result is NO ANSWER (prior behaviour: BUSY).
* If all queue members are paused, the CDR result is again whatever the result was prior to going into app_queue.
* If the caller hangs up, times out, or presses '*' with the 'h' option, the result is again not set.

In general, we've kept the modifications as minor as possible and fixed the only truly glaring weirdness, which was that queue members being paused (but not all) caused the disposition to be BUSY.

I don't expect any additional modifications to CDR behaviour to be made, given how difficult it is to get concurrence on CDR behaviour in Queues.  As such, I'm going to close this issue out as "Fixed" - for as much as we can ever "Fix" these kinds of issues.
                
> No CDR record is generated if caller hangs up while in Queue and members are busy. Reproduced in 1.8 and 1.6 as well.
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-17776
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-17776
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Applications/app_queue
>    Affects Versions: 1.8.3
>            Reporter: Attila Megyeri
>
> SIP endpoint (SIP/oatest01) is added as member to Queue "oatest" with penalty 1.
> Sip endpoint oatest01 is Busy (talking).
> A new call is inserted into queue "oatest".
> Console says
>     -- Got SIP response 486 "Busy Here" back from <Masked IP>
>     -- SIP/oademo01-00000043 is busy
> Caller hangs up.
> No CDR record is  created either in the DB or in the file system.
> In other words, NO INFO at all about a missed call...
> ****** ADDITIONAL INFORMATION ******
> Very simple to reproduce.
> Create a queue
> -----
> [oademo]
> strategy=rrmemory ;ringall
> context=oademo-voicemail
> setinterfacevar=yes
> setqueuevar=yes
> updatecdr=yes
> ringinuse=no
> joinempty=no
> membermacro=oademo-member
> ----------
> Add a member to a queue, with penalty 1
> ----
> queue add member SIP/oademo01 to oademo penalty 1
> ----
> Make the member busy (has a call).
> Enqueue a call into the queue:
> exten => 223344,1,      NoOp(Queue CDR debug extension)
> exten => 223344,n,      Ringing()
> exten => 223344,n,      Wait(1)
> exten => 223344,n,      Answer()
> exten => 223344,n,      Queue(oademo,R,,,240)
> Disconnect the call that is waiting in the queue.
> Check the CDR - there will be no track of the call.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira