ALE Application Partner Program Inter-Working Report

Transcription

1 ALE Application Partner Program Inter-Working Report Partner: Cieme Application type: Hospitality / CAS Application name: Infoserv Hotel Alcatel-Lucent Enterprise Platform: OmniPCX Office 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. ALE Application Partner Program Inter-working report - Edition 1 - page 1/57

2 Certification overview Date of the certification May 2016 ALE International representative AAPP member representative Thierry Chevert Laurent Cordier Alcatel-Lucent Enterprise OmniPCX Office Communication Platform Alcatel-Lucent Enterprise Communication Platform Release R AAPP member application version V2.9 Application Category Hospitality dedicated software Author(s): Reviewer(s): Karthik Padmarajan Rachid Himmi, Krassimira Atanassov Revision History Edition 1: creation of the document May 2016 Test results Passed Refused Postponed Passed with restrictions Refer to the section 6 for a summary of the test results. IWR validity extension None ALE Application Partner Program Inter-working report - Edition 1 - page 2/57

3 AAPP Member Contact Information Contact name: Title: Bogdan PIETRARU Research and development Manager Address: Street of 8 May 1945 (25) Zip Code: City: BOISSY SAINT LEGER Country: France Phone: Fax: Mobile Phone: Web site: address: bpietraru@cieme.com ALE Application Partner Program Inter-working report - Edition 1 - page 3/57

4 TABLE OF CONTENTS 1 INTRODUCTION VALIDITY OF THE INTERWORKING REPORT LIMITS OF THE TECHNICAL SUPPORT CASE OF ADDITIONAL THIRD PARTY APPLICATIONS APPLICATION INFORMATION TEST ENVIRONMENT HARDWARE CONFIGURATION SOFTWARE CONFIGURATION SUMMARY OF TEST RESULTS SUMMARY OF MAIN FUNCTIONS SUPPORTED SUMMARY OF PROBLEMS SUMMARY OF LIMITATIONS NOTES, REMARKS TEST RESULT TEMPLATE TEST RESULTS FOR 4 DIGITS PASSWORD CONNECTIVITY AND SET-UP Test objectives Test results PBX PMS - CHECK-IN FROM PMS GUEST ROOM NUMBER ALLOCATION BY PMS Test objectives Test results PBX PMS - MODIFICATION OF GUEST CONFIGURATION Test objectives Test procedure PBX PMS - ROOM STATUS CHANGE Test objectives Test procedure PBX PMS - WAKE- UP EVENTS Test objectives Test procedure PBX HOTEL APPLICATION - MANAGEMENT OF CALL TICKETS: STATION MESSAGE DETAIL RECORDING Test objectives Test procedure PBX HOTEL APPLICATION - INTERROGATION MANAGEMENT FOLLOWED BY PBX HOTEL APPLICATION GUEST TELEPHONE ACCOUNT Test objectives Test procedure PBX HOTEL APPLICATION - CHECK OUT GUEST Test objectives Test procedure PBX HOTEL APPLICATION = INIT REQUEST PBX HOTEL APPLICATION = REINIT Test objectives Test procedure DISRUPTION OF OHL LINK Test objectives Test procedure TEST RESULTS FOR 6 DIGITS PASSWORD ALE Application Partner Program Inter-working report - Edition 1 - page 4/57

5 9.1 CONNECTIVITY AND SET-UP Test objectives Test results PBX PMS - CHECK-IN FROM PMS GUEST ROOM NUMBER ALLOCATION BY PMS Test objectives Test results PBX PMS - MODIFICATION OF GUEST CONFIGURATION Test objectives Test procedure PBX PMS - ROOM STATUS CHANGE Test objectives Test procedure PBX PMS - WAKE- UP EVENTS Test objectives Test procedure PBX HOTEL APPLICATION - MANAGEMENT OF CALL TICKETS: STATION MESSAGE DETAIL RECORDING Test objectives Test procedure PBX HOTEL APPLICATION - INTERROGATION MANAGEMENT FOLLOWED BY PBX HOTEL APPLICATION GUEST TELEPHONE ACCOUNT Test objectives Test procedure PBX HOTEL APPLICATION - CHECK OUT GUEST Test objectives Test procedure PBX HOTEL APPLICATION = INIT REQUEST PBX HOTEL APPLICATION = REINIT Test objectives Test procedure DISRUPTION OF OHL LINK Test objectives Test procedure METERING MODE TESTS Test objectives APPENDIX B: CONFIGURATION REQUIREMENTS OF THE AAPP MEMBER S APPLICATION INFOSERV HOTEL (HOTEL) APPLICATION SCREENSHOTS FROM THE APPLICATION APPENDIX C: ALCATEL-LUCENT ENTERPRISE COMMUNICATION PLATFORM: CONFIGURATION REQUIREMENTS APPENDIX C: ALCATEL-LUCENT ENTERPRISE COMMUNICATION PLATFORM: CONFIGURATION REQUIREMENTS 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 ALE Application Partner Program Inter-working report - Edition 1 - page 5/57

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. ALE Application Partner Program Inter-working report - Edition 1 - page 6/57

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. ALE Application Partner Program Inter-working report - Edition 1 - page 7/57

