alcatel-lucent application partner program inter-working ......the validity of the interworking...

Alcatel-Lucent Application Partner Program – Inter-working report - Edition 1 - page 1/31

Copyright © 2014 Alcatel-Lucent, All rights reserved

Alcatel-Lucent Application Partner Program Inter-Working Report

Partner: Etrali Application type: Trading Turrets

Application name: OpenTrade Alcatel-Lucent Platform: OmniPCX Enterprise™

The product and release listed have been tested with the Alcatel-Lucent Communication Platform and the release specified hereinafter. The tests concern only the inter-working between the AAPP member’s product and the Alcatel-Lucent Communication Platform. The inter-working report is valid until the AAPP member’s product issues a new major release of such product (incorporating new features or functionality), or until Alcatel-Lucent issues a new major release of such Alcatel-Lucent product (incorporating new features or functionalities), whichever first occurs. ALCATEL-LUCENT MAKES NO REPRESENTATIONS, WARRANTIES OR CONDITIONS WITH RESPECT TO THE APPLICATION PARTNER PRODUCT. WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, ALCATEL-LUCENT HEREBY EXPRESSLY DISCLAIMS ANY AND ALL REPRESENTATIONS, WARRANTIES OR CONDITIONS OF ANY NATURE WHATSOEVER AS TO THE AAPP MEMBER’S PRODUCT INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF MERCHANTABILITY, NON INFRINGEMENT OR FITNESS FOR A PARTICULAR PURPOSE AND ALCATEL-LUCENT FURTHER SHALL HAVE NO LIABILITY TO AAPP MEMBER OR ANY OTHER PARTY ARISING FROM OR RELATED IN ANY MANNER TO THIS CERTIFICATE.



Certification overview

Date of the certification June 2014

Alcatel-Lucent’s representative Yves Dupont

AAPP member representative Ryma HADJI

Alcatel-Lucent Communication Platform

OmniPCX Enterprise

Alcatel-Lucent Communication Platform release

R11.0.1 (k1.520-29)

AAPP member application release V4

Application Category Trading turrets

Author(s): Ryma Hadji Reviewer(s): Rachid Himmi Revision History Edition 1: creation of the document – July 2014

Test results

Passed

Refused Postponed

Passed with restrictions

Refer to the section 6 for a summary of the test results.

IWR validity extension None



AAPP Member Contact Information

Contact name: Raymond DAVID Title: Quality Assurance Address: 15 rue henri-Rol-Tanguy Zip Code: 93100 City: MONTREUIL Country: FRANCE Phone: +33155829360 Fax: Mobile Phone: +33764951394 Web site: www.etrali.com

Email address: [email protected]

mailto:[email protected]



TABLE OF CONTENTS

1 INTRODUCTION .................................................................................................................................... 5

2 VALIDITY OF THE INTERWORKING REPORT ............................................................................. 6

3 LIMITS OF THE TECHNICAL SUPPORT ......................................................................................... 7

3.1 CASE OF ADDITIONAL THIRD PARTY APPLICATIONS ............................................................................. 7

4 APPLICATION INFORMATION .......................................................................................................... 8

5 TEST ENVIRONMENT ............................................................................................................................ 9

5.1 HARDWARE CONFIGURATION .............................................................................................................. 9 5.2 SOFTWARE CONFIGURATION ................................................................................................................ 9

6 SUMMARY OF TEST RESULTS ........................................................................................................ 10

6.1 SUMMARY OF MAIN FUNCTIONS SUPPORTED ...................................................................................... 10 6.2 SUMMARY OF PROBLEMS ................................................................................................................... 10 6.3 SUMMARY OF LIMITATIONS ............................................................................................................... 10 6.4 NOTES, REMARKS .............................................................................................................................. 10

7 TEST RESULT TEMPLATE ................................................................................................................. 11

8 TESTS RESULTS ................................................................................................................................... 12

9 APPENDIX A : AAPP MEMBER’S APPLICATION DESCRIPTION ............................................ 14

9.1 VOICE REQUIREMENTS ....................................................................................................................... 14 9.2 DTMF ............................................................................................................................................... 14 9.3 NOT SUPPORTED ................................................................................................................................ 15 9.4 SIP URI ............................................................................................................................................. 15

