Skip to end of metadata
Go to start of metadata

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. 

The two key aspects of this solution, 1) the Switchvox and Digium Phones ability to detect that there is communication problem between the Phone and the PBX, and then with use of the Alternate Host setting.  The Alternate Host is configured with the IP Address (or FQDN) of the Vega Gateway ENP feature, giving the Digium Phone an alternate location to REGISTER and send calls to.  2) The Vega Gateway ENP feature is used to accept the incoming REGISTERs and calls and direct both Inbound and Outbound Traffic to assigned Ports and Phones.  Analog and VoIP Phones can make use of the PSTN access as well as call each other.

  Note: Digium D80 Phones do not support Alternate Host, thus do not work with this solution. (at the time this was written)

In a normal operation, the Digium Phones communicates with the Switchvox directly, in the case of a Remote Office, this would be the WAN IP of the Main Office Firewall, which Port Forwards traffic to the Switchvox.  When the Switchvox needs to make a PSTN call the PBX establishes communication with the Vega Gateway, which may have the Remote Office Firewall Port Forward to the Vega Gateway.


But things break, and other things fail.  The loss of communication can occur in many places.  PBX failure and broadband connection failures.  In any case, there is a loss of communication between the Digium Phones and Vega Gateway to the Switchvox.  These remote phones are no longer connected to the PBX for normal operation.  With the use of Alternate Host, these Remote Digium Phones can detect the loss of communication, and go into Failover Mode.  Also with the Alternate Host the Digium Phones can failover their communication with the Vega Gateway.  This allow Digium Phones to contact other Digium Phones, as well as any FXS Stations on the Vega Gateway, in addition use the FXO and T1/E1 Trunk lines for inbound and outbound calls.

 

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)


Under IP Configuration - complete the following information:

  • Gateway Address:  Enter the Default Gateway (Usually the Firewall)
  • DNS AddressEnter 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)


Under Phone Network - Modify - All 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:

Primary Host (PBX)

  • Host Address:  Enter the IP address or FQDN of the Switchvox, this is automatically entered based on the "Look Up External IP" pressed earlier

Alternate Host

  • 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 )



Modify the Extensions of only the D60/D62 and D65 Phones that are located at the Remote Office.

Note:  The follow steps are not the complete requirements for Extension creation, these steps are the requirements only for Remote Survivablity using Vega Gateway ENP.




Under Modify Extension - Phone Settings - Common Settings complete the following information:

  • Phone Password:  Enter a Password
  • Retype Phone PasswordReenter same Password
  • Phone NAT Traversal:  Select Always

Note:  Record this password for entry into the Vega Gateway.  Make sure this password long and secure using a mix of alpha numeric and special characters.



Under Create Extension - Phone Settings complete the following information:

  • Phone Password:  Enter a SIP Authentication Password
  • Retype Phone Password:  Enter the same SIP Authentication Password

Note:  This is the same SIP Authentication Password that will need to be entered into the Vega Gateway FXS Port configuration.



Click "Save SIP Extension"




Vega Gateway Configuration

General Configuration

NOTE

The following steps are specific to the setup of Remote Survivablity using the Vega Gateway ENP.  The following steps are additional configuration on top of Trunking and FXS Stations.  

Prior to enabling the Remote Survivablity 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.

https://wiki.sangoma.com/display/VG/Switchvox+Trunking+Configuration

https://wiki.sangoma.com/display/VG/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

1) ENP SIP Registrar for definition of the User and Authentication credentials.   The Digium Phone when configured with Alternate Host as the Vega Gateway ENP, the Phone will REGISTER to the Vega Gateway ENP.  The ENP needs to have the Username and Password for Authentication.

2) ENP Aliases for the Users.  These Aliases are the DIDs from the Gateway to route to individual extensions.

  • Use Aliases: Select "if_itsp_down"  This is needed for ENP to route Incoming Trunk calls to a specified extension, only when there is a loss of communication with the Switchvox.
  • Enabled:  Select Enable
  • Username:  This is the Extension Number of the Digium D60/D62 and D65 Phones.
  • Aliases:  Enter the corresponding DID from the FXO Port or T1/E1 Port that will ring this extension when in Failure Mode.
  • Password:  Enter the Phone Password, as defined in the Manage > Extensions > Modify > Phone Settings > Common Settings  , which was defined earlier.

Note:  Repeat this step for each Digium D60/D62 and D65 phone on the Remote Office.

Note:  Call Capacity should not exceed the Port/Channel capacity of the Vega Gateway.  4 FXS + 4 FXO Vega Gateway can have 8 Calls.  A Vega 100G Gateway can have 30 Calls. 

Note:  # of Phone REGISTERs impacts calls per second.  Max CPS of a Vega Gateway is 6 cps, with short Burst CPS support up to 12.  Do the math... How many phones x REG frequency = REG cps   ...   Vega cps - Reg cps = actual cps   ...   Leave enough actual cps to make calls effectively for your business.

Press Submit


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.

  • Mode:  Select "normal"
  • Proxy Test:  Select "options".  Here the Vega Gateway will send a OPTIONS ping to the Switchvox.
  • Test Interval (s):  Enter 30 Seconds.  Here the Vega Gateway will send an OPTIONS ping every 15 seconds (half time of Interval)
  • Transport:  Select UDP
  • Enable:  Select Enable
  • IP/Host:  Enter the WAN IP Address of the Firewall in front of Switchvox.  This is the "External IP Address" found in IP Configuration of the Switchvox.
  • Port:  Enter 5060
  • TLS Port:  Enter 5061, although this is not used.

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.   

  1. Local trunk gateways - these route calls to other Gateways, PBXs, and Channel banks outside the Vega Gateway (deselect the "Is PSTN Gateway?" checkbox)  
  2. PSTN gateways - these route calls to PSTN gateways, (select the "Is PSTN Gateway?" checkbox)   

In this Remote Office Survivalblity, when the Vega Gateway and the Digium Phone can no longer communicate with the Switchvox, we want to use the PSTN Gateway on the Vega Gateway (itself - Port 5060 of the same Vega Gateway).

The following settings, similar to SIP ITSP Proxies, is to test the accessibility of the PSTN Gateway.  Is there a PSTN Gateway available?

  • 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.   

Calls matching the attributes are routed to the specified gateway(s) (whether ITSP is up or down).  


PSTN Gateways have routing restrictions:   

  1. Calls from PSTN gateways cannot be routed to other PSTN gateways   
  2. Calls from PSTN gateways cannot be routed to the ITSP   
  3. Calls from unregistered users (even if " trusted") cannot be routed to PSTN gateways 


Press Add, to add a second Dial Plan

  • 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



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.













  • No labels