# Numeric/Beeping Pager

It has become fairly common to have the RTU call a numeric pager system with an alarm call. The RTU is well equipped to handle many of the current numeric pager protocols. Notification and Status Reports may be delivered to numeric paging destinations.

A report consists of a callback phone number, followed by *N, where N is the current number of unacknowledged alarms in the destination's group. Exception: when the callback string is Null, *N will be skipped. The callback phone number string may be set using Alarmware. The total number of characters allowed in a report is 30 characters. This is the display limit of most popular devices. If the pager cannot display 30 characters, a shorter callback phone number string may be configured. Otherwise, the service provider or pager will truncate the report.

The RTU phone number provides the default data for the pager callback string. Changing the RTU phone number will therefore immediately change the callback string for all destinations using the default.

There are a few cases where there are potential conflicts with no warning given:

1) The RTU phone number string may have incompatible characters. These characters are removed in the callback control and upon report delivery.

2) The RTU phone number string may be greater than 26 digits. No warning is given. The string is truncated at 26 digits.

3) The RTU phone number string may be null. No warning given. Callback control is also blank. The *N portion of the report is omitted.

Beeping Pagers can not display any sort of report.