ALE Application Partner Program Inter-Working Report

Transcription

1 ALE Application Partner Program Inter-Working Report Partner: Jurudata Services Sdn. Bhd. Application type: Hospitality / PMSi & VMS Application name: WINPAC Alcatel-Lucent Enterprise Platform: OmniPCX Enterprise The product and release listed have been tested with the Alcatel-Lucent Communication Platform and the release specified hereinafter. The tests concern only the inter-working between the AAPP member s product and the Alcatel-Lucent Communication Platform. The inter-working report is valid until the AAPP member s product issues a new major release of such product (incorporating new features or functionality), or until Alcatel-Lucent issues a new major release of such Alcatel-Lucent product (incorporating new features or functionalities), whichever first occurs. ALCATEL-LUCENT MAKES NO REPRESENTATIONS, WARRANTIES OR CONDITIONS WITH RESPECT TO THE APPLICATION PARTNER PRODUCT. WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, ALCATEL-LUCENT HEREBY EXPRESSLY DISCLAIMS ANY AND ALL REPRESENTATIONS, WARRANTIES OR CONDITIONS OF ANY NATURE WHATSOEVER AS TO THE AAPP MEMBER S PRODUCT INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF MERCHANTABILITY, NON INFRINGEMENT OR FITNESS FOR A PARTICULAR PURPOSE AND ALCATEL-LUCENT FURTHER SHALL HAVE NO LIABILITY TO AAPP MEMBER OR ANY OTHER PARTY ARISING FROM OR RELATED IN ANY MANNER TO THIS CERTIFICATE. ALE Application Partner Program Inter-working report Edition 03 page 1/73

2 Certification overview Date of the certification From 15th to 17th February 2017 Alcatel-Lucent s representative AAPP member representative Thierry Chevert Syaiful Izham Bin A Rahman Alcatel-Lucent Communication Platform Alcatel-Lucent Communication Platform Release AAPP member application version Application Category OmniPCX Enterprise R11.2 PMSi v3.12 VMS Analog v3.8 VMS SIP Trunk v1.0 Hospitality dedicated software Healthcare dedicated software Author(s): Reviewer(s): T. Chevert Krassimira Atanassov, Rachid Himmi. Historic Edition 1: creation of the document - February 2017 Edition 2: clarify SIP certification (Trunk vs Extension) - March 2017 Edition 3: update in section 11.4 & March 2017 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 03 page 2/73

3 AAPP Member Contact Information Contact name: Title: Contact name: Title: Contact name: Title: Syaiful Izham Bin A Rahman Manager, Technical Mr. Andrew Lim Senior Manager, Solution Architect Mr. Lum Peng Chee Director Address: No.A-28-02, Block A, 3 Two Square Business Centre, No. 2, Jalan 19/1, Section 19 Zip Code: Petaling Jaya City: Selangor Country: Malaysia Phone: Fax: Mobile Phone: Web site: address: syaiful.izham@jds.com.my andrewlim@jds.com.my lumpc@jds.com.my ALE Application Partner Program Inter-working report Edition 03 page 3/73

4 TABLE OF CONTENTS 1 INTRODUCTION VALIDITY OF THE INTERWORKING REPORT LIMITS OF THE TECHNICAL SUPPORT CASE OF ADDITIONAL THIRD PARTY APPLICATIONS APPLICATION INFORMATION TESTS ENVIRONMENT DESCRIPTION DIAGRAM OF 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 CASES PBX PMS CHECK IN WITH GUEST NUMBER (ALLOCATION ON PBX) (MANDATORY IN CASE OF GUEST MANAGEMENT) / USE OF PBX VOICE MAIL PBX PMS CHECK IN ON ROOM EXTENSION A FRAME PBX PMS - ALLOCATION OF AN EXTENSION TO A GUEST H FRAME PBX PMS MODIFICATION OF GUEST OR ROOM CONFIGURATION A FRAME PBX PMS ROOM STATUS CHANGE - C FRAMES(OPTIONAL) PBX PMS WAKE UP EVENTS - P FRAMES(OPTIONAL) PBX PMS MANAGEMENT OF CALL TICKETS K OR J FRAMES (MANDATORY) PBX PMS DATA TRANSFER MANAGEMENT & MINIBAR - P FRAMES PBX PMS - INTERROGATION MANAGEMENT AND PBX PMS GUEST TELEPHONE ACCOUNT I & T FRAMES PBX PMS PBX VOICE MAIL ATTRIBUTION - F FRAMES PBX PMS PBX VOICE MAIL EVENT - F FRAMES PBX DYNAMIC SUITE - S FRAME PBX PMS CHECK OUT WITH GUEST NUMBER MANAGEMENT - D FRAME PBX PMS CHECK OUT WITH ROOM NUMBER MANAGEMENT D FRAME PBX PMS NIGHT AUDIT REQUEST - N FRAME PBX PMS RE-INITIALIZATION REQUEST AND PBX PMS DATABASE RE-INITIALIZATION Z & U FRAMES DISRUPTION OF AHL LINK (MANDATORY) JDS VMS ANALOG EXTERNAL VOICE MAIL AND WAKE-UP CALL SERVICES JDS VMS SIP TRUNKING - VOICE MAIL FOR MESSAGING JDS VMS SIP EXTENSION HIGH AVAILABILITY SPATIAL REDUNDANCY COMSERVER APPENDIX A : AAPP MEMBER S APPLICATION DESCRIPTION APPENDIX B: AAPP MEMBER S APPLICATION CONFIGURATION REQUIREMENTS MANAGEMENT OF WINPAC PMSI / WINPAC VMS ANALOGUE/ WINPAC VMS SIP TRUNK Intelligent Console Module (IC) System Operations & Maintenance Reporting Module Web Winpac Console MANAGEMENT OF WINPAC VMS ANALOGUE Main Screen ALE Application Partner Program Inter-working report Edition 03 page 4/73

5 VM Configuration / Maintenance Web Winpac VMS MANAGEMENT OF WINPAC VMS SIP TRUNK Main Screen Web Winpac VMS APPENDIX C: ALCATEL-LUCENT PLATFORM: CONFIGURATION REQUIREMENTS MANAGEMENT OF OMNIPCX ENTERPRISE ROOM EXTENSION MANAGEMENT GUEST NUMBER MANAGEMENT (GPIN) APPLICATION HOTEL MANAGEMENT APPLICATION HOTEL COMPUTER LINK MANAGEMENT ANALOG VOICE MAIL VPS CONFIGURATION SIP TRUNKING VOICE MAIL MANAGEMENT CLASS OF SERVICE CONFIGURATION PREFIXES MANAGEMENT INTEGRATED VOICE MAIL ASSIGNMENT ANALOG VOICE MAIL ASSIGNEMENT SIP TRUNK VOICE MAIL ASSIGNMENT SIP TRUNKING MANAGEMENT SIP EXTENSION VMS CONFIGURATION AHL LINK CONFIGURATION TIPS 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 03 page 5/73

