Page/Party Conference 1 Line

Page/Party Conference 1 Line - principle

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

From each Intercom, one can:

• Start a Duplex Conference with all participants in "Listen only" mode allowing for Page mode from the Initiator.
• Participate in the Party line call by briefly pressing the M key. The user is now a full duplex member of the conference.
• Only the Initiator is allowed to end the Page/Party call.

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 (IPDM, IPDMH, IP-CROR, IP-CRM-V-2, TFIE-1, TFIX-1) but can also be a TCIS-1 with M key, or a Substation with 2 buttons (TCIS-5, TFIE and TFIX) using another DAK key as the M-key.

DAK 1 is programmed to start and end the Page/Party Conference. The M key is used to start full duplex conversations from the participant station.

During the Page/Party Conference, the C key and DAK keys are blocked in the participant station. Only the Initiator can end the Conference using DAK 1. All stations are busy marked during the conference.

Number plan

The application is using the Duplex Conference feature of the ICX-AlphaCom. There are 20 conference channels, default numbers are 8301-8320. The application is also using the Groups feature of the ICX-AlphaCom. There are 250 groups, default numbers are 84-899

Each Page/Party conference in the system requires one duplex conference and one group.

General rules

• Each Page/Party conference is using one Duplex Conference and one Group.
• The Duplex Conference, Group and DAK key are freely changeable by editing the events.
• In the below example, we are using Duplex Conference 1 (8301) uses Group 10 (894)
• The Call setup and Teardown are in the example using DAK 1

Configuration

• Initiator stations must be included in UDP 1
• All participants in the Conference must be included in the associated group, here 894.

Event Handler configuration

Call Setup event

Initiator start Page/Party Conference using DAK 1

Action commands:

IF %UDD(%1.PHY)​
WUDD %1.PHY 0​
$ODC L894 L8300​
LOG "Conference %1.DIR %1.NAM Disabled"​
STOP​
ENDIF​
WUDD %1.PHY 1​
$ODC L894 L8301​
LOG "Conference %1.DIR %1.NAM Enabled"

On Conference Join

Participants join in Listen Only mode

Action commands:

$SEB L%1.DIR U5 U1
IF %UDD(%1.PHY)
STOP
ENDIF
$DIP L%1.DIR "auo 8"
WUDD %OP(%1.PHY,+,500) 1
$SEB L%1.DIR U4 U1

On Conference End

Reset key locks on Conference end

Action commands:

WUDD %op(%1.phy,+,500) 0​
$SEB L%1.DIR U5 U0
​$SEB L%1.DIR U4 U0

On Participant M-Key

Enable microphone on Participant stations

Action commands:

IF %UDD(%OP(%1.PHY,+,500))​
$DIP L%1.DIR "auo 1"​
ENDIF

Initialization of UDD variables at ICX System startup

At ICX startup all UDD flags are reset

Action commands:

tmp 0 "0"​
LOOP
​tmp 0 "%op(%tmp(0),+,1)"
​WUDD %tmp(0) 0
​IF %op(%tmp(0),=,50)​
BREAK​
ENDIF​
ENDLOOP​
tmp 1 "500"​
LOOP​
tmp 1 "%op(%tmp(1),+,1)"
WUDD %tmp(1) 0​
IF %op(%tmp(1),=,550)​
BREAK​
ENDIF​
ENDLOOP

The use of UDD variables

UDDs are used to store various status information:

• UDD 1 - 50: Conference status using %1.PHY, one UDD per initiator: 0 = Conference not active. 1 = Conference is active. Expand this if more initiators are required.
• UDD 500 - 550: Conference status using %1.PHY + 500, one UDD per Conference Member. 0 = Not Member. 1 = Member. Expand this if more members are required.