Alcatel-Lucent Applications Partner Program Inter · PDF file4400/Enterprise, OmniTouch, OmniPCX Office, ...) OmniPCX Office Alcatel-Lucent compatibility release R7.1 / 014.001 Partner’s

Alcatel-Lucent Applications Partner Program – Inter-working report Copyright © 2008 Alcatel, All rights reserved

Edition 1 – Page 1

Alcatel-Lucent Applications Partner Program

Inter-Working Report

Partner: AudioCodes Application type: Analog equipments SIP Gateway

Application name: MP-202

The product and version listed have been tested with the Alcatel-Lucent Communication Server and the version specified hereinafter. The tests concern only the inter-working between the Application Partner product and the Alcatel-Lucent Communication platforms. The inter-working report is valid until the Application Partner issues a new version of such product (incorporating new features or functionality), or until Alcatel-Lucent issues a new version of such Alcatel-Lucent product (incorporating new features or functionality), 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 APPLICATION PARTNER 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 APPLICATION PARTNER OR ANY OTHER PARTY ARISING FROM OR RELATED IN ANY MANNER TO THIS CERTIFICATE.



Tests identification

Date of the tests December 2008

Alcatel’s representative Roland Baumert Partner’s representative

Alcatel-Lucent Communication Platform (OmniPCX 4400/Enterprise, OmniTouch, OmniPCX Office, ...)

OmniPCX Office

Alcatel-Lucent compatibility release R7.1 / 014.001 Partner’s application version R2.6.3_B_3

Environment (if it has a sense) Author(s): R. Baumert Reviewer(s): E.Denis, R.Himmi, D.Lienhart Historic Edition 1: creation of the document - 02-28-2008 Edition 2: update of the document - 01-09-2009

Test results

Passed

Refused Postponed

Passed with restrictions

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

ACD Business



Company Contact Information (Information provided by the partner) Contact name : Bertrand Goldfarb Title : Sales Director Address 1 : 3, Avenue de la Source City : BOUGIVAL Zip : 78380 Country : France Phone : +33 1 39 18 29 57 Fax: +33 1 30 82 20 12 Web address : http://www.audiocodes.com E-mail : [email protected]



TABLE OF CONTENTS

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

1.1 GLOSSARY ........................................................................................................................................... 5

2 APPLICATION INFORMATION ............................................................................................................. 6

3 TESTS ENVIRONMENT ......................................................................................................................... 7

3.1 GENERAL ARCHITECTURE .................................................................................................................... 7

4 SUMMARY OF TEST RESULTS .......................................................................................................... 8

4.1 SUMMARY OF MAIN FUNCTIONS SUPPORTED ........................................................................................ 8 4.2 SUMMARY OF PROBLEMS ..................................................................................................................... 8 4.3 SUMMARY OF LIMITATIONS .................................................................................................................. 8 4.4 CORRECTED PROBLEMS ....................................................................................................................... 8 4.5 REMARKS ............................................................................................................................................ 8

5 TEST SCENARIOS.................................................................................................................................. 9

5.1 TEST PROCEDURE ................................................................................................................................ 9 5.2 RESULT TEMPLATE............................................................................................................................... 9

6 TESTING................................................................................................................................................. 10

6.1 CONFIGURATIONS ASPECTS ................................................................................................................ 10 6.1.1 Objective ................................................................................................................................... 10

6.2 SET-UP AND ACCEPTANCE TESTS........................................................................................................ 11 6.2.1 Test objectives ........................................................................................................................... 11 6.2.2 Test procedure .......................................................................................................................... 11

6.3 FAX .................................................................................................................................................. 12 6.3.1 Test objectives ........................................................................................................................... 12

6.4 DEFENCE AND PERTURBATION ........................................................................................................... 12 6.4.1 Test objectives ........................................................................................................................... 12

6.5 MEDIA SPECIFICATION ....................................................................................................................... 13 6.5.1 Test objectives ........................................................................................................................... 13

6.6 BASIC CALLS ..................................................................................................................................... 14 6.6.1 Test objectives ........................................................................................................................... 14 6.6.2 Test procedure .......................................................................................................................... 14

6.7 TELEPHONIC SERVICES....................................................................................................................... 15

7 APPENDIX A: TESTDIRECTOR TEST LIST ................................................................................... 17

8 APPENDIX B : APPLICATION DESCRIPTION............................................................................... 20

