SIP trunks not registering on startup until firewall checker is run - 16.0.611

[dj403]

This was solved previously in this thread, https://www.3cx.com/community/threa...-startup-until-firewall-checker-is-run.70948/

but now that the system updated to 16.0.611 the problem is back. Hardware and providers have not changed found the problem when shutting down for UPS maintanance.

We added the delay in the system service but it did not help this time.

 

[JohnS_3CX]

Will restarting the service solve it? Because if not we will have to look in a different direction.
(assuming this is the same machine as the last post)

 

[dj403]

Restarting services did not bring the trunks up.

Yes, exact same machine as last post. Nothing has changed except the 3CX version.

 

[JohnS_3CX]

Ok in this case, lets start entirely from from scratch, ignore the previous thread entirely.

Please provide all the details as per here please with a full description of the issue along with what steps you took so far. https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

 

[dj403]

3CX 16.0.611
Running on Debian9 installed from 3CX iso (originally 16.0.493)
Local hardware Lenovo M92Tiny. i5,8gb,128gb SSD.
Trunk provider VoIP.ms
Firewall checker passes except 5090 because port is not forwarded
Custom templates for T42 and T46 phones. All phones are local no remote.

When the 3CX server starts up the trunk to voip.ms does not come up automatically. The status icon on the trunk stays red.

Restarting services did not bring trunk up
Adding service start delay, the trunk does not come up automatically
Opening port 5090 and restarting 3CX, the trunk does not come up automatically

Manually running firewall checker brings up trunk to voip.ms.

 

[JohnS_3CX]

I would suggest the following then:

1. Reboot the machine when you can do so
2. When it comes back up, check that all services are running, and that VOIP.MS is remains unregistered
3. Open a 2nd tab to your management console and set your logging options to Verbose (Activity Log section)
4. Start a capture now from the same page
5. From the 1st tab, restart the SIP service ( 3CX PhoneSystem 01 SIP Server )
6. Wait for the services to all come up again, and note whether the trunk is still down
7. Finally from the 2nd tab, you may end the captur and click to Generate Support Info

The Support info file will contain some valuable information we can now analyze.

 

[dj403]

Completed those steps, trunk did not come up on reboot. But this time trunk came up after the SIP service restart. The Support file did not come thru until we ran the firewall test.

How do we submit?

 

[JohnS_3CX]

Please upload it in a public folder, and send me a private conversation message with your link