Operation Manual
208 NetWare MultiProtocol Router for ISDN 3.1 Installation and ISDN Configuration Guide
Consequence
Router A tries to establish the connection with more than 2 B channels. Router B can maximally offer 2 B
channels. The connection is established using the number of B channels router B can provide. However,
the ISDN-Controller T1 is constantly trying to set up the rest of the B channels. In countries, where the
attempt to set up a connection already costs a charge unit (as for example in Switzerland), this can lead
to high ISDN costs! Thus, be sure that the remote site is able to provide the number of B channels you
want to use at the time of the connection.
Operation of the Self-Learning Inactivity Timeout
The Self-Learning Timeout automatically adjusts the Inactivity
Timeout for outgoing connections to different charge intervals over
the day. To calculate the appropriate timeout value, the intervals
between two charging pulses sent by the PTT are measured.
To use the Self-Learning Timeout and adapt the Inactivity Timeout,
the following requirements must be met:
- the Inactivity Timeout must not be disabled.
- Advice On Charge During Call (AOCD) must be activated at your
ISDN access
- the connection charges must be counted during the ISDN connec-
tion and not only at the end of the connection.
If there are changes within your Private Branch Exchange or the Local
Exchange, the charging pulse can be ´lost´. If this is the case, set the
Inactivity Timeout to "Time-Controlled". For more information, refer to
Chapter 7, "Configuring ISDN Call Destinations".
When the Self-Learning Timeout is enabled, the NetWare MultiProto-
col Router for ISDN sets the Inactivity Timeout to one charge interval
minus two seconds. The calculated value is displayed on the system
console as follows:
Calculated self-learning timeout <x>
The Disconnect Timeout is only adjusted, when
- Disconnect Timeout = Same As Inactivity Timeout
- Inactivity Timeout is set to ´0´ (=disabled) and Disconnect Timeout
is set to any other value
In any other case, the Disconnect Timeout is not adjusted.
Configur.pm6 27.05.97, 12:33208