9 APPENDIX C: ALCATEL COMMUNICATION PLATFORM: CONFIGURATION REQUIREMENTS.......................................................................................................................................... 22

10 APPENDIX D: PARTNER ESCALATION PROCESS .................................................................. 23

11 APPENDIX E: AAPP PROGRAM, DOCUMENTATION AND TECHNICAL ASSISTANCE. 24

12 APPENDIX F: ALCATEL-LUCENT ESCALATION PROCESS IN CASE OF PROBLEM WITH A CERTIFIED EXTERNAL APPLICATION (REFERENCED IN THE AAPP) ....................... 28



1 Introduction The goal of these tests is to qualify an external application as an Alcatel-Lucent Applications Partner Program solution for the Alcatel-Lucent Communication Platform. The scope of the tests is the interoperability of the application with the Alcatel-Lucent Communication Platform. It covers a basic or complex inter-working to ensure that services requested by the application and provided by the Communication Platform (and/or conversely) are properly completed. These tests do not verify the functional achievement of the application as well as they do not cover load capacity checks, race conditions and generally speaking any real customer's site conditions. The objective of these tests was mainly to validate the interworking with Fax machines in T38 mode connected behind AudioCodes MP202 gateway that uses SIP protocol to work with OXO PBX R7.1. Also to check basic voice calls using analog sets behind the gateway.

1.1 Glossary MF : Multifrequency numbering

SIP : Session Initiation Protocol

CLIP : Calling Line Identification Presentation

CLIR : Calling Line Identification Restriction

IP: Internet Protocol

VoIP: Voice over IP

FoIP: Fax over IP

RTP: Real –time Transport Protocol

PSTN: Public switched telephone network

T.38: ITU standard for sending FAX across IP networks in a real-time mode



2 Application information Application type : IP gateway Application commercial name : AudioCodes MP202 Application version : R2.6.3_B_3 Interface type : SIP Brief application description :

The MP-202 is a 2-line SIP gateway allowing analog sets or Fax to access IP based telephonic networks using SIP protocol.

This equipment allows in our business context a remote connectivity for such equipments working logically as “local” equipments for the PBXs via the IP/Internet world.

The MP-202 provides main telephony features, including Caller ID, Call waiting, Call forward, Call transfer, 3-way conference and Fax connection using T38. Only Fax communication checks were concerned by this test campaign so as Basic (simple calls) telephonic feature.

The MP202 also serves as a router supporting NAT, DHCP, PPPoE, PPTP, Firewall functions. The current campaign did not take these features in account.

The tests are done using an OmniPCX Office with a Private SIP connectivity to the AC-MP202 gateway.



3 Tests environment

3.1 General architecture

Figure 1 Global architecture

Tests Objectives: The objective of the tests was mainly to use one OXO node and one AudioCodes gateway playing with it’s analog Set/Fax trough the Private SIP Trunking connectivity to OXO, also to test Break-in and out with equipments behind Public ISDN Network. Telephonic Voice features have also been tested for basic telephony features, complex telephonic features are not supported by OXO. Used Releases: AudioCodes MP202: R2.6.3_B_3 OXO PBX: R7.1_014.001

FaxFaxFaxFaxOXOPABX

LANLANLANLAN

FaxFaxFaxFax

PSTN

LANLANLANLAN

Fax

G711G711G711G711PrivateSIP

AudioCodesMP 202

SIP Gateway

ISDN FaxFaxFaxFaxFaxFaxFaxFaxOXOPABX

LANLANLANLAN

FaxFaxFaxFaxFaxFaxFaxFax

PSTN

LANLANLANLAN

Fax

G711G711G711G711PrivateSIP

AudioCodesMP 202

SIP Gateway

ISDN



4 Summary of test results

4.1 Summary of main functions supported The main supported functions implied in the test campaign are:

• Installation and configuration of the AC-MP202 gateway • Compatibility with OXO SIP Private Trunking • Basic communications (internal and external) • Check telephonic features (Basic Call only) • Supports all kind of numbering Abbreviated Number, internal and external numbers) • DDI number can be used for the AC Analog equipments, for incoming calls. • Access to the OXO Voice mail boxes and MF dialing for within navigation • Multi Frequency sending in conversation/connected state, also on ISDN • Different kind of Codec compressions can be used: G711, G729. • Fax G3 and SuperG3 Check.

