I ran the v4 to v4.5 upgrade automated script and help my breath… thank goodness it actually worked without a hitch.
However I would still like to know how to keep the OS up to date in a way that can’t affect the VPX from working safely. If this was a different system, I would have just done it.
I am now on V4.5.0-7 with Asterisk 20.11.1 and Debian 12 Bookworm.
A side note… every time I reboot, I have to go into the master trunk, hit update and then do the save/refresh for incoming calls to start working… no idea why that would be.
And just discovered non of the statistics on the dashboard is updating and no graphs either. Yikes.
Update: Found fix for stats issue:
Edit the file /usr/share/vitalpbx/monitor/config.ini and change the value localhost to 127.0.0.1 in the [asterisk] section. Finally, restart the vpbx-monitor service. systemctl restart vpbx-monitor
That worked - so just left with master trunk not auto connecting on reboot issue.