User's Manual

Figure 160: Module eDMSAPI inbound event - detailed configuration
• Next the eKERNEL module contacts the eLOCATION module to find out the physical
location of the SIP DECT user.
In DECT Messenger prior to release 2.9.10, the eKERNEL contacts only the eLOCATION
of the same site and the same area as the eDMSAPI module that alerted the alarm. This
means if the alarm was detected from eDMSAPI site 1 area 1, eKERNEL only contacts
eLOCATION site 1 area 1. This was a limitation to the scalability of the solution, as there
is a one-to-one relationship between eDMSAPI numbering and eLOCATION
numbering.
In release 2.9.10 and in subsequent releases, the eKERNEL contacts every instance of
eLOCATION of the same site of the originating eDMSAPI module. This means that an
alert from eDMSAPI site 1 area 1 is forwarded to all eLOCATION instances of site 1. As
a result, in a environment with three DAP Controller PCs and three associated
eLOCATION instances, the location request is sent to all three eLOCATION modules.
Each DAP Controller PC then has the opportunity to provide feedback on the last known
location of the requested extension or calling party, and return this last known location to
eKERNEL.
Depending on the version of eKERNEL, prior to release 2.9.10 or release 2.9.10 and
subsequent releases, the eKERNEL interprets the results from the location request. In
release 2.9.10 and newer version, the last use timestamp indication is used to determine
the location.
For these steps the eLOCATION instances must be configured, as shown in the following
figure. The configuration of eLOCATION involves a record in eLOCATION for each DAP
Module - eLOCATION
216 DECT Messenger Installation and Commissioning — Book 1 March 2012
Comments? [e-mail]