[Home]

Summary:ASTERISK-21846: RINGNOANSWER event for an agent in queue, but data1 field is null
Reporter:newborn (newborn838)Labels:
Date Opened:2013-05-30 03:49:39Date Closed:2013-06-21 11:16:47
Priority:MajorRegression?
Status:Closed/CompleteComponents:Applications/app_queue
Versions:1.8.21.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:i see events with RINGNOANSWER in queue log table, but data1 field is null. this is not normal, because the timeout in queues.conf is set to 12 sec.

Here is the problem call:
{noformat}
 id   |            time            |     callid      |   queuename    |     agent     |    event     | data1 |      data2      | data3 | data4 | data5
-------+----------------------------+-----------------+----------------+---------------+--------------+-------+-----------------+-------+-------+-------
18357 | 2013-05-22 12:14:59.073579 | 1369210498.1167 | queue1 | NONE          | ENTERQUEUE   |       | 84950000000     | 1     |       |
18358 | 2013-05-22 12:15:01.100576 | 1369210498.1167 | queue1 | SIP/operator4 | RINGNOANSWER | 0     |                 |       |       |
18359 | 2013-05-22 12:15:03.130709 | 1369210498.1167 | queue1 | SIP/operator4 | RINGNOANSWER | 0     |                 |       |       |
18360 | 2013-05-22 12:15:06.47696  | 1369210498.1167 | queue1 | SIP/operator4 | CONNECT      | 7     | 1369210505.1170 | 1     |       |
18363 | 2013-05-22 12:15:20.131533 | 1369210498.1167 | queue1 | SIP/operator4 | TRANSFER     | 0000  | internal     | 7     | 14    | 1
{noformat}
Comments:By: Matt Jordan (mjordan) 2013-05-31 10:51:50.443-0500

Without enough information, there's no way to tell for sure whether or not this is a bug. However, I don't think it is.

The data1 field for a RINGNOANSWER queue entry is the amount of time the agent was rung. It is not a timeout value either for the Queue application or from {{queues.conf}}. Often, these two times *may* be equivalent; however, if a queue member is paused or their channel technology rejects the call immediately, the amount of time they are rung will be nearly 0 (and will be reported as 0 due to rounding).

A debug log would confirm this one way or the other.
By: Rusty Newton (rnewton) 2013-05-31 20:56:46.141-0500

@newborn

As Matt mentioned above, we need a debug log to see what is going on here.

Please provide an Asterisk full log with VERBOSE and DEBUG at level 5 as described here: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

Please attach the log as a .txt file (More Actions > Attach files) and point out the particular call in the log.
By: Rusty Newton (rnewton) 2013-06-21 11:16:39.715-0500

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.  Further information can be found at http://www.asterisk.org/developers/bug-guidelines