Exclusive Conference

Note: Exclusive conference is activated on the turret.

Location: Terminal Boot Settings, Terminal Profile Settings, profile
TPO	Exclusive conference truefalse Key: profile.setting.old.privateconf Description: Activate the exclusive conference. When this mode is activated and the user clicks on the exclusive button, he will be in conference with the remote party and other connected users on public state. Constraint: true|false Related settings: OLD release conference exclusivity policy (profile.setting.old.conference.release.privacy) Private conference (application.privateconference.keepconf)

Two scenarios may happen

1.Scenario 1:  Slot goes to exclusive during the call

The slot is on “public” and used by the IPTrade Terminal and a Remote Party.

The PBX phone reaches the slot through the access point. PBX phone, IPTrade Terminal and Remote party can hear and talk to each other.

Then, the IPTrade’s user changes the talking mode of the slot to Exclusive (in this case, exclusive conference), the Remote Party, PBX Phone and IPTrade Terminal can talk to each other, but no other Phone or IPTrade Terminal can join the slot.

Example:

Turret: TLAB01; Remote Party: RP; IP phone: 1120; DDI Line 5041; Access Point 5042

TLAB01 has an established call with Remote party RP on slot 101. Slot 101 is in public talking mode; TLAB01 and RP can hear and speak each other;

Phone 1120 dials 5042, access point for DDI line 5041. Phone 1120 joins 101 slot by entering the DTMF code: 101# => 1120 and TLAB01 and RP can hear and speak each other.

TLAB01 press on exclusive button => 1120 can still hear and talk to TLAB01 and RP.

2.Scenario 2: Join on “exclusive conference”

The slot is on “exclusive” and used by the IPTrade Terminal and a Remote Party.

The PBX phone tries to reach the slot through the access point. The PBX phone can’t enter the conference and the call to access point ends.