[asterisk-users] billsec exceeds duration on some calls

[Tilghman Lesher]

On Wednesday 11 August 2010 11:51:10 Tim Nelson wrote:
> ----- "Tilghman Lesher" <tlesher at digium.com> wrote:
> > On Wednesday 11 August 2010 03:59:28 A J Stiles wrote:
> > > I'm having a problem with Asterisk 1.6.2.9 with the MySQL cdr
> >
> > addon.
> >
> > > With some calls, the value in the `billsec` field in the CDR is
> >
> > exceeding
> >
> > > the value in the `duration` field.
> > >
> > > I didn't think this was supposed to happen?  Our old installation
> >
> > (some
> >
> > > ancient version, sorry not available)  always had `billsec` <=
> >
> > `duration`.
> >
> > > The problem does not seem to be evenly distributed among
> >
> > extensions.
> >
> > > If you need any additional information, please let me know.
> >
> > I'd love to know what circumstance caused that.  I agree that this
> > should not
> > occur.
>
> Can call waiting, on hold, or three way calls cause this? Just a stab in
> the dark...

No, duration and billsecs are derived values from 3 timestamps:  start,
answer, and end.  The only way for billsecs to be higher than duration would
be for the answer to be earlier than the start.

Just thought of a possible cause.  If the difference is only a second, then
the setting initiatedseconds=yes could cause this.  This is because duration
is a simple subtraction of end minus start, and any fraction of seconds is
discarded.  Similarly, billsec is normally end minus answer, but with this
setting, any fraction of seconds increments the second count.

-- 
Tilghman Lesher
Digium, Inc. | Senior Software Developer
twitter: Corydon76 | IRC: Corydon76-dig (Freenode)
Check us out at: www.digium.com & www.asterisk.org