Outgoing Wan Connections; How Outgoing Connections Are Established - Digi PortServer II User Manual

Outgoing WAN Connections

How outgoing connections are established

Outgoing WAN connections can be initiated two ways:
1. If the set user option dialout=on and no ActivateTime (described
later) is defined, the connection is created immediately the user requests it. If a
bringup filter is defined, PortServer II waits for the filter to trigger before dialing;
if there is no bringup filter, the number is dialed immediately.
Note: Even if a bringup filter is defined, but the NetRouting parameter is rec or
both, an initial connection is made to attempt to learn about routes from
the remote end of the connection.
2. Using the ActivateTime option. Outgoing connections can be initiated at specific
times or on certain days using the set user basic options command with the
AccessTimes option. If the current time is out of the specified range,
PortServer II waits until the time enters the allowable range before bringing up the
connection.
3. Entering the command wan
connection specified by name.
An outgoing WAN connection remains active until the period during which the
connection is permitted expires, an idle timeout or hang-up is detected, or you issue a
wan close command. Entering the following command also closes any current
connections on the named WAN:
set wan name=name dialout=off
Note: For more information on the wan command options, refer to wan in the
Command Reference Guide.
Outgoing connections can also be closed by an idle timeout. The idle timer monitors
activity on the connection and, if it does not detect IP packets, before the timer delay
expires, it disconnects the user. The link is returned to the bringup state, awaiting IP
packet activity to re-establish the connection.
90030500B
start=name immediately brings up the
Configuring WAN Connections Page 113