Solved Voip trunks not resolving since updating to 16.5 yesterday

[NickG]

We use Voipfone here in the UK to provide three trunks, all working fine for years until we updated to V16.5 yesterday. Voipfone hasn't seen a registration since that time on any of them and the log for one of them is below

04/23/2020 10:07:51 AM - Lc:10001(@dsi[<sip:0/UDP>]): Registration postponed until target's destination is resolved

04/23/2020 10:07:51 AM - Registering Line Lc:10001(@dsi[<sip:0/UDP>])

04/23/2020 10:07:51 AM - Unregister: ADS for 10001 is not found

04/23/2020 10:07:51 AM - Unregistering Line 10001

04/23/2020 10:07:50 AM - Lc:10001(@dsi[<sip:0/UDP>]) Resolving targets: primary - sip:sip.voipfone.net:5060, no secondary over +UDP+IPv4+IPv6

04/23/2020 10:07:50 AM - Lc:10001(@dsi[<sip:0/UDP>]) is enabled now

04/23/2020 10:07:50 AM - Line 10001: Request for registration in 1141 ms

 

[Alphabetic]

I just set up my voipfone account with no problems.

Server address: sip.voipfone.net port 5060.

check your DNS, try pinging the address.

 

[NickG]

NSLookup resolves, if I put the ip address in the settings it connects fine. I wonder if this is an issue with running it on Server 2012 R2?

 

[Alphabetic]

So assuming your SIP trunk isnt registered? You havent managed to either get that IP in your 3CX blacklist or Voipfone have blacklisted your IP? Give them a quick live chat on their website and ask the question. Are you using correct credentials? Same as login for my.voipfone.co.uk website

 

[Alphabetic]

I cant see why.

whats your primary DNS server on the server?

 

[NickG]

It is it's own DNS server with forwarders set to Google & our ISP

 

[Alphabetic]

just stick them to external DNS and have done.

 

[NickG]

I need the dns server on there for other reasons but will try a few things out, thanks for your help.

 

[Alphabetic]

Be aware PC should be dedicated for 3CX only. Otherwise your installation becomes unsupported in the eyes of 3CX.

 

[inspired1]

I have exactly the same issues with a client..

NSLOOKUP shows destination resolved but +log show destination is not resolved

Andy

 

[NickG]

Putting the IP address in did the trick but obviously not a long term solution. Made loads of changes to the DNS settings on the server, none made any difference. Was working fine for years before the 16.5 update yesterday.

 

[ajnewtexas]

I am having the same issue with this update. Different provider (Siptrunk.com), same issues.

 

[NickG]

Tried setting up the NIC with Google DNS servers, local router, ISP's DNS server, made no difference, it doesn't resolve. NSLookup fine, web browsing fine, etc. V16.4 was fine...

 

[ajnewtexas]

Tried setting up the NIC with Google DNS servers, local router, ISP's DNS server, made no difference, it doesn't resolve. NSLookup fine, web browsing fine, etc. V16.4 was fine...

Same...just got off with SIPTRUNK. Looks like it is this 16.5 build.

Any help 3cx? Downgrade path?

 

[Alphabetic]

What happens if you make the SIP Trunk from new? Does it work with host name?

 

[ajnewtexas]

No luck rebuilding the trunk, tried it 3 times.

 

[Alphabetic]

Are you on Windows too?

 

[ajnewtexas]

Yes. No issues on my Windows 10 Pro build until 16.5 . I can resolve the host outside of 3cx, but nothing from 3cx. Bridges work, but that is via IP. It won't even show a failed registration. It doesn't seem to try to resolve.

 

[Alphabetic]

@JohnS_3CX Any issues you're aware with latest update with 3CX on windows and unsupported SIP trunks? Voipfone (original poster) works fine for me on Linux.

 

[dmayer]

We had the issue happen to a customer yesterday, initially they registered but went down and would not register, created new, nothing. Nothing in wireshark capture.

We noticed that 3CXPhoneSystem.exe was chewing up 12-13% CPU and it's an 8 Core i9 system, so it looked like it was chewing a whole core up. The PSTN gateway was working, but not the SIP trunk. Anyone else noticing that process eating up a lot of CPU?

We ended up rolling back to get them back and running.