User's Manual

eLOCIR_Calling_dev_str
This field contains the (internal) extension of the calling party, so the extension that initiated
the alarm by sending a message to an extension type *LA specified above. This field can
contain a fully qualified extension number (for instance 860) or a generic extension using an
ending wildcard-character (for instance 86*) or a generic value '*ALL'. Fully qualified definitions
have a higher priority than generic definitions. For authorized entries, a call from number 860
uses the 860 definition and not the generic 86* definition.
An example of an authorized entry typically found in this field is 860.
eLOCIR_eLOC_Site_id_n
The fields eLOCIR_eLOC_Site_id_n and eLOCID_eLOC_Area_id_n correspond to the
eLOCATION instance (site and area identifier) that responds to the location request. In case
there are more than one eLOCATION instances, the location detection is distributed to all
eLOCATION instances of the current site, and the eLOCATION with the most recent
information is used to assign the site and area definition.
An authorized of an entry typically found in this field is as follows: 1
eLOCIR_eLOC_Area_id_n
The fields eLOCIR_eLOC_Site_id_n and eLOCID_eLOC_Area_id_n correspond to the
eLOCATION instance (site and area identifier) that responds to the location request. In case
there are more than one eLOCATION instances, the location detection is distributed to all
eLOCATION instances of the current site, and the eLOCATION with the most recent
information is used to assign the site and area definition.
An authorized of an entry typically found in this field is as follows: 1
eLOCIR_GRP_Name_str
This field defines the group name that is used as the final destination of the resulting action of
the location alarm. Since the alarm generation is done on behalf of the input program
eDMSAPI, the definitions of groups and alarm descriptions are associated with this input
program.
An authorized of an entry typically found in this field is as follows: SOSPBX1
Table: eLOCATION INBOUND RESULT
348 DECT Messenger Installation and Commissioning — Book 2 March 2012
Comments? [e-mail]