Specifications

9261-7974 Issue 06
ESFIRECODER - Emergency Services Firecoder
Page 48
www.multitone.com
6.54.4 Message 27: Text_Message
For test purposes, if this message is sent to any Multitone Router (port 0), the router will send
the message back to the source.
6.54.5 Message 42: Alert_Crew
The following additional <alert_group> functions are available:
"FH".."FJ" - User defined fire call
“TH".."TJ" - User defined test call
"PN" - Page Engineer
“P0".."P9" - Page user entry 0..9
6.54.6 Message 43: Alerter_Engineering
The following additional <alerter_engineering> functions are available:
'F' - Transmit Pocsag zeros
'G' - Transmit Pocsag ones
'H' - Transmit Pocsag zeros & ones
'R' - Enable out-of-range transmissions
'S' - Disable out-of-range transmissions
6.54.7 Message 66 - MTA Status Change
This message provides adequate status for MTA failures, but does not cover errors arising
from "transient" events on dial-up MTA's, such as Engaged Lines and No Answer conditions.
Multitone dial-up MTA's can optionally be configured to send extended MTA_status_change
messages on dial-up fails with the following format:
<extended_MTA_status><comms_address><tel_number>
where <extended_MTA_status> codes are:
0..3 - As GD-92
4 - Modem Error
5 - Line Busy/Engaged
6 - No Carrier
7 - No Answer
8 - No Dial-tone
9 - No Logon (Modem answers but no ACK from remote)
<comms_address> is the node that the MTA was dialling. <tel_number> is the telephone
number it was using.