8 3 Limits of the Technical support For certified AAPP applications, Technical support will be provided within the scope of the features which have been certified in the InterWorking report. The scope is defined by the InterWorking report via the tests cases which have been performed, the conditions and the perimeter of the testing and identified limitations. All those details are documented in the IWR. The Business Partner must verify an InterWorking Report (see above Validity of the InterWorking Report) is valid and that the deployment follows all recommendations and prerequisites described in the InterWorking Report. 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. Access to technical support by the Business Partner requires a valid ALE maintenance contract For details on all cases (3 rd party application certified or not, request outside the scope of this IWR, etc.), 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 ). ALE Application Partner Program Inter-working report - Edition 1 - page 8/57

9 4 Application information Application commercial name: InfoServ Hotel Application version: V2.9 Interface type: OHL Application Summary: InfoServ Hotel is suitable both for economy hotels, the holiday club and luxury hotel. InfoServ Hotel offers specific functionality for the hotel world as the booking management, check in individual or grouped, wake up call, various billing services, room status management for optimization of client management time. Moreover, InfoServ Hotel offers full interoperability with application front office (PMS). InfoServ Hotel benefits - Intuitive web interface, quick and easy to use. - The reports calls Incoming to avoid losses of sales revenue. - All specifics Hotel functionalities are managed with InfoServ Hotel - Publishing of the invoice in the guest language (French, English). - Interfaces with every Property Management System (option). ALE Application Partner Program Inter-working report - Edition 1 - page 9/57

10 5 Test environment Figure 1 Test environment ALE Application Partner Program Inter-working report - Edition 1 - page 10/57

11 5.1 Hardware configuration Alcatel-Lucent Enterprise Communication Platform: Omni PCX Office - ISDN T0 CoCPU /RAS, UA and Z interfaces, digital and analogues sets. Alcatel-Lucent Communication Platform: OmniPCX Office Rack Power CPU Release: R103/ OMC: 10.3_7.1a_XX_Alcatel OLD version Setup Details: Setup Information OXO 1 OXO 1 IP address Domain name Voic No Attendant No 100 OXO Extension Details used for test IP Touch extension numbers Oxo1testing.proservtesting.com IPset-1 : 150 IPset-2 : 151 IPset-3 : 152 IPset-3 : 140 Ipset-4 : Software configuration Alcatel-Lucent Enterprise Communication Platform: - OmniPCX Office: R103/ Office Link Driver: v Partner Application : InfoServ V2.9 (V13/013) ALE Application Partner Program Inter-working report - Edition 1 - page 11/57

12 6 Summary of test results 6.1 Summary of main functions supported Hotel / Healthcare Check-in OK Check-out OK Phone allocation ( i.e. DDI number allocation ) OK Modification (Name,DND, Barring cat., wakeup OK time etc ) Wake-Up events OK Interrogation OK Re-initialization request OK CDR Outgoing call from guest room OK CDR Outgoing call from booth OK CDR Outgoing transferred call OK CDR Outgoing not charged calls OK 6 digits password OK 6.2 Summary of problems None 6.3 Summary of limitations Only full re-initialization request is supported by partner application. Modification of password is not supported by the application. 6.4 Notes, remarks The application considers the response sent by the OXO. The application can work in metering mode alone. In this mode only call metering is possible. ALE Application Partner Program Inter-working report - Edition 1 - page 12/57

13 7 Test Result Template The results are presented as indicated in the example below: Test Case Id 1 Test Case N/A OK NOK Comment Test case 1 Action Expected result Test case 2 Action Expected result Test case 3 Action Expected result Test case 4 Action Expected result 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 Test Case Id: a feature testing may comprise multiple steps depending on its complexity. Each step has to be completed successfully in order to conform to the test. Test Case: describes the test case with the detail of the main steps to be executed the and the expected result N/A: when checked, means the test case is not applicable in the scope of the application OK: when checked, means the test case performs as expected NOK: when checked, means the test case has failed. In that case, describe in the field Comment the reason for the failure and the reference number of the issue either on ALE International side or on AAPP member side Comment: to be filled in with any relevant comment. Mandatory in case a test has failed especially the reference number of the issue. ALE Application Partner Program Inter-working report - Edition 1 - page 13/57

14 8 Test Results for 4 digits password 8.1 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 Communication Platform are connected and the interface link is operational) Test results Test Case Id Test Case N/A OK NOK Comment 1 OHL Driver Configuration 2 Partner application ALE Application Partner Program Inter-working report - Edition 1 - page 14/57

15 8.2 PBX PMS - CHECK-IN from PMS Guest Room Number allocation by PMS Test objectives These tests shall verify that the check-in is performed as expected depending on the status of rooms and information to setup Test results All check-in request are done with frame A unless you use the 6 digit password configuration where we use the frame B. Test Case Id CIC101 CIC102 CIC103 CIC104 CIC105 CIC106 CIC107 CIC108 CIC109 CIC110 CIC111 Test Case Generate a check-in for a valid guest room extension number with guest name Generate a check-in for an invalid guest room extension number Generate a check-in with an already checked-in room extension number Generate a check-in with language parameter Generate a check-in with an wrong value in the language field Generate a check-in with wake-up call time Generate a check-in with wrong wake-up call time (e. g. 99:99) Generate a check-in with Dialling Restrictions (i.e. Barring) Generate a check-in with a Deposit Generate a check-in with a bad Deposit value (e. g ) Generate a check-in and enable DND REPLY message expected from PBX I INV JG INV JA I INV JG I I N/A OK NOK Comment Wrong language parameter cannot be entered from the application. Not supported CIC112 CIC113 CIC114 Generate a check-in with password Auto Allocate a DDI (Direct Dial Inwards) number to a checked -in GUEST ROOM Auto Allocate a DDI (Direct Dial Inwards) number to a checked -in GUEST ROOM when there are no free DDI numbers available ALE Application Partner Program Inter-working report - Edition 1 - page 15/57

