Actions

Mooring Conference

From Zenitel Wiki

AI.png

Requirements

  1. Everybody shall hear the Active User
  2. When a user presses the M-key he will become the Active User. The Active User doesn't have to keep the M-key pressed while talking
  3. The Bridge shall be able to talk into the conference by pressing the M-key. When the M-key is released the Active User shall continue to talk without pressing the M-key
  4. When next user presses M-key, he shall become the Active User
  5. The Bridge shall from the DAK panel be able to select who should be the Active User
  6. The DAK panel shall indicate on LED's who is participating in the conference, and who is Active User.
  7. The Bridge shall be able to disconnect the confrence by pressing a DAK key
  8. Each user shall be able to disconnect from the conference by dialing a code, e.g. 8200
  9. It shall be possible to integrate a mobile radio system. The radio shall be able to talk into the conference when the squelsh signal is present. When the squelsh signal is removed, the Active User shall continue to talk without pressing the M-key


Configuration

  • Include all conference participants, except the Bridge and the Radio Interface (if radio is connected) in UDP group 1
  • Include the Bridge (and Radio Interface if connected) in UDP group 2
  • Include all conference participants, including the Bridge and the Radio Interface, in group 9
  • Include the Bridge (and Radio Interface if connected) in group 10
  • In order to override the active user, all users (incl. Bridge and Radio Interface must have the "SX Conf Override" flag enabled (Users & Stations > User Preferences).

Event Handler programming

In the following programming example the directory number 8201 is used for the Simplex Conference and directory number 138 for the CRM V station. The mobile radio interface is using directory number 110. Other numbers can of course be used.

In AlphaPro, Exchange & System -> Events, insert events with the following parameters:

The conference is started by dialing event trigger 9533 from the Bridge. UDD 500, which contains the current Active User, is cleared:

Application16a.png


Action commands:

WUDD 500 0
CNG 9 1



The conference is stopped by dialing event trigger 9534 from the Bridge:

Application16b.png


Action commands:

CNG 9 0



When a user releases the M-key, the station will be forced to still feed the conference:

Application16c.png


Action commands:

pause
$CONF_TALK L%1.dir



When the Bridge releases the M-key, the Active User will be talking into the conference. A 1.0 sec timer is used to retrigger the Active User in case the Bridge (or radio) presses M-key briefly:

Application16d.png


Action commands:

$CONF_TALK L%udd(500)
$ST L%1.dir W10 L99 



The 1.0 sec timer retriggers the Active Talker in case the Bridge (or radio) pressed the M-key briefly:

Application16e.png


Action commands:

$CONF_TALK L%udd(500)



When someone is talking into conference 8201, on station 138 switch off the "Active User LED" for the previous user, and switch on the "Active User LED" for the current user. Store the current active user in UDD 501. If the talker is member of group 10 (i.e. all users except bridge), update the Active User UDD 500:

Application16f.png


Action commands:

OWN r 138
IND %2.phy %2.dak(I%udd(501)) 2 3 OFF
IND %2.phy %2.dak(I%1.dir) 2 3 ON
WUDD 501 %1.dir
IF %sgm(%1.phy,10)
WUDD 500 %1.dir
ENDIF



Turn the red LED steady ON when a station joins the conference 8201:

Application16g.png


Action commands:

OWN r 138
IND %2.phy %2.dak(I%1.dir) 1 1 ON



Turn the red and green LED's off when a station leaves conference 8201:

Application16h.png


Action commands:

OWN r 138
IND %2.phy %2.dak(I%1.dir) 1 1 OFF
IND %2.phy %2.dak(I%1.dir) 2 3 OFF



By means of the two step event trigger (default 9535), the Bridge can select from the DAK panel who should be the Active User:

Application16i.png


Action commands:

$CONF_TALK L%2.dir
$DISCON_ST L%1.dir 0


Assign 9535 to a DAK key. Press this DAK key and then the DAK key of the station that shall be come to Active User.


The keying of the radio transmitter is controlled by an RCO output (here RCO 1 is used as an example):

Application16j.png




The squelch signal from the mobile radio transmitter is triggering an RCI input. When ON the Radio Interface (here number 110) will feed the conference. When OFF the Active User will continue to feed the conference. A 1.0 sec timer is included to retrigger the Active User in case a short ON -> OFF signal:

  • RCI ON:
$CONF_TALK L110


  • RCI OFF:
$CONF_TALK L%udd(500);$ST L110 W10 L99