Alliance & Application Partner Program Inter-Working Report

(1)

Alliance & Application Partner Program

Inter-Working Report

Partner: NewVoice

Application type: Alarm system

Application name: MobiCall

The product and version listed have been tested with the Alcatel-Lucent Communication Server and the version specified hereinafter. The tests concern only the inter-working between the Application Partner product and the Alcatel-Lucent Communication platforms. The inter-working report is valid until the Application Partner issues a new version of such product (incorporating new features or functionality), or until Alcatel-Lucent issues a new version of such Alcatel-Alcatel-Lucent product (incorporating new features or functionality), whichever first occurs.

ALCATEL-LUCENT MAKES NO REPRESENTATIONS, WARRANTIES OR CONDITIONS WITH RESPECT TO THE APPLICATION PARTNER PRODUCT. WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, ALCATEL-LUCENT HEREBY EXPRESSLY DISCLAIMS ANY AND ALL REPRESENTATIONS, WARRANTIES OR CONDITIONS OF ANY NATURE WHATSOEVER AS TO THE APPLICATION PARTNER PRODUCT INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF MERCHANTABILITY, NON INFRINGEMENT OR FITNESS FOR A PARTICULAR PURPOSE AND ALCATEL-LUCENT FURTHER SHALL HAVE NO LIABILITY TO APPLICATION PARTNER OR ANY OTHER PARTY ARISING FROM OR RELATED IN ANY MANNER TO THIS CERTIFICATE.

(2)

Tests identification

Date of the tests

3 december 2009

Date of regression tests

Alcatel-Lucent’s representative

Bruno Fouarge

Partner’s representative

David Fermet

Alcatel-Lucent Communication

Platform (OmniPCX

4400/Enterprise, OmniTouch,

OmniPCX Office, ...)

OXE - OmniPCX

Enterprise

Alcatel-Lucent compatibility release

R9.0 (H1.301.28)

R9.1 (I1.605.13)

Partner’s application version

7.2.1 Environment (if it has a sense)

Author(s): Bruno Fouarge

Reviewer(s): Denis Lienhart, Bernard Roth History:

1. Edition 1: Creation

Test results

Passed Refused Postponed

Passed with restrictions

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

(3)

Company Contact Information

Contact name: Georges Brigati

Title: Director Address 1: St. Gallerstrasse 8 Address 2: City: Lachen State: Zip: 8853 Country: Switzerland Country code: CH Phone: +41 41 743 14 77 Fax: +41 41 743 14 78

Web address: http://www.newvoiceinternational.com E-mail: [email protected]

(4)

1 Introduction

The goal of these tests is to qualify an external application as an Alliance & Application Partner Program solution for the Alcatel-Lucent Communication Platform.

The scope of the tests is the interoperability of the application with the Alcatel-Lucent Communication Platform. It covers a basic or complex inter-working to ensure that services requested by the application and provided by the Communication Platform (and/or conversely) are properly completed.

These tests do not verify the functional achievement of the application as well as they do not cover load capacity checks, race conditions and generally speaking any real customer's site conditions.

(7)

2 Application information

Application type: Alarm server Application commercial name: Mobicall Application version: V7.2

Interface type: QSIG-GF (T2 or T0) with ABC-F, Paging Interface version (if relevant):

Brief application description:

Mobicall is based on a modular and multi-lingual concept with a seamless integration into OmniPCX 4400/Enterprise and OmniPCX Office.

The server runs Mobicall Server, which purpose is to post alarms to groups or individuals. The alarm calls can be:

• manually launched,

• triggered on call reception,

• sent from a Web-based client.

The server is made of Mobicall services, a Web Apache server and a database (MySql). It could as well connect to any ODBC database.

(8)

3 Tests environment

3.1.1 General architecture

The tests are performed on the Alcatel-Lucent AAPP Etesting platform in the following environment:

3.1.2 Hardware configuration

• Alcatel-Lucent Communication Platform: 3 OmniPCX Enterprise, two in spatial redundancy (10.1.2.1/10.10.10.1), one node linked to the main using ABCF link 3.

Three PRA E1 board for the ABFC link between OmniPCX Main and Mobicall Main, for ABCF link between OmniPCX Standby and Mobicall Standby, for ABC-F link between OmniPCX Main and OmniPCX Remote Node.