16 Test Case Id CIC115 CIC116 CIC117 CIC118 CIC119 Result Test Case Generate a check-in with bad language parameter Generate a check-in with bad DND parameter Generate a check-in with room extension forwarded to voic Generate a check-in with bad Password parameter (e. g. illegal characters) Generate a check-in for a room set which is out of service (check-in should still work!) CHECK-IN from PMS with GUEST NUMBER allocation by PMS REPLY message expected from PBX I I N/A OK NOK Comment Wrong language parameter cannot be entered from the application. Not supported ALE Application Partner Program Inter-working report - Edition 1 - page 16/57

17 8.3 PBX PMS - MODIFICATION of GUEST configuration Test objectives Check the ability of the application to change GUEST configuration data Test procedure All requests for this test are done with frame M or frame N in case of 6 digits password. Test Case Id MOC 101 Test Case Modification of GUEST with new password REPLY message expected from PBX MOC 102 Modification with deposit MOC 103 MOC 104 Modification of language parameter Modification on Dialling Restrictions (i.e. Guest room outward dialling Barring) M M MOC 105 Modification of the name M MOC 106 Modification of the Wake up M MOC 107 MOC 108 Result Modification of DND state Modification of DDI number (eg. Allocate a new DDI to a room) MODIFICATION of GUEST configuration M N/A OK NOK Comment Not supported ALE Application Partner Program Inter-working report - Edition 1 - page 17/57

18 8.4 PBX PMS - ROOM STATUS change Test objectives Check the ability of the application to change the room status Test procedure Test Case Id STAT 101 STAT 102 STAT 103 STAT 104 STAT 105 Test Case Room status change message with maid room problem identification code from a room phone Room status change message without maid problem identification code from a room phone Room status change message with maid 'Clean' Status and 'no problem' code from a room phone Room status change message with maid room ' Unclean' and ' problem' identification code from a room phone Room status message with different problem (re- Initialization message) and status codes sent to the PMS from the PBX: e. g. Maid arrives in the room, room has be cleaned for a new guest or the same guest REPLY message expected from PBX N/A OK NOK Comment Result ROOM STATUS change ALE Application Partner Program Inter-working report - Edition 1 - page 18/57

19 8.5 PBX PMS - WAKE- UP events Test objectives Check the ability of the application to manage wake-up events Test procedure Test Case Id WUP 101 WUP 102 WUP 103 WUP 104 WUP 105 WUP 106 WUP 107 WUP 108 Test Case Wake-up message with normal answer Wake-up message with no answer Wake-up message with busy line Wake-up message with out of order line Wake-up cancellation message Wake-up message generated by programming Wake-up message generated by modification Wake-up cancellation generated by modification message. REPLY message expected from PBX N/A OK NOK Comment Result WAKE- UP events ALE Application Partner Program Inter-working report - Edition 1 - page 19/57

20 8.6 PBX Hotel Application - Management of CALL TICKETS: Station Message Detail Recording Test objectives Check the ability of the application to manage call tickets Test procedure Test Case Id CAT 101 CAT 102 CAT 104 CAT 105 CAT 106 CAT 107 CAT 108 CAT 109 CAT 110 Result Test Case SMDR message of a charged outgoing call with pulses or cost. Call done on room extension. SMDR message of a charged outgoing call with pulses or cost. Call done on booth extension SMDR message of a transferred outgoing call from GUEST to GUEST with pulses or cost SMDR message of a transferred outgoing call from an ADMIN extension to a GUEST with pulses or cost SMDR message of a non charged outgoing call (Free call destination e. g. 0800) SMDR message of an incoming call SMDR message of a transferred incoming call SMDR message of a transferred outgoing call from ROOM1 to ROOM2 which is forwarded on mail box SMDR message of a charged outgoing call with pulses or cost. Call done on booth phone using MTR and the charge assigned to a guest room Management of CALL TICKETS: Station Message Detail Recording. REPLY message expected from PBX N/A OK NOK Comment Incoming calls are not accounted in the application ALE Application Partner Program Inter-working report - Edition 1 - page 20/57

21 8.7 PBX Hotel Application - Interrogation management followed by PBX Hotel Application Guest Telephone Account Test objectives Check the ability of the application to get information from PBX using the Interrogation command Test procedure Test Case Test Case Id INT101 Asks for the Guest room extension telephone accounts. INT102 Asks for the Guest room extension telephone accounts using a Guest room number which is out of the range. INT103 Asks for the Guest room extension telephone accounts using a Guest room number which is not checked in. INT104 Asks for the Guest room extension telephone accounts Verify the management of Cost, Total Deposit and Guest balance. INTERROGATION Result management followed by Guest Telephone Account. REPLY message expected from PBX N/A OK NOK Comment ALE Application Partner Program Inter-working report - Edition 1 - page 21/57

