search for: finalized_state_fn_table

...record is sent to the cdr backend later. Unfortunately, it is not modifiable from the "h" extension, because the cdr_object is already in the finalized table. Is there a way how to modify the CDR without hacking the code? How bad idea is it to comment the (it_cdr->fn_table == &finalized_state_fn_table) tests in ast_cdr_setuserfield and ast_cdr_setvar and thus allow the "h" extension write to a finalized CDR? Is there any chance the feature was left out by an accident and if so, is there a plan to add it again? My extensions.conf: exten => h,1,NoOp(${CDR(userfield)}) exten =>...

...h" extension, because the cdr_object is already in >> the finalized table. >> >> Is there a way how to modify the CDR without hacking the code? >> >> > Unfortunately, no. > > >> How bad idea is it to comment the (it_cdr->fn_table == >> &finalized_state_fn_table) tests in ast_cdr_setuserfield and ast_cdr_setvar >> and thus allow the "h" extension write to a finalized CDR? >> >> > Well... I'm not sure :-) > > As the guy who signed himself up for the dubious honour of porting the CDR > code to Asterisk 13 - and try...

Hi, I'm trying to migrate from Asterisk 1.8 to Asterisk 13 and can't figure this one out. I'm pretty sure the question has been already asked, but I failed to find a solution. Can you modify CDR values in an h-extension? My cdr.conf contains: [general] enable=yes unanswered=yes endbeforehexten=yes initiatedseconds=no batch=no The diaplan contains a simple "h" extension