[asterisk-bugs] [Asterisk 0016638]: [patch] Update CDR variables that are available, before pbx starts

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16638 
====================================================================== 
Reported By:                alecdavis
Assigned To:                alecdavis
====================================================================== 
Project:                    Asterisk
Issue ID:                   16638
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   tweak
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
JIRA:                       SWP-749 
Regression:                 No 
Reviewboard Link:           https://reviewboard.asterisk.org/r/455/ 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-01-18 15:50 CST
Last Modified:              2010-01-20 03:56 CST
====================================================================== 
Summary:                    [patch] Update CDR variables that are available,
before pbx starts
Description: 
In asterisk 1.6.1 this was done on-hangup, so new fields that were added in
cdr.c:set_one_cid were not seen until after hangup.

Trunk during the hangup, doesn't execute ast_cdr_update anymore, so unless
dialplan code that sets a cdr variable was executed, the variable would not
saved.

First noticed after 'dnid' addition to cdr records.
https://reviewboard.asterisk.org/r/455/
====================================================================== 

---------------------------------------------------------------------- 
 (0116975) alecdavis (developer) - 2010-01-20 03:56
 https://issues.asterisk.org/view.php?id=16638#c116975 
---------------------------------------------------------------------- 
Now during a call, any new cdr variables added in cdr.c:set_one_cid are
filled in, example being the new 'dnid' cdr variable.

test*CLI> core show channel DAHDI/i1/45551234:1234-1
 -- General --
           Name: DAHDI/i1/45551234:1234-1
           Type: DAHDI
       UniqueID: 1263980756.0
       LinkedID: 1263980756.0
      Caller ID: 45551234
 Caller ID Name: (N/A)
    DNID Digits: 8699
       Language: en
          State: Up (6)
          Rings: 1
  NativeFormats: 0x8 (alaw)
    WriteFormat: 0x8 (alaw)
     ReadFormat: 0x8 (alaw)
 WriteTranscode: No
  ReadTranscode: No
1st File Descriptor: 20
      Frames in: 2142
     Frames out: 332
 Time to Hangup: 0
   Elapsed Time: 0h0m43s
  Direct Bridge: <none>
Indirect Bridge: <none>
 --   PBX   --
        Context: incoming
      Extension: 8699
       Priority: 3
     Call Group: 0
   Pickup Group: 0
    Application: VoiceMailMain
           Data: (Empty)
    Blocking in: ast_waitfor_nandfds
      Variables:
CALLEDTON=1
PRIREDIRECTREASON=UNKNOWN
ANI2=0
CALLEDSUBADDR=8690
CALLINGSUBADDR=1234

  CDR Variables:
level 1: dnid=8699
level 1: clid=45551234
level 1: src=45551234
level 1: dst=8699
level 1: dcontext=incoming
level 1: channel=DAHDI/i1/45551234:1234-1
level 1: lastapp=VoiceMailMain
level 1: start=2010-01-20 22:45:56
level 1: answer=2010-01-20 22:45:56
level 1: duration=42
level 1: billsec=42
level 1: disposition=ANSWERED
level 1: amaflags=DOCUMENTATION
level 1: uniqueid=1263980756.0
level 1: linkedid=1263980756.0
level 1: sequence=0 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-20 03:56 alecdavis      Note Added: 0116975                          
======================================================================