alcatel applications partner program inter-working … makes no representations, warranties or...

Alcatel Applications Partner Program

Inter-Working Report

Partner: SLIT

Application type: OHL

Application name: Novacom

The product and version listed have been tested with the Alcatel Communication Server and the version specified hereinafter. The tests concern only the inter-working between the Application Partner product and the Alcatel Communication platforms. The inter-working report is valid until the Application Partner issues a new version of such product (incorporating new features or functionality), or until Alcatel issues a new version of such Alcatel product (incorporating new features or functionality), whichever first occurs. ALCATEL MAKES NO REPRESENTATIONS, WARRANTIES OR CONDITIONS WITH RESPECT TO THE APPLICATION PARTNER PRODUCT. WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, ALCATEL HEREBY EXPRESSLY DISCLAIMS ANY AND ALL REPRESENTATIONS, WARRANTIES OR CONDITIONS OF ANY NATURE WHATSOEVER AS TO THE APPLICATION PARTNER PRODUCT INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF MERCHANTABILITY, NON INFRINGEMENT OR FITNESS FOR A PARTICULAR PURPOSE AND ALCATEL FURTHER SHALL HAVE NO LIABILITY TO APPLICATION PARTNER OR ANY OTHER PARTY ARISING FROM OR RELATED IN ANY MANNER TO THIS CERTIFICATE.

Alcatel Applications Partner Program – Inter-working report Copyright © 2003 Alcatel, All rights reserved

Edition 1 –

Tests identification

Date of the tests 27-28 July 2004

Alcatel’s representative Veritest - Arnaud ANGUELU

Partner’s representative Mr François LARDY

Alcatel Communication Platform (OmniPCX 4400/Enterprise, OmniTouch, OmniPCX Office, ...)

OmniPCX Office, OHL Driver V1.5.1.0

Alcatel compatibility release R300 / 019.001

Partner’s application version 3.1

Environment (if it has a sense)

Author(s): Arnaud Anguelu Reviewer(s): xxx

Historic Edition 1: creation of the document – 09-06-2004 Edition 2: update of the document - mm-dd-yyyy (add the reason of the update)

Test results

Passed

Refused Postponed

Passed with restrictions

Refer to the section 4 for a summary of the test results.

ACD Business


Edition 1 –

Company Contact Information (Information provided by the partner)

Contact name: Mr François LARDY

Title: Technical Director

Address 1: 36 bd des Canuts

Address 2:

City: Lyon

State:

Zip: 69317

Country: FRANCE

Country code: 33

Phone: +33.(0)4.72.10.16.48

Fax: +33.(0)4.78.27.97.34

Web address: http://www.slit.fr

E-mail: [email protected]


Edition 1 –

TABLE OF CONTENTS

1 INTRODUCTION............................................................................................................................................ 7

2 APPLICATION INFORMATION................................................................................................................... 8

3 TESTS ENVIRONMENT ............................................................................................................................. 13

3.1 GENERAL ARCHITECTURE ........................................................................................................................ 13 3.2 HARDWARE CONFIGURATION ................................................................................................................... 14 3.3 SOFTWARE CONFIGURATION .................................................................................................................... 14 3.4 OMNIPCX OFFICE PARAMETERS CONFIGURATION ................................................................................... 14

4 SUMMARY OF TEST RESULTS .............................................................................................................. 15

4.1 SUMMARY OF MAIN FUNCTIONS SUPPORTED ............................................................................................ 15 4.2 SUMMARY OF PROBLEMS ......................................................................................................................... 15 4.3 SUMMARY OF LIMITATIONS ...................................................................................................................... 15 4.4 NOTES, REMARKS .................................................................................................................................... 15

5 TEST SCENARIOS...................................................................................................................................... 17

5.1 TEST PROCEDURE .................................................................................................................................... 17 5.2 RESULT TEMPLATE................................................................................................................................... 17

6 CONNECTIVITY AND SETUP................................................................................................................... 18

6.1 TEST OBJECTIVES..................................................................................................................................... 18 6.2 TEST PROCEDURE .................................................................................................................................... 18

7 PBX <---> PMS CHECK-IN FROM PMS GUEST ROOM NUMBER ALLOCATION BY PMS....... 19


8 PBX <---> PMS MODIFICATION OF GUEST CONFIGURATION..................................................... 21


9 PBX <---> PMS ROOM STATUS CHANGE............................................................................................. 22


10 PBX <---> PMS WAKE- UP EVENTS ................................................................................................... 23


11 PBX <---> HOTEL APPLICATION MANAGEMENT OF CALL TICKETS: STATION MESSAGE

DETAIL RECORDING. ...................................................................................................................................... 24


12 PBX <---> HOTEL APPLICATION INTERROGATION MANAGEMENT FOLLOWED BY PBX

<--->HOTEL APPLICATION GUEST TELEPHONE ACCOUNT. ............................................................... 25

12.1 TEST OBJECTIVES..................................................................................................................................... 25 12.2 TEST PROCEDURE .....................................................................................................................................25


Edition 1 –

13 PBX <---> HOTEL APPLICATION CHECK OUT GUEST................................................................ 26


