Alcatel-Lucent Application Partner Program Inter-Working Report

Transcription

1 Alcatel-Lucent Application Partner Program Inter-Working Report Partner: Sagemcom Canada Inc. Application type: Fax Server Application name: XMediusFAX Alcatel-Lucent Enterprise Platform: OmniPCx Enterprise The product and release listed have been tested with the Alcatel-Lucent Enterprise Communication Platform and the release specified hereinafter. The tests concern only the inter-working between the AAPP member s product and the Alcatel-Lucent Enterprise 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 ALE International issues a new major release of such Alcatel-Lucent Enterprise product (incorporating new features or functionalities), whichever first occurs. ALE INTERNATIONAL MAKES NO REPRESENTATIONS, WARRANTIES OR CONDITIONS WITH RESPECT TO THE APPLICATION PARTNER PRODUCT. WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, ALE INTERNATIONAL 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 ALE INTERNATIONAL FURTHER SHALL HAVE NO LIABILITY TO AAPP MEMBER OR ANY OTHER PARTY ARISING FROM OR RELATED IN ANY MANNER TO THIS CERTIFICATE. Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 1/51

2 Certification overview Date of the certification 2015/02/ /04/10 ALE International representative AAPP member representative Alcatel-Lucent Enterprise Communication Platform Alcatel-Lucent Enterprise Communication Platform release AAPP member application release Application Category Denis Lienhart Daniel Narloch Simon Yee Jie Ming Du OmniPCX Enterprise OXE R11.1 (l f-us-c80s1) XMEDIUSFAX Hotfix Hotfix Fax server Author(s): Reviewer(s): Jie Ming Du Dennis Lienhart, Daniel Narloch, Simon Yee Revision History Edition 1 10 April 2015 Initial test results by Jie Ming Du Sagemcom Canada Inc. Edition 2 10 August Removed item from report. Fixed XMF issue TT# The FoIP driver may crash during a G.711/V.34 call as a result of memory corruption on XMF. FoipDriver version Updated/corrections on numbering on session 6.1. Modified the notes on session scenario 4. Regression test result in Test results Passed Refused Postponed Passed with restrictions (due to existing issues with G711 Passthrough it is not recommended to use this feature) Refer to the section 6 for a summary of the test results. IWR validity extension None Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 2/51

3 AAPP Member Contact Information Contact name: Title: Contact name: Title: Contact name: Title: Jie Ming Du Software Test Specialist Daniel Narloch Software Test Manager Simon Yee Interoperability/Certification Program Manager Address 1: 3400 de Maisonneuve Blvd. West, Suite 1135 PO BOX 48 City: Montreal State: Quebec Zip: H3Z 3B8 Country: Canada Country code: 1 Phone: Fax: Web address: Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 3/51

4 TABLE OF CONTENTS 1 INTRODUCTION VALIDITY OF THE INTERWORKING REPORT LIMITS OF THE TECHNICAL SUPPORT CASE OF ADDITIONAL THIRD PARTY APPLICATIONS APPLICATION INFORMATION TESTS ENVIRONMENT GENERAL ARCHITECTURE Basic Test Environment User Scenarios Test Environment HARDWARE CONFIGURATION SOFTWARE CONFIGURATION SUMMARY OF TEST RESULTS SUMMARY OF MAIN FUNCTIONS SUPPORTED SUMMARY OF PROBLEMS SUMMARY OF LIMITATIONS NOTES & REMARKS TEST SCENARIOS TEST PROCEDURE RESULT TEMPLATE TESTING BASIC SIGNALLING COMPATIBILITY Test objectives Required Basic SIP_UDP Required Basic SIP_TCP THOROUGH T.30 AND T.38 COMPATIBILITY Test objectives Required G3 Documents SIP_UDP Required G3 Documents SIP_TCP Optional Error Correction Mode (ECM) SIP_TCP Optional G4 Documents SIP_TCP Optional SIP_TCP CODEC (CNG) Test objectives Required Codec (CNG) SIP_UDP Required Codec (CNG) SIP_TCP ERROR HANDLING Test objectives Required Error Handling SIP_UDP Required Error Handling SIP_TCP Optional Error Handling SIP_TCP STABILITY Test objectives Required Load Tests SIP_UDP Required Load Tests SIP_TCP USER SCENARIOS Test objectives User Scenarios ADDITIONAL TESTS TEST CASES DETAILS Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 4/51

5 8.8.1 Required Tests Optional Tests User Cases Additional tests (Alcatel) APPENDIX A : AAPP MEMBER S APPLICATION DESCRIPTION APPENDIX B: CONFIGURATION REQUIREMENTS OF THE AAPP MEMBER S APPLICATION PORTS FOR SIP PEER FOR SIP_UDP: PEER FOR SIP_TCP: SIP SECURITY FOR AUTHENTICATION FAX OPTIONS OF USER PROFILE APPENDIX C: ALCATEL-LUCENT ENTERPRISE COMMUNICATION PLATFORM: CONFIGURATION REQUIREMENTS SIP TRUNK DECLARATION DIALLING PLAN SETUP EXT SIP GATEWAY DECLARATION EXT SIP GATEWAY CONFIGURATION FOR AUTHENTICATION CONFIGURATION FOR SPATIAL REDUNDANCY APPENDIX D: AAPP MEMBER S ESCALATION PROCESS APPENDIX E: AAPP PROGRAM ALCATEL-LUCENT APPLICATION PARTNER PROGRAM (AAPP) ENTERPRISE.ALCATEL-LUCENT.COM APPENDIX F: AAPP ESCALATION PROCESS INTRODUCTION ESCALATION IN CASE OF A VALID INTER-WORKING REPORT ESCALATION IN ALL OTHER CASES TECHNICAL SUPPORT ACCESS Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 5/51

