Toggle sidebar Toggle sidebar

Voip.msTrunks Keep Disconnecting/Reconnecting

SethTalley

Customer
Basic Certified
Joined
Oct 5, 2019
Messages
83
Reaction score
12
As referenced here: https://www.3cx.com/community/threads/3cx-v18-trunk-keeps-disconnecting-telnyx.127155/post-605319

We're running 1ea VoIP.ms, Telnyx and Flowroute. The outages usually last between 2 and 10 minutes, at least according to the software - to the best of my knowledge they haven't interfered with our calls. BUT since we're a midwifery practice and we need to know whether our patients can page us in the middle of the night, five midwives (including my wife) and three students received push notifications at 11:56, 11:58, 12:01, 12:03, 12:06, 12:08, 12:21, 12:23, 1:03 and 1:05am last night.

This obviously isn't making me popular.

Last night it was all Voip.ms, but it'll often be two in a day, and once was all three. I would say it happens once or twice a week.

What can I do to fix this, please?
 
Do you still experience this issue?
 
Intermittently, yes. We have not experienced it since Tuesday but it will often be several days between disconnects.
 
Can you please also contact with your partner and in case this occurs to create a support ticket so we can check this further?
 
  • Like
Reactions: SethTalley
I can. Will keep you posted.
 
3CX reported 10-minute outage at 11:19am PST Saturday and a 2 minute outage at 1:07am PST Sunday.

This month's have all been 3CX so far; I just confirmed with them that they have no outages or reports of outages from any other customer.

Warning1229306/23/2024 1:06 AMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/22/2024 11:26 AMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/22/2024 11:24 AMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/22/2024 11:21 AMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/22/2024 11:19 AMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/18/2024 1:02 AMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/18/2024 12:21 AMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/18/2024 12:06 AMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/18/2024 12:00 AMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/17/2024 11:56 PMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/13/2024 8:45 AMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/13/2024 8:43 AMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/13/2024 8:40 AMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/03/2024 1:02 AMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/03/2024 1:00 AMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/03/2024 12:57 AMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/02/2024 3:04 PMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/02/2024 3:02 PMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/02/2024 2:59 PMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
 
Can you please keep monitoring and let me know if you still experience any issue?
 
  • Like
Reactions: SethTalley
Yup. We had a drop from 11:02AM PST to 11:09AM PST. I can confirm this is an actual, not just a reported drop - I was unable to reach the office through that trunk line, although internal communications were uninterrupted.

Warning1229306/24/2024 11:09 AMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/24/2024 11:07 AMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/24/2024 11:04 AMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/24/2024 11:02 AMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
 
We will check this with the hosting provider and get back to you; in the meantime, please communicate this with VoIP.MS to ensure that this is not an issue on their side causing the de-registrations

As a countermeasure, please also add their IP address 208.100.60.8 to the IP blacklist section within the admin console > advanced > IP Blacklkst section and set it to ALLOW.
 
  • Like
Reactions: SethTalley
Added, thanks. Voip.ms was made aware of it Saturday and reported no issues on their side that would account for the errors.

Although these are all Voip.ms, last month I also experienced identical behavior with Flowroute and Telnyx.
 
Please monitor this and let us know if you have any further issues.
 
  • Like
