Application Partner Program Inter-Working Report · ... FCS Computer Systems Sdn Bhd ... Alcatel-Lucent Application Partner Program – Inter-working report ... Application Partner
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
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.
Date of the certification 2013-08-28 to 2013-08-30
Date of regression tests 2013-11-27
Alcatel-Lucent’s representative Rong LIU
AAPP member representative Jimmy Lew Cher Wen/Ricky Huang
Alcatel-Lucent Communication Platform
OmniPCX Enterprise
Alcatel-Lucent Communication Platform release
R10.1.1-J260322
AAPP member application release Version 2.0
Application Category Voice Mail Hospitality dedicated software
Author(s): Rong LIU Reviewer(s): Denis Lienhart History: Edition 1: Creation of the document – 11-22-2013 Edition 2: Extension to OXE R11 – February 2014 Edition 3: Mention to SIP removed to avoid confusion – February 2014
Test results
Passed
Refused Postponed
Passed with restrictions
Refer to Section 6 for a summary of the test results.
IWR validity extension Extended to OXE R11 – February 2014
Contact Name: Hoo Chong Kee Title: VP of Software Development – UMS & Windows Applications Address: FCS Computer Systems Sdn Bhd C1001 Block C, Kelana Square No.17 Jalan SS7/26, Kelana Jaya 47301 Petaling Jaya
Selangor, Malaysia Phone: + 60 3 7953 7357 Fax: + 60 3 7953 7312 Web address: www.fcscs.com E-mail: [email protected]
6 SUMMARY OF TEST RESULTS ........................................................................................................ 11
6.1 SUMMARY OF MAIN FUNCTIONS SUPPORTED ...................................................................................... 11 6.2 SUMMARY OF PROBLEMS ................................................................................................................... 11 6.3 SUMMARY OF LIMITATIONS ............................................................................................................... 11 6.4 NOTES, REMARKS .............................................................................................................................. 11
7 TEST RESULTS ..................................................................................................................................... 12
7.1 INTEGRATION WITH FCS UNICORN .................................................................................................... 12 6.2 CHECK OUT GUEST ............................................................................................................................... 15 6.3 AUTO WAKEUP (AWU) ......................................................................................................................... 15 6.4 MINIBAR ................................................................................................................................................ 17 6.5 ROOM STATUS ........................................................................................................................................ 18 7.6 LEVEL INTEROPERABILITY TEST (ANALOG PROTOCOL) .................................................................... 18
12 APPENDIX E: AAPP ESCALATION PROCESS ........................................................................... 36
12.1 INTRODUCTION .................................................................................................................................. 36 12.2 ESCALATION IN CASE OF A VALID INTER-WORKING REPORT ............................................................. 37 12.3 ESCALATION IN ALL OTHER CASES ..................................................................................................... 38 12.4 TECHNICAL SUPPORT ACCESS ............................................................................................................ 39
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 (https://businessportal.alcatel-lucent.com) in the Application Partner Interworking Reports corner (restricted to Business Partners)
- the Application Partner portal (https://applicationpartner.alcatel-lucent.com) with free access.
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.
Technical support will be provided only in case of a valid InterWorking Report (see chapter 2 “Validity of the InterWorking Report) and in the scope of the features which have been certified. That scope is defined by the InterWorking report via the tests cases which have been performed, the conditions and the perimeter of the testing as well as the observed limitations. All this being documented in the IWR. The certification does not verify the functional achievement of the AAPP member’s application as well as it does not cover load capacity checks, race conditions and generally speaking any real customer's site conditions.
Any possible issue will require first to be addressed and analyzed by the AAPP member before being escalated to Alcatel-Lucent. For any request outside the scope of this IWR, Alcatel-Lucent offers the “On Demand Diagnostic” service where assistance will be provided against payment. For more details, please refer to Appendix F “AAPP Escalation Process”.
3.1 Case of additional Third party applications
In case at a customer site an additional third party application NOT provided by Alcatel-Lucent is included in the solution between the certified Alcatel-Lucent and AAPP member products such as a Session Border Controller or a firewall for example, Alcatel-Lucent will consider that situation as to that where no IWR exists. Alcatel-Lucent will handle this situation accordingly (for more details, please refer to Appendix F “AAPP Escalation Process”).
4 Application information Application type: Hospitality & IVR Application commercial name: FCS Phoenix Application version: Version 2.0 Interface type: Analog Interface version (if relevant): FCS Phoenix v2.0 is running on SIP protocol with list of RFC standardization such as RFC3261, RFC1889 (for RTP), RFC3550, RFC2833 (for DTMF) and etc. It also supports traditional analog interface. This last interface has been tested in this IWR. Brief application description: FCS Phoenix is the next generation industry-renowned dynamic voice messaging system designed for hotels and resorts that enables all voice service operations via Interactive Voice Response (IVR). The communications architecture developed by FCS integrates and works seamlessly with all major PMS and PABX systems (included Alcatel OmniPCX Enterprise). This is to ensure guest’s voice messaging is handled securely, efficiently and completely. All the voice messages are dynamically maintained and stored in a dedicated server within our database so important messages can be archived for easy retrieval when required. FCS Phoenix offers the following guest-centric features –
Voicemail: FCS Phoenix provides each guest with a personal voice mailbox during check-in. This means that voice messages are recorded directly in the recipient’s personal voice mailbox. Retrieving messages from the guestroom is easy and only requires dialling a single-digit number (speed dial) on the guest phone in the room. However, retrieving messages from outside the hotel requires guests to enter their unique PIN before permitting them to listen to their messages
Send and receive fax
Auto Wakeup call (AWU): Allow hotel staff to set a wakeup call to the guest rooms at the pre-set time/date as per guest request; or the guest himself can set one from the room phone
Mini Bar Posting: Allow Housekeeping to post mini bar consumption (total or itemized) to the PMS in real-time
Room Status Update: Offers Housekeeping staff an IVR system to post room status to the PMS in real-time to facilitate Front Office personnel with the latest room availability for efficient guest check-ins
5.1 General architecture The tests were performed on the Alcatel Technical Support Large Systems platform in the following environment: Figure 1 Test environment
Message Waiting Indication (MWI) ON/OFF – Analog ok
Phoenix (High Level) Module
Able to call in to Phoenix via Pilot number provided ok
Able to leave voice message for guest/admin ok
Guest/Admin phone MWI is ON when new message available ok
Guest/Admin able to listen to voice message ok
Guest/Admin phone MWI is OFF when no more new message ok
WebUI able to track guest/admin voice messages ok
WebUI able to track guest/admin voice message ok
Guest/Admin able to record own greeting message ok
Guest/Admin able to change PIN number ok
Guest/Admin can change default language prompt ok
Guest can set Auto Wakeup Call (AWU) from phone ok
WebUI able to track and monitor AWU set by guest ok
AWU is trigger according to the date/time set by guest ok
Admin can do minibar & room status posting via phone ok
WebUI able to track and monitor Minibar & Room Status posted via Phone
ok
Able to transfer call to operator ok
Able to terminate the call from either the phone or application ok
Able to call in to the various call flows based on specific numbers tied to entry points (numbers programmed in the PBX to call forward to Phoenix Pilot Number)
ok
Able to send fax to a DID assigned to a room N/A
Guest able to retrieve fax from in-room fax machine N/A
6.2 Summary of problems
None
6.3 Summary of limitations Need at least 1 VPS line for Message waiting light ON/OFF operation. This should be
configured in separate RSVP group. Can’t have VPS line working for Message waiting light together with left message , retrieve message, transfer call in one RSVP group. This need FCS side do more development.
SIP extension can’t work for message deposit prefix. SIP extension not passed test. See
crms00425847.
6.4 Notes, remarks
FCS phoenix VPS interface only operate on physical room number for message deposit. Message lamp on/off need more than 12s.
7.1 Integration with FCS Unicorn (Some test cases are optional as they do not directly integrate with Alcatel-Lucent system)
Case No
Protocol involved
Test title and test description
Expected Result
Result and Comment
6.1.1 N/A Check in a guest manually from Unicorn
Able to view guest already checked in via web
ok
6.1.2 N/A Check out a guest manually from Unicorn
Able to view guest already checked out via web. It should not be in the list of checked in guest anymore.
Ok
6.1.3 Analog Room Move 1. Check in a room (A) and view the status from web module 2. Leave a voice message to Room A 3. Use a simulated FOS to do a room change from Room A to Room B 4. Retrieve the voice message using Room B phone
1. Room (A) with guest info accurate 2. Web module on guest info will indicate new message. 3. Web module indicates the guest in a new room number with correct no. of messages. 4. Able to retrieve the voice message left while in previous room.
ok
6.1.4 Analog Check message waiting lamp on guest phone 1. Leave a voice message for guest
1. Message Waiting Lamp turn ON
ok
6.1.5 Analog Check message waiting lamp on guest phone 1. Retrieve all new messages on guest phone
1. Message Waiting Lamp turn OFF
ok
6.1.6 Analog Able to leave message when no one answer the call 1. Call a guest phone, do not answer the phone
Voice prompting to leave message should take over after a pre-set no. of rings /
retrieve voicemail will prompt user to choose whether to retrieve text message or not 2. User transferred to message desk extension
6.1.16 Analog Able to change guest pin no. 1. Go to feature menu and select to change the pin no. Enter the desired pin no.
The new pin no. is announced right after keying in.
Ok
6.1.17 Analog Able to change admin pin no. 1. Go to feature menu and select to change the pin no. Enter the desired pin no. 2. Try to call voice mail system to retrieve voice message, keying in using the new pin
1. The new pin no. is announced right after keying in. 2. Can access voicemail using new pin
Ok
6.1.18 Analog Forwarding message 1. Forward a message from one admin to another admin extension
Able to forward message to another mailbox. Ensure the message count incremented.
ok
6.1.19 N/A Do manual check in from web module
Able to view guest already checked in via web
ok
6.1.20 N/A Do manual check out from web module
Able to view guest already checked out via web. It should not be in the list of checked in guest anymore.
ok
6.1.21 N/A Manual name change, room change and language change via web module
Guest name can be changed. Room change can be performed. Language can be changed.
ok
6.1.22 Analog Message lamp is ON when there is at least 1 new
Test title and test description Expected Result Result and Comment
6.4.1 N/A Create minibar item 1. Go to the web “Hotel Operation -> Item Pricing” to create minibar items
Able to create minibar item and able to view the list from the web.
ok
6.4.2 N/A Create user via web to use minibar system 1. Create Supervisor ID, Minibar/Room Status ID from web “Hotel Operation – Hotel User -> User Configuration”
Able to create minibar users and able to view the list from the web.
ok
6.4.3 Analog Able to record new item prompt using Supervisor ID
Confirm that the prompt is recorded and can be heard.
ok
6.4.4 Analog Able to do minibar posting from room through phone
Confirm that the item correctly posted and information sent to Unicorn
ok
6.4.5 N/A Able to do minibar posting from room through web
Confirm that the item correctly posted and information sent to Unicorn
ok
6.4.6 N/A Able to generate all minibar reports with correct posting amount in web “Reports -> Minibar”
Report generated should be accurate and complete.
ok
6.4.7 N/A Able to do total minibar posting based on system setting
Check that correct record received by Unicorn
ok
6.4.8 N/A Able to view/edit/delete users from web “Hotel Operation – View/Edit/Delete User”
Action submitted takes effect. The web list of users reflects the changes.
ok
6.4.9 N/A Able to view/edit/delete minibar items from web “Hotel Operation – Item Pricing”
Action submitted takes effect. The web list of minibar items reflects the changes.
Test title and test description Expected Result Result and Comment
6.5.1 Analog Able to post room status from room
Status posted correctly to Unicorn
ok
6.5.2 N/A Able to post room status from web “Hotel Operation – Room Status Posting”
Status posted correctly to Unicorn
ok
6.5.4 N/A Able to generate all room status report on web “Reports – Room Status Reports”
The details listed are accurate as the actual status and time posted.
ok
7.6 Level Interoperability Test (Analog Protocol)
Case No
Test title and test description Expected Result Result and Comment
6.7.1 Obtain Caller ID Traceable via Channel Monitor.
ok
6.7.2 Incoming Call (call made from a phone that is connected to PBX to Phoenix)
Call is answered and all signals are handled properly. Traceable via Channel Monitor.
ok
6.7.3 Outgoing Call (call made from Phoenix to any phone that is connected to the PBX)
Phone is ringing and once answered, all signals are handled properly. Traceable via Channel Monitor.
ok
6.7.4 Transferring call (After the call is connected, Phoenix may initiate a call transfer using PBX flash hook method to 3rd party phone that is connected to the PBX)
3rd party phone is ringing and when answered can hear the conversation between 1st party and 3rd party. Traceable via Channel Monitor.
ok
6.7.5 Disconnecting call (After the call is connected, caller will hang up the phone)
Signal on call disconnect is handled properly. Traceable via Channel Monitor.
ok
6.7.6 Disconnecting call (After the call is connected, Phoenix will disconnect the call)
Signal on call disconnect is handled properly. Traceable via Channel Monitor.
ok
6.7.7 Send a message waiting indicator (MWI) to set the message light ON
Signal is handled properly and the message lamp on the
8 Appendix A : AAPP member’s Application description & configuration
Below is the configuration of all components of FCS Phoenix. Hardware and Software pre-requisite.
Software
Operating System Microsoft Windows Operating System
Microsoft Windows 2008 Server 64-bit
Microsoft Windows 7 Pro 64-bit
Browser Internet Explorer Version 7/8/9
Database MYSQL Version 5.5/5.6
Others FCS Unicorn
Hardware
Processor Intel i5 or i7 2.0GHz CPU or higher
Memory 6GB DDR-2 RAM or higher
Hard Drive 146GB Hard Disk or higher
Network Card Gigabit Ethernet LAN Card
Monitor Support 1024x768 Resolution
Analog Interface Card
Synway SHT-8C/PCI/FAX (8-port analog card, PCI interface)
Installation Guide
Install FCS Phoenix and 3
rd party components
o Run the setup file for the FCS Phoenix to install the system along with all the relevant 3
rd party components
Network configuration
o The IP address of Phoenix must be within the same subnet group with Unicorn and Alcatel PBX.
o The common “Ping” command shall be used to verify the proper setup of networking of all these PCs.
FCS Phoenix engine configuration
Those configuration files for each module are located at <Phoenix Folder>\config. Set the Name and Location (common used IP or DNS) for the module. Set the LocalIPAddr (for HMPCall_Config only). Set the Type, IP Address, Username and Password for database accordingly.
9 Appendix B: Alcatel-Lucent Communication Platform: configuration requirements
The test is based on hotel Guest management. 1.VPS line configuration: We configure 4502,4503 as 4620 type VPS line and put it in RSVP group 4336. This 4336 group is used to left voice message , transfer call, consult voice message, minibar. Configure 4501 VPS line and put it in RSVP group 4337. RSVP group 4337 used for message waiting Lamp on/off.
With this configuration, after left voice mail display “1 call back” on phone set.
Use this prefix to retrieve voice message. Also manage #91 for voice mail deposit and *90 for Message LED off. See related configuration in FCS page. 3. For minibar management Configure ghost z set: 4333, make 4333 immediate forwarding to 4336.
Any request or support issue reported and not responded within the Expected Response Time as stipulated above, customer may proceed to initiate the various levels of escalation to FCS accordingly by contacting the list of FCS personnel as provided in 5. Escalation Contacts. ESCALATION CONTACTS PHONE CONTACT FOR ESCALATION OF RESPONSE TIME & EMERGENCY CONTACT 1ST LEVEL ESCALATION
11.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's product family. The program provides tools and support for developing, verifying and promoting compliant third-party applications that complement Alcatel-Lucent's product family. Alcatel-Lucent facilitates market access for compliant applications. The Alcatel-Lucent Application Partner Program (AAPP) has two main objectives:
Provide easy interfacing for Alcatel-Lucent communication products: Alcatel-Lucent's communication products for the enterprise market include infrastructure elements, platforms and software suites. To ensure easy integration, the AAPP provides a full array of standards-based application programming interfaces and fully-documented proprietary interfaces. Together, these enable third-party applications to benefit fully from the potential of Alcatel-Lucent products.
Test and verify a comprehensive range of third-party applications: to ensure proper inter-working, Alcatel-Lucent tests and verifies selected third-party applications that complement its portfolio. Successful candidates, which are labelled Alcatel-Lucent Compliant 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.
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 http://applicationpartner.alcatel-lucent.com
11.2 Alcatel-Lucent.com You can access the Alcatel-Lucent website at this URL: http://www.Alcatel-Lucent.com/
The purpose of this appendix is to define the escalation process to be applied by the Alcatel-Lucent Business Partners when facing a problem with the solution certified in this document. The principle is that Alcatel-Lucent 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, Alcatel-Lucent and the Application Partner, are engaged as following:
(*) The Application Partner Business Partner can be a Third-Party company or the Alcatel-Lucent