• Terminals : DECT MR300/400 in GAP, GAP+, DECT 9D24, WIFI MR 610/310, SIP SEPLOS, IP TOUCH serie 8 and serie 9, IP TOUCH behind the second node.

OmniPCX Enterprise Remote node OmniPCX Enterprise Main 10.1.2.1 OmniPCX Enterprise StandBy 10.10.10.1 ABCF link 1 ABCF link 2 ABCF link 3 Mobicall main Mobicall standby IP/CSTA/Paging link SIP SEPLOS DECT GAP+ DECT GAP ASCOM 9D24 IP TOUCH serie8 serie 9 MR 610/310 IP TOUCH serie8 serie 9 On remote ABCF node

(9)

• Server application:

• Mobicall equipment and configuration

• Mobicall is a pc-based alarming system, which can be installed on any table or in a rack, protected against dust, vibrations and humidity

One 17” screen with keyboard and mouse placed in front of a chair is perfect

• Mobicall should be connected to an uninterrupted power supply with 6 plugs for pc, screen, modem or remote access, ip-boxes…

• Mobicall has one E1 trunk with Q.Sig GF protocol

• There is one RJ45 plug reserved for the E1 interface from Mobicall-Alarm server to the Alcatel-Lucent

Mobicall: 1+2 (RCV-Ring+ Tip) and 4+5 (XMIT_RING+Tip)

3.1.3 Software configuration

• Alcatel-Lucent Communication Platform: OXE R9.0 (H1.301.28) and R9.1(i1.6056.13), with WIFI (OmniAccess 4304), Dect base station IBS.

(10)

4 Summary of tests results

4.1 Voice based alarms notification on OmniPCXEnterprise

4.1.1 Summary of main functions supported

The Mobicalll supports :

• The sending of voice based alarm, with a message of 16 characters displayed in the ringing state, another message of 16 characters in the conversation state, and the sending of a mini message of 120 character after the conversation

• The sending of voice based alarm, with a message of 30 characters displayed in the ringing state, another message of 30 characters in the conversation state, and the sending of a mini message of 120 character after the conversation, on MIPT 310/610 phone only, and only in G1.301.30 or R9.1 (i1.602.4), and only in ABC-F link.

• The acknowledge of the alarm message in the conversation mode, using DTMF.

• The sending of mini messages of 120 characters only

• The activation of the loudspeaker to play an announcement message on.

• Ring cadence differentiation

• Intrusion

• UTF8 long text display ( not available on version R9.0, only in G1.301.29, and R9.1)

• Play voice messages on answer / confirm

• Voice conference calls for 2 party calls with recording

• Voice conference calls for multiple party

• DECT phone localization

• Numeric / analog phone localization (Not available in 1.43 version tested of Mobicall)

• The spatial redundancy of OmniPCX Enterprise CPU, and also the duplication of Mobicall, with two ABC-F trunk.

Three protocols support this type of alarms notification:

QSIG-GF / ABC-F on T2 or T0

Mobicall with OXE / QSIG-GF – ABC-F

Features Global status

M o b il e 3 0 0 /4 0 0 M IP T 3 1 0 /6 1 0 IP T o u c h A s c o m 9 D 2 4 M K 2 G A P S IP p h o n e s S T 2 0 2 2 /2 0 2 3 A S C O M i 7 5

Display alarms on ringing OK

Display alarms on pick up OK NA NA

Send a User to User information

with the call OK

NA NA NA

Send a User to User information

after answer (or confirm) OK

NA NA NA

Call back sender OK

Hand free on alarm reception OK NA NA NA

Ring cadence differentiation OK NA NA NA

(11)

Localization OK NOK NOK NOK NOK

Voice conference OK

Start alarm from phone OK

H323

Mobicall with OXE / H323

M o b il e 3 0 0 /4 0 0 M IP T 3 1 0 /6 1 0 IP T o u c h A s c o m 9 D 2 4 M K 2 G A P S IP p h o n e s S T 2 0 2 2 /S T 2 0 2 3 A S C O M i 7 5

Display alarms on pick up Not Applicable Send a User to User information Not Applicable Call back sender Not Applicable Hand free on alarm reception Not Applicable

Voice conference OK

Display a picture on ringing Not Applicable

SIP Trunk

Mobicall with OXE / SIP TRUNK