Reactions: SethTalley
Warning1229306/27/2024 7:07 PMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/27/2024 7:04 PMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
Warning1229306/27/2024 7:02 PMSIP ServerRegistration at VoIP.MS - Main has failed. Destination (sip:208.100.60.8:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.
 
Did this ever get resolved or a root cause determined?
I have two different sip providers and only the voip.ms trunks drop. They go down and come back within 7-10 minutes. The event log simply shows an error such as:
Registration at VoIP.MS has failed. Destination (sip:208.100.60.9:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available

I have two trunks defined for voip.ms on the same PBX and both go down together.
I'm going to try changing one of the trunks to use their IP rather than DNS and see if that has any impact.

These are my outage times in EST:
7/14 9:00 AM unregistered
7/14 9:10 AM registered
10 minutes

7/27 9:29 AM unregistered
7/27 9:38 AM registered
9 minutes

7/31 8:24 AM unregistered
7/31 8:31 AM registered
7 minutes

8/1 2:38 PM unregistered
8/1 2:45 PM registered
7 minutes

8/8 2:23 PM unregistered
8/8 2:32 PM registered
9 minutes

8/9 6:08 AM unregistered
8/9 6:16 AM registered
8 minutes

8/15 1:23 PM unregistered
8/15 1:32 PM registered
9 minutes

I can also make my own thread if this user is no longer impacted by this.
 
pellisCMIT said:
Did this ever get resolved or a root cause determined?
I have two different sip providers and only the voip.ms trunks drop. They go down and come back within 7-10 minutes. The event log simply shows an error such as:
Registration at VoIP.MS has failed. Destination (sip:208.100.60.9:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available

I have two trunks defined for voip.ms on the same PBX and both go down together.
I'm going to try changing one of the trunks to use their IP rather than DNS and see if that has any impact.

These are my outage times in EST:
7/14 9:00 AM unregistered
7/14 9:10 AM registered
10 minutes

7/27 9:29 AM unregistered
7/27 9:38 AM registered
9 minutes

7/31 8:24 AM unregistered
7/31 8:31 AM registered
7 minutes

8/1 2:38 PM unregistered
8/1 2:45 PM registered
7 minutes

8/8 2:23 PM unregistered
8/8 2:32 PM registered
9 minutes

8/9 6:08 AM unregistered
8/9 6:16 AM registered
8 minutes

8/15 1:23 PM unregistered
8/15 1:32 PM registered
9 minutes

I can also make my own thread if this user is no longer impacted by this.
Click to expand...
Can you please open a support ticket via your portal to check this? We are going to need some information that we cannot request via the forum
 
It happened less and less as I reported back and then eventually dropped off. Voip.ms now has an MMS hook into 3CX; I'm wondering if there's some behind-the-scenes changes that are causing this. I haven't had any problem with Telnyx or Flowroute in a couple months.
 
SethTalley said:
It happened less and less as I reported back and then eventually dropped off. Voip.ms now has an MMS hook into 3CX; I'm wondering if there's some behind-the-scenes changes that are causing this. I haven't had any problem with Telnyx or Flowroute in a couple months.
Click to expand...
Suppose only the VoIP.MS trunk is having this issue, and other trunks are not experiencing this on the same system. I would suggest contacting VoIP.MS directly to check their trunk.
 
Well... the one that resets the most is "Webmeeting Bridge" which goes straight to you without passing through anybody else so I'm not quite ready to point the finger at Voip.ms.

I've got 6 12294s in the past 30 days - three voip.ms, two Flowroutes and a Telnyx. L:90000 (Webmeeting bridge) doesn't generate 12294s but I've got four emails telling me it's status has changed to "registered" in the same amount of time.
 
Charles_3CX said:
Suppose only the VoIP.MS trunk is having this issue, and other trunks are not experiencing this on the same system. I would suggest contacting VoIP.MS directly to check their trunk.
Click to expand...
Info410008/18/2024 7:10 AMSIP ServerTrunk L:10002(Telnyx MMS) has changed status to registered.
Info410008/18/2024 7:09 AMSIP ServerTrunk L:10000(VoIP.MS - Main) has changed status to registered.
Info410008/18/2024 7:08 AMSIP ServerTrunk L:10002(Telnyx MMS) has changed status to unregistered. This means that no more calls will pass via this trunk. Please check your network connection and the voip provider or other SIP PBX
Info410008/18/2024 7:07 AMSIP ServerTrunk L:10001(Flowroute Toll Free) has changed status to unregistered. This means that no more calls will pass via this trunk. Please check your network connection and the voip provider or other SIP PBX
Info410008/18/2024 7:07 AMSIP ServerTrunk L:10001(Flowroute Toll Free) has changed status to registered.
Info410008/18/2024 7:07 AMSIP ServerTrunk L:10000(VoIP.MS - Main) has changed status to unregistered. This means that no more calls will pass via this trunk. Please check your network connection and the voip provider or other SIP PBX
 
Hello,
Could you please check with your SIP TRUNK service providers what is the shortest Time Between Registration they can support?

Voip.MS and Telnyx

This could be a first point to investigate.

Llet me know
 
Voip.MS says they have no minimum but they recommend setting the parameter to 300 seconds. Telnyx says their supported minimum is 60 seconds.
 
You must log in or register to reply here.

Latest Posts

Forum statistics

Threads
111,973
Messages
590,074
Members
164,895
Latest member
jasonkkrause
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom