Summary:	ASTERISK-05708: Truncated CDR records
Reporter:	Christian Benke (christianbee)	Labels:
Date Opened:	2005-11-25 12:56:34.000-0600	Date Closed:	2011-06-07 14:10:16
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) dialplan_disa.txt ( 1) disacut.sh ( 2) disa-usergroup1.sh ( 3) PROPER_examples_cdr_verboselog.txt
Description:	While parsing my cdrs of the last week, i realized that approx. 1 in 100 _successful_ outbound zap-calls are recorded with a truncated destination number in the verbose logs and in the cdrs. Several digits are simply missing. eg 0049xxxxxxxx is recorded as 0049. I have received cdrs from the telco, and have verified that the "long version" was definitely dialed, and answered. Most of my traffic (99%) is via DISA, and so far this behaviour has only surfaced with outbound DISA calls. I can't be certain that its a DISA only problem, though. I've added the dialplan that applies to these calls(dialplan_disa.txt), the agis that are beeing executed(disa-usergroup1.sh, disacut.sh), samples of verbose logs for wrong numbers, cdr's and corresponding cdr's from my telco(examples_cdr_verboselog.txt). I've upgraded to 1.2 final on 25.11.2000 03:00am in the hope this would be resolved but also today i have faulty records.
Comments:	By: Christian Benke (christianbee) 2005-11-25 13:16:48.000-0600 please review PROPER_examples_cdr_verboselog.txt for the logs and cdr's, the other file is missing information... aint allowed to delete my own attachments :-( also the severity was ment to be major... i'm used to bugzilla, sorry... By: Mark Spencer (markster) 2005-11-25 13:36:41.000-0600 This is not a bug.  The system is behaving precisely correctly.  They're dialing 0049, then we're dialing 0049 out the zap interface, and then they're dialing additional digits which we're sending as overlap dial outbound.  Those are not reflected within the CDR because that's not the called extension.  What you presumably want is to postfix the number with a "w" to force zap to send "number complete" and cause the call to an incomplete number to fail. By: Christian Benke (christianbee) 2005-11-25 14:52:29.000-0600 mark, thanks for looking into this. I have postfixed with "w" and am watching to see if things improve. quite honestly, im not sure i get what i'm doing here, seems the wiki is misleading or incorrect on the usage of w. can you point me to appropriate docu on w? one minor request - can you delete my examples_cdr_verboselog.txt - it's not properly anonymised.... By: Mark Spencer (markster) 2005-11-25 14:55:04.000-0600 "w" would normally indicate a "wait", but putting it at the end of your dialstring will cause asterisk to assume the number before is "complete". By: Christian Benke (christianbee) 2005-11-25 14:59:06.000-0600 mark - thanks a million. you saved my weekend. ill wiki it tomorrow ;-) By: Mark Spencer (markster) 2005-11-25 15:01:38.000-0600 you're welcome.