Difference between revisions of "ESPA 4.4.4"
From Zenitel Wiki
(→Reference) |
(→Message example) |
||
Line 7: | Line 7: | ||
Typical example of a ESPA 4.4.4 message which AlphaCom will send to a paging system (checksum not show): | Typical example of a ESPA 4.4.4 message which AlphaCom will send to a paging system (checksum not show): | ||
− | SOH 1 STX | + | SOH 1 STX 1 US 550 RS 2 US CALL ME 101 RS 3 US 3 RS 4 US 3 RS 5 US 3 RS 6 US 3 ETX |
Same message, written as hex-values: | Same message, written as hex-values: | ||
Line 14: | Line 14: | ||
− | It is configurable if AlphaCom requires a “Status information” message in return. It is also configurable which callstatus value which is required to consider the call to be successful (Recordtype 7). | + | It is configurable if AlphaCom requires a “Status information” message in return. It is also configurable which callstatus value which is required to consider the call to be successful (Recordtype 7). |
== Reference == | == Reference == |
Revision as of 11:29, 21 May 2010
ESPA 4.4.4 is a protocol controlling wireless pagers. It uses ISO 1745, point-to-point on RS232 as data link layer. The AlphaCom can use this in two ways:
- Output: Sends a “start paging” message either due to manual or automatic action.
- Input: The AlphaCom can be set up to look like a pager transmitter. The AlphaCom inspects the display text and generates events to the Event Handler which do a range of actions. (“Fire Alarm protocol”).
Message example
Typical example of a ESPA 4.4.4 message which AlphaCom will send to a paging system (checksum not show):
SOH 1 STX 1 US 550 RS 2 US CALL ME 101 RS 3 US 3 RS 4 US 3 RS 5 US 3 RS 6 US 3 ETX
Same message, written as hex-values:
01 31 02 20 31 1F 35 35 30 1E 32 1F 43 41 4C 4C 20 4D 45 20 31 30 31 1E 33 1F 33 1E 34 1F 33 1E 35 1F 33 1E 36 1F 33 03
It is configurable if AlphaCom requires a “Status information” message in return. It is also configurable which callstatus value which is required to consider the call to be successful (Recordtype 7).