10 APPENDIX B: CONFIGURATION REQUIREMENTS OF THE AAPP MEMBER’S

APPLICATION .............................................................................................................................................. 16

10.1 CARRIER ............................................................................................................................................ 16 10.2 DID PREFIX ....................................................................................................................................... 16 10.3 PERIPHERAL EQUIPMENT ................................................................................................................... 17 10.4 LINK/CHANNELS ................................................................................................................................ 17 10.5 ROUTING RULES ................................................................................................................................ 18 10.6 CPN SELECTION ................................................................................................................................ 19 10.7 OUTGOING TRUNK ............................................................................................................................. 19

11 APPENDIX C: ALCATEL-LUCENT COMMUNICATION PLATFORM: CONFIGURATION

REQUIREMENTS.......................................................................................................................................... 20

11.1 TRUNK GROUP CONFIGURATION ........................................................................................................ 20 11.2 SIP EXT GATEWAY CONFIGURATION ................................................................................................. 21 11.3 INTERNAL TRUNK GROUP CONFIGURATION........................................................................................ 22 11.4 SIP GATEWAY ................................................................................................................................... 22 11.5 ARS (AUTOMATIC ROUTE SELECTION) ............................................................................................. 23

12 APPENDIX D: AAPP MEMBER’S ESCALATION PROCESS .................................................... 25

13 APPENDIX E: AAPP PROGRAM ................................................................................................... 26

13.1 ALCATEL-LUCENT APPLICATION PARTNER PROGRAM (AAPP)......................................................... 26 13.2 ALCATEL-LUCENT.COM ..................................................................................................................... 27

14 APPENDIX F: AAPP ESCALATION PROCESS ........................................................................... 28

14.1 INTRODUCTION .................................................................................................................................. 28 14.2 ESCALATION IN CASE OF A VALID INTER-WORKING REPORT ............................................................. 29 14.3 ESCALATION IN ALL OTHER CASES ..................................................................................................... 30 14.4 TECHNICAL SUPPORT ACCESS ............................................................................................................ 31



1 Introduction This document is the result of the certification tests performed between the AAPP member’s application and Alcatel-Lucent’s platform. It certifies proper inter-working with the AAPP member’s application. Information contained in this document is believed to be accurate and reliable at the time of printing. However, due to ongoing product improvements and revisions, Alcatel-Lucent cannot guarantee accuracy of printed material after the date of certification nor can it accept responsibility for errors or omissions. Updates to this document can be viewed on:

