Configuring Patton SmartNode - Analog 2 and 4 Port FXO VoIP Gateways for 3CX
pixel500w-500x1
Zero Admin
With the new Dashboard
pixel500w-500x1
Bulletproof Security
With SSL certs and NGINX
pixel500w-500x1
Install on $150 Appliance
Intel MiniPC architecture
pixel500w-500x1
New, Intuitive Windows Client
More themes, more UC
pixel500w-500x1
More CRM Integrations
Scripting Interface to add your own
pixel500w-500x1
Improved Integrated Web Conferencing
iOS and Android apps included
pixel500w-500x1
Personal Click2Meet URLs

Patton Analog 2 and 4 Port FXO

Configuring Patton SmartNode FXO VoIP Gateway

Supported Models: Patton SmartNode SN4112 / SN4114 FXO

After you familiarize yourself with the basic concept of SIP Trunks (http://www.3cx.com/docs/manual/sip-trunks/) proceed to add a PSTN gateway into the PBX. All templates are designed to work with Patton SmartWare firmware and the device should run on the “latest 6.X firmware”. Trinity Firmware/Devices are currently NOT supported.

Configuring Patton SmartNode FXO VoIP Gateway

Supported Models: Patton SmartNode SN4112 / SN4114 FXO

Step 1: Add and Choose Device

Step 2: PSTN Line Setup

Step 3: Port Configuration

Step 3: Upload Configuration

Step 4: Inbound Rules

Step 5: Add Outbound Rules

This guide focuses on the setup of FXO (external analog). If you are looking for another PSTN technology:

Step 1: Add and Choose Device

Navigate to “SIP Trunks” within the 3CX Management Console and select “Add Gateway”:

  1. Select Brand: Patton
  2. Select model/device: Patton Analog FXO
  3. Number of Physical PSTN Ports on device: The amount of FXO ports the device has in total (not how many ports are going to be used)
  4. Main Trunk No: Define the number of your FXO lines which should act as catch all destination. Commonly your most important number of all.
  5. Press OK to save the device.

Step 2: PSTN Line Setup

Now you need to define some device and line specific options:

  1. Registrar: Enter your Patton FXO device’s  IP address.
    (the IP address will be set to static in case DHCP is being used)
  2. Subnet Mask: Enter your Network Mask size.
    (if network topologies requires routing informations such as default routes, see
    here how to add the default route to a Patton device).
  3. Tone Set: Define in which country your are using this device. If the country is not listed request from your telco the used tone set of your line.
  4. Number of SIM Calls: Define how many FXO ports are going to be used. This might be equal to the amount of physical PSTN ports the device has or less.

Step 3: Port Configuration

Navigate to the “Options” tab and in the section “PSTN Gateway Options”. In this section define how outbound calls should address your PSTN ports.

  1. Dial Delay: Set how the device should detect that the line is open and ready to dial. Most configurations will work once a dial tone is detected by the PSTN gateway, however, in some cases the wait time must extend beyond this.
  2. Hunting Mode: As all FXO ports will be placed in a hunt group, select how the Patton device should allocate the ports while placing outbound calls. Options are: “Normal” (always start from the first port) or opt to take a “Cyclical” approach (spreading the calls across all ports evenly in a round robin manner). Note: ports that are already in use will be skipped and the next available port will be used.

Step 3: Upload Configuration

By pressing the ”Generate config file”, the 3CX Management Console will directly open the web interface of the Patton gateway on the “Import Configuration” page (e.g. http://192.168.9.122/imp-cfg.html). A configuration file is automatically downloaded which then needs to be saved and uploaded onto the Patton device by using the browse and import button.

The device will reboot in order to apply the configuration. After this the “Port/Trunk” status on the Management Console should change from RED to GREEN.

Step 4: Inbound Rules

Analog lines (FXO) can present the calling number but not the called number. Therefore each FXO port is reflected with a fix DID number. This is allowing your to individually route calls received from FXO port 0 to destination A while calls to FXO port 1 are routed differently (and so on). The mapping is as follows:

  • FXO Port 0/0 indicates the dialed number: 000000
  • FXO Port 0/1 indicates the dialed number: 000001
  • FXO Port 0/2 indicates the dialed number: 000002
  • FXO Port 0/3 indicates the dialed number: 000003

Create those DIDs within the gateway to allow calls to be routed based on the port the call was received on. General inforation on how to manage inbound calls can be found here: http://www.3cx.com/docs/manual/inbound-rules/.

Step 5: Add Outbound Rules

To create “Outbound Rules” read Chapter 13 of the admin manual: Outbound rules - Routing outgoing calls.

You might also be interested in:

<