[OpenSIPS-Users] Maybe it's a bug

Daniel Zanutti daniel.zanutti at gmail.com
Tue Jun 9 23:27:21 EST 2020

Hi folks

We implemented millisecond billing in our platform, so no need to round on
the Opensips layer, the rounding is done in our business billing layer.
This way customers can have a different rounding than VoIP providers. It's
not a way to penalize customers, but some providers just work differently
than others and you cannot demand them to work "your way".

I suggest store a float (instead of integer) with milliseconds included OR
an option to store milliseconds on a separated column.


On Tue, Jun 9, 2020 at 4:45 PM Calvin Ellison <calvin.ellison at voxox.com>

> +1 to ceil() rounding, and stating in the documentation that this is
> the method used. Alternatively, some new option to specify ceiling,
> floor, round, truncate, etc.
> I can back up SM's claim that a single billing interval discrepancy
> will cost people real money. Clarification in the documentation will
> help people avoid that pitfall. I also concur with Vlad that the
> duration in milliseconds is preferable. The millisecond data can help
> to settle any billing disputes from clients or vendors, and it
> demystifies CDRs for everyone: one field for actual call duration in
> ms, another field for call duration after rounding, and/or one for the
> final charged call duration after rounding and billing interval.
> Regards,
> Calvin Ellison
> Senior Voice Operations Engineer
> calvin.ellison at voxox.com
> On Tue, Jun 9, 2020 at 12:14 PM Johan De Clercq <johan at democon.be> wrote:
> >
> > Upwards seems best.
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20200609/066fec78/attachment.html>

More information about the Users mailing list