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
118 DECT Messenger Customer Engineer Manual
• requires an IP connection to a DAP Controller (DCC) in the SIP DECT
environment
• location detection only works on SIP DECT extensions
eLOCATION can support configurations with more than 255 radios. If
more than 255 radios are used, the first 255 radios use a 2-byte definition
from 00 to FF. The remaining radios use a 3-byte definition, for example
100, 101, 102, and so on.
ATTENTION
IMPORTANT
eLOCATION can handle location registration for one DECT cluster only.
eLOCATION works with SIP DECT only.
How it works
A handset sends a short message to the predefined extension number.
This extension number must have the property Location Alarm in DECT
Messenger. Based on this property, DECT Messenger activates location
retrieval for the handset. This means that DECT Messenger sets up a
connection to a DAP Controller through IP, and asks for the location of
the calling line ID (CLI) in the call. This CLI is the extension number of
the DECT handset making the call. The DAP Controller responds by
sending the RPN (Radio Part Number) to DECT Messenger. This RPN
number is not meaningful location information. There is a conversion
table (eLOCATION_RPN) that translates the RPN to meaningful location
information. This location information can be used in the message that
is sent.
The message can be sent to any output device. The relation between
the generated message and the destination group is defined in the table:
eLOCATION_INBOUND_RESULT. In this table, the relation is established
between the Calling Line ID, the Called Line ID and the Group to which the
message is sent. The message (string) is also defined in this table.
The message can contain variables that are filled in by DECT Messenger
before it is sent. You can use this feature of DECT Messenger to generate
a message similar to the following message.
SOS at location [Location] at [Location time] on [Location date]
from [Calling number] to [Called number]
Where:
• [Location] = the contents of the eLOCRPN_Message_str field in the
table eLOCATION_RPN
• [Location time] = current time
Nortel Communication Server 1000
DECT Messenger Fundamentals
NN43120-120 01.06
17 October 2008
Copyright © 2003–2008 Nortel Networks
.