Display alarms on pick up Not Applicable Send a User to User information Not Applicable Call back sender Not Applicable Hand free on alarm reception Not Applicable

Voice conference OK

Display a picture on ringing Not Applicable

(12)

4.1.2 Summary of problems

On Mini message (User to User information) :

When the length of the User to User information is longer than 120 characters, the message is not sent. This limit depends on the whole message length which include the phone

number. Hence this limitation could be 120 to 124 characters, depending on the dial plan. On ring cadence differentiation:

• When the phone is forwarded (immediate or not), the call is lost, and is in status failed on Mobicall.

The MobiCall system has to be configured to ignore call forward.

On alarm with call announcement on loud speacker :

• When the called device is a Dect phone out of service, or out of coverage, the message is not play on the phone, but the Mobicall return a status Done.

This problem is referenced as SR 1-101961861.

4.1.3 Summary of limitations

Mobicall is not able to manage the case where the destination device is forwarded to another one.

4.1.4 Notes, remarks

(13)

4.2 Text based alarms notification on OmniPCXEnterprise

4.2.1 Summary of main functions supported

The Mobical supports:

The sending of normal alarm, with or without acknowledge, of urgent alarm with of without acknowledge, of discrete alarm with or without acknowledge. Each alarm is a text message of 128 characters maximum.

The specification of cadence ringing type in the alarm from 1 to 8 :

1 = xx_xx___ 2 = xxx_____ 3 = xxxxxxxxx 4 = x_x_x_x_x 5 = x__x__x__ 6 = xxx____ 7 = xxx____ 8 = xxx____ where x is the ringtone _ is a silence

The acknowledge of alarm

The OmniPCX Enterprise spatial redundancy Mobicall with OXE / Paging

Display alarms on ringing OK NA NA NA

Display alarms on pick up OK NA NA NA

Send a User to User information Not Applicable Call back sender Not Applicable Hand free on alarm reception Not Applicable Voice conference + recording Not Applicable Display a picture on ringing Not Applicable

4.2.2 Summary of problems

None

4.2.3 Summary of limitations

The Mobicall doesn’t support the delete of sent alarm.

4.2.4 Notes, remarks

(14)

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-Lucent or the Partner.

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 … …

(15)

6 Voice based alarms notification on

OmniPCXEnterprise

6.1 Using QSIG-GF/ ABC-F

The tests cover following scenarios:

Calls from Mobicall to OmniPCX Enterprise (OXE) phones

Display 16 digit name on phones while calling

Display 16 digit name on phones on answer

Send a User to User message with the call

Send a User to User message after the call is answered / confirmed

Hand free alarm reception

Ring cadence differentiation

Intrusion

UTF8 long text display ( not available on version R9.0 tested, only in G1.301.29, and R9.1)

Play voice messages on answer / confirm

Voice conference calls for 2 party calls with recording

Voice conference calls for multiple party

DECT phone localization

Numeric / analog phone localization (Not available in 1.43 version tested of Mobicall)

6.1.1 Text display on ringtone

6.1.1.1 Test Definition

MobiCall calls all phones of the list

All phones are respectively not forwarded, in immediate forward, in forward on busy and out

of service

A 16 character text display is configured

A voice prompt is played. Possible alarm confirmation by key 3

6.1.1.2 On not forwarded set

problem

Comment 1 From Alcatel-Lucent Mobile

300/400 OK 16 character displayed 2 On Alcatel-Lucent MIPT 310/610 OK 16 characters displayed 3 On Ascom 9d24 MK2 OK 16 characters displayed 4 On GAP handset OK 14 characters displayed only 5 On Alcatel-Lucent IP Touch OK 16 characters displayed 6 On SIP phones (Thomson 20x0)

OK 16 characters

displayed 7 On ASCOM I75

OK 16 characters

(16)

8 On Alcatel-Lucent IP Touch

attached to a distant OXE node OK

16 characters displayed

6.1.1.3 On forwarded set (immediate)

problem

300/400 OK 2 On Alcatel-Lucent MIPT 310/610 OK 3 On Ascom 9d24 MK2 OK 4 On GAP handset OK 14 characters displayed only 5 On Alcatel-Lucent IP Touch OK “Trunk name -> forwarded” displayed 6 On SIP phones (Thomson 20x0) OK

7 On ASCOM I75 OK