4.2 Summary of problems • none

4.3 Summary of limitations

•

In case of Waiting /Queued to an AC set, the waiting OXO set hears no waiting tone .

-> this may be an OXO limitation/problem. • Forward on Busy set doesn’t work . This is an already known MP202 problem.

-> This is an AudioCodes problem. • CLIP problem : Calling an AudioCodes set, the identity is not displayed to the caller

OXO set. -> This is an AudioCodes problem.

4.4 Corrected problems • Waiting on a current Fax communication: the current FAX communication is

perturbated so it goes to be incomplete. -> This was an AudioCodes problem in R2.4.2_P11_build5 that has been corrected

in release 2.6.3

4.5 Remarks

• For FAX T38 communications, the Modem parameter has to be set to “VoiceBandData” to be working. The supported AC equipments features are Waiting and Forward

Note that this configuration is defined for the both equipments. The forward feature has to be activated/released by the equipments theirselves.



5 Test Scenarios

5.1 Test procedure Step Action N/A Result Origin of the problem Comment Step : a test may comprise multiple steps depending on its complexity. Each step has to be completed successfully in order to conform to the test. Step 0 when present represents the initial state for all the following steps. Action : describes which action to realize in order to set-up the conditions of the test. N/A: the step within this test is not applicable to this application. This has to be filled in only if the test is checked as mandatory in the applicability box. In that case, the column comment must indicate the reason of the non-applicability (e.g.: service not supported). Result : describes the result of the test from an external point of view. If it is positive, it describes which application's trigger was checked. If it is negative, it describes as precisely as possible the problem. Origin of the problem : this column has to be filled in when a problem occurs during the test. It must contain a high level evaluation of the localization of the responsibility: Alcatel-Lucent or the Partner. �� it is not intended during this test session to debu g and fix problems .

5.2 Result template The results table must be formatted as indicated in the example below: Step Action N/A Result Origin of the

problem Comment

1 . action 1 OK 2 . action 2

OK

The application waits for PBX timer or phone set hangs up

3 . action 3 OK 4 . action 4

X

Relevant only if the CTI

interface is a direct CSTA

link 5 . action 5

NOK No indication,

no error message

… …

�� it is not intended in this session to mention any A nomaly Report (the anomaly report will be mentioned in Paragraph 8 & A ppendix A).



6 Testing Convention: In the following chapters:

• AC may be used in place of “AudioCodes ” • The Analog equipments connected to the AudioCodes gateway may be named “AC set ” or

“AC set1”, “SG set2”, or “AC fax ” for a Fax machine. • “OXO Fax” is a directly connected Fax to the OXO PBX using an analog connectivity.

6.1 Configurations aspects

6.1.1 Objective This chapter gives principle information on configuration aspects and summaries the minimum well configurations on OXO and AudioCodes sides to be able for the AC sets to work well and easily for the EndUser. Configuration details examples are given in the Annexes. OXO Aspects: The VoIP feature is subject to Licenses. To configure analog set or Fax to be working behind the AudioCodes gateway, a VoIP Trunk and Access have to be configured and trunk channels to be defined. The ARS (Automatic Routing Selection) mechanism is used to access to such sets. This implies the Internal Numbering Plan configuration for the AudioCodes equipments Directory Numbers declared with use of “ARS” function. An ARS Prefix has to be defined for the Dialing numbers range, Prefix, Gateway address, Protocol and Codec configurations. Private configuration of the ARS entry is used in this topology. The Private Numbering Plan is used and has to be configured for the numbers the AudioCodes equipments will have to dial to, and through, OXO. Barring and Link category rights have to be checked to allow the connectivity between the SIP end equipments and the trunk they use, and the other sets or trunks of the PABX installation. The End of Numbering policy may be adapted for trunk connectivity dialings. Transfer from External to External may be set in the System Particularities configuration.



6.2 Set-up and acceptance tests

6.2.1 Test objectives Check the installations and configuration aspects to bring the platform working. Check the acceptance through simple incoming and outgoing calls

6.2.2 Test procedure Step Action N/A Result Origin of the

problem Comment

1 OXO configuration checks for SIP trunk and AudioCodes gateway configuration

OK

1 Configuration with SIP Option mechanism

OK

1 Simple call between OXO and AC OK

1 Release before answering OK 1 Calling Line Presentation to

the analog AC set in incoming ringing phase OK