14 PBX <---> HOTEL APPLICATION = INIT REQUEST PBX <---> HOTEL APPLICATION =

REINIT .................................................................................................................................................................. 27


15 DISRUPTION OF AHL LINK ................................................................................................................ 28


APPENDIX A : APPLICATION DESCRIPTION, INSTALLATION AND USE.......................................... 30

APPENDIX B: ALCATEL COMMUNICATION PLATFORM: CONFIGURATION REQUIREMENTS45

APPENDIX C: AAPP PROGRAM, DOCUMENTATION AND TECHNICAL ASSISTANCE .................. 47


Edition 1 –


Edition 1 –

1 Introduction

The goal of these tests is to qualify an external application as an Alcatel Applications Partner Program

solution for the Alcatel Communication Platform. The scope of the tests is the interoperability of the application with the Alcatel Communication Platform. It covers a basic or complex inter-working to ensure that services requested by the application and provided by the Communication Platform (and/or conversely) are properly completed. These tests do not verify the functional achievement of the application as well as they do not cover load capacity checks, race conditions and generally speaking any real customer's site conditions.

• Check-in with several conditions (busy room, unavailable DDI, invalid guest room…)

• Check-out with several conditions (room not checked-in, invalid guest room…)

• Assign / Modify DDI

• Assign / Modify cash deposit

• Modify Guest Name

• Call tickets management in different situations: - outgoing call from guest room - outgoing call from booth and charged to guest room - outgoing not charged call - outgoing call transferred to guest room - incoming call

• Behaviour in case of link disruptions (LAN, V24)

• Behaviour in case of OHL Driver unavailability


Edition 1 –

2 Application information

Application type: Hospitality/Healthcare

Application commercial name: Novacom

Application version: 3.1

Interface type: OHL Driver

Interface version (if relevant): 1.5.1.0

Operating Systems: MS Windows 9x, Me, NT4, 2000, 2003, XP.

Product Languages: French

Documentation Languages: French


Edition 1 –

Application description:

Novacom is a full 32 bits Windows application designed with two complementary arrays of competence :

• Recording and reporting of data, with a virtually unlimited number of call data records storage.

• Managing hospitals and clinics guests telephony services. In more detail: Process metering output (display, archive, statistics, billing) - Billing, Accounting : collecting call charge ticket via OHL - Guest management and billing : OHL interface

Manages a directory (no interface with the PBX) Manages application alarms

Office

Basic outgoing call

Basic incoming call

Hold/Retrieve

Consultation call

Transfer

Conference/Cancel

Voice logger

Trunk side recording

Extension side recording

Free seating

Selective recording

Total recording

CCD calls

Business calls

IVR

Call presentation Based on:

DNIS

ANI

Correlator Data

Make call

Answer

Consultation

Transfer

Reconnect

Clear

Conference

Blind transfer Target:

Device

CCD pilot


Edition 1 –

Supervised transfer Target:

Device

CCD pilot

Correlator Data

ACD agent desktop

Logging on/off

Ready/not ready

Wrap-up

Free seating

Call presentation Based on

DNIS

ANI

Correlator Data

Make call

Consultation

Hold/Retrieve

Transfer

Conference/Cancel

Voice &data transfer

Range

Local

Network

Outbound campaign manager

Preview dialing Call type

CCD

Business

Progressive dialing Call type

CCD

Business

Predictive dialing Distribution method

CCD agent

CCD pilot

Business set

Call classification Capabilities

No answer

Busy

Answering

Fax/modem

ERP/CRM

Agent control Features

Logging on/off ��

Ready/not ready

Wrap-up

Free seating

Call presentation Based on

DNIS

ANI

Correlator Data


Edition 1 –

Data

Call control Features

Make call

Consultation

Hold/Retrieve

Transfer

Conference/Cancel

Voice &data transfer

Range

Local

Network

Hospitality / Healthcare

Check-in ��(set only)

Check-out ��(set only)

Phone allocation ��(set only)

Modification (Name-Password-Barring cat., deposit, wakeup time etc…)

Partial

Interrogation

Reinitialization request


Edition 1 –

Figure 1 Global architecture

Client machines

CTI/Application

Server

LAN

Alcatel Communication

Platform

PSTN

OHL Driver

Server

V24 link

Novacom server interacts with the OmniPCX Office via the OHL Driver API. Both OHL Driver and Novacom server can be installed on the same machine, or they can be on separate computers, as shown in the picture here above. It is not mandatory to run a Server operating system for these components, but it is recommended for Novacom Server.


Edition 1 –

3 Tests environment

3.1 General architecture The tests are performed on the Alcatel TSS Applications International platform in the following environment:

Figure 2 Tests environment

Alcatel Communication

Platform Client machine

not used

Application Server OHL Driver

Application GUI

LAN

PSTN

server

V24 link

Alcatel Communication Platform:

• name: Veritest2

• IP address: 192.168.92.236

CTI/Application server – Win 2000 Server

• name: W2KSalcatel2

• domain: WORKGROUP

• IP address: 192.168.92.3

Client application platform – Win 2000 Prof. NOT USED

