Phones local to the PBXtra use a Network Time Service in order to synchronize with the accurate, local time. This Time Service comes in the form of an IP address given to the phone by the PBXtra (If used as a DHCP server) or by your own DHCP server.
This technology is called NTP, and though Fonality tries to automate the process of a new phone booting up and correctly synchronizing the time for your location, when the phone is moved from the office to a remote location (including a remote office that does not have a PBXtra installed on-site), the automated process will fail.
Fonality uses the IP address of your PBXtra as the NTP value for every phone. When the phone is moved to a remote location, it stores this IP address. However, the IP address of your server is private and cannot be located from a remote location. Therefore, the time on the phone will begin blinking 12:00 and/or set to some other incorrect time.
You can manually configure the NTP settings on your Polycom or Aastra phone if you follow these directions:
Aastra
Polycom
As long as the router in your remote location allows the phone to communicate with pool.ntp.org, the phone should correctly synchronize with the local time.