Specifications

197
Subscriber Database
Figure 45: ZbaseW — Transmitter Set to “N” for TAP Outdial
The outbound TAP pages’ log posting will show the external ID being used, as well as the
TAP destination number. In the example below the external ID is “8900110”, as was
entered in the subscriber database record. The network node destination for the subscriber
was set up to be outdial TAP destination 5, and RF channel one, zone zero. The local RF
page was sent before the TAP page due to the batching controls for the station and TAP
cards.
0095 test pg sent 11:37:11a 2 C 1|00S G0 00123456 D 18 95 TEST MESSAGE 65
0095 test pg sent 11:38:45a 2 C TAP05D ID [8900110] D 18 95 TEST MESSAGE 65
ZbaseW allows only a single “external” ID for a subscriber, which is used when calling
into a TAP destination. This means that the subscriber who is to have multiple outdial TAP
destinations must have the same ID code on all sites being dialed into, otherwise some
extra work must be done to set up their database entry.
To support a subscriber with multiple IDs on several terminals, first make a set of status
“V” records, one per TAP destination for this subscriber. Each of the status “V” records is
given a different TAP destination and the proper ID value to use when sending TAP pages
to that destination. As these status “V” records are never called, they may be given
subscriber numbers that do not fall within the normal number ranges of the paging
terminal.
Now set up the subscriber’s main ID number as a group, status “G”. Make the set of status
“V” records be members of the group just created, using the Edit Group function. Finally,
update the paging terminal with these changes. Now when the subscriber’s number is
called a series of pages will be generated, one per TAP destination and each with the
proper subscriber ID to use on that terminal.