Alcatel-Lucent OmniPCX Office SIP Trunk Solution: OPENIP (FR) Configuration Guideline R920

Overview

This document details how to set up an OXO R920 IPBX for enabling a public SIP trunk of the Operator OPENIP in FRANCE.

Revision History

Edition 01: October 24, 2014 - First R920 edition released for GA publication.

Legal Notice

Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein. Copyright © 2014 Alcatel-Lucent. All rights reserved.

1 General

This guide details the "from-scratch" configuration of an R920 customer system featuring a SIP trunk of the Operator OPENIP. It ensures a convenient setup and correct operation of this SIP trunk.

1.1 References

Alcatel-Lucent documentation available from the Business Partner Web Site:

• [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

The document is intended for engineers familiar with OMC and the basic setup of the IPBX. It is based on the OMC tool used in English language.

Configuration parameters/values are typed in purple color with the heading sign. For example:

• NP_International_Prefix = "00"
• VoIP_RTP_Direct = False
• ARS_GWalive_Timer = (N/A)

Parameters ending with "_example" require customization. For example:

• LAN_Subnet_Mask_example = "255.255.255.0"
• Access_Channels_example = "4"

Example values may be masked or partially masked with asterisks for privacy reasons.

1.3 Scope of Alcatel-Lucent's support

Support is delimited by the approved context and system configuration. It covers protocol and functional aspects of the SIP trunk, but not audio quality related to the Operator or client's IP infrastructure. Deployment is supported under specific service models: LA (Limited Availability) or GA (General Availability).

The up-to-date support model must be checked on Alcatel-Lucent's Web portal.

1.4 Software/ Hardware components on customer's infrastructure

1.5 Feature & Set Compatibility List

Tables 1.5.1 & 1.5.2 detail supported models and inter-op features. Items are marked as "OK" (full support), "WR" (With Restriction), "NOK" (Not OK or Not Applicable), or "NT" (Not Tested).

Note for "NT" items: For items marked "NT", contact sip-for-smb@alcatel-lucent.com for certification details if you wish to have them supported.

1.5.1 Supported Sets

1.5.2 Supported Features

1.5.3 Restrictions

Internal Call Forward, External Call Forward and Dynamic Call Routing may have issues with COLP.

2 System General Info and Basic Setup

2.1 Pre-required information

The following tables show customized data required for OXO configuration. The second table gathers SIP data that must be supplied/confirmed by the Operator.

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

IP PARAMETERS

SIP TRUNK PARAMETERS

2.2 System Connection procedure

To configure the IPBX, use the OMC software at the Expert level session.

2.3 Network configuration

Configure the IP settings using the OMC menu Hardware and Limits > LAN IP Configuration.

The "Boards" Tab shows the IP address for the main CPU and the default gateway. The main CPU IP address must be edited there.

• LAN_Main_CPU_IPadd_example = "192.168.137.246"

The "LAN Configuration" Tab allows editing the default gateway IP address and the subnet mask.

• LAN_Def_Router_IPadd_example = "192.168.137.254"
• LAN_Subnet_Mask_example = "255.255.255.0"

Note: A system reboot ("Warm reset") is required after modifying LAN-IP parameters.

2.4 Numbering configuration

2.4.1 Installation numbers

Configure public numbering for the SIP trunk via OMC Numbering > Installation Numbers.

Configuration for "Installation Numbers":

• Install. Number: NP_Instal_Number_example = "9****3430"
• International Prefix: NP_International_Prefix = "00"
• International Code: NP_International_Code = "33"
• 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 = ""

2.4.2 DDI numbers

Configure DDI numbers in OMC Numbering > Numbering Plans – Public Numbering Plan Tab.

Configuration for "Public Numbering Plan":

• DDI range: NP_DDI_Range_example = "3431 3435"

This example allocates the DDI range "3431 3435" to extensions "110 - 114".

2.4.3 Internal Numbering Plan

Configure the internal numbering plan in OMC Numbering > Numbering Plans.

This example defines access to the internal ARS table for user dialing starting with digit 0. The "Drop" attribute indicates that the number dialed must be analyzed in the ARS Prefix table after dropping the initial digit 0.

2.5 Traffic Sharing and Barring (reminder)

Correct configuration of traffic sharing, barring, and feature rights is necessary for call features and outbound traffic over the SIP trunk.

3 Detailed SIP Trunk Configuration

3.1 SIP ability check

A specific SW license is mandatory for IP trunks. The OMC menu Hardware and Limits > Software Key Features provides an overview of allowed features. In the Multi-site Tab, check the number of "IP Trunks" activated.

3.2 SIP Trunk creation

The VoIP trunk uses SIP signaling and DSP resources. To create the SIP trunk, allocate DSP resources.

3.2.1 Management of VoIP channels

Configure parameters in OMC Voice Over IP > VOIP:Parameters - General Tab.

• VoIP protocol: VoIP_Protocol = SIP
• Number of channels for VoIP trunks: VoIP_Trunk_Channels_example = "4"
• RTP routing mode and codec management:
• VoIP_RTP_Direct = False
• VoIP_Trunk_Codec_Passthru = False
• VoIP_Phone_Codec_Passthru = False
• IP Quality of Service: VoIP_IP_QoS_example = 10111000 DIFFSERV_PHB_EF
• G711 codec for Music On Hold: VoIP_G711_MOH = False

Configure Echo Cancellation and VAD parameters in OMC Voice Over IP > VOIP:Parameters - DSP Tab.

• Echo Cancellation: VoIP_DSP_Echo_Cancel = True
• Voice Active Detection: VoIP_DSP_VAD = False

Configure the "Default Codecs List" and "Default Framing" in OMC Voice Over IP > VOIP:Parameters - Codecs.

• Default Codecs List: VoIP_Def_CodecList = G711.μ
• Default Framing: VoIP_Def_CodecFraming = "20"

3.2.2 "Physical" Access associated to the SIP Trunk

Select the VoIP access in OMC External Lines > List of access.

Configure access parameters:

• "Public trunk" option: Access_is_Public = True
• Number of channels: Access_Channels_example = "4"
• "Alternative CLIP/COLP Number": Access_Alt_CLIP_example = ""

3.2.3 Hosting System Trunk Group

Include the SIP trunk access into a Trunk Group using OMC External Lines > List of Trunk Groups.

The SIP trunk can be placed in one or several Trunk Groups for traffic sharing and access rights management.

3.3 ARS context associated to the SIP Trunk

Configure the ARS context for the trunk, including the IP address of the peering SIP Gateway. Configuration can be static IP or dynamic IP address resolution.

This SIP Operator provides dynamic IP address resolution, so DNS-SRV configuration is applied.

3.3.1 ARS Trunk Groups Lists

Create ARS Trunk Groups via OMC Numbering > Automatic Routing Selection > Trunk Groups Lists.

Select the line index corresponding to a System Trunk Group defined in section 3.2.3.

3.3.2 ARS Gateway Parameters

Configure peer SIP gateway parameters in OMC Numbering > Automatic Routing Selection > Gateway Parameters. This includes IP access, account registration, and authentication.

Parameters like "GW_Target_Domain", "GW_Outb_Proxy", "GW_Reg_Name", "GW_Prim_DNS", "GW_Sec_DNS" are controlled by the Operator and may vary.

Configure the gateway parameters for index 1:

• Login: Configure in "ARS SIP Accounts".
• Password: Configure in "ARS SIP Accounts".
• Domain Name: GW_Target_Domain = "sip9.voip-centrex.net"
• Realm: GW_Realm = ""
• RFC 3325: GW_RFC3325 = Yes
• Remote SIP Port: GW_Remote_SIP_Port = "5060"
• DNS Mode: GW_DNS_Mode = DNSSRV
• Primary DNS: GW_Prim_DNS = "83.167.37.51"
• Secondary DNS: GW_Sec_DNS = "8.8.8.8"
• Outbound Proxy: GW_Outb_Proxy = "sip9.voip-centrex.net"
• Fax Mode: GW_Fax_Mode = G711
• Registration Req.: GW_Reg_Requested = Yes
• Public DDI Registr.: GW_Reg_PubDDI = No

Note: If "GW_Reg_Request" is "No", related parameters are disabled. If DNS is set to "DNS SRV", "Registrar IP Address" is blank.

3.3.3 ARS SIP Accounts

Configure authentication parameters in OMC Numbering > Automatic Routing Selection > SIP Accounts.

• Login: GW_Login_example = "thJO******rUk"
• Password: GW_Password = "*****"
• Registered User: GW_Reg_Username_example = "thJO******rUk"
• GW Parms Index: "1"

Check registration status and logs in OMC History&Anomalies > History Table.

3.3.4 ARS Prefixes

Configure ARS Prefixes in OMC Numbering > Automatic Routing Selection > Automatic Routing Prefixes.

Associate the SIP Trunk to an ARS Prefix by configuring the prefix with the peering SIP Gateway's IP address in static IP address mode.

Add route-lines for standard calls (national/international numbers) and configure line parameters.

Example configuration for four Prefixes lines:

• Line 1: Standard calls starting with digit 0.
• Line 2: External emergency numbers (e.g., 112).
• Line 3 & 4: External short numbers.

In area 2, "Calling" and "Called/PP" fields must be set as shown.

• "Called (ISVPN/..)": ARS_Called_Mode = het
• "Destination": ARS_Destination = SIP Gateway

Configure right part of "Automatic Routing: Prefixes":

• IP Type: ARS_IP_Type = Dynamic
• IP Address: ARS_IP_Address = (N/A)
• GW Alive Protocol: ARS_GWalive_Prot = (N/A)
• GW Alive Timer: ARS_GWalive_Timer = (N/A)
• Gateway Bandwidth: ARS_GW_Bwidth_example = 512 kBit/s
• Codec/Framing: ARS_Codec_Framing = Default

Note: If "DNS SRV" is selected for "DNS", "IP Type" is automatically set to "Dynamic" and fields for IP Address, Protocol, and Timer are disabled.

3.3.5 ARS SIP Public Numbering

Define phone number formats in OMC Numbering > Automatic Routing Selection > SIP Public Numbering.

Configuration for outgoing calls - calling number (From):

• Format: SIPnum_Out_Calling_Format = National without intercity prefix
• Prefix: SIPnum_Out_Calling_Prefix = ""

Configuration for outgoing calls - called number (To):

• Format: SIPnum_Out_Called_Format = National/International
• Prefix: SIPnum_Out_Called_Prefix = ""
• Short Prefix: SIPnum_Out_Called_Short_Prefix = ""

Configuration for Incoming calls - calling number (From):

• Format: SIPnum_Inc_Calling_Format = National
• Prefix: SIPnum_Inc_Calling_Prefix = ""

Configuration for Incoming calls - called number (To):

• Format: SIPnum_Inc_Called_Format = National
• Prefix: SIPnum_Inc_Called_Prefix = ""

Configuration for Alternative CLIP/COLP for out-calls - calling number (From):

• Alternative CLIP/COLP: SIPnum_Alt_CLIP_example = ""

3.4 VOIP Misc Parameters

3.4.1 SIP Timers

Configure SIP timers in OMC Voice Over IP > VOIP:Parameters/SIP.

• Timer T1: VoIP_SIP_Timer_T1 = "1000"
• Timer T2: VoIP_SIP_Timer_T2 = "4000"
• Number of Retries: VoIP_SIP_N_Retries = "6"

3.4.2 Fax (T38)

G711 pass-thru is validated in ARS. Default T38 settings:

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

3.4.3 UDP Source Port for SIP Signaling

Configure the UDP Source Port in OMC Voice Over IP > VOIP:Parameters/Gateway.

• "SIP Trunk Signal Source Port": VoIP_SIPSourcePort = "5060"

3.5 Noteworthy Addresses

Some configurations are accessed via internal flags or "Labels" in OMC System Miscellaneous > Memory Read/Write.

Noteworthy addresses have factory default values dependent on the OXO software installation target (country).

System flags are key for SIP trunk configuration and require careful checking/editing. After editing, click 'Modify' then 'Write' to send the new value to the IPBX. A warm reset may be needed.

3.5.1 Debug Labels

Configure debug labels in OMC System Miscellaneous > Memory Read/Write > Debug Labels.

• Flag_MultAnsRei = "01" (controls emission of Re-INVITE messages during SDP negotiation)
• Flag_SuprAlerTo = "00" (controls Ring Back Tone)

VOIPnwaddr is a 64-byte table of flags controlling most VoIP/SIP parameters outside regular OMC screens. Pay special attention to it.

Configuration for VOIPnwaddr lines:

• Line 1 (000): Flag_VOIPnwaddr_Line1 = "00 00 00 00 00 00 00 00"
• Line 2 (008): Flag_VOIPnwaddr_Line2 = "00 00 00 00 00 00 00 00"
• Line 3 (010): Flag_VOIPnwaddr_Line3 = "00 00 01 00 00 00 00 00"
• Line 4 (018): Flag_VOIPnwaddr_Line4 = "00 00 00 00 00 00 00 00"
• Line 5 (020): Flag_VOIPnwaddr_Line5 = "00 00 00 00 00 00 00 00"
• Line 6 (028): Flag_VOIPnwaddr_Line6 = "00 00 00 00 00 00 00 00"
• Line 7 (030): Flag_VOIPnwaddr_Line7 = "00 00 00 00 00 00 00 00"
• Line 8 (038): Flag_VOIPnwaddr_Line8 = "00 00 00 00 00 00 00 00"
• Line 9 (040): Flag_VOIPnwaddr_Line9 = "00 00 00 00 00 00 00 00"
• Line 10 (048): Flag_VOIPnwaddr_Line10 = "00 00 00 00 00 00 00 00"

Note: A warm reset is needed to validate modifications to this table.

3.5.2 Other Labels

Configure labels in OMC System Misc > Memory Read/Write > Other Labels.

• Flag_VipPuNuA = "00" (controls global public/ private numbering model)
• Flag_ExtNuFoVoi = "22" (controls usage of the Installation Numbers table)
• Flag_DtmfDynPL = "6A" (sets the payload value for DTMF)
• Flag_SimulIpAlt = "00" (controls usage of the local dial tone)
• Flag_PrefCodec = "00 00"
• Flag_PrefFramin = "00"
• Flag_FaxPasCd = "01 FF" (configures codec pass-through preference for fax G711)
• Flag_AlCodLst = (N/A) (permits to select one specific default codec list)
• Flag_SIPInDspNm = "00" (controls display of received “CNIP” name)
• Flag_SIPOgDspNm = "01" (controls the “CNIP” name sent over the network)
• Flag_INVwSDPtrk = "00" (controls generating INVITEs with/ without SDP)
• Flag_SIPdtmfInB = "00" (sets alternative DTMF mode for inbound calls)
• Flag_G7222DynPL = "75" (sets the payload value for G722-2 codec)
• Flag_SuprAlerTo = "00"

3.6 Miscellaneous Configuration

3.6.1 Calling Identity when External Call Forward

Configure calling CLIP sent by OXO for forwarded-to destinations.

Check parameters in OMC System Misc > Feature Design, tab Part 1 & tab Part 2:

• "CLI for external diversion": Misc_CLI_Ext_Diversion = True
• "CLI is diverted party if ext..": Misc_CLI_is_Diverted_Party = False

For extensions, check the CLI parameter in Subscribers/Basestation List > Details.

4 SIP trunk Configuration Abstract

This chapter gathers the rough values of OXO parameters.

Table 1

Table 2

Table 3

Follow us on Facebook and Twitter

Stay tuned on our Facebook and Twitter channels where we inform you about:

• New software releases
• New technical communications
• AAPP InterWorking Reports
• Newsletter
• Etc.

twitter.com/ALUE_Care

facebook.com/ALECustomerCare

Submitting a Service Request

Please connect to our eService Request application.

Before submitting a Service Request, make sure that:

• In case a Third-Party application is involved, that application has been certified via the AAPP.
• You have read through the Release Notes which lists new features available, system requirements, restrictions etc. available in the Technical Documentation Library.
• You have read through the Troubleshooting Guides and Technical Bulletins relative to this subject available in the Technical Documentation Library.
• You have read through the self-service information on commonly asked support questions, known issues and workarounds available in the Technical Knowledge Center.