OK by Default with Belgacom

set Not for ETSI

sets For the Anomaly points, see chapter 4 the corresponding problem/limitation descriptions and chapter 8 the anomalies summary.



6.3 FAX

6.3.1 Test objectives

• Fax transmission in T.38 mode with G3 and Super G3 fax machines • Fax In waiting situation • Fax forwarding

Step Action N/A Result Origin of the

problem Comment

1 Simple G3 fax transmission

OK

1 Super G3 fax transmission OK 1 Transmission of

multiple/complex sheets (6) OK

1 Call a Busy Fax , both ways OK 1 Waiting on AC Fax on a

current fax comm OK AudioCodes AC Anomaly corrected in

R2.6.3 1 Call an AC Forwarded Fax OK 1 Call an AC Fax through

ISDN Break-in in T38 OK

1 Call an AC Fax through ISDN Break-out in T38 OK

1 Redundancy Check OXO and AC with values 0 to 2

OK

For the Anomaly points, see chapter 4 the corresponding problem/limitation descriptions and chapter 8 the anomalies summary.

6.4 Defence and perturbation

6.4.1 Test objectives

• Check the behaviour in case of perturbation

Step Action N/A Result Origin of the problem

Comment

1 SIP out of order

OK

1 Trunk busy OK 1 Trunk not available OK 1 IP link failure OK For the Anomaly points, see chapter 4 the corresponding problem/limitation descriptions and chapter 8 the anomalies summary.



6.5 Media Specification

6.5.1 Test objectives Check the different cases of negotiation regarding the communication establishment and the impact of some configuration parameters

• Codec

• Framing

• Signalling TCP / UDP

Step Action N/A Result Origin of the problem

Comment

1 Codec Negotiation

OK

1 Framing Use Case of different packet size for voice ( 20ms, 30ms, 40ms … )

OK

1 Signaling TCP-UDP SIP Signaling only transmitted in UDP mode by OXO

OK

For the Anomaly points, see chapter 4 the corresponding problem/limitation descriptions and chapter 8 the anomalies summary.



6.6 Basic Calls

6.6.1 Test objectives Check the difference cases of simple incoming and outgoing call. During the call, some points are checked :

• tones

• display before and after the conversation

• release the called / calling party at first

• type of the device : analog set, ua set ( 4035 ), IP Phone ( 4038/ 4068 )

• CLIP / CLIR

• Call back

6.6.2 Test procedure Step Action N/A Result Origin of the

problem Comment

1 Basic call OK

1 Release before answer

OK

1 Basic call with Authentication

x

1 Call an unregistered set and busy set both ways OK but limitation if

OXO set waiting OXO

No tone is given to the OXO waiting

caller

1 OXO set in Do not disturb OK OK

1 PSTN break-in call PSTN incoming call to an AC set

OK

1 PSTN break-out call Call from an AC set to an external PSTN party

OK

1 Call with attendant / both ways The second party is an attendant

OK

1 Calling Line Presentation to the analog AC set in incoming ringing phase / OXO set caller

OK

OK With Belgacom by

default, not for ETSI sets



1 Calling Line Presentation to the analog AC set in incoming ringing phase / RNIS caller through OXO OXO PABX (Break In)

OK

1 CLIP Check the display

NOK

Is an Interworking

Limitation: is an AC problem

No CLIP when an OXO set

calls an AC set // OK in the other way

1 CLIR Check the display with / without Identity secret / Internal called / ISDN called

OK But OXO

Problem for break out to ISDN / CLIR from Gateway not supported

by OXO

6.7 Telephonic services Check the features available in local mode and during the conversation.

� The supported AC equipments features are Waiting/Ringing, Waiting/Queued and Forward. Note that this configuration is defined for the both equipments. The forward feature has to be activated/released by the equipment it self.

� AC equipments can activate Broker Call so as call evolutions lying on this feature, but such call evolutions are not supported by OXO, so these features have not been well tested..

Step Action N/A Result Origin of the

problem Comment

1 OXO set calls a Busy AC set (without waiting) OK

1 OXO set calls a Busy AC set with waiting OK

1 OXO set calls a AC Forwarded set to another OXO set

OK

1 OXO set calls an AC Forwarded set to ISDN N* through OXO PBX

NOK OXO Anomaly crms00104805

1 ISDN incoming call to a AC Forwarded set to an OXO set

