+1 Always ALWAYS round up, never down (in terms of ms to secs) +1 Also do your billing were your application is, not on a proxy.
On Tue, 9 Jun 2020 at 19:58, Liviu Chircu <[email protected]> wrote: > On 09.06.2020 15:43, Saint Michael wrote: > > I talked to Vlad, who I believe wrote the code, and he does not think > > it is a bug and I should use the ms and not the seconds. But thousands > > of businessmen will not spot this and thus their billing will never > > match the carrier, and they will lose money. If anybody thinks for a > > second that a call with a 200 OK will be free, is dreaming. Not in > > America. > > Hi, SM! > > Opinion #1: I doubt that anyone who is serious about their billing & > revenue (e.g. your nitpicky carrier) would leave to randomness the > answer to the most basic question of: "does our platform correctly bill > each call?". No disrespect here, just maybe highlighting the fact that > your platform could benefit from a bit more testing. > > Opinion #2: we could definitely change the default of the > second-accurate precision to be _greedy_ instead of _generous_. I bet > most people (myself included) would be more happy with a ceil() [1] > behavior instead of a trunc() [2] one. That is: round _upwards_, not > _downwards_. More opinions would be useful here! > > Best regards, > > [1]: man ceil > [2]: man trunc > > -- > Liviu Chircu > www.twitter.com/liviuchircu | www.opensips-solutions.com > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -- Regards, David Villasmil email: [email protected] phone: +34669448337
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
