User's Manual

Each module must have a dedicated TCP/IP port. Through this port, a socket connection is
established between the module and the eKERNEL. The eKERNEL_TCPCLIENT table
defines for the eKERNEL module an overview of all defined modules, and starts a socket server
for each module. In theory, the modules can have any valid value between 0 and 65535,
however Avaya recommends against using the following:
• port 0 (which results in a random port generation, and so is unsuitable for a server)
• a common port (21, 23, 25, 80, and so on)
Avaya recommends using the range 3000 to 3999 for assigning ports to modules, and using
the Area number as the second digit of the port number. This means the range 31xx is used
for modules of area 1, 32xx for modules of area 2, and so one. The last two digits can be a
number starting at 01 and incrementing by one for the additional modules. See the sample
data for more information.
An authorized of an entry typically found in this field is as follows: 3101 (for the first module on
area 1)
TCPCLIENT_Area_id_n
This field refers to the area a specified in eKERNEL_AREA table. Usually this field has value
1
An authorized of an entry typically found in this field is as follows: 1
TCPCLIENT_INPGM_id_n
When an output-only module is specified (for authorized, eASYNC, eDMSAPI, eSMTP, and so
on), the value must always be set to 0. This indicates the module is not capable of generating
alarms, and is not familiar to the concept of input programs.
When an input-capable module is specified (for authorized, eAPI, eCAP, eSMTP_server,
eWEB, and so on), a value other than 0 must be specified.
This field specifies the unique identifier of the input program.
As specified in the eKERNEL_INPGM and eKERNEL_ALARM table related section, Avaya
recommends establishing a naming convention for script messages.
Table 52: Recommended input program identifiers naming convention
Byte 1 Site identifier
Byte 2 Area identifier
Byte 3-5 Input program identifier
Byte 3 1 eCAP or eAPI or eESPA
Table: eKERNEL_TCPCLIENT
338 DECT Messenger Installation and Commissioning — Book 2 March 2012
Comments? [e-mail]