Actions

Difference between revisions of "2-2e. Event Trigger - Event Handler (practice)"

From Zenitel Wiki

Line 1: Line 1:
{{stub}}
+
[[File:2-2d exercise.PNG|left|thumb|500px|System configuration]]
 +
<br style="clear:both;" />
 +
=== Exercise ===
  
EX1: Set RCO, transfer and send to LOG.
+
'''Exercise goal:''' Learn how to use the Event Trigger as a toggle feature to execute multiple actions in the AlphaCom. Learn about UDD's and IF statement.
  
EX2: Toggle event. Toggle RCO and Transfer ON/OFF by same DAK key.
+
'''Call setup:'''
 +
* The Entrance and the SOS Point should be configured to make a Call Request (623 + 101) to the Control Room.
 +
* The Control Room should be configured as a CRM (Control Room Master), the DAK display should be enabled, and the Navigation Keys should be used for call queue navigations.
  
[[File:2-2e exercise.PNG|left|thumb|500px|System configuration]]
+
'''Set Call Request Forwarding:'''
<br style="clear:both;" />
+
* When dialing the event trigger number 9533, or when pressing a DAK key programmed to 9533 on the Control Room station, the following features should be activated:
=== Exercise ===
+
** Turn on Call Request Forwarding from Control Room station 101 to station 103 (M. Larsen), so that all new call requests will be forwarded to station 103. Use the command "$SCRT" for this.
 +
** Turn on a lamp (use RCO 3) to signal that call forwarding is active
 +
** Write to the System LOG that the call forwarding has been activated. Use the LOG "..." statement.
  
'''Scheduling''':
+
'''Reset Call Request Forwarding:'''
* At 15:00 a prerecorded message "We ask passengers not to leave their luggage unattended..." should be distributed to the stations in group 87.
+
* When dialing the event trigger number 9534, or when pressing a DAK key programmed to 9534 on the Control Room station, the following features should be activated:
 +
** Turn off Call Request Forwarding for Control Room station 101. Use the command "$SCRT" for this.
 +
** Turn off the lamp (RCO 3) to signal that call forwarding is no longer active
 +
** Write to the System LOG that the call forwarding has been turned off. Use the LOG "..." statement.
  
  
Tip:
 
* Use AlphaWeb to upload a wav-file as alarm message 3, dir no 8193 (wav file is found on the memory stick)
 
* Use the $GM command to dispatch the message
 
  
  

Revision as of 17:24, 6 November 2013

System configuration


Exercise

Exercise goal: Learn how to use the Event Trigger as a toggle feature to execute multiple actions in the AlphaCom. Learn about UDD's and IF statement.

Call setup:

  • The Entrance and the SOS Point should be configured to make a Call Request (623 + 101) to the Control Room.
  • The Control Room should be configured as a CRM (Control Room Master), the DAK display should be enabled, and the Navigation Keys should be used for call queue navigations.

Set Call Request Forwarding:

  • When dialing the event trigger number 9533, or when pressing a DAK key programmed to 9533 on the Control Room station, the following features should be activated:
    • Turn on Call Request Forwarding from Control Room station 101 to station 103 (M. Larsen), so that all new call requests will be forwarded to station 103. Use the command "$SCRT" for this.
    • Turn on a lamp (use RCO 3) to signal that call forwarding is active
    • Write to the System LOG that the call forwarding has been activated. Use the LOG "..." statement.

Reset Call Request Forwarding:

  • When dialing the event trigger number 9534, or when pressing a DAK key programmed to 9534 on the Control Room station, the following features should be activated:
    • Turn off Call Request Forwarding for Control Room station 101. Use the command "$SCRT" for this.
    • Turn off the lamp (RCO 3) to signal that call forwarding is no longer active
    • Write to the System LOG that the call forwarding has been turned off. Use the LOG "..." statement.








Related articles