
281
The “.CUS” Files
;
; This mapping can be seen via zlink by running the "pagers" command.
; However, note that for POCSAG the Zpage function code is 1 less than the
; zbase function code. Thus if you set a pager up with function code 2 in
; zbase, it will log P1 in the system log. So the default table as seen
; by the pagers command will be:
; 00 01 02 03 04 05 06 07 08 09 10
; Voice 03 03 03 03 00 00 00 00 00 00 00
; Display 00 01 02 03 00 00 00 00 00 00 00
; Display 00 01 02 03 00 00 00 00 00 00 00
;
; In the M2000, if another mapping is desired, the "PagerCodes pocsag
; voice", "PagerCodes pocsag display", and "PagerCodes pocsag tone" (if
; Send Empty Message Yes) lines can be used to set the mapping to whatever
; is desired.
;
; A POCSAG voice or display pager, who is a group member, will use the
; group function code when it is a group member. If the group is a voice
; and display group, function code 4 had better be used, so that the voice
; and the display message are successfully sent in one page.
Load Management
Load management in 2000 Series paging terminals regulates access to the terminal so that
pages accepted from callers are processed within a reasonable length of time.
When the rate at which pages are entered exceeds the rate at which they can be
transmitted, the queue of waiting pages grows and the delay before a new page is
transmitted increases. The queue also consumes system memory; when memory is
exhausted, the processing of pages is delayed without consideration for page priority.
The limit of acceptable delay depends strongly on callers’ expectations. If a page is not
answered within the expected period, callers will often assume it was lost or missed and
enter it again. This produces a positive feedback in the load; once this threshold is crossed,
load management becomes necessary.
The need for load management mechanisms indicates that the paging market’s demands
exceed the terminal’s present capacity. This is likely to cause user dissatisfaction and loss
of customers. The system operator needs to know when a larger potential market exists so
that the system can be expanded accordingly.
The key elements of load management are: restricting entry of pages when system load
becomes excessive; monitoring of paging delays and memory usage to detect overload;
specifying paging delay and memory usage thresholds which cause load management
mechanisms to be invoked; and reporting of overloads to the system operator.
Load Regulation
All load regulation is achieved by rejecting calls. Call rejection always occurs after the
subscriber ID is known. This means that the caller must overdial the ID on an end-to-end
line or special DID number. Once the ID is known, load management logic is based on the
type and destination of the call and the subscriber's priority.
When a call is rejected, if the system has voice prompts and the “load management”
prompt is available, it is played. This prompt should inform callers that their call cannot be
Kommentare zu diesen Handbüchern