Outbound calling failure since update

[auxiliary]

Ever since our 3CX installation updated 2 days ago to the newest version, we've been having outbound calling failures that are random and also seem to resolve themselves.

We use Flowroute as a provider and everything has worked for years. 2 nights ago when the latest update installed, the next day we stopped being able to make outbound calls. The call would go out but 3CX would think the call was dropped. The phone that was called would receive the call but have no audio.

Flowroute support helped a bit and said that 3CX was not responding to 200 OK packets but even though we didn't change anything on the firewall or 3CX the calls started working again after maybe restarting services? (we're not actually sure what fixed it). Now the next day (today) it was broken again and it just fixed itself after running the firewall checker (nothing else was changed, restarted or anything).

Anyone else experiencing anything like this? I'm not even sure where to start troubleshooting.

 

[leejor]

Have you run the 3CX Firewall Checker, just to confirm that everything is "open".

 

[auxiliary]

Yea, firewall checker is green. Again, nothing on my end changed, only the recent update that got auto-installed. The day before everything was 100%, after patch broken, then next day broken again.

It seems like after restarting services that it fixes it for a while.

 

[YiannisH_3CX]

Hi @auxiliary

I will send you a p.m. so we can look a little deeper into this.

 

[auxiliary]

@YiannisH_3CX

What's even more strange about this, I have 3 complete 3CX installations and all of them are configured very similarly and all run over Flowroute and only this one has an issue, the other 2 are working fine and have not had outbound calls fail.

 

[cobaltit]

I'd add a fake Flowroute trunk in 3CX so you can see what the current template looks like and compare it to the existing trunk and update the settings as needed

 

[auxiliary]

That was one of the things that Flowroute support did with me over the phone. We verified all the settings including turning on Supports Re-Invite and adding the public IP to the SIP VIA header. When it worked after enabling those, we thought that was it, but then it broke the next day in the same manner when these two settings were still on. Then we realized those didn't matter.

 

[YiannisH_3CX]

I would recommend putting the settings back to the default and leave it like that to keep testing consistent.