Page 236 / 285 Scroll up to view Page 231 - 235
20-2
Call Scheduling
Lower numbered sets take precedence over higher numbered sets thereby avoiding scheduling conflicts.
For example, if sets 1, 2, 3 and 4 in are applied in the remote node then set 1 will take precedence over set
2, 3 and 4 as the Prestige, by default, applies the lowest numbered set first. Set 2 will take precedence over
set 3 and 4, and so on.
You can design up to 12 schedule sets but you can only apply up to four schedule sets for a remote node.
To delete a schedule set, enter the set number and press the [SPACE BAR] in the
Edit Name
field.
20.3 Schedule Set Setup
To setup a schedule set, select the schedule set you want to setup from menu 26 (1-12), press
[ENTER]
and
then type in a name for the set. Press
[ENTER]
to display
Menu 26.1 - Schedule Set Setup
as shown next.
Figure 20-2 Schedule Set Setup
If a connection has been already established, your Prestige will not drop it. Once the connection is dropped
manually or it times out, then that remote node can't be triggered again until the time period configured in
the
Duration
field expires.
Menu 26.1 - Schedule Set Setup
Active= Yes
Start Date(yyyy/mm/dd) = 2000 – 01 - 01
How Often= Once
Once:
Date(yyyy/mm/dd)= 2000 – 01 - 01
Weekdays:
Sunday= N/A
Monday= N/A
Tuesday= N/A
Wednesday= N/A
Thursday= N/A
Friday= N/A
Saturday= N/A
Start Time (hh:mm)= 00 : 00
Duration (hh:mm)= 00 : 00
Action= Forced On
Press ENTER to Confirm or ESC to Cancel:
Page 237 / 285
Call Scheduling
20-3
Table 20-1 Schedule Set Setup Fields
FIELD
DESCRIPTION
EXAMPLE
Active
Choose
Yes
to activate and
No
to deactivate the schedule set.
Yes
(default)
Start Date
Enter the start date that you wish the set to take effect in year -
month-day format. Valid dates are from the present to February 5,
2036.
2000 – 07 – 01
How Often
Should this schedule set recur weekly or be used just once? Choose
Once
or
Weekly
. Both these options are mutually exclusive. If
Once
is selected, then all weekday settings are
N/A
. When
Once
is
selected, the schedule rule deletes automatically after the scheduled
time elapses.
Once
(default)
Once:
Date
If you select
Once
in the
How Often
field above, enter the date the
set should activate in year-month-day format.
If you select
Weekly
in the
How Often
field above, this field is
N/A
.
2001 – 01 – 01
Weekday:
Day
If you select
Weekly
in the
How Often
field above, then choose the
day(s) the set should activate (and recur). Individual
Day
parameters are active when their fields read
Yes
and inactive when
their fields read
No
or
N/A
.
N/A
(default)
Start Time
Enter the start time that you wish the schedule set to take effect in
hour : minute format.
12 : 00
Duration
Enter the maximum duration allowed in hour : minute format for this
scheduled connection.
10 : 00
Action
Choose an action. Choices are:
Forced On
means that the connection is maintained whether or not
there is a demand call on the line and will persist for the time period
specified in the
Duration
field.
Forced Down
means that the connection is blocked whether or not
there is a demand call on the line.
Enable Dial-On-Demand
means that this schedule permits a
demand call on the line.
Disable Dial-On-Demand
means that this schedule prevents a
demand call on the line.
Forced On
Page 238 / 285
20-4
Call Scheduling
20.4 Applying Schedule Sets to Remote Nodes
Once your schedule sets are configured, you must apply them to the desired remote node(s). Enter 11 from
the main menu and, using the
[SPACE BAR]
, select
PPPoE
or
PPTP
in the
Encapsulation
field. Enter
your target remote node index number(s) in the
Schedules
field, as shown next.
Figure 20-3 Applying Schedule Sets to a Remote Node Example (PPPoE Encapsulation)
You can apply up to four schedule sets, separated by commas, for one remote node. Enter the schedule set
numbers for specific remote nodes in the
Schedules
field. In the examples, shown previously and next,
schedule sets 1, 3 and 4 are applied.
Menu 11.1 - Remote Node Profile
Rem Node Name= ChangeMe
Active= Yes
Encapsulation= PPPoE
Service Type= Standard
Service Name=
Outgoing:
Rem Login=
Rem Password= ********
Authen= CHAP/PAP
PPTP:
My IP Addr=
Server IP Addr=
Connection ID/Name=
Route= IP
Edit IP= No
Telco Option:
Allocated Budget(min)= 0
Period (hr)= 0
Schedules= 1,3,4
Nailed-Up Connection= No
Session Options:
Edit Filter Sets= No
Idle Timeout(sec)= 300
Press ENTER to Confirm or ESC to Cancel:
Page 239 / 285
Call Scheduling
20-5
Figure 20-4 Applying Schedule Sets to a Remote Node Example (PPTP Encapsulation)
Menu 11.1 - Remote Node Profile
Rem Node Name= ChangeMe
Active= Yes
Encapsulation= PPTP
Service Type= Standard
Service Name=
Outgoing:
Rem Login=
Rem Password= ********
Athen= CHAP/PAP
PPTP:
My IP Addr=
Server IP Addr=
Connection ID/Name=
Authen= CHAP/PAP
Route= IP
Edit IP= No
Telco Option:
Allocated Budget(min)= 0
Period (hr)= 0
Schedules= 1,3,4
Nailed-Up Connection= 0
Session Options:
Edit Filter Sets= No
Idle Timeout(sec)= 100
Press ENTER to Confirm or ESC to Cancel:
Page 240 / 285

Rate

4 / 5 based on 1 vote.

Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top