|
|
|
|
|
|
The commands nms assign, nms change, nms display, and nms unassign let you administer digital protocols on the NMS telephony cards.
Synopsis
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Description
The following table describes the arguments for these commands:
Argument |
Description |
Comments |
card |
A number that identifies a telephony card |
� |
protocol |
The digital protocol used on the card |
Options include: prit1 (ISDN-PRI T1), prie1 (ISDN-PRI E1), loopt1 (Loop Start T1), loope1 (Loop Start E1), and winkt1 (Wink Start T1) |
frametype |
The frame format |
� |
linecode |
A replacement for strings of consecutive zeros in data transmission using pulse code modulation (PCM) |
Options include AMI, AMI_ZCS, and B8ZS for ISDN-PRI T1 |
clktrunk |
The trunk that the card uses to set its internal clock |
� |
clksrc |
The origin of the telephony board's clock reference
|
OSC refers to the telephony board's oscillator, and NETWORK refers to the clock extracted from the telephony trunk. |
clkmode |
If the telephony board only controls its own clock, then the mode is STANDALONE. |
STANDALONE is the only option |
clkfallback |
The trunk that the system uses to set its internal clock if the timing source on clktrunk stops working |
At least 2 trunks must be connected to the card, with one being the clktrunk. The card uses the clktrunk source again when that source starts working. |
idlecode |
See idle code |
� |
isdntype |
The supplier of the ISDN service |
� |
length |
The length of the cable between the telephony board and the telephone network |
This value should only be changed if the length is more than 200 feet or if there are transmission problems |
fax |
Whether or not fax is enabled |
� |
dchannel1 |
Whether or not a data channel is available on Trunk 1 |
� |
dchannel2 |
Whether or not a data channel is available on Trunk 2 |
� |
country |
Which country the system is in |
� |
The nms assign command creates a configuration file, which is created by copying default parameters for the specified protocol to the configuration file, except for any parameters that have been entered on the command line. Any command-line parameters are copied to the configuration file. The nms assign command exits with a usage error if an assign is attempted for a card that already has a configuration file. If the card does not exist, the command exits with a usage error. This command supports only two trunks (a dual card).
The nms change command changes configuration file parameters for the card. The protocol associated with the change command is determined from the existing configuration file for that card. If the configuration file does not exist, the change command exits with a usage error.
Note:
The nms assign and nms change commands issue an error message if you enter y for dchannel1 or dchannel2 when using the protocol prie1, since NFAS is not supported for the prie1 protocol.
The nms display command, with a card parameter, displays the protocol and all of the administerable fields for that protocol for the card.
The nms unassign command deletes the configuration file, and the backup configuration file, if any, for the specified card. (The backup configuration file, that adds .bak to the configuration file name, is created if one or more nms change commands are executed for the card after it has been assigned.)
The nms display assignments command displays the cards and associated protocols for every card that has a configuration file.
Files
The following file is associated with the nms command:
/vs/data/NMS_Bx.cfg (where x is the card number)
See also