6 1 Introduction This document is the result of the certification tests performed between the AAPP member s application and Alcatel-Lucent s platform. It certifies proper inter-working with the AAPP member s application. Information contained in this document is believed to be accurate and reliable at the time of printing. However, due to ongoing product improvements and revisions, Alcatel-Lucent cannot guarantee accuracy of printed material after the date of certification nor can it accept responsibility for errors or omissions. Updates to this document can be viewed on: - the Technical Support page of the Enterprise Business Portal ( 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 03 page 6/73

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 Alcatel-Lucent issues a new major release of such Alcatel-Lucent product (incorporating new features or functionalities), whichever first occurs. A new release is identified as following: a Major Release is any x. enumerated release. Example Product 1.0 is a major product release. a Minor Release is any x.y enumerated release. Example Product 1.1 is a minor product release The validity of the InterWorking report can be extended to upper major releases, if for example the interface didn t evolve, or to other products of the same family range. Please refer to the IWR validity extension chapter at the beginning of the report. Note: The InterWorking report becomes automatically obsolete when the mentioned product releases are end of life. ALE Application Partner Program Inter-working report Edition 03 page 7/73

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. 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 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 will consider that situation as to that where no IWR exists. ALE will handle this situation accordingly (for more details, please refer to Appendix F AAPP Escalation Process ). ALE Application Partner Program Inter-working report Edition 03 page 8/73

9 4 Application information Application family: Application commercial name: Hospitality PMS and VMS WINPAC Application version: PMSi v3.12 VMS Analog v3.8 VMS SIP v1.0 Interface types: AHL (Alcatel Hotel Link) on TCPIP first, Voice Mail System on Analog VPS ports or SIP Extension or SIP trunking. The voice mail systems (analog & SIP) were used with Guests in the hospitality context but not with administratives. The RS232c / V24 is also available with this application but was not part of tests. Alcatel Hotel Link (AHL) is a proprietary protocol on V24 or TCP/IP and designed to interface hospitality applications (hotels, hospitals, cruise ships...). Brief application description: WINPAC Property Management System Interface (commonly known as Call Accountiing System or WINPAC PMSi in short) & WINPAC Voice Related System (either Analog or SIP Based) are web-based systems designed to cater for hospitality sector which integrates and works impeccably with all major PMS and PABX systems; especially Alcatel OmniPCX Enterprise. Interacting with OmniPCX Enterprise : The application interacts with the OmniPCX Enterprise via TCP/IP & V24 AHL interfaces to manage hotel guest phone, real time billing of guest telephone call charges, wake up call etc and perform real-time posting to Hotel PMS. ALE Application Partner Program Inter-working report Edition 03 page 9/73

10 5 Tests environment description 5.1 Diagram of test environment PSTN JDS WINPAC Analog VPS lines OmniPCX Enterprise R11.2 Main CPU: AHL TCP/2561 SIP Trunk UDP/5060 LAN Guest phones 5.2 Hardware configuration OmniPCX Entreprise: o CS (Call Server Processing Unit) o GD (Gateway driver processing Unit ) o PRA T2 (ISDN Access) o MIX 2/4/4 (ISDN T0, digital & analog interfaces) o UA digital and analog sets AHL interface: o TCP/IP port TCP/2561 SIP Trunking interface: o TCP/IP port UDP / 5060 ALE Application Partner Program Inter-working report Edition 03 page 10/73

11 5.3 Software configuration Alcatel Communication Platform: OmniPCX Enterprise R11.2 Partner Application: WINPAC PMS 3.12 / WINPAC VMS 1.0 Computer used: ASUS PC wirh OS Windows 7 Professional 32bits from ALE Lab. ALE Application Partner Program Inter-working report Edition 03 page 11/73

12 6 Summary of test results 6.1 Summary of main functions supported Winpac PMS behave as a middleware gateway in interworking of Front Office (Ex: Fidelio Opera) and AHL of OmniPCX Enterprise. Front Office ProprietaryProtocol WinPAC PMS AHL OXE Therefore, some hotel information are transiting through PMS and are sent to directly Front Office (ex: Room Status). OK:Test passed / NA: Not Available in Partner Application Features Tested Property Management System PMS Guest Management (GPIN) Room Management Room Status Wake-Up call management & Events Call Ticketing (SMDR) Data Transfer MiniBar Integrated Voice mail - Attribution Integrated Voice Mail - Events Dynamic Suites Interrogation / Guest Telephone Account Night Audit request Database Reinitialization High Availability Spatial Redundancy OK OK OK OK OK OK OK OK NA NA NA OK OK With Alternate IP address and not DNS. ALE Application Partner Program Inter-working report Edition 03 page 12/73

13 Analog Voice Mail System VMS Voice mail box attribution Voice message deposit Voice message consultation an deletion Message Led switch-on/off Wake-Up time programming with IVR Wake-Up call from Application OK OK OK OK Done with prefixes OK OK SIP Trunk Voice Mail System VMS SIP Authentication SIP Registration SIP Option (Keep-alive) Voice mail box attribution Voice message deposit NA NA OK OK OK Voice message consultation an deletion Message Led switch-on/off OK OK Done by PMS and Message deposit information into M frame. SIP Extension Voice Mail System VMS SIP Extension - Registration Voice mail box attribution in VMS Voice message deposit from PBX Voice message consultation an deletion from PBX Message Led switch-on/off OK OK NOK NOK NOK 6.2 Summary of problems The SIP Extension Voice Mail System was configured and tested but it was not working as desired and test calls failed. Therefore we did use the SIP Trunking VMS to complete the functional tests of Voice Mail System. 6.3 Summary of limitations None ALE Application Partner Program Inter-working report Edition 03 page 13/73

14 6.4 Notes, remarks There was an issue with unwanted ACK sent by PMS (used as keep-alive in V24 link). It has been fixed during tests. The Reply frames were not taken into account at beginning but it has been modified into application software. The database re-initialization request has been added during test session. The Alternate IP address mode has also been added during tests. ALE Application Partner Program Inter-working report Edition 03 page 14/73

15 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 Alcatel-Lucent side or on Application Partner 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 03 page 15/73

16 8 Test cases 8.1 PBX PMS Check in with Guest Number (allocation on PBX) (mandatory in case of Guest management) / Use of PBX Voice Mail. JDS interact as PMS gateway with additional Front Office (like Opera, ). Front office will provide interface to Customer Front Desk and password is not used by Front office and need to be retrieve from JDS PMSi using an web link page. OXE Prefixes: - Wake-Up call prefix Cancel Wake-Up call prefix Room Status prefix MiniBar prefix Overflow busy/no answer to associate prefix 487 Test Case Id CIC201 CIC202 CIC203 CIC204 CIC205 CIC206 CIC207 CIC208 CIC209 CIC210 CIC211 Test Case Generate a check-in without PWD Generate a check-in with PWD (PWD sent by the PMS) Generate a check-in with an invalid Guest Number Generate a Check-in followed by an Allocation with an invalid room extension Generate a check-in without GPIN Auto assignment from Oxe. Generate a check-in with Status PBX: No DID Number available Generate a check-in with Deposit / Prepaiement. Generate a check-in with V.I.P status Generate a check-in with language parameter Generate a check-in with wake-up call time Generate a check-in with Direct Output Restrictions REPLY message expected from PBX N/A OK NOK Comment Reply= I with PWD Reply= I Reply =INV JG Reply= BR to H frame Reply Reply=INV JG Reply= IE Reply= IE Reply= IE Reply= IE Reply= IE Password is stored into JDS PMSi and not transmitted to Front Office. Use of for GPIN Not possible in Application. Not possible in Application. Not possible in Application. Into Check-in frame. Only with Modification frame because of Front office communication ALE Application Partner Program Inter-working report Edition 03 page 16/73

17 (Class of service) CIC212 CIC213 CIC214 Generate a check-in with Message deposite Generate a check-in with Do Not Disturb codes (1:Fwd VM, 2: DND) Generate a check-in with voice mail attribution Reply= IE Reply= IE PMS sends P frame Pbx sends Ack Only with Modification frame because of Front office communication Only with Modification frame because of Front office communication Not part of Check-in frame A Result Check-In With Guest Number Nota1: OXE System Parameters: Language 1=English, 2=French, 3=German, 4=Spanish. Nota2: OXE COS Public access: 0=closed no access, 2= Open all access - International. Nota 3: When Mini-PMS (PMS software by ImagineSoft) send Language number, it used a Modification frame. When Mini-PMS send the Class of Service, it used Check-in but then it cancel the Language and PBX put back the default language of the Room. If now with External PMS like Fidelio it will relay the frames to PBX. Nota4: This PMS do not work with Rotating DID and it need to manage itself the Guest Numbers Non-DDI and DDI.Management is now are Guests non DDI and are guests DDI. No more rotating DDI in PBX. ALE Application Partner Program Inter-working report Edition 03 page 17/73

18 8.2 PBX PMS Check in on Room Extension A Frame (mandatory in case of Room management) Room extensions are Booth extension is Test Case Id Test Case CIR101 Generate a check-in without PWD CIR102 CIR103 CIR104 Generate a check-in with PWD (PWD sent by the PMS) Generate a check-in with an invalid Room Extension Generate a check-in with an already checked-in Room extension CIR105 Generate a check-in with deposit CIR106 CIR107 CIR108 CIR109 CIR109 CIR109 Result Generate a check-in with V.I.P status Generate a check-in with language parameter Generate a check-in with wake-up call time Generate a check-in with Direct Output Restrictions COS Generate a check-in with Message Deposit (Message waiting) Generate a check-in with Do Not Disturb codes (1:Fwd VM, 2: DND) CHECK IN ON ROOM EXTENSION REPLY message expected from PBX Reply= I with Room extension and PWD Reply= IE Reply=INV JG Reply=INV JA Reply=I (if pwd) or Reply=IE Reply=I (if pwd) or Reply=IE Reply=I (if pwd) or Reply=IE Reply=I (if pwd) or Reply=IE N/A OK NOK Comment Error into log but not raised to Front Office. Error into log but not raised to Front Office. Use Modification frame only Use Modification frame only Use Modification frame only ALE Application Partner Program Inter-working report Edition 03 page 18/73

19 8.3 PBX PMS - Allocation of an Extension to a Guest H Frame (mandatory in case of Guest management) Test Case Id ALL101 ALL102 ALL103 ALL104 ALL105 ALL106 ALL107 ALL108 ALL109 ALL109 Test Case Allocation of a GUEST to an extension with room state = room cleaned. Allocation of a GUEST to an extension with room state = room not done for a new guest or the same guest a) Execute ( PBX initialisation) b) Refuse (PBX initialisation) Allocation of a GUEST to an extension with a GUEST NUMBER out of range ( it doesn't exist). Allocation of a GUEST to an extension with a GUEST NUMBER not checked-in. Allocation of a GUEST to an extension which is out of range ( ex: it doesn't exist). Allocation of a GUEST from a ROOM EXTENSION to another ROOM EXTENSION with DID and NONDID Guest numbers affected to both ROOMS. Allocation of a GUEST to a dynamic suite extension). Room move: Change a Guest from one room to another. Multi-occupation (Sharer mode): more than one Guest into a Room extension. Retire a GUEST of a Room Etension REPLY message expected from PBX a) execute with Reply=INV AO. b) Refuse with Reply=INV BO Reply=INV BG Reply=INV BA Reply=INV BR Use of H frame Reply=AO N/A OK NOK Comment According to value of Check-in Facility configuration Room not done: True/False) Not possible in application see chapter Result ALLOCATION of an extension to a guest ALE Application Partner Program Inter-working report Edition 03 page 19/73

