Network error on calls node's only

[Joshua M Clatney]

Hello, I feed to BCFY feeds, 2 calls nodes, and 2 rdio scanner servers.



All of a sudden, and since the lost recent update, everything but the calls node's work. Once a call goes in line for either, it immeidaltey switches from "connected" to "temporary broadcast error) and no calls go through unlike on the rest where its fine. I've tried deleting and redoing the settings, no luck. Tried uninstalling and reinstalling sdrtrunk, no luck.



Any ideas? 

[Joshua M Clatney]

In the logs I also see "rejected call skew too long" 

[CT POLICE LIVE]

Might be your PC clock??

https://forums.radioreference.com/threads/broadcastify-calls-node-skew-problems.447894/

UPDATE 7/1/2023 - We are now going to start blocking calls from Broadcastify Calls Nodes that have a node skew of greater than 15 seconds, or less than -15 seconds.

Node Skew represents the difference in time between when a call was captured on a Broadcastify Node and when it was received by the system. Typically, when the skew or time difference is greater than 15 seconds, this indicates that the time set on the machine capturing the call is set incorrectly, or significant network or hardware processing latency exists between the capturing node and the Broadcastify Calls systems.

It is absolutely critical that the time set on your Broadcastify Calls Node is synchronized to a correct accurate time source on the Internet.

Broadcastify Calls Providers can view the current Node Skew for your system by going to your calls management page at:

https://www.broadcastify.com/calls/manage/

Click the "Manage Node" icon for your node:

[Austin Hruskach]

Important note: If you are using an old PC, the CMOS battery on the motherboard might be dying or dead. This is important because the CMOS battery powers the onboard clock during system shutdown time, but also affects the time keeping accuracy. I run an old optiplex 8010 and the cmos battery is toast, so the hardware clock always resets on reboot. That would also cause a time drift of a few 5-10ms / 5min, which would drift way too quick. To fix this, not only did I change the battery, I use https://www.timesynctool.com/ to sync the time every 5 minutes, then it logs the corrected offset so you can see how much it had to change it to correct the drift. Also, this serves as a nifty internet outage tool because it will also log if it cant reach the NTP server.