Page/Party Conference 5 Lines

Page/Party Conference 5 Line - principle

This article describes how the ICX-AlphaCom system can be configured to operate as a Page/Party line Conference 5 line system.
Up to 16 participants can be included in AlphaCom XE and up to 64 participants can be included in ICX-500 across all 5 Party Lines

From each Intercom, one can:

• Press and Hold the Page button to make a PA Announcement
• Press and Hold the PTT button on a Handset or Headset if connected
• Select a Party Line to toggle in and out of a Full Duplex Conference
• Select other Party Lines without having to toggle off first
• View if Paging is Ongoing from the LED indications (if available)
• View if a Party Line is in use from the LED indications (if available)
• View which Party Line is connected to the device from the LED indications (if available)

The stations must be Zenitel IP Devices. SIP devices are not supported in this application.

Operation

The application is based on using a Zenitel IP Master Station with at least 6 DAK keys (IPDM, IPDMH, IP-CRM-V-2) or a Substation with 6 buttons (TFIE-2 and TFIX-2).

DAK 1 - 5 are programmed to join and leave a Party Line. DAK 6 is programmed as the Page button. M-Key and PTT are also programmed as Paging buttons

Page:

• Press and Hold Page button to make a PA announcement or
• Press and Hold PTT button on Handset or Headset to make a PA announcement
• Release Page/PTT button and select a Party Line
• Uses Group Call feature; Configurable Gong Tone

Party Line:

• Toggle on/off by pressing the Party button
• Select other Party Line without having to Toggle off first
• Can use Page button while already in Party Line

Uses Duplex Conference - Up to 64 Members (ICX-500) or 16 Members (AlphaCom XE)

LED Behavior:

• Party Line is Red - In Use at this time.
• Party Line is Green - Current Party Line connected
• Page button is Red - Ongoing Page

Number plan

The application is using the Duplex Conference feature of the ICX-AlphaCom. Duplex Conference 1 - 5 (8301 - 8305) are hardcoded for use as Party lines 1 - 5.

General rules

• UDP group 1: All Page/Party Stations
• Group 85 (2): Paging Group. Configured with "Automatic M-key".
• Group 86 (3): All Page/Party Stations with DAK LED
• Group 11-15: Dynamic groups containing current conference members in conference 1-5
• UDDs: UDD equal to physical number is used as "Conf Flag" to store current conference membership
• DAK 1-5: Hardcoded for Duplex Conference 1-5 (8301-8305). Note that DAK tables must be empty
• DAK 6: Paging button
• M-key/PTT: Paging button

Event Handler configuration

Station Online event

Initiator start Page/Party Conference using DAK 1

WUDD %1.phy 0
IND %1.phy 0 0 0
$GRM L%1.dir NG11 U0
$GRM L%1.dir NG12 U0
$GRM L%1.dir NG13 U0
$GRM L%1.dir NG14 U0
$GRM L%1.dir NG15 U0

Station DAK use

Participants join in Listen Only mode

IF %op(%sev,>=,1)
IF %op(%sev,<=,5)
IF %chg(1,0)
IF %op(%udd(%1.phy),=,%sev)
$ODC L%1.dir L8300
WUDD %1.phy 0
LOG "%1.dir: Conference OFF"
stop
ENDIF
$ODC L%1.dir L8300
$ODC L%1.dir L830%sev U1 U4
WUDD %1.phy %sev
LOG "%1.dir: Conference 830%sev"
ENDIF
ENDIF
ENDIF
IF %op(%sev,=,6)
IF %chg(1,0)
$DISCON_ST L%1.dir U0
pause
pause
pause
$DD L%1.dir L85
LOG "%1.dir: Group Call 85"
stop
ENDIF
$DISCON_ST L%1.dir U0
IF %udd(%1.phy)
pause
$ODC L%1.dir L830%udd(%1.phy) U1 U4
LOG "%1.dir: Reconnect Conference 830%udd(%1.phy)"
ENDIF
ENDIF

Operation on PTT and M Key

Reset key locks on Conference end

IF %chg(1,0)
$DISCON_ST L%1.dir U0
pause
pause
pause
$DD L%1.dir L85
LOG "%1.dir: Group Call 85 from PTT button"
stop
ENDIF
$DISCON_ST L%1.dir U0
IF %udd(%1.phy)
pause
$ODC L%1.dir L830%udd(%1.phy) U1 U4
LOG "%1.dir: Reconnect Conference after PTT: 830%udd(%1.phy)"
ENDIF
ENDIF 

Operation on On-Hook (Handset Use)

Enable microphone on Participant stations

IF %udd(%1.phy)
pause
pause
pause
pause
$ODC L%1.dir L830%udd(%1.phy) U1 U4
LOG "%1.dir: Reconnect Conference when going on-hook: 830%udd(%1.phy)"
ENDIF 

Operation on Conference Start / Stop

At ICX startup all UDD flags are reset

IND %1.phy %2.dir(1) 2 1
$GRM L%1.dir NG1%2.dir(1) U%chg(1,0)
LOG " Group Member: $GRM L%1.dir NG1%2.dir(1) U%chg(1,0)"
IF %chg(1,0)
GIND 3 %2.dir(1) 1 1 ON
LOG "Turn all LEDs ON for conf %2.dir"
$ST L%1.dir W1200 L9999
LOG "Start conversation timer for %1.dir"
ENDIF
IF %chg(0,1)
pause
pause
LOG "%1.dir: Conference OFF. Are there more members in %2.dir?"
IF %op(%gns(1%2.dir(1),0),=,0)
GIND 3 %2.dir(1) 1 1 OFF
LOG "No more members. Turn all LEDs OFF for conf %2.dir"
stop
ENDIF
LOG "Yes, there are more members. Keep LEDs ON"
ENDIF

Event Timeout

At ICX startup all UDD flags are reset

$DISCON_ST L%1.dir U0
WUDD %1.phy 0
LOG "Conversation timeout for %1.dir"

Paging Call

At ICX startup all UDD flags are reset

GIND %2.phy 6 1 1 

Option to disable Connection Tones

At ICX startup all UDD flags are reset

$SNV Q0 W1 W6 W54
$SNV Q0 W1 W6 W57

The use of UDD variables

UDDs are used to store various status information:

• UDD 1 - 552: UDD equal to physical number is used as "Conf Flag" to store current conference membership