6 1 Introduction This document is the result of the certification tests performed between the AAPP member s application and Alcatel-Lucent Enterprise 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, ALE International 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 ( in the Application Partner Interworking Reports corner (restricted to Business Partners) - the Application Partner portal ( with free access. This document describes the series of tests that certify that Alcatel OXE Gateway is XMediusFAX compatible and that they work together. The tests verify the following: Basic signalling compatibility Thorough T.30 and T.38 compatibility Codec (CNG) Error handling Stability User scenarios Additional tests (Alcatel test plan) The process of certification needs to be redone if the T.38 interface between the FoIP Server and the VoIP Gateway is modified or if any major change is done in the T.38 module. Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 6/51

7 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 ALE International issues a new major release of such Alcatel-Lucent Enterprise 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. Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 7/51

8 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 ALE International For any request outside the scope of this IWR, ALE International 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 ALE International is included in the solution between the certified Alcatel-Lucent Enterprise and AAPP member products such as a Session Border Controller or a firewall for example, ALE International will consider that situation as to that where no IWR exists. ALE International will handle this situation accordingly (for more details, please refer to Appendix F AAPP Escalation Process ). Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 8/51

9 4 Application information Application type: Application commercial name: Fax over IP (FoIP) fax server software XMediusFAX SP Application version: Release Hotfix HotFix Interface type: T.38/G.711 Passthrough; T.38 with Fallback to G.711 on SIP_UDP/SIP_TCP Interface version (if relevant): N/A Brief application description: XMediusFAX SP is the first board less and multi-tenant Fax over IP (FoIP) fax server software. Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 9/51

10 5 Tests environment 5.1 General architecture The tests are performed on the Alcatel-Lucent TSS Applications International platform in the following environment: Basic Test Environment Figure 1 Basic Test Environment Scenario 1 Loopback Local Network PSTN Line PSTN XMediusFax OXE Scenario 2 Fax Terminal Local Network PSTN Line PSTN XMediusFax OXE Fax Terminal Fax Lab In both configurations, XMediusFAX (FoIP Server), will use the VoIP Gateway as it s primary OXE Gateway. All Outbound calls will use the OXE Gateway and all Inbound calls reaching the OXE Gateway will be routed back to the FoIP Server. Scenario 1 Loopback : In this configurations, the FoIP Server will dial a number which will be routed through the PSTN and back into the OXE Gateway. One call will take 2 channels. Scenario 2 Fax Terminal: The FoIP Server will dial a number which is routed externally to another location other than itself. One call will take 1 channel. Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 10/51

11 5.1.2 User Scenarios Test Environment Figure 3. User Scenarios Test Environment OXE R11.1-l f 2 XMediusFAX Rel Hotfix LAN T1 3 FAX 4 ANALOG 5 6 Scenario # OXE Scenario: 1 OXE Scenario: 2 OXE Scenario: 3 OXE Scenario: 4 OXE Scenario: 5 OXE Scenario: 6 FAX Description SIP : Loopback in OXE SIP : To PSTN through T1 SIP : From PSTN through T1 SIP : Loopback on PSTN through T1 SIP : To Analog device plugged in OXE SIP : From Analog device plugged in OXE Alcatel-Lucent Communication Platform: Name: OmniPCX Enterprise Version: R11.1-l f-us-c80s1 Client Application Platform: Name: XMediusFAX Version: Release Hotfix HotFix Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 11/51

12 5.2 Hardware configuration Alcatel-Lucent Communication Platform: Large Rack Common Hardware Media Gateway (CPU5; GD3, GA3, MG-PRA T1, MG-UAI 16, MG-SLI 16, MG-APA 4) Application Platform: Dell Optiplex 755 (Intel Quard Core CPU/3GB RAM) 5.3 Software configuration Alcatel-Lucent Communication Platform: OmniPCX Enterprise R11.1 Application platform: Windows 2008 R2 Standard English x64 Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 12/51

13 6 Summary of test results 6.1 Summary of main functions supported SIP_UDP - Basic signalling compatibility Required Basic - Section T.38 - PASS G.711 Passthrough - PASS (see 6.2.1b) T.38 with Fallback to G PASS SIP_TCP - Basic signalling compatibility Required Basic - Section T.38 - PASS G.711 Passthrough - PASS T.38 with Fallback to G PASS SIP_UDP thorough T.30 and T.38 compatibility Required G3 Documents Section T.38 - PASS G.711 Passthrough - PASS (see 6.2.1b) T.38 with Fallback to G PASS (see 6.2.1b) SIP_TCP thorough T.30 and T.38 compatibility Required G3 Documents Section T.38 - PASS G.711 Passthrough - PASS (see 6.2.1b) T.38 with Fallback to G PASS (see 6.2.1b) Optional Error Correction Mode (ECM) Section T.38 - PASS G.711 Passthrough - PASS Optional G4 Documents Section T.38 - PASS G.711 Passthrough - PASS T.38 with Fallback to G PASS Optional SIP Section T.38 - PASS G.711 Passthrough - PASS SIP_UDP Codec (CNG) Required - Section T.38 - PASS SIP_TCP Codec (CNG) Required Section T.38 - PASS Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 13/51

14 SIP_UDP - Error handling Required Error Handling - Section T.38 - PASS G.711 Passthrough - PASS SIP_TCP - Error handling Required Error Handling - Section T.38 - PASS G.711 Passthrough - PASS Optional Error Handling - Section T.38 - PASS G.711 Passthrough - PASS SIP_UDP - Stability Required Load Tests - Section T.38 - PASS G.711 Passthrough - FAIL (High failure rate, see 6.2.1a) SIP_TCP - Stability Required Load Tests - Section T.38 - PASS G.711 Passthrough - FAIL (High failure rate, see 6.2.1a) User scenarios Scenario 1 UDP/T.38 UDP/G.711/V.34 TCP/T.38 TCP/G.711/V.34 Scenario 2 UDP/G.711/V.34 TCP/T.38 Scenario 3 UDP/G.711/V.34 TCP/T.38 Scenario 4 UDP/T.38 UDP/G.711/V.34 TCP/T.38 TCP/G.711/V.34 - PASS - PASS - PASS - PASS - FAIL (High failure rate, see 6.2.1a) - PASS - PASS - PASS - PASS - FAIL (regression with High failure rate, See 6.2.1a) - PASS - FAIL (High failure rate, see 6.2.1a) Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 14/51

15 Scenario 5 UDP/T.38 TCP/G.711/V.34 Scenario 6 UDP/T.38 TCP/G.711/V.34 - PASS - PASS - PASS - PASS Additional tests Section 8.7 For additional tests like inter nodes communications or Spatial redundancy, refer to the tests made with Open Touch fax Server. 6.2 Summary of problems 1. Occasional loss of signal in the RTP stream from OXE at inbound side of PSTN loopback calls (TT#21522). As a result of this issue: a. High failure rate for G.711 Passthrough (UDP/TCP, V.17/V.34) during load tests b. Some G3/G4 document tests may fail occasionally for G.711 Passthrough. Due to existing issues with G711 Passthrough it is not recommended to use this feature. 6.3 Summary of limitations 1. OXE is not H.323 enabled on our equipment; therefore H.323 tests were not performed and reported in this document. 2. SIP TLS is not currently supported and thus not tested in this test activity. 3. For T.38 (TCP/UDP), maximum fax rate that can be reached is 9,600bps. OXE overrides the modulation settings in the T.38 packet with V.27 and V.29 only even maximum T.38 fax rate is set to 14,400bps on it. 4. For T.38 (TCP/UDP), ECM will not be used even ECM is enabled on all equipments along the path. OXE resets the ECM bit in the T.38 packet to Notes & remarks ECM is available with following OXE releases: J K L Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 15/51

16 7 Test Scenarios 7.1 Test procedure Step Action 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. 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. OK: Positive result 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). N/T: No tested NOK: Negative result 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 debug and fix problems. 7.2 Result template The results table must be formatted as indicated in the example below: Step Action 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 N/T No test resource 4. action 4 N/A Relevant only if the CTI interface is a direct CSTA link 5. action 5 NOK No indication, no error message Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 16/51

17 8 Testing These tests will verify that the different components are properly connected and can communicate together (the external application and the Alcatel-Lucent Enterprise Communication Platform is connected and the interface link is operational). 8.1 Basic signalling compatibility Test objectives The objective of this section is to validate that the basic fax send and receive functions work between XMediusFax and OXE Required Basic SIP_UDP Result Step Action Fallback T.38 G.711 to G SendToFaxTerminal OK OK OK 2 ReceiveFromFaxTerminal OK OK OK 3 SendReceive1PageFax OK OK OK 4 SendReceive2PagesFax OK OK OK 5 SendReceive5PagesFax OK OK* OK OXE 6 SendReceive20PagesFax OK OK OK Origin of the problem Comment Failed at first attempt, passed after resending. See 6.2.1b Required Basic SIP_TCP Result Step Action T.38 G.711 Fallback to G SendToFaxTerminal OK OK OK 2 ReceiveFromFaxTerminal OK OK OK 3 SendReceive1PageFax OK OK OK 4 SendReceive2PagesFax OK OK OK 5 SendReceive5PagesFax OK OK OK 6 SendReceive20PagesFax OK OK OK Origin of the problem Comment Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 17/51

18 8.2 Thorough T.30 and T.38 compatibility Test objectives This section validates that the documents type G3 and G4 are well sent and received Also, the Error Correction Mode (ECM) enabled is verified Required G3 Documents SIP_UDP Result Step Action Fallback T.38 G.711 to G SendG3400X400ToResoluti onlimitedterminal OK OK OK 2 SendReceiveA3MultiRes OK OK OK 3 SendReceiveB4MultiRes OK OK* OK* OXE SendReceiveG3200X100Le tter SendReceiveG3200X200Le tter SendReceiveG3300X300Le tter SendReceiveG3400X400Le tter OK OK OK OK OK OK OK OK OK OK OK OK 8 SendReceiveLegalMultiRes OK OK OK* OXE 9 SendReceiveMultiSizeMulti Res OK OK* OK OXE Origin of the problem Comment Failed at first attempt, passed after resending. See 6.2.1b Failed at first attempt, passed after resending. See 6.2.1b Failed at first attempt, passed after resending. See 6.2.1b Required G3 Documents SIP_TCP Step 1 Action SendG3400X400ToResoluti onlimitedterminal Result Fallback T.38 G.711 G.711 OK OK OK 2 SendReceiveA3MultiRes OK OK* OK OXE 3 SendReceiveB4MultiRes OK OK OK* OXE 4 SendReceiveG3200X100Le tter OK OK OK 5 SendReceiveG3200X200Le tter OK OK OK 6 SendReceiveG3300X300Le tter OK OK OK 7 SendReceiveG3400X400Le tter OK OK OK 8 SendReceiveLegalMultiRes OK OK OK 9 SendReceiveMultiSizeMulti Res OK OK* OK* OXE Origin of the problem Comment Failed at first attempt, passed after resending. See 6.2.1b Failed at first attempt, passed after resending. See 6.2.1b Failed at first attempt, passed after resending. See 6.2.1b Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 18/51

19 8.2.4 Optional Error Correction Mode (ECM) SIP_TCP Step Action Result Origin of the T.38 G.711 problem OptReceiveECMEnableFromECMT erminal OK OK OXE OptReceiveECMEnableFromNoEC MTerminal OptReceiveNoECMFromECMTerm inal OptReceiveNoECMFromNoECMTe rminal 5 OptSendECMEnabledToECMTerm inal OK OK OXE 6 OptSendECMEnabledToNoECMTe rminal OK OK 7 OptSendNoECMToECMTerminal OK OK 8 OptSendNoECMToNoECMTermin al OK OK OK OK OK OK OK OK Comment In T.38 mode, fax success without ECM. Refer to In T.38 mode, fax success without ECM. Refer to Optional G4 Documents SIP_TCP Step Action OptSendReceiveG4200X10 0Letter OptSendReceiveG4200X20 0Letter OptSendReceiveG4300X30 0Letter OptSendReceiveG4400X40 0Letter Result Fallbak T.38 G.711 To G.711 OK OK OK OK OK OK OK OK OK OK OK OK Origin of the problem Comment Optional SIP_TCP Step Action Result T.38 G OptSIPConfigurableSIPInvite OK OK 2 OptSIPAuthentication OK OK 3 OptSIPMultipleDestinationPeers OK OK Origin of the problem Comment Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 19/51

20 8.3 Codec (CNG) Test objectives This section validates that error cases are treated smoothly and the error is reported appropriately Required Codec (CNG) SIP_UDP Step Action Result T.38 1 CNGRTPActivated OK 2 CNGT38Activated OK Origin of the problem Comment Required Codec (CNG) SIP_TCP Step Action Result T.38 1 CNGRTPActivated OK 2 CNGT38Activated OK Origin of the problem Comment 8.4 Error Handling Test objectives This section validates that error cases are treated smoothly and the error is reported appropriately Required Error Handling SIP_UDP Result Step Action Fallback T.38 G.711 to G ReceiveNoChannelAvailabl e OK OK OK 2 SendDestinationBusy OK OK OK 3 SendDestinationNoAnswer OK OK OK 4 StopXMediusFAXDriverWhil ereceiving OK OK OK 5 StopXMediusFAXDriverWhil esending OK OK OK 6 SendAllChannelsBusy OK OK OK 7 SendDestinationHangup OK OK OK 8 SendDestinationAnswerVoic e OK OK OK 9 InitiateVoiceCallToXMedius Fax OK OK OK Origin of the problem Comment Required Error Handling SIP_TCP Step Action Result T.38 G ReceiveNoChannelAvailable OK OK 2 SendDestinationBusy OK OK 3 SendDestinationNoAnswer OK OK 4 StopXMediusFAXDriverWhileRecei ving OK OK Origin of the problem Comment Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 20/51

21 Step Action Result T.38 G StopXMediusFAXDriverWhileSendi ng OK OK 6 SendAllChannelsBusy OK OK 7 SendDestinationHangup OK OK 8 SendDestinationAnswerVoice OK OK 9 InitiateVoiceCallToXMediusFax OK OK Origin of the problem Comment Optional Error Handling SIP_TCP Step Action Result T.38 G OptUnplugFaxTerminalWhileRecei ving OK OK 2 OptUnplugFaxTerminalWhileSendi ng OK OK 3 OptUnplugVoIPGatewayPSTNWhil ereceiving OK OK 4 OptUnplugVoIPGatewayPSTNWhil esending OK OK 5 OptUnplugVOIPGatewayWhileRec eiving OK OK 6 OptUnplugVOIPGatewayWhileSen ding OK OK 7 OptUnplugXMediusFAXDriverWhil ereceiving OK OK 8 OptUnplugXMediusFAXDriverWhil esending OK OK 9 OptGtwyNotTrusted OK OK 10 OptSendNoRouteToDestinationOn Gtwy OK OK 11 OptUnplugFaxTerminalWhileRecei vingfirstpage OK OK 12 OptUnplugXMediusFax OK OK 13 XMediusFAXDriverAllChannelsBus y OK OK 8.5 Stability Test objectives Origin of the problem Comment This section validates that the system holds on load tests and longer duration fax exchanges Required Load Tests SIP_UDP Step Action Result Origin of the T.38 G.711 problem 1 MassiveNearEmpty OK OK 2 AllChannelsInBoth OK OK 3 Massive3page OK NOK OXE Comment 7.43% 7.43% outbound inbound failure Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 21/51

22 8.5.3 Required Load Tests SIP_TCP Step 1 Action MassiveNearEmpty Result T.38 G.711 OK NOK OXE 2 AllChannelsInBoth OK OK 3 Massive3page OK NOK OXE Origin of the problem Comment 2.81% 2.63% outbound inbound failure 16.02% 15.96% outbound inbound failure 8.6 User Scenarios Test objectives This section validates 6 typical user configurations with a normal load User Scenarios Step Result Origin of the problem Action UDP TCP T.38 G.711-V.34 T.38 G.711-V.34 1 Scenario-01-SIP OK OK OK OK 2 Scenario-02-SIP N/T NOK OK N/T OXE 2.34% failure 3 Scenario-03-SIP N/T OK OK N/T 4 Scenario-04-SIP OK NOK OK NOK 5 Scenario-05-SIP OK N/T N/T OK 6 Scenario-06-SIP OK N/T N/T OK OXE Comment Regression with UDP/G.711-V34: 4.39% 2.79% outbound/inbound failure TCP/G.711-V.34: 4.18% 2.74% outbound inbound failure 8.7 Additional tests This section contains tests that are performed by Alcatel R&D team Step Action Result 1 OEM/ OXE-Additional/ MultipleGDs N/A 2 OEM/ OXE-Additional / InternodesCommunication N/A 3 OXE/ OXE-Additional / SpatialRedundancy N/A 4 OXE/ OXE-Additional / PassiveCommunicationServer N/A Origin of the problem Comment Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 22/51

23 8.8 Test Cases Details Required Tests ID : Required/ Basic/ 1-SendToFaxTerminal 1. Send G3_200X200_Letter_1page.tif fax from FoIP server to the fax terminal. 2. Wait for the fax to be sent. 3. Repeat step 1 and Repeat step 1 and 2. ID 1.1.2: Required/ Basic/ 2-ReceiveFromFaxTerminal 1. Send printed G3_200X200_Letter_1page.tif from the fax terminal to FoIP server. 2. Wait for the fax to be received 3. Repeat step 1 and Repeat step 1 and 2. ID 1.1.3: Required/ Basic/ 3-SendReceive1PageFax 1. Send G3_200X200_Letter_1page.tif ID 1.1.4: Required/ Basic/ 4-SendReceive2PagesFax 1. Send G3_400X400_Letter_2pages.tif ID :Required/ Basic/ 5-SendReceive5PagesFax 1. Send G3_300X300_Letter_5pages.tif ID 1.1.6: Required/ Basic/ 6-SendReceive20PagesFax 1. Send G3_400X400_Letter_20pages.tif ID 1.2.1: Required/ ErrorHandling/ 1-ReceiveNoChannelAvailable Test Scenario 1 "Loopback" Test Scenario 2 "Fax Terminal" 1. The faxes were successfully sent. 2. The content of the receive faxes are identical to the original document. Test Scenario 2 "Fax Terminal" 1. The faxes were successfully received. 2. The content of the receive faxes are identical to the original document. Test Scenario 1 "Loopback" 1a. The fax is sent successfully 1b. The fax is received successfully 1c. The received fax content is visually the same as the sent fax (expect for the fax header) Test Scenario 1 "Loopback" 1a. The fax is sent successfully 1b. The fax is received successfully 1c. The received fax content is visually the same as the sent fax (expect for the fax header) Test Scenario 1 "Loopback" 1a. The fax is sent successfully 1b. The fax is received successfully 1c. The received fax content is visually the same as the sent fax (expect for the fax header) Test Scenario 1 "Loopback" 1a. The fax is sent successfully 1b. The fax is received successfully 1c. The received fax content is visually the same as the sent fax (expect for the fax header) Test Scenario 1 "Loopback" 2a. The fax is not sent and reports an "destination is Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 23/51

24 1. Configure all channels on FoIP Server in send only. 2. Send G3_200X200_Letter_1page.tif from the FoIP Server Note: Each call made with an error condition must be followed by a successful call for the test to pass. Busy" error. ID 1.2.2: Required/ ErrorHandling/ 2-SendDestinationBusy Handling and recovering of Error conditions 1. Take the fax terminal off hook or replace by a phone and take off hook. 2. Send G3_200X200_Letter_1page.tif from the FoIP Server to the Fax Terminal. ID 1.2.3: Required/ ErrorHandling/ 3-SendDestinationNoAnswer Handling and recovering of Error conditions 1. Configure the fax terminal in manual mode or replace it with a phone. 2. Send a G3_200X200_Letter_1page.tif from the FoIP Server to the Fax Terminal. 3. Wait at most 2 min or for the fax to fail. Scenario 2 "Fax Terminal" 2. The transmission fails with Error message "destination busy" Scenario 2 "Fax Terminal" ID 1.2.4: Required/ ErrorHandling/ 4-StopXMediusFAXDriverWhileReceiving Handling and recovering of Error conditions 1. Send a fax G3_200X200_Letter_1page.tif from Fax Terminal to FoIP server. 2. Wait for the first page to be transmitted. 3. Stop XMediusFAX Driver. 4. Wait for the fax to fail and channel released on FoIP server and VoIP Gateway. 5. Start XMediusFAX Driver. 6. Send again without interrupting the transmisssion. ID 1.2.5: Required/ ErrorHandling/ 5-StopXMediusFAXDriverWhileSending Handling and recovering of Error conditions 1. Send a fax G3_200X200_Letter_3page.tif from FoIP server to Fax Terminal. 2. Wait for the first page to be transmitted. 3. Stop XMediusFAX Driver. 4. Wait for the fax to fail and channel released on FoIP server and VoIP Gateway. 5. Start XMediusFAX Driver. 6. Send again without interrupting the transmission. ID 1.2.6: Required/ ErrorHandling/ 6-SendAllChannelsBusy Handling and recovering of Error conditions 1. Send fax when all channels on VoIP Gateway are busy 2. Send the same fax when the channels are available ID 1.2.7: Required/ ErrorHandling/ 7-SendDestinationHangup Handling and recovering of Error conditions 1. Send a fax to a number from which you can answer manually (yourself). 3a. Fax fails. Error "No answer detected " 3b. All channels are released on the FoIP Server and the VoIP Gateway 4a. Interrupted Fax fails. 4b. Verify that the channel are released on the FoIP server and VoIP gateway. 4c. Only the first page is fully received by the FoIP server. Note: 4c. is not applicable for Enterprise and for 4.6. In 5.5+, the fax will be displayed in the Inbound History when starting the XMediusFAX Driver. 6a. Fax is successfully received. 4a. Interrupted Fax fails. Note: In Enterprise, fax becomes Ready to Send. 4b. Verify that the channel are released on the FoIP server and VoIP gateway. 6a. Fax is successfully sent. 1. Fax remain in 'Ready to send' until one of the channels are available. 2. Fax is sent successfully 3a. Verify the Error reported is 502, 307 (Remote-end hangup) or 602 (No fax detected). Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 24/51

25 2. Answer the call and wait few seconds 3. Hangup. ID 1.2.8: Required/ ErrorHandling/ 8-SendDestinationAnswerVoice Handling and recovering of Error conditions 1. Configure the fax terminal in manual mode or replace it with a phone. 2. Send a G3_200X200_Letter_1page.tif from the FoIP Server to the Fax Terminal. 3. Start to speak on the phone. Wait at most 2 min or for the fax to fail. ID 1.2.9: Required/ ErrorHandling/ 9-InitiateVoiceCallToXMediusFax Handling and recovering of Error conditions PSTN Voice Call to DUT: 1. Enable T.38 on DUT. 2. Initiate a voice call from PSTN to DUT. 3a. Fax fails. Error "No answer detected " 3b. All channels are released on the FoIP Server and the VoIP Gateway 2a. Verify the PSTN phone hears the tones after the voice leg of the call is setup. 2b. Verify the call is torn down cleanly. ID 1.3.1: Required/ G3Documents/ 1-SendG3400X400ToResolutionLimitedTerminal 1. Configure the receiving maximum resolution capability to high (200x200). 2. Send G3_400X400_Letter_2pages.tif ID 1.3.2: Required/ G3Documents/ 2-SendReceiveA3MultiRes 1. Send G3A3MultiRes.tif ID1.3.3: Required/ G3Documents/ 3-SendReceiveB4MultiRes 1. Send G3B4MultiRes.tif ID 1.3.4: Required/ G3Documents/ 4-SendReceiveG3200X100Letter 1. Send G3_200X100_Letter.tif ID 1.3.5: Required/ G3Documents/ 5-SendReceiveG3200X200Letter Test Scenario 1 "Loopback" 2a. The fax is sent successfully 2b. The fax is received successfully 2c. The received fax content is visually the same as the sent fax (expect for the fax header) 2d. Resolution of the received is fax 200x200. Test Scenario 1 "Loopback" 1a. The fax is sent successfully 1b. The fax is received successfully 1c. The received fax content is visually the same as the sent fax (expect for the fax header) 1d. Resolution and encoding of each pages of the received & sent fax are identical. Test Scenario 1 "Loopback" 1a. The fax is sent successfully 1b. The fax is received successfully 1c. The received fax content is visually the same as the sent fax (expect for the fax header) 1d. Resolution and encoding of each pages of the received & sent fax are identical. Test Scenario 1 "Loopback" 1a. The fax is sent successfully 1b. The fax is received successfully 1c. The received fax content is visually the same as the sent fax (expect for the fax header) 1d. Resolution and encoding of the received & sent fax are identical. Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 25/51

26 1. Send G3_200X200_Letter_1page.tif Test Scenario 1 "Loopback" 1a. The fax is sent successfully 1b. The fax is received successfully 1c. The received fax content is visually the same as the sent fax (expect for the fax header) 1d. Resolution and encoding of the received & sent fax are identical. ID 1.3.6: Required/ G3Documents/ 6-SendReceiveG3300X300Letter 1. Send G3_300X300_Letter_5pages.tif ID 1.3.7: Required/ G3Documents/ 7-SendReceiveG3400X400Letter 1. Send G3_400X400_Letter_2pages.tif ID 1.3.8: Required/ G3Documents/ 8-SendReceiveLegalMultiRes 1. Send G3LegalMultiRes.tif Contains:: Letter Low, Legal high, A4 high, B4 fine, A3 super fine ID 1.3.9: Required/ G3Documents/ 9-SendReceiveMultiSizeMultiRes 1. Send G3MultiSizeMultiRes.tif ID 1.4.1: Required/ LoadTests/ 1-MassiveNearEmpty Set number of channels on the FoIP server to the gateway capacity. 2. Set 40% of the channels in "Send and 60% in "Receive". 3. The retry must be set to 0 to avoid faltering statistics. 4. Send ("nbr of channel of the VoIP Gateway" * 2000) Test Scenario 1 "Loopback" 1a. The fax is sent successfully 1b. The fax is received successfully 1c. The received fax content is visually the same as the sent fax (expect for the fax header) 1d. Resolution and encoding of the received & sent fax are identical. Test Scenario 1 "Loopback" 1a. The fax is sent successfully 1b. The fax is received successfully 1c. The received fax content is visually the same as the sent fax (expect for the fax header) 1d. Resolution and encoding of the received & sent fax are identical. Test Scenario 1 "Loopback" 1a. The fax is sent successfully 1b. The fax is received successfully 1c. The received fax content is visually the same as the sent fax (expect for the fax header) 1d. Resolution and encoding of each pages of the received & sent fax are identical. Test Scenario 1 "Loopback" 1a. The fax is sent successfully 1b. The fax is received successfully 1c. The received fax content is visually the same as the sent fax (expect for the fax header) 1d. Resolution and encoding of each pages of the received & sent fax are identical. Test Scenario 1 3a. All fax should be sent or failed. 3b. Sending failure rate should be less than 2%. 3c. Receiving Failure rate must be inferior or equal to the sending failure rate. 3d. Verify that all the channels are released on the FoIP server and VoIP gateway. Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 26/51

27 Empty.tif. Note: Receiving failure rate is calculated with the following formula: ("total nbr sent" - "nbr received with success") / "total nbr sent" When test are executed from the VoIP Server, the retry mechanism must be set to 0 to avoid faltering statistics. 1. Because of collisions that may appear during mass test, a Busy is not considered as a failure 2. For improved results during mass testing, channel allocation should be 40% for outbound traffic and 60% inbound traffic. All tests are executed with ECM disabled unless specified ID 1.4.2: Required/ LoadTests/ 2-AllChannelsInBoth Set number of channel on the FoIP server to the gateway capacity. 2. Set all channels on the FoIP Server in "both". 3. Send ("nbr of channel of the VoIP Gateway" * 100) G3_200X200_Letter_1page.tif. 4. Wait for all faxes to be sent or failed. 5. Send a fax G3_200X200_Letter_1page.tif. ID 1.4.3: Required/ LoadTests/ 3-Massive3page 1.Set number of channel on the FoIP server to the gateway capacity. 2. Set 40% of the channels in "Send" and 60% in "Receive". 3.The retry must be set to 0 to avoid faltering statistics 4. Send ("nbr of channel of the VoIP Gateway" * 500) G3_200X200_Letter_3page.tif. Notes: Receiving failure rate is calculated with the following formula: ("total nbr sent" - "nbr received with success") / "total nbr sent" When test are executed from the VoIP Server, the retry mechanism must be set to 0 to avoid faltering statistics 1. Because of collisions that may appear during mass test, a Busy is not considered as a failure 2. For improved results during mass testing, channel allocation should be 40% for outbound traffic and 60% inbound traffic. Test Scenario 1 "Loopback" 4a. All fax should be sent or failed. 4b. Verify that the channels are released on the FoIP server and VoIP gateway. 5a. The fax must be sent & received successfully. Note: This test will cause many faxes to fail, this is expected! No crash from the driver or reset from the VoIP Gateway is expected Test Scenario 1 3a. All fax should be sent or failed. 3b. Sending failure rate should be less than 2%. 3c. Receiving Failure rate must be inferior or equal to the sending failure rate. 3d. Verify that all the channels are released on the FoIP server and VoIP gateway. 3e. Randomly open 0.1% or minimally 5 received faxes to validate their. All tests are executed with ECM disabled unless specified. ID: Required/ CNG_CODEC_DUALDID/ 1-CNGRTPActivated 1. Set Peer Port in Driver to "Send CNG using RTP". 2. Send xyz.tif fax to a number that is not a fax device (i.e., phone). 3. Send xyz.tif fax to a fax machine that waits to emit CED tones (after hearing CNG) Scenario 2 "Fax Terminal" 2a. Should hear fax tone. 2b. Fax fails. Error "no answer detected?" 3. Fax is successfully sent Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 27/51

28 ID: Required/ CNG_CODEC_DUALDID/ 2-CNGT38Activated 1. Set Peer Port in Driver to "Send CNG using T.38". 2. Send xyz.tif fax to a number that is not a fax device (i.e., phone). 3. Send xyz.tif fax to a fax machine that waits to emit CED tones (after hearing CNG) Optional Tests Scenario 2 "Fax Terminal" 2a. Should not hear any fax tone. 2b. Fax fails. Error "no answer detected?" 3. Fax call fails to setup (there is no RE-INVITE). ID 2.1.1: Optional/ ErrorHandling/ 01-OptUnplugFaxTerminalWhileReceiving Handling and recovering of Error conditions 1. Send a fax G3_200X200_Letter_3page.tif from from Fax Terminal to FoIP server 2. Wait for the first page to be transmitted 3. Unplug the fax terminal from the Telephony Network 4. Wait for the fax to fail 5. Replgg the fax terminal to the Telephony Network 6. Send again without interrupting the transmission 4a. Interrupted Fax fails. 4b. Verify that the channel are released on the FoIP server and VoIP gateway. 4c. Only the first page is fully received by the FoIP server. 6a. Fax is successfully received. ID 2.1.2: Optional/ ErrorHandling/ 02-OptUnplugFaxTerminalWhileSending Handling and recovering of Error conditions 1. Send a fax G3_200X200_Letter_3page.tif from FoIP server to Fax Terminal. 2. Wait for the first page to be transmitted 3. Unplug the fax terminal from the Telephony Network 4. Wait for the fax to fail 5. Replug the fax terminal to the Telephony Network 6. Send again without interrupting the transmission 4a. Interrupted Fax fails. 4b. Verify that the channel are released on the FoIP server and VoIP gateway. 6a. Fax is successfully sent. ID 2.1.3: Optional/ ErrorHandling/ 03-OptUnplugVoIPGatewayPSTNWhileReceiving Handling and recovering of Error conditions 1. Send a fax G3_200X200_Letter_3page.tif from Fax Terminal to FoIP server. 2. Wait for the first page to be transmitted. 3. Unplug the PSTN from the VOIP Gateway. 4. Wait for the fax to fail and channel released on FoIP server and VoIP Gateway. 5. Replug the PSTN to the VOIP gateway. 6. Send again without interrupting the transmission. 4a. Interrupted Fax fails. 4b. Verify that the channel are released on the FoIP server and VoIP gateway. 4c. Only the first page is fully received by the FoIP server. 6a. Fax is successfully received. ID 2.1.4: Optional/ ErrorHandling/ 04-OptUnplugVoIPGatewayPSTNWhileSending Handling and recovering of Error conditions 1. Send a fax G3_200X200_Letter_3page.tif from FoIP server to Fax Terminal. 2. Wait for the first page to be transmitted. 3. Unplug the PSTN from the VOIP Gateway. 4. Wait for the fax to fail and channel released on FoIP server and VoIP Gateway. 5. Replug the PSTN to the VOIP gateway. 6. Send again without interrupting the transmission. 4a. Interrupted Fax fails. 4b. Verify that the channel are released on the FoIP server and VoIP gateway. 6a. Fax is successfully sent. ID 2.1.5: Optional/ ErrorHandling/ 05-OptUnplugVOIPGatewayWhileReceiving Handling and recovering of Error conditions Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 28/51

29 1. Send a fax G3_200X200_Letter_3page.tif from Fax Terminal to FoIP server. 2. Wait for the first page to be transmitted. 3. Unplug the VOIP gateway from the Switch. 4. Wait for the fax to fail and channel released on FoIP server and VoIP Gateway. 5. Replug the VOIP gateway to the Switch. 6. Send again without interrupting the transmission. ID 2.1.6: Optional/ ErrorHandling/ 06-OptUnplugVOIPGatewayWhileSending Handling and recovering of Error conditions 1. Send a fax G3_200X200_Letter_3page.tif from FoIP server to Fax Terminal. 2. Wait for the first page to be transmitted. 3. Unplug the VOIP gateway from the Switch. 4. Wait for the fax to fail and channel released on FoIP server and VoIP Gateway. 5. Replug the VOIP gateway to the Switch. 6. Send again without interrupting the transmission. 4a. Interrupted Fax fails. 4b. Verify that the channel are released on the FoIP server and VoIP gateway. 4c. Only the first page is fully received by the FoIP server. 6a. Fax is successfully received. 4a. Interrupted Fax fails. 4b. Verify that the channel are released on the FoIP server and VoIP gateway. 6a. Fax is successfully sent. ID 2.1.7: Optional/ ErrorHandling/ 07-OptUnplugXMediusFAXDriverWhileReceiving Handling and recovering of Error conditions 1. Send a fax G3_200X200_Letter_3page.tif from Fax Terminal to FoIP server. 2. Wait for the first page to be transmitted. 3. Unplug the FoIP server from the switch. 4. Wait for the fax to fail and channel released on FoIP server and VoIP Gateway. 5. Replug the FoIP server to the switch. 6. Send again without interrupting the transmission. 4a. Interrupted Fax fails. 4b. Verify that the channel are released on the FoIP server and VoIP gateway. 4c. Only the first page is fully received by the FoIPs server. 6a. Fax is successfully received. ID 2.1.8: Optional/ ErrorHandling/ 08-OptUnplugXMediusFAXDriverWhileSending Handling and recovering of Error conditions 1. Send a fax G3_200X200_Letter_3page.tif from FoIP server to Fax Terminal. 2. Wait for the first page to be transmitted. 3. Unplug the FoIP server from the switch. 4. Wait for the fax to fail and channel released on FoIP server and VoIP Gateway. 5. Replug the FoIP server to the switch. 6. Send again without interrupting the transmission. ID 2.1.9: Optional/ ErrorHandling/ 09-OptGtwyNotTrusted Handling and recovering of Error conditions 1. Enable gateway security on FoIp server 2. Remove VoIP gateway from trusted gateway list 3. Send G3_200X200_Letter_1page.tif from fax terminal 4. Add VoIP gateway to trusted gateway list 5. Send G3_200X200_Letter_1page.tif from fax terminal 4a. Interrupted Fax fails. 4b. Verify that the channel are released on the FoIP server and VoIP gateway. 6a. Fax is successfully sent. Scenario 2 "Fax Terminal" 3a. Fax terminal reports an error 3b. Check FoIP server logs and validate that the fax was refused for security reasons 5. Fax is sent successfully ID : Optional/ ErrorHandling/ 10-OptSendNoRouteToDestinationOnGtwy Handling and recovering of Error conditions 1. Remove route rules to PSTN on the VoIP gateway 2. Send G3_200X200_Letter_1page.tif from FoIP server Test Scenario 1 "Loopback" 2. Fax fails with error message saying there is no route to destination 4. Fax is sent successfully Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 29/51

30 3. Restore the route rule to PSTN on the VoIP gateway 4. Send G3_200X200_Letter_1page.tif from FoIP server. ID : Optional/ ErrorHandling/ 11-OptUnplugFaxTerminalWhileReceivingFirstPage Handling and recovering of Error conditions 1. Send a fax G3_200X200_Letter.tif from from Fax Terminal to FoIP server 2. Wait until the transmission starts 3. Unplug the fax terminal from the Telephony Network 4. Wait for the fax to fail 5. Replug the fax terminal to the Telephony Network 6. Send again without interrupting the transmission. ID : Optional/ ErrorHandling/ 12-OptUnplugXMediusFax Handling and recovering of Error conditions 1. Unplug the network cable from DUT. 2. Make a fax call to DUT from PSTN. 3. Plug the network cable to DUT 4. Make another fax call to DUT; send 10 pages. 2. Fax fails with error message saying there is no route to destination 4. Fax is sent successfully 2a. Verify the first fax call fails. 4a. Second fax call is completed and pages transmitted. ID : Optional/ ErrorHandling/ 13-XMediusFAXDriverAllChannelsBusy Handling and recovering of Error conditions 1. Make DUT busy so it cannot received any fax. 2. Initiate another analog fax call from PSTN to DUT. ID 2.2.1: Optional/ ECM/ 1-OptReceiveECMEnableFromECMTerminal 1. Enable ECM on FoIP Server and Fax Terminal 2. Send printed G4_200X100_Letter.tif from the fax terminal to FoIP server. 3. Wait for the fax to be received 4. Repeat step 1 and Repeat step 1 and 2. ID 2.2.2: Optional/ ECM/ 2-OptReceiveECMEnableFromNoECMTerminal 1. Enable ECM on FoIP Server 2. Disable ECM on Fax Terminal 2. Send printed G4_200X100_Letter.tif from the fax terminal to FoIP server. 3. Wait for the fax to be received 4. Repeat step 1 and Repeat step 1 and 2. ID 2.2.3: Optional/ ECM/ 3-OptReceiveNoECMFromECMTerminal 1. Disable ECM on FoIP Server. 2. Enable ECM on Fax Terminal. 3. Send printed G4_200X100_Letter.tif from the fax terminal to FoIP server. 2a. DUT is busy, the Fax is pending on the analog fax, when the busy state clear the fax should be sent. Test Scenario 2 "Fax Terminal" 1. The faxes were successfully received. 2. The content of the receive faxes are identical to the original document. Test Scenario 2 "Fax Terminal" 1. The faxes were successfully received. 2. The content of the receive faxes are identical to the original document. Test Scenario 2 "Fax Terminal" 1. The faxes were successfully received. 2. The content of the receive faxes are identical to the original document. Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 30/51

31 4. Wait for the fax to be received 5. Repeat step 1 and Repeat step 1 and 2. ID 2.2.4: Optional/ ECM/ 4-OptReceiveNoECMFromNoECMTerminal 1. Disable ECM on FoIP Server and Fax Terminal. 2. Send printed G3_200X200_Letter_1page.tif from the fax terminal to FoIP server. 3. Wait for the fax to be received 4. Repeat step 1 and Repeat step 1 and 2. ID 2.2.5: Optional/ ECM/ 5-OptSendECMEnabledToECMTerminal 1. Enable ECM on FoIP Server and Fax Terminal 2. Send G4_200X100_Letter.tif fax from FoIP server to the fax terminal. 3. Wait for the fax to be sent. 4. Repeat step 1 and Repeat step 1 and 2. ID 2.2.6: Optional/ ECM/ 6-OptSendECMEnabledToNoECMTerminal 1. Enable ECM on FoIP Server 2. Disable ECM on Fax Terminal 3. Send G4_200X100_Letter.tif from FoIP Server to Fax Terminal ID 2.2.7: Optional/ ECM/ 7-OptSendNoECMToECMTerminal 1. Disable ECM on FoIP Server. 2. Enable ECM on Fax Terminal. 3. Send G4_200X100_Letter.tif fax from FoIP server to the fax terminal. 4. Wait for the fax to be sent. 5. Repeat step 1 and Repeat step 1 and 2. ID 2.2.8: Optional/ ECM/ 8-OptSendNoECMToNoECMTerminal 1. Disable ECM on FoIP Server and Fax Terminal. 2. Send G4_200X100_Letter.tif from FoIP Server to Fax Terminal ID 2.3.1: Optional/ G4Documents/ 1-OptSendReceiveG4200X100Letter 1. Send G4_200X100_Letter.tif Test Scenario 2 "Fax Terminal" 1. The faxes were successfully received. 2. The content of the receive faxes are identical to the original document. TestScenario 2 "Fax Terminal" 3a. The faxes were successfully sent. 3b. The content of the receive faxes are identical to the original document. 4a. The faxes were successfully sent. 4b. The content of the receive faxes are identical to the original document. 5a. The faxes were successfully sent. 5b. The content of the receive faxes are identical to the original document. Test Scenario 2 "Fax Terminal" 3a. The fax was successfully sent. 3b. The content of the received fax is identical to the original document. TestScenario 2 "Fax Terminal" 4a. The faxes were successfully sent. 4b. The content of the receive faxes are identical to the original document. 5a. The faxes were successfully sent. 5b. The content of the receive faxes are identical to the original document. 6a. The faxes were successfully sent. 6b. The content of the receive faxes are identical to the original document. Test Scenario 2 "Fax Terminal" 2a. The fax was successfully sent. 2b. The content of the received fax is identical to the original document. Test Scenario 1 "Loopback" 1a. The fax is sent successfully Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 31/51

32 ID Optional/ G4Documents/ 2-OptSendReceiveG4200X200Letter 1. Send G4_200X200_Letter.tif ID 2.3.3: Optional/ G4Documents/ 3-OptSendReceiveG4300X300Letter 1. Send G4_300X300_Letter.tif ID 2.3.4: Optional/ G4Documents/ 4-OptSendReceiveG4400X400Letter 1. Send G4_400X400_Letter.tif ID: Optional/ SIP/ 1-OptSIPConfigurableSIPInvite 1b. The fax is received successfully 1c. The received fax content is visually the same as the sent fax (expect for the fax header) 1d. Resolution and encoding of the received & sent fax are identical. Test Scenario 1 "Loopback" 1a. The fax is sent successfully 1b. The fax is received successfully 1c. The received fax content is visually the same as the sent fax (expect for the fax header) 1d. Resolution and encoding of the received & sent fax are identical. Test Scenario 1 "Loopback" 1a. The fax is sent successfully 1b. The fax is received successfully 1c. The received fax content is visually the same as the sent fax (expect for the fax header) 1d. Resolution and encoding of the received & sent fax are identical. Test Scenario 1 "Loopback" 1a. The fax is sent successfully 1b. The fax is received successfully 1c. The received fax content is visually the same as the sent fax (expect for the fax header) 1d. Resolution and encoding of the received & sent fax are identical. Scenario 1 "Loopback" 1. Change Display Name ("calling party name") in SIP 1. Change should be accepted for Inbound INVITE. header. 2. The fax is received successfully. 2. Change User name ("calling number") in SIP header 4. Inbound call reflects changes. - can be typed in any name as long as the $ signs are Note: Use Wireshark to validate changes deleted. 3. Change Host name ("IP address") in SIP header - take out the $ signs and type in the IP address of the machine. 4. Send xyz.tif fax from Fax Terminal to FoIP server. ID: Optional/ SIP/ 2-OptSIPAuthentication Note: In order to setup OXE Authentication Realm follow the steps described in the attached doc. 1. Verify that the fax server has been added to Realms List under Driver/SIP Authentication. 2. Send xyz.tif fax. ID: Optional/ SIP/ 4-OptSIPMultipleDestinationPeers 1. Configure at least 2 gateways in the Driver/Peer Scenario 1 "Loopback" 2a. Fax is successfully sent (call is authenticated). 2b. Fax is successfully received. Scenario 2 "Loopback" 5a. Interrupted Fax fails. Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 32/51

33 List. 2. Send a fax xyz.tif from FoIP server to Fax Terminal. 3. Wait for the first page to be transmitted. 4. Unplug the PSTN from one of the VOIP Gateways. 5. Wait for the fax to fail and channel released on FoIP server and VoIP Gateway. 6. Send again without interrupting the transmission. 7. Replug the PSTN to the VOIP gateway. ID 2.4.1: Optional/ H.323/ 1-OptReceiveWithFastStartNoTunneling 1. On the VoIP Gateway configure to support only H.323 Fast Start with no tunnelling. 1. Send printed G3_200X200_Letter_1page.tif from the fax terminal to FoIP server. 2. Wait for the fax to be received 3. Repeat step 1 and Repeat step 1 and 2. ID 2.4.2: Optional/ H.323/ 2-OptReceiveWithFastStartTunneling 1. On the VoIP Gateway configure to support only H.323 Fast Start with tunnelling 1. Send printed G3_200X200_Letter_1page.tif from the fax terminal to FoIP server. 2. Wait for the fax to be received 3. Repeat step 1 and Repeat step 1 and 2. ID 2.4.3: Optional/ H.323/ 3-OptReceiveWithSlowStartNoTunneling 1. On the VoIP Gateway configure to support only H.323 Slow Start with no tunnelling. 1. Send printed G3_200X200_Letter_1page.tif from the fax terminal to FoIP server. 2. Wait for the fax to be received 3. Repeat step 1 and Repeat step 1 and 2. ID 2.4.4: Optional/ H.323/ 4-OptReceiveWithSlowStartTunneling 1. On the VoIP Gateway configure to support only H.323 Slow Start with tunnelling. 1. Send printed G3_200X200_Letter_1page.tif from the fax terminal to FoIP server. 2. Wait for the fax to be received 3. Repeat step 1 and Repeat step 1 and 2. ID 2.4.5: Optional/ H.323/ 5-OptSendWithFastStartNoTunneling 1. On the VoIP Gateway configure to support only H.323 Fast Start with no tunneling 2. Send G3_200X200_Letter_1page.tif fax from FoIP server to the fax terminal. 3. Wait for the fax to be sent. 4. Repeat step 1 and 2. 5b. Verify that the channel are released on the FoIP server and VoIP gateway. 6a. Fax is successfully sent. Test Scenario 2 "Fax Terminal" 1. The faxes were successfully received. 2. The content of the receive faxes are identical to the original document. Test Scenario 2 "Fax Terminal" 1. The faxes were successfully received. 2. The content of the receive faxes are identical to the original document. Test Scenario 2 "Fax Terminal" 1. The faxes were successfully received. 2. The content of the receive faxes are identical to the original document. Test Scenario 2 "Fax Terminal" 1. The faxes were successfully received. 2. The content of the receive faxes are identical to the original document. Test Scenario 2 "Fax Terminal" 1. The faxes were successfully sent. 2. The content of the receive faxes are identical to the original document. Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 33/51

34 5. Repeat step 1 and 2. ID 2.4.6: Optional/ H.323/ 6-OptSendWithFastStartTunneling 1. On the VoIP Gateway configure to support only H.323 Fast Start with tunneling 2. Send G3_200X200_Letter_1page.tif fax from FoIP server to the fax terminal. 3. Wait for the fax to be sent. 4. Repeat step 1 and Repeat step 1 and 2. ID 2.4.7: Optional/ H.323/ 7-OptSendWithSlowStartNoTunneling 1. On the VoIP Gateway configure to support only H.323 Slow Start with no tunneling 2. Send G3_200X200_Letter_1page.tif fax from FoIP server to the fax terminal. 3. Wait for the fax to be sent. 4. Repeat step 1 and Repeat step 1 and 2. ID 2.4.8: Optional/ H.323/ 8-OptSendWithSlowStartTunneling 1. On the VoIP Gateway configure to support only H.323 Slow Start with tunneling 2. Send G3_200X200_Letter_1page.tif fax from FoIP server to the fax terminal. 3. Wait for the fax to be sent. 4. Repeat step 1 and Repeat step 1 and User Cases Test Scenario 2 "Fax Terminal" 1. The faxes were successfully sent. 2. The content of the receive faxes are identical to the original document. Test Scenario 2 "Fax Terminal" 1. The faxes were successfully sent. 2. The content of the receive faxes are identical to the original document. Test Scenario 2 "Fax Terminal" 1. The faxes were successfully sent. 2. The content of the receive faxes are identical to the original document. ID 2.5.1: UserCases/ Scenario-01-SIP 1. Set number of channel on the FoIP server to the gateway capacity. 2. Set 40% of the channels in "Send" and 60% in "Receive". 3. the retry must be set to 0 to avoid faltering statistics 4. Send ("nbr of channel of the VoIP Gateway" * 500) G3_200X200_Letter_3page.tif. Preconditions and Setup: SIP : Loopback in OXE 3a. All fax should be sent or failed. 3b. Sending failure rate should be less than 2%. 3c. Receiving Failure rate must be inferior or equal to the sending failure rate. 3d. Verify that all the channels are released on the FoIP server and VoIP gateway. 3e. Randomly open 0.1% or minimally 5 received faxes to validate their. ID 2.5.2: UserCases/ Scenario-02-SIP 1. Send G3_200X200_Letter_5pages.tif fax from FoIP server to the fax terminal. 2. Wait for the fax to be sent. 3. Repeat step 1 and Repeat step 1 and 2. Preconditions and Setup: FoIP---OXE---T1----PSTN---FaxLab 1. The faxes were successfully sent. 2. The content of the receive faxes are identical to the original document. Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 34/51

35 ID 2.5.3: OXE/ UserCases/ Scenario-03-SIP 1. Send printed G3_200X200_Letter_5pages.tif from the fax terminal to FoIP server. 2. Wait for the fax to be received 3. Repeat step 1 and Repeat step 1 and 2. ID 2.5.4: UserCases/ Scenario-04-SIP 1. Set number of channel on the FoIP server to the gateway capacity. 2. Set 40% of the channels in "Send" and 60% in "Receive". 3. the retry must be set to 0 to avoid faltering statistics 4. Send ("nbr of channel of the VoIP Gateway" * 500) G3_200X200_Letter_3page.tif. ID 2.5.5: UserCases/ Scenario-05-SIP 1. Send G3_200X200_Letter_2pages.tif fax from FoIP server to the fax terminal. 2. Wait for the fax to be sent. 3. Repeat step 1 and Repeat step 1 and 2. ID 2.5.6: UserCases/ Scenario-06-SIP 1. Send printed G3_200X200_Letter_5pages.tif from the fax terminal to FoIP server. 2. Wait for the fax to be received 3. Repeat step 1 and Repeat step 1 and 2. Preconditions and Setup: SIP : From PSTN through T1 1. The faxes were successfully received. 2. The content of the receive faxes are identical Preconditions and Setup: SIP : Loopback on PSTN through T1 3a. All fax should be sent or failed. 3b. Sending failure rate should be less than 2%. 3c. Receiving Failure rate must be inferior or equal to the sending failure rate. 3d. Verify that all the channels are released on the FoIP server and VoIP gateway. 3e. Randomly open 0.1% or minimally 5 received faxes to validate their. Preconditions and Setup: SIP : To Analog device plugged in OXE 1. The faxes were successfully sent. 2. The content of the receive faxes are identical to the original document. Preconditions and Setup: SIP : From Analog device plugged in OXE 1. The faxes were successfully received. 2. The content of the receive faxes are identical Additional tests (Alcatel) ID: OEM/ OXE-Additional/ PassiveCommunicationServer Check how the system will react in case of a CPU reboot, switchover or link failure. The test system is configured with PCS backup. Passive Comm Server (PCS) support. 1) Switchover to Passive Call Server (IP link to main/stdby call servers down). For each configuration check: Can new outgoing calls be made immediately after switchover? Are existing calls maintained after switchover? Are incoming calls (from new MAIN CS) accepted immediately after switchover? can existing call be modified (transfer, hang-up, etc.) after switchover? Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 35/51

36 ID: OEM/ OXE-Additional/ InternodesCommunication Preconditions and Setup: Send faxes between the fax server on one OXE node and a fax on another OXE node. 1) Send printed G3_200x200_Letter_5pages.tif from FoIP server to the fax terminal. 2) Wait for the fax to be received. The fax is sent/received properly. ID: OEM/ OXE-Additional/ SpatialRedundancy Check how the system will react in case of a CPU reboot, switchover or link failure. A. Spatial Redundancy support. 1) Do a CPU switchover (bascul). 2) Send printed G3-200x200_Letter-5pages.tif from FoIP server to fax terminal. 3) Wait for the fax to be recived. 4) Repeat step 2 and 3. 5) Repeat step 2 and 3. B. Passive Comm Server (PCS) support. 1) Switchover to Passive Call Server (IP link to main/stdby call servers down). Preconditions and Setup: The test system is configured with spatial redundancy (duplicate call servers on two different IP subnetworks). For each configuration check: Can new outgoing calls be made immediately after switchover? Are existing calls maintained after switchover? Are incoming calls (from new MAIN CS) accepted immediately after switchover? can existing call be modified (transfer, hang-up, etc.) after switchover? Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 36/51

