User's Manual

eDMSAPI_Seats_count_n
This field specifies the total number of seats available for E2 messaging (aCsOpenStream).
Sending an E2 message to a DECT extension consumes one seat (one seat is allocated
between the StartDataPath and the StopDatPath).
For receiving E2 messages (generation of an alarm), DECT extensions that are configured to
generate alarms (table eKERNEL_DEVICE field DEV_IoRegister_b) must be IoRegistered.
The number of possible IoRegisters is related to the number of seats available.
If eDMSAPI is configured with a larger value than available, too many simultaneous E2-data
requests are initiated simultaneously, which leads to a large number of failed requests.
An example of an entry typically found in this field is as follows: 30
eDMSAPI_eKERNEL_Seats_count_n
This field specifies the number of seats reserved for message requests (<msgrqs>) from
eKERNEL.
An example of an entry typically found in this field is as follows: 5
eDMSAPI_External_Seats_count_n
This field specifies the number of seats reserved for applications with direct access to the
eDMSAPI. For example, the eWeb module. The number of seats specified in the field is part
of the number of seats defined in the eDMSAPI_Seats_count_n field.
An example of an entry typically found in this field is as follows: 2
eDMSAPI_External_Address_str
This field specifies the IP address of the PC where the eDMSAPI module runs.
This value is necessary for external clients such as eWeb, which directly access the eDMSAPI
module.
When sending a normal message, the following format is used: SNDNMSG|ID|DNR|
Message<cr><lf>
When sending an urgent message, the following format is used: SNDUMSG|ID|DNR|
Message<cr><lf>.
Table: eDMSAPI
208 DECT Messenger Installation and Commissioning — Book 2 March 2012
Comments? [e-mail]