Specifications

Configuration and Maintenance Manual

• Restrict duplicate personal IDs on audio connections:

• If selected, duplicate IDs are not allowed on audio connections.

Participant impact:

Depending on the option selected by the leader, participants may be forced to enter a Personal

ID upon joining a conference. The email invitation will indicate if a Personal ID is required to

attend the conference. Additionally, as stated under Leader impact, if Personal ID approval is

required, the participants will receive an email once the leader has approved their attendance

indicating Approval Granted.

Google Apps Integration

MCA 5.0 will support Google integration. In this release, we will provide the ability to invite

members to a conference via Google and also have the invited guests easily enter the scheduled

conference into their calendar.

SIP and HD Video Support

SIP Video Call Support

A SIP (Session Initiation Protocol) Device such as the UC360, UC Advanced Desktop and

Mobile clients as well as tested and supported 3rd party endpoints will be able to send and

receive video stream after joining an active conference call on the MCA server. This functionality

will be supported through a configured MCD PBX only. Prior to MCA 5.0, a SIP Device could

only participate in the audio portion of the conference. SIP Video requires an Enhanced Video

license.

Deployment with SIP Servers and End Points

MCA supports the SIP protocol. As a result, it is capable of operating with a number of third

party SIP Servers and SIP end points such as SIP phones, Audio Conference Units and Video

Conference Units.

Mitel maintains a SIP Centre of Excellence (SIP CoE); the CoE performs interoperability testing

between third party devices and Mitel SIP devices. The CoE generates documents that cover

Note: SIP device(s) can only receive a single video stream. MCA system determines

the active video based on the precedence level of the participants in the following order:

1) MCA client - leader

2) MCA client - participant (sharing host)

3) MCA client - participant (if more than one is broadcasting then the first that joined

takes precedence)

4) SIP device - leader (if more than one SIP device joined as a leader and is broadcasting,

then the one that joined first takes precedence)

5) SIP device - participant (if more than one SIP device joined as a participant and is

broadcasting, then the one that joined first takes precedence).