Alliance & Application Partner Program Inter-Working Report

Transcription

1 Alliance & Application Partner Program Inter-Working Report Partner: NewVoice Application type: Alarm system Application name: MobiCall 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.

2 Tests identification Date of the tests 3 december 2009 Date of regression tests Alcatel-Lucent s representative Partner s representative Bruno Fouarge David Fermet Alcatel-Lucent Communication Platform (OmniPCX 4400/Enterprise, OmniTouch, OmniPCX Office,...) Alcatel-Lucent compatibility release Partner s application version OXE - OmniPCX Enterprise R9.0 (H ) R9.1 (I ) Environment (if it has a sense) ACD Business Author(s): Reviewer(s): Bruno Fouarge Denis Lienhart, Bernard Roth History: 1. Edition 1: Creation Test results Passed Refused Postponed Passed with restrictions Refer to the section 4 for a summary of the test results. Alliance & Application Partner Program Inter-working report Edition 1 - page 2/59

3 Company Contact Information Contact name: Title: Georges Brigati Director Address 1: St. Gallerstrasse 8 Address 2: City: Lachen State: Zip: 8853 Country: Switzerland Country code: CH Phone: Fax: Web address: [email protected] Alliance & Application Partner Program Inter-working report Edition 1 - page 3/59

4 TABLE OF CONTENTS 1 INTRODUCTION APPLICATION INFORMATION TESTS ENVIRONMENT General architecture Hardware configuration Software configuration SUMMARY OF TESTS RESULTS VOICE BASED ALARMS NOTIFICATION ON OMNIPCXENTERPRISE Summary of main functions supported Summary of s Summary of limitations Notes, remarks TEXT BASED ALARMS NOTIFICATION ON OMNIPCXENTERPRISE Summary of main functions supported Summary of s Summary of limitations Notes, remarks TEST SCENARIOS TEST PROCEDURE RESULT TEMPLATE VOICE BASED ALARMS NOTIFICATION ON OMNIPCXENTERPRISE USING QSIG-GF/ ABC-F Text display on ringtone UUI message sent with the call UUI message sent after the call is answered / confirmed Hand free alarm reception Ring cadence differentiation Intrusion UTF8 long text display Voice conference: 2 party conference Voice conference: multiple participant (>2) Start alarm from Alcatel-Lucent phones to MobiCall Localization of DECT phone USING H Text display on ringtone USING SIP TRUNK Text display on ringtone Call reception by MobiCall REDUNDANCY TESTS VOICE BASED ALARM REDUNDANCY TESTS Alarm call reception (Redundant MobiCall ARS configuration) OXE Spatial redundancy OXE spatial redundancy with PCS, MobiCall connected to the PCS TEXT BASED ALARM REDUNDANCY TESTS OXE Spatial redundancy TEXT BASED ALARMS NOTIFICATION Alliance & Application Partner Program Inter-working report Edition 1 - page 4/59

5 8.1 USING PAGING INTERFACE ON OMNIPCXENTERPRISE Connectivity and set-up Surveillance / recovery License tests Functional Tests Sending alarms Acknowledges of alarms APPENDIX A : APPLICATION DESCRIPTION APPLICATION DESCRIPTION TESTS ENVIRONMENT APPENDIX B: ALCATEL-LUCENT COMMUNICATION PLATFORM: CONFIGURATION REQUIREMENTS FOR OMNIPCX ENTERPRISE Trunk (T2) declaration Trunk declaration for H Paging interface declaration XML IP Touch declaration UTF8 Long messages (30 characters on 310/610) APPENDIX C: ALCATEL-LUCENT OMNIPCX ENTERPRISE PLATFORM: LICENCING FOR OMNIPCX ENTERPRISE Trunk (QSIG-GF/ABCF) Trunk declaration for H Trunk declaration for SP Paging interface declaration XML IP Touch declaration UTF8 Long messages (30 characters on 310/610) APPENDIX D: PARTNER ESCALATION PROCESS CONTACT INFORMATION RD PARTY SUPPORT DETAIL Contact General Information Severity Description and Response Times Support Level Definitions Call Flow Description APPENDIX E: AAPP PROGRAM, DOCUMENTATION AND TECHNICAL ASSISTANCE APPENDIX E: ALCATEL-LUCENT ESCALATION PROCESS IN CASE OF PROBLEM WITH A CERTIFIED EXTERNAL APPLICATION (REFERENCED IN THE AAPP) Alliance & Application Partner Program Inter-working report Edition 1 - page 5/59

6 1 Introduction The goal of these tests is to qualify an external application as an Alliance & Application 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. Alliance & Application Partner Program Inter-working report Edition 1 - page 6/59

7 2 Application information Application type: Application commercial name: Alarm server Mobicall Application version: V7.2 Interface type: QSIG-GF (T2 or T0) with ABC-F, Paging Interface version (if relevant): Brief application description: Mobicall is based on a modular and multi-lingual concept with a seamless integration into OmniPCX 4400/Enterprise and OmniPCX Office. The server runs Mobicall Server, which purpose is to post alarms to groups or individuals. The alarm calls can be: manually launched, triggered on call reception, sent from a Web-based client. The server is made of Mobicall services, a Web Apache server and a database (MySql). It could as well connect to any ODBC database. Fore more details, refer to Appendix A. Alliance & Application Partner Program Inter-working report Edition 1 - page 7/59

8 3 Tests environment General architecture The tests are performed on the Alcatel-Lucent AAPP Etesting platform in the following environment: MR 610/310 IP TOUCH serie8 serie 9 OmniPCX Enterprise Main ASCOM 9D24 ABCF link 1 SIP SEPLOS ABCF link 3 OmniPCX Enterprise Remote node DECT GAP DECT GAP+ Mobicall main IP TOUCH serie8 serie 9 On remote ABCF node ABCF link 2 OmniPCX Enterprise StandBy Mobicall standby IP/CSTA/Paging link Hardware configuration Alcatel-Lucent Communication Platform: 3 OmniPCX Enterprise, two in spatial redundancy ( / ), one node linked to the main using ABCF link 3. Three PRA E1 board for the ABFC link between OmniPCX Main and Mobicall Main, for ABCF link between OmniPCX Standby and Mobicall Standby, for ABC-F link between OmniPCX Main and OmniPCX Remote Node. Terminals : DECT MR300/400 in GAP, GAP+, DECT 9D24, WIFI MR 610/310, SIP SEPLOS, IP TOUCH serie 8 and serie 9, IP TOUCH behind the second node. Alliance & Application Partner Program Inter-working report Edition 1 - page 8/59

9 Server application: Mobicall equipment and configuration Mobicall is a pc-based alarming system, which can be installed on any table or in a rack, protected against dust, vibrations and humidity One 17 screen with keyboard and mouse placed in front of a chair is perfect Mobicall should be connected to an uninterrupted power supply with 6 plugs for pc, screen, modem or remote access, ip-boxes Mobicall has one E1 trunk with Q.Sig GF protocol There is one RJ45 plug reserved for the E1 interface from Mobicall-Alarm server to the Alcatel-Lucent Mobicall: 1+2 (RCV-Ring+ Tip) and 4+5 (XMIT_RING+Tip) Software configuration Alcatel-Lucent Communication Platform: OXE R9.0 (H ) and R9.1(i ), with WIFI (OmniAccess 4304), Dect base station IBS. Alliance & Application Partner Program Inter-working report Edition 1 - page 9/59

10 4 Summary of tests results 4.1 Voice based alarms notification on OmniPCXEnterprise Summary of main functions supported The Mobicalll supports : The sending of voice based alarm, with a message of in the ringing state, another message of in the conversation state, and the sending of a mini message of 120 character after the conversation The sending of voice based alarm, with a message of 30 characters in the ringing state, another message of 30 characters in the conversation state, and the sending of a mini message of 120 character after the conversation, on MIPT 310/610 phone only, and only in G or R9.1 (i ), and only in ABC-F link. The acknowledge of the alarm message in the conversation mode, using DTMF. The sending of mini messages of 120 characters only The activation of the loudspeaker to play an announcement message on. Ring cadence differentiation Intrusion UTF8 long text display ( not available on version R9.0, only in G , and R9.1) Play voice messages on answer / confirm Voice conference calls for 2 party calls with recording Voice conference calls for multiple party DECT phone localization Numeric / analog phone localization (Not available in 1.43 version tested of Mobicall) The spatial redundancy of OmniPCX Enterprise CPU, and also the duplication of Mobicall, with two ABC-F trunk. Three protocols support this type of alarms notification: QSIG-GF / ABC-F on T2 or T0 Mobicall with OXE / QSIG-GF ABC-F Features Global status Mobile 300/400 MIPT 310/610 IP Touch Ascom 9D24 MK2 GAP SIP phones ST 2022/2023 ASCOM i75 Display alarms on ringing Display alarms on pick up NA NA Send a User to User information NA NA NA with the call Send a User to User information NA NA NA after answer (or confirm) Call back sender Hand free on alarm reception NA NA NA Ring cadence differentiation NA NA NA Intrusion NA NA NA Alliance & Application Partner Program Inter-working report Edition 1 - page 10/59

11 Localization N N N N Voice conference Start alarm from phone H323 Mobicall with OXE / H323 Features Global status Mobile 300/400 MIPT 310/610 IP Touch Ascom 9D24 MK2 GAP SIP phones ST 2022/ST2023 ASCOM i75 Display alarms on ringing Display alarms on pick up Not Applicable Send a User to User information Not Applicable Call back sender Not Applicable Hand free on alarm reception Not Applicable Voice conference Start alarm from phone Display a picture on ringing Not Applicable SIP Trunk Mobicall with OXE / SIP TRUNK Features Global status Mobile 300/400 MIPT 310/610 IP Touch Ascom 9D24 MK2 GAP SIP phones ST 2022/ST2023 ASCOM i75 Display alarms on ringing Display alarms on pick up Not Applicable Send a User to User information Not Applicable Call back sender Not Applicable Hand free on alarm reception Not Applicable Voice conference Start alarm from phone Display a picture on ringing Not Applicable Alliance & Application Partner Program Inter-working report Edition 1 - page 11/59

12 4.1.2 Summary of s On Mini message (User to User information) : When the length of the User to User information is longer than 120 characters, the message is not sent. This limit depends on the whole message length which include the phone number. Hence this limitation could be 120 to 124 characters, depending on the dial plan. On ring cadence differentiation: When the phone is forwarded (immediate or not), the call is lost, and is in status failed on Mobicall. The MobiCall system has to be configured to ignore call forward. On alarm with call announcement on loud speacker : When the called device is a Dect phone out of service, or out of coverage, the message is not play on the phone, but the Mobicall return a status Done. This is referenced as SR Summary of limitations Mobicall is not able to manage the case where the destination device is forwarded to another one Notes, remarks None Alliance & Application Partner Program Inter-working report Edition 1 - page 12/59

13 4.2 Text based alarms notification on OmniPCXEnterprise Summary of main functions supported The Mobical supports: The sending of normal alarm, with or without acknowledge, of urgent alarm with of without acknowledge, of discrete alarm with or without acknowledge. Each alarm is a text message of 128 characters maximum. The specification of cadence ringing type in the alarm from 1 to 8 : where 1 = xx_xx 2 = xxx 3 = xxxxxxxxx 4 = x_x_x_x_x 5 = x x x 6 = xxx 7 = xxx 8 = xxx x is the ringtone _ is a silence The acknowledge of alarm The OmniPCX Enterprise spatial redundancy Mobicall with OXE / Paging Features Global status Mobile 300/400 MIPT 310/610 IP Touch Ascom 9D24MK2 GAP SIP phones ST2022/ST2023 ASCOM i75 Display alarms on ringing NA NA NA Display alarms on pick up NA NA NA Send a User to User information Not Applicable Call back sender Not Applicable Hand free on alarm reception Not Applicable Voice conference + recording Not Applicable Display a picture on ringing Not Applicable Summary of s None Summary of limitations The Mobicall doesn t support the delete of sent alarm Notes, remarks None Alliance & Application Partner Program Inter-working report Edition 1 - page 13/59

14 5 Test Scenarios 5.1 Test procedure 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. Origin of the : this column has to be filled in when a 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 s. 5.2 Result template The results table must be formatted as indicated in the example below: 1. action 1 2. action 2 3. action 3 4. action 4 5. action 5 X N The application waits for PBX timer or phone set hangs up Relevant only if the CTI interface is a direct CSTA link No indication, no error message Alliance & Application Partner Program Inter-working report Edition 1 - page 14/59

15 6 Voice based alarms notification on OmniPCXEnterprise 6.1 Using QSIG-GF/ ABC-F The tests cover following scenarios: Calls from Mobicall to OmniPCX Enterprise (OXE) phones Display 16 digit name on phones while calling Display 16 digit name on phones on answer Send a User to User message with the call Send a User to User message after the call is answered / confirmed Hand free alarm reception Ring cadence differentiation Intrusion UTF8 long text display ( not available on version R9.0 tested, only in G , and R9.1) Play voice messages on answer / confirm Voice conference calls for 2 party calls with recording Voice conference calls for multiple party DECT phone localization Numeric / analog phone localization (Not available in 1.43 version tested of Mobicall) Text display on ringtone Test Definition MobiCall calls all phones of the list All phones are respectively not forwarded, in immediate forward, in forward on busy and out of service A 16 character text display is configured A voice prompt is played. Possible alarm confirmation by key On not forwarded set 1 From Alcatel-Lucent Mobile 300/400 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 4 On GAP handset 5 On Alcatel-Lucent IP Touch 6 On SIP phones (Thomson 20x0) 7 On ASCOM I75 16 character 14 characters only Alliance & Application Partner Program Inter-working report Edition 1 - page 15/59

16 8 On Alcatel-Lucent IP Touch attached to a distant OXE node On forwarded set (immediate) 1 From Alcatel-Lucent Mobile 300/400 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 4 On GAP handset 5 On Alcatel-Lucent IP Touch 6 On SIP phones (Thomson 20x0) 7 On ASCOM I75 8 On Alcatel-Lucent IP Touch attached to a distant OXE node 14 characters only Trunk name -> forwarded On forwarded set (on busy) 1 From Alcatel-Lucent Mobile 300/400 * 2 On Alcatel-Lucent MIPT 310/610 * 3 On Ascom 9d24 MK2 * 4 On GAP handset * 14 characters only 5 On Alcatel-Lucent IP Touch * 6 On SIP phones (Thomson 20x0) * 7 On ASCOM I75 * 8 On Alcatel-Lucent IP Touch attached to a distant OXE node * * the display of the texte message in ringing is depending on the display of the forward on the terminal. Not are On set out of service 1 From Alcatel-Lucent Mobile 300/400 * 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 * 4 On GAP handset * 5 On Alcatel-Lucent IP Touch * 6 On SIP phones (Thomson 20x0) * 7 On ASCOM I75 8 On Alcatel-Lucent IP Touch attached to a distant OXE node Trace on on 610 Destination out of order : 0x9B Destination out of order : 0x9B Destination out of order : 0x9B Alliance & Application Partner Program Inter-working report Edition 1 - page 16/59

17 * On phones where the status is out of service, the Mobicall reports that the alarm has been presented on the phone. Text display on answer Test Definition MobiCall calls all phones of the list All phones are respectively not forwarded, in immediate forward, in forward on busy and out of service A 16 character text display is configured A different 16 character text on answer is configured A voice prompt is played. Possible alarm confirmation by key On not forwarded set 1 From Alcatel-Lucent Mobile 300/400 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 4 On GAP handset 5 On Alcatel-Lucent IP Touch 6 On SIP phones (Thomson 20x0) 7 On ASCOM I75 8 On Alcatel-Lucent IP Touch attached to a distant OXE node Trace on on IP touch On forwarded set (immediate) The alarm is forwarded on forward destination phone. 1 From Alcatel-Lucent Mobile 300/400 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 4 On GAP handset 5 On Alcatel-Lucent IP Touch 6 On SIP phones (Thomson 20x0) 7 On ASCOM I75 8 On Alcatel-Lucent IP Touch attached to a distant OXE node N/A N/A No message in conversation No message in conversation No message in conversation No message in conversation Alliance & Application Partner Program Inter-working report Edition 1 - page 17/59

18 6.1.2 UUI message sent with the call Test Definition MobiCall calls all phones of the list All phones are respectively not forwarded, in immediate forward, in forward on busy and out of service A 16 character text display is configured A different 16 character text on answer is configured A User to User Information message is sent to the phone with the call A voice prompt is played. Possible alarm confirmation by key On not forwarded set 1 From Alcatel-Lucent Mobile 300/400 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 4 On GAP handset N/A 5 On Alcatel-Lucent IP Touch 6 On SIP phones (Thomson 20x0) N/A 7 On ASCOM I75 N/A 8 On Alcatel-Lucent IP Touch attached to a distant OXE node * : if message greather than 120 char, no message is received on phone and Mobicall get no status. Only with message of 120 char max, after * Only with message of 120 char max, after * Only with message of 120 char max, after * Only with message of 120 char max, after * On forwarded set (immediate) The call is forwarded. The text message is delivered on the called device, not on the forward destination. 1 From Alcatel-Lucent Mobile 300/400 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 4 On GAP handset N/A 5 On Alcatel-Lucent IP Touch 6 On SIP phones (Thomson 20x0) N/A 7 On ASCOM I75 N/A 8 On Alcatel-Lucent IP Touch attached to a distant OXE node Trace generated : message received on IP TOUCH forwarded on MR On forwarded set (on busy) The call is forwarded. The text message is delivered on the called device, not on the forward destination. Alliance & Application Partner Program Inter-working report Edition 1 - page 18/59

19 1 From Alcatel-Lucent Mobile 300/400 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 4 On GAP handset N/A 5 On Alcatel-Lucent IP Touch 6 On SIP phones (Thomson 20x0) N/A 7 On ASCOM I75 N/A 8 On Alcatel-Lucent IP Touch attached to a distant OXE node UUI message sent after the call is answered / confirmed Test Definition MobiCall calls all phones of the list All phones are respectively not forwarded, in immediate forward, in forward on busy and out of service A 16 character text display is configured A different 16 character text on answer is configured A User to User Information message is sent to the phone when the call is answered A voice prompt is played. Possible alarm confirmation by key On not forwarded set 1 From Alcatel-Lucent Mobile 300/400 * 2 On Alcatel-Lucent MIPT 310/610 * 3 On Ascom 9d24 MK2 * 4 On GAP handset N/A ** 5 On Alcatel-Lucent IP Touch * 6 On SIP phones (Thomson 20x0) N/A ** 7 On ASCOM I75 N/A ** 8 On Alcatel-Lucent IP Touch attached to a distant OXE node * *Trace 6142 generated : code de retour ISDN 9F : unspeficied cause. ** code 90 normal clearing received On forwarded set (immediate) The call is forwarded. The text message is delivered on the called device, not on the forward destination. 1 From Alcatel-Lucent Mobile 300/400 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 4 On GAP handset N/A 5 On Alcatel-Lucent IP Touch Alliance & Application Partner Program Inter-working report Edition 1 - page 19/59

20 6 On SIP phones (Thomson 20x0) N/A 7 On ASCOM I75 N/A 8 On Alcatel-Lucent IP Touch attached to a distant OXE node On forwarded set (on busy) The call is forwarded. The text message is delivered on the called device, not on the forward destination. 1 From Alcatel-Lucent Mobile 300/400 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 4 On GAP handset N/A 5 On Alcatel-Lucent IP Touch 6 On SIP phones (Thomson 20x0) N/A 7 On ASCOM I75 N/A 8 On Alcatel-Lucent IP Touch attached to a distant OXE node Hand free alarm reception Test Definition MobiCall calls all phones of the list All phones are respectively not forwarded, in immediate forward, in forward on busy and out of service A 16 character text display is configured A different 16 character text on answer is configured A User to User Information message is sent to the phone when the call is answered The phone automatically answers the call on the loudspeaker A voice prompt is played. Possible alarm confirmation by key On not forwarded set 1 From Alcatel-Lucent Mobile 300/400 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 4 On GAP handset N/A 5 On Alcatel-Lucent IP Touch 6 On SIP phones (Thomson 20x0) N/A 7 On ASCOM I75 N/A 8 On Alcatel-Lucent IP Touch attached to a distant OXE node On forwarded set (immediate) The call is forwarded. The text message is delivered on the called device, not on the forward destination. Alliance & Application Partner Program Inter-working report Edition 1 - page 20/59

21 1 On forward to Alcatel-Lucent Mobile 300/400 2 On forward to Alcatel-Lucent MIPT 310/610 3 On forward to Ascom 9d24 MK2 4 On forward to GAP handset N/A 5 On forward to Alcatel-Lucent IP Touch 6 On forward to SIP phones (Thomson 20x0) N/A 7 On forward to ASCOM I75 N/A 8 On forward to Alcatel-Lucent IP Touch attached to a distant OXE node On forwarded set (on busy) 1 On forward to Alcatel-Lucent Mobile 300/400 2 On forward to Alcatel-Lucent MIPT 310/610 3 On forward to Ascom 9d24 MK2 4 On forward to GAP handset N/A 5 On forward to Alcatel-Lucent IP Touch 6 On forward to SIP phones (Thomson 20x0) N/A 7 On forward to ASCOM I75 N/A 8 On forward to Alcatel-Lucent IP Touch attached to a distant OXE node Ring cadence differentiation Test Definition MobiCall calls all phones of the list All phones are respectively not forwarded, in immediate forward, in forward on busy and out of service A 16 character text display is configured A different 16 character text on answer is configured A User to User Information message is sent to the phone when the call is answered The call ring cadence is different from a normal call : this use the cadence specified in the OmniPCX parameter boss/secretary cadency field. A voice prompt is played. Possible alarm confirmation by key On not forwarded set Alliance & Application Partner Program Inter-working report Edition 1 - page 21/59

22 1 From Alcatel-Lucent Mobile 300/400 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 4 On GAP handset N/A 5 On Alcatel-Lucent IP Touch 6 On SIP phones (Thomson 20x0) N/A 7 On ASCOM I75 N/A 8 On Alcatel-Lucent IP Touch attached to a distant OXE node The executive cadency must be managed on the remote node also On forwarded set (immediate) 1 On forward to Alcatel-Lucent Mobile 300/400 N * 2 On forward to Alcatel-Lucent MIPT 310/610 N * 3 On forward to Ascom 9d24 MK2 N * 4 On forward to GAP handset N/A * 5 On forward to Alcatel-Lucent IP Touch N * 6 On forward to SIP phones (Thomson 20x0) N/A 7 On forward to ASCOM I75 N/A 8 On forward to Alcatel-Lucent IP Touch attached to a distant OXE N * node * : the call is lost, no phone rings. An error ISDN error is received by the Mobicall. Call is in status failed on Mobicall On forwarded set (on busy) 1 On forward to Alcatel-Lucent Mobile 300/400 N * 2 On forward to Alcatel-Lucent MIPT 310/610 N * 3 On forward to Ascom 9d24 MK2 N * 4 On forward to GAP handset N/A * 5 On forward to Alcatel-Lucent IP Touch N * 6 On forward to SIP phones (Thomson 20x0) N/A 7 On forward to ASCOM I75 N/A 8 On forward to Alcatel-Lucent IP Touch attached to a distant OXE N * node * : the call is lost, no phone rings. An error ISDN error is received by the Mobicall. Call is in status failed on Mobicall. Alliance & Application Partner Program Inter-working report Edition 1 - page 22/59

23 6.1.6 Intrusion Test Definition MobiCall calls all phones of the list All phones are mono-line and in conversation A 16 character text display is configured A different 16 character text on answer is configured A User to User Information message is sent to the phone when the call is answered The called phone hears a call presentation beep and hears the alarm message. A voice prompt is played Test result 1 From Alcatel-Lucent Mobile 300/400 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 4 On GAP handset N/A 5 On Alcatel-Lucent IP Touch 6 On SIP phones (Thomson 20x0) N/A 7 On ASCOM I75 N/A 8 On Alcatel-Lucent IP Touch attached to a distant OXE node UTF8 long text display Test Definition This function is only availble in G or R9.1 release, and on MIPT 310/610. See Appendix 10 for OXE specific configuration. MobiCall calls all phones of the list All phones are respectively not forwarded, in immediate forward, in forward on busy and out of service A 30 character text display is configured A different 30 character text on answer is configured A User to User Information message is sent to the phone when the call is answered A voice prompt is played. Possible alarm confirmation by key 3. The handset is in DTMF transparency after the connect. When the handset is busy, a pop-up window is On not forwarded set 1 From Alcatel-Lucent Mobile 300/400 N/A 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 N/A 4 On GAP handset N/A 5 On Alcatel-Lucent IP Touch N/A Alliance & Application Partner Program Inter-working report Edition 1 - page 23/59

24 6 On SIP phones (Thomson 20x0) N/A 7 On ASCOM I75 N/A 8 On Alcatel-Lucent IP Touch attached to a distant OXE node N/A On forwarded set (immediate) 1 From Alcatel-Lucent Mobile 300/400 N/A 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 N/A 4 On GAP handset N/A 5 On Alcatel-Lucent IP Touch N/A 6 On SIP phones (Thomson 20x0) N/A 7 On ASCOM I75 N/A 8 On Alcatel-Lucent IP Touch attached to a distant OXE node N/A On forwarded set (on busy) 1 From Alcatel-Lucent Mobile 300/400 N/A 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 N/A 4 On GAP handset N/A 5 On Alcatel-Lucent IP Touch N/A 6 On SIP phones (Thomson 20x0) N/A 7 On ASCOM I75 N/A 8 On Alcatel-Lucent IP Touch attached to a distant OXE node N/A Voice conference: 2 party conference Test Definition MobiCall receives a call from any type of phone MobiCall calls a phone and sets up the conference once the called phone answers A 16 character text display is configured A different 16 character text on answer is configured A User to User Information message is sent to the phone with the call The conference is recorded Test result 1 MobiCall receives a call from any type of phone Alliance & Application Partner Program Inter-working report Edition 1 - page 24/59

25 2 MobiCall calls a phone and sets up the conference once the called phone answers 3 A 16 character text display is configured 4 A User to User Information message is sent to the phone with the call 5 The conference is recorded Voice conference: multiple participant (>2) Test Definition MobiCall receives a call from any type of phone MobiCall calls several phones and sets up the conference once at least on called phone answers. Other participants join the conference as they answer. A 16 character text display is configured A different 16 character text on answer is configured Test result 1 MobiCall receives a call from any type of phone 2 MobiCall calls several phones and sets up the conference once at least on called phone answers. Other participants join the conference as they answer 3 A 16 character text display is configured Start alarm from Alcatel-Lucent phones to MobiCall Test Definition Each phone calls the MobiCall extension number to start an alarm A voice prompt is played, asking to record a voice message The alarm is started and the recorded voice message played to the called phones Test result 1 A phone calls the MobiCall extension number to start an alarm Alliance & Application Partner Program Inter-working report Edition 1 - page 25/59

26 2 A voice prompt is played, asking to record a voice message 3 The alarm is started and the recorded voice message played to the called phones Localization of DECT phone Test Definition Each phone calls the MobiCall extension number to start the localization process MobiCall starts an alarm according to the DECT base station that has been localized Test result 1 From Alcatel-Lucent Mobile 300/400 2 On Alcatel-Lucent MIPT 310/610 X 3 On Ascom 9d24 MK2 4 On GAP handset 5 On Alcatel-Lucent IP Touch X 6 On SIP phones (Thomson 20x0) X 7 On ASCOM I75 X 8 On Alcatel-Lucent IP Touch attached to a distant OXE node X Alliance & Application Partner Program Inter-working report Edition 1 - page 26/59

27 6.2 Using H323 The tests cover the same scenario than using QSIG Calls from Mobicall to OmniPCX Enterprise (OXE) phones Text display on ringtone Test Definition MobiCall calls all phones of the list All phones are respectively not forwarded, in immediate forward, in forward on busy and out of service A 16 character text display is configured A voice prompt is played. Possible alarm confirmation by key On not forwarded set 1 From Alcatel-Lucent Mobile 300/400 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 4 On GAP handset 5 On Alcatel-Lucent IP Touch 6 On SIP phones (Thomson 20x0) 7 On ASCOM I75 8 On Alcatel-Lucent IP Touch attached to a distant OXE node 14 characters On forwarded set (immediate) 1 From Alcatel-Lucent Mobile 300/400 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 4 On GAP handset 5 On Alcatel-Lucent IP Touch 6 On SIP phones (Thomson 20x0) 7 On ASCOM I75 8 On Alcatel-Lucent IP Touch attached to a distant OXE node 14 characters only Trunk name -> forwarded Alliance & Application Partner Program Inter-working report Edition 1 - page 27/59

28 On forwarded set (on busy) 1 From Alcatel-Lucent Mobile 300/400 * 2 On Alcatel-Lucent MIPT 310/610 * 3 On Ascom 9d24 MK2 * 4 On GAP handset * 14 characters only 5 On Alcatel-Lucent IP Touch * 6 On SIP phones (Thomson 20x0) * 7 On ASCOM I75 * 8 On Alcatel-Lucent IP Touch attached to a distant OXE node * * the display of the texte message in ringing is depending on the display of the forward on the terminal. Not are Alliance & Application Partner Program Inter-working report Edition 1 - page 28/59

29 6.3 Using SIP trunk The tests cover the same scenario than using QSIG Calls from Mobicall to OmniPCX Enterprise (OXE) phones Text display on ringtone Test Definition MobiCall calls all phones of the list All phones are respectively not forwarded, in immediate forward, in forward on busy and out of service A 16 character text display is configured A voice prompt is played. Possible alarm confirmation by key On not forwarded set 1 From Alcatel-Lucent Mobile 300/400 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 4 On GAP handset 5 On Alcatel-Lucent IP Touch 6 On SIP phones (Thomson 20x0) 7 On ASCOM I75 8 On Alcatel-Lucent IP Touch attached to a distant OXE node On forwarded set (immediate) 1 From Alcatel-Lucent Mobile 300/400 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 4 On GAP handset 5 On Alcatel-Lucent IP Touch 6 On SIP phones (Thomson 20x0) 7 On ASCOM I75 8 On Alcatel-Lucent IP Touch attached to a distant OXE node Alliance & Application Partner Program Inter-working report Edition 1 - page 29/59

30 On forwarded set (on busy) 1 From Alcatel-Lucent Mobile 300/400 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 4 On GAP handset 5 On Alcatel-Lucent IP Touch 6 On SIP phones (Thomson 20x0) 7 On ASCOM I75 8 On Alcatel-Lucent IP Touch attached to a distant OXE node * the display of the texte message in ringing is depending on the display of the forward on the terminal. Not are Call reception by MobiCall Test Definition Any phone on the list dials a number directed to the MobiCall server MobiCall receives the call and starts an incoming call scenario Call reception by MobiCall from a phone from the network 1 From Alcatel-Lucent Mobile 300/400 2 On Alcatel-Lucent MIPT 310/610 3 On Ascom 9d24 MK2 4 On GAP handset 5 On Alcatel-Lucent IP Touch 6 On SIP phones (Thomson 20x0) 7 On ASCOM I75 8 On Alcatel-Lucent IP Touch attached to a distant OXE node?? Alliance & Application Partner Program Inter-working report Edition 1 - page 30/59

31 7 Redundancy tests 7.1 Voice based alarm redundancy tests The purpose of this section is to test the Alcatel-Lucent OXE with MobiCall in different topologies of redundancy, and illustrate that all redundancy failover mechanism are available Alarm call reception (Redundant MobiCall ARS configuration) Test Definition An Alcatel Lucent phone calls a MobiCall extension number to start an alarm This extension number is configured with ARS, and respectively routed to MobiCall master server and slave server The alarm is started in any case whether the master or the slave is down Test result 1 From any Alcatel-Lucent phone, Call the extension with MobiCall master server down 2 From any Alcatel-Lucent phone, Call the extension with MobiCall master server down OXE Spatial redundancy Test Definition A MobiCall server is connected to a GD in spatial redundancy MobiCall starts an alarm call to any type of Alcatel-Lucent phone or MobiCall starts a conference between two Alcatel-Lucent phones The CPU switch is done before and during a call / conference The alarm call or conference is handled / uncut in any case Switch before a call emission by MobiCall 1 MobiCall calls any Alcatel-Lucent phone * Switch during a call emission by MobiCall Alliance & Application Partner Program Inter-working report Edition 1 - page 31/59

32 1 MobiCall calls any Alcatel-Lucent phone, and is in conversation with thoses phones. ** Switch before a conference hosted by MobiCall 1 MobiCall receives a call from any Alcatel-Lucent phone, and calls any Alcatel-Lucent phone to establish a conference The calls which are in ringing state when the bascul happens, are lost Switch during a conference hosted by MobiCall 1 MobiCall receives a call from any Alcatel-Lucent phone, and calls any Alcatel-Lucent phone to ** establish a conference * On a IP TOUCH attached thought ABC-F on IP link, the call cannot be delivered until the ABCF link between the two OmniPCX Enterprise goes up. This link is broken during the bascul. ** On a IP TOUCH attached thought ABC-F on IP link, the call is lost, because the ABCF link goes down OXE spatial redundancy with PCS, MobiCall connected to the PCS Test Definition A MobiCall server is connected to a PCS, connected to an OXE in spatial redundancy MobiCall starts an alarm call to any type of Alcatel-Lucent phone (attached to the PCS) or MobiCall starts a conference between two Alcatel-Lucent phones (attached to the PCS) The link between the PCS and the CPUs is cut before and during a call / conference The alarm call or conference is handled / uncut in any case When the PCS takes the CPU MAIN role, all the phones reboot. Hence no alarm can be received by phone until the end of the phone reboot. This is the normal OmniPCX Enterprise behaviour Switch before a call emission by MobiCall 1 MobiCall calls any Alcatel-Lucent phone The phone on the PCS reboot, when the PCS became MAIN Switch during a call emission by MobiCall Alliance & Application Partner Program Inter-working report Edition 1 - page 32/59

33 1 MobiCall calls any Alcatel-Lucent phone X All the communication are lost during the bascul on PCS Switch before a conference hosted by MobiCall 1 MobiCall receives a call from any Alcatel-Lucent phone, and calls any Alcatel-Lucent phone to establish a conference Switch during a conference hosted by MobiCall 1 MobiCall receives a call from any Alcatel-Lucent phone, and calls any Alcatel-Lucent phone to X establish a conference All the communication are lost during the bascul on PCS 7.2 Text based alarm redundancy tests The purpose of this section is to test the Alcatel-Lucent OXE with MobiCall in different topologies of redundancy, and illustrate that all redundancy failover mechanism are available OXE Spatial redundancy Test Definition A MobiCall server is connected to OmniPCX Enterprise using CSTA. The OmniPCX Enterprise CPU bascul on the standby CPU. MobiCall starts an alarm call to alcatel-lucent phone Switch before a call emission by MobiCall 1 MobiCall calls any Alcatel-Lucent phone The mobicall supports the switch of CPU, in spatial redundancy The Paging link must be established on the new MAIN CPU, after the bascul. This takes 10 seconds, when no Paging alarm can be sent. The Mobicall waits for the establishment of the link to send thoses alarms. Alliance & Application Partner Program Inter-working report Edition 1 - page 33/59

34 8 Text based alarms notification 8.1 Using Paging Interface on OmniPCXEnterprise Connectivity and set-up Test objectives These tests shall verify that the different components are properly connected and can communicate together (the external application and the Alcatel-Lucent-Lucent Communication Platform are connected and the interface link is operational) Test procedure 1 Connect the application, checks if there are incident messages using «incvisu» command 2 Check using the http interface of the cstamono (port 2555) that the application is connected Alliance & Application Partner Program Inter-working report Edition 1 - page 34/59

35 8.1.2 Surveillance / recovery Test objectives Check how will react the application in case of a PBX reboot, switch-over or link failure Test procedure 1 Disconnect the IP interface between the OXE and the application server. 2 Use the application to send an message 3 Reconnect the IP interface, and check if the application is connected again. 4 Check if the previously message is sent to the OXE 5 Reboot the OXE, and then send a message using the application 6 Check if the application is connected again 7 Check if the previously message is sent The alarm is not sent, an error message is in mobicall The connection is done again The message is not sent The alarm is not sent, an error message is in mobicall The connection is done again The message is not sent Alliance & Application Partner Program Inter-working report Edition 1 - page 35/59

36 8.1.3 License tests Test objectives These tests shall verify that the application is working using the following rules : If the Notification Server lock on the OXE is strictly less than 50, the link is broken, and the application stops. If the Notification Server lock on the OXE is more or equal than 50, the application runs Test procedure 1 Put an Notification Server lock of 10, an run the application. 2 Try to send an message using the application. Alliance & Application Partner Program Inter-working report Edition 1 - page 36/59

37 8.1.4 Functional Tests Sending alarms These tests shall verify that the application is able to send urgent and normal alarms 1 Send a normal alarm without ack 0 2 Send a normal alarm with ack 1 3 Send a urgent alarm without ack 2 4 Send a urgent alarm with ack 3 3 Delete a sent alarm 4 Send a discrete alarm 4 5 Send a discrete alarm 5! on front alarm * on front alarm # is on front alarm The phone doesn t ring. is on front alarm # is on front alarm The phone doesn t ring. is on front alarm PagingRequestType ActiveAlarmCall value 0 - to send an alarm (text message) StopAlarmCall value 1 - to delete a previous alarms AskSotwarePack value 2 - to get current licenses ActiveSndCall value 3 - to send a discrete alarm PagingPriority NormalNoAck value 0 NormalAck value 1 UrgentNoAck value 2 UrgentAck value 3 NormalSndCall value Acknowledges of alarms These tests shall verify that the application is able to manage the acknowledge of an alarm. 1 Send a normal alarm, and verify that acknowledge : phone ring is 2 Read the alarm and acknowledge it. Check status read in the application Alliance & Application Partner Program Inter-working report Edition 1 - page 37/59

38 3 Send a alarm to a phone our of service 4 Send a alarm to a phone without the Notification Server right. PagingState protocol values : Alert value 0 - the message is stored (ringing state) Process value 1 - the message is read or acknowledged OutOfCoverage value 2 - the destination is out of radio coverage OutOfservice value 4 - the destination is out of service Undefined value 5 - destination not declared as a NS device NoAlert value 6 - the alarm cannot be deposit SPNoser value 7 - used for licenses validation Alliance & Application Partner Program Inter-working report Edition 1 - page 38/59

39 Sending alarms These tests shall verify that the application is able to send urgent and normal alarms. Using Mobicall the difference between a normal and an urgent alarm is the tones ringing. For an normal alarm, the ringing tones specified in the protocol is 1, for an urgent alarm it is 4. 1 Phone Set connected and in service. Send a normal alarm 2 Phone Set connected and in service. Send an urgent alarm 3 Phone Set out of service. Send a normal alarm 4 Phone Set out of service. Send an urgent alarm 5 Phone Set in a call. Send a normal alarm 6 Phone Set in a call. Send an urgent alarm 7 Phone Set forwarded. Send a normal alarm 8 Phone Set forwarded. Send an urgent alarm Acknowledges of alarms These tests shall verify that the application is able to manage the acknowledge of an alarm. 1 Phone Set connected and in service. Send a normal alarm, and read it on the phone 2 Phone Set connected and in service. Check its state in the application 3 Phone Set out of service. Send a normal alarm, and read it on the phone 4 Phone Set out of service. Check its state in the application 5 Phone Set in a call. Send a normal alarm, and read it on the phone 6 Phone Set in a call. Check its state in the application Alliance & Application Partner Program Inter-working report Edition 1 - page 39/59

40 7 Phone Set forwarded. Send a normal alarm, and read it on the phone 8 Phone Set forwarded. Check its state in the application PagingState protocol values : Alert value 0 - the message is stored (ringing state) Process value 1 - the message is read or acknowledged OutOfCoverage value 2 - the destination is out of radio coverage OutOfservice value 4 - the destination is out of service Undefined value 5 - destination not declared as a NS device NoAlert value 6 - the alarm cannot be deposit SPNoser value 7 - used for licenses validation Alliance & Application Partner Program Inter-working report Edition 1 - page 40/59

