Limitations

Due to barge call(s) characteristics, when the last trader leaves the call, the call is closed and the slot is freed even if barger(s) is (are) present in the call. The previously mentioned term "trader" can refer to a Turret or FlexGo Device user.

Before the last trader leaves the call

After the last trader leaves the call

An exception to this limitation can occurs when a conference is made on a DDI slot with the setting application.conference.preservation.barge set to true. In this specific case, if more than one remote party take part in the conference, the conference between remote parties is kept even without any trader on the slot. Then, the barge call(s) is (are) kept.

Before the las trader leave the call

After the last trader leaves the call (conference preservation enabled)

If the remote party is placed on hold by the last remaining trader, the barger(s) will be dropped from the call.

Before placing the remote party on hold

After placing the remote party on hold

As mentioned further in this section, a barge call attempt on a held call will be rejected.

When the trader takes back the remote party, the call is re-established between the trader and the remote party while the barger is kept out of the call. Thus the barger can still re-barge the active call.

After the trader un-holds the remote party

If the DDI slot is of type S or P, barge call(s) can be done on the slot, event if no trader is on this slot.

Barge call(s) attempt on Holding, Held or Resuming call state will be rejected.

Barge call(s) on a call that is in exclusive or exclusive conference mode is allowed, but the barger is out of the exclusive "group", and thus does not hear anyone.