[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 17:19:22 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 17:19 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 ...
======================================================================
----------------------------------------------------------------------
(0099165) dzajro (reporter) - 2009-01-30 17:19
http://bugs.digium.com/view.php?id=13892#c99165
----------------------------------------------------------------------
And last thing, sorry for my note from 2009-01-09, meanwhile I forgot
crashes :-(.
With 13892.patch, unaswered=yes and call to number released by PSTN with
0x01 => crash:
---------------------------------------------------------------------------
rogram received signal SIGSEGV, Segmentation fault.
[Switching to Thread 78375840 (LWP 26303)]
0x00a6ae2f in dial_exec_full (chan=0x8c1d318, data=Variable "data" is not
available.
) at app_dial.c:1449
1449 if
(strcmp(o->chan->cdr->dstchannel, chan->cdr->dstchannel) == 0) {
(gdb) bt
http://bugs.digium.com/view.php?id=0 0x00a6ae2f in dial_exec_full
(chan=0x8c1d318, data=Variable "data" is
not available.
) at app_dial.c:1449
http://bugs.digium.com/view.php?id=1 0x00a6d3e4 in dial_exec (chan=0x0,
data=0xffffffff) at
app_dial.c:1869
http://bugs.digium.com/view.php?id=2 0x080cafb0 in pbx_extension_helper
(c=0x8c1d318, con=Variable "con" is
not available.
) at /usr/src/asterisk/asterisk-1.4.22/include/asterisk/strings.h:35
http://bugs.digium.com/view.php?id=3 0x080cb4fa in ast_spawn_extension (c=0x0,
context=0xffffffff <Address
0xffffffff out of bounds>,
exten=0xffffffff <Address 0xffffffff out of bounds>, priority=-1,
callerid=0xffffffff <Address 0xffffffff out of bounds>)
at pbx.c:2317
http://bugs.digium.com/view.php?id=4 0x00142ff6 in _macro_exec (chan=0x8c1d318,
data=Variable "data" is not
available.
) at app_macro.c:308
http://bugs.digium.com/view.php?id=5 0x080cafb0 in pbx_extension_helper
(c=0x8c1d318, con=Variable "con" is
not available.
) at /usr/src/asterisk/asterisk-1.4.22/include/asterisk/strings.h:35
http://bugs.digium.com/view.php?id=6 0x080cf766 in __ast_pbx_run (c=0x8c1d318)
at pbx.c:2317
http://bugs.digium.com/view.php?id=7 0x080d162e in pbx_thread (data=0x8c1d318)
at pbx.c:2621
http://bugs.digium.com/view.php?id=8 0x08101835 in dummy_start
(data=0xffffffff) at utils.c:912
http://bugs.digium.com/view.php?id=9 0x0074b3cc in start_thread () from
/lib/tls/libpthread.so.0
http://bugs.digium.com/view.php?id=10 0x006a41ae in clone () from
/lib/tls/libc.so.6
Issue History
Date Modified Username Field Change
======================================================================
2009-01-30 17:19 dzajro Note Added: 0099165
======================================================================
More information about the asterisk-bugs
mailing list