Summary:	ASTERISK-00645: CDR "dst" field is not updating properly
Reporter:	Ricardo Villa (ricvil)	Labels:
Date Opened:	2003-12-09 20:42:12.000-0600	Date Closed:	2011-06-07 14:10:49
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	We updated to latest CVS yesterday: =>>>Asterisk CVS-12/08/03-23:49:34 built by root@wailea on a i686 running Linux ...and the cdr_addon_mysql application stopped updating the CDRs properly.  If after the user hangups you have things happening under the "h" type extension then "h" is what will appear under the "dst" field of the CDR. For example: [local-gw] exten => _01XXXXXXXXXX,1,Dial(Zap/1/${EXTEN:2}) exten => h,1,SetVar(MONITORDIR=/var/spool/asterisk/monitor) exten => h,2,GotoIf($[${CALLFILENAME} = ${FOO}]?6:3) exten => h,3,NoOp exten => h,6,NoOp will generate an entry like this in MySQL (note 4th field): | 2003-12-09 21:21:34 | 1002 | 1002 | h            | local-gw              | IAX2[pbxmaui@pbxmaui]/1 | Zap/1-1    | NoOp     |              |        6 |       2 | ANSWERED    |        3 |             |          | If we remove the "h" extension type then the CDR is recorded normally.  This proplem does not happen with CVS from Nov 15.
Comments:	By: Ricardo Villa (ricvil) 2003-12-09 20:46:43.000-0600 And by the way...the same problem happens to the flat file CDRs in the "Master.csv" file By: Brian West (bkw918) 2003-12-10 00:12:55.000-0600 exten => h,1,SetVar(MONITORDIR=/var/spool/asterisk/monitor) exten => h,2,ResetCDR(w) exten => h,3,GotoIf($[${CALLFILENAME} = ${FOO}]?6:4) exten => h,4,NoOp exten => h,6,NoOp Its not a bug.. just a config problem. By: Brian West (bkw918) 2003-12-10 00:13:08.000-0600 Local config issue.