[asterisk-bugs] [JIRA] Created: (ASTERISK-20165) No CDR when queue call hangs up while ringing agent and 2 or more agents in that queue are busy

[Rusty Newton (JIRA)]

No CDR when queue call hangs up while ringing agent and 2 or more agents in that queue are busy
-----------------------------------------------------------------------------------------------

                 Key: ASTERISK-20165
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20165
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Applications/app_queue
    Affects Versions: 1.8.11.1, 10.6.1
         Environment: Debian
            Reporter: millsu2
            Assignee: millsu2
            Severity: Minor


When a call rings in to a queue with at least one available agent and at least 2 busy agents no CDR record is generated if the caller hangs up while ringing the free agent. I tested this with both 5 and 3 agents in the queue.

It does this regardless if endbeforehexten=yes or endbeforehexten=no. I did not test with unanswered=yes since that will mess up our CDR's.

I can recreate the problem in Asterisk 10.6.1 by creating a queue called 'test', adding 3 queue members through AddQueueMember, making 2 of them busy by calling an outside line or calling each other, then putting a call in the queue. The queue will ring the free agent. While it is ringing, before the agent answers, the queue caller hangs up.
At this point a CDR should be created for this call in all configured cdr back ends, but none is created either in the CSV file, the pgsql database or throguh odbc to pgsql.

While gathering the logfile data, I noticed it was trying to log only to sqlite, which I didn't know was enabled.I checked that db file and the CDR's were correctly logged there. I turned off sqlite and tested again, but the CDR is now not logged anywhere.

The attached debug log was done on a test machine with no activity so it mostly only includes info about the specific call (timestamp: Jul 20 14:30:38)



--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira