Prestige 100 and 100IH ISDN Router and Router/Hub
Telco Options: |
|
|
|
|
Allocated Budget | This field sets a ceiling for outgoing call time for this |
| Default = 0 | |
(min) | remote node. The default for this field is 0 for no budget |
| ||
| control. |
|
| |
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 | 64k/ | ||
| Prestige and this remote node. When set to Leased, the | Leased | ||
| Allocated Budget and Period do not apply. |
| ||
|
|
| ||
This field specifies if you want to make the connection to | Yes/No | |||
| this remote node a |
| ||
| more details. |
|
| |
|
|
|
|
|
Session Option: | Use the space bar to toggle this field to Yes and press |
| Default= No | |
Edit Filter Sets | [Enter] to open Menu 11.5 to edit the filter sets. See the |
| ||
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 RIP |
| node will never be | |
| are not counted as data. The default is 300 |
| automatically | |
| seconds (5 minutes). This option only applies when |
| disconnected. | |
| 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.
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.
Remote Node Configuration |