Rebooting server causes "No transport is found for destination" error on Register trunks

[mash4]

We have encountered what looks to be a bug in 3CX. This is on version 16.0.611 running on a Debian server (installed with the 3CX installer, only 3CX running on it).

If the server reboots then when it comes back, all the Register/Account based Trunks will not come back online and the activity log will have lines like:

05/22/2020 7:30:03 AM - Dev(XXXXXXXX):[sip:[email protected] / XXXXXXXXX]: (!) No transport is found for destination: <sip147.75.65.192:5060/UDP>

This keeps repeating for all the trunks that are Register/Account based. The IP Based trunks seem to come online OK.

To "fix" this I can go into the 3CX services and restart "3CX PhoneSystem 01 SIP Server". Afterward then the trunks come up OK.

This makes me suspect that there is some sort of race condition when the server restarts, so perhaps the SIP Server service is started before some necessary component comes online, and it doesn't retry something properly. Thanks.

 

[cobaltit]

So this sounds a little like the bug that was supposed to be Windows only. From the change log:

https://www.3cx.com/blog/change-log/phone-system-change-log/

I don't know if any code changes were actually made in the linux version as the change log just says the version (.612) was for parity reasons. But if you are so inclined you could take a backup (copy if off the box) uninstall and reinstall and then you should be on .612