6.1.1.4 On forwarded set (on busy)

problem

300/400 OK * 2 On Alcatel-Lucent MIPT 310/610 OK * 3 On Ascom 9d24 MK2 OK * 4 On GAP handset OK * 14 characters displayed only 5 On Alcatel-Lucent IP Touch OK *

6 On SIP phones (Thomson 20x0) OK *

7 On ASCOM I75 OK *

attached to a distant OXE node OK *

* the display of the texte message in ringing is depending on the display of the forward on the terminal. Not 16 characters are displayed

6.1.1.5 On set out of service

problem

300/400 OK*

2 On Alcatel-Lucent MIPT 310/610

OK Destination out of

order : 0x9B

3 On Ascom 9d24 MK2 OK*

4 On GAP handset OK*

5 On Alcatel-Lucent IP Touch OK*

6 On SIP phones (Thomson 20x0) OK* 7 On ASCOM I75

OK Destination out of

order : 0x9B 8 On Alcatel-Lucent IP Touch

Destination out of order : 0x9B Trace 6115.2 on OK on 610

(17)

* On phones where the status is out of service, the Mobicall reports that the alarm has been presented on the phone. Text display on answer

of service

A different 16 character text on answer is configured

problem

300/400 OK 16 characters displayed 2 On Alcatel-Lucent MIPT 310/610 OK 16 characters displayed 3 On Ascom 9d24 MK2 OK 16 characters displayed 4 On GAP handset OK 16 characters displayed 5 On Alcatel-Lucent IP Touch OK 16 characters displayed 6 On SIP phones (Thomson 20x0)

N/A No message in conversation 7 On ASCOM I75 N/A No message in conversation 8 On Alcatel-Lucent IP Touch

Trace 6121.5 on OK on IP touch.

The alarm is forwarded on forward destination phone.

problem

OK No message in conversation 7 On ASCOM I75 OK No message in conversation 8 On Alcatel-Lucent IP Touch

(18)

6.1.2 UUI message sent with the call

of service

A User to User Information message is sent to the phone with the call A voice prompt is played. Possible alarm confirmation by key 3

problem

300/400 OK

Only with message of 120 char max, after * 2 On Alcatel-Lucent MIPT 310/610

3 On Ascom 9d24 MK2

OK

Only with message of 120 char max, after *

4 On GAP handset N/A

OK

Only with message of 120 char max, after * 6 On SIP phones (Thomson 20x0) N/A

7 On ASCOM I75 N/A

Only with message of 120 char max, after *

* : if message greather than 120 char, no message is received on phone and Mobicall get no status.

The call is forwarded. The text message is delivered on the called device, not on the forward destination.

problem

300/400 OK

2 On Alcatel-Lucent MIPT 310/610 OK

3 On Ascom 9d24 MK2 OK

5 On Alcatel-Lucent IP Touch OK

6 On SIP phones (Thomson 20x0) N/A

Trace 6133.5 generated : message received on IP TOUCH forwarded on MR300.

(19)

Step Action N/A Result Origin of the problem

300/400 OK

6.1.3 UUI message sent after the call is answered / confirmed

of service

A User to User Information message is sent to the phone when the call is answered A voice prompt is played. Possible alarm confirmation by key 3

problem

300/400 OK *

2 On Alcatel-Lucent MIPT 310/610 OK *

3 On Ascom 9d24 MK2 OK *

4 On GAP handset N/A **

5 On Alcatel-Lucent IP Touch OK *

6 On SIP phones (Thomson 20x0) N/A **

7 On ASCOM I75 N/A **

• *Trace 6142 generated : code de retour ISDN 9F : unspeficied cause.

• ** code 90 normal clearing received.

problem

300/400 OK

(20)

problem

300/400 OK

6.1.4 Hand free alarm reception

of service

A User to User Information message is sent to the phone when the call is answered The phone automatically answers the call on the loudspeaker

problem

300/400 OK

(21)

Step Action N/A Result Origin of the problem Comment 1 On forward to Alcatel-Lucent Mobile 300/400 OK 2 On forward to Alcatel-Lucent MIPT 310/610 OK 3 On forward to Ascom 9d24 MK2 OK 4 On forward to GAP handset N/A

5 On forward to Alcatel-Lucent IP

Touch OK

6 On forward to SIP phones