22 8.8 PBX Hotel Application - CHECK OUT Guest Test objectives These tests shall verify that the check-out performed as expected depending on the status of rooms Test procedure Test Case Id COC 101 COC 102 COC 103 Test Case Check Out of a guest room number Check Out of a guest which room line is busy Check Out of a guest with not consulted messages in the associated voice mail box COC 104 Check Out of an invalid guest room number COC 105 Check Out of a none checked in guest room number COC 106 COC 107 COC 108 Result Verify metering bills by checking out a guest room number Verify metering bills by checking out a guest room number which was transferred from one room to another room and called from each of them Verify metering bills by checking out a guest room number which call from a booth extension (i.e. MTR call assignment to a room by operator) CHECK OUT GUEST NUMBER REPLY message expected from PBX D O D O D O D PG D N/A OK NOK Comment The application cannot send check out for an guest which is not checked in. The application cannot send check out for an guest which is not checked in. The application checks the metering bills by default during the checkout The application checks the metering bills by default during the checkout. Same comment as in COC106 ALE Application Partner Program Inter-working report - Edition 1 - page 22/57

23 8.9 PBX Hotel Application = INIT REQUEST PBX Hotel Application = REINIT Test objectives These tests shall verify that the Initialization requests are performed as required Test procedure Test Case Test Case Id REI101 Generate a reinit request for a specific GUEST room number - Full guest reinit. REI102 Generate a reinit request for a specific GUEST room number - Partial guest reinit. REI103 Generate a reinit request for a GUEST room number out of range REI104 Generate a reinit request for a specific GUEST room number not checked in. REI105 Generate a reinit request for all GUESTS checked-in: - Full guest reinit. REI106 Generate a reinit request for all GUESTS checked-in: - Partial guest reinit. Result RE-INITIALIZATION REQUEST REPLY message expected from PBX N/A OK NOK Comment Not supported Not supported Not supported Not supported Not supported ALE Application Partner Program Inter-working report - Edition 1 - page 23/57

24 8.10 Disruption of OHL Link Test objectives These tests shall verify that the application does not hang or loose data in case of link disruptions Test procedure Test Case Test Case N/A OK NOK Comment Id DIS101 Cut the ethernet link between PMS interface and the OmniPCX Office: Generate some events like check-in, Phone allocations from the PMS. Establish the link and verify that the events are sent to the OmniPCX. DIS102 Power off the PMS interface and generate some events from the OmniPCX Office side. Restart the interface and verify that the events are sent and taken in consideration on the PMS side DIS103 If the PMS is composed with several devices, the same tests have to be done by powering off and restarting separately the different devices. DIS104 Generate an XOFF on the OmniPCX Office. Generate some events on PMS. Send an XON on the OmniPCX Office side. Result DISRUPTION OF OHL LINK ALE Application Partner Program Inter-working report - Edition 1 - page 24/57

25 9 Test Results for 6 digits password 9.1 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 Communication Platform are connected and the interface link is operational) Test results Test Case Id Test Case N/A OK NOK Comment 1 OHL Driver Configuration 2 Partner application ALE Application Partner Program Inter-working report - Edition 1 - page 25/57

26 9.2 PBX PMS - CHECK-IN from PMS Guest Room Number allocation by PMS Test objectives These tests shall verify that the check-in is performed as expected depending on the status of rooms and information to setup Test results All check-in request are done with frame A unless you use the 6 digit password configuration where we use the frame B. Test Case Id CIC101 CIC102 CIC103 CIC104 CIC105 CIC106 CIC107 CIC108 CIC109 CIC110 CIC111 Test Case Generate a check-in for a valid guest room extension number with guest name Generate a check-in for an invalid guest room extension number Generate a check-in with an already checked-in room extension number Generate a check-in with language parameter Generate a check-in with an wrong value in the language field Generate a check-in with wake-up call time Generate a check-in with wrong wake-up call time (e. g. 99:99) Generate a check-in with Dialling Restrictions (i.e. Barring) Generate a check-in with a Deposit Generate a check-in with a bad Deposit value (e. g ) Generate a check-in and enable DND REPLY message expected from PBX I INV JG INV JA I INV JG I I N/A OK NOK Comment Wrong language parameter cannot be entered from the application. Not supported CIC112 CIC113 CIC114 Generate a check-in with password Auto Allocate a DDI (Direct Dial Inwards) number to a checked -in GUEST ROOM Auto Allocate a DDI (Direct Dial Inwards) number to a checked -in GUEST ROOM when there are no free DDI numbers available ALE Application Partner Program Inter-working report - Edition 1 - page 26/57

27 Test Case Id CIC115 CIC116 CIC117 CIC118 CIC119 Result Test Case Generate a check-in with bad language parameter Generate a check-in with bad DND parameter Generate a check-in with room extension forwarded to voic Generate a check-in with bad Password parameter (e. g. illegal characters) Generate a check-in for a room set which is out of service (check-in should still work!) CHECK-IN from PMS with GUEST NUMBER allocation by PMS REPLY message expected from PBX I I N/A OK NOK Comment Wrong language parameter cannot be entered from the application. Not supported ALE Application Partner Program Inter-working report - Edition 1 - page 27/57

