Solved Nexvortex DNS failure after update to 16.0.3.676

[ITRUSA]

Within minutes of the update to 16.0.3.676, my NexVortex truck failed with this error every few minutes:

Registration at Nexvortex has failed.
Destination (sip:000.000.000.000:5060;transport=TCP;lr) is not reachable, DNS error resolving FQDN, or service is not available.

When attempting to call out

Device 00000000 dialed on (AnyLine@Nexvortex) had no available outgoing trunk(s) for Call(from "Some User"<sip:[email protected]>;tag=00000000 to 00000000000)

On the SIP TRUNKS Page:
The value for host had been nexvortex.com
Changing it to px1.nexvortex.com solved the problem, but this eliminates the redundancy of just using the base domain name.

What has changed in this latest version? Any settings I can adjust to go back to nexvortex.com?

Thanks

 

[cobaltit]

I don't believe Nexvortex is a supported provider anymore and hasn't been for some time. That being said this is most likely due to the trunk changes in SP3. You'll want to play with or talk to Nexvortex support for the proper options to set for the transport protocol and autodiscovery settings.

 

[ITRUSA]

Thank you. Can you point me to the "trunk changes in SP3?"

Are you referring to the last bullet, Updated provider templates based on the new “Transport Protocol” and “IP Mode” parameters. on this page: https://www.3cx.com/blog/change-log/phone-system-change-log/ ?

 

[StefanW]

As per their documentation, it should be
"If your PBX supports DNS SRV, your registrar IP is reg.nexvortex.com."
and in our settings auto-discover and transport UDP (as TCP is not offered)...

Best to contact their support for further clarification.

 

[ITRUSA]

Yes, Nexvortex confirmed, With the new update there is a box for "Auto-Discovery" within the general trunk settings. Please be sure this enabled in order to register to "nexvortex.com".

Checking this solved the problem.

Thank you!