20 8.4 PBX PMS Modification of Guest or Room configuration A Frame (mandatory in case of Guest management) Test Case Id MOC101 Test Case Modification of GUEST with NEW PWD (only for Guest) REPLY message expected from PBX N/A OK NOK Comment MOC102 Modification of GUEST with an invalid GPIN (only for Guest) Reply=INV NG MOC103 Modification with an no checked- in GPIN (only for Guest) Reply=INV NA MOC104 Modification of Deposit / Prepaiement Reply= ME MOC105 Modification of V.I.P status Reply= ME MOC106 MOC107 MOC108 MOC109 Modification of language parameter Programmation on wake-up call time Modification of wake-up call time Modification of wake-up call time Reply= ME Reply= ME PxxxxxW P Reply= ME PxxxxxW M Reply= ME PxxxxxW C MOC110 Modification of Class of service Reply= ME MOC116 Modification of the Guest Name Reply= ME MOC117 MOC118 Result Modification of message deposit (Switch on the LED message) Modification in Do Not Disturb state MODIFICATION of GUEST/ROOM configuration (1) While cancel wake-up by M frame with 00000, OXE answer a Reply with ME for Modification Executed then P frame with C for Cancel and the initial wake-up time. ALE Application Partner Program Inter-working report Edition 03 page 20/73

21 8.5 PBX PMS Room status change - C Frames(optional) Test Case Id Test Case Message Sent by PBX N/A OK NOK Comment STAT101 Room status message with maid identification code cxxxxx xxxx is for Room Number is for maid id -3 is the status code Frame Acked by Winpac and will be forwarded to Front Office. STAT102 Room status message without maid identification code STAT103 Room status message with different status managed by the PMS: Ex: Maid arrives in the room, room has be cleaned for a new guest or the same guest etc. Result ROOM STATUS change Note : to perform a Room status change, enter the prefix followed by a digit between 0 and 9 and release the line. Prefix for Room Status is 587 Codes used: 1 Vacant Clean, 2 Vacant Dirty, 3 Occupied Clean, 4 Occupied Dirty, 5 Inspected Occupied 8.6 PBX PMS Wake Up events - P Frames(optional) Test Case Id Test Case Messages send by PBX N/A OK NOK Comment WUP101 Wake-up message with normal answer from PMS ->Pgpin W A WUP102 Wake-up message with no answer ->PgpinW N WUP103 Wake-up message with busy line ->PgpinW B WUP104 Wake-up message with out of order line PgpinW O WUP105 Wake-up message generated by programming from a phone set PgpinW P WUP106 Wake-up message generated by modification from a phone set PgpinW M WUP107 Wake-up cancellation generated by modification message from a phone set PgpinW C Result WAKE- UP events Pbx prefixes for wake-up call management are: 506: wake-up programming, 507: wake-up cancellation ALE Application Partner Program Inter-working report Edition 03 page 21/73

22 8.7 PBX PMS Management of Call Tickets K or J Frames (Mandatory) Station Message Detail Recording Extended call ticket: K Frame / Reduced call ticket: J Frame Warning: The type of tickets K or J have to be configured into partner application. Test Case Id CAT101 CAT102 CAT103 CAT104 CAT105 CAT106 Test Case SMDR message of a charged outgoing call with pulses and costs. Extended Ticket Call done on room extension. SMDR message of a charged outgoing call with pulses and costs. Reduced Ticket Call done on room extension. SMDR message of a charged outgoing call with pulses or cost. Call done on booth extension. (1) SMDR message of a transfered outgoing call from room to room with pulses or cost.(2) SMDR message of a transfered outgoing call from an ADMIN extension to a GUEST with pulses or cost. SMDR message of a non charged outgoing call (Call not answered) Messages send by PBX K J. N/A OK NOK Comment The application does not take care of Pulses or Cost but calculate price with Duration and area codes. CAT107 SMDR message of an incoming call CAT108 CAT109 CAT110 SMDR message of a transfered incoming call SMDR message of a transferred outgoing call from ROOM1 to ROOM2 which is forwarded on mail box Management of SMDR messages for a Guest number in application. The accounting calculation is in JDS application and is sent then to Front Office. Result Management of CALL TICKETS: (1): When using booth in guest management, the external access require the Guest number and its personal code. (2): in Application/Hotel/Numerical parameters: transfer on hang-up for room sets= transfer on hang-up allowed. ALE Application Partner Program Inter-working report Edition 03 page 22/73

