...
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
This document will guide you through the process of configuring a Remote Survivability solution using the Enhanced Network Proxy (ENP) feature in the Vega Gateway to work with Switchvox and the Digium Phones.
Introduction
At times there calls for a solution that provide simple VoIP Phone Survivability where Phones can continue basic PSTN calling and local calling, should the PBX fail, or any broadband connection fail, resulting in a loss of connection and communication between the Phones and the PBX. In this document, the example when there is a Remote Office, where there are several Digium Phones, and a Analog Station connected over the Internet to the Main Office where the Switchvox is located. There is a Vega Gateway connected to the PSTN, either over FXO or T1/E1. Also connected to the Gateway is a FXS Analog Station. The Vega Gateway is configured to operate with the Switchvox to deliver Trunking and Analog Station solutions. This document will focus on the Remote Survivablity configuration of the Vega Gateway, and requirements of the Switchvox and Digium Phone configuration to ensure that Digium phones can use the Vega Gateway in a Failover Mode. This document will not discuss the configuration of the FXS Station, FXO Trunk and T1/E1 Trunk to the Switchvox, as there are other Wikis for this.
...
| Info |
|---|
Note: This example is for a Remote Office, very similar configuration is used if the Vega Gateway is co-located with the Switchvox. |
Remote Extensions
Both Digium D60/62 and D65 Phones and the POTS Phones on the Vega Gateway will REGISTER to the Switchvox. As these are Remote Phones, they will REGISTER to the WAN IP Address of the Firewall at the Main Office, the Firewall will Port Forward to the Switchvox. DPMA Provisioning will also be forwarded to the Swtichvox. An Alternate Host will also be configured to provide the Digium Phone the Vega Gateway IP Address to REGISTER to in the event of a Failure.
Switchvox Configuration
General Configuration
The Switchvox will typically have a Static IP or Fully Qualified Domain Name on the LAN and a Static IP or Fully Qualified Domain Name on the WAN (Internet). In this configuration we are defining the Digium Phones and Vega Gateway FXS Lines to REGISTER to the WAN IP of the Switchvox. Typically, the Switchvox reside behind a Firewall, thus the Firewall will Port Forward SIP Protocol to the Switchvox. From there the Switchvox will accept calls from the Digium Phones and the Vega Gateway FXS Line. In addition to the normal configuration, the Digium Phones are given an Alternate Host location, this is used when the Digium Phone detects that it no longer is in communication with the Swtichvox. When the Digium Phone is in Failover Mode, they will begin to call the Alternate Host, which is the Vega Gateway.
IP Configuration
Open the IP Configuration tab. (Server > Networking > IP Configuration)
...
Gateway Address: Enter the Default Gateway (Usually the Firewall)
DNS Address: Enter the DNS Server
Allow NAT Port Forwarding: Select YES
External IP Address: Either Enter the WAN IP of the Firewall or press "Look Up External IP"
...
Phone Networks
Open the IP Configuration tab. (Server > Networking > Phone Networks)
...
Note: All Networks is modified as all the Remote Phones will come from outside the Internal LAN.
When modifying "All Networks" complete the following information:
...
Host Address: Enter the IP Address of the Vega Gateway
Port: Enter the IP Address of the Vega Gateway ENP Rx Port (not 5060) - Note: See Later in Vega Gateway ENP setup
Transport: Select UDP
...
Manage Extensions
Open the Manage tab. ( Setup > Extensions > Manage )
...
Click "Save SIP Extension"
...
Vega Gateway Configuration
General Configuration
NOTE
The following steps are specific to the setup of Remote Survivability using the Vega Gateway ENP. The following steps are additional configuration on top of Trunking and FXS Stations.
Prior to enabling the Remote Survivability features on the Vega Gateway ENP, ensure that the FXS Stations, FXO and T1/E1 Trunking, and Digium Phones are completely operational. Phones and Stations are registered, Trunking is working.
Switchvox Trunking Configuration
Switchvox FXS Station Configuration
ENP
The following configuration applies to all variants of Vega Gateways.
Configuration > Expert Config > ENP
...
SIP Proxy Configuration
This section of ENP defines the ENP Mode, which is the core behavior of ENP, then SIP Realm, which is the SIP Domain, and the ENP Receive Port, which is different than the Gateway Port of the Vega Gateway and is used for the ENP feature.
Mode: Select "standalone_proxy"
Realm: Enter the IP Address of the Vega Gateway
Rx Port: Enter a Port, 6060, (and is not 5060) Note: This is the same port defined in Alternate Host Port field in the Switchvox.
...
Press Submit
...
SIP Proxy Auth Users
Two functions to this section
...
Note: Here is a configuration example from the Vega Gateway Quick Config where the DID is configured for a FXO Port, This DID should be an Alias for a Phone under SIP Proxy Auth Users.
...
SIP Proxy Filters
At minimum, the Trusted IP Addresses Filter needs to be configured. This defines allowed or trusted IP Addresses to access the ENP.
Enable: Select Enable
ipmin: Enter the Lowest numeric IP Address of the Remote Office
ipmax: Enter the Highest numeric IP Address of the Remote Office
...
Press Submit
...
SIP ITSP Proxies
This is where the ENP can determine where the Switchvox is located and when the communication is interrupted to the Switchvox.
...
Note: Upon 3 consecutive OPTION ping failures, the Vega Gateway will deem the Switchvox as down. Thus, if the Test Interval is 30 seconds, 3 consecutive failures will at 45 seconds, the Switchvox is deemed down.
...
Press Submit
...
Trunk Gateway
There are 2 types of trunk gateways.
...
SIP Messages from Trunk Gateway: Select "trust" This will allow the ENP to trust SIP calls from the local PSTN Gateway
Allow Calls from ITSP Proxy to PSTN: Select "never". Calls from the Switchvox should not be calling the ENP. Switchvox should be calling the Gateway port (5060) not the ENP port (6060 - defined earlier)
Transport: Select UDP
Mode: Select "normal"
Test: Select "options" This uses OPTIONs ping.
Test Interval(s): This is the interval in sending OPTIONs ping.
Gateway ID: 1 will always be the localhost or the Vega Gateway itself. This is what we want to use the send and receive calls from.
Enabled: Select Enable
Is PSTN Gateway?: Select Enable
IP/Host: For Gateway ID 1 - this will always be 127.0.0.1 for the Vega Gateway itself
Press Submit
...
Trunk Gateway Call Routing
When in Failover Mode, the Digium Phones will start calling the ENP of the Vega Gateway. A Dial Plan is needed to route calls to the Trunk Gateways defined in the previous step.
...
Enabled: Select to Enable
Description: Open Text field, enter a description
Call Attributes: Enter TEL:.* (TEL Colon Dot Asterisk)
Trunk Gateway ID List: Enter 1 This is for the Trunk Gateway ID 1 in the previous step which defines the internal PSTN Gateway.
Routing Rule: Enter linear_up
Redirection Responses: Enter 500-599
Press Submit
...
To receive call from POTS on your Dphones ( incoming calls from POTS ) , navigate to:
configuration → Expert config→ SIP
Modify profile 1 and set local domain == IP address of vega gateway
Save Configuration
You are done. Press Save Configuration.
...
You will have to reboot as well when changing IP Addresses.
...
Verify ENP Remote Survivablity
Digium Phone Registration with ENP
Configuration > Expert Config > ENP > SIP Proxy Registered Users
This is a registration status on the Vega Gateway ENP that shows the Digium Phones that are registered. Digium Phones should be registered for ENP to be operational.
