You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Contents

Introduction

The following example demonstrates a complete FXO to IP PBX deployment using an Edge 8300 model and the 

Unable to show "metadata-from": No such page "_space_variables"
24.1 software release. The example includes screenshots of menus found in all the major configuration areas, including:

  • Setup Wizard
  • SWe Edge and Analog Licensing
  • SWe Edge provisioning
  • SIP Gateway provisioning for FXO ports

Refer to Workflow for Initial Setup for the entire provisioning process, including physically Installing Edge 8000 Hardware.

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 a customized configuration for an FXO 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.

Network and Call Flow Diagrams

In this demonstration, an 

Unable to show "metadata-from": No such page "_space_variables"
8300 product is configured to support two signaling groups:

  • On the analog side, an FXO port connects to an analog PBX, which connects to an analog phone
  • On the private or LAN side, a gigabit Ethernet port connects to an IP PBX, which connects to an IP phone

The following diagrams depict the network topology, network interfaces, and call flows of this demonstration.

Network Topology

Edge 8300 Network Interfaces

Signaling and Media Call Flows

Setup Wizard Values

After physically installing the device, the deployment team uses the 

Unable to show "metadata-from": No such page "_space_variables"
Setup Wizard to establish basic platform settings.

The following tables show the values entered in Setup Wizard for this demonstration. Consult your network design and deployment teams for specific values appropriate for your network.

System Configuration

Hostname

6WIND fastpath cores

e80004 (default)

Set the Hostname according to the instructions of your local administrator or deployment team. Leave the 6WIND fastpath cores set to the default value.

Bridge Settings (BR1-4)

Interface Interface NameIPv4 AddressNetmaskMembers

DHCP server
(default = enabled)

Enable DHCP client
(default = enabled)

Setup Wizard Note
BR1 VNF Privatebr110.56.68.9024 (default)ge1

[   ] disabled (press the space bar to toggle)

n/a


BR2 VNF Managementbr210.56.88.9022ge7 (default)[   ] disabled (press the space bar to toggle)n/a
BR3 VNF Internalbr3169.254.1.1 (default)24 (default)n/an/an/a
BR4 VNF Publicbr40.0.0.0 (default)
24 (default)_____ (default)n/a[ * ] enabled (default)DHCP Client requires manual configuration of the gateway and DNS settings.
BR5 VNF Additionalbr50.0.0.0 (default)24 (default)_____ (default)n/a[ * ] enabled (default)DHCP Client requires manual configuration of the gateway and DNS settings.

In this demonstration:

  • Bridge 1 and Bridge 2 are set according to the IP addresses given by the local network administrator. Consult your network administrator for the values appropriate for your own network.
  • Bridge 3 (br3) is an internal bridge and is not configurable.
  • Bridge 4 and Bridge 5 are not used.

Gigabit Ethernet Settings (GE1-8)

InterfaceInterface NameIPv4 AddressNetmask Length
Setup Wizard Note
GE1ge10.0.0.0 (default)0 (default)


If the interface is a member of a bridge interface, do not set these values.

GE2ge20.0.0.0 (default)0 (default)


If the interface is a member of a bridge interface, do not set these values.

GE3ge30.0.0.0 (default)0 (default)


If the interface is a member of a bridge interface, do not set these values.

GE4ge40.0.0.0 (default)0 (default)


If the interface is a member of a bridge interface, do not set these values.

GE5ge50.0.0.0 (default)0 (default)


If the interface is a member of a bridge interface, do not set these values.

GE6ge60.0.0.0 (default)0 (default)


If the interface is a member of a bridge interface, do not set these values.

GE7ge70.0.0.0 (default)0 (default)


If the interface is a member of a bridge interface, do not set these values.

GE8ge80.0.0.0 (default)0 (default)


If the interface is a member of a bridge interface, do not set these values.

In this demonstration, all of the GE ports are left at their default settings.

Small Form-factor Pluggable (SFP9-10)

InterfaceInterface NameIPv4 AddressNetmask Length

Enable DHCP Client

(default = disabled)


Setup Wizard Notes
SFP9sfp90.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.

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

In this demonstration, the SFP ports are not used.

Default Gateway

IPv4 Address

Setup Wizard Note

10.56.88.1

MUST be an IPv4 address within a subnet on an interface.

This is the external gateway that the

Unable to show "metadata-from": No such page "_space_variables"
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
Unable to show "metadata-from": No such page "_space_variables"
device doesn't know where to send its responses. Set the value as given by your local network administrator or deployment team.

SWe Edge Settings

CPUs (1 2 4)

Memory (MBs)

Extra Interface 1

Extra Interface 2

Setup Wizard Note

2 (default)2048 (default)________________________________

The Extra Interface values are any of the physical port names, for example, ge1, sfp9 or the VNF Public bridge interface name, br4.

In this demonstration, the Extra Interfaces are not used.

SWe Edge and Analog Licenses

In this demonstration, the Edge 8300 device employs SWe Edge and Analog licenses.

To view the licenses, open a browser and enter the

