Technical Bulletin OmniPCX Enterprise

TC2005 ed.17 Release 10.0 and above

SIP providers supported on OmniPCX®

Enterprise and/or Opentouch®

This document list the SIP Providers supported by Alcatel-Lucent Enterprise for the following products: OmniPCX®
Enterprise and/or OpenTouch®.

Revision History
Edition 1: November 7, 2014
Edition 2: November 19, 2014
Edition 3b: August 13, 2015
Edition 4: October 8, 2015
Edition 5: September 16, 2016
Edition 6: January 4, 2017
Edition 7: March 24, 2017
Edition 8: May 11, 2017
Edition 9: July 6, 2017
Edition 10: August 9, 2017
Edition 11: January 10, 2018
Edition 12: April 24, 2018
Edition 13: November 26, 2018
Edition 14: February 2, 2019
Edition 15: April 19, 2019
Edition 16: June 7, 2019
Edition 17: October 3, 2019
creation of the document
update of the document
update of the document
update of the document
update of the document
update of the document
update of the document
update of the document
update of the document
update of the document
update of the document
update of the document
update of the document
update of the document
update of the document
update of the document
update of the document

Legal notice:
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. To view other trademarks used by
affiliated companies of ALE Holding, visit: www.al-enterprise.com/en/legal/trademarks-copyright. All other trademarks are the
property of their respective owners. The information presented is subject to change without notice. Neither ALE Holding nor any
of its affiliates assumes any responsibility for inaccuracies contained herein. © 2019 ALE International. All rights reserved.
www.al-enterprise.com
General Disclaimer
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER ALE INTERNATIONAL NOR ANY OF ITS AFFILIATES,
PARENT OR SISTER COMPANIES, DIRECTORS, EMPLOYEES OR OTHER REPRESENTATIVES WILL BE LIABLE FOR DIRECT,
INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE OR CONSEQUENTIAL DAMAGES OF ANY KIND INCLUDING BUT NOT LIMITED
TO LOSS OF USE, DATA, LOSS OF PROFITS, INCOME, BUSINESS, ANTICIPATED SAVINGS, REPUTATION AS WELL AS
FINANCING COSTS OR INCREASE IN OPERATING COSTS OR OTHER ECONOMIC LOSS.

OmniPCX Enterprise - Release 10.0 and above

SIP providers supported on OmniPCX® Enterprise and/or Opentouch® TC2005 ed.17
Copyright © ALE International 2019 page 2/13
Table of contents
1 Introduction ............................................................................................................................................ 4
2 List of SIP Providers tested ...................................................................................................................... 5
3 Interoperability testing process ................................................................................................................ 9
3.1 Process description (4 steps) ............................................................................................................. 9
3.2 Guideline for effective technical support process ............................................................................ 11

OmniPCX Enterprise - Release 10.0 and above

SIP providers supported on OmniPCX® Enterprise and/or Opentouch® TC2005 ed.17
Copyright © ALE International 2019 page 3/13
 1 Introduction
This document list all SIP Providers supported by ALE International for the following product: OmniPCX
Enterprise and/or OpenTouch.

Upward compatibility on a SIP interoperability test is granted for OXE from release 10.1.1 but only on
the functional perimeter initially tested.

Warning It is important to note that support is only granted on OXE releases officially supported. Please refer to
last edition of the document “Release Policy Information – MLV” Ref ENT_MLE_034198 available on the
ALE Business Portal here.

To initiate a new interoperability test, the “Interop pack of documents” can be recovered on ALE Business
Portal here, it contains:
0.Interoperability_testing_with_a_SIP_provider_v8.docx (process description)
1.PublicSIPtrunking_TechnicalQuestionnaire_OT_OXE_ed10_2019_09.docx (data collection)
2.TCxxxxen-Ed01_SIP_Trunk_SIPProvider_ConfigurationGuideline_R12.3-ed01.docx (test plan & guideline to
execute an interop test)
3.Interworking_Test_Technical_support_v6.doc (how to access technical support)
ProductDescription_PublicSIPtrunking_OXE R12.3_2019_09.docx (SIP trunking product description & list of
supported RFCs)