OK

1 AC set calls a Forwarded OXO set to the Voice mail OK

2 AC set sends DTMF to the OXO Voice Mail and navigate within

OK CLIP OK =>

call back from VM possible

1 AC set sends DTMF to an ISDN destination OK

1 MF In Band mode OK



1 MF in RFC 2833 mode

OK



7 Appendix A: TestDirector test list

This appendix will give an extract of Test-director with the campaigns related to the test report, the list of the tests_name, their level and their status (Failed, Passed, NoRun, Postponed, NotCompleted).

This extract must list the following Test-Director fields per Test-Director campaign in test-lab :



Plan: Test Name Plan: Description Plan: Level Status C_04_03_ACC_001_foip_OXO-framing-redondance

A fax is sending through the SIP trunk with different framing and redundancy values

Mandatory Passed

C_04_01_ACC_008_foip_gen -- Fax local forwarding

A fax on system A is forwarded to another fax machine on system A. A fax of System B sends then a fax to the forwarded fax machine on System A. We aim at checking the good reception of the fax.

Recommended

Passed

C_04_01_ACC_011_foip_gen -- Fax sending to busy fax machine

A fax is sent from a System A fax machine A to a System B faxB which is already busy. The goal of the test is to check that the behavior on calling and called fax machines is OK.

Recommended

Passed

C_09_01_ACC_002_foip_gen -- trunk - private

A fax is sending between 2 systems connected through a Sip trunk

Mandatory Passed

C_09_01_ACC_003_foip_gen -- trunk - multi-fax

Some faxes are sending between 2 systems connected with a Sip trunk. Faxlab tool is used to simulate different type of faxes

Mandatory Passed

C_09_01_ACC_004_foip_gen -- trunk - private_PSTN break-in

A fax is sending from PSTN between 2 systems connected through a Sip trunk

Mandatory Passed

C_09_01_ACC_005_foip_gen -- trunk - private_PSTN break-out

A fax is sending on PSTN between 2 systems connected through a Sip trunk.

Mandatory Passed

C_09_01_ACC_008_foip_gen -- immediate forwarding over IP_2 ways

Objective : ========= A setA on System A is diverted to a systemB setB through an IP link. A setB of system B then calls the diverted set on System A over IP. Objective is to check the right functionning of diversion.

Mandatory Passed

C_09_01_PERF_002_foip_gen -- trunk - long and complex fax

A complex multi pages fax including images is sent through Trunk IP by using the T.38 protocol

Mandatory Passed

C_09_01_PERT_003_foip_gen -- Trunk--busy Set

The aim of this test is to see the behavior of a fax call through a SIP trunk when the called fax is busy

Mandatory Passed

180 - codec-framing - G.729

Use the IP analyser.

Mandatory Passed

181 - codec-framing - G.711

Use the IP analyser.

Mandatory Passed

E_10_50_ACC_001_foip_fax call in G711- Transparant FAX

A fax is sending through the AudioCodes box with the protocol G711.

Mandatory N/A

C_09_01_ACC_001x1_foip_gen --super G3 trunk - public

A fax is sending between 2 systems connected through a Sip trunk FAX machines are of type super G3

Mandatory Passed

A_13_01_007_SIP-ICMP Keep Alive

SIP-ICMP Keep Alive check.

Mandatory Passed



Plan: Test Name Plan: Description Plan: Level Status A_13_01_008_SIP-SIP Option Keep Alive

SIP-SIP Option Keep Alive check.

Mandatory Passed

E_10_50_ACC_002_foip_Queued T38 Fax

Waiting feature is configured on the AudioCodes gateway for sets or Fax. A T38 Fax waits on a current Fax communication release.

Supplementary

Failed

B_08_01_PERT_010_sip_gen -- out of order SIP set

A set makes a call with a SIP set "out of order" Recommended

Passed

B_08_01_ACC_020x1_voip_gen -- internal no-reply and busy forwarding

A SIP set is forwarded to another extension on the same System. Forwarding mode: forwarding on no reply forwarding on busy An other set calls the SIP forwarded set.

Recommended

Failed



8 Appendix B : Application description The AudioCodes MP-202 is a Telephone Adapter which allows the connection of ordinary analog phones or fax machines to a Voice over IP networks using SIP protocol. The MP-202 product combines superior voice quality and cutting-edge features for end users, such as T.38 Fax Relay and G.168-2004 compliant Echo Cancellation. Low bit rate vocoders (voice coders) can be used simultaneously on all the telephony ports to save valuable bandwidth. MP202 SIP Configuration:



