Actions

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

From Zenitel Wiki
(→‎Related articles)
 
(10 intermediate revisions by one other user not shown)
Line 1: Line 1:
−
{{stub}}
+
[[File:2-2d exercise.PNG|left|thumb|500px|System configuration]]
−
[[File:2-2e exercise.PNG|left|thumb|500px|System configuration]]
 
 
<br style="clear:both;" />
 
<br style="clear:both;" />
 
=== 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.
+
[[File:2-2d solution1.PNG|left|thumb|500px|Select the '''Entrance''' station in the list box, press '''DAK''' button, and enter "'''I 623 I 101'''" on  DAK 1. Do the same for the '''SOS Point''' station.]]
−
[[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 103, 107 and 108 as members of group 4 (87):
+
* ''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 solution2.PNG|thumb|left|500px|Define group members]]
+
 
 +
[[File:2-2d solution2.PNG|left|thumb|500px|Select the '''Control Room''' station in the list box, and set "Station Type" = '''CRM'''.]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
  
−
In AlphaPro, '''Exchange & System''' -> '''Events''', '''Insert''' a new event with the following properties:
+
[[File:2-2d solution3.PNG|left|thumb|500px|Select the '''Control Room''' station in the list box, select the "'''Station Type'''" tab, and enable the "'''Station use DAK Display'''" flag.]]
−
[[File:2-2f solution3.PNG|thumb|left|500px|Use the command $GM to dispatch the message]]
 
 
<br style="clear:both;" />
 
<br style="clear:both;" />
  
 +
[[File:2-2d solution4.PNG|left|thumb|500px|Select the '''Control Room''' station in the list box, press '''DAK''' button, select the "'''Navig.keys'''" tab, and enter 7638 (Answer), 7639 (Next), 7632 (Top) and 7630 (Cancel)]]
 +
<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
 
  
 +
====Toggle 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 toggled ON/OFF every time the number is activated:''
 +
** ''Turn on/off 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/off a lamp (use RCO 3) to signal that call forwarding is active''
 +
** ''Write to the System LOG that the call forwarding has been activated/turned off. Use the LOG "..." statement.''
  
−
====Alternative ways of testing the Scheduler====
+
[[File:2-2e solution1.PNG|left|thumb|500px|Select the '''Control Room''' station in the list box, press '''Events''' button, and '''Insert''' a new event with parameters shown on the screenshot.]]
 +
<br style="clear:both;" />
  
−
'''Alternative 1:''' <br>
+
The full action string is:
−
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.
+
IF %udd(1)                                          If Call Forwarding is active (UDD 1 different from 0")
 +
$SCRT L101                                          Turn off Call Forwarding at 101
 +
RCO 3 OFF                                            Turn off RCO 3
 +
LOG "Control Room: Call Forwarding turned off"      Send info to System log
 +
WUDD 1 0                                            Set new status = Call Forwarding not active (UDD 1 = 0)
 +
STOP                                                Don't execute the rest of the actions
 +
ENDIF                                                If Call Forwarding is not active (UDD 1 = 0)
 +
$SCRT L101 L103                                      Turn on Call Forwarding at 101
 +
RCO 3 ON                                            Turn on RCO 3
 +
LOG "Control Room: Call Forwarding active"          Send info to System log
 +
WUDD 1 1                                            Set new status = Call Forwarding active (UDD 1 = 1)
  
−
'''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:
+
Program DAK 1 of the Control Room station with the code for Call Forwarding on/off (9533), and add an appropriate display text.
−
*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
+
[[File:2-2e solution2.PNG|left|thumb|500px|Select the '''Control Room''' station in the list box, press '''DAK''' button, select the "'''DAK 1-10'''" tab, and on DAK key 1 and 2 enter 9533 T <text>.]]
 +
<br style="clear:both;" />
  
 +
 +
 +
'''Verify that:'''
 +
* Call Forwarding is toggled on and off
 +
* RCO 3 is toggled on and off
 +
* The Call forwarding on/off is logged in the "System Log" (AlphaWeb: System Monitoring -> Logging. It might be that logging has to be enabled first: System Configuration -> Logging).
  
  
Line 60: Line 65:
 
===Related articles ===
 
===Related articles ===
 
* [[2-2e. Event Trigger - Event Handler (practice)]]
 
* [[2-2e. Event Trigger - Event Handler (practice)]]
 +
 +
[[Category: AlphaCom practice]]

Latest revision as of 10:07, 30 June 2022

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.
Select the Entrance station in the list box, press DAK button, and enter "I 623 I 101" on DAK 1. Do the same for the SOS Point station.



  • 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.
Select the Control Room station in the list box, and set "Station Type" = CRM.


Select the Control Room station in the list box, select the "Station Type" tab, and enable the "Station use DAK Display" flag.


Select the Control Room station in the list box, press DAK button, select the "Navig.keys" tab, and enter 7638 (Answer), 7639 (Next), 7632 (Top) and 7630 (Cancel)



Toggle 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 toggled ON/OFF every time the number is activated:
    • Turn on/off 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/off a lamp (use RCO 3) to signal that call forwarding is active
    • Write to the System LOG that the call forwarding has been activated/turned off. Use the LOG "..." statement.
Select the Control Room station in the list box, press Events button, and Insert a new event with parameters shown on the screenshot.


The full action string is: 

IF %udd(1)                                           If Call Forwarding is active (UDD 1 different from 0")
$SCRT L101                                           Turn off Call Forwarding at 101
RCO 3 OFF                                            Turn off RCO 3
LOG "Control Room: Call Forwarding turned off"       Send info to System log 
WUDD 1 0                                             Set new status = Call Forwarding not active (UDD 1 = 0)
STOP                                                 Don't execute the rest of the actions
ENDIF                                                If Call Forwarding is not active (UDD 1 = 0)
$SCRT L101 L103                                      Turn on Call Forwarding at 101
RCO 3 ON                                             Turn on RCO 3
LOG "Control Room: Call Forwarding active"           Send info to System log
WUDD 1 1                                             Set new status = Call Forwarding active (UDD 1 = 1)


Program DAK 1 of the Control Room station with the code for Call Forwarding on/off (9533), and add an appropriate display text.

Select the Control Room station in the list box, press DAK button, select the "DAK 1-10" tab, and on DAK key 1 and 2 enter 9533 T <text>.



Verify that:

  • Call Forwarding is toggled on and off
  • RCO 3 is toggled on and off
  • The Call forwarding on/off is logged in the "System Log" (AlphaWeb: System Monitoring -> Logging. It might be that logging has to be enabled first: System Configuration -> Logging).






Related articles

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