Limitations and known issues

•Bridges are not restored in cluster hotbackup DNS and Persistency mode.

•When Bridges is used on different clusters, these clusters must be configured with the same redundancy mode.

•Only local bridging is supported in cluster DNS. For example, the user can not bridge DDI slots from cluster DNS A with DDI slots from cluster DNS B.

•This feature is not supported on ED137 Radio system

•The Conference mode (ALL or MasterOnly) of the DDI places involved into the conference bridge must be the same.

•Conference call is not supported. The trader/user can not create a bridge with slot involved in a conference call.

• If a TPO Place involved in a bridge is stopped, the bridge is destroyed.

•Once the bridge is created, Exclusive and Exclusive conferences are not available on the slots of the bridge.

•The trader/user can not create a bridge with a DDI slot in Exclusive or Exclusive conference.

•Slot bridging can't 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.

•Each created bridge consumes one DDI conference resource.

•When a DDI slot is already involved in a bridge, it it not available for creating another bridge. A DDI slot can only be used in one bridge.

•It is not possible to add/remove a DDI slot of a bridge.

•When creating a bridge in which different TPOs are involved, if one TPO is not reachable, the bridge can not be created.

•When creating a bridge in which different TPOs are involved,  if one TPO becomes out of service the bridge is still active. If the failed TPO becomes in service, it is not involved in the bridge anymore.

•Instant Replay feature is not taken into account by the bridge. The trader can only replay the remote party voice of the DDI slot in which he is connected.

•PBX Phone Access feature is not taken into account by the bridge. The phone access's user can only access on the DDI slot in which he is connected.

•Recording Beep Tone is not taken account by the bridge but it has an effect on the recorded call.

•Limitation on the record by slot of Voice recording over TPO

Here are some example to explain the behavior:

Scenario 1: context

- TPO is configured for Beep Recording feature

- DDI place with slot 101 to 130

- User 1 is only configured for recording on the handset 1

1. User1 establishes a call with Remote Party X on handset 1 on slot 101. The call 1 is recorded and X receives the beep tone.

2. User1 establishes a call with Remote Party Y on the handset 2 on slot 102. The call 2 is not recorded and Y does not receive the beep tone.

3. User1 bridges slot 101 and slot 102

=> User1 and X and Y can speak and hear each other

=> The call 1 is recorded with User1, X and Y BUT THE REMOTE PARTY Y WILL NOT RECEIVE THE BEEP TONE.

Scenario 2: context

- TPO is configured for Beep Recording feature

- DDI place with slot 101 to 130

- User 1 is configured for recording

- User 2 is not configured for recording

1. User1 establishes a call with Remote Party X on slot 101. The call 1 is recorded and X receives the beep tone.

2. User2 establishes a call with Remote Party Y on slot 102. The call 2 is not recorded and Y does not receive the beep tone.

3. User1 bridges slot 101 and slot 102

=> User1, User2, X and Y can speak and hear each other

=> The call 1 is recorded with User1, User2, X and Y BUT THE REMOTE PARTY Y WILL NOT RECEIVE THE BEEP TONE.