OmniPCX Enterprise - Release 10.0 and above

SIP providers supported on OmniPCX® Enterprise and/or Opentouch® TC2005 ed.17
Copyright © ALE International 2019 page 4/13
 2 List of SIP Providers tested
X = release(s) tested. Refer to chapter 1 for releases supported.
OmniPCX Enterprise OT OT-SBC

Last version

Last version

SBC wizard
R10.1.x

R11.0.x

tested2
TCs published

profile
tested
R10.0

R11.1

R11.2

R12.0

R12.1

R12.2

R12.3
Country SIP provider name on Business
Portal

Australia Telstra X X R2.3

Australia Telstra/One Access X
Austria Citycom X R2.1 X TC2156en
Austria TELE2 X TC2188en
Austria A1 SIP trunk X X R2.2 R2.3 X TC2388en
Austria UPC X R2.3 X TC2574en
Austria Neotel X R2.3 TC2594en
Austria IP Austria X R2.3 TC2620en
Belgium Proximus X X X X X TC2290en
Belgium Mobistar X
Belgium Telenet X X X R2.0 R2.0 X TC2157en
Belgium WIN X R2.0
Cyprus CYTA X
Denmark Telia Entry V1/V2 X X
Denmark Telenor X
Finland TDC X X R2.0 R2.0
Finland Telia Puheväylä X TC2351en
Finland Line Carrier X TC2268en
Finland Elisa X TC2276en
Finland Fujitsu X TC2289en
Finland DNA X R2.1 X TC2430en
France Axialys X R1.0
France OBS BTIP-SIP X X X X X X X X X R2.5
France SFR Business Team X X X X R2.0
France Bouygues Telecom X
France IP Directions X R1.0 R1.0
France Jaguar-Network X

OmniPCX Enterprise - Release 10.0 and above

SIP providers supported on OmniPCX® Enterprise and/or Opentouch® TC2005 ed.17
Copyright © ALE International 2019 page 5/13
 OmniPCX Enterprise OT OT-SBC

Last version

Last version

SBC wizard
R10.1.x

R11.0.x

tested2
TCs published

profile
tested
R10.0

R11.1

R11.2

R12.0

R12.1

R12.2

R12.3
Country SIP provider name on Business
Portal

France Open-IP X R2.0 R2.0

France Alphalink (OpenVNO) X TC2362en
Germany M.net X R2.0 X TC2155en
Germany QSC X R2.1 X TC2250en
Germany Toplink X R2.1 R2.1 X TC2274en
Germany Vodafone X R2.1 X TC2236en
Germany HFO X TC2267en
Corporate SIP
Germany International (CSIP) – T- X TC2288en
Systems

Germany 1&1 Versatel X R2.3 X TC2439en

Germany Ecotel X TC2570en

Germany EWE / Swb / Osnatel X TC2584en
Germany Voiceworks X R2.3 TC2598en
DeutschlandLAN
Germany X R2.3 TC2629en
(Deutsche Telekom)
Germany Telefonica X R2.3 TC2641en
Greece Forthnet X R1.3
Ireland Imagine Telecom X
Italy British Telecom Italy X X
Italy Telecom Italia X X X R2.3
Italy Stato Città del Vaticano X TC2403en
Italy Poste Italiane X TC2558en
Luxembourg Visual Online X X
Maldives Dhiraagu X
Mexico Enlace X TC2375en
Netherlands KPN X X X TC2575en
Netherlands Vodafone X X
Netherlands UPC X
Netherlands T-Mobile X X TC2361en

OmniPCX Enterprise - Release 10.0 and above

