This relates tangentially to my previous post about 2FA woes.
My iOS devices with active cell service relocated across time zones several years ago and I was not vigilant in updating the addresses in my ATT account other than the primary and billing. These were not the only entries necessary when moving. Primary place of residence and e911 were separate entries, only one of which I was able to update on the app or web (yes I tried both). Part of the issue is the paternalistic attitude of iOS that required me to enable WiFi calling on my primary ATT device. This prompted me through a EULA and verifying my address (the e911 address entry) before I could toggle WiFi calling separately for ‘other devices’. The ATT ‘help’ articles were silent on this user workflow, as was the magical AI option.
This straightforward path started in a bramble of ridiculousness with my time zone setting. Asking iOS to set my time zone automatically set my clock incorrectly and I could not fix it for years. (Minor annoyances build to massive headaches. And iOS mandates time.apple.com as the hardcoded server.) This cascaded into services and cell-based devices (like ToTP and the wife’s iPhone) fading in and out of usefulness without real understanding of the cause or consequences of being a minute or more out of sync.
The rub of irritation continued as toggling on and off the automatic setting put me back into compliance, yet could not solve the issue. The key was noticing the non-cellular iPad blissfully unaware of my temporal troubles.
Toggling cellular service on and off did not solve the issue, nor did WiFi on or off, or any combination of the two, and I despaired until digging further into ATT’s shoddy settings and figuratively stumbling upon my solution of turning on WiFi calling.
Perhaps this will help the single-digit percentage of existing ATT users who move to a new time zone with iOS devices and have never turned on WiFi calling.