Solved Flowroute trunk registration not heeding Registrar setting

[lfr1138]

I am getting the following error in the event log 2 - 3 times per minute:

SIP Server/Call Manager ID: 12293
Registration at Flowroute has failed. Destination (sip:216.115.69.144:5060;transport=TCP;lr) is not reachable, DNS error resolving FQDN, or service is not available.

The problem is that 216.115.69.144 is the address for sip.flowroute.com (which I believe is being/has been retired, which may be why I started seeing this recently) and not us-west-or.sip.flowroute.com (which resolves to 34.210.91.112) as is set as "Registrar/Server/Gateway Hostname or IP" in my trunk configuration. Also, I seem to be unable to override the "Outbound Proxy" setting to match as it always reverts to sip.flowroute.com after I save the settings. I made the change to my configurations to use us-west-or last year with the notifications to do so from Flowroute/Interado and everything had been working, but have had registration issues for the last couple weeks that I noticed. As of now, I get a busy tone when attempting outbound calls, but some inbound seem to get through, but maybe not consistently.

I am currently running version 16.0.5.619 on a local Debian Virtualbox VM.

 

[JohnS_3CX]

Update 3CX to the latest version and then I would start by deleting the trunk and setting it up using our default template. You are also running in an unsupported hypervisor, so it's another factor you need to consider.

Supported Hypervisors: https://www.3cx.com/docs/manual/phone-system-installation-windows/#h.5hoy5wwhhk5c

Flowroute: https://www.3cx.com/docs/usa-sip-trunk-flowroute/

 

[lfr1138]

Thanks for the info! I'll do the upgrade and trunk reinstall later tonight and post back any results.

I have been running on this hypervisor for a couple years now with no real issues before this one, so likely not an issue, but I may be able to get KVM to run on the host as a last resort.

 

[JohnS_3CX]

Sure, leave the hypervisor as the last step and see if the upgrade and trunk rebuild using defaults works.

 

[lfr1138]

After getting up-to-date with the latest (non-Alpha) version, I tried updating the proxy setting on the trunk to us-west-or.sip.flowroute.com before doing the delete/re-add, just to see, and the setting saved/ registered immediately. So, it looks like I am good to go!

Thanks again for the assistance!