Alcatel Lucent OXO R9.

00 - Sip Trunking (TC1843en-Ed01) - Svanto Wiki - Svanto Knowledge Base

Svanto Wiki / Svanto Wiki / Alcatel Lucent

Alcatel Lucent OXO R9.00 - Sip Trunking (TC1843en-Ed01)
Added by Sven Antonissen, last edited by Sven Antonissen on Jan 25, 2014

Technical Bulletin | Alcatel-Lucent OmniPCX Office

TC1843 ed.01
SIP TRUNK SOLUTION: SVANTO.NET (BE)
CONFIGURATION GUIDELINE R900
This document details the configuration necessary on the IPBX ALCATEL-LUCENT OXO R900 to let it inter-operate with the SIP trunk
offer of the Operator SVANTO.NET in Belgium.

Table of contents
1 GENERAL 3
1.1 REFERENCES 3
1.2 SCOPE OF THE DOCUMENT 3
1.3 SCOPE OF ALCATEL-LUCENT'S SUPPORT 4
1.4 SOFTWARE/ HARDWARE VERSIONS 4
1.5 FEATURE & SET COMPATIBILITY LIST 4
1.5.1 Supported Sets 4
1.5.2 Supported Features 5
1.5.3 Restrictions 5
2 SYSTEM GENERAL INFO AND BASIC SET UP 6
2.1 PRE-REQUIRED INFORMATION 6
2.2 SYSTEM CONNECTION PROCEDURE 7
2.3 NETWORK CONFIGURATION 7
2.4 (PUBLIC) NUMBERING CONFIGURATION 7
2.4.1 Installation numbers 7
2.4.2 DDI numbers 9
3 DETAILED SIP TRUNK CONFIGURATION 9
3.1 SIP ABILITY CHECK 9
3.2 SIP TRUNK CREATION 10
3.2.1 Management of VoIP channels 10
3.2.2 "Physical" Access associated to the SIP Trunk 11
3.2.3 Hosting System Trunk Group 12
3.3 INTERNAL NUMBERING PLAN 13
3.4 TRAFFIC SHARING AND BARRING (REMINDER) 13
3.5 ARS CONTEXT ASSOCIATED TO THE SIP TRUNK 13
3.5.1 ARS Trunk Groups Lists 13
3.5.2 Gateway/ Registrar Proxy parameters 14
3.5.3 ARS prefixes for remote Gateway with Static-IP 17
3.5.4 ARS prefixes for remote Gateway with Dynamic-IP 17
3.5.5 SIP format of public phone numbers 19
3.6 VOIP MISC PARAMETERS 20
3.6.1 SIP Timers 20
3.6.2 Fax (T38) 20
3.7 NOTEWORTHY ADDRESSES 21
3.7.1 Debug Labels 21
3.7.2 Other Labels 23
3.8 MISCELLANEOUS CONFIGURATION 24
3.8.1 Calling Identity when External Call Forward 24
4 SIP TRUNK CONFIGURATION ABSTRACT 25

1 General
The purpose of this document is to describe the configuration steps needed on the Omni PCX Office (OXO) release R900 to inter-
operate with the SIP commercial offer delivered by the Operator SVANTO.
1.1 References
Alcatel-Lucent documentation (available from the Business Partner Web Site):
Alcatel Lucent OXO R9.00 - Sip Trunking (TC1843en-Ed01) - Svanto Wiki - Svanto Knowledge Base

1. Alcatel-Lucent OmniPCX Office Communication Server- Expert Documentation

2. Alcatel-Lucent OmniPCX Office Communication Server- Public SIP Trunking
1.2 Scope of the document
This guideline documentation targets the configuration associated to the "SIP trunk" feature. It is intended for normal-skilled engineers
who are familiar with the OMC configuration tool and who know the basic set up of the IPBX. Management of local phones and trunk
resources are considered as basic topics and are therefore not covered herein.
In the document, when placed outside the OMC screen pictures, the parameters /values can be easily identified: they are put in green
with the leading the sign ~• placed in front. Some examples:
~• NP_International_Prefix = "00" (quoted when value is freely edited in OMC)
~• VoIP_RTP_Direct = True (non-quoted when value is selected from a user pick-list in OMC)
~• ARS_GWalive_Timer = (N/A) (when the parameter is not shown or disabled in OMC)

For deployment on a customer site, the config values provided in this doc must be respected, excepted if the parameter
name ends with "_example". This is a mark for site-dependent parameters: the value read is just an example and needs
to be adapted. Examples:
c3• LAN_Subnet_Mask_example = "255.0.0.0" c3• Access_Channels_example = "2"

Because they can be taken from a real customer site, some example parameters of the doc may be masked or partially masked with
asterisks in order to keep the privacy of sensible data (i.e. IP public addresses, logins, public phone numbers). Examples:
~• GW_Reg_Username_example = "3243*000" ~• NP_DDI_Range_example = "43*000 43*000"