(Thomson 20x0) N/A

7 On forward to ASCOM I75 N/A 8 On forward to Alcatel-Lucent IP

Touch attached to a distant OXE node

OK

problem Comment 1 On forward to Alcatel-Lucent Mobile 300/400 OK 2 On forward to Alcatel-Lucent MIPT 310/610 OK 3 On forward to Ascom 9d24 MK2 OK 4 On forward to GAP handset N/A

Touch OK

OK

6.1.5 Ring cadence differentiation

of service

A User to User Information message is sent to the phone when the call is answered The call ring cadence is different from a normal call : this use the cadence specified in the

OmniPCX parameter boss/secretary cadency field.

problem

(22)

1 From Alcatel-Lucent Mobile

300/400 OK

8 On Alcatel-Lucent IP Touch attached to a distant OXE node

OK

The executive cadency must be

managed on the remote node also

problem Comment 1 On forward to Alcatel-Lucent Mobile 300/400 NOK * 2 On forward to Alcatel-Lucent MIPT 310/610 NOK *

3 On forward to Ascom 9d24 MK2 NOK *

4 On forward to GAP handset N/A *

Touch NOK *

NOK *

* : the call is lost, no phone rings. An error ISDN error is received by the Mobicall. Call is in status failed on Mobicall.

problem Comment 1 On forward to Alcatel-Lucent Mobile 300/400 NOK * 2 On forward to Alcatel-Lucent MIPT 310/610 NOK *

3 On forward to Ascom 9d24 MK2 NOK *

4 On forward to GAP handset N/A *

Touch NOK *

NOK *

* : the call is lost, no phone rings. An error ISDN error is received by the Mobicall. Call is in status failed on Mobicall.

(23)

6.1.6 Intrusion

All phones are mono-line and in conversation A 16 character text display is configured

A User to User Information message is sent to the phone when the call is answered The called phone hears a call presentation beep and hears the alarm message. A voice prompt is played.

6.1.6.2 Test result

problem

300/400 OK

6.1.7 UTF8 long text display

This function is only availble in G1.503.30 or R9.1 release, and on MIPT 310/610. See Appendix 10 for OXE specific configuration.

of service

A User to User Information message is sent to the phone when the call is answered A voice prompt is played. Possible alarm confirmation by key 3. The handset is in

DTMF transparency after the connect.

When the handset is busy, a pop-up window is displayed.

problem

300/400 N/A

3 On Ascom 9d24 MK2 N/A

(24)

attached to a distant OXE node N/A

problem

300/400 N/A

5 On Alcatel-Lucent IP Touch N/A 6 On SIP phones (Thomson 20x0) N/A

problem

300/400 N/A

5 On Alcatel-Lucent IP Touch N/A 6 On SIP phones (Thomson 20x0) N/A

6.1.8 Voice conference: 2 party conference

MobiCall receives a call from any type of phone

MobiCall calls a phone and sets up the conference once the called phone answers A 16 character text display is configured

A User to User Information message is sent to the phone with the call The conference is recorded

problem

Comment 1 MobiCall receives a call from any

(25)

2 MobiCall calls a phone and sets up the conference once the called

phone answers OK

3 A 16 character text display is

configured OK

4 A User to User Information message

is sent to the phone with the call OK

5 The conference is recorded OK

6.1.9 Voice conference: multiple participant (>2)

MobiCall receives a call from any type of phone

MobiCall calls several phones and sets up the conference once at least on called phone

answers. Other participants join the conference as they answer.

problem

Comment 1 MobiCall receives a call from any

type of phone OK

2 MobiCall calls several phones and sets up the conference once at least on called phone answers. Other participants join the conference as they answer

OK

3 A 16 character text display is

configured OK

6.1.10 Start alarm from Alcatel-Lucent phones to MobiCall

Each phone calls the MobiCall extension number to start an alarm A voice prompt is played, asking to record a voice message

The alarm is started and the recorded voice message played to the called phones

problem

Comment 1 A phone calls the MobiCall extension

(26)

2 A voice prompt is played, asking to

record a voice message OK

3 The alarm is started and the recorded voice message played to

the called phones OK

6.1.11 Localization of DECT phone

Each phone calls the MobiCall extension number to start the localization process MobiCall starts an alarm according to the DECT base station that has been localized

problem

300/400 OK

