User's Manual

Avaya Branch Gateway Manager 10.0 Page 766
15-601011 Issue 29r (Friday, November 02, 2012)B5800 Branch Gateway
9.28 Conferencing
The Avaya Branch Gateway system supports a number of conference features and allows multiple simultaneous
conferences.
Conference Types
There are 2 types of conference supported by the system:
· Ad-Hoc Conferencing
An ad-hoc conference is one created on the fly, typically by holding an existing call, making another call and then
pressing a conference key on the phone. Other people can be added to the conference by repeating the process.
· Meet Me Conferencing
Conference Meet Me allows users to join or start a specific numbered conference. This method of operation allows
you to advertise a conference number and then let the other parties join the conference themselves.
· User Personal Conference Number
For Release 6.2+, each user's own extension number is treated as their own personal conference number.
Only that user is able to start a conference using that number as the conference ID. Any one else attempting
to start a conference with that number will find themselves in a conference but on hold until the owner also
joins. Personal conferences are always hosted on the owner's system. Note, when a user calls from their
mobile twinned number, the personal conference feature will only work if they access the conference using an
FNE 18 service.
Conference Capacity
The system supports up to 128 conference parties in total. However, the maximum of 64 parties applies to any individual
conference. The system capacity is reduced by the number of Embedded Voicemail channels is use. The system
automatically applies silence suppression to quiet parties in conferences involving 10 or more parties.
Conference Notes
· Other Uses of Conference Resources
System features such as call intrusion and silent monitoring all use conference resources for their operation. On IP
Office Aura Edition systems, each Embedded Voicemail call in progress also reduces the conference capacity.
· Automatically Ending Conferences
The behavior for the system automatically ending a conference varies as follows:
· A conference remains active until the last extension or trunk with reliable disconnect leaves. Connections to
voicemail or a trunk without reliable disconnect (for example an analog loop-start trunk) will not hold a conference
open.
· The Drop External Only Impromptu Conference setting controls whether a conference is automatically ended
when the last internal party exits the conference.
· Analog Trunk Restriction
In conferences that include external calls, only a maximum of two analog trunk calls are supported. This limit is not
enforced by the system software.
· IP Trunks and Extensions
Conferencing is performed by services on the system's non-IP interface. Therefore a voice compression channel is
required for each IP trunk or extension involved in the conference.
· Call Routing
A short code routing calls into a conference can be used as an Incoming Call Route destination.
· Conference Tones
The system provides conference tones. These will be either played when a party enters/leaves the conference or as a
regularly repeated tone. This is controlled by the Conferencing Tone (System | Telephony | Tones & Music )
option.
163 163