Update 3 causing outbound timeouts ... found a solution, for us at least

[CCAdmin]

We recently had our 3CX auto-update to the newest v16.3 (even though auto update is off - but that's a different problem, lol).
Since the update, we had several SIP trunks not allowing outbound calls. The error would come back as a timeout.
After lots of troubleshooting, we finally discovered the problem (at least for us)!

There's a new "auto-discovery" feature on the SIP trunks. After the update, some were checked and some weren't.
3CX apparently changed how they look up DNS for the SIP server host.
All the ones that were NOT checked, were allowing inbound calls just fine, but no outbound calls.
Once we checked the "auto-discovery" box, every trunk began working perfectly again.

Hope this helps others dealing with a similar issue.

Also, side note, for those still using NexVortex as their SIP provider, NexVortex also told me that since v15,
their trunks work better with 3CX if you change authentication from "Do not require - IP based" (old setting) to
"Register/Account based" (new setting).
I found one trunk not authenticating properly by making this change. (extra bonus)

 

[cobaltit]

Thanks for posting resolution. Two things to note:

• This is one of the reasons it's good to use a supported provider. As a supported provider (with auto-testing setup with 3CX) we've had zero issues with the Update 3 changes.
• You should try to participate in the alpha/beta releases. These changes were in there and wonky auto-updates not withstanding, at least you would have had a heads up as to what changes were coming up.