User's Manual

ManualsBrandsAvaya ManualsHandsetsAvaya DECT Messenger with CS1000 Rls 7.0 - Book 2

251

252

253

254

255

256

257

258

259

260

260 Table: eDMSAPI_INBOUND

*IC When a call is made, the calling line identifier of the calling party

(also known as CLID) is used to confirm outstanding messages for those

devices in DEVICE table with the DEV_Pincode_str equal to the CLID.

This technique is known as incoming confirmation, and is typically used in

environments where urgent messages must be confirmed when sent to

devices such as SMS, PAGING, and SMTP, without implicit bidirectional

confirmation techniques embedded. A callback from a predefined number

(for example, GSM, home subscriber, and so on) can be used to call-off

and confirm messages.

An incoming confirmation is only valid if the called device is defined in the

eDMSAPI_INBOUND table with eDMSAPI_Type_str = *IC. Therefore, the

calling device receives a Ö indication before the message to confirm the

called device is valid, and an X for an invalid destination.

*IA When a E2 message is sent by an extension that is IoRegistered (field

DEV_IoRegister_b in table eKERNEL_DEVICE is true), an incoming alarm

action is triggered, providing eKERNEL with four pieces of information: the

calling device, called device, message, and priority.

When the eKERNEL application receives a request, the request is

valid when the called device is defined in the eDMSAPI_INBOUND

table with Type = *IA, and if the called and calling device is defined in

the eDMSAPI_INBOUND_EVENT table. Therefore, valid requests are

indicated with a Ö symbol before the message sent, invalid requests with a

X indication.

An example of an entry typically found in this field is as follows: *IA

eDMSAPII_Comments_str

This field can optionally be used by an administrator to store reminder

information, describing, for example, usage of the extension.

An example of an entry typically found in this field is as follows: "this port

is used for outbound user-to-user messaging".

Table 12

Sample data

eDMSAPII

_Site_id_n

eDMSAPII_

Area_id_n

eDMSAPII_

Called_dev_str

eDMSAPII

Type_str eDMSAPII_Comments_str

1 1 12345

*IC TEST Incoming confirmation

1 1 222

*IA TEST Incoming alarm

1 1 333

*IC Incoming confirmation

1 1 56789

*IA TEST

Nortel Communication Server 1000

DECT Messenger Installation and Commissioning — Book 2

NN43120-301 02.01 4 June 2010