• name: W2Kalcatel1

• domain: WORKGROUP

• IP address: 192.168.92.2


Edition 1 –

3.2 Hardware configuration

• Alcatel Communication Platform: Omni PCX Office - ISDN T0 interface, UA and Z interfaces, digital and analogues sets, DECT sets.

• Server application: Dell Dimension L733r / Celeron 733 MHz - 128MB RAM

• Client Platform (not used): Dell Dimension L733r / Celeron 733 MHz - 128MB RAM

• Information from SLIT – Server station

CPU: Pentium III 500 MHz RAM: 128 Mo HD Space: 500 Mo available Resolution: 800x600 256 clrs Other communication devices: Specific Hardware required:

3.3 Software configuration

OmniPCX Office: R3.0, software release version 19.001

- MultiReflex version 100/001.004

- 4093 ASM : SW version 3.01

- PM5 : PMI 300/16.1

Application platform (W2KALCATEL): PC station

- Windows 2000 SP4

- Last Microsoft updates

3.4 OmniPCX Office parameters configuration

• Initialize as Hotel application

• Connection controller: V24 interface (4093ASM) on Reflex set

• Metering parameters: activate "External metering activation"

• For the output of the call data records, all the Printed fields of proof marked “M” must be selected:

M - Charged User O - Dialing Mode

M - Communication Type O - Ringing Duration

M - Trunk Number M - Cost in the local currency

M - Date (only for checking that it is a valid CDR) O - Account Code

M - Time O - Carrier

M - Duration M - Initial User

M - Amount of Taxes O - Node

M - Services O - User8

M - Facilities O - Trunk4

M - Dialed Number O - Subscriber Name

See details Appendix AB


Edition 1 –

4 Summary of test results

4.1 Summary of main functions supported

Hospitality / Healthcare

Check-in Pass (set only)

Check-out Pass (set only)

Phone allocation Pass (set only)

Modification (Name-Password-Barring cat., deposit, wakeup time etc…)

Partially supported

Wake-Up events Not supported

Interrogation Not supported

Reinitialization request Not supported

CDR – Outgoing call from guest room Pass

CDR – Outgoing call from booth Not supported

CDR – Outgoing transferred call Pass (1)

CDR – Outgoing not charged calls Pass

(1) Parsed as expected except if target extension is redirected to Voice Mail

4.2 Summary of problems None

4.3 Summary of limitations

• A CDR corresponding to a call passed from a booth and charged to a guest room is not taken in account by the application. Usage of booth is rare in hospitals, so not supported by the application.

• OmniPCX Office charges a Hunting Group Extension instead of the target guest room when a charged call is transferred to this guest room and while the phone is transferred to the voice mail. As a consequence, the target room is not charged.

• Last call is not charged if it was in progress while the operator performed the checkout.

• All operations performed manually from the operator phone set, such as check-in, check-out, deposit modification… are not taken in account by the application (the application ignores all unsolicited messages sent by OHL Driver) By design, all operations must be executed from the application interface, except Wake-up programming (Novacom does not support wake-up management). So, as the Novacom can not send a full or partial reinitialisation request, the ' Hotel Key' on the OmniPCX operator set should be deleted to prevent database synchronisation lose between the OmniPCX and the application.

4.4 Notes, remarks

• Because OmniPCX Office does not accept decimal values for currency (only accepts whole numbers), only the integer part of the amount that is sent by the application is taken in account (for example, 1.99 EUR will be recorded as 1 EUR). The application user has to know.


Edition 1 –


Edition 1 –

5 Test Scenarios

5.1 Test procedure

Step Action N/A Result Origin of the problem Comment

Step: a test may comprise multiple steps depending on its complexity. Each step has to be completed successfully in order to conform to the test. Step 0 when present represents the initial state for all the following steps.

Action: describes which action to realize in order to set-up the conditions of the test.

N/A: the step within this test is not applicable to this application. This has to be filled in only if the test is checked as mandatory in the applicability box. In that case, the column comment must indicate the reason of the non-applicability (e.g.: service not supported).

Result: describes the result of the test from an external point of view. If it is positive, it describes which application's trigger was checked. If it is negative, it describes as precisely as possible the problem.

Origin of the problem: this column has to be filled in when a problem occurs during the test. It must contain a high level evaluation of the localization of the responsibility: Alcatel or the Partner.

Note: it is not intended during this test session to debug and fix problems.

5.2 Result template The results table must be formatted as indicated in the example below:

Step Action N/A Result Origin of the

problem

Comment

1 action 1 OK

2 action 2

OK

The application waits for PBX timer or phone set hangs up

3 action 3 OK

4 action 4 X

Relevant only if the CTI interface is a direct CSTA link

5 action 5 NOK

No indication, no error message

… …


Edition 1 –

6 Connectivity and setup

6.1 Test objectives These tests shall verify that the different components are properly connected and can communicate together (the external application and the Alcatel Communication Platform are connected and the interface link is operational).

6.2 Test procedure

Step Action N/A Result Origin of the

problem

Comment

1 OHL Driver Configuration OK

2 Gardien NovaCS - Eclateur OK Shows all traffic to OHL driver

