VOIP.MS Trunk disconnecting on weekends

[buecker]

I've been testing voip.ms with 3cx on two different occasions. On both occasions when the weekend arrives I get literally over 5000 emails stating the same thing. It's this way until I can delete the trunk. I am using the standard voip.ms template that is in 3cx. This is on version 15.5.

Registration at VoIP.MS has failed.
Destination (sip:[email protected]:5060) is not reachable, DNS error resolving FQDN, or service is not available.

I have many subaccounts with voip.ms and manage several different asterisk servers. I've only come across this with 3cx. On Sunday I verified there was no issues with the subaccount and I could ping the FQDN. Since this only seems to happen Saturday morning I don't know if there is some keep alive setting I have to tweak? I tried two different settings Sunday night but don't remember the names. Obviously the trunk didn't re-register.

 

[JohnS_3CX]

Hi @buecker

There is no option it keep it alive or anything like that. Does this definitely happen only on weekends or was two chance occurrences?

The email is accompanied by corresponding logs though: set your logs to verbose and see what else happens with the trunk registration and the overall system over the weekend.

I would also consider other avenues, such as any possible batch jobs or uploads/downloads that may be happening over the weekend that soak up all the bandwidth to the point that registrations fail or replies take too long to get through and expire before the system manages to get through to the provider.

Another thing that tends to happen over the weekends is attacks on your system: people always tend to attack when offices are more likely to be closed, and I don't know what this does to the firewall or the PBX, but you might be getting a bunch of blacklisted IPs as evidence. There are email notifications for those that you can also enable.

Move to V16 while you can, and make use of our Global Blacklist. It does a good job of keeping out well known attackers (who target systems globally).

 

[buecker]

Thanks for the suggestions. It wasn't from any attacks. My other trunks stayed up just fine and I was able to vpn in and delete the voip.ms trunk sunday evening.

I'll enable verbose and see if I can find anything useful in the logs.

Yes, things move very slowly here and all the 3cx servers are on windows.