SIP trunk not attempting to register

[ebs1]

We have 3CX installed on a physical Windows machine. It updated itself automatically over the weekend - current version is showing as 16.0.619.

We have a SIP trunk with Spitfire (UK) that is failing to register. It doesn't appear to be even attempting to register - I've monitored SIP traffic on the network interface and there's nothing being sent to the provider, and the admin page shows "Last Register Sent" to be ten days ago:

I tried adding a new trunk with the same details (changing the name and auth ID of the existing one first), and that didn't attempt to register either.

Any idea what's going on or what I can look at to troubleshoot?

 

[Aaron Paul]

Does your firewall checker pass?

 

[Saqqara]

Can the machine ping / nslookup the hostname

Is the windows firewall enabled, have your tried to disable it and see what happens.

 

[ebs1]

Does your firewall checker pass?

Yes, firewall checker passes.

Can the machine ping / nslookup the hostname

Is the windows firewall enabled, have your tried to disable it and see what happens.

Yes, it can lookup the hostname.
Windows firewall is permanently disabled on this machine, but I double checked it

 

[Saqqara]

Have you tried clicking on 'Enable All' icon ?

 

[leejor]

The Activity Log show no attempt, even after a reboot of the machine, or restart of services?

 

[AWS2P]

If you replace Domain by IP 62.133.0.196 , is the trunk turns green working?

 

[ebs1]

Have you tried clicking on 'Enable All' icon ?

Yes, I've tried that. 'Disable All' and 'Enable All' doesn't seem to have much effect - should Disable All also disable the WebMeeting Bridge, because it's not.

The Activity Log show no attempt, even after a reboot of the machine, or restart of services?

No, no attempt logged and the "Register Sent" field doesn't update. I've monitored the traffic with wireshark and there are no register attempts showing.

If you replace Domain View attachment 16521 by IP 62.133.0.196 , is the trunk turns green working?

Sadly not; same thing happens.

 

[ebs1]

Running a Wireshark capture with "host 62.133.0.196" filter set and restarting the SIP service results in absolutely nothing being captured.

 

[leejor]

Does the machine only have one Ethernet port? Are email notifications going out as usual? Any remote sets working?

 

[AWS2P]

If you do an nslookup on spifiretsp.net from your PBX does it resolve ?

Not sure if it can be the same as recent problem lot of people got same with trunks from several providers over the world having trunk unable to register. Problem was 3CX internal problem with DNS resolution failure.

have got this myself, randomly trunk fails and don't try to reconnect to SIP provider. Refresh button do nothing, no packet sent to provider, only a pbx reboot or a change in trunk setting from domain to Provider IP was a temporary solution.
After this 3CX do a change to fix this behavior.
May be this is not what happens for you but clearly this seems similar.

Which dns do you use on your NIC ? 8.8.8.8 ?

 

[ebs1]

Does the machine only have one Ethernet port? Are email notifications going out as usual? Any remote sets working?

Yes to all. I don't have any remote provisioned extensions, but all remote 3CX clients are working fine for internal calls.

If you do an nslookup on spifiretsp.net from your PBX does it resolve ?

have got this myself, randomly trunk fails and don't try to reconnect to SIP provider. Refresh button do nothing, no packet sent to provider, only a pbx reboot or a change in trunk setting from domain to Provider IP was a temporary solution.

Which dns do you use on your NIC ? 8.8.8.8 ?

Yes, it resolves. Using the local Windows DNS, which forwards to 8.8.8.8.

I previously changed the registrar to the IP and it didn't change anything. Since changing the proxy as well, I can now see REGISTERs being sent, but no response received. Problem shifted slightly!

As this box is running Windows 8 and needs an upgrade anyway, I may just wipe it and reinstall.

 

[AWS2P]

I remember, first step was to delay services to be sure windows network stack to be ready when register tries are sent.
Not sure if OS can be involved in problem, but for sure it's not a supported one , so it's a good idea to upgrade to one which is

 

[YiannisH_3CX]

As this box is running Windows 8 and needs an upgrade anyway, I may just wipe it and reinstall.

That might explain the issue as Windows 8 is no longer a supported OS and may cause issues. Upgrade your machine to a supported OS and see if that resolves your issue.
https://www.3cx.com/docs/manual/

 

[ebs1]

Final update: at some point, after changing both the registrar and the proxy URLs to IP and back again, it started working perfectly normally

I'm going to rebuilt it this week anyway.