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

[DavidQ]

Updated to latest ver on Windows ver 16.0.6.641.
Since the upgrade I get No transport is found for destination

If the server reboots when it comes back, all the Register/ Account based Trunks will not come back online and the activity log will have lines like: No transport is found for destination

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

Was not there before 3CX was all fine this must be a bug in ver 16.0.6.641

 

[AWS2P]

most probably you are in same problem exposed here
https://www.3cx.com/community/threads/sip-trunk-not-registering-or-attempting-too.75955/

 

[Saqqara]

Change the service for 3CX PhoneSystem 01 SIP Server to delay start, to see if this helps

 

[AWS2P]

Try to let IPV4 only