NAME
/vs/data/pri/pri.rc - PRI parameters
DESCRIPTION
The /vs/data/pri/pri.rc file (if present) contains
name/value pairs that can be used to override the default
values for system-wide parameters associated with PRI.
In the case of multiple PRI D-channels within a system, it
is also possible to have separate files for each D-channel.
The parameters specific to a D-channel must be installed in
files whose last character(s) are the number of the D-
channel group as identified in the output of the display
command. For example for a D-channel group 2, the display
card output would show DCH_GRP: 2 and the applicable parame-
ters would be found in /vs/data/pri/pri.rc.2
If there is a PRI parameter file present for the specific
D-channel, it will take priority over the system-wide PRI
parameter file (/vs/data/pri/pri.rc).
NOTE: It is the customer's responsibility to create and
maintain any files that are specific to a D-channel group.
These files may need to be renamed or otherwise changed
after administration of the T1/E1, or Quad boards used for
PRI, or after any automatic or manual renumbering of boards.
The PRI package will install the /vs/data/pri/att.dflts,
/vs/data/pri/nortel.dflts, /vs/data/pri/etsi.dflts,
/vs/data/pri/nisdn+bcas.dflts, and /vs/data/pri/nisdn-
bcas.dflts, files. These files contain the recommended
default timer and parameter values for each of the supported
PRI Types. Unless there is a /vs/data/pri/pri.rc.local
file, one of these files will be installed as the
/vs/data/pri/pri.rc file whenever the cvis_menu is used to
assign or change PRI assignments. The PRI Type field will
be used to select the matching .dflts file. Please note
that the last PRI Type field that is selected will apply to
the entire system (not just to an individual span as one
might assume when using the screen). The
/vs/data/pri/*.dflts files should not be modified.
If there is a need to change timer or other parameter values
in one of the .dflts files, then it is recommended that you
copy the appropriate .dflts file to /vs/data/pri.rc.local
and make the necessary changes in the /vs/data/pri.rc.local
file. The /vs/data/pri/pri.rc.local file if present will
take precedence over any of the .dflts files.
If more than one PRI Type is to be supported in the system,
or if there is a need to have different timer or parameter
values for some D channels, then you must create as many
/vs/data/pri/pri.rc.<n> files as are needed. The number of
these D channel specific files can usually be minimized by
letting the system wide defaults (from a .dflts file or
/vs/data/pri/pri.rc.local file) apply to the most common PRI
configuration in the system. Please remember that the D-
Channel specific files need to be re-checked whenever the D
channel numbers get revised by any administration.
Please note that the /vs/data/pri/pri.rc should not be hand
editted except perhaps for a quick test of the effect of
changing a parameter. That file (and any changes you have
made) is likely to be overwritten whenever PRI administra-
tion changes are made. If you want to permanently change
parameter values, create(or edit) the
/vs/data/pri/pri.rc.local file or the
/vs/data/pri/pri.rc.<n> files.
In general the PRI parameters will not need to be changed by
customers. In special cases, the application developer,
customer engineer (or the customer) may need to create the
/vs/data/pri/pri.rc.local file (or create and maintain files
specific to the D-channel).
NOTE: Numeric values rather than define symbol names must be
used. Parameter values can be entered in decimal (default)
or hex (when preceded by "0x").
NOTE: very little error or range checking is performed on
these parameters, so care must be used in changing these
files.
The following PRI parameters are supported:
DCHAN_DELAY This parameter indicates how many seconds the
mtc process should sleep after being told
that the D-channel is in-service before try-
ing to place the B-channels in-service. The
default value of 0 is appropriate for most
switches. A value such as 2 is recommended
for PRI connections to a Definity switch (to
reduce the chance of B-channels getting left
in the NETOOS state). This parameter is res-
tricted to the range 0 through 6.
NPI_TOA This parameter provides the Numbering Plan
Identifier and Type Of Addressing that is to
be provided in octet 3 of the Called Party
Number IE, or a special code that indicates
how prefix digits will be handled. Legal
values for this field can be be found in the
applicable PRI specification. A few of the
more likely values such as NAT_TEL(0x22) are
defined in q931_defs.h. The special code of
INT_OR_NAT_TEL (0x400) indicates that
INT_TEL(0x21) or NAT_TEL(0x22) will be used
based on whether an international number pre-
fix of "01" or "011" appears or does not
appear respectively in the dial string pro-
vided to irCall(3IRAPI). When INT_OR_NAT_TEL
is used, the international prefix (if any)
will be stripped from the dial string. Other
special codes for prefix handling may be
created for future PRI packages. The default
is 0x400 (INT_OR_NAT_TEL). When E1 PRI is
being used with the ACULAB protocol converter
card, it is recommended that NPI_TOA be set
to 0x22 (NAT_TEL) rather than using the
default value. Use hexadecimal numeric
values rather than define symbol names when
changing this parameter.
PROTOCOL This parameter indicates which country/switch
protocol applies. So far, no specific values
are defined. The default is 0.
FLAGS This parameter contains a combination of
values which controls different aspects of
the protocol stack. Possible FLAGS values,
in hexadecimal, are listed below.
0x10000 If set, PROGRESS message will cause a state
change.
0x20000 If set, calls are accepted on the D channel.
0x40000 If set, we will respond to global restart
requests with a global restart ack, other-
wise, we respond on a per B channel basis.
0x80000 If set, we ignore global restart requests.
0x01000 If set, we resend CONNECT on first expiration
of T313.
0x02000 If set, we do not send a STATUS message for
some types of unexpected messages received in
the call clearing state.
0x04000 If set, incoming calls to unavailable chan-
nels are negotiated to other channels, from
high to low.
0x00800 If set, incoming calls to unavailable chan-
nels are negotiated to other channels, from
low to high.
0x00100 If set, cause value 98 is used instead of
101.
0x00200 If set, we send RELEASE COMPLETE on "clear
collisions", otherwise, we do not send a
RELEASE COMPLETE.
0x00400 If set, we send a RELEASE COMPLETE when T303
expires the second time, otherwise, we just
clear the call internally and do not send a
RELEASE.
0x00800 If set, when T305 expires, the RELEASE mes-
sage sent includes the cause value from the
DISC, otherwise, the cause value "recovery on
timer expiry" is used.
0x00010 If set, companding can be different than the
protocol specifies, otherwise, calls are
rejected with cause value 88, incompatible
destination.
0x00020 If set, NISDN B Channel Availability Signal-
ing is used, to bring the channel into and
out of service.
0x00040 If set, Channel ID IEs, for NFAS B channels,
are sent and received with interface id
numbering for NORTEL 0,2,3..., otherwise,
interface id numbering of 1,2,3... is
expected.
0x00080 If set, if the SETUP includes an IE coded
"comprehension required", and that IE is not
understood by the protocol stack, we send a
RELEASE with CV 96, otherwise, the call is
accepted and the application has the oppor-
tunity to parse the IE.
0x00001 If set, AT&T style SERVICE messages are used,
to bring the channel into and out of service.
0x00002 If set, Overlap receiving is supported, oth-
erwise, if a received SETUP does not include
a called party ID, the SETUP is rejected.
0x00004 If set, The Sending Complete IE is included
in sent SETUPs.
0x00008 If set, FACILITY IEs belong to codeset 6
(instead of 0)
Common FLAGS values are:
0x33609 AT&T PRI
0x00c84 ETSI, overlap receiving not supported
0x00c86 ETSI with supported overlap receiving
0x00c99 E1 with ACULAB protocol converter
0x80941 Nortel
0x40980 NISDN without B channel availability signal-
ing
0x409a1 NISDN with B channel availability signaling
Additional information about the following layer 2 and layer
3 timer values can be found in the applicable PRI specifica-
tions.
T203 The default is 30 seconds.
T302 The default is 15 seconds.
T303 The default is 4 seconds.
T304 This default is 30 seconds.
T305 The default is 4 seconds.
T308 The default is 4 seconds.
T309 The default is 30 seconds.
T310 The default is 10 seconds.
T313 The default is 4 seconds.
T316 The default is 120 seconds.
T3M1 The default is 120 seconds.
T372 The default is 7 seconds.
SEE ALSO
VERSION
This is version 9/18/00 of this man page.