| Summary: | ASTERISK-15173: Double CDR if unanswered call | ||
| Reporter: | Maciej Krajewski (jamicque) | Labels: | |
| Date Opened: | 2009-11-19 04:10:35.000-0600 | Date Closed: | 2011-06-07 14:08:22 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | CDR/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) asterisk.log | |
| Description: | There is a bug in creating CDR's in unasnwered calls. If the option in cdr.conf "unanswered" is set to "yes" and the call is unanswered when the user is logged (registered) to asterisk there are 2 CDR's - normal one and one strange from s extension (?). In my dialplan there is no S extensions except these to: [ Context 'app_queue_gosub_virtual_context' created by 'app_queue' ] 's' => 1. NoOp() [app_queue] [ Context 'app_dial_gosub_virtual_context' created by 'app_dial' ] 's' => 1. NoOp() [app_dial] However if the user is not registered to Asterisk there is only one CDR created (without s extension). There is a log in attachment | ||
| Comments: | By: David Woolley (davidw) 2009-11-19 06:37:59.000-0600 I believe this is already documented. Setting that option causes the party B CDR to be output as well as the party A CDR. From cdr.conf.sample in 1.6.1.0 ; find this information horribly useless. Others find it very valuable. Note, in "yes" ; mode, you will see one CDR, with one of the call targets on one side, and the originating ; channel on the other, and then one CDR for each channel attempted. This may seem ; redundant, but cannot be helped. By: Maciej Krajewski (jamicque) 2009-11-19 07:22:12.000-0600 ok so the ticket can be closed.... By: Leif Madsen (lmadsen) 2009-11-19 09:34:35.000-0600 Closed per davidw's redirection to documentation. | ||