Hello everyone,
I am using version 6.0 of the ASTPP application and have noticed that the system does not round the call duration times. This can create a discrepancy between the time measured by ASTPP and the time handled by trunk providers, who do round their times.
After a brief investigation, I found that this detail seems to originate from FreeSWITCH, as the variable billsec , according to what is observed in the Example XML CDR, truncates the time instead of rounding it.
<caller_id>%22Mikey%22%20%3C1160%3E</caller_id> <duration>39</duration> <billsec>36</billsec> <progresssec>0</progresssec> <progress_mediasec>0</progress_mediasec> <flow_billsec>39</flow_billsec>
<mduration>39583</mduration> <billmsec>36267</billmsec> <progressmsec>238</progressmsec> <progress_mediamsec>237955</progress_mediamsec> <flow_billmsec>39583</flow_billmsec> <uduration>39583335</uduration>
<billusec>36267529</billusec> <progressusec>237955</progressusec> <progress_mediausec>237955</progress_mediausec> <flow_billusec>39583335</flow_billusec> <read_codec>PCMU</read_codec> <read_rate>8000</read_rate>
I would like to know if anyone in the community is aware of how to configure the system to round the call duration times. This would be very helpful for optimizing billing and avoiding small losses that, while they may seem insignificant, can accumulate over time.
Thank you in advance for any advice or solutions you can offer!