# Pager Examples (Using Keycodes)

Case #1: Simple Case Pager

The simplest case is when you only have to call the pager and can hang up as soon as it answers, with no information being passed to the pager except that someone called. If you have only one RTU (and no one else uses the number) you assume that any call from the pager is an RTU alarm call, and proceed from there. Of course, if you had two possible callers, you wouldn't know which one had called.

Configure the first phone number to call the pager, the second phone number to call the plant foreman (in case pager call does not get through).

1. Enter Keycode 70 1* 9 #5 1 713 235 3456 ENTER

70 1* | Configure Destination 1
9 | Get an outside line
#5 | Pause 1 second
1 713 235 3456 | Hypothetical long distance number to call pager
ENTER | Complete phone number

2. Enter Keycode 70 2* 9 #5 548 7632 ENTER

70 2* | Configure Destination 2
9 | Get an outside line
#5 | Pause 1 second
548 7632 | Hypothetical local number to call foreman
ENTER | Complete phone number

Case #2: Passing a Phone Number to a Pager

Some pager systems will allow the caller to enter a phone number (or other ID) which is then sent to the pager for display. When the person with the pager gets the call, he will know immediately from the number displayed, which RTU has called. This is a good system if you are using multiple RTUs, or have other pager calls in addition to the RTU.

Consider the following example of initiating a call to a paging system. We will assume here that we don't have to dial a 9 to get an outside line for this example. Entry of additional delay digits may be required for proper timing of the pager call session.

The phone number string for this example with the first phone number calling a pager is:

1. Enter Keycode 70 1* 235 2456 #5#5#5 548 1234 ENTER

70 1* | Configure Destination 1
235 2456 | Pager phone number
#5#5#5 | Wait 3 seconds
548 1234 | RTU phone or other number used to identity the source of the pager call
ENTER | Perform command

2. Enter Keycode 70 2* 548 7632 ENTER (this configures the second Destination to call the foreman in case the pager call doesn't get through).

70 2* | Configure Destination 2
548 7632 | Hypothetical local number to call foreman

Case #3: Exception

With some pager systems, having the RTU Call Progress Monitoring (CPM) turned ON may cause a delay that will not allow the pager message to be transmitted in the time allowed. If this is the case with your paging system, either have CPM in the default OFF state, or if you want CPM ON, a "@" symbol can be used in the place of #6 pause for tone detect. The critical task here is to time the delay from the last digit dialed until the pager beeps. The delay time requirements are determined by using a stopwatch or a clock with a second hand. You want to time this delay to the nearest second, then add 1 second to be sure. Consult the diagram to see the time line of events, then configure the RTU.