41 9 Appendix A : Application description 9.1 Application description Mobicall system overview Mobicall is based on 4 elements allocated to the server. These are fully integrated: The suppliers of information which bring the information to the Mobicall server. The receivers of information which receive the information from the Mobicall server. The Personnel-, Group & Alarm data which defines the way the information input is processed. Supervision & Analysis provides the user with all the required statistics for adequate management of the system. * Suppliers of information Mobicall basically supports all interfaces which are supported by standard computer systems. It is essential that the interfaces be reliable and, if possible, supervised by any kind of watchdogconcepts. Here are some examples: Supervision of contacts free of potential Integration of fire and intrusion detection systems Links to building management systems / SPS Nurse calls, heart alarm, emergency calls Launching alarms by phone calls, SMS, , mouse, key-board and screen, fax, internet / Web Connections through com-port interface, also ESPA Data connection over SNMP, TCP/IP, Socket, FTP, Netsend... * Receivers of information In principle, Mobicall supports all interfaces which are backed by standard computer systems. It is essential that the calls are confirmed by the person answering the call so that Mobicall may function successfully and continue mobilization. Depending on the situation, Mobicall may start the escalation and call upon additional persons. Calls with clear messages (Voice) to internal and external phones Text-messages to DECT phones and other system phone sets Text-messages sent as SMS to GSM mobile phones and pager Alarm messages and information sent by fax and or Broadcasting onto loudspeaker system Alarm signal through broadcast to any PC-system in the network Emergency calls through SNMP, FTP, contacts (relays free of potential, others Support of any H.323 terminal with Voice-over-IP connection * Personnel & Group Data Every person to be contacted by Mobicall has a record containing access numbers (e.g. telephone, fax, pager, ) and function. Information receivers can be assigned to groups. In a matrix the various receivers with their particular identification (telephone number, address, ) can be selected and allocated to the respective groups. Depending on the concept of the mobilization and the definition of the processes, a person may have several telephone numbers assigned. Alliance & Application Partner Program Inter-working report Edition 1 - page 41/59

42 * Supervision & Analysis The analysis of an event includes printing by a local or remote network printer. An automatic printout at the time of the event is also feasible by fax or by . The printout shows the time, the calls were executed to the receivers, whether the called party answered, was busy or did not answer. It also shows a statistic of the calls answered, occupied or not answered, in percentage and in accordance with their escalation level. Mobicall - top spot Mobicall supports both mobilization types: Sequential (search for first success) and Parallel (e.g. all members of a group at the same time) and a combination of both. Mobicall is able to record conversations also in combination with configurable ACD concepts. If a number is busy, the next numbers and groups are dialed, until one answers the call. Mobicall also supports the free combination of traditional telephony and Voice over IP (MobiNETcall). Mobicall supports broadcasting. A recorded message can be sent to comfort-phones. Their loudspeakers will automatically open to play the message. Mobicall allows to call people according to their function and skills: e.g. Three avalanche rescue dogs, five policemen, two detonation-experts. The Web-Interface / Mobicall Messenger! Mobicall systems may be configured and monitored by using a web browser. IP-Box Contact Controller The contact controller with TCP/IP or V.24 - link! Client specific watch-dog concepts Mobicall Alcatel-Lucent-Lucent OmniPCX integration Mobicall is based on a modular and multi-lingual concept with a seamless integration into OmniPCX 4400/Enterprise and OmniPCX Office by using Q-SIG GF link. The overall solution DECT OmniPCX 4400-Enterprise / OmniPCX Office Mobicall has unique selling points to replace pager-based solution. These are: Multi-line DECT, never occupied, can receive alarm calls at any time. Showing display messages while the handset is ringing. Showing a new display message during answer. Combination of voice messages and display-text supporting confirmation by answer, confirm with key 3, cancel with key 4, password or id and password. Showing a confirmation text when launching a conference call. An important number of installed systems, satisfied customers and resellers and a growing demand for DECT Alcatel-Lucent-Lucent OmniPCX Mobicall gives reasons to certify this solution for a better promotion all over the world. Return of investment with additional features by combining other interfaces of the Alcatel-Lucent- Lucent OmniPCX for intrusion, broadcast, sending mini-message and more! Alliance & Application Partner Program Inter-working report Edition 1 - page 42/59

43 Alliance & Application Partner Program Inter-working report Edition 1 - page 43/59

44 Mobicall the components Alarm configurator; Every alarm contact can be individually identified and configured with individual attributes. Personnel & group editor; In a matrix alarm receivers with identification (telephone number, address and others) can be assigned to groups. Alarm evaluation and presentation; It is possible at any time to analyze mobilizations. The alarm view program visualizes running or previous alarms. Scheduler year / week; The scheduler allows to specify the work shifts individually. Also, the responsible person for the 24 hour-hotline support can be specified. Alarm launcher; All defined alarms can be launched manually for testing and training purposes. Every launched alarm is reported and traced. Alarm simulation; Different alarm simulations can be defined and stored for repetitive testing. Alarms and escalations are running as defined without disturbing anything. Test dial program; This feature allows to test easily all features of outbound calls. Post job-manager / configurator; Lists all queued jobs. Jobs may be stopped or cancelled by the system administrator. Timer job-program; This screen shows all jobs that are queued for later execution. Jobs may be started prematurely or cancelled. Voic configurator - Backup-tool - Centralised management - IP-box - Information/configuration of the system - Watchdog - Fax server and more Mobicall system variety Mobicall is a completely modular system that can be assembled to your needs. Mobicall may grow with your demand. It allows you to start with a basic set-up and add more functionality to your system for the future, without losing the investments already made. If an interface is not yet available, our customer support group is at your disposal to develop an interface according to your needs or specifications. Mobicall is available in six languages: German, French, Italian, English, Spanish and Chinese. Alliance & Application Partner Program Inter-working report Edition 1 - page 44/59

45 Mobicall typical applications Mobicall stands for: simple and clear solutions with a guaranteed inexpensive integration in the existing workflow and infrastructure. Alliance & Application Partner Program Inter-working report Edition 1 - page 45/59

46 9.2 Tests environment Mobicall equipment and configuration Mobicall is a PC-based alarming system, which can be installed on any table or in a rack, protected against dust, vibrations and humidity. One 17 screen with keyboard and mouse placed in front of a chair is perfect. Mobicall should be connected to an uninterrupted power supply with 6 plugs for PC, screen, modem for remote access, IP-boxes Mobicall has one E1 trunk with Q-SIG GF protocol. There is one RJ45 plug reserved for the E1 interface from Mobicall-Alarm server to the Alcatel-Lucent OmniPCX Office. Mobicall: 1+2 (RCV-Ring+ Tip) and 4+5 (XMIT_RING+Tip). Diva Server configuration Launch the Diva Configuration Manager from the "Diva Server for Windows 2000" folder in the start menu. Choose Advanced in the View menu: Remove all RAS links, starting from the last in case of "4BRI" Adapter (either the parameter "Extension Collected by" cannot be set to "Application"). Configure all other parameters as shown here above, particularly the ones shown in red. Alliance & Application Partner Program Inter-working report Edition 1 - page 46/59

47 Application Configuration files These files are located in C:\WINNT: NVT.INI: [D300] Alcatel-LucentCallingName = 2 (default was 0) Nvammsg.ini [Messages] 7000 = J'ai perdu les clés du garage 7001 = Cave inondée Set an alarm voice message up From the "Centrale d'alarme Mobicall" window, select an alarm From the contextual menu, select "Enregistrer un message d'alarme" "Enregistrer et écouter le message en appelant le": type the Reflex terminal from where you will record the message.for example, 100. Unhook the extension set (100 in our example). Activate MF Type 1 (Enregistrer). Speak Type any key to validate Type 2 to listen and check the voice message. Type 3 to validate Set-up groups for sending in parallel or serially From the "Centrale d'alarme Mobicall" window, on the right panel, edit the persons Add the subscribers such as 101, 102, 104, 107, 110 and 149. Edit the groups and create one containing all these persons. In case of alarms not sent From the "Configurer alarme" page, switch to "Paramètres étendus" Uncheck the box "Arrêter l'alarme si le statut est déjà ON". Set-up alarm transmission on call reception Menu "Entrée d'alarmes" "Nouvelle entrée d'alarmes" Choose "1000" in the left column and press on the green arrow Menu "Entrée d'alarmes" "Configuration des entrées d'alarmes" - Select the "1000" entry - Choose "Distribution/Déclenchement" d'une alarme" - Choose the alarm number that will be sent. Menu "Configuration" "Appel entrants et alarmes sur appels entrants". - Check "Afficher message sur le display" - Lancer le module si le status : A Check "Module NVE optionnel" - Select A4220. Set-up conference on call reception Menu "Entrée d'alarmes" "Configuration des entrées d'alarmes" - Select the "1000" entry - Choose "Démarrer une conférence" - Choose the alarm number that will be sent. Menu "Alarme" "Configuration d'une alarme", select the one that will be used and change type to "Conférence/Parallèle". Alliance & Application Partner Program Inter-working report Edition 1 - page 47/59

48 Alliance & Application Partner Program Inter-working report Edition 1 - page 48/59

49 10 Appendix B: Alcatel-Lucent Communication Platform: configuration requirements 10.1 For OmniPCX Enterprise Trunk (T2) declaration see Newvoice documentation Trunk declaration for H323 see Newvoice documentation Paging interface declaration No specific configuration except: NS licenses to be available NS parameter to be set for each device addressed by Paging Interface (mono-line mode only) XML IP Touch declaration Standard declaration of mobicall application within XML API server as defined in XML Web Services Installation manual UTF8 Long messages (30 characters on 310/610) A new trunk group data has been added: Mgr->Trunk Group -> Special Services + Alarm Call + Nothing + Urgent Broadcasting + Timed call Release This parameter must be set as Alarm call, on the Mobicall Trunk Group. When the 310/610 answers the call, it ditrectly goes to DTMF mode. When 310/610 dials the digits in DTMF mode, display of digits on 310/610 screen can be managed through parameter given in below path : Mgr -> System -> Other System Parameter + No. Digits on the Sets Alliance & Application Partner Program Inter-working report Edition 1 - page 49/59

50 11 Appendix C: Alcatel-Lucent OmniPCX Enterprise Platform: Licencing 11.1 For OmniPCX Enterprise Trunk (QSIG-GF/ABCF) Licence 019 : CORPORATE NETWORKING (ABC, ABCVPN, ISVPN) Trunk declaration for H323 licence 187 : H323 network link Trunk declaration for SP licence 188 : SIP networking link l icence 185 : SIP Gateway Paging interface declaration licence 89 : Notification server to be set at 50 at least XML IP Touch declaration licence 318 : XML IPTOUCH engine UTF8 Long messages (30 characters on 310/610) No licences Alliance & Application Partner Program Inter-working report Edition 1 - page 50/59

51 12 Appendix D: Partner escalation process 12.1 Contact information Address : ST Gallerstrasse Lachen Main Phone : Main Fax : Main mail : [email protected] rd Party Support Detail Contact Address : ST Gallerstrasse Lachen Main Phone : Main Fax : Main mail : [email protected] General Information The first level support is delegated to our resellers and installers. NewVoice, as a software editor only provides second level support. The 2 nd level support is mainly for configuration and installation s. These are easy s than can be solved pretty quickly. There are two different support resolution methods : - phone assistance : adapted for simple and recurrent questions - on-line assistance with remote connexion : used as the highest level of support provided for incident resolution. Expert connect to the system to get more precise information (after a pre qualification) and to solve it Severity Description and Response Times Priority/Severit Response Description y Time Low Trouble with installation, configuration 10min. Blocking Trouble with communication with other systems 30min to 24h Support Level Definitions Level Description 1 st Qualification of an incident, a. Includes the collection of every configuration information, a detailed description of the occuring and the cinematic conducting to that. 2 nd Resolution of an incident. Problems of configuration, installation of the application, or uneffective functionnalities. 3 rd Hardware issues. Since no hardware is provided, there is no such support level Alliance & Application Partner Program Inter-working report Edition 1 - page 51/59

52 Call Flow Description There are two ways of joining the support team : - by - by phone For each way, the flow is as follows : Information like : - description - test scenario - associated log files will be asked as a base input for identification. Then the support team will provide help in configuration or bug-fixing, asking R&D if needed. Support can also be used for first businesses to help the partner configure the system. Ideally all person involved in an installation has been trained by NewVoice, but due to the large number of modules in the application, it can occur that some points have never been seen by the partner, thus requiring help, that NewVoice will provide. Escalation procedure is detailed with each partner to define the perimeter of responsibility. Alliance & Application Partner Program Inter-working report Edition 1 - page 52/59

53 13 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 thirdparty 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 communication products: Alcatel-Lucent's communication products for the enterprise market include infrastructure elements, platforms and software suites. To ensure easy integration, the AAPP provides a full array of standards-based application programming interfaces and fully-documented proprietary interfaces. Together, these enable third-party applications to benefit fully from the potential of Alcatel-Lucent products. Test and verify a comprehensive range of third-party applications: to ensure proper inter-working, Alcatel-Lucent tests and verifies selected third-party applications that complement its portfolio. Successful candidates, which are labelled Alcatel-Lucent Compliant 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: Alcatel-Lucent.com You can access the Alcatel-Lucent website at this URL: Alliance & Application Partner Program Inter-working report Edition 1 - page 53/59

54 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: 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: Alliance & Application Partner Program Inter-working report Edition 1 - page 54/59

55 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): click the Partner Center link and then Support e-support from the Alcatel-Lucent Business Partners Web site (if registered Alcatel-Lucent Business Partners): click the e-support link and then e-service Request [email protected] Fax number: +33(0) Telephone numbers: Alcatel-Lucent Business Partners Contact Center: France : French agent Austria : German agent Denmark : English agent Germany : German agent Ireland : English agent Italy : Italian agent UK : English agent Spain : Spanish agent Switzerland : German agent For other countries: English answer : + 33 (0) French answer : + 33 (0) German answer : + 33 (0) Spanish answer : + 33 (0) Alliance & Application Partner Program Inter-working report Edition 1 - page 55/59

