
Output Program that is used for the diversion destination device.
• DIVERTED DEVICE Outpgm Facility
Output Program Facility that is used for the diversion destination device.
INrqs.csv
This file contains information about the response(s) (reply) that came from devices on an
outgoing alarm/message. 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 response was received from the output device or from the PBX if the device
did not respond itself. Format: YYYY-MM-DD.
• TIME
Time that the response was received from the output device or from the PBX if the device
did not respond itself. Format: HH-MM-ss.
• DEVICE Id
Device ID of the output device that generated the response. Of course, this is the same
as the device to which the alarm was sent. The Device ID is not necessarily unique.
However, the combination between the Device ID, the Device Area, Device Outpgm and
the Device Outpgm Facility makes the device unique. Therefore you must always take
these fields together, to avoid mistakes.
• DEVICE Area
Area of the output device that generated the response.
• DEVICE Outpgm
Output Program of the output device that generated the response.
• DEVICE Outpgm Facility
Output Program facility of the output device that generated the response.
• MESSAGE
This is the actual message that was send to the output device and for which it generated
the response.
DECT Messenger Customer Engineer Manual
152 DECT Messenger Fundamentals March 2012
Comentarios a estos manuales