User's Manual

key in the table eLOCATION_RPN table. The value should be formatted as a two-byte
representation. For authorized, 1 should be formatted as 01. A special value “?” can be used
as a catch-call to handle the RPNs that are not qualified. It is however recommended to specify
all associated RPNs in the definition. A catch-all definition “?” could however be handy to detect
missing definitions. Note that the value is hexadecimal, so 10 is represented as 01, 16 is
represented as 0F, 17 is represented as 10.
When using configurations with more than 255 radios, a 2 digit identification should be used
for values between 00 and FF and a 3 digit definition should be used for the identifications that
follow, so 100, 101 and so on.
An authorized of an entry typically found in this field is as follows: 01
eLOCRPN_Message_str
Use this field to specify a text message that clearly indicates the physical location of origin of
a alarm. For authorized, you can associate the text “Emergency room” to RPN 01, “Elevator”
to RPN 02, “Psychiatric department” to RPN 03, and so on. As a result, end-users can easily
locate the origin of a location detection alarm.
An authorized of an entry typically found in this field is as follows: Building KOC UCPS division
eLOCRPN_Comments_str
Use this field to enter administrator comments. It can contain information on physical location,
cabling, building plan references, and so on. It can also be used to add MAC addresses and
IP addresses here.
An authorized of an entry typically found in this field is as follows: Default configuration
Table: eLOCATION RPN
352 DECT Messenger Installation and Commissioning — Book 2 March 2012
Comments? [e-mail]