|Summary:||ASTERISK-20068: CDR(dst) is set to s when destination is BUSY on AMI Originate|
|Reporter:||Sebastian Gutierrez (sum)||Labels:|
|Date Opened:||2012-06-28 08:15:02||Date Closed:|
|Versions:||10.5.0 13.9.1||Frequency of|
|Environment:||Attachments:||( 0) full.zip|
|Description:||After an AMI Originate that has the BUSY response (cdr.conf with unanswered=yes) CDR(dst) is set with s instead of the called number|
|Comments:||By: Rusty Newton (rnewton) 2012-06-28 19:59:23.408-0500|
Can you provide full log, VERBOSE and DEBUG level 5 covering the time the originate occurs and when the CDR would have been populated?
By: Sebastian Gutierrez (sum) 2012-06-29 06:59:26.441-0500
attached full log with some busy calls generated via ami
By: Sebastian Gutierrez (sum) 2012-06-29 06:59:56.266-0500
By: Sebastian Gutierrez (sum) 2012-07-04 13:36:20.188-0500
any update on this?
By: Sebastian Gutierrez (sum) 2012-07-09 13:40:44.875-0500
can anyone point me in the right direction where in the code this cdr is build so I can try to make a patch to get the CDR(dst) correct.
By: Sebastian Gutierrez (sum) 2012-09-17 14:36:47.120-0500
By: Sebastian Gutierrez (sum) 2016-06-01 19:54:30.177-0500
this is still happening today on ast 13
By: Sebastian Gutierrez (sum) 2016-10-30 13:58:44.374-0500
is this expected? could someone point me in the right direction to where to look at the code?
By: Joshua C. Colp (jcolp) 2016-10-30 14:03:03.175-0500
This is in queue to be looked into, there's no updates on it. The CDR code is self contained in main/cdr.c and the AMI code for origination would be in main/manager.c. I don't really know in any deeper level where exactly to look.