1.3 Scope of Alcatel-Lucent's support

The present SIP trunk solution benefits of differentiated support at Alcatel-Lucent: Limited Availability support (LA level) when the
approval is on-going or, General Availability support (GA level once the approval process is fully achieved).

The support delivered by Alcatel-Lucent is strictly delimited by the approved interop context and the system
configuration that are detailed in this document. The protocol and functional aspects of the SIP trunk are in the
scope, but not the audio quality of calls for the part incumbent on the Operator or linked to the client's IP
infrastructure.

1.4 Software/ Hardware versions

INFRASTRUCTURE COMPONENT VERSION (minimal compatible)

OXO system ALZBE900/033.002

OMC Management Software OMC900/17.1a

1.5 Feature & Set Compatibility List

The two tables hereafter list the main inter-operation features and the models of sets that are supported in
the solution described. The "Supported" value corresponds to:
"YES" _> supported by Alcatel-Lucent (i.e. tests done or not necessary for the related context)
"NO" _> not supported (i.e. tests are KO or have not been done or are Not Applicable)
"WR" _> (With Restrictions") restricted support as detailed in section 1.5.3

SUPPORTED SETS (OXO/ SVANTO.NET) SUPPORTED * (YES / NO / WR) REMARKS

Analogue Z (POTS) NO NOT TESTED

Desktop IP 40x8 series YES

Alcatel Lucent OXO R9.00 - Sip Trunking (TC1843en-Ed01) - Svanto Wiki - Svanto Knowledge Base

Desktop UA 40x9 series NO NOT TESTED

Desktop MyICphone 8082 NO NOT TESTED

Desk phone series 8002/ 8012 NO NOT TESTED

Appli MyICmobile IPhone NO NOT TESTED

Appli MyICmobile Android NO NOT TESTED

DECT UA models (all) NO NOT TESTED

IP-DECT 4080 NO NOT TESTED

SIP Trunk Solution: SVANTO.NET (BE) Configuration Guideline R900 TC1843 ed.01
Copyright © 2013 by Alcatel-Lucent. All rights reserved page 4/28

1.5.2 Supported Features

The following table lists the main inter-operation features supported.

INTER-OP FEATURE (OXO/ SUPPORTED (YES/NO/WR)* REMARKS

SVANTO.NET)

Type Of topology YES Remote Hosted NAT

SIP Registration YES Provider WITH Registration

SIP Authentication YES Provider WITH Authentication

GW Dynamic Mgmt. YES

Direct RTP YES

Out Bound Basic Call YES

In Bound Basic Call YES

Dynamic Codec Mgmt. YES

Call Release YES

Internal Call Transfer YES

Internal Call Forward YES

Call Hold YES

In Bound Call to DDI YES

Reception of DTMF YES

Emission of DTMF YES

Emergency Calls NO TEST KO

Callers Repertory YES

CLIP In. & Out Bound YES

Alcatel Lucent OXO R9.00 - Sip Trunking (TC1843en-Ed01) - Svanto Wiki - Svanto Knowledge Base

CLIR In. & Out Bound YES

External Call Transfer NO TEST KO

External Call Forward YES

Conference with 2 Ext. YES

Out Bound Fax T38 NO NOT TESTED

In Bound Fax T38 NO NOT TESTED

Out Bound Fax G711 NO NOT TESTED

In Bound Fax G711 NO NOT TESTED

Dynamic Call Routing YES

Busy State YES

Preannouncement YES

1.5.3 Restrictions
None reported.

2 System General Info and Basic Set Up

2.1 Pre-required information
The tables below gather all necessary information that should be collected before starting the OXO configuration.

When the "Example Value" is empty, the parameter is either not relevant or not mandatory for the configuration with
this SIP Operator.

IP PARAMETERS

Data Type Parameter Example Value

IP Data subnetwork OXO CPU - Data IP 10.70.0.1

Default Gateway 10.0.0.1

Netmask 255.0.0.0

Data VLAN

IP Voice Subnetwork OXO CPU - Voice IP 10.70.0.1

Default Gateway 10.0.0.1

Netmask 255.0.0.0

Voice VLAN

Table of IP infrastructure parameters (to be customized for the customer site) SIP TRUNK PARAMETERS

Data Type Parameter Example Value

Numbering Plan Installation Number

Alcatel Lucent OXO R9.00 - Sip Trunking (TC1843en-Ed01) - Svanto Wiki - Svanto Knowledge Base

Public DDI range 43**000 43**000

SIP-Trunk Data SIP Operator GW IP (N/A)

Registered Username 3243***000

Login 3243***000

Password *****

SIP Operator Domain voip.svanto.net

SIP Customer Domain

SIP Realm voip.svanto.net

Outbound Proxy

Registrar IP address

Registrar name

Authentication name 3243***000

Resolving DNS server 1 8.8.8.8

Resolving DNS server 2 8.8.4.4

Table of SIP trunk parameters (communicated by the Operator)

SIP Trunk Solution: SVANTO.NET (BE) Configuration Guideline R900 TC1843 ed.01

2.2 System Connection procedure

In order to configure the IPBX, it's necessary to use the OMC software at the Expert level session
2.3 Network configuration
The IP configuration is to be set before going further. This is done using the OMC menu Hardware and Limits - > LAN IP
Configuration.

10.70.0.1255.0.0.010.0.0.1The "Boards" Tab shows the IP address for the main CPU and the default gateway. The main CPU IP
address
must be edited there ~
c3• LAN_Main_CPU_IPadd_example = "10.70.0.1"
The "LAN Configuration" Tab lets you edit the values of default gateway IP address and the subnet mask ~
~• LAN_Def_Router_IPadd_example = "10.0.0.1"
~• LAN_Subnet_Mask_example = "255.0.0.0"
Alcatel Lucent OXO R9.00 - Sip Trunking (TC1843en-Ed01) - Svanto Wiki - Svanto Knowledge Base

Once LAN-IP parameters are modified, a further system reboot ("Warm reset") is required to validate the
changes !!

2.4 (Public) Numbering configuration

As for any type of trunk, the public numbering used for SIP trunk is first ruled by the general numbering configuration of the PBX.
2.4.1 Installation numbers
Go to OMC Numbering -> Installation Numbers .to check/ edit the "Installation Numbers" screen

Intercity Code1
2
3
4
5
6
7000032 - Configuration for "Installation Numbers":
~ Installation Number : ~• NP_Instal_Number_example = ""
~ International Prefix : ~• NP_International_Prefix = "00"
~ International Code : ~• NP_International_Code = "32"
® Intercity Prefix : ~• NP_Intercity_Prefix = "0"
~ Intercity Code : ~• NP_Intercity_Code_example = ""
© Recall Prefix : ~• NP_Recall_Prefix = "0"
~ Alternative System CLIP : ~• NP_System_Alt_CLIP_example = ""

for inbound calls, the CLI of the DDI range is configured in OMC via a combination of the parameters
"NP_Instal_Number" (blank in the example above) and "NP_DDI_Range" (see 2.4.2).

2.4.2 DDI numbers

Alcatel Lucent OXO R9.00 - Sip Trunking (TC1843en-Ed01) - Svanto Wiki - Svanto Knowledge Base

Go to OMC:.. Numbering -> Numbering Plans – Public Numbering Plan Tab...

For an item stated as not supported and mentioning the remark "Tests not done": In case you would like or need to have
this item passed to the supported category and, if you are ready to collaborate with our approval process: simply send an email to
"[email protected]" and ask for the details related to the certification of the required item.
1.5.1 Supported Sets
The following table lists the models of supported sets.
Configuration for "Public Numbering Plan":

DDI range : * NP_DDI_Range_example = "43**000 43*000"

In conjunction with the configuration of section 2.4.1, this basic example allocates the DDI range "43**000 43**000" to the
extension "110".
3 Detailed SIP Trunk Configuration
Illustrated with OMC screenshots, this chapter describes the OXO configuration parts corresponding to the public SIP trunk and
the hosting IP infrastructure.
3.1 SIP ability check
The trunk is the link between the IPBX and the network. A specific SW licence is mandatory to enable IP trunks on the system.
The OMC menu Hardware and Limits -> Software Key Features gives an overview of the allowed features.

In the Multi-site Tab, check the number of "IP Trunks" really activated (number of channels available for the VOIP trunk).

3.2 SIP Trunk creation

The VoIP trunk uses a specific signaling protocol (i.e. SIP) and physical resources embedded in the IPBX (i.e. DSP's). To create
the SIP trunk in the system, it's first necessary to allocate some of the DSP resources to it.
3.2.1 Management of VoIP channels
Go to OMC Voice Over IP -> VOIP:Parameters - General Tab to check/ edit the requested parameters.
Alcatel Lucent OXO R9.00 - Sip Trunking (TC1843en-Ed01) - Svanto Wiki - Svanto Knowledge Base

x* x* x00000000 DIFFSERV_PHB_BESIP2- ~ the VOIP protocol in use :

c3• VoIP_Protocol = SIP
- ~ from the amount available in the system, the number of channels dedicated to VoIP trunks:
~• VoIP_Trunk_Channels_example = "2"
the RTP routing mode and codec management for IP extensions:
~ "RTP Direct" :
c3• VoIP_RTP_Direct = True
® "Codec pass-through for SIP trunk":
~• VoIP_Trunk_Codec_Passthru = True
~ "Codec pass-through for SIP phones":
c3• VoIP_Phone_Codec_Passthru = False
the IP Quality of Service :
© "IP Quality of Service" :
~• VoIP_IP_QoS_example = 00000000 DIFFSERV_PHB_BE
the control of G711 codec for Music On Hold:
~ "G711 codec for MOH and preannouncement " :
~• VoIP_G711_MOH = True
With OMC menu Voice Over IP -> VOIP:Parameters - DSP Tab , also define the global control of Echo
cancellation and the VAD parameters of VoIP calls.

Set DSP parameters as follows:

"Echo Cancellation" : * VoIP_DSP_Echo_Cancel = True*
"Voice Active Detection" : * VoIP_DSP_VAD = False*
3.2.2 "Physical" Access associated to the SIP Trunk
From OMC External Lines -> List of access, select the VoIP access associated to the VoIP trunk.
Alcatel Lucent OXO R9.00 - Sip Trunking (TC1843en-Ed01) - Svanto Wiki - Svanto Knowledge Base

31 22 Then, configure the access parameters:

"Public trunk" option : * Access_is_Public = True*
number of channels allocated to the SIP trunk access "VoIP-Trunk Ch.":
* Access_Channels_example = "2"*
"Alternative CLIP/COLP Number" :
* Access_Alt_CLIP_example = ""*

3.2.3 Hosting System Trunk Group

To enable phone calls over the SIP trunk, it's necessary to have this latter included within one Trunk Group of the system. Two
alternative cases are considered here below.
Use the OMC menu External Lines ->List of Trunk Groups is used for that.

Carry out the selections and push-button steps 1 to 6 above. As a variant, at step 2, you can decide to include the SIP trunk
access into the OXO's main Trunk Group (i.e. step 2a for index #1) or include it into one 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: several Trunk Groups permits
to manage traffic sharing based on called destinations and/or access rights assigned to internal subscribers.
The index number selected at step 2 is used in further configuration at section 3.5

3.3 Internal Numbering Plan

Accessible from OMC Numbering -> Numbering Plans menu, the internal numbering plan is the place where dialing of internal
Alcatel Lucent OXO R9.00 - Sip Trunking (TC1843en-Ed01) - Svanto Wiki - Svanto Knowledge Base

phones is first analyzed by the system.

The example configuration here defines access to the internal ARS table for a number dialed that starts with digit 0. The Drop
value associated indicates that the number analysis must be continued in the ARS Prefix table without keeping the initial digit 0.
3.4 Traffic Sharing and Barring (reminder)
Though not described here, correct configuration of traffic sharing, barring and feature rights mechanisms is necessary to allow
call features and outbound traffic over the SIP trunk.
3.5 ARS context associated to the SIP Trunk
In-depth configuration of the SIP trunk is carried out via the ARS context associated to the trunk.
3.5.1 ARS Trunk Groups Lists
To enable voice calls via the ARS system, it's necessary to have ARS Trunk Groups created via the OMC menu Numbering ->
Automatic Routing Selection -> Trunk Groups Lists.

In this menu, new lines are created after clicking the mouse right button and selecting function "Add"

Carry out the selections and push-button steps 1 to 5 above. At step 4, you need to select the line index corresponding to a
System Trunk Group previously defined at section 3.2.3 (i.e. selecting 4a for the Main Trunk Group or 4b for the secondary Trunk
Group of index #2).
3.5.2 Gateway/ Registrar Proxy parameters
The OMC menu +"Numbering" "Automatic Routing Selection" "Gateway Parameters"+ permits to define parameters for SIP
Registration and Outbound Proxy (e.g. proxy, realm, domain, authentication). The screen also permits to select the operation
mode to use in front of the remote GW: resolution (static or DNS) and Fax (T38 or G711 pass-thru).
Alcatel Lucent OXO R9.00 - Sip Trunking (TC1843en-Ed01) - Svanto Wiki - Svanto Knowledge Base

In the present configuration, the SIP trunk is conveyed by the gateway referred as index 1. For this Gateway line, set up the
whole parameters as shown in the three partial pictures below (i.e. left part + middle part + right part):

voip.svanto.net
voip.svanto.net YesDynamic1 (Left part)
*******3243*000
~ "Login" : ~• GW_Login_example = "3243*000" (partially masked)

~ "Password" : ~• GW_Password = "***" (masked)

~ "Domain Name" : ~• GW_Target_Domain = "voip.svanto.net"
® "Realm" : ~• GW_Realm = "voip.svanto.net"
~ "RFC 3325" : ~• GW_RFC3325 = Yes
© "Remote SIP Port" : ~• GW_Remote_SIP_Port = "Dynamic" (see Note below)
~ "SIP Numbers .." : index number 1 shown as example (detailed at Ch. 3.5.5)
!worddav851084928386079ac722ca2b2db2d676.png|height=552,width=658!Default value of Remote SIP port is 5060. After
completing the further parameters, this value will automatically change to "Dynamic" whenever the parameter DNS is set to "DNS
SRV".G7118.8.8.8 8.8.4.4DNSSRV1237654- while "GW_Reg_Request " is equal to "No", the remaining parameters related to
registration are
disabled in OMC.
The "Registrar IP Address" is automatically set to blank if DNS parameter is set to "DNS SRV".Public DDI RegistratYes No~
"DNS" : ~• GW_DNS_Mode = DNSSRV
~ "Primary DNS..." : ~• GW_Prim_DNS = "8.8.8.8"
~ "Secondary DNS" : ~• GW_Sec_DNS = "8.8.4.4" ® "Outbound Proxy" : ~• GW_Outb_Proxy = ""
~ "Fax" : ~• GW_Fax_Mode = G711
© "Registration Req." : ~• GW_Reg_Requested = Yes (see note after)
~ "Public DDI Regist.." : ~• GW_Reg_PubDDI = No(middle part)

The IPBX registration (status and logs) can be checked in OMC +History&Anomalies History Table.+
Alcatel Lucent OXO R9.00 - Sip Trunking (TC1843en-Ed01) - Svanto Wiki - Svanto Knowledge Base

SIP Trunk Solution: SVANTO.NET (BE) Configuration Guideline R900 TC1843 ed.01
Copyright © 2013 by Alcatel-Lucent. All rights reserved page 16/28

3.5.3 ARS prefixes for remote Gateway with Static-IP

Not Applicable. Configuration of dynamic DNS mode described at section 3.5.4 is required instead.
3.5.4 ARS prefixes for remote Gateway with Dynamic-IP
The ARS Prefix table is the entry place of the ARS system to start the analysis of dialed numbers. Go to the OMC menu
Numbering -> Automatic Routing Selection -> Automatic Routing Prefix.

As illustrated in the picture below, you need first to configure the route line for standard calls (national and international): use the
Add function to create a new line and then, configure the line parameters as indicated. Note that the parameters relative to the
right part of the line are depicted a further in this doc section.

Depending on the customer context, you must add several other route lines, each dedicated to a range of special numbers (i.e.
short numbers or emergency numbers). Here below is given a more complete example with four Prefixes lines (customized values
in area 1 and 2) enabling the routing of all the required public numbers:
Alcatel Lucent OXO R9.00 - Sip Trunking (TC1843en-Ed01) - Svanto Wiki - Svanto Knowledge Base

(left part)1 3 2 4
hetSIP-GW

Line 1: standard calls starting with digit 0 (national and international calls)
Line 2: for external emergency numbers (e.g.112). This line is linked internally to the country emergency numbers specified in the
system flag table "EmergNum" (refer to Technical Bulletin TC80)
Line 3 and 4: for short-format external numbers (country dependent). The complete list of short numbers will require one or
several ARS lines depending on the country considered

~ "Registrar IP
.." : ~• GW_Reg_IP_Address = (N/A) (see Note after)

~ "Port : ~• GW_Reg_Port = "5060"

~ "Registrar Name" : ~• GW_Reg_Name = "voip.svanto.net"
® "Expire Time" : ~• GW_Reg_Expire_Time = "3600"
~ "Local Domain .." : ~• GW_Local_Domain_Name = ""
© "Registered Usern." : ~• GW_Reg_Username_example = "3243*000"
Line 3: example for France, for short numbers that begin with digit 3 (e.g. 3611, 3900, ...)
Line 4: example for France, for short numbers that begin with digit 1 (e.g. 11, 118712, ...)
In area 2, the "Calling" and "Called/PP" fields must be set as shown in the example, in order not to interfere
with other SIP parameters for numbering.
In area 3 and 4, values must also be respected :
"Called (ISVPN/..)": ~• ARS_Called_Mode = het

"Destination" : ~•
ARS_Destination = SIP-GW

128 kBit/sDefaultDynam ic
1234567
~ "IP Type": ~• ARS_IP_Type = Dynamic (see note below)
Alcatel Lucent OXO R9.00 - Sip Trunking (TC1843en-Ed01) - Svanto Wiki - Svanto Knowledge Base

~ "IP Address": ~• ARS_IP_Address = (N/A) (see note below) ~ "GW Alive Protocol": ~• ARS_GWalive_Prot = (N/A) (see note below)
® "GW Alive Timer": ~• ARS_GWalive_Timer = (N/A) (see note below)
~ "Gateway Bandwidth": to be configured according to the customer IP infra (real bandwidth
available for VoIP calls) ~• ARS_GW_Bwidth_example = 128 kBit/s
© "Codec/Framing": ~• ARS_Codec_Framing = Default
~ The Gateway Alive Status is modified when OXO performs a contact with the concerned gateway
The gateway Parameters Index field is accessible after the Gateway parameters menu is completed (step 3.5.2)

If GW parameter is set to "DNS SRV" at Ch.3.5.2, then the field ~ (IP type) is automatically set to "Dynamic" and the
fields ~, ~, ® get disabled.

3.5.5 SIP format of public phone numbers

The menu Numbering -> Automatic Routing Selection -> SIP Public Numbering is the place to define which number format is supposed to
be received or sent over the SIP trunk.

(left part)
CanonicalCanonical31 2- Configuration for outgoing calls - calling number (Erom): ~
"Format": ~• SIPnum_Out_Calling_Format = Canonical
"Prefix": ~• SIPnum_Out_Calling_Prefix = ""
Configuration for outgoing calls - called number (To): ~ ~"Format": ~• SIPnum_Out_Called_Format = Canonical
"Prefix": ~• SIPnum_Out_Called_Prefix = ""
"Short Prefix": c3• SIPnum_Out_Called_Short_Prefix = ""SIP Public Numbering (right part)
Canonical/InternationalCanonical/International4 5 6

Configuration for Incoming calls - calling number (Erom):

"Format": ~• SIPnum_Inc_Calling_Format = Canonical/International
"Prefix": ~• SIPnum_Inc_Calling_Prefix = ""
Configuration for Incoming calls - called number (To): ~
"Format": ~• SIPnum_Inc_Called_Format = Canonical/International
Alcatel Lucent OXO R9.00 - Sip Trunking (TC1843en-Ed01) - Svanto Wiki - Svanto Knowledge Base

"Prefix": ~• SIPnum_Inc_Called_Prefix = ""

Configuration for Alternative CLIP/COLP for out-calls - calling number (Erom):
"Alternative CLIP/COLP...":
c3• SIPnum_Alt_CLIP_example = ""

3.6 VOIP Misc Parameters

3.6.1 SIP Timers
Go to OMC menu Voice Over IP -> VOIP:Parameters/SIP presented below

400010006 Check/ Set values as follows:

"Timer T1": ~• VoIP_SIP_Timer_T1 = "1000"
"Timer T2": c3• VoIP_SIP_Timer_T2 = "4000" "Number of Retries": ~• VoIP_SIP_N_Retries = "6"
3.6.2 Fax (T38)

Because the FoIP protocol retained for the solution is G711 pass-thru, the parameters below are not relevant. They
are just reminded as the default settings in the system.

Go to OMC menu Voice Over IP -> VOIP:Parameters/Fax presented below

01 Check/ Set values as follows:

"UDP Redundancy": ~• VoIP_T38_UDP_Redundancy = "1"
"Framing": ~• VoIP_T38_Fax_Framing = "0"

3.7 Noteworthy Addresses

Some PBX specific tuning may not be accessible directly via dedicated OMC screens. In such case, the tuning is done via internal
control parameters (flags) also called "Noteworthy addresses" or "Labels". Access to the system Labels is made with OMC menu
System Miscellaneous -> Memory Read/Write.

Noteworthy addresses have a customized factory default value which is dependent of the SW installation target
selected for OXO (country dependent).

The different flags detailed hereafter are key for the configuration of the SIP trunk and therefore they need
to be checked/ edited with special care. When a flag needs to be modified, click on the 'modify' then on the
'write' buttons to send the new value to the IPBX. Also, if specified in the document, a further system
warm reset may be requested for some of the flags to have the new value taken into account.

3.7.1 Debug Labels

Go to System Miscellaneous ->Memory Read/Write > Debug Labels > and check/ edit values carefully as detailed below.
MultAnsRei controls emission of Re-INVITE messages during SDP negotiation Flag_MultAnsRei = "01"
VOIPnwaddr is a 64-byte-size table of flags controlling most of the VoIP/SIP config parameters not found within the regular OMC
screens. Therefore, special attention must be paid when reading or editing the contents of this table:
Alcatel Lucent OXO R9.00 - Sip Trunking (TC1843en-Ed01) - Svanto Wiki - Svanto Knowledge Base

000000 00 00 00 00 00 00 00 00000008 00
00 00 00 00 00 00 00
000010 00 00 00 00 00 00 00 00
000018 00 00 00 00 00 00 00 00
000020 00 00 00 00 00 00 00 00
000028 00 00 00 00 00 00 00 00
000030 00 00 00 00 00 00 00 00
000038 00 00 00 00 00 00 00 00
000040 00 00 00 00 00 00 00 00
000048 00 00 00 00 00 00 00 00
000050 00 00 00 00 00 00 00 00
000058 00 00 00 00 00 00 00 00
000060 00 00 00 0000 00 00 00 00 00 00 00

Line 1: ~• Flag_VOIPnwaddr_Line1 = "00 00 00 00 00 00 00 00"

Alcatel Lucent OXO R9.00 - Sip Trunking (TC1843en-Ed01) - Svanto Wiki - Svanto Knowledge Base

Line 2: ~• Flag_VOIPnwaddr_Line2 = "00 00 00 00 00 00 00 00"

Line 3: ~• Flag_VOIPnwaddr_Line3 = "00 00 00 00 00 00 00 00"

Line 4: ~• Flag_VOIPnwaddr_Line4 = "00 00 00 00 00 00 00 00"

Line 5: ~• Flag_VOIPnwaddr_Line5 = "00 00 00 00 00 00 00 00"

Line 6: ~• Flag_VOIPnwaddr_Line6 = "00 00 00 00 00 00 00 00"

Line 7: ~• Flag_VOIPnwaddr_Line7 = "00 00 00 00 00 00 00 00"

Line 8: ~• Flag_VOIPnwaddr_Line8 = "00 00 00 00 00 00 00 00"

A warm reset must be performed after changing any of the values in that table !

3.7.2 Other Labels

Go to System Misc ->Memory Read/Write > Other Labels section and configure labels as shown below.

DtmfDynPL: Sets the payload value for DTMF

c3• Flag_DtmfDynPL = "6A"
PrefCodec indicates if a particular codec has preference c3• Flag_PrefCodec = "00 00"
PrefFramin indicates the preferred length of RTP packets c3• Flag_PrefFramin = "00"
AlCodLst permits to select one specific default codec list c3• Flag_AlCodLst = "00"
SIPInDspNm controls display of received "CNIP" name when receiving a call c3• Flag_SIPInDspNm = "01"
SIPOgDspNm controls the "CNIP" name sent over the network for outgoing calls c3• Flag_SIPOgDspNm = "01"
FaxPasCd configures codec pass-through preference for fax G711 (between G711a and G711u) c3• Flag_FaxPasCd = "01 FF"
VipPuNuA controls the global public/ private numbering model. Value must be set to 00. c3• Flag_VipPuNuA = "00"
ExtNuFoVoi controls usage of the Installation Numbers table. Value must be set to 22. c3• Flag_ExtNuFoVoi = "22"
SimulIpAlt controls usage of the local dial tone. c3• Flag_SimulIpAlt = "00"
INVwSDPtrk controls generating INVITEs with/ without SDP for call scenaree with delayed re-routing. c3• Flag_INVwSDPtrk =
"00"

3.8 Miscellaneous Configuration

3.8.1 Calling Identity when External Call Forward
This configuration permits to define the calling CLIP that is sent by OXO to the "forwarded-to" destination (case of an incoming
external call coming to an internal user who has an external diversion engaged). The control can be made globally for the PBX or
extension by extension.
!worddav168723885bcace7e82d8b3f4c4548310.png|height=414,width=597!From the menu System Misc -> Feature Design, tab
Part 1 & tab Part 2; check the parameters: "CLI for external diversion": ~• Misc_CLI_Ext_Diversion = True
"CLI is diverted party if ext..": ~• Misc_CLI_is_Diverted_Party = False 0.I for external diversion 0.I is diverted party if
external caller For extensions taken from the menu Subscribers/Basestation List, check with the Details button the similar
CLI parameter:
Alcatel Lucent OXO R9.00 - Sip Trunking (TC1843en-Ed01) - Svanto Wiki - Svanto Knowledge Base

"CLI is diverted party": ~•

Misc_CLI_is_Diverted_Party = False

4 SIP trunk Configuration Abstract

This chapter gathers the rough value of OXO parameters (three following tables).
Table 1
CONFIG OXO R900
VALUE
REMARK
LAN_IP_Infra
LAN_Main_CPU_IPadd_example
"10.70.0.1"
Value given as example
LAN_Def_Router_IPadd_example
"10.0.0.1"
Value given as example
LAN_Subnet_Mask_example
"255.0.0.0"
Value given as example
System_Numbering_Plan
NP_Instal_Number_example
""
NP_International_Prefix
"00"
NP_International_Code
"32"
NP_Recall_Prefix
"0"
NP_Intercity_Prefix
"0"
NP_Intercity_Code_example
""
NP_System_Alt_CLIP_example
""
NP_DDI_Range_example
"43**000 43**000"
Value given as example
VoIP_General
VoIP_Protocol
SIP
VoIP_Trunk_Channels_example
"2"
Value given as example
VoIP_RTP_Direct
True
VoIP_Trunk_Codec_Passthru
True
VoIP_Phone_Codec_Passthru
Alcatel Lucent OXO R9.00 - Sip Trunking (TC1843en-Ed01) - Svanto Wiki - Svanto Knowledge Base

False
VoIP_G711_MOH
True
VoIP_IP_QoS_example
00000000 DIFFSERV_PHB_BE
Value given as example
VoIP_DSP_Echo_Cancel
True
VoIP_DSP_VAD
False
VoIP_T38_UDP_Redundancy
VoIP_T38_Fax_Framing
"0"
VoIP_SIP_Timer_T1
"1000"
VoIP_SIP_Timer_T2
"4000"
VoIP_SIP_N_Retries
"6"
VoIP_Def_CodecFraming
(N/A)
VoIP_Def_CodecList
(N/A)
Trunk_access
Access_is_Public
True
Access_Alt_CLIP_example
""
Access_Channels_example
Value given as example
System_Misc
Misc_CLI_Ext_Diversion
True
Misc_CLI_is_Diverted_Party
False

Table 2

CONFIG OXO R900 VALUE REMARK

ARS_Prefixes

ARS_Called_Mode het

ARS_Destination SIP-GW

ARS_IP_Type Dynamic

ARS_IP_Address (N/A)

ARS_GWalive_Timer (N/A)

ARS_GWalive_Prot (N/A)

ARS_GW_Bwidth_example 128 kBit/s Value given as example

ARS_Codec_Framing Default

ARS_GW_Parms

GW_Login_example "3243***000" Example partially masked

Alcatel Lucent OXO R9.00 - Sip Trunking (TC1843en-Ed01) - Svanto Wiki - Svanto Knowledge Base

GW_Password "*****"

GW_Target_Domain "voip.svanto.net"

GW_Realm "voip.svanto.net"

GW_RFC3325 Yes

GW_DNS_Mode DNSSRV

GW_Remote_SIP_Port "Dynamic"

GW_Fax_Mode G711

GW_Local_Domain_Name ""

GW_Prim_DNS "8.8.8.8"

GW_Sec_DNS "8.8.4.4"

GW_Outb_Proxy ""

GW_Reg_Requested Yes

GW_Reg_PubDDI No

GW_Reg_Username_example "3243***000" Example partially masked

GW_Reg_IP_Address (N/A)

GW_Reg_Port "5060"

GW_Reg_Name "voip.svanto.net"

GW_Reg_Expire_Time "3600"

ARS_SIP_Public_Numbering_Plan

SIPnum_Out_Calling_Format Canonical

SIPnum_Out_Calling_Prefix ""

SIPnum_Out_Called_Format Canonical

SIPnum_Out_Called_Prefix ""

SIPnum_Out_Called_Short_Prefix ""

SIPnum_Inc_Calling_Format Canonical/International

SIPnum_Inc_Calling_Prefix ""

SIPnum_Inc_Called_Format Canonical/International

SIPnum_Inc_Called_Prefix ""

SIPnum_Alt_CLIP_example ""

Table 3
Alcatel Lucent OXO R9.00 - Sip Trunking (TC1843en-Ed01) - Svanto Wiki - Svanto Knowledge Base

CONFIG OXO R900 VALUE REMARK

System_Flags

Flag_VOIPnwaddr_Line1 "00 00 00 00 00 00 00 00"

Flag_VOIPnwaddr_Line2 "00 00 00 00 00 00 00 00"

Flag_VOIPnwaddr_Line3 "00 00 00 00 00 00 00 00"

Flag_VOIPnwaddr_Line4 "00 00 00 00 00 00 00 00"

Flag_VOIPnwaddr_Line5 "00 00 00 00 00 00 00 00"

Flag_VOIPnwaddr_Line6 "00 00 00 00 00 00 00 00"

Flag_VOIPnwaddr_Line7 "00 00 00 00 00 00 00 00"

Flag_VOIPnwaddr_Line8 "00 00 00 00 00 00 00 00"

Flag_VOIPnwaddr_Line9 "00 00 00 00 00 00 00 00"

Flag_VOIPnwaddr_Line10 "00 00 00 00 00 00 00 00"

Flag_VOIPnwaddr_Line11 "00 00 00 00 00 00 00 00"

Flag_VOIPnwaddr_Line12 "00 00 00 00 00 00 00 00"

Flag_VOIPnwaddr_Line13 "00 00 00 00"

Flag_MultAnsRei "01"

Flag_DtmfDynPL "6A"

Flag_PrefCodec "00 00"

Flag_PrefFramin "00"

Flag_AlCodLst "00"

Flag_SIPInDspNm "01"

Flag_SIPOgDspNm "01"

Flag_FaxPasCd "01 FF"

Flag_VipPuNuA "00"

Flag_ExtNuFoVoi "22"

Flag_SimulIpAlt "00"

Flag_INVwSDPtrk "00"