| Summary: | ASTERISK-01851: Overlap digits not stored in the cdr | ||
| Reporter: | petersv (petersv) | Labels: | |
| Date Opened: | 2004-06-19 09:36:19 | Date Closed: | 2004-09-25 02:42:33 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Overlap digits are not stored in the cdr, just the part of the number that was needed to initiate the dial. I tried adding the numbers to the chan->exten storage but that did not get carried back to the ast_cdr_update call in pbx.c since our Dial:s are run in a macro and therefore in a spawn extension. At least I think that is why it failed. Any ideas as how this could be implemented? | ||
| Comments: | By: Mark Spencer (markster) 2004-06-19 13:56:28 Asterisk begins the CDR once ast_pbx_run begins. There is no mechanism after that to update the CDR because (from the perspective of Asterisk) the call has been started at that point. It's conceivable that you could try keep updating the CDR until PROGRESS is received, but I'm not sure how much I like that idea -- especially outside the realm of ISDN and it would take a lot of work to do. Of course in the mean time you can always just turn off overlap dial on the outbound and use a global matching rule (e.g. exten => _0.,1,Dial(Zap/${EXTEN:1}) | ||