37 9 Appendix A : AAPP member s Application description XMediusFAX SP is the first board less and multi-tenant Fax over IP (FoIP) fax server software. Ideal for any service provider or large enterprise that has deployed or plans to deploy an IP telephony infrastructure. Field-proven to manage large fax volumes and deliver high levels of scalability, reliability and availability. Addresses the fax problem in IP networks with the most advanced T.38 FoIP integration with gateways. Provides seamless ipbx integration and virtual machine support using VMWare Figure 2 Typical deployment architecture Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 37/51

38 10 Appendix B: Configuration requirements of the AAPP member s application Please refer to XMediusFAX Manuals to setup FoIP (Administration Guide.pdf). Additional setup: 10.1 Ports for SIP XMediusFAX System Configuration Hosts {Hostname} Driver Properties SIP Local SIP UDP Port: 5360 Local SIP TCP Port: 5360 Local SIP TLS Port: Peer for SIP_UDP: XMediusFAX System Configuration Hosts {Hostname} Driver Properties Peer List => Add SIP Peer Host Name: IP of OXE CS Transport: UDP Port: 5060 Media Type: T.38 Fax Relay G.711 Passthrough T.38 with Fallback to G.711 Keep all the other parameters in their default values Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 38/51

39 10.3 Peer for SIP_TCP: XMediusFAX System Configuration Hosts {Hostname} Driver Properties Peer List => Add SIP Peer Host Name: IP of OXE CS Transport: TCP Port: 5060 Media Type: T.38 Fax Relay G.711 Passthrough T.38 with Fallback to G.711 Keep all the other parameters in their default values Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 39/51