23 8.8 PBX PMS Data Transfer Management & MiniBar - P Frames (optional) Test Case Id DAT101 DAT102 DAT103 Test Case Generates a DATA TRANSFER message by MiniBar prefix and with informations in data field. Generates DATA TRANSFER messages by MiniBar prefix with more than 20 characters in data field.it's possible by generating a # character, that permits to send immediatly a first DATA TRANSFER message followed by an other one with the rest of the character If more than one code is used, do the same tests for each code. REPLY message expected from PBX Pxxxxx 477 yyyyyyyyy Xxxxx is room Yyyyyyy is codes N/A OK NOK Comment Result DATA TRANSFER Management Pbx Prefix for data transfer or MiniBar is 477. Coding is: xyy x is quantity and yy is item 8.9 PBX PMS - Interrogation management and PBX PMS Guest Telephone Account I & T Frames (optional) Test Case Test Case Id Asks for the GUEST or INT101 ROOM EXTENSION telephone accounts. Asks for the GUEST or ROOM EXTENSION INT102 telephone accounts with GUEST Number or ROOM EXTENSION out of range. Asks for the GUEST or ROOM EXTENSION INT103 telephone accounts with GUEST Number or ROOM EXTENSION not checked-in. Asks for the GUEST or ROOM EXTENSION telephone accounts. INT104 Verify the management of Cost, Total Deposit and Guest balance. Result Interrogation followed by Guest Telephone Account. REPLY message expected from PBX N/A OK NOK Comment Reply=INV RG Reply=INV RA Not supported by Partner ALE Application Partner Program Inter-working report Edition 03 page 23/73

24 8.10 PBX PMS PBX Voice mail attribution - F Frames (optional) Type of Omni Message: A4645 Test Case Id VAT101 VAT102 VAT103 VAT104 VAT105 VAT106 VAT107 VAT108 VAT109 VAT 110 VAT 111 VAT 112 VAT 113 Test Case Open a GUEST voice mail box Open a ROOM extension voice mail box Open a voice mail box on GUEST number out of range Open a voice mail box on ROOM extension out of range REPLY message expected from PBX Reply= FE Reply=INV WG Reply=INV WG Open a voice mail box on GUEST number non checkedin Reply=INV WA Open a voice mail box on ROOM extension not checked Reply=INV WA in Open a voice mail box on GUEST number with no more mail box available on PBX Reply=INV WX (this test is performed after the mail box is full) Open a voice mail box on ROOM EXTENSION with no more mail box available on Reply=INV WX PBX (this test is performed after the mail box is full) Open a voice mail box on GUEST with voice mail out of range or not linked on PBX (This test is performed by Reply=INV WV removing the directory voice mail number from hotel management) Open a voice mail box on ROOM EXTENSION with voice mail out of range or not linked on PBX Reply=INV WV (This test is performed by removing the directory voice mail number from hotel management) Open a voice mail box on GUEST number which Reply=INV WZ already owns a mail box Open a voice mail box on ROOM extension which Reply=INV WZ already owns a mail box Open a voice mail box on GUEST number by generating Reply=INV WJ N/A OK NOK Comment PMS sent FgpinP1 ALE Application Partner Program Inter-working report Edition 03 page 24/73

25 a false code in action field. VAT 114 VAT 115 Open a voice mail box on ROOM EXTENSION by generating a false code in action field. Open a voice mail box on GUEST number by generating a false code identification in the message Reply=INV WJ Reply=INV WK VAT 116 Open a voice mail box on ROOM EXTENSION by generating a false code identification in the message Reply=INV WK VAT 117 Close a GUEST voice mail box Only after Check-out but not individually. VAT118 VAT119 VAT120 VAT121 VAT122 Close a ROOM extension voice mail box Close a GUEST voice mail box which is working at this moment. Close a ROOM extension voice mail box which is working at the moment Close a GUEST voice mail box which has not consulted messages. Close a ROOM extension voice mail box which has not consulted messages. Reply=INV WW Reply=INV WW Reply=INV WM Reply=WM Only after Check-out but not individually. Configuration allows to close vm box even if not empty. Configuration allows to close vm box even if not empty. Result VOICE MAIL Attribution 8.11 PBX PMS PBX Voice mail event - F Frames (optional) Type of Omni Message : A4645 Test Case Id VEV101 VEV102 VEV103 VEV104 VEV105 Test Case Voice mail event after a message has been deposited in an empty mail box. Voice mail event after a message has been deposited in an non empty mail box. Voice mail event after a message deposit generates an overflow state. Voice mail event after box is becoming empty. Voice mail event on a non allocated GUEST Number after a message has been deposited Message Sent by PBX FgpinM1 FgpinM2. FgpinM0 N/A OK NOK Comment ALE Application Partner Program Inter-working report Edition 03 page 25/73

26 in an empty mail box. VEV106 VEV107 VEV108 VEV109 Result Voice mail event on a non allocated GUEST Number after a message has been deposited in an non empty mail box. Voice mail event on a non allocated GUEST: - then allocate the GUEST. - Listen messages and remove them. Listen messages on a non empty mail box after checkingout the Room extension. Check-in a guest or room extension which mail box isn t empty. VOICE MAIL event To consult voice mail dial PBX DYNAMIC SUITE - S Frame (optional, relevant only in case of Guest management) Test Case Id SUI101 SUI102 SUI103 SUI104 SUI105 SUI106 SUI107 SUI108 Test Case Create a suite with managing extension and moved slave extension Create a suite with managing extension and moved first level suite extension Create a suite with an out of range managing extension and moved slave extension Create a suite with a managing extension and a moved slave extension out of range Create a suite with managing extension already in a suite Allocate GUEST number to a suite Substract a slaved extension from the suite Substract a slaved extension which doesn t belong to the suite from the suite REPLY message expected from PBX N/A OK NOK Comment Reply INV SG Reply INV SR Reply INV SU Reply INV SU ALE Application Partner Program Inter-working report Edition 03 page 26/73

27 SUI109 Allocate a guest to a slave extension Reply INV SU Result DYNAMIC SUITE Not applicable with PMS PBX PMS Check out with Guest number management - D Frame (mandatory for Guest management) Test Case Id Test Case REPLY message expected from PBX N/A OK NOK Comment COC101 Check-out of a guest Number COC102 COC103 COC104 COC105 COC106 Check-out of a guest which room line is busy. PBX configuration: execute the command. Check-out of a guest which room line is busy. PBX configuration: refuse the command. Check-out of a guest with not consulted messages in the associated voice mail box. PBX configuration: execute the command. Check-out of a guest with not consulted messages in the associated voice mail box. PBX configuration: refuse the command. Check Out of an invalid guest Number Reply = OL Reply = PL Reply = OM Reply = PM Reply = PG Ext Call is released. Not used Message can still be consulted till next check-in. Not used COC107 Check-out of a Not checked in guest Number Reply = PA COC108 Check out with no guest in room Reply = PU COC109 COC110 COC111 COC112 Verify metering bills by checking-out a guest number Verify metering bills by checking out a guest number which was transferred from one room to another room and called from each of them. Verify metering bills by checking out a guest number which called from a booth extension. Check Out of a GUEST which is not allocated to a ROOM. Checked into Application ALE Application Partner Program Inter-working report Edition 03 page 27/73

28 Result CHECK OUT GUEST NUMBER (1) Application/Hotel/Consult-Modify: Checkout if Ext.Call=False (2) Application/Hotel/Consult-Modify: Checkout if Voice Mess=False ALE Application Partner Program Inter-working report Edition 03 page 28/73

