The following example demonstrates a complete FXS to IP PBX deployment using an Edge 8300 model and the Edge 8000 Series 24.1 software release. The example includes screenshots and specific values for all the major configuration areas of the deployment:
- Setup Wizard
- Licensing
- SWe Edge provisioning
- SIP User Agent provisioning for FXS ports
For the entire provisioning process, including physically Installing Edge 8000 Hardware, refer to Workflow for Initial Setup.
While the goal of this example is not to provide a detailed configuration that meets the needs of every scenario, it does provide a starting point for building your own customized configuration for an FXS to IP PBX deployment.
Attention
The IP addresses shown in the examples may conflict with an existing or planned production network. Consult with your network administrator for the specific IP addresses required for your deployment.
Contents
Network and Call Flow Diagrams
In this demonstration, an Edge 8300 is configured to support two signaling groups:
- On the analog side, an FXS port connected to an analog phone
- On the private or LAN side, an IP PBX with VLAN logical sub-interfaces connected to an IP phone
The following diagrams depict the deployment topology, network interfaces, and call flows for this demonstration.
Deployment Topology
Network Interfaces
Signaling and Media Call Flows
Setup Wizard Values
After physically installing the device, the deployment team uses the Edge 8000 Setup Wizard to establish basic platform settings.
The following tables show the values entered in Setup Wizard for this FXS to SIP IP PBX demonstration. Consult your network design and deployment teams for the specific values appropriate for your network.
System Configuration
Hostname | Time Zone | 6WIND fastpath cores |
|---|---|---|
| e8000 | America/Mexico_City | 4 (default) |
Bridge Settings (BR1-4)
| Interface | Interface Name | IPv4 Address | Netmask | Members | DHCP server | Enable DHCP client | Setup Wizard Note |
|---|---|---|---|---|---|---|---|
| BR1 VNF Private | br1 | 10.56.67.166 | 24 | ge1 | [ ] disabled (press the space bar to toggle) | n/a | |
| BR2 VNF Management | br2 | 10.56.66.166 | 26 | ge7 (default) | [ ] disabled (press the space bar to toggle) | n/a | |
| BR3 VNF Internal | br3 | 169.254.1.1 (default) | 24 (default) | n/a | n/a | n/a | |
| BR4 VNF Public | br4 | 0.0.0.0 | 24 (default) | _____ (default) | n/a | [ * ] enabled (default) | DHCP Client requires manual configuration of the gateway and DNS settings. |
Gigabit Ethernet Settings (GE1-8)
| Interface | Interface Name | IPv4 Address | Netmask Length | Setup Wizard Note | |
|---|---|---|---|---|---|
| GE1 | ge1 | 0.0.0.0 (default) | 0 (default) | If the interface is a member of a bridge interface, do not set these values. | |
| GE2 | ge2 | 0.0.0.0 (default) | 0 (default) | If the interface is a member of a bridge interface, do not set these values. | |
| GE3 | ge3 | 0.0.0.0 (default) | 0 (default) | If the interface is a member of a bridge interface, do not set these values. | |
| GE4 | ge4 | 0.0.0.0 (default) | 0 (default) | If the interface is a member of a bridge interface, do not set these values. | |
| GE5 | ge5 | 0.0.0.0 (default) | 0 (default) | If the interface is a member of a bridge interface, do not set these values. | |
| GE6 | ge6 | 0.0.0.0 (default) | 0 (default) | If the interface is a member of a bridge interface, do not set these values. | |
| GE7 | ge7 | 0.0.0.0 (default) | 0 (default) | If the interface is a member of a bridge interface, do not set these values. | |
| GE8 | ge8 | 0.0.0.0 (default) | 0 (default) | If the interface is a member of a bridge interface, do not set these values. |
Small Form-factor Pluggable (SFP9-10)
| Interface | Interface Name | IPv4 Address | Netmask Length | Enable DHCP Client (default = disabled) | Setup Wizard Notes | |
|---|---|---|---|---|---|---|
| SFP9 | sfp9 | 0.0.0.0 (default) | 0 (default) | [ ] disabled | If the interface is a member of a bridge interface, do not set these values. DHCP Client requires manual configuration of the gateway and DNS settings. | |
| SFP10 | sfp10 | 0.0.0.0 (default) | 0 (default) | [ ] disabled | If the interface is a member of a bridge interface, do not set these values. DHCP Client requires manual configuration of the gateway and DNS settings. |
Default Gateway
IPv4 Address | Setup Wizard Note |
|---|---|
| 10.10.216.1 | MUST be an IPv4 address within a subnet on an interface. Note: This is the external gateway that the Edge 8000 device routes to in order to reach outside of itself, beyond its own subnet. It's how the gateway can respond when you ping it. Without this, the Edge 8000 device doesn't know where to send its responses. |
SWe Edge Settings
CPUs (1 2 4) | Memory (MBs) | Extra Interface 1 | Extra Interface 2 | Setup Wizard Note |
|---|---|---|---|---|
| 2 (default) | 2048 (default) | br4 | ________________ | The Extra Interface values are any of the physical port names, for example, ge1, sfp9 or the VNF Public bridge interface name, br4. |
SWe Edge and Analog Licenses
In this demonstration, the Edge 8300 device requires SWe Edge and Analog licenses.
To view the license features, open a browser and enter the SBC SWe Edge webUI IP address. Log in as user admin.
Note
In this demonstration, the SBC SWe Edge webUI IP address is 10.56.66.166. This is the address assigned as the BR2 VNF Management IP in Setup Wizard.
Click the Settings tab and navigate to System > Licensing > Current Licenses.
The following screenshots illustrate the Analog and SWe Edge licenses employed for this demonstration.
Analog License Features
SWe Edge License Features
SWe Edge Configuration
Network Interface Values
Network Interfaces define the way the Edge 8000 device communicates with the external network.
The Edge 8000 supports system-created logical interfaces known as Admin IP, Ethernet 1 IP, Ethernet 2 IP, and Ethernet 3 IP for the SWe Edge function. In addition to the system-created logical interfaces, the Edge 8000 supports user-created VLAN logical sub-interfaces.
In this demonstration:
- The Admin IP is an internal logical SWe Edge IP address that is not reachable from an external network. Its value is pre-set at the factory.
- The Ethernet 2 IP is an internal logical SWe Edge interface supporting a connection to the analog ports. Its value is pre-set at the factory.
The following IP addresses must be entered manually using the Edge 8000 webUI:
- the Ethernet 1 IP address, which is a SWe Edge logical interface supporting a connection to the LAN IP PBX
- the Ethernet 1.2626 IP address, which is a SWe Edge logical interface supporting a connection to a VLAN logical sub-interface to the LAN IP PBX
For this demonstration, the following Network Interface values have been set:
Network Interface Assignments
| Interface Name | IP Assign Method | Primary Address | Primary Netmask | Media Next Hop IP |
|---|---|---|---|---|
| Admin IP | Static | 169.254.1.251 | 255.255.255.240 | |
| Ethernet 1 IP | Static | 10.56.67.167 | 255.255.255.0 | 10.56.67.1 |
| Ethernet 1.2626 IP | Static | 10.10.203.157 | 255.255.255.128 | 10.10.203.129 |
| Ethernet 2 IP | Static | 169.254.1.120 | 255.255.255.128 |
Note
To create a VLAN I/F for a Logical Interface, navigate to SBC > Networking Interfaces > Logical Interfaces > Create VLAN I/F.
To display Network Interfaces in the SWe Edge WebUI:
- click the Settings tab
- navigate to SBC > Networking Interfaces > Logical Interfaces
The following screenshots illustrate the Network Interfaces defined for this demonstration.
Network Interfaces
Example of a Network Interface: Ethernet 1.2626 IP
Static Route Values
Static routes enable communication with remote networks. In a production environment, static routes are mainly configured for routing from a specific network to another network that can only be accessed through one point or one interface (single path access or default route). Points to consider include:
- For smaller networks with just one or two routes, configuring static routing is preferable. This is often more efficient since a link is not being wasted by exchanging dynamic routing information.
- For networks that have a LAN-side gateway on Voice VLAN or Multi-Switch Edge Devices (MSEs) with voice VLAN towards the SBC Edge, static routing configurations are not required.
Note
This demonstration does not have a LAN-side gateway, nor does it have MSEs.
For this demonstration, a Static Route is defined to give access to the IP PBX.
Static Route fields include:
- Destination IP – Specifies the destination IP address.
- Mask – Specifies the network mask of the destination host or subnet. (If the 'Destination IP Address' field and 'Mask' field are both 0.0.0.0, the static route is called the 'default static route'.)
- Gateway – Specifies the IP address of the next-hop router to use for this static route.
To display Static Routes in the SWe Edge WebUI:
- click the Settings tab
- navigate to SBC > Protocols > IP > Static Routes
The following screenshot illustrates the Static Routes defined for this demonstration.
Static Routes
Signaling Groups
Signaling groups allow telephony channels to be grouped together for routing and shared configuration purposes. They are the locations from which ingress calls enter and to which egress calls route out. They are also the location from which Tone Tables are selected. In the case of SIP, they specify protocol settings and are linked to server, media, and mapping tables.
The following diagram depicts the role of Signaling Groups in a typical call flow sequence. Every call enters through an ingress Signaling Group, traverses through a Call Routing Table and its associated Transformation Table or Tables, and exits through an egress Signaling Group. For each Signaling Group, a SIP Server Table or Local Registrar defines where the call should go on egress.
SIP to SIP Call Flow Sequence
For this demonstration, two Signaling Groups are defined :
- To/From IP PBX Signaling Group – serves the LAN-side IP PBX and associated IP phones
- To/From FXS Signaling Group – serves the analog-side FXS ports and associated analog phones
The following fields must be modified, as a minimum, for each Signaling Group:
- SIP Profile
- Tone Table
- Call Routing Table
- SIP Mode
- SIP server table / Local Registrar
- Media List ID
- Signaling/Media Source IP
- Listen Ports
- Federated IP/FQDN
Additional fields may be modified per end-user requirements.
Note
Be sure to set the following parameters correctly per your network plan:
- Signaling/Media Source IP – this value is specific to the associated Signaling Group
- Federated IP/FQDN – this value is specific to the associated Signaling Group
- as the IP address of the IP PBX (10.35.180.111 in this example) for the IP PBX Signaling Group, or
- as the IP address of the internal SIP User Agent (169.254.1.100 in this example) for the FXS Signaling Group
To display Signaling Groups in the Edge 8000 webUI:
- click the Settings tab
- navigate to SBC > Signaling Groups
The following screenshots illustrate the Signaling Groups defined for this demonstration.
To/From IP PBX Signaling Group
To/From FXS Signaling Group
SIP Profiles
SIP Profiles control how the Edge 8000 device communicates with other SIP devices. SIP Profiles control important characteristics such as session timers, SIP header customization, SIP timers, MIME payloads, and option tags.
In this demonstration, two SIP Profiles are defined, one for each Signaling Group:
- To/From IP PBX Profile – serves the To/From IP PBX Signaling Group
- Default SIP Profile – serves the To/From FXS Signaling Group
To display SIP Profiles in the Edge 8000 webUI:
- click the Settings tab
- navigate to SBC > SIP > SIP Profiles
The following screenshots illustrate the SIP Profiles defined for this demonstration.
To/From IP PBX Profile
Default SIP Profile
Tone Tables
Tone Tables allow the Edge 8000 administrator to customize the tones a user hears when placing a call. You can modify the tone to match your local PSTN or PBX. The default Tone Table is configured for the values used in the United States for the following categories: Ringback, Dial, Busy, Congestion, Call Waiting, Disconnect, and Confirmation.
In this demonstration, each Signaling Group uses a unique Tone Table:
- United States Tone Table – serves the To/From IP PBX Signaling Group
- Default Tone Table – serves the To/From FXS Signaling Group
To display Tone Tables and associated profiles in the Edge 8000 webUI:
- click the Settings tab
- navigate to SBC > Tone Tables
The following screenshots illustrate the Tone Table and associated Tone Profiles defined for this demonstration.
United States Tone Table
Default Tone Table
Ringback Tone Profile
Congestion Tone Profile
Transformation Tables
Transformation Tables facilitate the conversion of names, numbers, and other fields when routing a call. They can, for example, convert a public PSTN number into a private extension number or into a SIP address (URI). Every entry in a Call Routing Table requires a Transformation Table.
In this demonstration, two Transformation Tables are defined:
- Transformation Table, IP PBX Numbers
- supports the Call Routing Table, From IP PBX
- matches the telephone number ranges of the IP phones
- Transformation Table, FXS Numbers
- supports the Call Routing Table, From FXS
- matches the telephone number ranges of the analog phones
To display Transformation Tables in the Edge 8000 webUI:
- click the Settings tab
- navigate to SBC > Call Routing > Transformation
The following screenshots illustrate the Transformation Tables defined for this demonstration.
Note
To understand Input Field and Output Field values, refer to SBC Edge Regular Expressions for Number Matching and Transformation.
Transformation Table – IP PBX Numbers
Transformation Table – FXS Numbers
Call Routing Tables
Call Routing Tables allow calls to be carried between signaling groups, thus allowing calls to be carried between ports and between protocols. Call Routing Tables define routes, which allow for flexible configuration of which calls are carried and how they are translated. These tables are one of the central connection points of the system, linking Transformation Tables, Message Translations, Cause Code Reroute Tables, Media Lists, and the Signaling Groups.
Each Signaling Group has one Call Routing Table. In this demonstration, two Signaling Groups, each with its own Call Routing Table, are defined:
Signaling Group and Matching Call Routing Table
| Signaling Group | Call Routing Table |
|---|---|
| To/From IP PBX | From IP PBX |
| To/From FSX | From FXS |
The following fields of the Call Routing Table must be modified as a minimum:
- Number/Name Transformation Table
- Destination Signaling Groups
Additional fields may be modified per end-user requirements.
To display Call Routing Tables in the Edge 8000 webUI:
- click the Settings tab
- navigate to SBC > Call Routing > Call Routing Table
The following screenshots show the two Call Routing Tables and the entry in each table. Each entry specifies a different Transformation Table.
Call Routing Table – From IP PBX
Entry – To FXS
Call Routing Table – From FXS
Entry – To IP PBX
SIP Server Tables
SIP Server tables contain the IP address or FQDN of one or more SIP servers where INVITE messages can be sent to egress calls on a Signaling Group. The entries in the tables provide information about the IP Addresses, ports, and protocols used to communicate with the servers. The entries also contain links to counters that are useful for troubleshooting.
In this demonstration, one SIP Server Table, IP PBX, serves the To/From IP PBX Signaling Group.
The following fields of the SIP Server Table must be modified as a minimum:
- Host FQDN/IP
- Port
- Protocol
Additional fields may be modified per end-user requirements.
To display SIP Server Tables in the Edge 8000 webUI:
- click the Settings tab
- navigate to SBC > SIP > SIP Server Tables
The following screenshot shows the SIP Server Table, IP PBX, created for this demonstration.
SIP Server Table – IP PBX
Local Registrar
SIP provides a registration function that allows IP phone users to upload their current location for use by proxy servers. Registration creates a binding in a location service for a particular domain that associate an address-of-record URI with one or more contact addresses.
Registration entails sending a REGISTER request to a special type of UAS (User-Agent Server) known as a registrar. A registrar acts as the front end to the location service for a domain, reading and writing mappings based on the contents of REGISTER requests. This location service is then typically consulted by a proxy server that is responsible for routing requests for that domain.
In this demonstration, one SIP Local Registrar Table is defined.
The following field of a Local Registrar Table must be defined as a minimum:
- Maximum Number of Users
Additional fields may be modified per end-user requirements.
To display Local Registrars in the Edge 8000 webUI:
- click the Settings tab
- navigate to SBC > SIP > Local Registrars
The following screenshot shows the FXS SIP Registrar local registrar associated with the To/From FXS Signaling Group in this demonstration.
FXS SIP Registrar
Media Profiles
Media Profiles allow you to specify individual voice and fax compression codecs and their associated settings for inclusion in a Media List. Different codecs provide varying levels of compression, allowing a tradeoff between reducing bandwidth at the expense of reducing voice quality.
The following field of a Media Profile must be modified as a minimum:
- Codec
Additional fields may be modified per end-user requirements.
To display Media Profiles in the Edge 8000 webUI:
- click the Settings tab
- navigate to SBC > Media > Media Profiles
The following screenshots show the Media Profiles created for this demonstration.
IP PBX: G.711 A-Law
IP PBX: G.711 Mu-Law
IP PBX: G.729
Default G.711 A-Law
Default G.711 Mu-Law
Media Lists
A Media List contains a list of media profiles you order to give preference to more desirable codecs above less desirable ones. Profile order determines the order in which codecs are specified in SIP message(s) sent to a peer.
The following field of a Media List must be modified as a minimum:
- Media Profiles List
Additional fields may be modified per end-user requirements.
To display Media Lists in the Edge 8000 webUI:
- click the Settings tab
- navigate to SBC > Media > Media List
The following screenshots show the two Media Lists created for this demonstration:
- IP PBX List associated with the To/From IP PBX Signaling Group
- Default Media List associated with the To/From FXS Signaling Group
IP PBX List
Default Media List
FXS Port Configuration
Before an FXS port can be used for calls, it must be enabled and configured through the Ribbon Edge 8000 webUI. To configure FXS ports, you must configure global and port-level SIP User Agent (SIP UA) settings.
Global SIP UA Settings
The following parameters must be modified as a minimum for the SIP UA Global Configuration:
Minimum Global Configuration Settings for the SIP User Agent
| Parameter | Setting |
|---|---|
| Enable-SIPUA | This flag activates the FXS ports. This value is set to True for this demonstration. |
| SIP-SERVER-IP | This address is allocated to the internal packet port on the SWe Edge for internal SIP communication with PRI/FXS/FXO. It is set to the IP address of the SBC SWe Edge’s Ethernet 2 interface. This IP address is factory set to 169.254.1.120 and is not configurable. |
| SIP-UA-IP | This is the IP address allocated to FXS ports for SIP signaling to the SWe Edge. This IP address is factory set to 169.254.1.100 and is not configurable. |
| SIPUA-Bind-Port | This is set to 1025 for this demonstration. |
| Enable-Register | This is set to True for this demonstration, to allow the FXS ports to register to the SIP Server IP. |
To configure the SIP UA global settings in the Edge 8000 WebUI:
- click the Settings tab
- navigate to Gateway > SIP-User-Agent > UA-Setting > Global-Configuration
The following screenshots show the settings used for this demonstration.
SIP User Agent – Global Configuration
Port-Level SIP UA Settings
The following parameters must be modified as a minimum for the SIP UA Port-Level Configuration:
Minimum Port-Level Configuration Settings for the SIP User Agent
| Parameter | Setting |
|---|---|
| SIP Display Name | This is a string containing a name for the identified user. |
| SIP User Name | This is usually the phone number or extension. |
To configure the SIP UA port-level settings in the Edge 8000 WebUI:
- click the Settings tab
- navigate to Gateway > SIP-User-Agent > UA-Setting > Port-Level-Configuration
Note
In this demonstration, an analog phone is connected to the first FXS port, which is port [0].
The following screenshots show the settings used for this demonstration.
SIP User Agent – Port-Level Configuration
Overview
Content Tools