40 10.4 SIP Security for Authentication XMediusFAX System Configuration Hosts {Hostname} Driver Properties SIP Security => Add (Realm) 10.5 Fax Options of User Profile XMediusFAX Sites {Site Name} Configuration Profiles {Profile Name} Properties => Fax Options Retries Default: 0 Maximum: 0 Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 40/51

41 Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 41/51

42 11 Appendix C: Alcatel-Lucent Enterprise Communication Platform: configuration requirements 11.1 SIP trunk declaration Trunk Group ID: 5 Trunk Group Type: T2 Q931 Signal variant: T2 Specification: SIP ABC-F 11.2 Dialling Plan setup Translate 4-digit external numbers from T1 trunk to 7-digit internal numbers Route calls to 7-digit numbers with prefix 515 to trunk group 5 Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 42/51

43 11.3 Ext SIP Gateway declaration SIP remote domain: IP of XMediusFAX SIP Port Number: 5360 Transport type: UDP TCP Trunk group number: 5 FAX Procedure Type: T38 Only G711 Only Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 43/51

44 11.4 Ext SIP Gateway configuration for Authentication 11.5 Configuration for Spatial redundancy Refer to Open Touch fax Server Release Notes (TC 2016; section 8.6) Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 44/51

45 12 Appendix D: AAPP member s escalation process SAGEMCOM 250, route de l'empereur 27, rue Leblanc Rueil-Malmaison Paris - FRANCE Tel: +33 (0) Support: +33 (0) Fax: +33 (0) Technical support: xmedius.support.emea@sagem.com Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 45/51

46 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 Enterprise's product family. The program provides tools and support for developing, verifying and promoting compliant thirdparty applications that complement Alcatel-Lucent Enterprise's product family. ALE International facilitates market access for compliant applications. The Alcatel-Lucent Application Partner Program (AAPP) has two main objectives: Provide easy interfacing for Alcatel-Lucent Enterprise communication products: Alcatel-Lucent Enterprise'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 Enterprise products. Test and verify a comprehensive range of third-party applications: to ensure proper inter-working, ALE International tests and verifies selected third-party applications that complement its portfolio. Successful candidates, which are labelled Alcatel-Lucent Enterprise 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. Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 46/51

47 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 Enterprise.Alcatel-Lucent.com You can access the Alcatel-Lucent Enterprise website at this URL: Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 47/51

48 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 ALE International Business Partners when facing a problem with the solution certified in this document. The principle is that ALE International 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, ALE International and the Application Partner, are engaged as following: (*) The Application Partner Business Partner can be a Third-Party company or the ALE International Business Partner itself Alcatel-Lucent Application Partner Program Inter-working report - Edition 2 - page 48/51