ZyXEL Communications 1001H manual Outgoing Authentication Protocol, 64k Leased

P100IH ISDN Router

Telco Options:

Allocated Budget (min)

Transfer Type

Period (hr)

This field sets a ceiling for outgoing call time for this remote node. The default for this field is 0 for no budget control.

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.

This field sets the time interval to reset the above outgoing call budget control.

Default = 0

64k/

Leased

Schedules	Apply up to 4 schedules sets, separated by commas to
	your remote node here. Please see later for a full
	discussion on schedules.
Nailed-up Connection	This field specifies if you want to make the connection to		Yes/No
	this remote node a nailed-up connection. See below for
	more details.
Toll Period	This is the basic unit of time for charging purposes, e.g.,
	25 cents every 3 minutes – then 3 minutes is the toll
	period. The minimum toll period is 5 seconds.
Session Option:	Use the space bar to toggle this field to Yes and press		Default=
Edit Filter Sets	[Enter] to open Menu 11.5 to edit the filter sets. See the		No
	Remote Node Filter section for more details.
Session Option:	This value specifies the number of idle seconds	Default=300 secs for
Idle Timeout (sec)	that elapses before the remote node is	an unconfigured
	automatically disconnected. Idle seconds is the	remote node. 0 secs
	period of time when no data is transmitted from	means the remote
	your Prestige. Administrative packets such as	node will never be
	RIP are not counted as data. The default is 300	automatically
	seconds (5 minutes). This option only applies	disconnected.
	when the Prestige initiates the call.

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.

5.1.3Outgoing 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

Remote Node Configuration 5-5