Filter
Top Products
Prestige 100 and 100IH ISDN Router and Router/Hub
Remote Node Configuration 4-5
Telco Options:
Allocated Budget
(min)
This field sets a ceiling for outgoing call time for this
remote node. The default for this field is 0 for no budget
control.
Default = 0
Period (hr) This field sets the time interval to reset the above
outgoing call budget control.
Transfer Type
This field specifies the type of connection between the
Prestige and this remote node. When set to Leased, the
Allocated Budget and Period do not apply.
64k/
Leased
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= No
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. The default is 300
seconds (5 minutes). This option only applies when
the Prestige initiates the call.
Default=300 secs for
an unconfigured
remote node. 0 secs
means the remote
node will never be
automatically
disconnected.
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 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.