SIP providers supported on OmniPCX® Enterprise and/or Opentouch® TC2005 ed.17
Copyright © ALE International 2019 page 6/13
 OmniPCX Enterprise OT OT-SBC

Last version

Last version

SBC wizard
R10.1.x

R11.0.x

tested2

profile
TCs published

tested
R10.0

R11.1

R11.2

R12.0

R12.1

R12.2

R12.3
Country SIP provider name on Business
Portal

Norway Phonero X X TC2158en

Norway Phonect X
Norway Telia Entry V1/V2 X X
Norway Telenor X X
Pan-
COLT X R1.3 R1.0 X
European
Pan-
Interoute X TC2325en
European
Portugal Vodafone Portugal X
Qatar Ooredoo X TC2528en
South Africa Mweb X
South Africa Vox X R2.1 X TC2319en
South Africa i-Connect X TC2513en
South Africa SBD Internet Solutions X TC2595en
Spain Telefonica X X R1.2
Spain Euskaltel X X R2.1 X TC2378en
Sweden Telia Entry V1/V2 X X
Sweden Telenor X R2.3 X
Sweden Tele2 X TC2559en
Swisscom Enterprise
Switzerland X X X R2.1 TC2350en
SIP
Swisscom Enterprise
Switzerland X X R2.3 TC2376en
SIP
Swisscom
Switzerland Smart Business X TC2352en
Connect
Switzerland Sunrise X X X TC2254en
Switzerland UPC (former Cablecom) X R2.1 TC2353en
Switzerland UPC (former Cablecom) X R2.1 TC2377en
Switzerland Sip-Call X TC2455en

OmniPCX Enterprise - Release 10.0 and above

SIP providers supported on OmniPCX® Enterprise and/or Opentouch® TC2005 ed.17
Copyright © ALE International 2019 page 7/13
 OmniPCX Enterprise OT OT-SBC

Last version

Last version

SBC wizard
R10.1.x

R11.0.x

tested2

profile
TCs published

tested
R10.0

R11.1

R11.2

R12.0

R12.1

R12.2

R12.3
Country SIP provider name on Business
Portal

UK Gamma Telecom X X R1.3 R2.0 X

UK Pure IP X
UK Virgin Media X R2.0 R2.0 X
UK TalkTalk Business X R2.1 TC2307en
UK KCOM X R2.1 R2.1 TC2316en
UK Via-Vox X R2.3 X TC2518en
UK Exponential-e X R2.3 TC2593en
US Verizon X X R2.1 TC2631en
US Sprint X R1.3 R1.0
US Broadvox X R1.3 R1.0
Charter
US X
Communications
US LEVEL-3 X
US COEO X TC2221en
US Powernet X R2.1
US Comcast X R2.3 TC2495en
US Spectrum Enterprise X R2.3 X TC2583en
US SuddenLink X R2.3 TC2619en

OmniPCX Enterprise - Release 10.0 and above

SIP providers supported on OmniPCX® Enterprise and/or Opentouch® TC2005 ed.17
Copyright © ALE International 2019 page 8/13
3 Interoperability testing process

3.1 Process description (4 steps)

1. Technical questionnaire:

 Fill-in: “1.PublicSIPtrunking_TechnicalQuestionnaire_OT_OXE_ed10_2019_09.docx”

 Create an eSR with the following parameters & attach this file
- Summary have to start with “[SBD] name of the SIP provider”
- SR Category = “Technical Support Communications”
- SR type = “Product Support”
- How found = “Acceptance Test”

 And email it to SIP-trunking-MLE@al-enterprise.com

→ After an in-depth analysis – that may sometimes require technical discussions with the
SIP provider technical staff - Alcatel-Lucent Enterprise will provide a GO (eventually with
a list of agreed restrictions) or a NO GO decision.

Furthermore, according to the provided answers in the Technical Questionnaire, several OXE
parameters can be configured. The Tech Support will send you the below document (partially
completed):
“2.TCxxxxen-Ed01_SIP_Trunk_SIPProvider_ConfigurationGuideline_R12.3”

