Specifications

191
Capcode Paging As Opposed To Subscriber ID Paging
well. If the subscriber’s service is discontinued then removing his record at his home
terminal will stop the generation of RF pages over the entire coverage region, although the
other terminals where he has phone number entries will continue to accept calls until his
record is deleted on each of them.
When using the above combination of ID and capcode paging it is sometimes convenient
to set up one “all area” secondary node address to send all TNPP ID pages over, and to
which all terminals will “listen”. Capcode pages are sent using destination node addresses
for each coverage region desired, as in the example above. When a terminal sees an ID
page that matches an ID in its database, it will send a capcode page out using the proper
secondary node address. Of course, this technique will only work if there is no overlap of
networked subscriber ID codes among all the terminals in the network.
The subscriber ID sent in a TNPP ID page could be that of a Group (status G) record. This
allows a group of pagers to be activated by network pages without having to send a
network page for each group member. Again, this also allows a single site to maintain the
group record, making it much easier to change the members of the group.