Specifications

9261-7974 Issue 06
ESFIRECODER - Emergency Services Firecoder
Page 27
www.multitone.com
As an asterisk (*) is used for a wildcard string match, any DTMF * codes are sent to the Agent
Manager as S(tar) characters, and any DTMF # codes are sent as H(ash).
6.14 Agent Events: Alerter_2 Agents
This agent type will send the following events to the agent manager:
MG4:xx MG4 error
Alrt:Fx Fire Call (x = A..J)
Alrt:Tx Test Call (x = A..J)
Alrt:PE Emergency Officer Page
Alrt:PP Priority Officer Page
Alrt:PR Routine Officer Page
Alrt:PA Admin Officer Page
Alrt:PN Engineering Page
Covr:On Coverage Test On
Covr:Off Coverage Test Off
Engn:x Engineering Command
This agent will send a Page_Officer message to the Agent Manager for every original page actually
transmitted by the agent (i.e. not including repeats). This is done following any directory translation
and expansion.
The source address of the Page_Officer message will be the original source address of the command
sent to the Agent, or in the case of internally generated Coverage pages, the address of the alerter
agent itself.
This facility would typically be used to forward a "fill-in" page to another alerter. To assist in this, the
GD-92 call type (normally Alpha or Numeric) is set to the beep code (1-8) of the locally sent page.
On receipt of this special message type, the destination alerter will override the default beep code for
that call type and send a page with the same beep code and message format as the original call.
6.15 Agent Events: Paging Agent
This agent will send the following events to the agent manager:
Event Action
Page:Successful Page Successful
Page:Unconfirmed Unconfirmed Page Complete
Page:Failed Page Failed
Page:<error_text>
Page Failed with specified error text