It was my conversation, and I told about
1) $Tsm is MICROseconds (6 digits)
2) It is microseconds of a current second.
On Wed, 19 Jan 2011 09:29:28 -0800
Dave Singer <dave.sin...@wideideas.com> wrote:
Be careful when using $Tsm. I read a thread the other
day that was just
talking about it and that it returns milliseconds since
midnight, not epoch.
So if that is true you will need to somehow handle calls
that cross midnight
for duration at least and start/answer/end of call if
including the
precision in those timestamps.
I'd be interested to see what you find.
What I've seen with sub second accounting is for
rounding purposes where for
example billing in 6 second increments and it is always
rounded up. So a
call 6.001 seconds would be charged for 12 seconds.
Dave
On Wed, Jan 19, 2011 at 6:35 AM, Brett Nemeroff
<br...@nemeroff.com> wrote:
On Wed, Jan 19, 2011 at 8:32 AM, Andrew Philp
<andrew.ph...@just-tek.com>wrote:
We are looking to use this for billing directly and for
most of our
customers are billed on a hundredth of a second.
Does this make sense?
Sure it does, but I've never heard of sub second
billing. The ACC module is
probably not going to help you for this need presently.
I believe $Tsm
returns milliseconds. You may be able to manually
account for the calls with
that.
-Brett
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
