User's Manual
Table Of Contents
- New in this release
- Nortel DECT Messenger Administrator Guide
- Preface
- Nortel DECT Messenger overview
- eCONFIG
- Adding a DECT device to the Messenger system
- DECT Messenger Customer Engineer Manual
- Preface
- DECT Messenger overview
- DECT Messenger in a WAN or MAN network
- Licensing
- Detailed module descriptions
- What is required to run DECT Messenger
- DATABASES in DECT Messenger
- Installing and getting started
- Using eCONFIG
- Using eTM
- eDMSAPI Inbound
- eLOCATION
- Connecting National Instruments modules
- Understanding Security features
- Using eBackup
- Setting up e-mail integration (eSMTP_Server/eSMTP)
- Using eSMTP Server
- Using eSMTP
- Sending SMS messages
- V.24 - RS232 connections (eCAP, eESPA)
- Using Import/Export menu
- eLOG
- Checking diagnostics

160 DECT Messenger Customer Engineer Manual
Figure 51
eKERNEL module refresh log file
The contents of these files are related to each other by means of
identifiers. You can import the files into a Spreadsheet application or
Database Application of your choice, for further analysis.
In the following sections, the contents of these files is explained.
ALARM Remove After GROUP id GROUP Description DEVICE id DEVICE
area DEVICE Outpgm eWEB user PINCODE Reason not processed
INrqs.csv file
In the file INrqs.csv is detailed information on the incoming alarms. The
following columns are available:
• INRQS id
This is a tag for each input request. This tag is an identifier for each
call. After the call is processed, the tag is free again and is 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 in format: YYYY-MM-DD
• TIME
Time in format: HH-MM-ss
• SET or RESET
The incoming request was a request to Set or Reset an alarm.
• TYPE
Indicates the type of incoming message:
Nortel Communication Server 1000
DECT Messenger Fundamentals
NN43120-120 01.06
17 October 2008
Copyright © 2003–2008 Nortel Networks
.