[asterisk-bugs] [Asterisk 0016559]: [patch] Duration and Billsec Decimal Place

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16559 
====================================================================== 
Reported By:                cianmaher
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16559
Category:                   Addons/cdr_addon_mysql
Reproducibility:            have not tried
Severity:                   feature
Priority:                   normal
Status:                     confirmed
Asterisk Version:           1.6.2.0 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-01-06 14:22 CST
Last Modified:              2010-01-11 18:04 CST
====================================================================== 
Summary:                    [patch] Duration and Billsec Decimal Place
Description: 
My problem at present is I has Sangoma ss7 box, woomera, asterisk1.6.2 and
addons 1.6.2 on a server that is connected to 8 ss7 trunks with other
carriers. I have asterisk writing cdr's to mysql however it appears to
round up always. 

For example:

One of the Carriers reports a call duration of 31.7seconds but we report
it as 33seconds assuming because there is some transit duration of approx
0.4 - 0.5 of a second which brings me to 32.1 or 32.2 but then it is
rounded up to 33.

My questions are:

* Is it possible for asterisk not to round the duration and billsec?
* Is it possible to show duration and billsec with a decimal to show the
true figure?

Thanks in advance

====================================================================== 

---------------------------------------------------------------------- 
 (0116485) snuffy (manager) - 2010-01-11 18:04
 https://issues.asterisk.org/view.php?id=16559#c116485 
---------------------------------------------------------------------- 
As discussed on #asterisk-dev

Best way forward is to modify the backends rather than the hack method.
billsec interpretations from cdr_pgsql added to
cdr_mysql/cdr_adaptive_odbc etc. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-11 18:04 snuffy         Note Added: 0116485                          
======================================================================