Prestige
FIELD | DESCRIPTION | EXAMPLE |
|
|
|
Edit ATM Options | Press [SPACE BAR] to select Yes and press [ENTER] to display | No |
| Menu 11.6 – Remote Node ATM Layer Options. |
|
Telco Option | This sets a ceiling for outgoing call time for this remote node. The | 0 |
Allocated Budget | default for this field is 0 meaning no budget control. | (default) |
|
| |
(min) |
|
|
|
|
|
Period (hr) | This field is the time period that the budget should be reset. For | 0 |
| example, if we are allowed to call this remote node for a maximum | (default) |
| of 10 minutes every hour, then the Allocated Budget is (10 |
|
| minutes) and the Period (hr) is 1 (hour). |
|
Schedule Sets | This field is only applicable for PPPoE encapsulation. You can |
|
| apply up to four schedule sets here. For more details please refer |
|
| to the Call Schedule Setup chapter. |
|
|
|
|
Nailed up | This field is only applicable for PPPoE encapsulation. This field | No |
Connection | specifies if you want to make the connection to this remote node a |
|
|
| |
| section. |
|
Session Options | Use [SPACE BAR] to choose Yes and press [ENTER] to open | No |
Edit Filter Sets | menu 11.5 to edit the filter sets. See the Remote Node Filter | (default) |
section for more details. |
| |
|
| |
Idle Timeout (sec) | Type the number of seconds | 0 |
| Prestige is idle (there is no traffic going to the remote node), | (default) |
| before the Prestige automatically disconnects the remote node. 0 |
|
| means that the session will not timeout. |
|
When you have completed this menu, press [ENTER] at the prompt “Press ENTER to confirm or ESC to cancel” to save your configuration or press [ESC] to cancel and go back to the previous screen.
4.1.3 Outgoing Authentication Protocol
For obvious reasons, you should employ the strongest authentication protocol possible. However, some vendors’ 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 the peer disconnects right after a successful authentication, make sure that you specify the correct authentication protocol when connecting to such an implementation.
Remote Node Configuration |