Primary/Secondary Server

Each Primary and Secondary supports a local audio conference capability with the following capacities:

IP500 V2 and Linux Expansion System

Each IP500 V2 and Linux Expansion System supports a local audio conference capability with the following capacities:

System Conferences

System conferences use the same conference capacity as above but are subject to the following additional limits:

• IP Office Essential Edition/IP Office Preferred Edition: 30.

• IP Office Server Edition/IP Office Select/IP Office Subscription (Linux): 120. System conferences are hosted by the primary server (secondary server during resilience).

Notes

1. Unless otherwise stated, R240 and R260 servers capacities are equivalent.

2. For virtual servers, the actually capacity also depends the virtual machine profile as detailed in "Deploying IP Office Servers as Virtual Machines".

3. The figures cover both ad-hoc and meet-me conference types.

4. With one-X Portal users active, a solution-wide limit of 750 conference channel participants applies, but this does not include conferences used for call recording.

5. IP Office Server Edition supports differing capacity and performance levels when Avaya Contact Center Select (ACCS) is attached. See Avaya Contact Center Applications.

6. The increased capacities for ACCS are only supported when the applications are actively connected to the host IP Office and should only be used for call recording purposes.

7. No dynamic solution-wide conference allocation is supported, only static via call flows or Conference Meet Me short code Line Group ID.

8. V2 Expansion conferences exist in the digital domain; hence all VoIP parties (trunk or extension) will require a VCM channel for the duration. See VCM Channel Capacity.

9. Further information on conferences can be found at: http://marketingtools.avaya.com/knowledgebase/businesspartner/ipoffice/mergedProjects/manager/_frame2.html?Conferencing.Overview.html

Which Servers Conference Resources are Used?

The location of the conference resource used when a conference is started are determined by a number of factors:

• A user performing an ad-hoc conference uses the conference resources of the server on which they are logged in.

• A meet-me conference using a user’s personal meet-me bridge uses the conference resources of the server on which they are logged in.

• A meet-me conference created by Voicemail Pro call flow, or the Conference meet-me short code feature use the system on which the feature was invoked.

• To invoke a meet-me Conference using the resources of a remote system, use the Line Group ID field of the Conference Meet Me short code feature. By default this is set to 0, for local system.

• For the case where a conference is scheduled by Avaya one-X® Portal and at the scheduled time the conference dials the delegates: The conference location is the server to which the active Avaya one-X® Portal is attached.

Recording a conference requires an additional conference channel, as well as an IP Office Line (SCN trunk) channel to the recording destination (Primary or Secondary Server, alternate during fail over operation). Neither IP Office nor Voicemail Pro can automatically link or move conference locations, but existing conferences can be connected together.

When conference resources run out, attempts to record calls, join or create conferences are rejected.