Actions

Difference between revisions of "2-2d. Event Trigger - Event Handler (solution)"

From Zenitel Wiki

(Created page with "{{stub}} left|thumb|500px|System configuration <br style="clear:both;" /> === Solution === '''Scheduling''': * ''At 15:00 a prerecorded message "We as...")
 
Line 4: Line 4:
 
=== Solution ===
 
=== Solution ===
  
−
'''Scheduling''':
+
'''Call setup:'''
−
* ''At 15:00 a prerecorded message "We ask passengers not to leave their luggage unattended..." should be distributed to the stations in group 87.''
+
''* The Entrance and the SOS Point should be configured to make a Call Request (623 + 101) to the Control Room.''
  
−
In AlphaWeb, '''System Configuration''' -> '''Messaging''', upload the wav-file using Message group 30, Index 3. This message will get directory number 8193.
+
* 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-2f solution1.PNG|thumb|left|500px|Upload wav file via AlphaWeb]]
 
−
<br style="clear:both;" />
 
  
 +
'''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.
  
−
In AlphaPro, '''Groups''' -> '''Local Groups''', include 103, 107 and 108 as members of group 4 (87):
+
'''Reset Call Request Forwarding:'''
−
[[File:2-2f solution2.PNG|thumb|left|500px|Define group members]]
+
* 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:
−
<br style="clear:both;" />
+
** 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.
  
−
In AlphaPro, '''Exchange & System''' -> '''Events''', '''Insert''' a new event with the following properties:
 
−
[[File:2-2f solution3.PNG|thumb|left|500px|Use the command $GM to dispatch the message]]
 
−
<br style="clear:both;" />
 
  
−
 
−
'''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:''' <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 time, and then wait for the 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.
 
−
 
−
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
 
  
  

Revision as of 16:12, 5 November 2013

System configuration


Solution

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

Retrieved from "https://wiki.zenitel.com/w/index.php?title=2-2d._Event_Trigger_-_Event_Handler_(solution)&oldid=126622"