Priority Landline on nbn UNI-V Reverts Phone's +8 WA, AU Time to UTC Time on Any Incoming Call

Hi everyone,

I have a very, very strange issue to report and I have zero idea why it's happening. I can't even be sure if it's NBN-related or what could be causing this.

An older lady friend has NBN FTTP. She has a priority landline, meaning her phone plugs directly to the battery-backed-up NBN NTD UNI-V port, not the router. She started having connection issues and rang Telstra to check it for her. They said there wasn't anything wrong as far as they could tell.

Here's what's happening now and it's a weird one: the phone set includes one base station + one satellite. When you set the time on the base, it also sets it to the satellite. So, you set our current time (+8, WA). All fine. It will keep time perfectly, – until any incoming call is answered, where the time will change and go back exactly 8 hours (UTC?) !!!

This has been replicated now on four, different phones (three new from Telstra, one from me). The only thing I could think of was that maybe it's something to do with the NBN NTD box since that's where the phone plugs to? Grasping at straws, I tried a reset + power-off of the NBN NTD box (but didn't disconnect the battery backup as the cord was stuck tight in the NBN NTD box and I didn't feel comfortable trying to get that stupid battery out). Three technicians from Telstra have attended and no one can fix it.

Any ideas what could be causing this? I'm completely stumped.

Thanks all!

Comments

  • I'd try Whirlpool instead of here.

  • -1

    why not just switch out the phone for something else ? its probably something to do with the nbn equipment and caller id defaulting to utc. or just move and relocate to the utc time zone

  • Got to love the brand and model numbers supplied so tech support can help….

    Landline…. Goes the way of the dodo bird when you switch over to NBN.

  • Please read the post. I'm looking for someone who might have an actual idea, not a dig.

    Bodymovin…This only just started on a phone that was fine. Now, it's ANY phone, and there's a reason we want to keep this one. This woman keeps this phone with her in the house. She's comforted by the familiar date & time. NO password, facial recognition, or figure-drawn-key needed to use it in an emergency. Why should she change when NONE of the replacements are working either?

    AndyC1…If you want model numbers, ask. Don't be a passive-aggressive ahole.
    Telstra is troubleshooting atm, but here you go. A202, there's one. Telstra has been back & forth over the phones. Don't recall the other 2 phone models but they're recent. The issue is constant- happens 100% of the time and for no reason that anyone has suggested.

    Landline…. Goes the way of the dodo bird when you switch over to NBN. I stated this woman is NBN-FTTP. Landline/priority will be around for a fair while. It has it's purposes, whether you personally need it isn't relevant.

    Anyone at OZB who knows their way around NBN FTTP direct landline-connection?

    • If you want model numbers, ask. Don't be a passive-aggressive ahole.

      It's not an unreasonable request. Settle down, particularly if you're wanting people on three separate forums to provide unpaid troubleshooting help.

      Can you disable the Caller ID feature from the menus of the phone handset (or any of the other phones you've mentioned were previously used)? If yes, I'd troubleshoot whether this changes the observed behaviour at all.

      Caller ID encodes additional time data in the call, and I suspect that this is being used to update the internal clock. Similar behaviour often occurs with car head units and DAB+/GPS telemetry data. If you know this for certain - through troubleshooting - you're in a much better position to try resolve with NBN (who are responsible for NTD firmware, not Telstra)/etc. If not, there are other troubleshooting steps to follow.

      I'd manage your expectations though - a lot of embedded equipment relies on time libraries that are ancient and vendors have zero interest in updating firmware. I've encountered similar behaviour with a device that used pre-2009 libraries (when the eastern states standardised DST arrangements), and despite being able to get to the nub of the issue, couldn't get it fixed.

Login or Join to leave a comment