Considerations for Conference

Last Updated : Mar 04, 2020 |

This section provides information about how the Conference feature behaves in certain circumstances. Use this information to ensure that you receive the maximum benefits of Conference under all conditions. The following considerations apply to Conference:

Bridged Appearances

If a station user who is active on a bridged appearance makes a conference or transfer, the user receives enhanced displays based on the Class of Restriction (COR) of the user's station, not the station with the primary extension.

12-party conference

For the 12-party conference feature to work, you must meet the following requirements in addition to configuration in the Feature-Related System-Parameters page:

  • Avaya Aura® Media Server must exist in any of the connected network regions of the parties that wish to be part of 12-party conference.

  • Distributed Communication System (DCS) must be disabled in Feature Administration page of Communication Manager licensing in SMI as well as in SAT.

  • If you are using ASAI, then the ASAI link version to AES must be 11 or above.

Trunk-to-Trunk Connections

If you do not allow trunk-to-trunk connections on your system, the system drops all conference participants when:

  • A user disconnects.

  • All the other participant connect to the conference through trunk lines.

Loss Plan on Conference Calls

The end-to-end total loss for multiparty conference calls that is administered on the Location Parameters screen is not always applied to a specific call. The loss applied to a three-party conference call, for example, is calculated by adding the fixed pairwise loss for each pair of ports to the value for two-party loss shown on the Location Parameters screen. If this total is less than the end-to-end total loss value configured for a three-party conference, calculate the difference, and divide the difference by 2. Add 1 to this figure, and the result is the amount of loss applied to the call.