ZETRON 2000 Series Specifications Page 196

  • Download
  • Add to my manuals
  • Print
  • Page
    / 232
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 195
Outdial TAP Networking
196 025-9034AA
The yellow time and maximum batch size setting form a pair of limits controlling the
passive holding of a batched page. Once either of these two limits for a destination has
been exceeded, that destination will start to be called. It will be called until all pages
batched for it have been sent or until one of the retry limits is exceeded.
By adjusting the batching control parameters you may “tune” the performance of outdial
TAP on your terminals. If you allow a fair number of pages to be collected before calling a
destination, you may reduce phone charges, due to reducing the effect of the logon
overhead per page. You may use the “scaling” parameter to cause high priority pages to be
sent immediately, while ordinary pages are batched up for a time before calling.
You may need to set various options for each terminal that you send TAP pages to. These
parameters are site-specific, so you will need to determine them for each new destination.
See Multiport for TNPP and TAP Outdial in the Series 2000 Paging Terminals Installation
and Maintenance for details.
Subscriber Database
When setting a subscriber up for a TAP outdial destination, you will need to select
Network destination for the subscriber. Fill out the symbolic TAP destination name for the
“Node” field and enter the subscribers ID on the destination terminal for the “ID” field.
The symbolic destination entry in the network.cus file will be used to set up the local
paging characteristics for the destination. You will need to fill out the pager information
for the subscriber and fill out their paging modes fields as well.
The following is an example of a subscriber record set up for an outdial TAP destination.
This subscriber will be paged locally as well. For any subscriber with “N” selected for the
Transmitters setting, the actual paging destinations are controlled by the network.cus file
on the paging terminal.
Orange Time After the orange time is reached for a batched page, the outdial
TAP card will boost the priority of the destination, ignoring the
normal retry timing until the page is sent or the red time is
reached. The orange time is the time that a batched page may
remain unsent before the retry delay values will be ignored.
Red Time After a page has been batched for more than the red time
without being successfully sent, it will be returned as being not
transmitted. In effect, a page exceeding the red time for its
destination is considered to have gone stale. This will result in
a log posting as a failed page, with a prefix character of “.” and
a status message of “no xmit”.
Page view 195
1 2 ... 191 192 193 194 195 196 197 198 199 200 201 ... 231 232

Comments to this Manuals

No comments