Features
540
System functions and features as of R3.0
syd-0367/1.3 – R3.0 – 03.2013
9. 8. 3
Time-controlled functions
Up to 50 (Aastra 470 up to 500) time-controlled functions (*/# function codes) can
be defined in the System Configuration to be executed once at a particular time on
a particular date. It is also possible to define recurring functions to be executed at a
particular time on a particular weekday or every weekday. The */# function codes
can be used for user-specific features or for settings applicable throughout the sys-
tem.
Unlike the control of features or the modification of configurations via the terminal,
time-controlled functions are not subject to the authorisations or to the digit bar-
ring that apply to individual users.
Tab. 363 Examples of time-controlled functions:
Tip:
The function is not carried out if neither an execution date nor a start /
stop range is defined. This allows you to deactivate entries in the table
without having to delete them.
Features and settings can also be activated, deactivated and modified with time
control and in parallel via terminals. Each particular status is event-controlled, i.e.
the last command chronologically determines the current status. The previous sta-
tuses of the functions are not verified. If a function is removed from the table, its
status is also retained.
Note:
Invalid entries in the function column which cannot be executed do not
trigger an error message.
No
.
Function
codes
Start
(Day)
Stop
(Day)
Execution
date
Execution
time
Switch
group
Meaning
1
*0620#21
Monday
Friday
08:00
Deactivate CFU of user 20
2
*0620*2124
Monday
Friday
16:30
CFU from user 20 to user
24
3
#74 854
20.12.2002
22:00
Deactivate control out-
put 854 (e.g. heating)
4
*74 854
06.01.2003
05:30
Activate control output
854 (e.g. heating)
