April 2013
nexVortex Setup Template
ZULTYS, INC.
Important! Your DNS Address
Your specific DNS address was provided in the Account Set Up email you received the day you opened your account. Your Authentication User ID and password are also in this email. If you need assistance locating this information, please contact [email protected].
Note: For all instructions throughout this Guide, you must substitute your DNS address wherever xx.xx.xxx.xxx is referenced.
Introduction
This document is intended only for nexVortex customers and resellers as an aid to setting up the Zultys PBX software to connect to the nexVortex Business Grade SIP Trunking Service.
Further Zultys information can be found at http://www.zultys.com.
Further help may be obtained by emailing [email protected].
If you find any errors in this document or have any suggestions, please email us at [email protected] so that we can make updates to this document.
Proxy Servers
To connect to the nexVortex network, you will need to add our proxy address into your phone system or device. The address of our proxy server will be a fully qualified domain name (FQDN). It was
automatically sent to you when your account was setup. If you no longer have this information or would like us to issue a new proxy key, please contact us at [email protected].
Note: If your system does not support a fully qualified domain name format, please contact support for a list of valid IP addresses for your account.
Special Characters
Please note that special characters should not be used anywhere in SIP configurations. These include, but are not limited to, @#$%&! and spaces.
Step 1:Trunk Configuration
Inbound service – You may receive SIP signaling from nexVortex from any of the four following IP addresses:
- 66.23.129.253 - 66.23.138.162 - 66.23.190.100 - 66.23.190.200
Your PBX should be configured with as many trunks as necessary to field traffic from these four IPs. If you need additional assistance ensuring your local PBX configuration meets this
requirement, please contact technical support for your equipment directly.
Outbound service – The most efficient way to ensure redundancy for outbound calling is to utilize DNS SRV for routing traffic to nexVortex. At present, if your PBX supports DNS SRV, pointing to
‘nexvortex.com’ as your Proxy IP address is all that should be necessary to ensure outbound redundancy.
If your PBX does not support DNS SRV, hopefully it supports configuration of multiple outbound proxies. If so, you should configure px1.nexvortex.com or px3.nexvortex.com or as your primary proxy IP address, and px5.nexvortex.com as your secondary IP address. If you need additional assistance with DNS SRV or configuring multiple outbound proxy IPs on your PBX, please contact technical support for your equipment directly.
Step 2: Trunk Settings
Your trunks MUST be configured to present your provisioned E911 number(s) (The E911 settings you created for your account at nexVortex.com) for Emergency calls (911) or emergency TEST calls (311 or 933). Either Remote-Party-ID or P-Asserted-Identity (preferred) headers containing your provisioned Network Edge Device (Firewall and/or Router)
In order to provide the highest level of service availability possible, nexVortex utilizes an n+1 architectural model for our call processing. You will need to ensure that your network edge (router and/or firewall) is configured to accommodate this architecture.
You may receive SIP signaling from nexVortex from any of the four following IP addresses:
- 66.23.129.253 - 66.23.138.162 - 66.23.190.100 - 66.23.190.200
You must ensure that each of these IPs is allowed to pass UDP 5060 traffic into your network and that this traffic is port‐forwarded (if necessary) to the internal IP of your PBX.
You will also need to open the RTP or audio ports. This is different for each customer premise device. Please reference Zultys for this detail. Your edge device must be configured to allow inbound RTP traffic on this port range from ALL IP addresses.
Configuring the Zultys MX System
Configuring the system is very simple. Before you start, please ensure you have access to the email sent to the registered user on the nexVortex account with the title ‘nexvortex Account Setup’. This email is sent after you register and order your plan(s) and contains the account information you need to complete the setup process.
Routing Configuration
When deploying the MX in a routing configuration there are six configuration steps:
1. Remove Default Gateway
2. Configure Ether Ports for Routing Mode 3. Provision Route Table
4. Provision SIP Servers
5. Provision ALG (Application Layer Gateway) 6. Provision Dial Plan
Step 1. Remove Default Gateway
1. Boot the MX in ‘Console Mode’.
2. In the ‘Provision’ menu go to ‘System Settings’
3. Select the ‘IP Addresses’ tab.
4. Delete any IP address in the ‘Default Gateway’ box.
Note: It should be blanks, not zeros.
Step 2: Configure Ether Ports for Routing Mode
1. Under ‘View’ select ‘Interface’ settings. You should see ‘Ethernet1’ (your private network/Local Area Network) and ‘Ethernet2’ for the WAN (Wide Area Network) or Public Network Connection.
2. Select one of the interfaces.
2.1. Select the ‘Configure’ button.
2.2. Select the ‘Parameters’ tab.
2.3. From the drop-down menu in the [Mode] field select 'Routing'.
2.4. Select the ‘IP Information’ tab.
2.5. In the 'Primary' row, insert the appropriate IP address.
For 'Ethernet1' the IP address for your specific network. Ask your system administrator if you are not sure. (e.g. 192.168.55.254)
For 'Ethernet2' the IP address will be the public IP address provided by your ISP (Internet
Service Provider).
Note: this address must be a static IP address if you will be receiving VOIP calls through the MX.
2.6. Select the ‘Apply’ button. Allow the MX to restart if necessary.
Step 3: Provision Route Table
1. Under ‘View’ select ‘Routes’.
2. There should be at least one entry on the ‘Static’ tab; a default route to the WAN Default Gateway (Next Hop field).
3. On the ‘Connected’ tab, you must include an entry for your LAN IP (Next Hop is 192.168.1.249 in this example)
Step 4: Provision SIP Server
1. In the ‘Provisioning’ menu select ‘SIP Servers and ITSPs’.
a. Select the ‘SIP Servers’ tab:
b. Under the ‘Name’ column double click the first row field and enter: NexVortex.
c. Under the ‘Type’ column double click the first row field and select ‘External’ from the drop down menu.
d. Under the ‘Address’ column double click the first row field and enter: xx.xx.xxx.xxx.
e. Under the ‘Port’ column double click the first row field and enter: 5060.
f. Under the ‘“From”domain’ column double click the first row field and enter your company domain or your company name.
g. Under the ‘Codec Profile’ column, select ‘Don’t Care’ from the drop down menu unless you have specific requirements for audio compression related to your network or your ISP service.
2. Ensure that the ‘Register’ box is unchecked if your PUBLIC IP address is STATIC.
Select the ‘Authentication’ tab. Double click the first row under the ‘Realm’ column.
3. In the ‘Realm Domain’ field enter “nexvortex.com.”
4. From the nexVortex Account Setup email, obtain the ‘Authentication Username’ and enter it in to the ‘User Name’ field. Please ensure you have no hidden characters or trailing spaces.
5. From the nexVortex Account Setup email, obtain the ‘Authentication Password’ and enter it in to the ‘Password’ field. Re-enter in the ‘Confirm Password ‘field.
Note: The password is case sensitive and must be entered as it has been provided. Please ensure that you have no hidden characters.
Step 5: Provision SBC
1. In the ‘Provision’ menu select he ‘SBC’ option.
a. Ensure each checkbox for the 0.0.0.0/0 entry is selected.
Note: It is important to make sure that the network address on the ‘System Settings|IP addresses’ under the ‘Ethernet LAN|IP address (main)’ and ‘Ethernet LAN|IP address (RTP)’ header is also listed in the ‘SBC’
table as a private network. (e.g. 192.168.1.0 with a subnet of 255.255.255.0 so as to encompass both addresses.)
Step 6: Provision Dial Plan
1. In the ‘Configure’ menu go to the ‘Dial Plan’ option.
a. Setup a call pattern so that when users dial externally, it gets routed to the nexVortex SIP proxy. The full 11 digits for domestic (US) calls (e.g.17035790200) and international calls need to be proceeded with the 011 then country code (e.g. 011442087510202).
b. Select the ‘Routing’ tab. Right-click within the white field and select ‘New Pattern’ from the pop-up menu for each of the follow patterns.
c. Under the following column headers fill in the appropriate information for domestic calling.
Name = [Choose a name i.e. “Domestic”]
Source = Don’t Care
Pattern = 1XXXXXXXXXX [note: 1 + ten “X”’s] Destination = choose SIP Server:NexVortex from the list. Transform = XXXXXXXXXXX [note: eleven “X”’s] Restricted = unchecked d. Under the following column headers fill in the appropriate information for international
calling.
Name = [Choose a name i.e. “International”]
Source = Don’t Care Pattern = 011XXX@
Destination = choose SIP Server:NexVortex from the list.
Transform = XXXXXX@
Restricted = unchecked
Optional: If you want the familiar 7 digit dialing on your system. Under the following column headers fill in the appropriate information for seven digit local dialing within your area code.
Name = [Choose a name i.e. “Local”]
Source = Internal
Pattern = [2-9]XXXXXX (including the brackets) Destination = choose SIP
Server:NexVortex from the list. Transform = 1AAAXXXXXXX [replace the “A”s with your area code
Restricted = unchecked
Note: Please ensure that you know the 911 call back number and that it is routed appropriately. For further details please log in to your account and click on 911.
Firewall/Router Paragraph
You will need to open UDP port 5060 on your firewall to enable the SIP signaling to traverse.
Important! Your DNS Address
Your specific DNS address was provided in the Account Set Up email you received the day you opened your account. Your Authentication User ID and password are also in this email. If you need assistance locating this information, please contact [email protected].
Note: For all instructions throughout this Guide, you must substitute your DNS address wherever xx.xx.xxx.xxx is referenced.
Troubleshooting
Customer System will not register with nexVortex:
- Check the system is pointing at xx.xx.xxx.xxx - Check UDP port 5060 is open on the firewall
- Check NAT translation is correct between LAN private IP address and public IP address - Check you have the correct proxy user name and password configured.
Customer System cannot make a call:
- Check the system is pointing at xx.xx.xxx.xxx - Check UDP port 5060 is open on the firewall
- Check NAT translation is correct between LAN private IP address and public IP address - Check you have the correct proxy user name and password configured.
Customer System cannot receive a call:
- Some systems require our IP Address xx.xx.xxx.xxx for verification to be configured - Check UDP port 5060 is open on the firewall
- Check NAT translation is correct between LAN private IP address and public IP address - Check that you have setup the IP route for the number correctly with nexVortex. This is
done through the customer or reseller Partner Connect portal->Preferences->Inbound Number Routing
- Check that the dial plan is configured to route the number to a valid location on the customer system.
One way audio or no audio after call is setup:
- Check the RTP audio UDP ports are open on the firewall.
Further help may be obtained by emailing [email protected].
