Hi Bruce,
To add to the risk, I was involved in a parliamentary enquiry in NZ when working for EY, where customers were being charged extra for calls based on call ticketing inaccuracies, resulting from non-synchronised cells. Other than being very embarrassing for the carrier, it was expensive as they were required to correct the over and under customer payments. When I was reviewing it, I found older nodes were using a centralised Perl scripts to periodically log into and reset the time, where newer devices were using NTP. * The issues was discovered to be a range of things including the centralised Perl script not being able to log into the node (wrong passwords), new nodes not registered centrally when deployed and NTP not configured. * Times varied depending on the node drift and if the technician setup old/new nodes properly when deployed. * Call ticketing handover when roaming between nodes also negatively contributed to the evidence needed to reconcile billing when syncing issues exist. Just a related point. Good luck with getting it sorted. Thanks Derek From: AusNOG <[email protected]> On Behalf Of Bruce Forster Sent: Wednesday, 2 October 2019 11:58 AM To: AUSNOG <[email protected]> Subject: [AusNOG] Telstra Mobile network bad time zone settings - Brisbane CBD Hi noggers, Hoping someone @ telstra is on the list who can take a look at this one. You have a radio near central station in Brisbane, approx 180 ann st area that is giving off bad time zone data, my phone switched from +10 to +8 and when i walked back to the office again back to +10.. I'm based at 300 ann. If you need more data about it please feel free to contact me off list. Screen caps from phone: https://imgur.com/a/hmMv1p7 These were taken at 11:48pm, and 12:20pm 2nd Oct 2019, Sorry if there is a page on telstra's site to report this but i guess my google fu was bad this time. -- Regards, Bruce
_______________________________________________ AusNOG mailing list [email protected] http://lists.ausnog.net/mailman/listinfo/ausnog