56 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: 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 optimise your training investments. Alliance & Application Partner Program Inter-working report Edition 1 - page 56/59

57 14 Appendix E: Alcatel-Lucent escalation process in case of 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 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. Alcatel Technical Support Business Partner Customer Experts Exchanges Answer SR In cases of the has not been sent to the right organization: Please open a SR into our partner database by mentioning our SR number SR Answer Technical Issues Partner s answers Application Partner Support SR = Service Request Alliance & Application Partner Program Inter-working report Edition 1 - page 57/59

58 General Rules The following general rules are applied: Only certified AAPP applications are officially supported by Alcatel-Lucent The certification is based on tests suite passed by Alcatel-Lucent and the Application Partner and the result is consigned into 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. any If the IWR for the Alcatel-Lucent release is not available, Alcatel-Lucent doesn t engage 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. Alliance & Application Partner Program Inter-working report Edition 1 - page 58/59

59 The escalation process As stated above, the Alcatel-Lucent support will be limited to applications with a valid inter-working report. Known s or remarks mentioned in the IWR will not be taken into account. In case of, 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 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 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 by the Business Partner or the party responsible for that Application for an analysis of the. Alcatel-Lucent has to be involved solely if the application partner demonstrate, with traces, after reproduction of the, 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 to the Alcatel-Lucent Hot-line if the Application Partner has demonstrated a 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 of 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. Alliance & Application Partner Program Inter-working report Edition 1 - page 59/59