Manufacturer: Alcatel-Lucent Enterprise
Product name: OXO Connect
Release: ONE030
Manufacturer website:

Please make sure you’ve read our information about the form of phone numbers at incoming calls.

IMPORTANT: Please provide the SIP user name in the From User field.

To ensure that external connections (calls, forwardings, parallel call configurations) are routed correctly, please make sure that the easybell SIP user name is entered in the "From User" field of the SIP Invite.

Unfortunately, we do not have any information from the manufacturer on how this setting is implemented for this telephone system. If there are any problems with the telephony, please contact the manufacturer directly and point out this issue.

1. Basic Setup

1.1 System Connection Procedure

The following configuration procedure makes use of the Operations & Maintenance Center (OMC) for OXO Connect and involves on-line connection to the IP PBX using the OMC Expert-level session. Setting up the LAN parameters for OXO (i.e. "IP address", "subnet mask" and "Def. Router Address") is consequently the prime action to complete. When connected, you can select the English language in OMC by the "Options" menu and subsequently the "Language" menu.

1.2 Checking the Software License

A specific software license is mandatory to enable IP trunks on the system. In the OMC tab "Hardware and Limits", open "Software Key Features" and "Multi-site". Make sure that the number of IP Trunks "really activated" (i.e. the max number of channels simultaneously usable on the VOIP trunk) is greater than zero and well adapted to the customer site.


1.3 Numbering Plan Configuration

1.3.1 Installation Numbers

No matter what type of Trunk is considered, OXO's handling of public numbers is first based on the "Installation Numbers" data configured to be entered from the OMC "Numbering" menu.


1.3.2 DDI Numbers

In OMC, the Public Numbering Plan permits to configure the DDI numbers allocated to the IP PBX subscribers. In OMC, open "Numbering", "Numbering Plans" and the "Public Numbering Plan" tab.

In conjunction with the configuration of the previous step 1.3.1, this basic example allocates the DDI range "11 19" to the range of extensions beginning at "100".


1.3.3 Internal Numbering Plan

Accessible from the OMC "Numbering" and "Numbering Plans" menu, the internal numbering plan is the place where dialing of internal phones is first analyzed by the OXO Call Server.

This example defines the access to the system ARS table for phone numbers dialed and starting with 0. The "Drop" attribute also indicates that the initial 0 of the number is dropped before it is passed to the ARS Prefix table.


1.4 CLI for External Diversion

Important: Currently, we have no information from the manufacturer regarding which SIP header is used for transmitting the number in case of CLIP no screening. The correct SIP header needs to be specified accordingly in the easybell customer portal. To do so manually, go to the calling line identification settings in the number management section. In order to learn which SIP header needs to be used, please contact your PBX vendor or installation partner.

For the scenario of external call forwarding (for example, external caller A via internal subscriber B towards external destination C), this configuration permits to select the CLIP number transmitted to C (i. e. either A or B). The control can be made globally for all PBX users, or for each extension.

From the tabs "Part 1" and "Part 2" of "System Misc" and "Feature Design" menu, verify the parameters as shown in the next screenshot.


After selecting an individual extension from the menu "Subscribers/Basestation List", use the Details button to access the "Feature Rights" screen and then, adjust the CLI parameter in the same way as shown below.


1.5 Traffic Sharing and Barring

Though it is not described here, a correct configuration of traffic sharing, barring and subscriber feature rights is necessary for enabling outbound calls and other features via the SIP trunk.

2. SIP Trunk Setup

2.1 Importing the easybell Reference Profile with SIP Easy Connect

In order to proceed with next configuration steps, you require the file "DE_EASYBELL_ONE030_SIP_edxx.spf" on your computer. This is the SIP trunk profile file this guide is based on.

Using SIP Easy Connect and the provider profile file are strongly recommended in order to ensure correct and secure configuration and avoid mistakes. If you don't have the dedicated profile file, please contact ALE technical support or your ALE integration partner.

The following screenshot summarizes the import steps using the profile file.


2.2 Adding the VoIP Trunk

In OMC, open the "External Lines" menu and the "List of Accesses" tab and click on "Add Voip".


2.3 Assigning the Trunk to a Gateway

In order to assign the easybell SIP Trunk to a gateway, please fill in the requested parameters as shown in the screenshot below.


2.4 Hosting System Trunk Group

To enable phone calls via the SIP trunk, it is required to have the trunk included within a trunk group in the system. Two alternative cases are considered in the next screenshot. Open the OMC menu "External Lines" and "List of Trunk Groups" and carry out the steps 1 to 5 shown below.

