Difference between revisions of "2-2f. Scheduler - Event Handler (solution)"
From Zenitel Wiki
(→Related articles) |
|||
| (10 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
[[File:2-2f exercise.PNG|left|thumb|500px|System configuration]] | [[File:2-2f exercise.PNG|left|thumb|500px|System configuration]] | ||
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
| − | === | + | === Solution === |
'''Scheduling''': | '''Scheduling''': | ||
| − | * ''At | + | * ''At 15:00 a prerecorded message "We ask passengers not to leave their luggage unattended..." should be distributed to the stations in group 87.'' |
In AlphaWeb, '''System Configuration''' -> '''Messaging''', upload the wav-file using Message group 30, Index 3. This message will get directory number 8193. | In AlphaWeb, '''System Configuration''' -> '''Messaging''', upload the wav-file using Message group 30, Index 3. This message will get directory number 8193. | ||
| − | [[File:2-2f solution1.PNG|thumb|left| | + | [[File:2-2f solution1.PNG|thumb|left|500px|Upload wav file via AlphaWeb]] |
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
| − | In AlphaPro, '''Groups''' -> '''Local Groups''', include | + | In AlphaPro, '''Groups''' -> '''Local Groups''', include 103, 107 and 108 as members of group 4 (87): |
| − | [[File:2-2f solution2.PNG|thumb|left| | + | [[File:2-2f solution2.PNG|thumb|left|500px|Define group members]] |
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
In AlphaPro, '''Exchange & System''' -> '''Events''', '''Insert''' a new event with the following properties: | In AlphaPro, '''Exchange & System''' -> '''Events''', '''Insert''' a new event with the following properties: | ||
| − | [[File:2-2f solution3.PNG|thumb|left| | + | [[File:2-2f solution3.PNG|thumb|left|500px|Use the command $GM to dispatch the message]] |
<br style="clear:both;" /> | <br style="clear:both;" /> | ||
| Line 29: | Line 29: | ||
| − | + | ====Alternative ways of testing the Scheduler==== | |
| − | When testing the scheduler function, the recommended way is to enter a time in the Scheduler event which is a few minutes past the current time, and then wait for the time to | + | '''Alternative 1:''' <br> |
| + | When testing the scheduler function, the recommended way is to enter a time in the Scheduler event which is a few minutes past the current AlphaCom time, and then wait for the set time to arise. | ||
| − | + | '''Alternative 2:''' <br> | |
| + | Adjust the real-time clock in the AlphaCom '''backwards'''. From a [[SuperUser]] dial 785 + New time + M. | ||
| + | |||
| + | '''Alternative 3:''' <br> | ||
| + | If adjusting the real-time clock '''forward''', be aware of the following: | ||
The scheduling has a "catch-up" mechanism which is operational when the time is forward adjusted. During the catch-up period (max 24 minutes) the real-time scheduling events is not executed. This might cause some confusion during testing. | The scheduling has a "catch-up" mechanism which is operational when the time is forward adjusted. During the catch-up period (max 24 minutes) the real-time scheduling events is not executed. This might cause some confusion during testing. | ||
| Line 54: | Line 59: | ||
===Related articles === | ===Related articles === | ||
* [[2-2f. Scheduler - Event Handler (practice)]] | * [[2-2f. Scheduler - Event Handler (practice)]] | ||
| + | |||
| + | [[Category: AlphaCom practice]] | ||
Latest revision as of 10:07, 30 June 2022
Solution
Scheduling:
- At 15:00 a prerecorded message "We ask passengers not to leave their luggage unattended..." should be distributed to the stations in group 87.
In AlphaWeb, System Configuration -> Messaging, upload the wav-file using Message group 30, Index 3. This message will get directory number 8193.
In AlphaPro, Groups -> Local Groups, include 103, 107 and 108 as members of group 4 (87):
In AlphaPro, Exchange & System -> Events, Insert a new event with the following properties:
About the $GM command string $GM L87 L8193 U1 U0 U0
- $GM = The command to dispatch prerecorded message to a group
- L87 = The group
- L8193 = The prerecorded message
- U1 = Play message once, then stop
- U0 = No gong before message
- U0 = Use the priority of the group
Alternative ways of testing the Scheduler
Alternative 1:
When testing the scheduler function, the recommended way is to enter a time in the Scheduler event which is a few minutes past the current AlphaCom time, and then wait for the set time to arise.
Alternative 2:
Adjust the real-time clock in the AlphaCom backwards. From a SuperUser dial 785 + New time + M.
Alternative 3:
If adjusting the real-time clock forward, be aware of the following:
The scheduling has a "catch-up" mechanism which is operational when the time is forward adjusted. During the catch-up period (max 24 minutes) the real-time scheduling events is not executed. This might cause some confusion during testing.
When you need to adjust the time forward for testing of scheduling events, you should do it in this way:
- Set the time and date one week past the scheduling point
- Reset the AMC
- Wait for 3 minutes
- Set the time and date back to 3 minutes before the scheduling point
- Reset the AMC
- Wait for the Scheduling event to trigger on time
In this way you omit the "catch-up" time