Actions

Difference between revisions of "Silent Alarm"

From Zenitel Wiki

(→‎Configure User Defined Properties - UDP)
(→‎Answer event)
 
(36 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
This application is intended for e.g. public offices which handles clients that can become threatening.  As client handling is confidential, each employee sits alone in his/her office, and a possible attack will not be noticed by co-workers.
+
{{AI}}
−
Each office is equipped with an intercom station, plus an alarm button. When the alarm button is pressed, a special group call with a characteristic ding-dong sequence is broadcast to neighboring offices, and all station displays shows “8123 Alarm XXXXX”. 
+
<table style="float:right; max-width:80%; border-style: double; border-color: #c7c7c7;">
−
The neighboring offices can then select to listen in to the alarm room by dialing the displayed directory number “8123”.  It’s possible to simulate an innocent conversation by pressing the M-key and saying “XXXX, do you have the file for client YYYY” and thus make the threatening client understand that he is not alone.
+
<tr style="rowspan:2;">
−
When the situation is under control, the alarm station can terminate the alarm conference.
+
<td style="display: block; vertical-align: bottom;">[[Image:Silent Al Diagram.PNG|400px]]</td>
 +
</tr>
 +
<tr>
 +
<td style='background-color:#efefef;'>Silent Alarm - principle diagram</td>
 +
</tr>
 +
</table>
 +
This article describes how to configure a '''Silent Alarm''' feature in an ICX-AlphaCom (or AlphaCom XE) system.
  
−
==Configuration of the exchange==
+
The Silent Alarm application can typically be used in:
−
===Exchange features used===
+
* Social security offices
−
*Alarm key: Use a substation “id” pulse which the exchange handles as DAK1. The DAK is programmed with dir.no 9534: “Event Trigger - Without Tone”.
+
* Correctional facilities
−
*Event Trigger causes event “User defined” on the alarm station.
+
* Mental hospitals
−
*Actions:
 
−
**Group call with special gong to group of neighbors. (The group is set up using a dummy station as A-subscriber.)
 
−
**Simplex conference to neighboring group. (To give display info along with the special gong.)One conference is used for all alarms. The name text is modified to indicate dial-back dir. no and alarm source.
 
−
*The dial-back feature is a dedicated simplex conference per alarm point. There are 50 simplex conferences, i.e. max 49 offices can have Silent Alarm. The alarm conference has the name of the alarm station, and the alarm station is default member and default speaker. As soon as one neighbor responds by dialing the displayed alarm number, the conference is fed from the alarm office’s microphone. The alarm office’s station display changes, which tells the threatened employee that someone is now listening and help is under way.
 
−
*To cancel an alarm, a DAK programmed with remote cancel of conference is used.
 
−
*To avoid eavesdropping via the alarm conference (default member/speaker), you can operate the system with conferences non-accessible via COS. The UserDefined alarm start-up action then moves simplex conference into COS1, and the corresponding conference cancel action moves conference out of COS1.  In/out of COS 1 uses the feature “Toggle COS1”.
 
  
−
===Configuration in AlphaPro===
+
An example application is public offices which handle clients that can become threatening.  As client handling is confidential, each employee sits alone in his/her office, and a possible attack will not be noticed by co-workers.
−
There are two pieces of information that must be organized per station:
+
Each office is equipped with an intercom station, plus an alarm button. When the alarm button is pressed, a special tone signal is heard in neighboring offices, and the these stations will display the alarm senders location, and they can activate a listen-in function.
−
*Which group to use to alarm neighbors
 
−
*Which conference to use for each alarm point
 
−
Example:
 
−
Station 123, Neighbor group 891, Alarm ding-dong group dummy station 199.
 
−
Action for the Userdefined event that starts the whole thing:
 
−
$DD L199 L891..............group call ding-dong…
 
−
$CONF  L891 L8223 U2..........display alarm source and dir. no
 
−
It’s possible to “hard-code” this information per station, as max 49 stations can have this functionality.
 
−
Alternatively, to ease configuration if say more than 10 stations is used, the AlphaCom's External Feature mechanism can be used. Then we must have some regularity in the number plan:
 
−
*E.g. using 3 digit station numbers 101-149
 
−
*Corresponding alarm conferences 8201 to 8249 (two last digits identical). 
 
−
*Use two Event Trigger dir. no's, e.g. 9501 for activate and 9502 for terminate.
 
−
*Use station 199 as dummy station for the initial ding-dong group call
 
−
*Use conference 8250 as the alarm display conference
 
  
−
===Configure User Defined Properties - UDP===
+
==General operation ==
−
*Set up the UDP names once; “Silent Alarm”.
+
[[File:Silent Al Display.PNG|right|300px]]
−
The UDP is a user-defined mechanism, which is referenced by the Event Handler only. You define what each UDP is used for, and give it a suitable name. Note that the UDP names are common for all stations, even if you can change it when entering the screen from one station.
+
* The silent alarm is triggered by pressing an alarm button associated to an Alarm Sender intercom.
−
*For each station that can set up an alarm, set the correct UDP checkbox.
+
* Alarm Receiver intercoms will play a special tone signal, and display the alarm senders location.  
−
Also, enter the neighbor group dir. no under “User Defined Parameter (%1.EXP)”.
+
* The Alarm Receiver can then press an "Answ" button. The microphone at the Alarm Sender intercom will then silently be activated, and the Alarm Receiver can listen in. The call LED or back light at the Alarm Sender will not turn on.
−
<br/>
+
* Multiple Alarm Receiver intercoms can listen-in to the same Alarm Sender
−
[[Image:AppSiAl 2.PNG]]
+
* Talkback to the Alarm Sender is possible by pressing the "M-key"
 +
* In case of multiple simultaneous alarms, the alarms will be queued at the Alarm Receiver intercom. The operator can scroll in the queue using "Next" and "Top" buttons, and select which one to listen to. Listen-in will automatically be activated when scrolling to a new alarm sender
 +
* When the situation is under control, the Alarm Receiver station clears his alarm by pressing the "Canc" button.
  
−
===Configure Event Handler===
+
<br>
−
Now we can use the Event handler’s ability to handle many stations with one line of event code.
+
 
−
*Enter Event Handling via the System screen. Now you can program for all stations in the exchange.
+
== Alarm Senders ==
−
*Alarm activation:
+
There can be up to 100 Alarm Sender intercoms in one system. The alarm sender can be any Zenitel IP device, typically a
−
Create one event, owned by “all alarm stations”, related-to the activate dir. no 9501, doing an action which refers to the actual station’s directory numbers.
+
* Desktop intercom,
−
The common action looks like this:
+
* A Turbine intercom station, or
−
  $DD L199 L%1.exp
+
* A VoIP kit with microphone and alarm button attached
−
  $SDT L8250 ‘82%1.dir(2) Alarm %1.nam()’
+
 
−
  $CONF L%1.exp L8250 U2
+
The [[Sound Detection]] feature can also be used to trigger the Silent Alarm.
−
*Alarm termination:
+
 
−
Create one event, owned by “all alarm stations”, related-to the terminate dir. no 9502, doing an action which refers to the actual station’s directory numbers.
+
SIP devices, such as ITSV phones, cannot be used.
−
The common action looks like this:
+
 
−
  $PROG_CONF L%1.exp L82%1.dir(2) U2
+
Configuration steps:
−
Parameters are:
+
# The directory numbers of the alarm sender intercoms must be in a specific range
−
  %1.EXP.........gets the active station’s Ext. Feature parameter, e.g. 891
+
# Each Alarm Sender intercom must be configured as a Default Speaker in a Simplex Conference
−
  %1.DIR(2)......gets the 2 last digits of the active station’s directory number, e.g. 23 from 123.
+
# The Alarm Sender intercoms should be member of UDP Group 1. Each Alarm Sender must be linked to a station group, defining who should receive alarm from this Alarm Sender
−
  %1.NAM().......gets the active station’s name
+
# Configure the Alarm Button
−
[[Image:AppSiAl 1.PNG]]
+
 
 +
 
 +
An "Alarm Sender" may at the same time be an "Alarm Receiver".
 +
 
 +
=== Directory numbers of the alarm sender intercoms===
 +
There must be a certain relation between the directory numbers of the Alarm Sender intercoms and the directory numbers of the Simplex Conference used by the Alarm Sender. The '''last two digits''' must be identical. The directory numbers of the alarm sender intercoms must be in the range 301 - 399. (other number range might be used, but the configuration below assumes that this number range is used).
 +
<table style='width:20%;'>
 +
  <tr style='background-color:#ffd400'>
 +
    <td style='border:1px solid; font-weight:bold'>Alarm Sender</td>
 +
    <td style='border:1px solid; text-align:left;font-weight:bold'>Simplex Conf.</td>
 +
  </tr>
 +
  <tr>
 +
    <td style='border:1px solid; text-align:center;'>3<u>01</u></td>
 +
    <td style='border:1px solid; text-align:center;'>Conf. 1, 82<u>01</u></td>
 +
  </tr>
 +
<tr>
 +
    <td style='border:1px solid; text-align:center;'>3<u>02</u></td>
 +
    <td style='border:1px solid; text-align:center;'>Conf. 2, 82<u>02</u></td>
 +
  </tr>
 +
<tr>
 +
    <td style='border:1px solid; text-align:center;'>3<u>03</u></td>
 +
    <td style='border:1px solid; text-align:center;'>Conf. 3, 82<u>03</u></td>
 +
  </tr>
 +
<tr>
 +
    <td style='border:1px solid; text-align:center;'>3<u>04</u></td>
 +
    <td style='border:1px solid; text-align:center;'>Conf. 4, 82<u>04</u></td>
 +
  </tr>
 +
</table>
 +
 
 +
 
 +
Enter directory number 3xx for each of the alarm sender intercoms:
 +
<table style="max-width:80%; border-style: double; width:500px; border-color: #c7c7c7;">
 +
<tr style="rowspan:2;">
 +
<td style="display: block; vertical-align: bottom;">[[Image:Alarm Sender Dirno.PNG]]</td>
 +
</tr>
 +
<tr>
 +
<td >Alarm Sender directory numbers</td>
 +
</tr>
 +
</table>
 +
 
 +
=== Simplex Conference configuration ===
 +
Configure an Alarm Sender as a Default Speaker in a Simplex Conference:
 +
<table style="max-width:80%; border-style: double; width:700px; border-color: #c7c7c7;">
 +
<tr style="rowspan:2;">
 +
<td style="display: block; vertical-align: bottom;">[[Image:Alarm Senders SX Conf.PNG]]</td>
 +
</tr>
 +
<tr>
 +
<td >Alarm Sender as Default Speaker in conference</td>
 +
</tr>
 +
</table>
 +
 
 +
This must be done for each Alarm Sender station.
 +
 
 +
 
 +
The name of the conference will show up in the display of the alarm receivers, hence the conference name should indicate the alarm location:
 +
 
 +
<table style="max-width:80%; border-style: double; width:700px; border-color: #c7c7c7;">
 +
<tr style="rowspan:2;">
 +
<td style="display: block; vertical-align: bottom;">[[Image:SX Conf Names.PNG]]</td>
 +
</tr>
 +
<tr>
 +
<td >The conference name is used to show the alarm location</td>
 +
</tr>
 +
</table>
 +
 
 +
=== UDP Group and Alarm Receiving Group===
 +
Include all Alarm Senders in UDP Group 1, and define in the %1.EXP field the alarm receiver group. The same alarm receiver group can be used by several Alarm Senders.
 +
<table style="max-width:80%; border-style: double; width:700px; border-color: #c7c7c7;">
 +
<tr style="rowspan:2;">
 +
<td style="display: block; vertical-align: bottom;">[[Image:Silent Al UDP1.PNG]]</td>
 +
</tr>
 +
<tr>
 +
<td >Set UDP 1 membership, and define which group to receive alarms from this alarm sender</td>
 +
</tr>
 +
</table>
 +
 
 +
===Configure the Alarm Button===
 +
Configure the Alarm Button to dial event trigger number 9534 (feature 52). The number 9534 is included in a default database. Add the letter "E" in front of the number. That will ensure alarm triggering even if the alarm sender intercom is busy in a call.
 +
<table style="max-width:80%; border-style: double; width:700px; border-color: #c7c7c7;">
 +
<tr style="rowspan:2;">
 +
<td style="display: block; vertical-align: bottom;">[[Image:Silent Al DAK.PNG]]</td>
 +
</tr>
 +
<tr>
 +
<td >Alarm Button = E9534</td>
 +
</tr>
 +
</table>
 +
 
 +
If the Alarm Sender is a Desktop station, and there is a need for an external alarm button, one can use an input of a TKIS-2 kit, and use the [[DIAL DAK|$DIAL_DAK command]] to simulate DAK press on the Desktop station. E.g. if a Desktop station with number 302 has "E9534" configured on DAK 1, one can trigger this DAK by the command ''$DIAL_DAK L302 U1''.
 +
 
 +
<br>
 +
 
 +
== Alarm Receivers ==
 +
The alarm Receiver intercom must be a Zenitel IP station with display. Either
 +
* Desktop intercom, or
 +
* IP Flush Master
 +
 
 +
SIP devices, such as ITSV phones, cannot be used.
 +
 
 +
=== Directory numbers and Station Type ===
 +
The Alarm Receiver stations can use any directory number. Correct display behavior is enabled by setting the Station Type to "'''CRM'''":
 +
 
 +
<table style="max-width:80%; border-style: double; width:700px; border-color: #c7c7c7;">
 +
<tr style="rowspan:2;">
 +
<td style="display: block; vertical-align: bottom;">[[Image:Silent Al CRM.PNG]]</td>
 +
</tr>
 +
<tr>
 +
<td >Set "Station Type" to '''CRM'''</td>
 +
</tr>
 +
</table>
 +
 
 +
=== Navigation Buttons ===
 +
When setting the station type to "CRM" the navigation buttons are automatically configured. Two of the default numbers needs to be changed. Enter number 9538 on the first button, and 9533 on the last button.
 +
* 9538 will be the "Answer" button
 +
* 9533 will be the "Cancel" button
 +
 
 +
The entries on line 2 (7639) and line 3 (7632) must remain.
 +
 
 +
<table style="max-width:80%; border-style: double; width:700px; border-color: #c7c7c7;">
 +
<tr style="rowspan:2;">
 +
<td style="display: block; vertical-align: bottom;">[[Image:Silent Al Navig.PNG]]</td>
 +
</tr>
 +
<tr>
 +
<td >Modifying the Navigation Buttons</td>
 +
</tr>
 +
</table>
 +
 
 +
 
 +
The number 9533 (feature 85) is included in a default database, but number 9538 has to be added to the database. In AlphaPro, select '''Directory & Features''', and '''Insert''' a new number:
 +
* Feature: 85
 +
* Directory number: 9538
 +
* Display Text: "Answer Alarm"
 +
 
 +
<table style="max-width:80%; border-style: double; width:700px; border-color: #c7c7c7;">
 +
<tr style="rowspan:2;">
 +
<td style="display: block; vertical-align: bottom;">[[Image:Silent Al 9538.PNG]]</td>
 +
</tr>
 +
<tr>
 +
<td >Adding number 9538 to the system</td>
 +
</tr>
 +
</table>
 +
 
 +
=== Membership in Alarm Groups ===
 +
The Alarm Receiver stations must be included in one or more Alarm Groups. In AlphaPro select '''Groups''' > '''Local Groups''', and select the alarm group from the list box. Add Alarm Receivers to the group:
 +
 
 +
<table style="max-width:80%; border-style: double; width:600px; border-color: #c7c7c7;">
 +
<tr style="rowspan:2;">
 +
<td style="display: block; vertical-align: bottom;">[[Image:Silent Al Members.PNG]]</td>
 +
</tr>
 +
<tr>
 +
<td >Adding Alarm Receivers to group 891</td>
 +
</tr>
 +
</table>
 +
 
 +
=== Notification Tone ===
 +
The Alarm Receivers will get a notification tone when an alarm is received. By default this is a 3 times dut-dut-dut-dut tone, repeated every 20 seconds. Often there will be a need to shorten that 20 second pause. See [[Urgent feature reminder]] for more details.
 +
 
 +
<br>
 +
 
 +
== Event Handler configuration ==
 +
 
 +
=== Alarm Button event ===
 +
This event is triggered when an Alarm Sender station is dialing 9534.
 +
[[Image:Silent Al Event Call.PNG|thumb|left|500px|Alarm Button event]]
 +
<br style="clear:both;" />
 +
 
 +
{{code2|
 +
  $SM L82%1.dir(2) L%1.exp U145
 +
  LOG "Alarm from %1.dir %1.nam to Alarm Group %1.exp"
 +
}}
 +
 
 +
 
 +
Explanation:
 +
* When station 3xx dials 9534, Send Mail (Call Request) with the Simplex Conference 82xx as sender, and the alarm group specified in the EXP field as the receiver, using priority 145.
 +
* Send info to the log
 +
 
 +
=== Answer event ===
 +
This event is triggered when the Alarm Receiver dials 9538 (Answer button).
 +
[[Image:Silent Al Event Answer.PNG|thumb|left|500px|Answer event]]
 +
<br style="clear:both;" />
 +
 
 +
{{code2|
 +
WUDD %1.phy 1
 +
  $MAILQ_NAVIG L%1.dir 1
 +
LOG "Alarm answered at %1.dir %1.nam"
 +
}}
 +
 
 +
 
 +
Explanation:
 +
* When an Alarm Receiver dials the "answer" code 9538, set an "answer"-flag (UDD = 1)
 +
* Re-trigger the event "23 - New Current Mail in station queue"
 +
* Send info to the log
 +
 
 +
=== Connect event ===
 +
This event is triggered when the alarm receiver has "answered" the alarm, and there is an alarm in queue.
 +
[[Image:Silent Al Event Connect.PNG|thumb|left|500px|Connect event]]
 +
<br style="clear:both;" />
 +
 
 +
{{Code2|
 +
  IF %udd(%1.phy)
 +
$SC L3%2.dir(2)
 +
$CONF %1.ref %2.ref
 +
  LOG "Audio established from %1.dir %1.nam to %2.dir %2.nam"
 +
$CPYM L%1.dir W%2.TAG L%1.dir U20
 +
$DIP L%1.dir "ind stl 2 0"
 +
$DIP L%1.dir "ind stl 0 1"
 +
ENDIF
 +
}}
 +
 
 +
Explanation:
 +
When the Alarm Receiver gets a new "current mail":
 +
* If the Alarm Receiver has answered/accepted the alarm call...  ("answer"-flag = 1)
 +
* ..enable "Silent Call" function for alarm sender 3xx. This will prevent LED and backlight to be turned on at the Alarm Sender.
 +
* ..turn on the Simplex Conference related to the alarm sender
 +
* ..send info to the log
 +
* ..copy the mail to itself, but with priority 20. This low priority will stop the notification tone
 +
* ..turn off flashing red LED in Alarm Receiver station, and
 +
* ..turn on steady red LED in Alarm Receiver station
 +
 
 +
 
 +
<br>
 +
 
 +
=== Cancel event ===
 +
This event is triggered when the Alarm Receiver dials 9533 (Cancel button).
 +
[[Image:Silent Al Event Cancel.PNG|thumb|left|500px|Cancel event]]
 +
<br style="clear:both;" />
 +
 
 +
{{Code2|
 +
WUDD %1.phy 0
 +
$CONF L%1.dir LV
 +
$CANM LV L%1.dir
 +
$DIP L%1.dir "ind stl 0 0"
 +
  LOG "Alarm cleared at %1.dir %1.nam"
 +
}}
 +
 
 +
Explanation:
 +
When the Alarm Receiver dials 9533 (Cancel button):
 +
* Reset the "answer"-flag (UDD = 0)
 +
* Turn off the Simplex Conference at this staion
 +
* Delete all mails in this station
 +
* Turn off steady red LED in this station
 +
* Send info to the log
 +
 
 +
<br>
 +
 
 +
== Logging ==
 +
With the log events configured above, the log data in the [[System log]] will look like this:
 +
 
 +
Mar 18 15:56:45 AlphaCom1 AlphaLog: N001.D065:.Exch:Alarm from 302 Desk A6 to Alarm Group 891
 +
Mar 18 15:56:51 AlphaCom1 AlphaLog: N001.D065:.Exch:Alarm answered at 109 Operator 4
 +
Mar 18 15:56:51 AlphaCom1 AlphaLog: N001.D065:.Exch:Audio established from 109 Operator 4 to 8202 Desk A6
 +
Mar 18 15:59:56 AlphaCom1 AlphaLog: N001.D065:.Exch:Alarm cleared at 109 Operator 4
 +
 
 +
 
 +
 
 +
 
 +
[[Category:AlphaCom Applications]]
 +
[[Category:ICX-AlphaCom Applications]]

Latest revision as of 16:11, 4 January 2023

AI.png
Silent Al Diagram.PNG
Silent Alarm - principle diagram

This article describes how to configure a Silent Alarm feature in an ICX-AlphaCom (or AlphaCom XE) system.

The Silent Alarm application can typically be used in:

  • Social security offices
  • Correctional facilities
  • Mental hospitals

An example application is public offices which handle clients that can become threatening. As client handling is confidential, each employee sits alone in his/her office, and a possible attack will not be noticed by co-workers. Each office is equipped with an intercom station, plus an alarm button. When the alarm button is pressed, a special tone signal is heard in neighboring offices, and the these stations will display the alarm senders location, and they can activate a listen-in function.

General operation

Silent Al Display.PNG
  • The silent alarm is triggered by pressing an alarm button associated to an Alarm Sender intercom.
  • Alarm Receiver intercoms will play a special tone signal, and display the alarm senders location.
  • The Alarm Receiver can then press an "Answ" button. The microphone at the Alarm Sender intercom will then silently be activated, and the Alarm Receiver can listen in. The call LED or back light at the Alarm Sender will not turn on.
  • Multiple Alarm Receiver intercoms can listen-in to the same Alarm Sender
  • Talkback to the Alarm Sender is possible by pressing the "M-key"
  • In case of multiple simultaneous alarms, the alarms will be queued at the Alarm Receiver intercom. The operator can scroll in the queue using "Next" and "Top" buttons, and select which one to listen to. Listen-in will automatically be activated when scrolling to a new alarm sender
  • When the situation is under control, the Alarm Receiver station clears his alarm by pressing the "Canc" button.


Alarm Senders

There can be up to 100 Alarm Sender intercoms in one system. The alarm sender can be any Zenitel IP device, typically a

  • Desktop intercom,
  • A Turbine intercom station, or
  • A VoIP kit with microphone and alarm button attached

The Sound Detection feature can also be used to trigger the Silent Alarm.

SIP devices, such as ITSV phones, cannot be used.

Configuration steps:

  1. The directory numbers of the alarm sender intercoms must be in a specific range
  2. Each Alarm Sender intercom must be configured as a Default Speaker in a Simplex Conference
  3. The Alarm Sender intercoms should be member of UDP Group 1. Each Alarm Sender must be linked to a station group, defining who should receive alarm from this Alarm Sender
  4. Configure the Alarm Button


An "Alarm Sender" may at the same time be an "Alarm Receiver".

Directory numbers of the alarm sender intercoms

There must be a certain relation between the directory numbers of the Alarm Sender intercoms and the directory numbers of the Simplex Conference used by the Alarm Sender. The last two digits must be identical. The directory numbers of the alarm sender intercoms must be in the range 301 - 399. (other number range might be used, but the configuration below assumes that this number range is used).

Alarm Sender Simplex Conf.
301 Conf. 1, 8201
302 Conf. 2, 8202
303 Conf. 3, 8203
304 Conf. 4, 8204


Enter directory number 3xx for each of the alarm sender intercoms:

Alarm Sender Dirno.PNG
Alarm Sender directory numbers

Simplex Conference configuration

Configure an Alarm Sender as a Default Speaker in a Simplex Conference:

Alarm Senders SX Conf.PNG
Alarm Sender as Default Speaker in conference

This must be done for each Alarm Sender station.


The name of the conference will show up in the display of the alarm receivers, hence the conference name should indicate the alarm location:

SX Conf Names.PNG
The conference name is used to show the alarm location

UDP Group and Alarm Receiving Group

Include all Alarm Senders in UDP Group 1, and define in the %1.EXP field the alarm receiver group. The same alarm receiver group can be used by several Alarm Senders.

Silent Al UDP1.PNG
Set UDP 1 membership, and define which group to receive alarms from this alarm sender

Configure the Alarm Button

Configure the Alarm Button to dial event trigger number 9534 (feature 52). The number 9534 is included in a default database. Add the letter "E" in front of the number. That will ensure alarm triggering even if the alarm sender intercom is busy in a call.

Silent Al DAK.PNG
Alarm Button = E9534

If the Alarm Sender is a Desktop station, and there is a need for an external alarm button, one can use an input of a TKIS-2 kit, and use the $DIAL_DAK command to simulate DAK press on the Desktop station. E.g. if a Desktop station with number 302 has "E9534" configured on DAK 1, one can trigger this DAK by the command $DIAL_DAK L302 U1.


Alarm Receivers

The alarm Receiver intercom must be a Zenitel IP station with display. Either

  • Desktop intercom, or
  • IP Flush Master

SIP devices, such as ITSV phones, cannot be used.

Directory numbers and Station Type

The Alarm Receiver stations can use any directory number. Correct display behavior is enabled by setting the Station Type to "CRM":

Silent Al CRM.PNG
Set "Station Type" to CRM

Navigation Buttons

When setting the station type to "CRM" the navigation buttons are automatically configured. Two of the default numbers needs to be changed. Enter number 9538 on the first button, and 9533 on the last button.

  • 9538 will be the "Answer" button
  • 9533 will be the "Cancel" button

The entries on line 2 (7639) and line 3 (7632) must remain.

Silent Al Navig.PNG
Modifying the Navigation Buttons


The number 9533 (feature 85) is included in a default database, but number 9538 has to be added to the database. In AlphaPro, select Directory & Features, and Insert a new number:

  • Feature: 85
  • Directory number: 9538
  • Display Text: "Answer Alarm"
Silent Al 9538.PNG
Adding number 9538 to the system

Membership in Alarm Groups

The Alarm Receiver stations must be included in one or more Alarm Groups. In AlphaPro select Groups > Local Groups, and select the alarm group from the list box. Add Alarm Receivers to the group:

Silent Al Members.PNG
Adding Alarm Receivers to group 891

Notification Tone

The Alarm Receivers will get a notification tone when an alarm is received. By default this is a 3 times dut-dut-dut-dut tone, repeated every 20 seconds. Often there will be a need to shorten that 20 second pause. See Urgent feature reminder for more details.


Event Handler configuration

Alarm Button event

This event is triggered when an Alarm Sender station is dialing 9534.

Alarm Button event


Action commands: 

$SM L82%1.dir(2) L%1.exp U145
LOG "Alarm from %1.dir %1.nam to Alarm Group %1.exp"



Explanation:

  • When station 3xx dials 9534, Send Mail (Call Request) with the Simplex Conference 82xx as sender, and the alarm group specified in the EXP field as the receiver, using priority 145.
  • Send info to the log

Answer event

This event is triggered when the Alarm Receiver dials 9538 (Answer button).

Answer event


Action commands: 

WUDD %1.phy 1
$MAILQ_NAVIG L%1.dir 1
LOG "Alarm answered at %1.dir %1.nam"



Explanation:

  • When an Alarm Receiver dials the "answer" code 9538, set an "answer"-flag (UDD = 1)
  • Re-trigger the event "23 - New Current Mail in station queue"
  • Send info to the log

Connect event

This event is triggered when the alarm receiver has "answered" the alarm, and there is an alarm in queue.

Connect event


Action commands: 

IF %udd(%1.phy)
$SC L3%2.dir(2)
$CONF %1.ref %2.ref
LOG "Audio established from %1.dir %1.nam to %2.dir %2.nam"
$CPYM L%1.dir W%2.TAG L%1.dir U20
$DIP L%1.dir "ind stl 2 0"
$DIP L%1.dir "ind stl 0 1"
ENDIF


Explanation: When the Alarm Receiver gets a new "current mail":

  • If the Alarm Receiver has answered/accepted the alarm call... ("answer"-flag = 1)
  • ..enable "Silent Call" function for alarm sender 3xx. This will prevent LED and backlight to be turned on at the Alarm Sender.
  • ..turn on the Simplex Conference related to the alarm sender
  • ..send info to the log
  • ..copy the mail to itself, but with priority 20. This low priority will stop the notification tone
  • ..turn off flashing red LED in Alarm Receiver station, and
  • ..turn on steady red LED in Alarm Receiver station



Cancel event

This event is triggered when the Alarm Receiver dials 9533 (Cancel button).

Cancel event


Action commands: 

WUDD %1.phy 0
$CONF L%1.dir LV
$CANM LV L%1.dir
$DIP L%1.dir "ind stl 0 0"
LOG "Alarm cleared at %1.dir %1.nam"


Explanation: When the Alarm Receiver dials 9533 (Cancel button):

  • Reset the "answer"-flag (UDD = 0)
  • Turn off the Simplex Conference at this staion
  • Delete all mails in this station
  • Turn off steady red LED in this station
  • Send info to the log


Logging

With the log events configured above, the log data in the System log will look like this: 

Mar 18 15:56:45 AlphaCom1 AlphaLog: N001.D065:.Exch:Alarm from 302 Desk A6 to Alarm Group 891
Mar 18 15:56:51 AlphaCom1 AlphaLog: N001.D065:.Exch:Alarm answered at 109 Operator 4
Mar 18 15:56:51 AlphaCom1 AlphaLog: N001.D065:.Exch:Audio established from 109 Operator 4 to 8202 Desk A6
Mar 18 15:59:56 AlphaCom1 AlphaLog: N001.D065:.Exch:Alarm cleared at 109 Operator 4
Retrieved from "https://wiki.zenitel.com/w/index.php?title=Silent_Alarm&oldid=231433"