29 8.14 PBX PMS Check out with Room number management D Frame (mandatory for Room management) Test Case Id COR101 COR102 COR103 COR104 COR105 COR106 Test Case Check Out of ROOM extension Check Out of a extension which room line is busy. PBX configuration: execute the command. Check Out of a room extension which room line is busy. PBX configuration: refuse the command. Check Out of a room extension with not consulted messages in the associated voice mail box. PBX configuration: execute the command. Check Out of a room extension with not consulted messages in the associated voice mail box. PBX configuration: refuse the command. Check Out of an invalid room extension REPLY message expected from PBX Reply = OL Reply = PL Reply = OM Reply = PM Reply = PG N/A OK NOK Comment COR107 COR108 Result Check Out of a Not checked in room extension Verify metering bills by checking out a room extension CHECK OUT WITH ROOM NUMBER MANAGEMENT Reply = PA ALE Application Partner Program Inter-working report Edition 03 page 29/73

30 8.15 PBX PMS Night Audit Request - N Frame (optional) Test Case Id NAU101 Test Case Generate a NightAudit REPLY message expected from PBX N/A OK NOK Comment Result NIGHT AUDIT REQUEST Done in Partner Application and not supported PBX PMS Re-initialization request and PBX PMS Database Reinitialization Z & U Frames (Recommended) JDS added the Database re-init request to his application and plan to check coherency between Database from Front Office (ex Fidelio) and PBX database. Test Case Id REI101 REI102 REI103 REI104 REI105 REI106 Test Case Generate a full re-init request for a Guest or a Room extension - ZxxxxxF Generate a partial re-init request for a Guest or a Room extension - ZxxxxxP Generate a re-init request for a Guest or a Room extension out of range Generate a re-init request for a Guest or a Room extension not checked in Generate a re-init request for every GUESTS or ROOM extensions checked-in..:- Full guest re-init. Z F Generate a re-init request for every GUESTS or ROOM extensions checked-in..: - Partial guest re-init. Z P REPLY message expected from PBX Reply = INV TG Reply = T N/A OK NOK Comment Result Database Re-initialisation Note : the strings send back are the same for a Full guest or a Partial guest re-init. ALE Application Partner Program Inter-working report Edition 03 page 30/73

31 Front-Office is master of guest database and do Swap Database to PMS at every restart for instance. In such situation, Meteor will request a check-out/checkin to the PBX for all rooms managed by the PMS. Meteor could not update the Front-office database because this is not in the protocol defined by the front office vendor like Fidelio. Database re-init has thus no interest with a solution based on Front-office----PMS-----OXE because the database synchro done between OXE and PMS would never be forwarded to Front-Office Disruption of AHL Link (mandatory) The Application PMS was installed on a PC in the Etesting Lab and we tested the link cut by disconnecting the Ethernet connection. Test Case Id DIS101 DIS102 DIS103 DIS104 DIS105 Test Case Cut the link between PMS interface and the PBX : Generate some events like wake-up and call-tickets on PBX side. Establish the link and verify that the events are taken into consideration on PMS side Cut the link between PMS interface and the PBX : Generate some events like check-in, allocations on PMS side. Establish the link and verify that the events are sent to the PBX. Cut the link between PMS interface and the PBX : Generate some events like wake-up and call-tickets on PBX side until the buffer is full. Establish the link and verify that the events are taken into consideration on PMS side. Power off the PMS interface and generate some events on PBX side.restart the interface and verify that the events are sent and taken in consideration on the PMS side. If the PMS is composed with several devices, the same tests has to be done by powering off and restarting separatly the different devices. REPLY messag e expecte d from PBX N/A OK NOK Comment Result DISRUPTION OF V24 AHL LINK If no keep-alive message for 60 seconds then connection is closed on OXE side. After reconnect of link the OXE wait 2 minutes before sending frames that are in buffer. ALE Application Partner Program Inter-working report Edition 03 page 31/73

32 8.18 JDS VMS Analog External Voice Mail and Wake-up call services This is a voice mail based on analog ports configured as VPS-4620 into PBX. The ports are managed as 4620 VPS into the OXE. The user rooms are managed with Voice Mail Dir.No.= (external VPS voice mail). Prefix for Forward on busy/no answer is 489. The message led is activated or switch-off with OXE prefixes configured into application voice mail. Test Case Id Test Case Messages N/A OK NOK Comment VMA101 Check-in a Guest in OXE Allocate Voice mail into application VMA102 VMA103 VMA104 VMA105 Message deposite to guest voice mail box -Call the Room and follow the overflow to Voice mail. -Leave your message Consult voice mail box from Guest -- -dial prefix VM consultation 43 here -dial 2 to consult messages Create a wake-up call from guest consultation -dial Voice mail consultation prefix 43 here -dial 1 for wake-up call -Enter the time for wake-up in 24 hour format or 4 * to cancel. Create a wake-up call from partner interface -Check that wake-up call is coming on time. VMA106 No answer for wake-up call VMA107 Room phone busy at wake-up time Result External Voice Mail and Wake-up call services From PMS: Aname. To VM: a5xxxxx with xxxxx guest called number. After deposit the message Led is blinking and got voice prompt from Oxe. Consult by dialling 43. Prefix is 43 then routing to VPS Pilote and get voice guides. Number of tries and delay between is configurable. 3 tries then go to voice mail of guest or reception Users: type= 4620 (VPS + CLIP) create 2 users Connect the 2 Analog interface to Meteor PC Dialogic. Groups/Hunting Group: Type=RSVP Hunting Group Application/Hotel: Guest Voice Mail MCDU= Voice Mail with code.secret consult=false Users: for Guest sets , manage VM directory=12429 Prefixes for Message Led: Message deposit:483 / Switch-off message led:482 Nota: Issue with A5+Number that goes only if dial consult VM prefix and not voice mail number We can not differentiate calling to Voice mail or Wake-up unless we have 2 groups and user has to dial its number to identify because oxe sent A7 and no directory number. ALE Application Partner Program Inter-working report Edition 03 page 32/73

33 8.19 JDS VMS SIP Trunking - Voice Mail for messaging Using SIP UDP/5060, no authentication, no registration. MWI is based on Message Deposit from PMS via AHL to provide a Business Center service where the Front Office is master. The Messages deposit dir.no. to define in OXE /Application/Hotel could not be a Voice Mail Directory No and it was necessary to manage a Virtual UA with immediate forwarded to VMS SIP directory number With this configuration, when there is a message waiting the PMS sends M Frame with Message deposit=1 and the Led of set blink. The guest will then call-back ( VMS) and get possibility to hear the message waiting. The License of VMS permits only 2 simultaneous channels. When reached then VMS send SIP 480 X Network Congestion. Test Case Id VMS101 VMS102 VMS103 Test Case N/A OK NOK Comment SIP Trunking set-up -Configuration of SIP External Gw to VMS and External Voice Mail directory number. -Configuration of SIP Proxy into VMS Check SIP-Option Keep-Alive from PBX to VMS Check SIP-Option Keep-Alive from VMS to PBX See Appendix B and C for details. Not supported by Application VMS104 SIP Registration VMS105 VMS106 SIP Authentication -SIP External Gateway configured with SIP Digest SIP Call from PBX user to VMS using Voice Mail Directory number VMS107 Leave a message from Local Caller VMS108 Leave a message from External Caller VMS109 Message Waiting Indication VMS110 VMS111 VMS112 Listening the voice messages -from Guest, dial 43 or Press 1 to listen your messages. Ask for transfer to Operator -from Guest, dial 43 or Press 0 to be transferred to Operator (or other directory Number) PIN code of Voice Mail Box management from Guest VMS113 Test SIP Call from VMS to PBX Not supported by Application Not supported by Application Not supported by Application No indication on Caller Line Identification in Voice mail messages. No indication on Caller Line Identification in Voice mail messages. Not done with SIP Notify but with AHL Message Deposit. Led blink and while off-hook get you have call-back waiting voice prompt and then auto routing to Fwd No pin code currently Only Incoming calls into VMS JDS. Result ALE Application Partner Program Inter-working report Edition 03 page 33/73

