|
|
|
|
|
The tbct command administers the Two B-Channel Transfer feature.
Synopsis
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Description
The tbct assign command creates a configuration file at $VS_CONFIG_DIR named tts.cfg if the file does not already exist. This configuration file is created by copying default parameters for TBCT to the configuration file for the specified card, except for any parameters that have been entered on the command line. Any command line parameters are copied to the configuration file. The default configuration file is located on the target server in /vs/data/tbct/tbct.cfg.
The system-wide parameters numchan, transfer, fail, and hunt must be assigned before any card parameters may be assigned. The tbct assign command exits with a usage error if an assignment of the system parameters is attempted a second time, that is if tbct already has a configuration file. The tbct assign command exits with a usage error if an assignment of parameters for a particular card is attempted a second time.
Card parameters can only be assigned for NMS cards that are assigned to the ISDN PRI T1 protocol isdntype of nortel or national. If an assignment is attempted for a card that is not assigned to the ISDN PRI T1 protocol with isdntype of nortel or national, the command exits with a usage error. Note that this command only supports two trunks (a dual card).
The tbct change command, with a card parameter, changes configuration file parameters for TBCT for that card. If the configuration file does not exist or the card is not already defined in the configuration file, the change command exits with a usage error.
The tbct display command, with a card parameter, displays the TBCT parameters for that card.
The tbct unassign command deletes the configuration file and the backup configuration file, if any.
Note:
The backup configuration file that adds .bak to the configuration file name is created if one or more tbct change commands are executed after tbct assign.
When Two B-Channel Transfer is administered for the first time, a configuration file is created in the $VS_CONFIG_DIR directory, or /vs/data if $VS_CONFIG_DIR is not defined. The configuration file is used by maintenance software when the voice system is initialized so that Two B-Channel Transfer (tbct) can be configured using the parameters defined in the configuration file.
The TBCT configuration file contains the following parameters:
Parameter Name |
Description |
Cardx.Trunk1 |
Indicates trunk1 for card x (x is the card number) allows or does not allow the TBCT feature |
Cardx.Trunk2 |
Indicates trunk2 for card x (x is the card number) allows or does not allow the TBCT feature |
bch_reserve |
Number of B-Channels to reserve for outgoing calls |
priority |
When to invoke the B-Channel transfer |
eh_method |
Error handling method to invoke if the B-Channel transfer fails |
ch_method |
Channel hunt method |
You can use the tbct assign or tbct change commands to administer the parameters. The following table lists the possible values for each parameter:
Config file parameter name |
Command-line argument |
Default value |
Possible values |
Config file values |
� |
card |
none |
Valid NMS card numbers |
Shows up as Cardx, where x is the card number in the Trunk parameters, such as Card1.Trunk1 |
Cardx.Trunk1 |
trunk1 |
none |
y|n |
y|n |
Cardx.Trunk2 |
trunk2 |
none |
y|n |
y|n |
bch_reserve |
numchan |
none |
0-94 You can reserve 0 through the total number of B-Channels |
0-94 You can reserve 0 through the total number of B-Channels |
priority |
transfer |
answer |
alerting|answer |
0/1 (0=answer, 1=alerting) |
eh_method |
fail |
bridge |
bridge|disconnect |
0/1 (0=bridge, 1=disconnect) |
ch_method |
hunt |
ascend |
ascend|descend |
0/1 (0=ascend, 1=descend) |
See also