At step 2 you can either include the SIP trunk access into the OXO main trunk group (i. e. step 2a for index #1) or into one of the secondary trunk groups (e. g. step 2b for index #2).

The SIP trunk can be placed freely into one or several trunk groups of the system to permit managing a differentiated control of traffic sharing for internal subscribers. The index number selected at step 2a or 2b is relevant for the further configuration in section 2.5.

2.5 ARS Trunk Group Lists

To enable voice calls via the ARS system, it is necessary to have ARS trunk groups created via the OMC menu "Numbering", under "Automatic Routing Selection" and "Trunk Groups Lists". In this menu, new lines are created by clicking the right mouse button and selecting the "Add" function.

Carry out the 1 to 4 as shown below. At step 3, you need to select the line index corresponding to the system trunk group previously defined at section 2.4.


2.6 Complementary Setup

The following steps are required for completing the OMC configuration as they are not automatically managed by SIP Easy Connect.

2.6.1 ARS Prefixes

ARS Prefixes are used in the system to build up the routing table of external calls. The initial digits dialed by a user are looked-up in the table lines, trying to match an existing prefix/ range number. Whenever a matching line is found, the call is conveyed through the specific trunk gateway (GW index) associated to this line.

In OMC, go to the "Numbering" menu and open "Automatic Routing Selection" and "Automatic Routing Prefixes".



As illustrated in the following screenshot, you can first insert a route-line covering all type of external calls. Use the "Add" function to create a new line and then, configure the line parameters as indicated.


In the call routing table, additional lines can be created to cope with specific public phone numbers, such as short numbers or emergency numbers. The next screenshot shows a typical example for France, including four prefix entries/ ranges and customized values in the marked regions 1 and 2.

Line 1: Coping with standard phone numbers starting with digit 0 (national and international calls)

Line 2: Coping with all public emergency numbers. The network attribute "emerg" permits the line to point automatically to the system list of emergency numbers. This list is country-dependent and can be edited via the OMC menu "Emergency" and "Emergency Numbers".

Line 3 and 4: Coping external short numbers. Depending on the country, the complete list of short numbers will require one or several ARS lines.

  • Line 3: Example for France, for short numbers beginning with digit 3 (such as 3611, 3900, ...)
  • Line 4: Example for France, for short numbers beginning with digit 1 (such as 11, 118712, ...)

In region 3, the "Calling" and "Called/PP" fields need to be set as shown in the screenshot above. The values shown in region 2 also need to be respected.


2.6.2 ARS SIP Accounts

The user credentials delivered by the SIP provider for authentication can be configured by entering the "Numbering" menu and opening "Automatic Routing Selection" and "SIP Accounts".

For solutions using several individual lines, it is necessary to create one SIP Account line per line (multi-account configuration). Otherwise, a single SIP Account line is generally sufficient.


2.6.3 VoIP Topology

Configuration of "static SIP/NAT" is required for solutions using the topology model referred as "Topology D". However, this step is not for easybell.

On the local CPE router, port forwarding for the relevant SIP ports to OXO would need to be configured accordingly.


2.6.4 System Flags

Some specific noteworthy addresses which are not imported by SIP Easy Connect may need to be configured manually.

The access to the system flags is done in the OMC "System Miscellaneous" menu in "Memory Read/Write" ("Debug Labels" or "Other Labels"). Please apply required flag changes in OMC very carefully and contact ALE technical support or your ALE integration partner.


2.7 Adjustments (Fine Tuning)

The next configuration steps refer to particular adjustments you can conduct based on the data imported by SIP Easy Connect as highlighted in the following screenhots.


2.7.1 VoIP Parameters: General

Go to the "Voice Over IP" menu and open the "VoIP: Parameter" settings and the "General" tab. Adjust the IP Quality of Service of VoIP Trunks (RTP Flow) by entering "10111000 DIFFSERV_PHB_EF" as shown in the following screenshot.


2.7.2 VoIP Parameters: Advanced

Öffnen Sie das über das Menü "Voice Over IP" die "VoIP: Parameter" Einstellungen und dort den Reiter "Erweitert".

In case of Dynamic Mode, adapt the value of the “sipgw_nat_ka” timer to the router “NAT keep Alive Timer” used to connect to the SIP provider.

This is the periodic timer used to send a SIP "OPTION" message to the provider. It can be used to maintain the router bindings opened for receiving incoming requests. Each router brand, release or version may have a specific timer value not known by ALE. In case of any issue or doubt in relation with this parameter, please contact your SIP or router provider directly.


2.7.3 VoIP Parameters: SIP Trunk

In the OMC "Voice Over IP", open "VoIP: Parameters" and the "SIP Trunk" tab. Adjust the IP Quality of Service of SIP trunk messages (SIP signaling) by entering "10111000 DIFFSERV_PHB_EF" as shown in the following screenshot.


2.7.4 Gateway Parameters: Media

Double-click on "External Lines" menu, and subsequently on "SIP" and "SIP Gateways". A new window "Gateway Parameters List" is displayed focusing on the index entry #1 of the SIP provider.

Press the button "Details".


In the newly opened "Gateway Parameter Details" window, now select the "Media" tab. Adjust the bandwidth to the site context as shown in the following screenshot.


2.7.5 Gateway Parameters: DNS

If you haven't done this already in the previous, double-click on "External Lines" menu, and subsequently on "SIP" and "SIP Gateways". In the "Gateway Parameter Details", open the "DNS" tab.

Replace the IP address by the private IP address of the LAN router. (This is the same value as configured as "Default Router Address" in the OMC "Hardware & Limits" menu, in "LAN-IP configuration" and the "LAN Configuration" tab.)


2.7.6 Gateway Parameters: Domain Proxy

The Operator will confirm the exact IP address of its SIP server to be configured in OMC. In the OMC menu "External Lines", open "SIP" and "SIP Gateways". Then, press the button "Details" and select the "Domain Proxy" tab of the "Gateway Parameters Details" window.

If necessary, change the IP address imported from the SIP profile to the relevant values defined by easybell.