2. Planning of interworking tests: ensure availability of the necessary resources for all stakeholders

3. Execution of the tests:

Configuration adjustment & debugging, production of test report and configuration guides.
The last version of the product to be tested (OXE, OT, OT-SBC) must be used for the tests.

Reference documents needed:

 “2.TCxxxxen-Ed01_SIP_Trunk_SIPProvider_ConfigurationGuideline_R12.3”
 “3.Interworking_Test_Tech_support_v6.doc” (for an effective technical support from ALE)

During tests, the certifier (BP, SP, etc…) MUST complete the reference document:
“2.TCxxxxen-Ed01_SIP_Trunk_SIPProvider_ConfigurationGuideline_R12.3”

Parts to be completed by the certifier:

- Administrative parts: Name of SIP Provider, Infra components, Topology
- All tests results
- The configuration (OXE and OT-SBC if needed)

OmniPCX Enterprise - Release 10.0 and above

SIP providers supported on OmniPCX® Enterprise and/or Opentouch® TC2005 ed.17
Copyright © ALE International 2019 page 9/13
 Once tests are finished, please attach in the created SR:
- The completed “2.TCxxxxen-
Ed01_SIP_Trunk_SIPProvider_ConfigurationGuideline_R12.3”
- The sipmotor traces results for the concerned tests
- The latest INFOCOLLECT file
- If topology B is used (topologies are explained in the “Technical Questionnaire” document),
2 cases:
o If eSBC = OTSBC, syslog traces are mandatory
o If eSBC = Another eSBC, eSBC’s wireshark traces on Public side are
mandatory

4. Certification:

Based on the final filled-in version, ALE will check the complete certification.
As a result, a technical communication will be published on ALE Business Portal.

Where can you find the request form?

On Business Portal on the Premium Customer Support section (PCS): “Public SIP trunking interoperability
tests Premium Customer Support Form OpenTouch OmniPCX Enterprise”
https://businessportal2.alcatel-lucent.com/public-sip-trunking-interoperability-tests-premium-customer-support-form-
opentouch-omnipcx

In case this process is not followed, the integrator will take its responsibilities and will not be supported by
Alcatel-Lucent Enterprise.

Different ways to perform a public SIP trunking tests

Test performed in the Partner premises or in the SIP provider premises

SOLUTION 1: Tests • Based on the technical questionnaire analysis, the Partner and ALE agrees on the
performed locally test plan coverage
(ALE FE, SP, BP, IOT • BP performs the test in a BP lab before deploying an End-Customer
partner) • ALE provides Technical Support L3 and deliver an acceptance when mandatory
deliverables are available (test plan filled, configuration files, reference traces)
If solution 1 is
not feasible
If the requester has not the knowledge to setup systems & perform SIP
SOLUTION 2: Trunk testing, ALE PROSERV can perform test remotely (SIP Trunk must be
available over INTERNET)
PROSERV PERFORMS • Remote PS Testing quoted case by case (based on technical questionnaire answer)
TESTING REMOTELY • Requester must agree to pay PS Testing to ALE
• Testing must be planned and booked in advance

If solution 1
and 2 are not If the requester has not the knowledge to setup systems & perform SIP
SOLUTION 3: Trunk testing, and if SP can not provide SIP Trunk over INTERNET
feasible • On site PS Testing quoted case by case (based on technical questionnaire answer)
PROSERV PERFORMS • Requester must agree to pay PS Testing to ALE (including travel/hotel)
TESTING ON SITE • Testing must be planned and booked in advance

OmniPCX Enterprise - Release 10.0 and above

SIP providers supported on OmniPCX® Enterprise and/or Opentouch® TC2005 ed.17
Copyright © ALE International 2019 page 10/13
3.2 Guideline for effective technical support process

1. PRE-REQUIREMENT after the 1st incoming / outgoing calls during the test plan:

