Toggle sidebar Toggle sidebar

SIP Trunk Not Registering or Attempting Registration

Status
Not open for further replies.
the131

the131

Silver Partner
Basic Certified
Joined
Mar 15, 2016
Messages
13
Reaction score
2
Hello,

Ran into a strange issue today with all of my 3CX clients that we support. Every one was showing that the SIP Trunk was unregistered. The strange part about this, was that 3CX did not appear to have ever attempted registration. There was no history, nothing in the logs, it was just unregistered. Any attempt to manually register with the buttons at the top did nothing, "Refresh Registration" and "Enable all" did nothing. The ONLY way I could get my SIP Trunks to register was to go into the SIP Trunk settings, click around, then hit "OK". Then it registered. On the last two I fixed I attempted to just go in, hit OK, which did not fix it. I actually had to go into the settings and click a few fields so that the system would actually "Save" the SIP Trunk (even though I changed nothing). Then it registered.

Obviously this is a huge problem and I am surprised nobody else is posting about it. I figured I'd post here in case any one else had this issue.
 
@Nickelpede not at all, it's a step in eliminating certain causes that can stop registration.

In your case there must be something else happening. Like you said, rolling back did not help, and using the IP straight up did not help so it seems to indicate that it is not directly related to the original poster's issue which we already discovered. I recommend to read the below, then start a new thread for your case:

https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/
 
We have the same problem with Spitfire trunk registering since the update.
Spitfire confirm the line is OK and that no requests are being received.
We created the SIP again using the default template and deleted the old.
After clicking around and then 'enable all' the trunk was back up.

Some 48hrs later the trunk had failed again, but what I noticed was the 'Register Sent - Register OK - Last failed register' were all blank.

In the past when we had a SIP line down, those register details would show Last failed register at least.

I have to go into the trunk settings again, click around then OK. Enable all - Then it is working again.(so far!)
 
We're experiencing the same issue on 5 or 6 sites, only a service restart kicks the trunks back online. Very annoying and clients getting irate!!

Must be a known issue/fix by now with the amount of users reporting it.
 
@JohnS_3CX.
I do not think that adding another thread about SIP registration failure is warranted.
The Original Poster said he got Registration failures without notification.
And then the thread became about registration failures with or without notification.
It was changed way before my entries.

My 3CX system was failing using FQDN similar to many others reported here.
I changed it to static IP and it still fails. Its not a DNS resolution issue.

But last night I was thinking about this and wondered
Why does the 3CX checks SIP registration so frequently?
What triggers a SIP trunk registration check?


3CX Version 16.0.612 on local WIndows 10 Pro using Nextiva SIP provider since 2015 with Yealink phones. Watchguard Firewall.
 
@Nickelpede I still think it does, because you clearly said in message #21 that reverting to 16.0.6.612 did not help.

So far we only know of .641 on Windows being affected, so you are looking at an entirely different scenario here, unless there is some additional unknown variable in the mix. I mean, you are still on 612 right now and you still have the issue yes?

As far as registrations go, what triggers is the SIP Expiry time. Once you register, you need to refresh the session in regular intervals (this is normal for SIP in general)
 
Here's 3 of my systems that are de-registering the SIP trunks, weve been using the "Generic" SIP provider for over 6 years now successfully with 3CX:

  • 3CX Version Standard Annual 16.0.641 16SC Pro
  • Server OS Windows Server 2016 Standard 64Bit
  • Is the 3CX Server Hosted and where? On Site
  • Trunk Provider Generic SIP Trunk
  • Has the Firewall Checker passed: YES

  • 3CX Version Standard Annual 16.0.641 4SC Pro
  • Server OS Windows Server 2016 Standard 64Bit
  • Is the 3CX Server Hosted and where? On Site
  • Trunk Provider Generic SIP Trunk
  • Has the Firewall Checker passed: YES

  • 3CX Version Standard Annual 16.0.641 8SC Pro
  • Server OS Windows 10 Pro 64Bit
  • Is the 3CX Server Hosted and where? On Site
  • Trunk Provider Generic SIP Trunk
  • Has the Firewall Checker passed: YES
 
Work around solution for me is to edit the SIP trunk, changing the domain of the SIP server to the IP address. Definitely a DNS resolution issue occurring here
 
Hi all, we've also been dealing with this trunk registration issue on a clients server after updating to latest version. 16.0.6.641

After significant testing this certainly looks to be a bug or issue within 3CX and not a DNS or SIP problem.

From testing
- If 3CX loses SIP registration the trunk status remains green
- No drop of registration is reported in the 3CX logs, as far as 3CX is concerned the trunk is active

As many other have reported this makes sense to why 3CX doesn't automatically refresh the registration, this would only occur if 3CX actually logged the drop, as far as 3CX is concerned the trunk is working but that's not the case.

To clarify, I believe the issue is related to 3CX not registering the drop of SIP registration to the provider.

I've tried setting the Network keep alive to 20, also set the trunk re-register time out from 200 to 30 but doesn't seem to make any difference.

Once the SIP trunk drops out the only work around I have found at this time is to manually refresh the registration, restart 3CX services or restart the server which are all not long term solutions.

Awaiting an update from 3CX. Happy to provide any support logs in relation to this issue
 
Last edited:
Hi @TechnicaGroup

If you don't mind post a screenshot of the affected trunk that contains exactly everything you see here, just hide your Authentication ID

1600333673227.png
 
I was having the same issue with SIPTRUNK.com SIP trunks dropping registration and not sending registration requests. 3CX has provided me with a hotfix update that corrected the issue. The hotfix is still in beta as they have developed it over the last two days.
 
I have noticed this issue on like 8-10 of my client's 3cx instances so far. all use babytel.net for the sip trunk. some are VMs, most are stand alone boxes. all running windows 10 pro and 3cx version 16.0.641.

attempts to reregister the trunk do not fix, attempts to rebuild the trunk do not fix. reboots, change of dns, flushing dns, etc no results. not even attempts at reregistering the trunk, even babytel do not see registration requests. if i ping the outbound proxy, the provider can see the ping requests fine. but no sip registration requests. .. changing to IP instead of FQDN and the trunk comes right up.

any word on when this will be patched?
 
this is my 4th PBX on this sunday morning i found SIP trunk down and unable to register. I've just had to restart sip service on this one to retrieve trunk instantly connected to provider
 
looks like the update released last night might fix this as it includes...
  • Fixed issue with DNS resolver on some operating systems.
i scheduled update for tonight on our phone systems <knock on wood>
 
fusion12 said:
looks like the update released last night might fix this as it includes...
  • Fixed issue with DNS resolver on some operating systems.
i scheduled update for tonight on our phone systems <knock on wood>
Click to expand...

Is that really the best thing to do? I'd manually update one system that is known to have the issue and then test to make sure something else didn't break first.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,962
Messages
589,996
Members
164,868
Latest member
swegner
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom