User's Manual

Figure 71: eESPA Connection tab showing a valid configuration
Because the eESPA is designed to handle serial data communications with a number of paging
systems, the eESPA must be configured before use. These values are returned through the
<cfgrpy> reply that is sent on return of the <cfgrqs> request.
Note:
The values shown in Figure 71: eESPA Connection tab showing a valid configuration on
page 122 are retrieved from the DECT Messenger database; from the KERNEL_INPGM
table, and from the eESPA, eESPA_OUTBOUND_CFG, and the eKERNEL_SITE tables.
At start up, the eESPA.exe appears the specified COM port with the specified settings.
Note:
The COM port you identify must be available, and you must specify a valid baud rate, and
so on.
As well, a physical connection between the specified COM port and the external paging system
must be available, which requires a serial cable. In most cases, you can use a standard null-
modem cable. However, in some cases, alarm systems support a limited number of control
signals (for example, ground, send and receive), so consult the alarm system vendor for cable
specifications.
If no COM ports are available, extra hardware (such as DigiBoard PC/4e and DigiBoard PC/
8e) is required to provide extra serial ports. Investigate compatibility issues (operating system
support, driver available, and so on) and hardware requirements (memory, available slots, IRQ
conflicts, and so on) before purchasing equipment, or configuring the system.
In some cases, additional hardware is needed, for example, when RS-232-C limitations apply
(for example, at 9600 baud maximum limit of 9 metres). In some cases galvanic isolation is
requested, or base-band modems, SOPHO LAM, CISCO equipment, and so on are needed
to bridge the distance between the DECT Messenger and the alarm system. In many cases
Module - eESPA
122 DECT Messenger Installation and Commissioning — Book 1 March 2012
Comments? [e-mail]