ZETRON 2000 Series Specifications download pdf (Page 190)

TNPP Networking

190 025-9034AA

There is no way to count the number of occurrences of a particular capcode network page.

The terminal that handled the call that caused the capcode page to be sent over the network

will record a call count for the phone call.

Capcode paging is useful when a subscriber wishes to receive pages over a large area, but

only has a phone number at one location. An example might be a contractor that may be

anywhere in the state but keeps a paging phone number just in the city where his office

resides.

TNPP subscriber ID paging, on the other hand, is similar to normal subscriber paging in

that each terminal that is expected to perform a local RF page for the subscriber must have

an database entry for that subscriber ID.

As the subscriber ID is passed as part of the page, each terminal accepting the page from

the network must look the ID up in its local database, so there is a great deal more control

over which pages will be transmitted locally. The network processing will allow the

acceptance of a particular range of subscriber IDs from a given node ID, similar to the

“valid digit block” on trunks.

As the receiving terminals perform a database look-up for each ID page it is possible to

correctly call count such pages at each terminal.

Network subscriber ID paging is useful when subscribers have local phone numbers at

several sites. This may occur when the network is a collection of terminals that control

their own transmitters, or when many of the terminals are just being used as concentrators,

sending pages to central sites that do the actual transmitter control. In either case, several

terminals will need a database record for network subscribers, in order to accept phone

calls for the subscriber.

A combination of ID and capcode paging can be used to an advantage when the above

example is desired. For any customer that has network coverage, each terminal that

supports a local phone number for that customer will have a database entry set up to

supply Network ID paging, with one exception. The exception is the “home” terminal for

that subscriber, usually the site that actually issued the pager to the subscriber; at that

terminal the subscriber is given a record for Network capcode paging. This one site has the

description of the subscriber’s pager, all the other terminals only know his ID code and

coverage region. If the subscriber’s pager needs to be replaced, or his coverage region is

changed, this is done only at his home site.

When using this combination the overall sequence of events is as follows. Someone

attempting to page the subscriber, Joe Smith, calls Joe’s local number on the terminal in

the caller’s city. The terminal accepts the display message and sends it over the network as

an ID page. When Joe’s home terminal receives the page it looks up his subscriber record,

extracts his pager information, and generates a local page and network capcode page for

Joe’s coverage region. This capcode page is sent back out over the network, where each

terminal in the coverage region will generate a local RF page from the network capcode

page.

This combination allows for single site maintenance of a subscriber’s pager and coverage

region information. Call counting for the subscriber can be done at a single location as

1 2 ... 185 186 187 188 189 190 191 192 193 194 195 ... 231 232

ZETRON 2000 Series Specifications Page 190