MP202 Line Configuration:

MP202 Fax Configuration:



9 Appendix C: Alcatel Communication Platform: configuration requirements

OXO PBX ARS Configuration:

Calling and Called attribute in private mode

Trunk Voip is declared as a private trunk



10 Appendix D: Partner escalation process In case you would need technical assistance, please contact the reseller/distributor where you purchased your AudioCodes products. They have been trained on the products to give you 1st and 2nd levels of support. They are in plus in direct relation with 3rd level AudioCodes support in case an escalation would be needed



11 Appendix E: AAPP program, documentation and technical assistance

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

• Provide easy interfacing for Alcatel-Lucent communi cation 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-part y 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 Applications, come from every area of voice and data communications.

The Alcatel-Lucent Applications 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, … Web site If registered Alcatel-Lucent Application Partners, you can access the AAPP website at this URL: http://www.applicationpartner.alcatel-Lucent.com/

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



Alcatel-Lucent documentation Alcatel-Lucent Applications Partner Program (AAPP) If registered Alcatel-Lucent Application Partners, you can access the current AAPP documentation at this URL: http://www.applicationpartner.alcatel-lucent.com/ and then click the Partner Center link. Alcatel-Lucent Business Partner Program (ABPP) The Alcatel-Lucent Business Partner Program is designed to empower and maximize the business of the Partners. In addition, it enables them to help their customers successfully maximize their telecom investment through optimum deployment and proper configuration of Alcatel-Lucent's solutions. Alcatel-Lucent Partners also receive the added benefit of rapid, highly qualified service and support as well as world class training. Alcatel-Lucent will work closely with Business Partners to provide top quality design, delivery, and support of the very best solutions for your customers. The Business Partner Program is designed around a flexible and scalable framework so each Partner can identify the exact support they need. So, depending on your specific requirements you can quickly become a 'Certified', 'Expert' or 'Premium' Business Partner with one of the world leaders in the communications industry. If registered Alcatel-Lucent Business Partners, you can access to an exciting on-line resource centre with a wealth of information on all product lines at this URL: http://www.businesspartner.Alcatel-Lucent.com



Technical assistance In order to guide you in your purchasing decisions and provide you with assistance for updating our Communication Server and Networking Infrastructure products and for commercial development, Alcatel-Lucent has created the SUPPORT CENTER. The SUPPORT CENTER is responsible for the management and routing of all your requests. It includes e-Support and a Contact Centre reserved for registered Alcatel-Lucent Application Partners and Alcatel-Lucent Business Partners. The Contact Centre is open 24 hours a day; 7 days a week and is available in 5 languages. This Call Centre has a team of 15 people and handles 10; 000 requests per month.

• e-Support from the Alcatel-Lucent Application Partners Web site (if registered Alcatel-Lucent Application Partners): http://www.applicationpartner.alcatel-lucent.com/ click the Partner Center link and then Support

• e-Support from the Alcatel-Lucent Business Partners Web site (if registered Alcatel-Lucent Business Partners): http://www.businesspartner.Alcatel-Lucent.com click the e-Support link and then e-Service Request

• e-mail: [email protected] • Fax number: +33 (0) 3 90 67 73 45 • Telephone numbers:

Alcatel-Lucent Business Partners Contact Center: France : 0 811 900 110 French agent Austria : 0 810 810 012 German agent Denmark : 70 11 21 09 English agent Germany : 0 1 803 000 680 German agent Ireland : 1 890 925 039 English agent Italy : 848 800 389 Italian agent UK : 0 845 601 4101 English agent Spain : 901 120 085 Spanish agent Switzerland : 0 844 850 588 German agent For other countries: English answer : + 33 (0)3 88 55 69 04 French answer : + 33 (0)3 88 55 69 02