2 On Alcatel-Lucent MIPT 310/610 X

4 On GAP handset OK

5 On Alcatel-Lucent IP Touch X 6 On SIP phones (Thomson 20x0) X

7 On ASCOM I75 X

(27)

6.2 Using H323

The tests cover the same scenario than using QSIG Calls from Mobicall to OmniPCX Enterprise (OXE) phones

6.2.1 Text display on ringtone

of service

problem

OK 16 characters displayed 7 On ASCOM I75 OK 16 characters displayed 8 On Alcatel-Lucent IP Touch

problem

300/400 OK 2 On Alcatel-Lucent MIPT 310/610 OK 3 On Ascom 9d24 MK2 OK 4 On GAP handset OK 14 characters displayed only 5 On Alcatel-Lucent IP Touch OK “Trunk name -> forwarded” displayed 6 On SIP phones (Thomson 20x0) OK

(28)

problem

300/400 OK * 2 On Alcatel-Lucent MIPT 310/610 OK * 3 On Ascom 9d24 MK2 OK * 4 On GAP handset OK * 14 characters displayed only 5 On Alcatel-Lucent IP Touch OK *

6 On SIP phones (Thomson 20x0) OK *

7 On ASCOM I75 OK *

(29)

6.3 Using SIP trunk

The tests cover the same scenario than using QSIG Calls from Mobicall to OmniPCX Enterprise (OXE) phones

6.3.1 Text display on ringtone

of service

problem

OK 16 characters displayed 7 On ASCOM I75 OK 16 characters displayed 8 On Alcatel-Lucent IP Touch

problem

300/400 OK

6 On SIP phones (Thomson 20x0) OK

(30)

problem

300/400 OK

6.3.2 Call reception by MobiCall

Any phone on the list dials a number directed to the MobiCall server MobiCall receives the call and starts an “incoming call” scenario

6.3.2.2 Call reception by MobiCall from a phone from the network

problem

300/400 OK

(31)

7 Redundancy tests

7.1 Voice based alarm redundancy tests

The purpose of this section is to test the Alcatel-Lucent OXE with MobiCall in different topologies of redundancy, and illustrate that all redundancy failover mechanism are available

7.1.1 Alarm call reception (Redundant MobiCall – ARS configuration)

An Alcatel Lucent phone calls a MobiCall extension number to start an alarm

This extension number is configured with ARS, and respectively routed to MobiCall master

server and slave server

The alarm is started in any case whether the master or the slave is down

problem

Comment 1 From any Alcatel-Lucent phone,

Call the extension with MobiCall master server down

OK 2 From any Alcatel-Lucent phone,

Call the extension with MobiCall master server down

OK

7.1.2 OXE Spatial redundancy

A MobiCall server is connected to a GD in spatial redundancy MobiCall starts an alarm call to any type of Alcatel-Lucent phone

or

MobiCall starts a conference between two Alcatel-Lucent phones The CPU switch is done before and during a call / conference The alarm call or conference is handled / uncut in any case

7.1.2.2 Switch before a call emission by MobiCall

problem

Comment 1 MobiCall calls any Alcatel-Lucent

phone OK *

7.1.2.3 Switch during a call emission by MobiCall

(32)

problem 1 MobiCall calls any Alcatel-Lucent

phone, and is in conversation with thoses phones.

OK **

7.1.2.4 Switch before a conference hosted by MobiCall

problem

Comment 1 MobiCall receives a call from any

Alcatel-Lucent phone, and calls any Alcatel-Lucent phone to establish a conference

OK

The calls which are in ringing state when the bascul happens,

are lost.

7.1.2.5 Switch during a conference hosted by MobiCall

problem

OK **

* On a IP TOUCH attached thought ABC-F on IP link, the call cannot be delivered until the ABCF link between the two OmniPCX Enterprise goes up. This link is broken during the bascul.

** On a IP TOUCH attached thought ABC-F on IP link, the call is lost, because the ABCF link goes down.

7.1.3 OXE spatial redundancy with PCS, MobiCall connected to the PCS

A MobiCall server is connected to a PCS, connected to an OXE in spatial redundancy MobiCall starts an alarm call to any type of Alcatel-Lucent phone (attached to the PCS)

or

