ZETRON 2000 Series Especificaciones descargar pdf (Pagina 299)

299

The “.CUS” Files

OUTBOUND keyword is a symbol name or a secondary node ID, no local destinations

should be specified here. Local paging should be set once with the matching INBOUND

destination entries. This assures that a change to local paging parameters affects both

locally originated and incoming network pages.

Node ID is a hexadecimal number, limited to the range of 0001 to FFFF. The TNPP

channel and TNPP zone values are decimal integers in the range of zero through sixty-

three. Note that the three values are delimited by “,”. More than a single destination may

be specified; each destination triplet is separated from the previous destination by white

space.

Local (RF) destinations are specified by channel and zone number. The zone value follows

the channel, and is separated from it by a vertical bar “|”. The zone value is followed by a

“S”, and no spaces are allowed between any parts of a RF description.

Sample TNPP NETWORK.CUS Set-ups

The following is an example of the simplest mappings, single node IDs with no secondary

addresses or symbolic names.

In this next example, the network has several terminals that share a secondary TNPP node

ID for regional pages. This node is based on the area code, “509”, and is entered as

“5090”. Note that while this is a hexadecimal value in the logs it gives “5090” to match

the decimal value of the area code. The outbound section does not contain any RF

information, as that is derived from the inbound mapping for the node ID. This insures that

incoming pages and outgoing pages for network address 5090 will both be paged the same

locally.

The next example uses a symbolic destination ID. Symbolic IDs are useful in several

ways. One is that the actual destination IDs are hidden from the database entry, meaning

that if the network or RF information changes the database entries need not be changed,

OUTBOUND 0110,1,0N 1|5S We send to node 110, using TNPP settings of

channel 1 and zone 0. Pages of priority 3 and

above go out as high priority pages. Locally we

will transmit the page on channel one, zone five.

INBOUND CAP 112 1 0 1 3 1|5S We accept capcode pages sent to node 112, which

is the “us” address, with TNPP channel and zone

values of 1,0. If the page is low priority use a local

priority of 1, if high use a local priority of 3. Send

these pages to channel 1, zone 5.

OUTBOUND 5090 2 Pages of priority 2 and above are treated as

network high priority.

INBOUND CAP 5090 Default 1 2 1|0S Incoming capcode pages to ID 5090, any TNPP

channel and zone, are sent to local RF channel 1,

zone 0. If the network page has its high priority bit

set the page gets a local priority of 2; otherwise it

is priority one.

1 2 ... 294 295 296 297 298 299 300 301 302 303 304 ... 375 376

Comentarios a estos manuales

Sin comentarios

ZETRON 2000 Series Especificaciones Pagina 299

Comentarios a estos manuales

Relacionado con productos y manuales para Terminales Punto De Venta ZETRON 2000 Series