User's Manual
250 Table: eCAP_generic
eCAPG_Dft_GRP_Name_str
This field is used to provide a default group name, in the event that no
value can be retrieved from the available datastream. In this case, the
same value is used for all alarms generated through this eCAP generic
interface instance.
The value N/A must be specified if this field is not used.
An example of an entry typically found in this field is as follows: N/A
eCAPG_Dft_Msg_str
This field is used to provide a default message, in the event that no value
can be retrieved from the available datastream. In this case, the same
value is used for all alarms generated through this eCAP generic interface
instance.
The value N/A must be specified if this field is not used.
An example of an entry typically found in this field is as follows: N/A
eCAPG_Dft_Ala_Descr_str
This field is used to provide a default alarm description, in the event that
no value can be retrieved from the available datastream. In this case, the
same value is used for all alarms generated through this eCAP generic
interface instance.
The value N/A must be specified if this field is not used.
An example of an entry typically found in this field is as follows: N/A
eCAPG_Reset_start_n
This value, together with eCAPG_Reset_len_n and eCAPG_Reset_str,
refers to the optional reset functionality that can be deployed in the eCAP
generic module.
In most cases, a eCAP generic is implemented in environments, where
alarms are detected through an asynchronous serial interface, such as a
printer port.
The eCAP generic is targeted to environments, where each alarm
indication results in sending an alarm request to the eKERNEL interface.
Due to the nature of such requests, and the scope of the current eCAP
implementation, these alarms results in setting an alarm, a so-called
<msgrqs>-transaction that contains a *set request. In most cases you
define these alarm types in eKERNEL_ALARM table as alarms that are
removed after *sent. Therefore, the parameter eCAPG_Remove_after_str
is, in most cases, set to *set.
Nortel Communication Server 1000
DECT Messenger Installation and Commissioning — Book 2
NN43120-301 02.01 4 June 2010
Copyright © 2003-2010 Nortel Networks. All Rights Reserved.
.