MobiCall starts a conference between two Alcatel-Lucent phones (attached to the PCS) The link between the PCS and the CPUs is cut before and during a call / conference The alarm call or conference is handled / uncut in any case

When the PCS takes the CPU MAIN role, all the phones reboot. Hence no alarm can be received by phone until the end of the phone reboot. This is the normal OmniPCX Enterprise behaviour.

problem

phone OK The phone on the PCS reboot, when the PCS became MAIN.

7.1.3.3 Switch during a call emission by MobiCall

problem

(33)

1 MobiCall calls any Alcatel-Lucent phone

X

All the communication

are lost during the bascul on

PCS

7.1.3.4 Switch before a conference hosted by MobiCall

problem

OK

7.1.3.5 Switch during a conference hosted by MobiCall

problem

X

All the communication

are lost during the bascul on

PCS

7.2 Text based alarm redundancy tests

The purpose of this section is to test the Alcatel-Lucent OXE with MobiCall in different topologies of redundancy, and illustrate that all redundancy failover mechanism are available

7.2.1 OXE Spatial redundancy

A MobiCall server is connected to OmniPCX Enterprise using CSTA. The OmniPCX Enterprise CPU bascul on the standby CPU.

MobiCall starts an alarm call to alcatel-Lucent phone

problem

phone OK The mobicall supports the switch of CPU, in spatial redundancy The Paging link must be established on the new MAIN CPU, after the bascul. This takes 10 seconds, when no Paging alarm can be sent. The Mobicall waits for the establishment of the link to send thoses alarms.

(34)

8 Text based alarms notification

8.1 Using Paging Interface on OmniPCXEnterprise

8.1.1 Connectivity and set-up

8.1.1.1 Test objectives

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

8.1.1.2 Test procedure

problem

Comment 1 Connect the application,

checks if there are incident messages using « incvisu » command

OK

2 Check using the http interface of the cstamono (port 2555) that the application is connected

(35)

8.1.2 Surveillance / recovery

Check how will react the application in case of a PBX reboot, switch-over or link failure…

problem

Comment 1 Disconnect the IP interface

between the OXE and the application server.

OK

2 Use the application to send an message OK The alarm is not sent, an error message is displayed in mobicall 3 Reconnect the IP interface,

and check if the application is connected again.

OK The connection

is done again 4 Check if the previously

message is sent to the OXE OK

The message is not sent 5 Reboot the OXE, and then

send a message using the

application OK The alarm is not sent, an error message is displayed in mobicall 6 Check if the application is

connected again OK

The connection is done again 7 Check if the previously

message is sent OK

The message is not sent

(36)

8.1.3 License tests

These tests shall verify that the application is working using the following rules : If the Notification Server lock on the OXE is strictly less than 50, the link is broken, and the application stops. If the Notification Server lock on the OXE is more or equal than 50, the application runs.

problem

Comment 1 Put an Notification Server

lock of 10, an run the application.

OK

2 Try to send an message

(37)

8.1.4 Functional Tests

8.1.5 Sending alarms

These tests shall verify that the application is able to send urgent and normal alarms

problem

Comment 1 Send a normal alarm without

ack “0” OK

2 Send a normal alarm with

ack “1” OK

! displayed on front alarm 3 Send a urgent alarm without

ack “2”

* displayed on front alarm 4 Send a urgent alarm with

ack “3” OK

# is displayed on front alarm 3 Delete a sent alarm

4 Send a discrete alarm “4”

OK The phone doesn’t ring. A @ is displayed on front alarm # is displayed on front alarm 5 Send a discrete alarm “5”

OK The phone doesn’t ring. A @ is displayed on front alarm PagingRequestType

ActiveAlarmCall value “0” - to send an alarm (text message)

StopAlarmCall value “1” - to delete a previous alarms

AskSotwarePack value ”2” - to get current licenses

ActiveSndCall value “3” - to send a discrete alarm

PagingPriority NormalNoAck value ”0” NormalAck value ”1” UrgentNoAck value ”2” UrgentAck value ”3” NormalSndCall value ”4”

8.1.6 Acknowledges of alarms

These tests shall verify that the application is able to manage the acknowledge of an alarm.

problem

Comment 1 Send a normal alarm, and

verify that acknowledge : phone ring is displayed

OK

2 Read the alarm and acknowledge it. Check status read in the application

(38)

3 Send a alarm to a phone our

