Limitations

Functions below suffers some limitations or are not supported on shared DDI line.

Call transfer (Cisco only)

Due to PBX-related limitations, consultative transfer (turret-to-turret) does not work between shared DDI lines whose directory numbers are bound to the same Profile-EK device.

This limitation has disappeared in CUCM 8.0 but there is no guaranty that the behaviour is going to remain consistent along different CUCM versions.

Call transfer between incoming calls

Depending on PBX limitations, transferring an incoming call on another incoming call may succeed only under certain conditions.For instance, CUCM authorizes to transfer one call to another only if both calls are handled by lines related to the same Profile-EK device.

In order to maximize chances of transfer success, transfer confirmation is not restricted in user interface. Regardless the lines which handle calls, a transfer attempt is always sent the the PBX which notifies the terminal in case of transfer failure.

Conference call

Shared DDI lines support building multi-party conference calls that include traders and external parties.

(1)Since the conference is hosted on a shared DDI line, traders have the capability to leave/join the conference without any restriction.

(2)Only traders have possibility to drop an external party from the conference.

(3)The call related slot properties, either Private Wire or Radio, cannot be dropped out from the conference.

(4)The conference is closed once all distant parties have left or when the last trader in the conference terminates the call.  In this last instance, the possibility to keep the conference call active between the external parties is provided only if setting key "application.conference.preservation" is set to true. This DDI conference preservation setting key is found on TSS Device Management -> TPO Clusters -> [Cluster of TPO] -> Settings -> Global -> Basic Mode.

(5)The number of external parties which can be joined in a single conference is only limited by the available resources in the system (See comparison conference mode table).

(6)In each scenario, conferencing function is possible only between calls/shared DDI lines which are managed by the same TPO service instance.

PBX Shared lines (Cisco only)

When a DDI Line is a Cisco Shared line, Cisco IP Phones can monitor the line activity and Barge in existing calls.

But if these calls are made between 2 PBX Lines belonging to the same PBX SIP Device, IP Phone user cannot barge in it.

Consider the following setup:

•1 PBX Device DeviceA having 3 lines 1001, 1002 and 1003, registered by a TPO

•1 PBX Device DeviceB having 3 lines 1004, 1005 and 1006, registered by the same TPO.

•1 IP Phone X sharing line 1003 with DeviceA.

•User1 having DeviceA:1002 as its default line.

•User2 having DeviceA:1003 as its default line.

•User3 having DeviceB:1004 as its default line.

The IP Phone monitors User2's calls and should be able to barge in them:

•but it cannot barge in a call between User1 and User2 due to PBX limitations, because 1002 and 1003 belongs to the same PBX SIP Device

•while barge in a call between User2 and User 3 works properly because 1003 and 1004 belongs to different PBX SIP devices

Mute/Unmute Conference call

Traders as remote parties can be muted.

(1)Only traders have possibility to mute or unmute conference participants including themself.

(2)Some kind of traders cannot be muted :

-FlexGo participant;

-MRD stream of MrdPermanent slot;

-Static stream of Static IP slot;

-Radio stream of Static IP Radio slot.

(3)Neither slot bridging nor conference with multiple remote parties can be made between two slots as soon as one of them contains a muted participant or a muted remote party and a participant cannot be muted on DDI slot of a bridge.

(4)When a trader leaves conference, TPO automatically hangs-up call with him. When last trader leaves conference:

-if DDI conference preservation is not set, conference is closed;

-if DDI conference preservation is active, all muted remote parties call are automatically hanged-up and if only one remote party call is unmuted, conference with all remote parties is closed.

(5)When a trader puts conference on hold, TPO automatically hangs-up call with him. When last trader puts conference on hold, all remote parties can hear music-on-hold if configured. When resuming, remote parties are in the same state as before having been put on hold : if muted, they stay muted.

(6)If a trader B joins conference and some participants are muted, trader B doesn't hear muted participant and muted participant cannot hear trader B.

(7)When a trader is on private talking mode with only one remote party and another trader mutes him, all calls are present but there is no more sound.

(8)Mute a participant has no effect on video.