TC1284en-Ed129 OXO Connect Public SIP Trunking Interoperability and Technical SupportProcedure
TC1284en-Ed129 OXO Connect Public SIP Trunking Interoperability and Technical SupportProcedure
TC1284en-Ed129 OXO Connect Public SIP Trunking Interoperability and Technical SupportProcedure
This document describes the ALE process for the approval and support of public SIP Trunk solutions with the OXO Connect
& OXO Connect Evolution. The doc also updates the reference list of supported solutions.
Revision History
Edition 1: August 25, 2012 creation of the document.
Legal notice:
www.al-enterprise.com 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. © Copyright 2023 ALE
International, ALE USA Inc. All rights reserved in all countries.
Table of contents
1 SIP Trunks .............................................................................................................................................. 3
2.1 Approval
A solution involving OXO and a Public SIP network must be approved by ALE thru a specific process intended to set up and
validate the SIP interop perimeter proper to the solution. The validation is done in collaboration with ALE Business Partners by
passing a suite of SIP tests and consolidating the end user operation on one or more pilot customer sites.
As a Business Partner, you can contact your ALE local representatives if you would like to help approving a new SIP provider.
To get more detailed information, please send your request to [email protected].
• GA solutions (General Availability): these solutions are approved for free deployment as of the specifications
published by ALE in the dedicated configuration guide. When the doc conditions are respected, technical
assistance, expertise and bug correction are ensured by ALE following the standard policy and SLAs. For
an issue occurring during the valid period of support of the OXO SW release, a Business Partner must just open a
normal Service Request indicating the name of the SIP Provider.
• LA/MA solutions (Limited Availability/Migrated Availability): the pilot-site program which is required to reach
the GA approval level of the solution is open but is either not achieved or not yet started. The solution is therefore
NOT open for free deployment on customer sites. As a partner, you can contact our organization via email
([email protected]) if you wish to join the pilot program or just want to be informed of its progress.
The LA/MA support is then a specific assistance delivered for customer pilot-sites. The Pilot sites must
have been identified and agreed by ALE before their installation. During the pilot period (at least 4 weeks),
the systems are monitored remotely by ALE and the associated Business Partner benefits of privileged access to ALE
Technical Support resources.
Detailed information concerning the management of SIP Trunk Profiles is available in the Technical
Bulletin TC1994 ("SIP EASY CONNECT: SIP Trunk Profile Import/Export").
GA solutions are noted with their TC ref. of configuration guide plus the applicable OXO release.
Or only the applicable release, in case of automatic GA report (whenever possible) in the next release(s). The TC
configuration guide to use, is then the most recent release one having a TC ref.
MA solutions mention the OXO release applicable SIP profile. The TC configuration guide to use, is then the most
recent GA release one having a TC ref.
LA solutions just mention the applicable OXO release.
OXO Connect R3.2, R4.0, R5.2 and OXO Connect R6.0 share the same TC Configuration guide and the same sip
profile.
Therefore for ie you can use OXO Connect R3.2, R4.0 or R5.2 inputs for OXO Connect R6.0 deployement.
(MA) Migrated Availability, indicates that a Limited Availability R10.3, Connect 2.x, Connect R3.x, Connect R4.0, Connect
R5.X or Connect R6.x SIP Profile is available on the BP web site and you can readily use it for SIP trunk deployment. This Limited
Availability SIP profile must be used together with the previous certified G.A Technical communication.
Any OXO sites you deploy with this L.A SIP Profile (there is no limit to the quantity of sites) are considered as Pilot sites.
Therefore, please inform the SIP Technical support team ([email protected]) about your site/s and they will monitor
them on your behalf during the standard 4 week pilot period.
Note: L.A pilot site solutions comply with the same features and restrictions level that was previously certified in the G.A branch.
This compatibility level is detailed in the associated G.A Technical communication.
Only if additional features or configuration changes are required on the L.A site but are not approved in the reference G.A
Technical communication, will a limited test/trace phase need to be managed again in relation with the new changes.
TC2774 (R3.1)
4 Telecom Services
Austria A1 (METRO)
TC2676 (R3.2)
NeoTel Business Trunk
TC2111 (R10.1)
⚫ R2.2 (MA) ⚫ R3.2 (MA)
TELE 2
TC2678 (R3.2)
UPC
TC2697 (R3.2)
TC2726 (R3.2)
RNT
Claro
Add-On
TC2706 (R3.2)
Axians
Codepi
Coriolis Telecom
Dstny (MyOPENIP)
Fingerprint
TC2042 (R10.0)
⚫ R2.2 (MA) ⚫ R3.2 (MA)
Hexanet
Keyyo
Legos
Linkersip
Linkt
⚫ R3.2 (MA)
TC2371 (R2.0)
Nerim
NXO Telecom
OBS-Biv
TC2681 (R3.2)
OBS-BTIP
OpenIP
OpenIP (MyOPENIP)
OVH
Unyc (Serveurcom)
Sewan
Synelyans A
TC2743 (R3.2)
Synelyans F
TC2745 (R3.2)
1&1 Versatel
(Remote Hosted NAT-TOPO C)
TC2752 (R3.2)
BiTel
Deutsche Telefon
Germany
TC2237 (R10.3) TC2284 (R2.0) ⚫ R3.2 (MA)
Deutsche Telekom
DLAN IP Voice/Data
(Router with SIP-ALG-TOPO B)
TC2769 (R3.2)
EmslandTel.NET
EnviaTel
TC2771 (R3.2)
htp
TC2772 (R3.2)
Inexio
TC2778 (R3.2)
ITK Connect
TC2779 (R3.2)
Komro
TC2845 (R3.2)
LWLcom
TC2780 (R3.2)
M-net
Plusnet (QSC)
SIPgate
Soco
TC2793 (R3.2)
Stadtwerke Merseburg
TC2673 (R3.2)
Telesys
TC2690 (R3.2)
UnityMedia
Vodafone
TC2794 (R3.2)
Voiceforce.one
TC2795 (R3.2)
Voiceworks
Greece
TC2295 (R10.3) ⚫ R2.2 (MA) TC2688 (R3.2)
OTE
TC2125 (R10.1)
⚫ R2.2 (MA) ⚫ R3.2 (MA)
TC2055 (R10.0)
Intellicom
OnVoIP (G7eleven)
Ireland
Viatel
TC2854 (R3.2)
Active Network
TC2729 (R3.2)
Net and work
ICTprovider
Voiceworks
Ziggo
Norway
TC2172 (R10.1) ⚫ R2.2 (MA) ⚫ R3.2 (MA)
Telenor
(Remote Hosted NAT - TOPO C)
Vodafone
M1
NetPluz Asia
TC2789 (R3.2)
Singtel
Orange
Slovakia
TC2821 (R3.2)
Swan
Telekom Slovakia
TC2790 (R3.2)
Biztec
Grupo IB 360
Grupo Universal
LCR.com
Telefonica (movistar)
Premium Max
Spain
TC2240 (R10.3) ⚫ R2.2 (MA) ⚫ R3.2 (MA)
Sarenet (Sarevoz)
TC2738 (R3.2)
Sisnet
TBC
TC2727 (R3.2)
Telecable
VozTelecom
Sweden TDC
TC2089 (R10.1)
⚫ R2.2 (MA) TC2833 (R3.2)
Switzerland Peoplefone
TC2834 (R3.2)
SIPCall.Ch
Sunrise
TC2168 (R10.2)
⚫ R2.2 (MA) ⚫ R3.2 (MA)
UPC Cablecom
(Remote Hosted NAT - TOPO C)
TC2807 (R3.2)
9 Group Telecomm.
Voiceflex
TC2751 (R3.2)
VoiceHost
(OXO Static NAT – TOPO D)
TC2739 (R3.2)
Akabis
TC2847 (R3.2)
USA
Bandwidth.com
TC2848 (R3.2)
CCI Networks
Clearfly
TC2849 (R3.2)
Saddleback Comm.
Securenet
Sotel
5 Ongoing Projects
The following table gives a rough status of the approval projects that are being carried out.
- END OF DOCUMENT -