of service OK

4 Send a alarm to a phone without the Notification Server right.

OK

PagingState protocol values :

Alert value “0” - the message is stored (ringing state)

Process value “1” - the message is read or acknowledged

OutOfCoverage value “2” - the destination is out of radio coverage

OutOfservice value “4” - the destination is out of service

Undefined value “5” - destination not declared as a NS device

NoAlert value “6” - the alarm cannot be deposit

(39)

8.1.6.1 Sending alarms

These tests shall verify that the application is able to send urgent and normal alarms. Using Mobicall the difference between a normal and an urgent alarm is the tones ringing. For an normal alarm, the ringing tones specified in the protocol is 1, for an urgent alarm it is 4.

problem

Comment 1 Phone Set connected and in

service.

Send a normal alarm

OK

2 Phone Set connected and in service.

Send an urgent alarm

OK

3 Phone Set out of service.

Send a normal alarm OK

4 Phone Set out of service.

Send an urgent alarm OK

5 Phone Set in a call.

6 Phone Set in a call.

7 Phone Set forwarded.

8 Phone Set forwarded.

8.1.6.2 Acknowledges of alarms

These tests shall verify that the application is able to manage the acknowledge of an alarm.

problem

Comment 1 Phone Set connected and in

service.

Send a normal alarm, and read it on the phone

OK

2 Phone Set connected and in service.

Check its state in the application

OK

3 Phone Set out of service. Send a normal alarm, and read it on the phone

OK

4 Phone Set out of service. Check its state in the application

OK

5 Phone Set in a call. Send a normal alarm, and read it on the phone

OK

6 Phone Set in a call. Check its state in the application

(40)

7 Phone Set forwarded. Send a normal alarm, and read it on the phone

OK

8 Phone Set forwarded. Check its state in the application

OK

PagingState protocol values :

Alert value “0” - the message is stored (ringing state)

Process value “1” - the message is read or acknowledged

OutOfCoverage value “2” - the destination is out of radio coverage

OutOfservice value “4” - the destination is out of service

Undefined value “5” - destination not declared as a NS device

NoAlert value “6” - the alarm cannot be deposit

(41)

9 Appendix A : Application description

9.1 Application description

Mobicall – system overview

Mobicall is based on 4 elements allocated to the server. These are fully integrated:

• The suppliers of information which bring the information to the Mobicall server.

• The receivers of information which receive the information from the Mobicall server.

• The Personnel-, Group & Alarm data which defines the way the information input is

• processed.

• Supervision & Analysis provides the user with all the required statistics for adequate management of the system.

* Suppliers of information

Mobicall basically supports all interfaces which are supported by standard computer systems. It is essential that the interfaces be reliable and, if possible, supervised by any kind of watchdog-concepts. Here are some examples:

• Supervision of contacts free of potential

• Integration of fire and intrusion detection systems

• Links to building management systems / SPS

• Nurse calls, heart alarm, emergency calls

• Launching alarms by phone calls, SMS, e-mail, mouse, key-board and screen, fax, internet / Web

• Connections through com-port interface, also ESPA 4.4.4

• Data connection over SNMP, TCP/IP, Socket, FTP, Netsend... * Receivers of information

In principle, Mobicall supports all interfaces which are backed by standard computer systems. It is essential that the calls are confirmed by the person answering the call so that Mobicall may function successfully and continue mobilization. Depending on the situation, Mobicall may start the escalation and call upon additional persons.

Calls with clear messages (Voice) to internal and external phones

• Text-messages to DECT – phones and other system phone sets

• Text-messages sent as SMS to GSM mobile phones and pager

• Alarm messages and information sent by fax and or e-mail

• Broadcasting onto loudspeaker system

• Alarm signal through broadcast to any PC-system in the network

• Emergency calls through SNMP, FTP, contacts (relays free of potential, others…

• Support of any H.323 terminal with Voice-over-IP connection * Personnel & Group Data

Every person to be contacted by Mobicall has a record containing access numbers (e.g. telephone, fax, pager, email) and function.

Information receivers can be assigned to groups. In a matrix the various receivers with their particular identification (telephone number, email address, …) can be selected and allocated to the respective groups.

Depending on the concept of the mobilization and the definition of the processes, a person may have several telephone numbers assigned.

Alliance & Application Partner Program Inter-Working Report