3 Gardien NovaCS - DHM OK Shows DHM

4 Gardien NovaCS - FILO OK Shows CDRs

5 NovaObs OK

Shows all events related to modules


Edition 1 –

7 PBX <---> PMS CHECK-IN from PMS Guest Room Number allocation by PMS

7.1 Test objectives These tests shall verify that the check-in is performed as expected depending on the status of rooms and information to setup

7.2 Test procedure

Step Action Impl. Reply Result, Origin of

the problem

Comment

CIC101 Generate a check-in for a valid guest room extension number with guest name

Request D, A Pass

(1)

Answer I

CIC102 Generate a check-in for an invalid guest room extension number

Request D, A Pass

Performs 3 attempts (1)

Answer PG JG BG

CIC103 Generate a check-in with an already checked-in room extension number

Request D, A Pass

(1)

Answer I

CIC104 Generate a check-in with language parameter

Request D, A Pass

(1)

Answer I

CIC105 Generate a check-in with an wrong value in the language field

Request N/A

Answer

CIC106 Generate a check-in with wake-up call time

Request N/A

Answer

CIC107 Generate a check-in with wrong wake-up call time ( eg. 99:99 )

Request N/A

Answer

CIC108 Generate a check-in with Dialling Restrictions ( ie:- Barring )

Request D, A Pass

(1)

Answer I

CIC109 Generate a check-in with a Deposit Request D, A Pass (1)

Answer I

(1) The application systematically performs a check-out prior to performing a check-in, so it prevents troubles with rooms managed outside of this application.


Edition 1 –

Step Action Impl. Reply Result, Origin of

the problem

Comment

CIC110 Generate a check-in with a bad Deposit value ( eg. - 10.00 )

Request N/A

The GUI prevents wrong characters

Answer

CIC111 Generate a check-in and enable DND Request N/S

Answer

CIC112 Generate a check-in with password Request N/S Only wit AHL

Answer

CIC113 Auto Allocate a DDI ( Direct Dial Inwards ) number to a checked -in GUEST ROOM

Request Pass

Answer

CIC114 Auto Allocate a DDI ( Direct Dial Inwards ) number to a checked -in GUEST ROOM when there are no free DDI numbers available

Request

Pass

Answer

CIC115 Generate a check-in with bad language parameter

Request N/A

Not possible App prevents

Answer

CIC116 Generate a check-in with bad DND parameter

Request N/A

Not possible App prevents

Answer

CIC117 Generate a check-in with room extension forwarded to voicemail

Request N/S

Answer

CIC118 Generate a check-in with bad Password parameter ( eg. illegal characters )

Request

Password is not modifiable

Answer

CIC119 Generate a check-in for a room set which is out of service ( check-in should still work ! )

Request D, A

Performs 3 attempts

Answer PG IG RG

Result CHECK-IN from PMS with GUEST NUMBER allocation by PMS

Pass


Edition 1 –

8 PBX <---> PMS MODIFICATION of GUEST configuration

8.1 Test objectives

Check the ability of the application to change GUEST configuration data

8.2 Test procedure Step Action Impl. Reply Result, Origin of

the problem

Comment

MOC

101

Modification of GUEST with new password

Request N/A

Answer

MOC

102

Modification with deposit Request M Pass App performs a new check-in

Answer M

MOC

103

Modification of language parameter Request N/S

Answer

MOC

104

Modification on Dialling Restrictions(ie:- Guest room outward dialling Barring)

Request Another method is used

See note (2)

Answer

MOC

105

Modification of the name Request M Pass App performs a new check-in

Answer M

MOC

106

Modification of the Wake up Request N/S

Answer

MOC

107

Modification of DND state

Request N/S

Answer

MOC

108