28 9.3 PBX PMS - MODIFICATION of GUEST configuration Test objectives Check the ability of the application to change GUEST configuration data Test procedure All requests for this test are done with frame M or frame N in case of 6 digits password. Test Case Id MOC 101 Test Case Modification of GUEST with new password REPLY message expected from PBX MOC 102 Modification with deposit MOC 103 MOC 104 Modification of language parameter Modification on Dialling Restrictions (i.e. Guest room outward dialling Barring) M M MOC 105 Modification of the name M MOC 106 Modification of the Wake up M MOC 107 MOC 108 Result Modification of DND state Modification of DDI number (eg. Allocate a new DDI to a room) MODIFICATION of GUEST configuration M N/A OK NOK Comment Not supported ALE Application Partner Program Inter-working report - Edition 1 - page 28/57

29 9.4 PBX PMS - ROOM STATUS change Test objectives Check the ability of the application to change the room status Test procedure Test Case Id STAT 101 STAT 102 STAT 103 STAT 104 STAT 105 Test Case Room status change message with maid room problem identification code from a room phone Room status change message without maid problem identification code from a room phone Room status change message with maid 'Clean' Status and 'no problem' code from a room phone Room status change message with maid room ' Unclean' and ' problem' identification code from a room phone Room status message with different problem (re- Initialization message) and status codes sent to the PMS from the PBX: e. g. Maid arrives in the room, room has be cleaned for a new guest or the same guest REPLY message expected from PBX N/A OK NOK Comment Result ROOM STATUS change ALE Application Partner Program Inter-working report - Edition 1 - page 29/57

30 9.5 PBX PMS - WAKE- UP events Test objectives Check the ability of the application to manage wake-up events Test procedure Test Case Id WUP 101 WUP 102 WUP 103 WUP 104 WUP 105 WUP 106 WUP 107 WUP 108 Test Case Wake-up message with normal answer Wake-up message with no answer Wake-up message with busy line Wake-up message with out of order line Wake-up cancellation message Wake-up message generated by programming Wake-up message generated by modification Wake-up cancellation generated by modification message. REPLY message expected from PBX N/A OK NOK Comment Result WAKE- UP events ALE Application Partner Program Inter-working report - Edition 1 - page 30/57

31 9.6 PBX Hotel Application - Management of CALL TICKETS: Station Message Detail Recording Test objectives Check the ability of the application to manage call tickets Test procedure Test Case Id CAT 101 CAT 102 CAT 104 CAT 105 CAT 106 CAT 107 CAT 108 CAT 109 CAT 110 Result Test Case SMDR message of a charged outgoing call with pulses or cost. Call done on room extension. SMDR message of a charged outgoing call with pulses or cost. Call done on booth extension SMDR message of a transferred outgoing call from GUEST to GUEST with pulses or cost SMDR message of a transferred outgoing call from an ADMIN extension to a GUEST with pulses or cost SMDR message of a non charged outgoing call (Free call destination e. g. 0800) SMDR message of an incoming call SMDR message of a transferred incoming call SMDR message of a transferred outgoing call from ROOM1 to ROOM2 which is forwarded on mail box SMDR message of a charged outgoing call with pulses or cost. Call done on booth phone using MTR and the charge assigned to a guest room Management of CALL TICKETS: Station Message Detail Recording. REPLY message expected from PBX N/A OK NOK Comment Incoming calls are not accounted in the application ALE Application Partner Program Inter-working report - Edition 1 - page 31/57

32 9.7 PBX Hotel Application - Interrogation management followed by PBX Hotel Application Guest Telephone Account Test objectives Check the ability of the application to get information from PBX using the Interrogation command Test procedure Test Case Test Case Id INT101 Asks for the Guest room extension telephone accounts. INT102 Asks for the Guest room extension telephone accounts using a Guest room number which is out of the range. INT103 Asks for the Guest room extension telephone accounts using a Guest room number which is not checked in. INT104 Asks for the Guest room extension telephone accounts Verify the management of Cost, Total Deposit and Guest balance. INTERROGATION Result management followed by Guest Telephone Account. REPLY message expected from PBX N/A OK NOK Comment Not supported Not supported Not supported Not supported Not supported ALE Application Partner Program Inter-working report - Edition 1 - page 32/57

33 9.8 PBX Hotel Application - CHECK OUT Guest Test objectives These tests shall verify that the check-out performed as expected depending on the status of rooms Test procedure Test Case Id COC 101 COC 102 COC 103 COC 104 Test Case Check Out of a guest room number Check Out of a guest which room line is busy Check Out of a guest with not consulted messages in the associated voice mail box Check Out of an invalid guest room number COC 105 Check Out of a none checked in guest room number COC 106 COC 107 COC 108 Result Verify metering bills by checking out a guest room number Verify metering bills by checking out a guest room number which was transferred from one room to another room and called from each of them Verify metering bills by checking out a guest room number which call from a booth extension (i.e. MTR call assignment to a room by operator) CHECK OUT GUEST NUMBER REPLY message expected from PBX D O D O D O D PG D N/A OK NOK Comment Voic not supported in this mode The application cannot send check out for an guest which is not checked in. The application checks the metering bills by default during the checkout. The application checks the metering bills by default during the checkout. Same comment as in COC106 ALE Application Partner Program Inter-working report - Edition 1 - page 33/57

