User's Manual

Not yet implemented.
• PINCODE
After an incoming Confirmation is received, you see the PIN code in this field. (For an
Incoming Confirmation, the TYPE filed shows incrqs *IC.)
• Reason not processed
This field gives you information on why an incoming alarm is not processed. The
messages gives you a clear indication of the cause, such as an alarm cannot be
processed. Another example of a message is: Called device does not exist in table
eCSTA_INBOUND_EVENT.
OUTrqs.csv file
This file contains a record for each outgoing message (request) to a device. The following
columns are available:
• OUTRQS id
This is a tag for each output request. This OUTRQS id is used in the two OUT log files
that specifies the output processing. Note that this OUTRQSid is not unique in the logging
files. It is used on a call-by-call basis and can therefore be reused for a next call/alarm
after the alarm is finished.
• INRQS id
This is a tag for each input request. This tag is a call-by-call identifier. After the call is
processed, the tag is free again and can be used for another incoming alarm. Therefore
this tag must always be seen in relation to the incoming alarm time and date. This INRQS
id is used in the two other LOG files that specifies the output processing.
• DATE
Date that the alarm was sent to the output device. Format: YYYY-MM-DD
• TIME
Time that the alarm was sent to the output device. Format: HH-MM-ss
• DEVICE id
Device ID of the output device to which the alarm was sent. The Device ID is not
necessarily unique. However, the combination of Device ID, Device Area, Device Outpgm
and Device Outpgm Facility make the device unique. Therefore you must always consider
these fields as a group, to avoid mistakes.
• DEVICE Area
Area of the output device to which the alarm was sent.
• DEVICE Outpgm
DECT Messenger Customer Engineer Manual
150 DECT Messenger Fundamentals March 2012
Comments? infodev@avaya.com