ZyXEL Communications 480 - Manual (Page 63)

Prestige 480 ISDN Router
Remote Node Configuration 4-5
Carrier Access Code This field allows you to select a specific carrier to take advantage
of discount telephone rates. Enter the carriers access code.
Nailed-up Connection This field specifies if you want to make the connection to this
remote node a nailed-up connection. See below for more details. Yes/No
Session Option:
Edit Filter Sets
Use the space bar to toggle this field to Yes and press [Enter] to
open Menu 11.5 to edit the filter sets. See the Remote Node
Filter section for more details. Default=
Blank
Session Option:
Idle Timeout (sec)
This value specifies the number of idle seconds that elapses
before the remote node is automatically disconnected. Idle
seconds is the period of time when no data is transmitted from
your Prestige. Administrative packets such as RIP are not
counted as data. This option only applies when the Prestige
initiates the call. Default=
100 secs for
the first
remote
node and
300 secs for
the others.
Once you have completed filling in Menu 11.1.1 – Remote Node Profile , press [Enter] at the message
[Press ENTER to Confirm…] to save your configuration, or press [Esc] at any time to cancel.
4.1.2 Nailed-up Connection
A nailed-up connection is a dial-up line where the connection is always up regardless of traffic
demand. The Prestige does two things when you specify a nailed-up connection. The first is that
idle timeout is disabled. The second is that the Prestige will try to bring up the connection at
power-on and whenever the connection is down.
A nailed-up connection can be very expensive for obvious reasons. Please do not specify a nailed-
up connection unless your telephone company offers flat-rate service or you need a constant
connection and the cost is of no concern.
4.1.3 Outgoing Authentication Protocol
Generally speaking, you should employ the strongest authentication protocol possible, for obvious
reasons. However, some vendor’s implementation includes specific authentication protocol in the
user profile. It will disconnect if the negotiated protocol is different from that in the user profile,
even when the negotiated protocol is stronger than specified. If you encounter the case where the
peer disconnects right after a successful authentication, please make sure that you specify the
correct authentication protocol when connecting to such an implementation.