34 9.9 PBX Hotel Application = INIT REQUEST PBX Hotel Application = REINIT Test objectives These tests shall verify that the Initialization requests are performed as required Test procedure Test Case Test Case Id REI101 Generate a reinit request for a specific GUEST room number - Full guest reinit. REI102 Generate a reinit request for a specific GUEST room number - Partial guest reinit. REI103 Generate a reinit request for a GUEST room number out of range REI104 Generate a reinit request for a specific GUEST room number not checked in. REI105 Generate a reinit request for all GUESTS checked-in: - Full guest reinit. REI106 Generate a reinit request for all GUESTS checked-in: - Partial guest reinit. Result RE-INITIALIZATION REQUEST REPLY message expected from PBX N/A OK NOK Comment Not supported Not supported Not supported Not supported Not supported ALE Application Partner Program Inter-working report - Edition 1 - page 34/57

35 9.10 Disruption of OHL Link Test objectives These tests shall verify that the application does not hang or loose data in case of link disruptions Test procedure Test Case Test Case N/A OK NOK Comment Id DIS101 Cut the ethernet link between PMS interface and the OmniPCX Office: Generate some events like check-in, Phone allocations from the PMS. Establish the link and verify that the events are sent to the OmniPCX. DIS102 Power off the PMS interface and generate some events from the OmniPCX Office side. Restart the interface and verify that the events are sent and taken in consideration on the PMS side DIS103 If the PMS is composed with several devices, the same tests have to be done by powering off and restarting separately the different devices. DIS104 Generate an XOFF on the OmniPCX Office. Generate some events on PMS. Send an XON on the OmniPCX Office side. Result DISRUPTION OF OHL LINK ALE Application Partner Program Inter-working report - Edition 1 - page 35/57

36 9.11 Metering mode tests Test objectives These tests shall verify that the application works fine in metering mode which is supported by the application. The application set in metering mode for collecting the SMDR tickets alone. This mode has to be tested in both 4 & 6 digits passwords.this mode is used for collecting tickets alone. Test Case Id SMDR1 SMDR2 SMDR3 SMDR4 SMDR5 SMDR6 Result Test Case N/A OK NOK Comment Outgoing call from IPTouch extension to external no. for 50 sec. duration using Manual dialling Outgoing call from IPTouch extension to external no. for 50 sec. duration using Redial dial Outgoing call from IPTouch extension to external no. for 50 sec. duration using Speed dial Make a call from IPTouch extension A to another IPTouch extension B but B is diverted to external number Outgoing call from an T0 call from booth extnesion External call transferred from the Booth extension to an Room extension Management of SMDR call tickets ALE Application Partner Program Inter-working report - Edition 1 - page 36/57

37 10 Appendix B: Configuration requirements of the AAPP member s application 10.1 InfoServ Hotel (Hotel) Application InfoServ Hotel V2.9 I Basic principles of the InfoServ Hotel software The basic purpose of InfoServ Hotel software is to bill telephone calls made by guest staying in hotels. This means being able to access real-time call information; specifically, InfoServ Hotel retrieves this information from the Details file of the database, and charges guest accordingly. With this software, the basic working component in Hotel mode is the Guest Sheet ; we use this sheet to view data about the guest, bill the guest, and perform a number of other operations depending on the specific configuration of the installation. II - Architecture of the InfoServ Hotel software Physical link between the PABX and InfoServ Santé: InfoServ Santé retrieves call tickets as the need arises via an IP link. Consulting InfoServ Hotel information: we can manage different users to consult InfoServ Hotel information via a Web access connected to the hotel s Intranet. ALE Application Partner Program Inter-working report - Edition 1 - page 37/57

38 InfoServ Hotel is an open application appreciated by users for its Windows usability via Web access. III. Interfacing with external applications III.1. Interfacing with Hotel management applications (option) InfoServ Hotel can interface with several Front Office packages using either our standard protocol or via a personalized solution, in order to adapt to the protocol used by the contractor. Cieme Informatique is compatible with the main Front Office softwares in the hotel typically used in the hotel sector. The interfaces between InfoServ Hotel and Front Office applications permit the following: Check-in data entered just one time, with identification via a key field. Updating of the patient directory (room changes inside the establishment). A single bill with the phone bill shown as part of an overall bill, and the mark-up compared with prices charged by operators. III.2. Interface with television management systems (option) InfoServ Hotel can interface with television management systems via an IP or an asynchronous link. The main television management interfaces generally encountered in the sector are: These interfaces between Infoserv and television management systems provide the following features: The telephone and the television can be opened in one single operation from Infoserv. ALE Application Partner Program Inter-working report - Edition 1 - page 38/57