- the Technical Support page of the Enterprise Business Portal (https://businessportal.alcatel-lucent.com) in the Application Partner Interworking Reports corner (restricted to Business Partners)

- the Application Partner portal (https://applicationpartner.alcatel-lucent.com) with free access.

https://businessportal.alcatel-lucent.com/

https://applicationpartner.alcatel-lucent.com/



2 Validity of the InterWorking Report This InterWorking report specifies the products and releases which have been certified. This inter-working report is valid unless specified until the AAPP member issues a new major release of such product (incorporating new features or functionalities), or until Alcatel-Lucent issues a new major release of such Alcatel-Lucent product (incorporating new features or functionalities), whichever first occurs. A new release is identified as following:

a “Major Release” is any x. enumerated release. Example Product 1.0 is a major product release.

a “Minor Release” is any x.y enumerated release. Example Product 1.1 is a minor product release

The validity of the InterWorking report can be extended to upper major releases, if for example the interface didn’t evolve, or to other products of the same family range. Please refer to the “IWR validity extension” chapter at the beginning of the report.

Note: The InterWorking report becomes automatically obsolete when the mentioned product releases are end of life.



3 Limits of the Technical support

Technical support will be provided only in case of a valid InterWorking Report (see chapter 2 “Validity of the InterWorking Report) and in the scope of the features which have been certified. That scope is defined by the InterWorking report via the tests cases which have been performed, the conditions and the perimeter of the testing as well as the observed limitations. All this being documented in the IWR. The certification does not verify the functional achievement of the AAPP member’s application as well as it does not cover load capacity checks, race conditions and generally speaking any real customer's site conditions.

Any possible issue will require first to be addressed and analyzed by the AAPP member before being escalated to Alcatel-Lucent. For any request outside the scope of this IWR, Alcatel-Lucent offers the “On Demand Diagnostic” service where assistance will be provided against payment. For more details, please refer to Appendix F “AAPP Escalation Process”.

3.1 Case of additional Third party applications

In case at a customer site an additional third party application NOT provided by Alcatel-Lucent is included in the solution between the certified Alcatel-Lucent and AAPP member products such as a Session Border Controller or a firewall for example, Alcatel-Lucent will consider that situation as to that where no IWR exists. Alcatel-Lucent will handle this situation accordingly (for more details, please refer to Appendix F “AAPP Escalation Process”).



4 Application information Application commercial name: OpenTrade Application version: 4 Interface type: SIP

Brief application description:

Open Trade is an intelligent trading communication platform combining voice, email, instant messaging and video, for easy communication in fast-moving markets.

With its pure IP architecture, voice trading on Open Trade integrates cloud strategy with the back-end localised in the network. It makes managing distant sites and turrets easier via remote access and administration. Any Open Trade component can be managed as standard IT equipment.

Open Trade :

uses IP LAN/WAN infrastructures to provide greater flexibility of deployment options;

is designed to leverage industry standard protocols and to ensure an easy integration with your company's IT solution providers and Administrative TDM or SIP Telephony infrastructures (PBX, IP PBX);

has moved from a "hardware only" design to a combination of software and hardware components, facilitating platform upgrades and support;

uses multicast technologies to optimise bandwidth;

offers three typical architectures: standalone, datacentre and remote, which can be simplified and combined.



5 Test environment Figure 1 Test environment

5.1 Hardware configuration

OmniPCX Entreprise: o CS (Call Server Processing Unit) o GD (Gateway driver processing Unit o PRA T2 (ISDN Access) o MIX 2/4/4 (ISDN T0, digital & analog interfaces) o UA digital and analog sets

AHL interface: o V24 through MOXA box o TCP/IP

5.2 Software configuration

Alcatel-Lucent Communication Platform: OmniPCX Enterprise R11.0.1 (R11.0.1-k1.520-29-fr-c0)

Partner Application : OpenTrade V4

Provider Alcatel OXE R11.0.1

Plugin

UnitOpen Trade

Server

Open Trade turrets

EN

_H

T0

46

-00

1.v

sd



6 Summary of test results

6.1 Summary of main functions supported

Basic Calls

Call presentation

Call Forwarding Unconditional(CFU)

Call Forwarding on no reply

Call Forwarding On Busy

Supervised Transfer

Blind Transfer.

Conference

DTMF Testing

Call Hold/Resume Scenarios

6.2 Summary of problems none

6.3 Summary of limitations

none

6.4 Notes, remarks



7 Test Result Template The results are presented as indicated in the example below:

Test Case Id

Test Case N/A OK NOK Comment

1

Test case 1

Action

Expected result

2

Test case 2

Action

Expected result

The application waits for PBX timer or phone set hangs up

3

Test case 3

Action

Expected result

Relevant only if the CTI interface is a direct CSTA link

4

Test case 4

Action

Expected result

No indication, no error message

… …

Test Case Id: a feature testing may comprise multiple steps depending on its complexity. Each step has to be completed successfully in order to conform to the test. Test Case: describes the test case with the detail of the main steps to be executed the and the expected result N/A: when checked, means the test case is not applicable in the scope of the application OK: when checked, means the test case performs as expected NOK: when checked, means the test case has failed. In that case, describe in the field “Comment” the reason for the failure and the reference number of the issue either on Alcatel-Lucent side or on AAPP member side Comment: to be filled in with any relevant comment. Mandatory in case a test has failed especially the reference number of the issue.



8 Tests Results

Test Case

Id Test Case

N/A

OK NOK Comment

1

Test case 1

Basic Call

confirm ringback ok, then confirm call connection. Hangup call and confirm proper resources release (no RTP remaining)

2

Test case 2

Call Presentation

The caller and connected name should be displayed.

3

Test case 3

Call Forwarding Unconditional(CFU)

The call should be established between set OT1 and set Alcatel phone

4

Test case 4

Call Forwarding on no reply

The should be established between set OT1 and set Alcatel phone

5

Test case 5

Call Forwarding On Busy

The call should be established between set OT1 and set Alcatel phone

The busy status is NA for openTrade user. Tests run for busy alcatel phones

6

Test case 6

Supervised Transfer

The call should be established between set OT1 and set Alcatel phone , ring back tone heard .

7

Test case 7

Blind Transfer

The call should be established between set OT1 and set Alcatel phone , ring back tone heard .

8

Test case 8

Conference

The call should be established between set OT1, OT2 and set Alcatel1, Alcatel2 phone. ,

9

Test case 9

DTMF Testing (incoming & outgoing)

DTMF working heard and seen in the traces

10

Test case 10

Long Duration Call / Session Timers

The call still established after session timer (REINVITE) and audio OK

OpenTrade doesn’t support midcall codec negotiation

11

Test case 11

Call Hold/Resume Scenarios

Hear MOH when hold and audio back when call resumed .



ue.



9 Appendix A : AAPP member’s Application description

9.1 Voice requirements RTP (Real Time protocol) is used for media traffic

Codec supported G711 (this codec sets the voice quality reference for narrow-band voice codecs from

the client perspective and is supported by many VoIP terminals in the consumer market)

A Law / U Law

Rate: 64 k

Framing : 20ms

Open Trade locks the RTP flows once the first one is received. Any modification (ssrc, codec, port..) on the

RTP session is not authorised apart if a SIP re-INVITE message is used.

UDP datagrams size UDP datagrams, that exceeds the size of the layer 2 maximum transmission unit (MTU), which for

Ethernet is 1500 bytes, may or may not be received correctly. Although fragmentation and re-

assembly at the IP layer can be used for long datagrams, packet loss or excessive delay can make

this unreliable.

Open Trade UDP datagrams size is under than 1300 bytes.

SDP size:

Offer: 320 octets Response: 190 octets

Ring back tone Usually, the calling side generates a local ring back tone upon receipt of a 180 ringing answer to

invite message.

9.2 DTMF

There are several ways to transmit DTMF tones:

Inband DTMF Inband transport of DTMF tones means that the DTMF tones are transmitted within the RTP stream.

This is only possible if the RTP stream is not compressed—for example, with the G.711 codec. Other

codecs that perform a compression/decompression—for example, G.729—are not suitable.

Outband DTMF The SIP INFO method can be used to transmit DTMF tones out-of-band as telephone-events in a

reliable manner independent of the media stream.

DTMF via RFC2833 (RTP Payload for DTMF Digits) Transport of DTMF tones is achieved via Named Events using two RTP payload formats, named

telephone-event and tone, and associated Internet media (MIME) types, audio/telephone-event and



audio/tone. These payload formats use a dynamic payload type number (for example, payload type

98 or 101). These payload formats can be interpreted at a PSTN Gateway, or at an Application

Server or an Interactive Response System.

The Open Trade system supports DTMF via TFC2833 with the payload type 101 by default (other

possible payload types 96 to 98).

Open Trade can transmit the following DTMF digits: ‘0’, ‘1’, ‘2’, ‘3’, ‘4’, ‘5’, ‘6’, ‘7’, ‘8’, ‘9’, ‘#’,

‘*’.

9.3 Not supported

CLIR / COLR Calling Line Identification Restriction / Connected Line Identification Restriction

CCBS / CCNR Completion of Calls to Busy Subscribers / No reply.

The CCBS and CCN) features allow a calling subscriber to be automatically connected to a busy or

no reply called subscriber when that subscriber becomes available.

The following functions are not used in the SIP trunk with service providers; given that Open Trade

support them natively and locally:

Hold

Transfer

Forward

FAX Open Trade does not support Inband FAX as well as FAX via T.38.

9.4 SIP URI Open Trade uses Display Name in the SIP URI, example:

”display name” <sip:[userinfo]hostname:port>

The “display name” can contain all Unicode/UTF8 characters.



10 Appendix B: Configuration requirements of the AAPP member’s application

Before connecting SIP trunk with IP PBX, Open Trade system needs to be installed and the basic

configuration should have been completed with the administration Open Trade application

10.1 Carrier Add a carrier for the SIP trunk (Facilities Management > Carriers menu).

Figure 1: Add a Carrier

10.2 DID Prefix Add a DID prefix, for the SIP Trunk (Facilities Management > DID Prefixes)

Figure 2: DID prefix

Then, add the associated DID in DID Declaration menu.

EN

_H

T0

13

-001

.VS

D



10.3 Peripheral Equipment The Peripheral equipment is added by defining which SIP-X (CAB) handles the SIP trunk.

The SIP Trunk is configured by selecting the parameters for manufacturer, product name and SIP

strategy and by adding the IP address(es) of the IP PBX.

Figure 3: Open Trade configuration for Alcatel

In the Contact Parameters => IP address or hostname : fill the IP address of the OXE .

10.4 Link/Channels The SIP trunk (Telco Link) is configured with the number of allowed concurrent voice calls or channels

(depending on bandwidth), the Carrier to be used, the DID prefix and the interface type.

Select the equipment previously created and configure the Telco Link (Peripheral equipments >

Link/Channel).



Figure 4: SIP trunk (Telco Link) configuration

10.5 Routing Rules The routing rules define which digits allow accessing the SIP trunk, which prefix is sent and if the

predefined public access code (domain) is used.

In Telecom Management node, add one or several routing rules (in the example below, all number

dialled on private domain are routed on the Private _IPBX carrier without changing the dialled

number).

Figure 5: Routing rule

EN

_H

T01

3-0

06

.VS

D



10.6 CPN Selection In Telecom Management node, add a CPN selection rule. The CPN Selection defines which type of

CPN (Calling Party Number) is sent to the particular SIP trunk Carrier (for PBX or IP PBX, select the

Private domain a short CPN type (generally without prefix selection).

Figure 6: CPN selection

10.7 Outgoing Trunk In Telecom Management node, add an Outgoing trunk.

All workgroups (containing the traders) which are permitted to use a particular trunk are added.

Optional the overflow trunk to be used can be selected and activated.

Figure 7: Outgoing trunk

EN

_H

T0

13

-006

.VS

D

EN

_H

T0

13

-00

7.V

SD



11 Appendix C: Alcatel-Lucent Communication Platform: configuration requirements

11.1 Trunk Group configuration This Trunk Group is associated to the External Gateway to Open Trade.

Review/Modify: Trunk Groups Node Number (reserved) : 2 Trunk Group ID : 3 Trunk Group Type + T2 Trunk Group Name : SIP OT UTF-8 Trunk Group Name : ------------------------- Number Compatible With : -1 Remote Network : 15 Shared Trunk Group + False Special Services + Nothing Node number : 2 Transcom Trunk Group + False Auto.reserv.by Attendant + False Overflow trunk group No. : -1 Tone on seizure + False Private Trunk Group + False Q931 Signal variant + ISDN all countries SS7 Signal variant + No variant Number Of Digits To Send : 4 Channel selection type + Quantified Auto.DTMF dialing on outgoing call + NO T2 Specification + SIP Homogenous network for direct RTP + NO Public Network COS : 31 DID transcoding + False Can support UUS in SETUP + True Associated Ext SIP gateway : -1 Implicit Priority Activation mode : 0 Priority Level : 0 Preempter + NO Incoming calls Restriction COS : 10 Outgoing calls Restriction COS : 10 Callee number mpt1343 + NO Overlap dialing + YES Call diversion in ISDN + NO

Note: Q931 Signal variant must be: ISDN all countries because Open Trade doesn’t support the SIP

REFER messages sent by the ABCF trunks.



11.2 SIP Ext Gateway configuration

Node Number (reserved) : 2 Instance (reserved) : 1 SIP External Gateway ID : 1 Gateway Name : SIP DKE RECO SIP Remote domain : 172.29.187.244 PCS IP Address : --------------------------------------- SIP Port Number : 5060 Transport type + UDP Belonging Domain : --------------------------------------- Registration ID : --------------------------------------- Registration ID P_Asserted + False Registration timer : 0 SIP Outbound Proxy : --------------------------------------- Supervision timer : 60 Trunk group number : 3 Pool Number : -1 Outgoing realm : --------------------------------------- Outgoing username : --------------------------------------- Outgoing Password : -------------------- Confirm : -------------------- Incoming username : --------------------------------------- Incoming Password : -------------------- Confirm : -------------------- RFC 3325 supported by the distant + False DNS type + DNS A SIP DNS1 IP Address : --------------------------------------- SIP DNS2 IP Address : --------------------------------------- SDP in 18x + False Minimal authentication method + SIP None INFO method for remote extension + False To EMS + False SRTP + RTP only Ignore inactive/black hole + False Contact with IP address + False Dynamic Payload type for DTMF : 97 Outbound Calls 100 REL + Supported Incoming calls 100 REL + Not Requested Gateway type + Standard type Re-Trans No. for REGISTER/OPTIONS : 2 P-Asserted-ID in Calling Number + True Trusted P-Asserted-ID header + False Diversion Info to provide via + Diversion Proxy identification on IP address + False Outbound calls only + False SDP relay on Ext. Call Fwd + Default SDP Transparency Override + False RFC 5009 supported / Outbound call + Not Supported Nonce caching activation + NO FAX Procedure Type + T38 only DNS SRV/Call retry on busy server : 0 Unattended Transfer for RSI + NO Redirection functionality + NO



Attended Transfer + NO Trusted From header + True Support Re-invite without SDP + True Type of codec negotiation + Single codec G711

In the SIP Remote domain: fill the IP address of the SIP X.

Dynamic Payload types for DTMF supported by Open Trade are: 96, 97, and 101.

11.3 Internal Trunk group configuration

─Review/Modify: Trunk Groups─ Node Number (reserved) : 2 Trunk Group ID : 20 Trunk Group Type + T2 Trunk Group Name : SIP_2 UTF-8 Trunk Group Name : -------------- Number Compatible With : -1 Remote Network : 12 Shared Trunk Group + False Special Services + Nothing Node number : 2 Transcom Trunk Group + False Auto.reserv.by Attendant + False Overflow trunk group No. : -1 Tone on seizure + False Private Trunk Group + False Q931 Signal variant + ABC-F SS7 Signal variant + No variant Number Of Digits To Send : 0 Channel selection type + Quantified Auto.DTMF dialing on outgoing call + YES T2 Specification + SIP Homogenous network for direct RTP + NO Public Network COS : 2 DID transcoding + False Can support UUS in SETUP + False Associated Ext SIP gateway : -1 Implicit Priority Activation mode : 0 Priority Level : 0 Preempter + NO Incoming calls Restriction COS : 10 Outgoing calls Restriction COS : 10 Callee number mpt1343 + NO Overlap dialing + YES Call diversion in ISDN + NO

11.4 SIP Gateway The SIP gateway is associated to the SIP trunk 20.

“Session Timer Method” must be: RE_INVITE. [Open Trade doesn’t support UPDATE messages]



─Review/Modify: SIP Gateway─

Node Number (reserved) : 2 Instance (reserved) : 1 Instance (reserved) : 1 SIP Subnetwork : 12 SIP Trunk Group : 20 IP Address : 172.16.21.177 Machine name - Host : node000001 SIP Proxy Port Number : 5060 SIP Subscribe Min Duration : 1800 SIP Subscribe Max Duration : 86400 Session Timer : 1800 Min Session Timer : 900 Session Timer Method + RE_INVITE DNS local domain name : ------------------- DNS type + DNS A SIP DNS1 IP Address : -------------------- SIP DNS2 IP Address : -------------------- SDP in 18x + False Cac SIP-SIP + False INFO method for remote extension + False Dynamic Payload type for DTMF : 97

11.5 ARS (Automatic Route Selection) In the Translator Menu, select the “Automatic Route Selection”=> ARS Route List=>ARS

Route:

Node Number (reserved) : 2 Instance (reserved) : 1 Instance (reserved) : 1 ARS Route list : 0 Route : 1 Name : TO OT Trunk Group Source + Route Trunk Group : 3 No.Digits To Be Removed : 0 Digits To Add : ------------------------------ Numbering Command Tabl. ID : 1 VPN Cost Limit : 0 Protocol Type + Dependant on Trunk Group Type NPD identifier : 255 Route Type + Public ATM Address ID : -1 Preempter + False Quality [ Add ] [ Remove ] [ Next ] [Previous] Quality + Speech

In the Translator Menu, select the “Automatic Route Selection”=> ARS Route List=>Time-based route

List:

Node Number (reserved) : 2 Instance (reserved) : 1 Instance (reserved) : 1 ARS Route list : 0



Time-based Route List ID : 1 Time-based Route [ Add ] [ Remove ] [ Next ] [Previous] Time-based Route Route Number : 1 Waiting Cost Limit : -1 Stopping Cost Limit : -1

In the Translator Menu, select the “Automatic Route Selection”=> Numbering Command

Table:

Node Number (reserved) : 2 Instance (reserved) : 1 Instance (reserved) : 1 Table ID : 1 Carrier Reference : 0 Command : I Associated Ext SIP gateway : 1

In the Translator Menu, select the “Numbering Plan” and check:

Review/Modify: Numbering Plan Node Number (reserved) : 2 Instance (reserved) : 1 Number : 5 Prefix Meaning + ARS Prof.Trg Grp Seizure Domain Identifier : 0 Discriminator No. : 0



12 Appendix D: AAPP member’s escalation process

Etrali Contact support Level 3

Email : [email protected]

Tel : +33155829348




13 Appendix E: AAPP program

13.1 Alcatel-Lucent Application Partner Program (AAPP)

The Application Partner Program is designed to support companies that develop communication applications for the enterprise market, based on Alcatel-Lucent's product family. The program provides tools and support for developing, verifying and promoting compliant third-party applications that complement Alcatel-Lucent's product family. Alcatel-Lucent facilitates market access for compliant applications. The Alcatel-Lucent Application Partner Program (AAPP) has two main objectives:

Provide easy interfacing for Alcatel-Lucent communication products: Alcatel-Lucent's communication products for the enterprise market include infrastructure elements, platforms and software suites. To ensure easy integration, the AAPP provides a full array of standards-based application programming interfaces and fully-documented proprietary interfaces. Together, these enable third-party applications to benefit fully from the potential of Alcatel-Lucent products.

Test and verify a comprehensive range of third-party applications: to ensure proper inter-working, Alcatel-Lucent tests and verifies selected third-party applications that complement its portfolio. Successful candidates, which are labelled Alcatel-Lucent Compliant Application, come from every area of voice and data communications.

The Alcatel-Lucent Application Partner Program covers a wide array of third-party applications/products designed for voice-centric and data-centric networks in the enterprise market, including terminals, communication applications, mobility, management, security, etc.



Web site The Application Partner Portal is a website dedicated to the AAPP program and where the InterWorking Reports can be consulted. Its access is free at http://applicationpartner.alcatel-lucent.com

13.2 Alcatel-Lucent.com You can access the Alcatel-Lucent website at this URL: http://www.Alcatel-Lucent.com/

http://applicationpartner.alcatel-lucent.com/

http://www.alcatel.com/



14 Appendix F: AAPP Escalation process

14.1 Introduction

The purpose of this appendix is to define the escalation process to be applied by the Alcatel-Lucent Business Partners when facing a problem with the solution certified in this document. The principle is that Alcatel-Lucent Technical Support will be subject to the existence of a valid InterWorking Report within the limits defined in the chapter “Limits of the Technical support”. In case technical support is granted, Alcatel-Lucent and the Application Partner, are engaged as following:

(*) The Application Partner Business Partner can be a Third-Party company or the Alcatel-Lucent Business Partner itself



14.2 Escalation in case of a valid Inter-Working Report

The InterWorking Report describes the test cases which have been performed, the conditions of the testing and the observed limitations. This defines the scope of what has been certified. If the issue is in the scope of the IWR, both parties, Alcatel-Lucent and the Application Partner, are engaged: Case 1: the responsibility can be established 100% on Alcatel-Lucent side.

In that case, the problem must be escalated by the ALU Business Partner to the Alcatel-Lucent Support Center using the standard process: open a ticket (eService Request –eSR)

Case 2: the responsibility can be established 100% on Application Partner side.

In that case, the problem must be escalated directly to the Application Partner by opening a ticket through the Partner Hotline. In general, the process to be applied for the Application Partner is described in the IWR.

Case 3: the responsibility can not be established.

In that case the following process applies:

The Application Partner shall be contacted first by the Business Partner (responsible for the application, see figure in previous page) for an analysis of the problem.

The Alcatel-Lucent Business Partner will escalate the problem to the Alcatel-Lucent

Support Center only if the Application Partner has demonstrated with traces a problem on the Alcatel-Lucent side or if the Application Partner (not the Business Partner) needs the involvement of Alcatel-Lucent.

In that case, the Alcatel-Lucent Business Partner must provide the reference of the Case Number on the Application Partner side. The Application Partner must provide to Alcatel-Lucent the results of its investigations, traces, etc, related to this Case Number.

Alcatel-Lucent reserves the right to close the case opened on his side if the investigations made on the Application Partner side are insufficient or do not exist.

Note: Known problems or remarks mentioned in the IWR will not be taken into account. For any issue reported by a Business Partner outside the scope of the IWR, Alcatel-Lucent offers the “On Demand Diagnostic” service where Alcatel-Lucent will provide 8 hours assistance against payment . IMPORTANT NOTE 1: The possibility to configure the Alcatel-Lucent PBX with ACTIS quotation tool in order to interwork with an external application is not the guarantee of the availability and the support of the solution. The reference remains the existence of a valid InterWorking Report. Please check the availability of the Inter-Working Report on the AAPP (URL: https://private.applicationpartner.alcatel-lucent.com) or Enterprise Business Portal (Url: Enterprise Business Portal) web sites. IMPORTANT NOTE 2: Involvement of the Alcatel-Lucent Business Partner is mandatory, the access to the Alcatel-Lucent platform (remote access, login/password) being the Business Partner responsibility.

https://private.applicationpartner.alcatel-lucent.com/

https://businessportal.alcatel-lucent.com/alugesdp/faces/gesdp/products/Listing.jspx?DOCTYPE=Technical_Documentation/Interworking_Reports&RESULTSBYPAGE=25&BOXES=partner,product&OPENFOLDER=doctype.Interworking_Reports&_afPfm=2

https://businessportal.alcatel-lucent.com/alugesdp/faces/gesdp/products/Listing.jspx?DOCTYPE=Technical_Documentation/Interworking_Reports&RESULTSBYPAGE=25&BOXES=partner,product&OPENFOLDER=doctype.Interworking_Reports&_afPfm=2



14.3 Escalation in all other cases

These cases can cover following situations:

1. An InterWorking Report exist but is not valid (see Chap Erreur ! Source du renvoi

introuvable. “Validity of an Interworking Report”)

2. The 3

rd party company is referenced as AAPP participant but there is no official

InterWorking Report (no IWR published on the Enterprise Business Portal for Business Partners or on the Alcatel-Lucent Application Partner web site) ,

3. The 3

rd party company is NOT referenced as AAPP participant

In all these cases, Alcatel-Lucent offers the “On Demand Diagnostic” service where Alcatel-Lucent will provide 8 hours assistance against payment.



14.4 Technical support access The Alcatel-Lucent Support Center is open 24 hours a day; 7 days a week:

e-Support from the Application Partner Web site (if registered Alcatel-Lucent Application

Partner): http://applicationpartner.alcatel-lucent.com

e-Support from the Alcatel-Lucent Business Partners Web site (if registered Alcatel-Lucent

Business Partners): https://businessportal.alcatel-lucent.com click under “Let us help you” the

eService Request link

e-mail: [email protected]

Fax number: +33(0)3 69 20 85 85

Telephone numbers:

Alcatel-Lucent Business Partners Support Center for countries:

Country Supported language Toll free number

France

French

+800-00200100

Belgium

Luxembourg

Germany

German Austria

Switzerland

United Kingdom

English

Italy

Australia

Denmark

Ireland

Netherlands

South Africa

Norway

Poland

Sweden

Czech Republic

Estonia

Finland

Greece

Slovakia

Portugal

Spain Spanish

For other countries: English answer: + 1 650 385 2193 French answer: + 1 650 385 2196 German answer: + 1 650 385 2197 Spanish answer: + 1 650 385 2198

END OF DOCUMENT

http://applicationpartner.alcatel-lucent.com/

https://businessportal.alcatel-lucent.com/


alcatel-lucent application partner program inter-working ......the validity of the interworking...

Documents