ARMS Monitor911 Application

NENA stands for National Emergency Number Association. The NENA standard is enforced upon telephone carriers by the government, bringing about some conformity with regard to exchanging ANI-ALI data across platforms (such as from the telephony system server to the CAD server). 

The 911 Call window prompts the dispatcher with the parsed ANI-ALI caller data, enables the dispatcher to start a new CAD entry, or appends an existing CAD entry (i.e., existing Open Call), or cancel.

How does ARMS obtain the ANI-ALI caller data?

ARMS Monitor 911 can read the raw data flowing into the connection to the ARMS server and then allow the agency to create and implement the desired parsing of that raw data. Additionally, this gives the agency the ability to somewhat change with the times, as new telephony equipment is brought into production (i.e., the agency is not backed into a corner with non-modifiable ANI-ALI settings).

Through a connection from the ARMS server to the telephony system server (typically, a COM port / serial cable connection), the telephony system and the ARMS server continually “shake hands” to stay in touch for active monitoring of sudden bursts of ANI-ALI caller data that “spills” over into CAD. This data is sent to CAD by the telephony system, in NENA standard form, within a few seconds of the dispatcher answering the call. However, the caller data is not sent by the telephone system until the call has been answered.

In the image above, you can see portions of the ARMS Monitor 911 Configuration feature, which allows the agency administrator to view the raw “Read Data” and apply parsing commands to retrieve the correct data appropriate fields in ARMS.

After the agency administrator has completed and saved the Parse Parameters as desired (i.e., the “Trimmed Data”), the settings are saved and put to work so the dispatcher is receiving new 911 Call prompts using effectively parsed ANI-ALI caller data.

ARMS CAD saves a copy of the ANI-ALI caller data into the CAD >> Police Information field. As a result, the dispatcher or administrator can view the original content received from the telephony system.

From the Blog

  • Struggling with TIBRS reporting? Learn the biggest challenges agencies face and what to consider when choosing an RMS.

    TIBRS Compliance Made Simple: Choosing the Right RMS

    State reporting requirements continue to evolve, placing increasing pressure on law enforcement agencies to capture, validate, and submit accurate crime data. For agencies in Tennessee, compliance with the Tennessee Incident-Based Reporting System (TIBRS) is a critical part of daily operations. While TIBRS is designed to provide more detailed and actionable crime data, many agencies struggle…

    , , ,
  • Discover why generic public safety systems fall short for campus police and the risks higher ed agencies must address.

    Why Higher Ed Police Departments Need Purpose-Built Public Safety Software

    Campus safety has become increasingly complex. Higher education police departments are responsible not only for traditional law enforcement duties, but also for ensuring compliance with federal regulations, coordinating across multiple departments, and maintaining a safe environment for students, faculty, and visitors. Unlike municipal agencies, campus police operate within a unique ecosystem that requires a different…

    , , ,