Just wanted to create this post to be informative for someone who might have a similar experience to me in the future.
Not sure if this is Flowroute specific but anyone struggling with their trunks registering on 3cx version prior to 16.0.3.676. It looks like this patch included some new trunk security features which might be the reason the trunk being unable to register. It had been about 4 days since the trunk had successfully registered for calls to no long be work and the trunk to unregister.
the error you will see in the event log will look like this:
I did contact Flowroute and the support mentioned it was not receiving my failed registration requests not sure if they were malformed or just not being routed properly on the older version.
**The Fix**
After logging the 3cx Debian server and using a
request and see dns was working properly like it should I went ahead and downloaded the pending update in 3cx management console from 16.0.2 something to 16.0.3.676 which resolved the issue and also added a new webmeeting bridge item in the SIP trunk area.
Hopefully this helps anyone who might get a call saying their phones aren't working in the near future with their 3cx failing to reregister. Lesson learned I have since enabled auto updates which I thought I had previously enabled but looks like I had not.
Not sure if this is Flowroute specific but anyone struggling with their trunks registering on 3cx version prior to 16.0.3.676. It looks like this patch included some new trunk security features which might be the reason the trunk being unable to register. It had been about 4 days since the trunk had successfully registered for calls to no long be work and the trunk to unregister.
the error you will see in the event log will look like this:
Code:
Registration at Flowroute - Trunk has failed. Destination (sip:@us-east-va.sip.flowroute.com:5060) is not reachable, DNS error resolving FQDN, or service is not available.I did contact Flowroute and the support mentioned it was not receiving my failed registration requests not sure if they were malformed or just not being routed properly on the older version.
**The Fix**
After logging the 3cx Debian server and using a
Code:
dig example.comHopefully this helps anyone who might get a call saying their phones aren't working in the near future with their 3cx failing to reregister. Lesson learned I have since enabled auto updates which I thought I had previously enabled but looks like I had not.
Last edited:
