[asterisk-bugs] [Asterisk 0013892]: After upgrading from 1.4.21.2 to 1.4.22 unaswered calls aren't correctly saved as CDR
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Jan 30 15:12:18 CST 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=13892
======================================================================
Reported By: dzajro
Assigned To: murf
======================================================================
Project: Asterisk
Issue ID: 13892
Category: CDR/General
Reproducibility: always
Severity: major
Priority: normal
Status: ready for testing
Asterisk Version: 1.4.22
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2008-11-12 17:11 CST
Last Modified: 2009-01-30 15:12 CST
======================================================================
Summary: After upgrading from 1.4.21.2 to 1.4.22 unaswered
calls aren't correctly saved as CDR
Description:
Call from SIP extension into PSTN via Zap to non-existing number. PSTN is
correctly returning unassigne/unallocated number.
-- Executing [s at macro-to-pstn-4:3] Dial("SIP/421232660232-0a2d22d8",
"Zap/g4/421230123123") in new stack
-- Requested transfer capability: 0x00 - SPEECH
-- Called g4/421230123123
-- Zap/1-1 is proceeding passing it to SIP/421232660232-0a2d22d8
-- Channel 0/1, span 1 got hangup request, cause 1
-- Hungup 'Zap/1-1'
== Everyone is busy/congested at this time (1:0/0/1)
With 1.4.21.2 and "unanswered = no" in cdr.conf * produces following CDR:
src=421232660232
dst=421230123123
channel=SIP/421232660232-xxx
dstchannel=Zap/1-1
duration=0
billsec=0
disposition=NO ANSWER
1.4.21.2 with "unanswered = yes" produces the same PLUS (the are 2 CDR for
the same call, with the same call_date):
src=421232660232
dst=s
channel=Zap/1-1
dstchannel=
duration=0
billsec=0
disposition=NO ANSWER
With 1.4.22 and "unanswered = no" system produces NO CDR
With 1.4.22 and "unanswered = yes" system produces only ONE CDR:
src=
dst=s
channel=Zap/1-1
dstchannel=
duration=0
billsec=0
disposition=NO ANSWER
This CDR is unusable for billing/documentary purpose, there's NO SRC, no
real channel.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0011849 Missing CDR's for Transfers
related to 0013691 [patch] Unanswered Queue() calls don't ...
======================================================================
----------------------------------------------------------------------
(0099153) murf (administrator) - 2009-01-30 15:12
http://bugs.digium.com/view.php?id=13892#c99153
----------------------------------------------------------------------
Oh, just to report on the d2.dig1 patch;
If the extension isn't found on the target system, on the calling system,
you get this CDR:
(for reference, use cdr_custom.conf to see what fields are listed, and in
what order; in the following DAHDI/51 is a regular fxs extension; DAHDI/10
and DAHDI/13 are in a T1 set that have the same names in both the calling
and the called systems... Dahdi/25 is the device you get when you call 125
on the called system; and 'unanswered=no' on the called system)
""fxs.51"
<151>","151","303","extension","DAHDI/51-1","DAHDI/13-1","Dial","Dahdi/13/1800|30|TtWwHhKkXx","2009-01-30
13:07:24","","2009-01-30
13:07:30","6","0","FAILED","DOCUMENTATION","","1233346044.6","",""
and on the called system, you get this report (assuming you have
callattempts=yes set in the [general] section of cdr.conf):
""fxs.51"
<151>","151","1800","t1incoming","DAHDI/13-1","<unknown>","","","2009-01-30
13:07:22","","2009-01-30
13:07:22","0","0","FAILED","DOCUMENTATION","","1233346042.x0","",""
if you haven't got callattempts = yes set, then you get nothing (but a
message on the console if you turn verbosity high enough)
Now, if you call a legal exten on the target system, but that device is
gone/not working or whatever, you get this on the calling system:
""fxs.51"
<151>","151","302","extension","DAHDI/51-1","DAHDI/10-1","Dial","Dahdi/10/180|30|TtWwHhKkXx","2009-01-30
13:46:27","","2009-01-30 13:46:34","7","0","NO
ANSWER","DOCUMENTATION","","1233348387.10","",""
and you get this on the called system: (Dahdi/80 doesn't exist)
""fxs.51"
<151>","151","180","t1incoming","DAHDI/10-1","Dahdi/80","Dial","Dahdi/80|30|eTtWwKkHhXx","2009-01-30
13:46:25","","2009-01-30
13:46:29","4","0","FAILED","DOCUMENTATION","","1233348385.1","",""
when you dial a legal exten via PRI you will get:
(on the calling system)
""fxs.51"
<151>","151","301","extension","DAHDI/51-1","DAHDI/10-1","Dial","Dahdi/10/125|30|TtWwHhKkXx","2009-01-30
13:58:52","2009-01-30 13:59:04","2009-01-30
13:59:09","17","5","ANSWERED","DOCUMENTATION","","1233349132.12","",""
(on the called system)
""fxs.51"
<151>","151","125","t1incoming","DAHDI/10-1","DAHDI/25-1","Dial","Dahdi/25|30|eTtWwKkHhXx","2009-01-30
13:58:53","2009-01-30 13:59:00","2009-01-30
13:59:04","11","4","ANSWERED","DOCUMENTATION","","1233349133.2","",""
And, when the pone on the called system doesn't answer, you get:
(on the calling system)
""fxs.51"
<151>","151","301","extension","DAHDI/51-1","DAHDI/10-1","Dial","Dahdi/10/125|30|TtWwHhKkXx","2009-01-30
14:01:03","","2009-01-30 14:01:36","33","0","NO
ANSWER","DOCUMENTATION","","1233349263.14","",""
and on the called system, we see:
""fxs.51"
<151>","151","125","t1incoming","DAHDI/10-1","DAHDI/25-1","Dial","Dahdi/25|30|eTtWwKkHhXx","2009-01-30
14:01:00","","2009-01-30 14:01:32","32","0","NO
ANSWER","DOCUMENTATION","","1233349260.4","",""
Issue History
Date Modified Username Field Change
======================================================================
2009-01-30 15:12 murf Note Added: 0099153
======================================================================
More information about the asterisk-bugs
mailing list