Specifications

System Configuration Files
294 025-9035AA
Following the function digit will be the values of the “Caller” and “Group” settings. The
caller field will be “Y” for “yes”, “N” for “no”, or “D” for the “default” setting. The group
setting will be displayed as a “G” if Group is “yes”, or a “-” if Group is “no”.
There are some changes to the log file posting as well. Posting related to a status “G”
record, the group master record will have “(group)” in the CAP code field and a lower
case “g” in the pager type field. The trunk function code overrides will post as “generic”
functions codes, that is “G<digit>”, for the group master and in some error cases. This
reflects that the override function code has not been converted to the pager specific
function code at that point. Actual pagers should have their function codes posted in the
normal fashion.
Sample TRUNKS.CUS lines
FunctionCode 5 Caller default Group yes
Trunk 8a 8B
Sample OPTIONS.CUS lines
;
; 'type' is the pager type
;
; 'msgs' is the type of message(s) that a particular page
; has. For pager types that will ever get voice messages the
; 'voice' and 'both' entries are not needed.
;
; The list 0..9 corresponds to the function code values
; that may have been selected by the trunk overrides.
;
; The list of numbers on each 'PagerCodes' line is the
; set of actual function codes to be used. You must fill
; in all ten values, even if most of them will never
; be used.
;
; -- Generic Function Codes -
; type msgs 0 1 2 3 4 5 6 7 8 9
;
PagerCodes poc tone 1 1 1 1 1 1 1 1 1 1
PagerCodes poc voice 4 4 4 4 4 4 4 4 4 4
PagerCodes poc display 9 8 7 6 5 4 3 2 1 0
PagerCodes poc both 4 4 4 4 4 4 4 4 4 4
;
PagerCodes multi tone 1 1 1 1 1 1 1 1 1 1
PagerCodes multi voice 4 4 4 4 4 4 4 4 4 4
PagerCodes multi display 9 8 7 6 5 4 3 2 1 0
PagerCodes multi both 4 4 4 4 4 4 4 4 4 4 ;
Commands within NETWORK.CUS
The 2000 Series terminal uses the network.cus file to describe its processing of inbound
and outbound pages, and the logging of status reports from the network card. There are
two main sections to the network.cus file, one for describing the processing of inbound
pages, the other one for the processing of outbound pages. These two sections are not
physical order dependent sections in the file. Rather they use a key word to tell which
section each line refers to. Lines within the network.cus file may be grouped by logical
section, such as all inbound control, by node ID, that is, grouping together the outbound,
inbound, and logging control for a given secondary node. The lines can even be placed in
random order.