34 8.20 JDS VMS SIP Extension The JDS VMS is connected to the OmniPCX Enterprise using SIP registration on OXE SIP Users (Type: SIP Extension). The SIP extensions users are grouped into an Hunting Group. This Hunting Group Directory Number is set as the associate of the Guest Numbers or Room Numbers. Then the diversion or overflow if busy or no answer is set to Associate. Test Case Id VMS201 VMS202 Test Case N/A OK NOK Comment Configuration of users SIP Extension and Hunting Group SIP Registration of VMS to the SIP Extension ports VMS203 Box attribution into Winpac VMS204 Test call to Guest with diversion to VMS (SIP Ext Hunting Group) VMS205 Guest consultating its voice messages VMS206 Voice mail ports congestion VMS207 Message Waiting Indication MWI Result SIP Extension VMS ALE Application Partner Program Inter-working report Edition 03 page 34/73

35 8.21 High Availability Spatial Redundancy ComServer The Spatial Redundancy means that the main Com Server (CPU) of OXE is backed-up with another Com Server which is not in same IP subnet. Therefore, you got 2 physical Com Server IP addresses (A and B) and 2 role MAIN IP addresses (Main 1 and Main 2). Only one main is active at same time while the redundancy is active. To avoid split brain mode (both Com Server are Main simultaneously), the management define a reference shelf with Media-gateway board that will mark the connected CPU as Main (the other one has to restart to become finally the Stand-By). The Application will need to connect to active Main Com Server, in single Com Server, the connection is done directly to Com Server IP address but in duplicated Com Server and especially Spatial Redundancy mode, you will have 3 methods to set-up this connection: Alternate Proxy method: The PBX administrator provide you the 2 Main Com Server IP address and the application has to test (Ping / icmp) the answer of the IP address before it send connection request. DNS Delegation method: The application will make a name query directly to the company DNS server (Microsoft DNS Server or Open Source Bind stack) where there will be a relay or delegation to provide the right answer to name query according to real status of the Main Com Server. This method is the simplest as soon as your application is ready to make DNS query. JDS uses the Alternate Proxy method based on 2 IP addresses corresponding to the 2 roles Main (Main1 & Main2). Test Case Id SRC101 SRC102 SRC103 SRC104 SRC105 Test Case Type of Test N/A OK NOK Comment Check that management is correct for Spatial Redundancy Com Server configuration. Update should be done on Main and Stand- By Com Server. Running on MAIN 1 Com Server, switch over to second one by using command bascul and check that PMS and PBX still communicate over AHL Link. Running on MAIN 1 Com Server, switch over to second one by using command bascul and check that VMS and PBX still communicate over AHL Link. Check that when second com server become Stand-By, the Hotel link and Voice mail link are still active and messages are properly processed by PBX. Running on MAIN 2, with second CS in Stand-By, cut the ethernet link of that Main 2 Com Server and system should switch-over. Check correct operation of Hotel Link and Voice Mail Link. Com Servers status Main/Stand-By AHL TCP link PMS PBX Switch-over to Main2 SIP Trunk Link VMS PBX Switch-over to Main2 Main/Stand-By AHL TCP link & SIP Trunk Link PMS reconnected after 3 minutes to MAIN 2 SIP VMS was available for call just after switchover. Result Spatial Redundancy Com Server ALE Application Partner Program Inter-working report Edition 03 page 35/73

36 9 Appendix A : AAPP member s Application Description Jurudata Services Sdn. Bhd. (or JDS in short) has in-house developed WINPAC Property Management System Interface (commonly known as Call Accounting System or WINPAC PMSi in short) and WINPAC Voice Related System to cater for hospitality sector which integrates and works seamlessly with all major PMS and PABX systems; including Alcatel OmniPCX Enterprise. WINPAC PMSi is a Web-Based system designed as the Mediator between PMS and PABX System to enable vairous hospitality features and functionalities of both PMS & PBX; whilst capturing call charges, perform call computation etc. Whilst WINPAC Voice Related System is a dynamic voice messaging system designed to provide voice oriented services via Interactive Voice Response (IVR). The system offers the following guest-centric modules: Voice Mail (VMS) : Provides each Guest with a personal voice mailbox during check-in. Voice messages are recorded directly to Guest Mailbox. Guest can retrive voice messages easily by dialing a single digit number (speed dial) on Guest Room phone. Guest retrieval of voice messages from outside the Hotel can be performed with unique phone PIN enabled. Auto Wake-up (AWU) : Allows Hotel Operator/Staff to set a wakeup call to the guest rooms at the pre-set date & time per request from Guest. Alternative, Guest can set their wakeup call with preferred date & time using Guest Room phone. Room Status Updating (RSU) : Provides Housekeeping Staff and IVR system to post room status to the PMS in real-time to facilitate Front Office Personnel with latest room availability for efficient guest checkins. Minibar Posting (MNB) : Allows Housekeeping Staff to post minibar consumption (total or itemized) to the PMS in real-time. ALE Application Partner Program Inter-working report Edition 03 page 36/73

37 10 Appendix B: AAPP member s Application Configuration Requirements 10.1 Management of WINPAC PMSi / WINPAC VMS Analogue/ WINPAC VMS SIP Trunk Winpac PMS is designed as the mediator between Front Office and PABX system which helps to enable various functionality of the said systems whilst capturing various call charges and activities within the hotel or enterprise segment Main Screen In the main module screen shown above, it is divided into 3 areas, which are System Menu Panel, Interface Menu Panel and Call Charges Panel. In order to access these functions, login is required. Features: 1. Online Monitoring Statistics Total Call Charges for each Charge Type Amount of calls for each Charge Type Amount of Failed Call Posted calls Amount of Posted calls Amount of Not Posted / Administration calls 2. Online Call Charges Display Show details of each calls with cost, surcharge, Tax and Total Show calls which have errors like Rate Not Found 3. Activity Logging. (Enable tracking of user operations) 4. Support multiple brand of PBX s and FOS s in one system 5. Call Logging and Call Voucher 6. Computation Rate table support up to 20 digits (accurate zone/are charging) Unlimited charge type (up to 99) Multiple rate table based on carrier (provided PBX have indicator for each carrier) ALE Application Partner Program Inter-working report Edition 03 page 37/73

38 Support call charges based on region/zone (Africa, America, Asia, Europe, etc) Support call charging like surcharge and tax based on VIP code and extension. Support discount rate for holidays Support auto rounding (up/down) for surcharge, tax and total Support split call charging for call transfer (provided PBX have indicator) 7. Reports Interface Module The screen above shows an interface between WINPAC and Alcatel Pabx System & Front Office System Simulator. On this screen, you can see the status of the interface, communication port and it s port number used, Last Started interface, number of errors found during transmission of data signal, number of data receive send and receive, last send and receive date and time and scope for raw data and formatted data. This interface may support protocol such as UDP, TCP/IP and computer serial communication port. ALE Application Partner Program Inter-working report Edition 03 page 38/73

39 This module is to be activated during start up in order to capture all outgoing calls and also for PMS interfaces. Once this module is not functioning, it will result in, the calls is neither capturing nor the PMS functions is working. This module was designed as such that it cannot terminate itself, it needs main module to control it from shutting down or have interface pause or resume Intelligent Console Module (IC) WINPAC provides a module named Intelligent Console (IC) for user to do online viewing or monitoring of WINPAC operation whereby you can see which interface is active or down. In the event of an interface down, there will be a pop up window alerting the user of the situation. Besides this, user can do manual posting of either PMS functions posting to each interface like creating/deletion of mailbox, barring/un-barring of phone lines, etc. and posting of charges to the front office system. This module also allows system administrators or authorised users to connect using TCP/IP-based client connection. ALE Application Partner Program Inter-working report Edition 03 page 39/73

