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

Revision as of 17:31, 6 November 2013

System configuration

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.

Select the Control Room station in the list box, press Events button, and Insert a new event with parameters shown on the screenshot.

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.

Select the Control Room station in the list box, press Events button, and Insert a new event with parameters shown on the screenshot

Program DAK 1 and DAK 2 of the Control Room station with the codes for Call Forwarding on (9533) and Call Forwarding off (9534), 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> and 9534 T <text>.

Verify that:

Call Forwarding is turned on and off
RCO 3 is turned 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 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;" />
 === 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;" />
-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;" />
-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;" />
+[[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
+====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.''
+[[File:2-2d solution6.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 ways of testing the Scheduler====
+====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.''
+[[File:2-2d solution7.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>
+Program DAK 1 and DAK 2 of the Control Room station with the codes for Call Forwarding on (9533) and Call Forwarding off (9534), and add an appropriate display text.
-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>
+[[File:2-2d solution5.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> and 9534 T <text>.]]
-Adjust the real-time clock in the AlphaCom '''backwards'''. From a [[SuperUser]] dial 785 + New time + M.
+<br style="clear:both;" />
-'''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
+'''Verify that:'''
+* Call Forwarding is turned on and off
+* RCO 3 is turned 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).

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

From Zenitel Wiki

Revision as of 17:31, 6 November 2013

Contents

Solution

Call setup:

Set Call Request Forwarding:

Reset Call Request Forwarding:

Related articles