Alcatel-Lucent training Technological innovative cycles are quickening and your customers are more and more demanding regarding the quality of services. In order to meet these requirements, you have to invest in skills: a key success factor for services. If registered Alcatel-Lucent Business Partners, you can access to the training part at this URL: http://www.businesspartner.Alcatel-Lucent.com and then click the Training link. Our vision of learning services is described in the Services Portfolio section . The Certification section gives you some statistics and details on how training curricula are designed to match certification levels. All updated training curricula and assessment tools are available in the Curricula & Catalogues section . The Schedule section is regularly updated to show forthcoming training sessions over the world. The How to Enrol section provides you with the registration procedure and the Alcatel-Lucent University Customer Service list of contacts world wide. Last but not least, find statistics and reports of what you think about our training services in the Customer Satisfaction section . The Alcatel-Lucent commitment : enabling you to opt imise your training investments.



12 Appendix F: Alcatel-Lucent escalation process in case of problem with a certified external application (referenced in the AAPP)

Introduction The purpose of this document is to define the split of responsibilities and the escalation process to be applied by the Business Partners when facing a problem with a solution involving an Alcatel-Lucent platform and an external application with a valid Alcatel-Lucent Inter-working report. As for other Alcatel-Lucent equipment, the Alcatel-Lucent business partner is the only one facing the end-customer for support or maintenance. The Business partner will open cases (service request) either on Alcatel-Lucent side or on Application Partner side depending on the nature of the issue. Expert from both companies will collaborate to provide the best and quickest correction.

Partner’s

answers

CustomerBusiness Partner

Application Partner Support

TechnicalIssues

Alcatel Technical Support

SR

SR = Service Request

SR

Answer

Answer

Experts Exchanges

In cases of the problem has not been sent to the right organization: “Please open a SR into our partner database by mentioning our SR number”

Partner’s

answers

CustomerBusiness Partner

Application Partner SupportApplication Partner Support

TechnicalIssues

Alcatel Technical SupportAlcatel Technical Support

SR

SR = Service Request

SR

Answer

Answer

Experts Exchanges

In cases of the problem has not been sent to the right organization: “Please open a SR into our partner database by mentioning our SR number”



General Rules The following general rules are applied:

• Only certified AAPP applications are officially sup ported by Alcatel-Lucent

• The certification is based on tests suite passed by Alcatel-Lucent and the Application Partner and the result is consigned in to an Inter-Working Report (IWR) validated by the two parties.

• The IWR is available on the AAPP Web site.

• Only the major releases of both parties are certified. Certification tests are usually not

performed for intermediate versions. Only the existence of the IWR in the AAPP Web site for the right Alcatel-Lucent release is the guarantee that the application has been certified with this Alcatel-Lucent release.

• If the IWR for the Alcatel-Lucent release is not available, Alcatel-Lucent doesn’t engage

any responsibility. In that case, please contact the central Pre-Sales team.

• The existence of the IWR engages Alcatel-Lucent and the Application Partner . Both

parties are engaged, not exclusively Alcatel-Lucent (see the section escalation process).

Warning:

The possibility to configure the Alcatel-Lucent PBX with ACTIS quotation tool in order to interwork with an external application, is not a guarantee of the availability of the solution. Please check the availability of the Inter-Working Report on AAPP web site.



The escalation process As stated above, the Alcatel-Lucent support will be limited to applications with a valid inter-working report. Known problems or remarks mentioned in the IWR will not be taken into account. In case of problem, the two 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 Business Partner to the Alcatel-Lucent Hot-line via the standard process: open a ticket (Service Request –SR)

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

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

� Case 3 : the responsibility can not be established

In that case the following process applies:

1) The Application Partner shall be contacted first b y the Business Partner or the party responsible for that Application for an analysis of the problem. Alcatel-Lucent has to be involved solely if the application partner demonstrate, with traces, after reproduction of the problem, that the defect which has generated the end-user’s demand of support is coming from the equipment provided by Alcatel-Lucent or if he needs support of Alcatel-Lucent. 2) The Business partner will escalate the problem to the Alcatel-Lucent Hot-line if the Application Partner has demonstrated a problem on Alcatel-Lucent side or if the Application Partner (not the Business Partner) needs the involvement of Alcatel-Lucent. In that case, the Business Partner must provide the reference o f the Case Number on 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 Application Partner side are insufficient or do no exist.

Note: Involvement of the Business Partner is mandatory because the access to the Alcatel-Lucent Platform (remote access, login/password) is under the Business Partner responsibility.

Documents

Alcatel-Lucent Applications Partner Program Inter · PDF file4400/Enterprise, OmniTouch, OmniPCX Office, ...) OmniPCX Office Alcatel-Lucent compatibility release R7.1 / 014.001 Partner’s