40 System Operations & Maintenance WINPAC provide this module for user to add, modify, delete, edit, view and print the database setting for Extension List, Group List, Rate Table, etc. To enter this maintenance setting, you must login into the system. Refer to chapter Mapping of Room Status This option is used to map the Room Status from one to another interface. For e.g. VCS provides 01, WINPAC needs VC and FOS needs 1 for Vacant Clean. ALE Application Partner Program Inter-working report Edition 03 page 40/73

41 Mapping of Language This option is used to map the language from one to another interface. For e.g. FOS needs EA, PBX needs 1 and VMS needs 2 for the language codes Mapping of COS This option is used to map the Class of Service from one to another interface. For e.g. FOS needs 01 and PBX needs 15 for bar IDD Calls Reporting Module Once this reporting module is activated, you will see the screen shown as above. You may select any report listed on the report menu. Once you have chosen a report from the report menu, a screen for inputting value will appear. This screen allows you to filter the parameter for reporting. ALE Application Partner Program Inter-working report Edition 03 page 41/73

42 Web Winpac Console The Web Winpac v3 Console - (Call Accounting System) for Windows system provides remote report access for Call Accounting System. It is designed to run on Internet Explorer \ Mozilla Firefox \ Safari and Opera browser. Basically most Windows based internet browser. ALE Application Partner Program Inter-working report Edition 03 page 42/73

43 10.2 Management of WINPAC VMS Analogue Winpac VMS Analogue is computer-based system that allows users and subscribers to exchange personal voice message to select and deliver voice information; and to process transactions relating to individuals, organizations, products and services, using an ordinary telephone. When a guest checks into the hotel, the guest is automatically assigned a personal Voice Mailbox for the duration of his stay in the hotel. This Mailbox will provide a private and confidential messaging environment for the guest Main Screen Channel Activities shows the channels status and activities. Activities can be such as playing a voice prompt, accepts an input dtmf digit, etc. Status can be Idle,etc. If red color appears, that means system encounters an error while performing the operation on that particular channel. Communication shows TCP/IP packets as well as serial port packets. There are four types of color representation. Blue color indicates normal messages, green indicates data is received either via TCP/IP or serial port, purple indicates data is sending out and red indicates error messages. means activities will be shown on the screen, if tick is removed, activities will not be shown on the screen but will be logged to the log files. ALE Application Partner Program Inter-working report Edition 03 page 43/73

44 VM Configuration / Maintenance This is the main screen of VM Configuration Program; left panel is a tree view whereby when it is clicked, the right panel of the windows will change accordingly. ALE Application Partner Program Inter-working report Edition 03 page 44/73

45 Channel Indicates the configuration information about the types of line, default script to be play, language for each single extension analogue line Language This section allows installer to setup language code used by the system and also mapping language code of PMS. ALE Application Partner Program Inter-working report Edition 03 page 45/73

46 Extension/ Room This section allows installer to setup extension/ room used by the system. It will display all existing extension and rooms in the database. New extension and room can be created using Add button and existing record can be changed or deleted using Edit or Delete button Web Winpac VMS The Web Voice Console - (Hotel Voic System) for Windows system provides remote report access for Hotel Voic System. It is designed to run on Internet Explorer \ Mozilla Firefox \ Safari and Opera browser. Basically most Windows based internet browser. ALE Application Partner Program Inter-working report Edition 03 page 46/73

47 The dashboard feature basically will display the summary analysis report in various of chart type. By using this feature, user will be able to know the statistics of the wakeup call status and minibar posting by daily and monthly basis. The statistic is based on the activities processed by the Hotel Voic System. If there is no record found, it will be shown as blank. The dashboard statistics covered: ALE Application Partner Program Inter-working report Edition 03 page 47/73

48 10.3 Management of WINPAC VMS SIP Trunk Winpac VMS SIP Trunk is computer-based system with fully TCP-IP connection to Alcatel pabx that allows users and subscribers to exchange personal voice message to select and deliver voice information; and to process transactions relating to individuals, organizations, products and services, using an ordinary telephone. When a guest checks into the hotel, the guest is automatically assigned a personal Voice Mailbox for the duration of his stay in the hotel. This Mailbox will provide a private and confidential messaging environment for the guest Main Screen Call Details Records shows the status and activities. Media Control Units shows type of connections, description of the channel and packets. ALE Application Partner Program Inter-working report Edition 03 page 48/73

49 Activities will be shown on the screen, if tick is Clear all button, activities will not be shown on the screen but will be logged to the log files Web Winpac VMS The Web Voice Console - (Hotel Voic System) for Windows system provides remote report access for Hotel Voic System. It is designed to run on Internet Explorer \ Mozilla Firefox \ Safari and Opera browser. Basically most Windows based internet browser. ALE Application Partner Program Inter-working report Edition 03 page 49/73

50 The dashboard feature basically will display the summary analysis report in various of chart type. By using this feature, user will be able to know the statistics of the wakeup call status and minibar posting by daily and monthly basis. The statistic is based on the activities processed by the Hotel Voic System. If there is no record found, it will be shown as blank. ALE Application Partner Program Inter-working report Edition 03 page 50/73

51 The dashboard statistics covered: ALE Application Partner Program Inter-working report Edition 03 page 51/73

52 11 Appendix C: Alcatel-Lucent Platform: configuration requirements 11.1 Management of OmniPCX Enterprise The OmniPCX Enterprise can be either manage with terminal console using telnet/ssh and mgr command or using the GUI OmniVista In Guest Management, Voice mail Number (ext vm sip) has to be assigned to Room Extension to get correct integration (Consult messages with prefix 43 / Automatic overflow to VM after 15sec) Room Extension Management ALE Application Partner Program Inter-working report Edition 03 page 52/73

53 In Guest management, the Use Type of Dir No for Room Extension is set to Multi-Occupation. In Room Management, the Use Type of Dir No for Room Extension is set to Normal. Hotmenu display of rooms: DISPLAY ALL ROOMS : : : Room no. : : : : : : : : : : Type : 1 : 1 : 1 : 1 : 1 : 1 : 1 : 1 : : Pla. Stat : 1 TD : 1 RE : 1 4 : 1 TD : 1 RE : 1 TD : 1 TD : 1 : : Guest Num. : : : : : : : : : : : : Room no. : : : : : : : : : : Type : 1 : 1 : 1 : 1 : 1 : 1 : 1 : 1 : : Pla. Stat : 1 : 1 TD : 1 TD : 1 TD : 1 TD : 1 TD : 1 TD : 1 TD : : : : Room no. : : : : : : : : : : Type : 1 : 1 : 1 : 1 : 1 : M 1 : S 1 : S 1 : : Pla. Stat : 1 TD : 1 TD : 1 TD : 1 5 : 1 TD : 1 TD : 1 TD : 1 TD : : Guest Num. : : : : : : : : : : : Number of displayed rooms : 24 Press any key to continue or <CR> to return to the previous menu 11.3 Guest Number Management (GPIN) We used GPIN to In Guest management, the Use Type of Dir No for GPIN is set to Guest. ALE Application Partner Program Inter-working report Edition 03 page 53/73

54 11.4 Application Hotel Management The Message deposit directory Number is used while the guest has a waiting message that was deposit by PMS to OXE using the Modification frame. ALE Application Partner Program Inter-working report Edition 03 page 54/73

55 Management mode can be Guest Management or Room Management. (To change from one mode to other, it is requiered to delete all Hotel rooms and guests) 11.5 Application Hotel Computer Link Management The interface configuration has to be set to Master in order to have the AHL over TCP-IP link. The CPU address has to be set with: Main IP Address of OXE if OXE is Stand-alone mode or regular redundancy mode (2 CPU into same IP Subnet). Or IP Address of PMS if having OXE in Spatial Redundancy configuration (2 CPU into different IP Subnets). ALE Application Partner Program Inter-working report Edition 03 page 55/73

