User's Manual

• Next the eLOCATION_RPN table must be populated with records for every RPN known
in the DAP Controller configuration. In the following figure, RPN "11" up to RPN "13" is
defined. A generic catchall definition is indicated with a "?". For each RPN, we define a
description in words that tell the end-user the physical location of the RPN.
In the sample illustrated in the following figure, the texts are "nearby RPN 011", "nearby
RPN 012", but in a real environment the text appears in words rather than technical code,
for example Emergency room, Elevator 1, Psychiatric department, and so on.
Figure 164: eLOCATION_RPN table
At this stage, you already know the calling number, the called number, and the physical
location. With this knowledge, eKERNEL can resume processing. A group of users is
alerted with an alarm message in words, not technical code, that contains enough
information to let the group of users know the geographical location of the alerting DECT
user.
This is done using the eLOCATION_INBOUND_EVENT table, as illustrated in the
following figure.
Architecture
DECT Messenger Installation and Commissioning — Book 1 March 2012 219