Network and Redundancy Installation Set Up Details
nexVortex operates multiple, redundant service nodes to ensure that your phone service is reliable and without interruption.
Every time a phone call is made, the IP-PBX talks to one of our service nodes. nexVortex operates multiple, geographically separated service nodes to ensure the highest level of service availability. In order to benefit fully from this N+1 architecture, your PBX and networking equipment must be properly configured and tested.
Our service nodes can be reached using DNS SRV of “nexvortex.com”, if your equipment supports it. If not, standard DNS of “px11.nexvortex.com” and “px15.nexvortex.com” should be used instead.
Setting this up correctly will ensure you have access to the redundancies of the nexVortex architecture. Should any portion of this architecture suffer a service impairment or undergo maintenance, your service will not be impacted. You can learn more about this in the SIP Trunking Implementation and Planning Guide.
WHAT TO CHECK
To verify that your systems are using fully qualified domain names (FQDNs) and not a dotted IP address, you will need to login to your IP-PBX and go to the SIP Trunking configuration screens. (The location of these screens will vary from manufacturer to manufacturer so check your IP-PBX User’s Guide if you are unsure). Once there, look for the address of the nexVortex SIP proxies.
If you see 188.8.131.52, you will need to change this to a FQDN. If you are using static 4-octet IPs like 184.108.40.206 or you only have one trunk configured using either static 4-octet IPs or specific DNS records like px11.nexvortex.com, you are likely not properly configured for redundancy. The only way you can be properly configured for redundancy with only one trunk is if that trunk is built utilizing DNS SRV of “nexvortex.com” as your proxy IP address.
WHAT TO CHANGE
If the system is using a dotted IP address, you will want to update it. Please change the address for our SIP proxy to either px11.nexvortex.com or px15.nexvortex.com. Note, some systems allow you to configure both a primary and backup SIP proxy. If the system supports a primary and backup SIP proxy, use px11.nexvortex or px15.nexvortex.com for the primary SIP proxy and px11.nexvortex.com or px15.nexvortex.com for the backup SIP proxy (you must use both px11.nexvortex.com and px15.nexvortex in order to be fully redundant). Also, if the IP-PBX has a special address for SIP Registrations or a Registrar Proxy, please change that to: reg.nexvortex.com.
Once you make the change, try making an outbound phone call to ensure everything is working. If you need additional information or have any questions, please refer to our SIP Trunking Implementation and Planning Guide as well as the appropriate SIP Trunking Configuration Guide for your IP-PBX on our support pages (Go to your nexVortex Web Portal -> Support > Setup Guides) or contact us directly at email@example.com.
ONE MORE THING
While we are talking about redundancy, please do not forget about inbound calling. We operate multiple nodes and depending on what is going on in the network, you may receive inbound calls from any of the following IP addresses:
Please check your firewall and IP-PBX settings and make sure that you can receive unsolicited traffic from any of these IP addresses. To tighten the firewall security settings, you can restrict the incoming traffic from the IP addresses above to UDP and port 5060.
Again, if you have any questions regarding this, please do not hesitate to contact us either by email at firstname.lastname@example.org or by phone at 855.639.6300. We are here to help.