56 11.6 Analog voice mail VPS configuration Analog user with set type 4620 (VPS + CLIP) Hunting group with type RSVP with Analog users External voice mail directory number ALE Application Partner Program Inter-working report Edition 03 page 56/73

57 11.7 SIP Trunking voice mail Management You have to manage an External Voice Mail Directory Number that is connected to SIP External Gateway 14. In order to identify correctly the service Voice mail, it was necessary to create a virtual user that is forwarded to External VM dir number. This number is in OXE hotel application as the Message deposit dir no. This is because the VMS dose not send the Message waiting indication directly to OXE but via the PMS using message deposit into Modification Frame. ALE Application Partner Program Inter-working report Edition 03 page 57/73

58 11.8 Class of service configuration Set the Message Deposit and Switch off Message Led for MWI from Analog VM As default value the Phone feature class of service is set to 0 for all users in OXE. ALE Application Partner Program Inter-working report Edition 03 page 58/73

59 11.9 Prefixes management ALE Application Partner Program Inter-working report Edition 03 page 59/73

60 11.10 Integrated Voice mail assignment The integrated voice mail is based on 4645 VM embedded into OXE ComServer. ALE Application Partner Program Inter-working report Edition 03 page 60/73

61 11.11 Analog Voice mail assignement ALE Application Partner Program Inter-working report Edition 03 page 61/73

62 11.12 SIP Trunk Voice mail assignment The SIP voice mail number is managed as External Voice Mail and calls are routed to a SIP Trunk Group toward Partner Application SIP Trunking management You need a SIP Trunk Group and an External SIP Gateway. Protocol used between call Handling and virtual coupler is ISDN all Countries. The T2 Specification can be SIP (60 Channels) or Mini SIP (4 channels). ALE Application Partner Program Inter-working report Edition 03 page 62/73

63 Trkstat 114 +==============================================================================+ S I P T R U N K S T A T E Trunk group number : 114 Trunk group name : SIP JDS Number of Trunks : 4 Max. Voice calls : Not Restricted Index : State : F F F F F: Free B: Busy Ct: busy Comp trunk Cl: busy Comp link WB: Busy Without B Channel Cr: busy Comp trunk for RLIO inter-act link WBD: Data Transparency without chan. WBM: Modem transparency without chan. D: Data Transparency M: Modem transparency (102)etesting2-a> ALE Application Partner Program Inter-working report Edition 03 page 63/73

64 11.14 SIP Extension VMS configuration The directory number is an Hunting group call number for SIP Extension Voice mail. The directory numbers and are the user numbers declared as SIP extension type and corresponding to Voice Mail ports. Management of Associate for GPIN in Guest management ALE Application Partner Program Inter-working report Edition 03 page 64/73

65 Management of Associate for Room management Management of prefix to validate the auto overflow to associate Management of Class of service to allow the feature overflow ALE Application Partner Program Inter-working report Edition 03 page 65/73

66 11.15 AHL Link configuration tips - To take into account the modifications made to the AHL configuration, ahltcp has to be restarted. To do this, connect as root and run: dhs3_init R AHLTCP (respect upper-case letters) - - If the AHL Computer Link uses IP protocol, it has to be configured as Master and the CPU address that has to be defined is the Call Server Main IP address. - If the management mode has to be changed from Guest to Room : Check out every guests (possibility to have the list with the hotmenu and hotdebug commands) Delete every guests declared in the Users Change all the Room Users for Administrative and Normal (this has to be done at the same time) Change the management mode in Application / Hotel Put every Users needed in Room / Normal ALE Application Partner Program Inter-working report Edition 03 page 66/73

67 12 Appendix D: AAPP member s escalation process MALAYSIA HEAD QUARTER 地区 AREA 姓名 NAME 分机 EXTENSION 手机号码 MOBILE NO. ALL SALES: lumpc@jds.com.my COUNTRIES Mr. Lum Peng Chee jackie.chang@jds.com.my Ms. Jackie Chang toongsh@jds.com.my Mr. Toong Siew Heng TECHNICAL: Mr. Andrew Lim andrewlim@jds.com.my Mr. Syaiful Izham syaiful.izham@jds.com.my JDS 24x7 SUPPORT HOTLINE: JDS SUPPORT support@jds.com.my CHINA 地区 AREA 姓名 NAME 电话 TELEPHONE NO (DURING OFFICE HOURS) 手机号码 MOBILE NO. 上海 SALES OR SHANGHAI 郭贻忠 ( 总经理马来西亚人 ) jududata@jds.com.my 朱李月 ( 出纳兼销售 ) zlylisa@jds.com.my TECHNICAL 姚庆 ( 工程师 ) Terry@jds.com.my 郑钰峰 ( 工程师 ) Seven@jds.com.my 卢晓洁 ( 秘书 ) lxj@jds.com.my 赵丽丽 ( 兼职会计 ) 上海 24 小时维保热线电话 SHANGHAI 24x7 SUPPORT HOTLINE: 上海 24 小时维保热线 SHANGHAI 24x7 SUPPORT jududata@jds.com.my 地区 AREA 姓名 NAME 电话 TELEPHONE NO (DURING OFFICE HOURS) 手机号码 MOBILE NO. 北京 SALES BEIJING 黄继辉 ( 北京经理 ) jerryhuang@jds.com.my 郭秦 ( 行政 ) nancyguo@jds.com.my TECHNICAL 李洋 ( 工程师 ) leif@jds.com.my 程泽旭 ( 工程师 ) kaka@jds.com.my 高淑凤 ( 兼职会计 ) 北京 24 小时维保热线电话 BEIJING 24x7 SUPPORT HOTLINE: OR 地区 AREA 姓名 NAME 电话 TELEPHONE NO (DURING OFFICE HOURS) 手机号码 MOBILE NO. 广州 SALES guangzhou 区少玲 ( 广州经理 ) nicole.ou@jds.com.my TECHNICAL 柯奇志 ( 工程师 ) evan@jds.com.my 石尹聪 ( 工程师 ) mori@jds.com.my 广州 24 小时维保热线电话 GUANGZHOU24x7 SUPPORT HOTLINE: OR THAILAND 地区 AREA 姓名 NAME 分机 EXTENSION 手机号码 MOBILE NO. THAILAND SALES +66 (0) or 50 ONLY Ms. Narisra Chungwatana +66 (0) narisra@jds.com.my TECHNICAL Mr. Thitiphan Pongsanoi +66 (0) thitiphan@jds.com.my THAILAND 24x7 SUPPORT HOTLINE: THAILAND 24x7 SUPPORT th.support@jds.com.my ALE Application Partner Program Inter-working report Edition 03 page 67/73

68 13 Appendix E: AAPP program 13.1 Alcatel-Lucent Application Partner Program (AAPP) The Application Partner Program is designed to support companies that develop communication applications for the enterprise market, based on Alcatel-Lucent Enterprise's product family. The program provides tools and support for developing, verifying and promoting compliant third-party applications that complement Alcatel-Lucent Enterprise's product family. ALE 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 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 03 page 68/73

69 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 03 page 69/73

70 14 Appendix F: AAPP Escalation process 14.1 Introduction The purpose of this appendix is to define the escalation process to be applied by the ALE Business Partners when facing a problem with the solution certified in this document. The principle is that ALE 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 and the Application Partner, are engaged as following: (*) The Application Partner Business Partner can be a Third-Party company or the ALE Business Partner itself ALE Application Partner Program Inter-working report Edition 03 page 70/73