[asterisk-bugs] [Asterisk 0013728]: After upgrading to 1.4.22 from 1.4.21.1 CDRs behave wrongly
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Oct 27 15:13:52 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=13728
======================================================================
Reported By: hesser
Assigned To: murf
======================================================================
Project: Asterisk
Issue ID: 13728
Category: CDR/General
Reproducibility: always
Severity: major
Priority: normal
Status: feedback
Asterisk Version: 1.4.22
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2008-10-17 09:31 CDT
Last Modified: 2008-10-27 15:13 CDT
======================================================================
Summary: After upgrading to 1.4.22 from 1.4.21.1 CDRs behave
wrongly
Description:
After the upgrade I am no longer able to set userfield nor accountcode
variables in the CDR for my SQL backend. CSV does not work either. Also,
there are no 2 identical call records in the database, whereas before,
there were 2 individual records.
I am using the external interface to create a call from the from-internal
context. Once the call is answered, it passes it to a context in extensions
conf.
In there I am using exten => queue1,2,Set(CDR(accountcode)= "1234").
That used to set the record properly. It no longer does. I looked at the
cdr.c in main and there are changes in regards to locked records, etc. I
think that is where the issue comes from. Why were these changes
implemented?
Kind regards
Holger
======================================================================
----------------------------------------------------------------------
(0094315) hesser (reporter) - 2008-10-27 15:13
http://bugs.digium.com/view.php?id=13728#c94315
----------------------------------------------------------------------
Hi Murf.
here are your answers ( I hope ).
Here is the manager interface call.
$TelnetClient->print ("Action: Originate");
$TelnetClient->print ("Channel: $final");
$TelnetClient->print ("Context: from-trunk-customer");
$TelnetClient->print ("Priority: 1");
$TelnetClient->print ("Exten: $dest");
$TelnetClient->print ("Callerid: \"Intervoice\" <xxxxxxxxx>");
There is no queue app involved. ( just bad naming)
It fails for both SIP and IAX2.
The dialplan is the standart one coming from amportal.
By just changing out the versions of asterisk I can make it fail.
Let me know if you need a full log.
Thanks
Holger
Issue History
Date Modified Username Field Change
======================================================================
2008-10-27 15:13 hesser Note Added: 0094315
======================================================================
More information about the asterisk-bugs
mailing list