Actions

Emergency group call with acknowledge

From Zenitel Wiki

Revision as of 14:15, 7 August 2009 by Asle (talk) (Acknowledge Event)

Feature

Configuration example

A special group of stations receives emergency broadcast from a CRMIV or CRMV station. The members can be located in different nodes in AlphaNet. When the CRM station activates the emergency call, the corresponding LED's in the DAK module gives a red slow blinking. At the same time a display message is transmitted to the members.

There is an acknowledge code to dial from the stations in the special group to tell the CRM that the member has acknowledged the emergency call. When the code is dialled the LED indication will change to steady green, and the display message will be cleared from that station. For those stations who don't acknowledge the call, the display message will remain in the station to indicate that the emergency call has been active while they were away.

A "Clear" code dialled on the CRM station will turn off all LED indications on the CRM, and remove the display information from all member stations.

Configuration example

Let us say that the members of the special group are:

  • Node 1: Stations 101, 104, 105 and 106
  • Node 2: Stations 201, 202 and 250
  • Node 3: 401, 402 and 450
  • The CRM directory number is 500. The station numbers above must be assigned to DAK keys on the CRM station.
  • Include the stations in the local group 20 in each exchange, and include the local group 20 in global group 20. Assign a directory number to the global group 20, say 9020. The CRM station can now dial 9020 to do the emergency broadcast.

Programming

Emergency Broadcast Activation

In the Exchange & System -> Events insert a new event:

Emergeny call event 1.png
Event Owner: The CRM IV station
Event type: 08 - Conversation Outgoing
Subevent: N/A
When change to: ON
When related to: Directory number, Id. 9020
Action: IND %1.phy %1.DAK(I101) 1 2 ON

IND %1.phy %1.DAK(I104) 1 2 ON
IND %1.phy %1.DAK(I105) 1 2 ON
IND %1.phy %1.DAK(I106) 1 2 ON
IND %1.phy %1.DAK(I201) 1 2 ON
IND %1.phy %1.DAK(I202) 1 2 ON
IND %1.phy %1.DAK(I250) 1 2 ON
IND %1.phy %1.DAK(I401) 1 2 ON
IND %1.phy %1.DAK(I402) 1 2 ON
IND %1.phy %1.DAK(I450) 1 2 ON
@U1 $SM %1.ref NG20 U119 NM17 GV U0 'Emergency' U0
@U2 $SM %1.ref NG20 U119 NM17 GV U0 'Emergency' U0
@U3 $SM %1.ref NG20 U119 NM17 GV U0 'Emergency' U0

When the CRM dials the global group 9020 the IND command will switch ON the red LED in the required DAK keys, and the SM command will send a mail message to stations in group 20 in each node 1, 2 and 3. The mail has priority 119, and the text 'Emergency' will be displayed. This event is programmed only in the node where the CRM station is located.

Acknowledge Code

In each exchange select the Directory & Features window, and create an Acknowledge Code, say 9590, with feature number 85/0.

In the Exchange & System -> Events create a new event which is triggered when the Acknowledge Code is dialled from any station. This event must be created in all exchanges:

Emergeny call event 2.png
Event Owner: Stations with UDP, UDP 8 (All stations)
Event type: 15 - Event Trigger Feature
Subevent: 0
When change to: ON
When related to: Directory number, Id: 9590
Action: @U1 $ER U15 U7 U1 U1 L500 U3 L%1.dir

When a station dials the acknowledge code an ER (Event Report) command is sent to the node where the CRM is located (node 1 in this example), which will trigger an event of type 15, subevent 7, When Change To: ON, Owner: 500, Related To: The dialling station.

Acknowledge Event

Emergeny call event 3.png

In the node where the CRM is located, create a new event which is triggered by the ER (Event Report) command generated when the acknowledge code is dialled from any member station.

Event Owner: The CRM IV station
Event type: 15 - Event Trigger feature
Subevent: 7
When change to: ON
When related to: All
Action: IND %1.phy %1.dak(I%2.dir) 2 1 ON

IND %1.phy %1.dak(I%2.dir) 1 2 OFF
$CANM %1.ref %2.ref NM255 U255

The IND command will turn the green led on and the red led off in the assosiated DAK key of the CRM station. The CANM command mail will delete the mail in the display.

Buzzer

Priority Mail in Idle

Emergeny call event 4.png

Insert a new event with the following parameters:

Event Owner: The CRM IV station
Event type: 12 - Priority Mail in Idle
Subevent: N/A
When change to: ON or OFF
When related to: All
Action: IND %1.phy 1023 1 2


This will turn on the internal buzzer when a call request is received. The buzzer will be silent during conversartion.


Other applications

CRM IV: Indicate status of remote stations in AlphaNet