Unable to show "metadata-from": No such page "_space_variables"
webUI IP address. Log in as user admin.

The webUI IP address is the address that was assigned as the Bridge 2 VNF Management IP during Setup Wizard.  In this demonstration, the webUI IP address is 10.56.88.90.

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

Networking Interface Values

Networking Interfaces define the way the SWe Edge component within the

Unable to show "metadata-from": No such page "_space_variables"
device communicates with internal and external networks. 

The Edge 8300 device supports system-created SWe Edge logical interfaces as follows:

  • Admin IP – an internal-facing logical SWe Edge address that supports management access to the SWe Edge; it is pre-set at the factory and not configurable
  • Ethernet 1 IP – an external-facing logical SWe Edge address that supports a connection to the LAN IP PBX; enter the IP address manually using the 
    Unable to show "metadata-from": No such page "_space_variables"
     webUI
  • Ethernet 2 IP – an internal-facing logical SWe Edge address that supports a connection to the analog ports (including the FXO ports); it is pre-set at the factory and not configurable

The following table summarizes the Networking Interfaces used for this demonstration.

Networking Interface Assignments

Interface NameIP Assign MethodPrimary AddressPrimary NetmaskMedia Next Hop IP

Manual Entry or Factory Pre-Set?

Admin IPStatic169.254.1.251255.255.255.240
Factory pre-set
Ethernet 1 IPStatic10.56.68.190255.255.255.010.56.68.1Manual 
Ethernet 2 IPStatic169.254.1.120 255.255.255.128
Factory pre-set

To display Networking Interfaces in the

Unable to show "metadata-from": No such page "_space_variables"
WebUI:

  • click the Settings tab
  • navigate to SBC > Networking Interfaces > Logical Interfaces

The following screenshots illustrate the logical Networking Interfaces defined for this demonstration.

Networking Interfaces

Example of a Networking Interface: Ethernet 1 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.

This demonstration does not have a LAN-side gateway, nor does it have MSEs.

For this demonstration, a Static Route is not necessary for access to the IP PBX because all of the LAN interfaces (Ethernet 1, Bridge 1, and the IP PBX) are on the same subnet. 

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 FXO Signaling Group – serves the analog-side FXO 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. It specifies the Logical IP address at which SIP messages are received. This address is used as the source IP for all SIP messages leaving the 8K through this Signaling Group.
  • Federated IP/FQDN – this value is specific to the associated Signaling Group. The Federated IP/FQDN feature acts as an access control by defining from which server a SIP Signaling Group will accept messages:
    • IP address of the IP PBX (10.56.68.50, in this example) for the To/From IP PBX Signaling Group, or 
    • IP address of the internal SIP Gateway (169.254.1.30, in this example) for the To/From FXO Signaling Group

To display Signaling Groups in the

Unable to show "metadata-from": No such page "_space_variables"
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 FXO Signaling Group

SIP Profiles

SIP Profiles control how the

Unable to show "metadata-from": No such page "_space_variables"
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 FXO Signaling Group

To display SIP Profiles in the

Unable to show "metadata-from": No such page "_space_variables"
webUI:

  • click the Settings tab
  • navigate to SBC > SIP > SIP Profiles

The following screenshots illustrate the two SIP Profiles used for this demonstration.

To/From IP PBX Profile

Default SIP Profile

Tone Tables

Tone Tables allow the

Unable to show "metadata-from": No such page "_space_variables"
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 FXO Signaling Group

To display Tone Tables and associated profiles in the

Unable to show "metadata-from": No such page "_space_variables"
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, Match IP PBX
    • supports the Call Routing Table, To/From IP PBX
    • matches the telephone number ranges of the IP phones
  • Transformation Table, Match FXO
    • supports the Call Routing Table, To/From FXO
    • matches the telephone number ranges of the analog phones

To display Transformation Tables in the

Unable to show "metadata-from": No such page "_space_variables"
webUI:

  • click the Settings tab
  • navigate to SBC > Call Routing > Transformation

The following screenshots show the two 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 – Match IP PBX

In an FXS (Central Office) to FXO (your house, for example) call scenario, the call is point-to-point and, therefore, comes without a To header. In this Transformation Table, Match IP PBX, the Output Field transforms the called number to 3001 to reach the 3001 extension configured on the IP PBX.

Transformation Table – Match FXO

In this Transformation Table, Match FXO, when the To header contains a called number that has an NXX of 220, the Output Field transforms the called number to NXX plus the next 4 digits (no dashes): 2203002.

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 configurations of which calls are carried and how they are translated. The Call Routing 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.

In this demonstration, two Signaling Groups are defined, each with its own Call Routing Table.

Signaling Group and Matching Call Routing Table and Transformation Table

Signaling Group Call Routing Table Transformation Table
To/From IP PBXFrom IP PBXMatch FXO
To/From FSO
From FXOMatch IP PBX

The following fields of the Call Routing Table must be modified as a minimum:

  • Description
  • Number/Name Transformation Table
  • Destination Signaling Groups
  • Audio Stream Mode

Additional fields may be modified per end-user requirements.

To display Call Routing Tables in the