39 Centralized billing of the telephone and television spend. In the case of an incoming guest who would like to have VOD (for example, package 2 with films for 5 days), this information will display on his admission sheet and on his patient slip. InfoServ Hotel sends the television management application a request to activate the VOD in the person's room for 5 days with package 2. This module is an option of the InfoServ Hotel solution. III.2. Interface with Internet Management systems (option) When checking in a guest, the hotel receptionist may have to handle the guest s requirement for Internet access. InfoServ Hotel has the capacity to create, from InfoServ Hotel screens, an Internet activation entry on the patient s bill of X hours or Y days, without interfacing with the external application. An alternative solution consists in interfacing with the external application managing the Internet. Guests taking out a telephone line are increasingly looking for an Internet access for X hours. Following crediting of an amount paid by the guest, InfoServ Hotel sends the Internet management application an instruction to open an Internet line for X hours. The main Internet management interfaces generally encountered in the sector are: IV InfoServ Hotel can be broken down into 3 components optimizing guest and administrative management General management of guests Financial management of guests Analyzing traffic IV 1. General management of guests This component consists of the following 8 fundamental aspects: Reservation Check In Managing items (mini bar) Programming wake-up calls Room Status Guest changing rooms Check Out Billing ALE Application Partner Program Inter-working report - Edition 1 - page 39/57

40 IV.1. Reservation The user can reserve hotel rooms using InfoServ Hotel. During a phone call with a potential guest, the receptionist has an immediate picture of the fill race, and can provide the caller with up to date, real-time information. IV.2. Check-In The high level of usability of the InfoServ Hotel Web interface, makes it very easy for hotel employees to use. Processing an incoming guest: Enter the following information in the Check-in screen: Family name First name Validate the date/time of arrival information if they are correct Room number Once a Guest Sheet has been created, an order is sent to the PABX with the instruction to activate extension XX in room YY. IV.3. Managing items (Mini bar) In addition to telephone consumptions, the InfoServ Hotel can be used to bill Additional services over the bedroom phone. For example, the InfoServ Hotel can bill the minibar. Room service personnel checking the room simply check the minibar, and then enter a specific code (the drinks code) on the telephone pad; in this way, minibar consumption is charged to the bill generated by InfoServ Hotel. IV.4. Programming wake-up calls The receptionist can issue wake-up calls for guest from the computer on which InfoServ Hotel is installed. The exact wake-up time can be programmed, and group wake-up calls can also be programmed (for all bus 1 tourists, for example). There is also a simpler consultation feature whereby the hotel receptionist can check whether or not the wake-up calls were successfully issued, and take steps if this is not the case (dispatching the hotel caretaker to the room in question, for example). All wake-up calls are acknowledged: Either: - Wake-up call completed successfully; - wake-up call did not complete successfully (i.e., the extension was busy or the person did not answer). IV.5. Room status The purpose of room status is to monitor the status of rooms at any given time. Specifically, the supervisor has one single window showing all information about the guest (nationality, wake-up calls, etc.) as well as practical information (room to be made up, light bulbs to change, etc.). This information is used by the supervisor to instruct hotel personnel as to what tasks they have to carry out. ALE Application Partner Program Inter-working report - Edition 1 - page 40/57

41 The hotel personnel can also use the telephone to signal actions to do, by entering a code corresponding to a given task (for example, light bulb to change = code 04) etc. and this information is then passed on to the hotel supervisor. In other words, the supervisor has an instantaneous picture on one single screen of the room status. IV.6. Guests changing rooms During his time in the hotel, a Guest may want to or may have to change room. In a large number of cases, in order to optimize the service provided to guest, the InfoServ Hotel has to manage the rotating DIDs so that the guest can keep his DID number. By pressing the button Room Change to Guest sheet, the hotel employee can enter the new room number; however, the DID number remains identical for the patient. ALE Application Partner Program Inter-working report - Edition 1 - page 41/57

42 IV.7. Check Out Processing hotel departures: The hotel employee processes guest departures from InfoServ Hotel consultation points using the procedure outlined below. Click on the Check Out tab of the Guest sheet; and simply validate the Check Out on the confirmation screen. As soon as you perform a Check Out, a bill is automatically printed. V. Billing guest The InfoServ Hotel can print two types of statements, summarizing the financial situation of patients: For the Financial Officer, InfoServ Hotel returns an up-to-date overall picture of phone income generated in the hotel. V.1. Multi-Operator Billing InfoServ Hotel features a host of functionalities from management of the unit cost of the tax identical for all installation extensions, up to the management of several operators on purchasing, with different breakdowns of the cost of sale per user category. In addition to the management of fixed costs and variable costs, InfoServ Hotel can handle the France Telecom Atout RPV (Private Virtual Network package) reduction. We need to determine the billing strategy at the customer wants to apply. InfoServ Hotel manages 2 call prices for each call (namely, purchase price and sale price). The purchase price corresponds to the cost paid to the supplier of the call (for example, France Telecom or some other operator); therefore, the purchase price will be the tool used to check purchasing bills. The sale price corresponds to the amount charged to the various persons or entities (guests, extensions, services, expenses centers, etc.).for the Financial Officer, InfoServ Hotel returns an up-to-date overall picture of phone income generated in the hotel. These two call prices can be configured to be identical or different (all price data is duplicated as purchase price and sale price) if you want the two call prices to be identical, simply enter the same information for the cost of the tax, formula codes, and so on. InfoServ Hotel can manage up to 5 customizable operator tariffs (in addition to Orange France). These tariffs are used to re-calculate the cost of calls at the rates charged by the operator in question. The guest can decide to entered the tariff which he took out contractually; Cieme Informatique can also propose operator tariffs. The guest must have opted for a remote management solution for the downloading of tariffs. VI Traffic analysis InfoServ Hotel has a traffic module to log incoming and outgoing calls. The InfoServ Hotel philosophy is: a single database for all modules. This has the advantage of pooling, on a single printout, information regarding both incoming and outgoing calls. This feature makes InfoServ Hotel an intelligent application adapting itself to the specific requirements of each patient. ALE Application Partner Program Inter-working report - Edition 1 - page 42/57