Modification of DDI number ( eg. Allocate a new DDI to a room

Request H/R Pass See note (3)

Answer D

Result MODIFICATION of GUEST

configuration

Pass

(2) Done when performing a deposit at check-in or later, and depends on the DEPOSIT LEVEL parameter value of the application.

(3) This is the full sequence (App do not provide an explicit DDI)

�� H <Room> R H <Room> D

H <Room> <Passwd> A

�� H <Room> R H <Room> D <DDI1> H <Room> <Passwd> A

�� H <Room> R H <Room> D <DDI2> H <Room> <Passwd> A

In fact the command H…R is repeated until the application receives the expected DDI.


Edition 1 –

9 PBX <---> PMS ROOM STATUS change

9.1 Test objectives

Check the ability of the application to change the room status


the problem

Comment

STAT

101

Room status change message with maid room problem identification code from a room phone

N/S

STAT

102

Room status change message without maid problem identification code from a room phone

N/S

STAT

103

Room status change message with maid 'Clean' Status and 'no problem' code from a room phone

N/S

STAT

104

Room status change message with maid room ' Unclean' and ' problem' identification code from a room phone

N/S

STAT

105

Room status message with different problem (re- Initialization message )and status codes sent to the PMS from the PBX:eg: Maid arrives in the room, room has be cleaned for a new guest or the same guest

Request

N/S

Answer

Result ROOM STATUS change N/S


Edition 1 –

10 PBX <---> PMS WAKE- UP events

10.1 Test objectives

Check the ability of the application to manage wake-up events


the problem

Comment

WUP

101

Wake-up message with normal answer N/S

WUP

102

Wake-up message with no answer N/S

WUP

103

Wake-up message with busy line N/S

WUP

104

Wake-up message with out of order line N/S

WUP

105

Wake-up cancellation message N/S

WUP

106

Wake-up message generated by programming

N/S

WUP

107

Wake-up message generated by modification

Request N/S

Answer N/S

WUP

108

Wake-up cancellation generated by modification message.

Request N/S

Answer

Result WAKE- UP events N/S


Edition 1 –

11 PBX <---> Hotel Application Management of CALL TICKETS: Station Message Detail Recording.


Check the ability of the application to manage call tickets


the problem

Comment

CAT

101

SMDR message of a charged outgoing call with pulses or cost. Call done on room extension .

Pass

Calculates cost from duration

CAT

102

SMDR message of a charged outgoing call with pulses or cost.Call done on booth extension

N/S

CAT

104

SMDR message of a transfered outgoing call from GUEST to GUEST with pulses or cost

Pass

CAT

105

SMDR message of a transfered outgoing call from an ADMIN extension to a GUEST with pulses or cost

Pass

CAT

106

SMDR message of a non charged outgoing call ( Free call destination eg. 0800 )

Pass

CAT

107

SMDR message of an incoming call . Pass

Not charged as expected

CAT

108

SMDR message of a transfered incoming call .

Pass

Not parsed

CAT

109

SMDR message of a transfered outgoing call from ROOM1 to ROOM2 which is forwarded on mail box. .

N/S

PCX Office charges a hunting group

CAT

110

SMDR message of a charged outgoing call with pulses or cost. Call done on booth phone using MTR and the charge assigned to a guest room

N/S

Application limitation (3)

Result Management of CALL TICKETS:

Station Message Detail Recording.

Pass

(4) The OHL driver logs this sequence, and the application should take all of them in account:

<STX>J 100 0 1009041209 00000.00 3699 76<ETX>

<STX>J 109 1 1009041209 00130.00 3699 7C<ETX>

<STX>J 101 15 1009041209 00130.00 64<ETX>


Edition 1 –

12 PBX <---> Hotel Application Interrogation management followed by PBX <--->Hotel Application Guest Telephone Account.


Check the ability of the application to get information from PBX using the Interrogation command


the problem

Comment

INT101 Asks for the Guest room extension telephone accounts.

Request N/S

Answer

INT102 Asks for the Guest room extension telephone accounts using a Guest room number which is out of the range .

Request N/S

Answer

INT103 Asks for the Guest room extension telephone accounts using a Guest room number which is not checked in.

Request N/S

Answer

INT104 Asks for the Guest room extension telephone accounts Verify the management of Cost, Total Deposit and Guest balance.

N/S

Result INTERROGATION management

followed by

Guest Telephone Account.

N/S


Edition 1 –

13 PBX <---> Hotel Application CHECK OUT Guest


These tests shall verify that the check-out performed as expected depending on the status of rooms.


the problem

Comment

COC

101

Check Out of a guest room number Request Pass

Answer O

COC

102

Check Out of a guest which room line is busy ..

Request N/S

Answer

COC

103

Check Out of a guest with not consulted messages in the associated voice mail box .

Request Pass

Answer RO

COC

104

Check Out of an invalid guest room number

Request Pass

Answer PG

COC

105

Check Out of a none checked in guest room number

Request Pass

Answer PR

COC

106

Verify metering bills by checking out a guest number;

Pass

COC

107

Verify metering bills by checking out a guest number which was transfered from one room to another room and called from each of them.

Pass

COC

108

Verify metering bills by checking out a guest number which called from a booth extension (ie. MTR call assignment to a room by the operator )

N/S

COC

109

Check Out of a GUEST if the V24 link is broken between OmniPCX and PC..

N/S

Result CHECK OUT GUEST NUMBER Pass


Edition 1 –

14 PBX <---> Hotel Application = INIT REQUEST PBX <---> Hotel Application = REINIT


These tests shall verify that the Initialization requests are performed as required.


the problem

Comment

REI101 Generate a reinit request for a specific GUEST room number - Full guest reinit.

Request N/S

Answer

REI102 Generate a reinit request for a specific GUEST room number - Partial guest reinit.

Request N/S

Answer

REI103 Generate a reinit request for a GUEST room number out of range

Request N/S

Answer

REI104 Generate a reinit request for a specific GUEST room number not checked in.

Request N/S

Answer

REI105 Generate a reinit request for all GUESTS checked-in..: - Full guest reinit.

Request N/S

Answer

REI106 Generate a reinit request for all GUESTS checked-in..: - Partial guest reinit.

Request N/S

Answer

Result REINIT REQUEST REINIT N/S


Edition 1 –

15 Disruption of AHL Link


These tests shall verify that the application does not hang or loose data in case of link disruptions..


the problem

Comment

DIS101 Cut the V24 link between PMS interface and the OmniPCX Office. Generate some events like wake-up and call-tickets on OmniPCX Office side. Establish the link and verify that the on PMS events are taken in consideration side

Pass

DIS102 Cut the ethernet link between PMS interface and the OmniPCX Office: Generate some events like check-in, Phone allocations from the PMS . Establish the link and verify that the events are sent to the OmniPCX.

Pass

DIS103 Cut the V24 link between PMS interface and the OmniPCX: Generate some events like wake-up and call-tickets on OmniPCX side until the buffer is full. Establish the link and verify that the events are taken in consideration on PMS side

N/T

DIS104 Power off the PMS interface and generate some events from the OmniPCX Office side. Restart the interface and verify that the events are sent and taken in consideration on the PMS side

Pass

DIS105 If the PMS is composed with several devices, the same tests have to be done by powering off and restarting separately the different devices.

Pass

DIS106 Generate an XOFF on the OmniPCX Office . Generate some events on PMS. Send an XON on the OmniPCX Office side.

N/T

DIS107 Establish a PM5 application session to the OmniPCX and attempt a connection with PMS whilst the PM5 session is active to verify the keep alive protocol timeout.

Pass

Result DISRUPTION OF AHL LINK Pass


Edition 1 –


Edition 1 –

Appendix A : Application description, Installation and Use

• Brief Description:

Novacom is a full 32 bits Windows application designed with two complementary arrays of competence :

• Recording and reporting of data, with a virtually unlimited number of call data records storage.

• Managing hospitals and clinics guests telephony services.

• General Architecture:

• Specific Details:

The NovaCom application is not based on a maximum number of possibly recorded calls, but on a period (in days) for which every call will be recorded. The maximum of days is fixed to 999. The physical maximum number recordable is only limited by the disk capacity, and the operating system limits.

The application directory manages both the subscribers of the site and their extensions. One or several extensions can be associated to one or several subscribers, and each entity is located into a hierarchy.

The included directory allows for 10 levels of hierarchy. Each subscribers is placed in a fonctional hierarchy and a geographical one. Each extension is placed in a technical hierarchy.

The application will, based on this directory and de Call Data records, be able to generate reports. These reports can be printed, exported to various data formats, or drawn using different chart methods. These reports can be generated interactively from the interface, or automatically according to a schedule.

The guest management interface relies on the same database and directory data for the management of an hospital or clinic. It will be able to follow the lifecycle of the guest inside the site (arrival, placements into rooms, departure), and generate the appropriate orders to be sent to the PBX. Upon departure, or within the stay of the guest, it can generate bills or other written documents.

Apart from the telephone services, the guest interface can also manage an external television server, or provide possilities to insert into the same bill other services like room arrangements for families, food or beverage orders,... that can be offered by the site.

The guest management interface can also be linked with several external hospital software, in order to receive directly from them informations on arrival, movement or departure of guests.

PC Network

Alcatel

OMNI PCX Office

OHL Link

NovaCom

Server

Figure 1: General Architecture


Edition 1 –

• Communication modules:

- Eclateur: it interfaces OHL Driver and separates data for processing by the two other modules

- FILO (Fil de l’eau) that processes tickets information

- DHM that processes Hospitality traffic (check-in etc…)

Alcatel

OHL Driver

V24

Eth

NovaCS

DHM

API

NovaCS

Eclateur

NovaCS

FILO

NovaCom Hospital GUI

NovaCS

monitoring

GUI


Edition 1 –

• Application setup – General information, link configuration

After installing the application, there are 3 tools to define the main server parameters. They are accessible from a launcher accessible from a Desktop shortcut or from the Start menu. The name of the launcher is “Server Taxation / Lanceur”

- NovaAnnu is for defining hospital organization in terms of telephony such as phonesets that will be used by guests.

- NovaHop is the User Interface

- NovaObs is for alarms and high level monitoring

Choose “NovaConf “ to define the lowest level parameters: link, protocol…

Then click on PABX and add one:

Here the Add option is not proposed because there is one PBX already defined. Its name is PABX1. Looking to the details by clicking Modifier:


Edition 1 –

In this screen there are two areas:

- Fil de l’eau: to configure CDR interface

- DHM : to configure hospitality interface

Clicking on “Liaison” provides access to link and protocol details.


Edition 1 –

Here after, the configuration screen for both DHM and FILO interfaces:


Edition 1 –

Still from NovaConf, click on Hôpital to define hospital specific parameters.

On the following screen we have the option to wait for PBX commands to be processed before going further. These are the parameters “DHM avec attente” or “DHM sans attente”. ”Compte téléphonique” must be checked as well to authorize telephone usage.

Still from NovaConf, you can click on:

- Paramètres généraux to setup currencies, telephone rates, password management

- Utilisateurs / Profils to define accounts and permissions to manage and / or use NovaCom

Other options (Annuaire and Historiques/Journaux are less important to get started)


Edition 1 –

• Application setup – Tax configuration

From the Lanceur, click on NovaHTax.

Here are the options :


Edition 1 –

• Application setup – Hospital organization configuration

Next step will be the configuration of information such as phonesets used in bedrooms. To launch the corresponding tool, from the Lanceur, choose Annuaire

Then first task is to create phonesets installed in bedrooms.

From the “Annuaire interne”, then “Hiérarchie technique” tabs, click “Créer”.

Fill the fields “Poste” and “au poste” to specify the range of phonesets that are used in bedrooms, for example 101 to 125.


Edition 1 –

After creation, this is the detail we can see for an extension:

There is an associated item (bed) that does not appear before the next step has been performed: associate beds to extensions. To perform this association, launch the Hospital User and Administrator GUI. From the Lanceur, click on NovaHop Then switch to the “Lits” tab:


Edition 1 –

Click on “Créer”. Fill the Intitulé field to provide a name to the bed and click on the Poste field, browser button, to associate a previously defined phoneset. Values are “Lit 102” and “102” in the following screenshot.

• Application usage – Admit a patient

Previous step, from Lanceur we launched this interface: NovaHop.

Switch to the “Patients présents” tab.


Edition 1 –

For a patient that was never recorded in the hospital, click on “Arrivée”. Otherwise open the “Patients absents” tab, select the one to readmit, and click “Ré-entrer”. On the window that opens, type a First Name, Last Name, birthday date then click “Arrivée”. On the same screen, select a bed then click “Modifier”. Here are the details of an admitted patient:


Edition 1 –

Next step consists in opening the phone line. From the previous screen switch to the “Comptes” tab. Click on the icon (red cross) next to the Téléphone label. Type a value in Euros (Integer) in the “Versement” field. Choose DDI allocation mode: “SDA manu” or” SDA auto”. A browse button allows to choose the DDI.

Then click on Valider. As soon as the operation is done on the PBX (status column “Etat PBX” of the “Patients presents” tab shows “Ok), the patient can use the telephone. A check-in was just performed.

• Application usage – Check-out

From the “Patients presents” tab, choose the patient that you want to check-out and click “Départ”. A window opens, click Départ again.

Several forms are created and displayed (bills and phone details), close them.

• Application usage – Check patient consumption, troubleshoot

To check a patient telephone call status, select him on the “Patients presents” list, double click on its name, then in the window that opens

- go to the “Comptes” tab

- click “Facturer”. A new window opens.

- Go to the “Détail des appels” tab.

To check that all operations are accomplished on the PBX:

- look at the status shown in the “Etat PBX” column of the “Patients présents” tab. If it is


Edition 1 –

different from “Ok”, and does not change, some operations are stopped. First, check that a phone line was opened by editing the patient profile, going to the Comptes tab, and clicking on the Telephone icon if it is displayed as a red cross. In this case, this is the reason why “Operation en cours” was permanently displayed. Nothing is sent to the OHL driver until a phone line is opened. For other symptoms, check that all modules are operational (OHL driver, Eclateur, and PBX. See next paragraph), then select the line(s) which status is not “Ok”, and from the Maintenance menu, click “Mise à jour PBX”. The application will retry the failing commands.

If a call cannot be initiated from a patient room, use the operator phoneset then:

- press the Hotel feature key

- type the room number

- check that the deposit cash is not null, that a DDI number is allocated and that there is no barring limitation.

• Server maintenance and troubleshooting

To view the three application modules status, double click on the green/red square ( ) of the taskbar

The “Gardien NovaCS” window opens.

.

- right click on a line allows to start/stop/display the corresponding Windows NT service

- double click on a line opens a window with details on communication traffic

Here are some examples.


Edition 1 –


Edition 1 –

Another interesting tool is the Event Observer that can be launched from the Lanceur by choosing NovaObs.


Edition 1 –

Appendix B: Alcatel Communication Platform: configuration requirements

IMPORTANT: The OmniPCX Office must be in " Hotel " mode before beginning the tests. Do this configuration before any other as your PBX requires to be COLD reset (Note: The Cold reset will also delete all previous programming/configuration). Cold reset the OmniPCX using a Reflexes set via installer session (ie:- Reception set) after the system restarts select Hotel mode in the wizard session which appears on the Reflexe set . The OmniPCX will at the end of the wizard session request to perform a Warm reset. Proceed with the Warm reset after which Hotel mode is implemented . Note : During the wizard session also select the system default language and Voice mails for all sets .

OmniPCX Office settings : Due to the analysis of the frames coming from the OmniPCX V24 Metering interface which generate OHL Messages, the OmniPCX Office must be configured using the PM5 configuration software as follows:-

• Hotel Parameters : - The “Print Check-In/Check-Out Ticket” check box must be checked.

Metering :

• Metering Printout sheet :

- The “External Metering Activation” check box should be checked. - Check boxes “Appointment printout” for ”Activation, Cancellation, Failed, Complete” - Type of printout : “Listing” - Language : “English” - Head printout : “No header” - The “Form feed” check box must be deactivated

• Metering Transmission Characteristics : - Character : “8” / Parity : "None" / Stop bits : "1" / Baud rate : "9600"

• Metering: Printed Fields of Proof :

- The following check boxes must be checked : Charged User

Communication Type Trunk Number Date Time Duration Amount of Taxes Services Facilities Dialled Number Cost Initial user

Note : The fields indicated above are mandatory and therefore must be selected, more fields may be selected if required.

• Hotel Metering for Active Currency :

- Check the “Print Room Status Ticket at any manual status change” - Check the “Cut if prepayment consumed” box. This is specific to this application. - Click “OK” to confirm your configuration

• Noteworthy Address : - Change in Debug label ' OpeMetEna ' to equal value 01


Edition 1 –


Edition 1 –

Appendix C: AAPP program, documentation and technical assistance

Alcatel Applications Partner Program (AAPP)

Complete e-business solutions at your disposal The Alcatel Applications Partner Program is designed to support companies that develop communication applications for the enterprise market, based on Alcatel's Omni product family. The program provides tools and support for developing, verifying and promoting compliant third-party applications that complement Alcatel's Omni-based products. Alcatel facilitates market access for compliant applications. The Alcatel Applications Partner Program (AAPP) has two main objectives:

• Provide easy interfacing for Alcatel communication products: Alcatel'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 products.

• Test and verify a comprehensive range of third-party applications: to ensure proper inter-working, Alcatel tests and verifies selected third-party applications that complement its portfolio. Successful candidates, which are labelled Alcatel Compliant Applications, come from every area of voice and data communications.

The Alcatel Applications Partner Program covers a wide array of third-party applications/products designed for voice-centric and data-centric networks in the enterprise market, including terminals, communication applications, mobility, management, security, …

Web site If registered Alcatel Application Partners, you can access the AAPP website at this URL: http://www.applicationspartner.alcatel.com/

Alcatel.com You can access the Alcatel website at this URL: http://www.alcatel.com/


Edition 1 –

Alcatel documentation

Alcatel Applications Partner Program (AAPP) If registered Alcatel Application Partners, you can access the current AAPP documentation at this URL: http://www.applicationspartner.alcatel.com/ and then click the Partner Center link.

Alcatel Business Partner Program (ABPP) The Alcatel Business Partner Program is designed to empower and maximize the business of the Partners. In addition, it enables them to help their customers successfully maximize their telecom investment through optimum deployment and proper configuration of Alcatel's solutions. Alcatel Partners also receive the added benefit of rapid, highly qualified service and support as well as world class training. Alcatel will work closely with Business Partners to provide top quality design, delivery, and support of the very best solutions for your customers. The Business Partner Program is designed around a flexible and scalable framework so each Partner can identify the exact support they need. So, depending on your specific requirements you can quickly become a 'Certified', 'Expert' or 'Premium' Business Partner with one of the world leaders in the communications industry. If registered Alcatel Business Partners, you can access to an exciting on-line resource centre with a wealth of information on all product lines at this URL: http://www.businesspartner.alcatel.com


Edition 1 –

Technical assistance In order to guide you in your purchasing decisions and provide you with assistance for updating our Communication Server and Networking Infrastructure products and for commercial development, Alcatel

has created the SUPPORT CENTER. The SUPPORT CENTER is responsible for the management and

routing of all your requests. It includes e-Support and a Contact Centre reserved for registered Alcatel Application Partners and Alcatel Business Partners.

The Contact Centre is open 24 hours a day; 7 days a week and is available in 5 languages. This Call Centre has a team of 15 people and handles 10; 000 requests per month.

• e-Support from the Alcatel Application Partners Web site (if registered Alcatel Application Partners): http://www.applicationspartner.alcatel.com/ click the Partner Center link and then Support

• e-Support from the Alcatel Business Partners Web site (if registered Alcatel Business Partners): http://www.businesspartner.alcatel.com click the e-Support link and then e-Service Request

• e-mail: [email protected]

• Fax number: +33 (0) 3 90 67 73 45

• Telephone numbers:

Alcatel Business Partners Contact Center: France : 0 811 900 110 French agent Austria : 0 810 810 012 German agent Denmark : 70 11 21 09 English agent Germany : 0 1 803 000 680 German agent Ireland : 1 890 925 039 English agent Italy : 848 800 389 Italian agent UK : 0 845 601 4101 English agent Spain : 901 120 085 Spanish agent Switzerland : 0 844 850 588 German agent For other countries: English answer : + 33 (0)3 88 55 69 04 French answer : + 33 (0)3 88 55 69 02


Edition 1 –

Alcatel training Technological innovative cycles are quickening and your customers are more and more demanding regarding the quality of services. In order to meet these requirements, you have to invest in skills: a key success factor for services. If registered Alcatel Business Partners, you can access to the training part at this URL: http://www.businesspartner.alcatel.com and then click the Training link.

Our vision of learning services is described in the Services Portfolio section. The Certification

section gives you some statistics and details on how training curricula are designed to match certification levels.

All updated training curricula and assessment tools are available in the Curricula & Catalogues

section.

The Schedule section is regularly updated to show forthcoming training sessions over the world.

The How to Enrol section provides you with the registration procedure and the Alcatel University Customer Service list of contacts world wide. Last but not least, find statistics and reports of what you think about our training services in the

Customer Satisfaction section.

The Alcatel commitment : enabling you to optimise your training investments.

alcatel applications partner program inter-working … makes no representations, warranties or...

Documents