Unable to show "metadata-from": No such page "_space_variables"
webUI:

  • click the Settings tab
  • navigate to SBC > Call Routing > Call Routing Table

The following screenshots show the two Call Routing Tables, From IP PBX and From FXO, defined for this demonstration. 

 Call Routing Table – From IP PBX

This Call Routing Table, From IP PBX, contains an entry for the Match FXO Transformation Table.

Call Routing Table – From FXO

This Call Routing Table, From FXO, contains an entry for the Match IP PBX Transformation Table.


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, two SIP Server Tables are defined:

  • SIP Server Table, IP PBX – serves the To/From IP PBX Signaling Group
  • SIP Server Table, FXO SIP Server – serves the To/From FSO 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

Unable to show "metadata-from": No such page "_space_variables"
webUI:

  • click the Settings tab
  • navigate to SBC > SIP > SIP Server Tables

The following screenshot shows the two SIP Server Tables created for this demonstration. 

SIP Server Table – IP PBX

Here, 10.56.68.50 is the IP address of the IP PBX.

SIP Server Table – FXO SIP Server

Here, 169.254.1.30 is the hard-coded (non-configurable) internal IP address of the internal SIP Gateway serving the FXO port. The port number must be 1026. (See the SIP Gateway (SIPGW) component in the Edge 8300 Network Interfaces diagram.)

Local Registrar 

A SIP Local Registrar Table is not defined since FXO ports do not register in this demonstration.

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

Unable to show "metadata-from": No such page "_space_variables"
webUI:

  • click the Settings tab
  • navigate to SBC > Media > Media Profiles

The following screenshots show the Media Profiles created for this demonstration.

Media Profile for To/From IP PBX (Trunk): G.711 A-Law

Media Profile for To/From IP PBX (Trunk): G.711 Mu-Law 

Media Profile for To/From IP PBX (Trunk): Fax

Default G.711 A-Law

Default G.711 Mu-Law

Media Lists

A Media List contains a list of media profiles ordered 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

Unable to show "metadata-from": No such page "_space_variables"
webUI: 

  • click the Settings tab
  • navigate to SBC > Media > Media List

The following screenshots show two Media Lists created for this demonstration:

  • IP PBX List – used by the To/From IP PBX Signaling Group
  • Default Media List – used by the To/From FXO Signaling Group

IP PBX List


Default Media List


FXO Configuration

Before an FXO port can be used for calls, it must be enabled and configured through the 

Unable to show "metadata-from": No such page "_space_variables"
Unable to show "metadata-from": No such page "_space_variables"
webUI. To configure an FXO port, you must configure the global and port-level settings of the internal
Unable to show "metadata-from": No such page "_space_variables"
SIP Gateway. (See the diagram of the internal
Unable to show "metadata-from": No such page "_space_variables"
components at Edge 8300 Network Interfaces.)

Global SIP Gateway Configuration

The following parameters must be modified as a minimum for the global SIP Gateway configuration:

Minimum Global SIP Gateway Settings

ParameterSetting
Enable-SIP-GatewayThis is set to True for this demonstration, to allow the FXO ports to be activated for use.
Register-With-SIP-ServerThis is set to False for this demonstration. It is not required for FXO ports to register to the SIP Server IP.
SIP-SERVER-IP

This field is read-only, with a value of 169.254.1.120. The value represents the SWe Edge internal IP address (Ethernet 2 IP address) used for SIP signaling to and from the SIP Gateway (SIP-Virtual-IP) to support FXO calls.

SIP-Virtual-IP

This field is read-only, with a value of 169.254.1.30. The value represents the SIP Gateway internal IP address used for SIP signaling to and from the SWe Edge internal SIP-SERVER-IP to support FXO calls.

Override-FROM-User-Name

7001 (in this example).  This is what every INVITE FROM header will be set to by the 8K, for every call that comes in/out of either of the 2 FXO ports. 

SIP-Authentication-Name7001 (in this example). 
SIP-Authentication-Password7001 (in this example). 
Max-FXO-Port2.  This value is hard-coded.

To configure the global SIP Gateway settings in the

Unable to show "metadata-from": No such page "_space_variables"
WebUI:

  • click the Settings tab
  • navigate to Gateway > SIP-Gateway > Global-Configuration

The following screenshots show the global SIP Gateway settings used for this demonstration.

SIP Gateway – Global Configuration

Port-Level SIP Gateway Configuration

The following parameters must be modified as a minimum for the port-level SIP Gateway configuration:

Minimum Port-Level SIP Gateway Settings

ParameterSetting
Enable-FXO-port

True for FXO-Port:0
False for FXO-Port:1

To configure the SIP UA port-level settings in the 

Unable to show "metadata-from": No such page "_space_variables"
WebUI:

  • click the Settings tab
  • navigate to Gateway > SIP-Gateway > Port-Level-Configuration
Note

In this demonstration, an analog phone is connected to the first FXO port, which is port [0].

The following screenshots show the port-level SIP Gateway settings used for this demonstration.

SIP Gateway – Port-Level Configuration


  • No labels