43 Customized information can be printed out on the basis of criteria provided by the user and on the basis of directory content (e.g.: for a given department, service, one or several persons, timeslot, etc.). The dimensioning can return analysis data per day, per hour, or in steps of 5 minutes (parameterizable). Printouts most frequently used can be stored by the InfoServ Hotel software. There is no limit to the maximum amount of printouts that can be stored. The InfoServ Hotel traffic module consists of the following 3 parts: General traffic information Quality of reception Dimensioning VI.1. General Traffic Information The elements taken into consideration are as follows: Duration of incoming calls (in seconds and HH;MM;SS). Duration of outgoing calls (in seconds and HH;MM;SS). Duration of incoming conversations (in seconds and HH;MM;SS). Duration of outgoing conversations (in seconds and HH;MM;SS). Duration of ringing time or queuing time. VI.2. Quality of Reception Collected data can be used to analyze the activity of your DID numbers. The available information is as follows: ALE Application Partner Program Inter-working report - Edition 1 - page 43/57

44 Number of incoming calls completed via DID. Number of incoming calls completed via operator set. Number of incoming calls completed via extension (transfer). Number of incoming calls not completed. Number of incoming calls completed via transfer. Information about POs (number of incoming calls; duration of incoming calls; duration of incoming conversations; duration of ringing time; number of direct incoming calls; number of incoming calls via extensions; number of incoming calls not completed; and number of incoming calls completed). Duration of ringing time or queuing time. Phone set obtained/phone set requested (group management). InfoServ Hotel can be used to automatically generate charts to analyze traffic, used to monitor the Quality of Service, monthly or by periods. VI.3. Dimensioning Dimensioning is used to perform fine analyses on each of the trunk groups (peak time, saturation, simulation, etc.) in order to optimize their configuration. Dimensioning consists in 3 different printouts distinguished by their selection criteria (selection by trunk group, by group of trunk groups, by dialed numbers, by directory sheet). Filtering operations carried out on trunk groups, outgoing dialed numbers and/or directory sheets can be combined simultaneously. Printouts can give detailed information on time periods from 5 to 60 minutes. ALE Application Partner Program Inter-working report - Edition 1 - page 44/57

45 Information available: Load in erlang: circuit occupation unit (example: 1 erlang = 1 occupied circuit). Peak time: Time with the highest level of consumption. Saturation: Information about times with a high level of circuit occupation (example: company with N incoming circuits => determine the number of busy circuits, and the duration of occupation). Number of incoming and/or outgoing calls. Hotel Client References ALE Application Partner Program Inter-working report - Edition 1 - page 45/57

46 10.2 Screenshots from the application Creation of room Creation Guest Number Room Management Screen ALE Application Partner Program Inter-working report - Edition 1 - page 46/57

47 Check-in Screenshot ALE Application Partner Program Inter-working report - Edition 1 - page 47/57

48 11 Appendix C: Alcatel-Lucent Enterprise Communication Platform: configuration requirements For installing instructions, please use documentation available on CD [Alcatel OXO installation instructions] which describes step by step configuration. OS, web browser and virtualization Windows Windows 7 Windows 8 Windows Server 2008 Windows Server 2012 Windows 10 Linux Linux Red Hat V6 ou 7 x CentOS V6 Virtualization VMWARE HYPER V Web browser Internet Explorer 10 Internet Explorer 11 Chrome Firefox Edge Hardware and Virtualization Caracteristics Minimal Memory Hard disk InfoServ V2.9 X X X X X X X X X X X X X X 4 Go 500 Go ALE Application Partner Program Inter-working report - Edition 1 - page 48/57

49 12 Appendix C: Alcatel-Lucent Enterprise Communication Platform: configuration requirements OXO have to be configured in hotel mode. In Counting the accounting through IP should be activated. We need to configure the check-in sequence in System miscellaneous > Hotel parameters The user extension has to be declared as a hotel set as displayed below. ALE Application Partner Program Inter-working report - Edition 1 - page 49/57

50 ALE Application Partner Program Inter-working report - Edition 1 - page 50/57

51 13 Appendix D: AAPP member s escalation process In case of problem please contact: CIEME technical support: Hotline (+33) Fax (+33) (correct?) Web site : address : services@cieme.com ALE Application Partner Program Inter-working report - Edition 1 - page 51/57

52 14 Appendix E: AAPP program 14.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. ALE Application Partner Program Inter-working report - Edition 1 - page 52/57

53 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: ALE Application Partner Program Inter-working report - Edition 1 - page 53/57

54 15 Appendix F: AAPP Escalation process 15.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 ALE Application Partner Program Inter-working report - Edition 1 - page 54/57