(Solved!) Grandstream 2160 will not get correct date/time from AREDN node NTP server

I had installed the whereaandwhen package in order to use a GPS antenna to obtain both location and date/time information on a "Go-Kit" node that would be deployed as part of our local ARES capabilities in case of an emergency and also for use in the ARES Simulated Emergency Test (SET).  We also use VOIP phones in our SET and they have been invaluable to passing traffic and for demostrations to our served agencies.  It always gets brought up that the date/time is not correct on the phones (this also happened at a Jamboree On The Air event with the Boy Scouts).  This had bugged our group for some time, but other than having a connection to the internet (which could be down at least locally in an actual emergency such as the hurricane that hit the Carolinas this year). I incorrectly thought that this would also allow other nodes and devices to use this as a source of timing as is.  It turns out it is more complicated than that.  I was trying to pass this information to the phones using DHCP option 42, but without success when pointing it to the AREDN node (you have to use the actual IP according to the standard) with the GPS antenna attached.  Here is what I did to get it working.  The node I was testing on was an AR-300M16 running nightly build 20241024-7d9ac7e which uses OpenWRT 23.05.5.  It turns out OpenWRT (and hence AREDN) uses BusyBox to provide a lot of stuff including ntpd.  I had to SSH into the node and edit /etc/config/system which involved locating the "ntp" section, and setting the "enable_server" option to '1'. Next, commit the change using "uci commit system". Finally, restart the NTP service using the command "/etc/init.d/sysntpd restart" to apply the changes. Once I did this, the phone picked up the correct date/time in short order.  Unfortunately, I have to redo these steps every time I boot the node.  As a workaround, I added the "-l" flag after the "-n -N" flags in /etc/init.d/sysntpd.  I don't like this, but at least it gets to a stopping point until I can look into it further.

Making this change persistent has been a challenge.  I manipulated the copy of the file /overlay/upper/etc/config/system; however, it did no good.  Apparently, that file gets overwritten by /rom/etc/config/system.  So I'm back defeating the original sysntpd script the way I did before.