ALE strongly recommends sending us the following information as soon as the 1 st incoming/outgoing calls
have been made. It will help us to make sure the initial configuration is correct.

Requested information:
1- Topology of the testing lab
2- Infocollect
3- SIPmotor traces for both inbound and outbound call:
motortrace 3
traced >/tmpd/traceSIP &

This information MUST be sent in the SR already created for the SIP Provider certification.

2. REQUESTED TRACES by Tech Support at the end of the test plan:

During the test plan, SIPmotor traces are requested for the concerned tests.

For more information, see the chapter “3- Tests results” of the following document:
“2.TCxxxxen_SIP_Trunk_SIPProvider_ConfigurationGuideline_Rx.x”

These traces will be archived by Tech Support along with your test plan.

Traces to be done for each requested test:

motortrace 3
traced >/tmpd/traceSIP_#xxx.txt &

 At the end of the tests, the latest INFOCOLLECTand all SIPmotor traces MUST be attached in the SR

3. FOR A TEST FAILURE ANALYSIS, a new Service Request (SR) MUST BE CREATED:

 A SR must be opened for any problem. One SR must describe one issue only.

 For efficient routing to Technical Support structure dedicated to SIP interoperability tests follow-up:

- Summary / Subject:
Must contain the tag: <Tested_Provider_Name> and the subject of the issue

- Case Detail / Parent Case:

Please fill-in the SR number of the tested SIP Provider (already created at the beginning of the
certification).

OmniPCX Enterprise - Release 10.0 and above

SIP providers supported on OmniPCX® Enterprise and/or Opentouch® TC2005 ed.17
Copyright © ALE International 2019 page 11/13
 - Summary / SR description:

a. The description MUST contain your TS contact for this SIP Provider certification:
“SR followed by: Mr Ilias DAHMANI-IDRISSI ALE”
OR “SR followed by: Mr Mikaël FERELLOC ALE”

b. Test reference in test plan if any, test summary otherwise

c. Test scenario: callee, caller, OXE user, external user called/calling through SIP trunk, SIP external
gateway, SBC, …

d. Step by step test description

e. Detailed test result: call establishment failure, immediate call cut, half way audio from caller to
callee, no audio, bad audio quality, bad display on set…

f. Important elements settings in Voip context: law, compression algorithm…

g. Requested traces MUST be attached in the SR:

 OXE sip motor traces:

killall traced
motortrace 6
traced -1 /tmpd/sipMotortrace -s 9000000 -f 99 -d &

 OXE call handling traces

tuner km ctr all=off
trc i
actdbg all=off
tuner at tr s cpu cpl hybrid=on time
actdbg sip=on fct=on isdn=on abcf=on rtp=on cnx=on voip=on
mtracer -aug -1 /tmpd/sipCHtrace -f 99 -s 9000000 -d&

 infocollect after the issue

 Immediately after SR creation, a mail should be sent to your TS contact with SR identifier and
short summary.

Thank you.

OmniPCX Enterprise - Release 10.0 and above

SIP providers supported on OmniPCX® Enterprise and/or Opentouch® TC2005 ed.17
Copyright © ALE International 2019 page 12/13
Submitting a Service Request
Please connect to our eService Request application.

Before submitting a Service Request, please be sure:

 The application has been certified via the AAPP if a third party application is involved.
 You have read the release notes that list new features, system requirements, restrictions, and more,
and are available in the Technical Documentation Library.
 You have read through the related troubleshooting guides and technical bulletins available in the
Technical Documentation Library.
 You have read through the self-service information on commonly asked support questions and known
issues and workarounds available in the Technical Knowledge Center.

- END OF DOCUMENT -

OmniPCX Enterprise - Release 10.0 and above

SIP providers supported on OmniPCX® Enterprise and/or Opentouch® TC2005 ed.17
Copyright © ALE International 2019 page 13/13