Operation Manual

Configuration Interdependencies 203
When Inbound Call Processing is enabled, Inactivity Timeout and Disconnect
Timeout should be set to the same value to prevent the remote site from
trying to set up the physical connection after an inactivity timeout.
Interdependencies with Timeout Mechanisms
Security Call-Back and Timeout Mechanisms
If Router B has to transfer data to Router A in regular intervals
throughout the day and the connection is terminated physically and
logically after a certain period of inactivity, it does not make sense to
configure Security Call-Back, since this would lead to additional
costs.
Situation
Router A:
Interface 1: Security Call-Back: Force Call-Back to Caller-Specified Number or
Force Call-Back to CLI Number
Router B:
Call destination
for Router A: Inactivity Timeout = Disconnect Timeout
- Router B calls Router A.
Consequence
When the connection has been idle for a specified period, it is disconnected physically and logically.
When Router B again sets up the physical and logical connection, Router A hangs up and calls back. In
this way, one charge unit is wasted each time by Router B. If the connection would only be terminated
physically after a certain time of inactivity, Router B would be able to set up the underlying physical con-
nection without wasting a charge unit.
Inactivity Timeout and Disconnect Timeout Set to Different Values
The following example shows what happens when the physical ISDN
connection is disconnected by the Inactivity Timeout, and the logical
network connection is terminated later by the Disconnect Timeout:
Configur.pm6 27.05.97, 12:33203