| Summary: | ASTERISK-20332: Missing CDR rows on Abandon queue event | ||
| Reporter: | Mario (susu) | Labels: | |
| Date Opened: | 2012-08-29 08:16:25 | Date Closed: | 2012-09-06 10:12:53 |
| Priority: | Critical | Regression? | Yes |
| Status: | Closed/Complete | Components: | CDR/General |
| Versions: | Frequency of Occurrence | Frequent | |
| Related Issues: | |||
| Environment: | Unix Centos | Attachments: | |
| Description: | Sometime when a caller abandon a queue, CDR does not write the row. If I put the "unanswered = yes" option on cdr.conf, it works, but I've (obviously) more than a row per call (# of row= # of busy agents on the queue, and this is correct). I've read that this bug affected also previous version of Asterisk. Is there a patch? | ||
| Comments: | By: Matt Jordan (mjordan) 2012-09-06 10:12:53.743-0500 With unanswered=no, CDR records are only written if a party B is also involved in the call. With unanswered=yes, calls that do not have a party B are also recorded. If a caller abandons a queue and no one has answered, then the expected behavior is that nothing will get written to the CDR unless you have unanswered=yes. Note that there are other bugs regarding CDRs in queues; those may or may not get fixed in a new version of Asterisk. However, to not perturb existing systems, the behavior is not going to be modified in current release branches. | ||