Managing MultiMedia Calling
Understanding the Multimedia Complex
Administrator’s Guide for Avaya Communication Manager
283
November 2003
If the system does not have sufficient ESM server resources available for all parties currently in
the call, the activation of T.120 data sharing will be denied. The mm-datacnf status lamp will flash
denial or the mm-datacnf FAC will produce reorder.
3
Each H.320 DVC system in the conference call is joined to the data conference. On many DVC
systems, the provided GUI may prompt the user with a dialog box, requesting the user to select a
specific conference to join. With MMCH, there should only be one conference available to select.
4
The user must now use the PC’s GUI to begin application sharing. The method for beginning
application sharing or file transfer is different for each H.320 multimedia application. One of the
H.320 DVC systems activates data sharing from the H.320 DVC vendor provided GUI. See your
H.320 DVC system documentation for details.
5
The same H.320 DVC system as in step 4, opens an application, whiteboard, etc. to share and the
image of the application is displayed on all H.320 DVC systems in the conference.
For details on how multiple users may control the shared application, see the vendor provided
documentation for your specific H.320 DVC system.
6
To end the data collaboration session and retain the voice/video conference, the station that
selected the mm-datacnf button or FAC may press the mm-datacnf button or hit transfer and dial
the mm-datacnf deactivation FAC.
NOTE:
As of this writing, many endpoints do not respond correctly to ending the data
collaboration session and retaining voice/video. Some H.320 DVC systems drop the entire
call. Avaya recommends that once T.120 data sharing has been enabled for a conference,
that it remain active for the duration of the conference call. When all endpoints have
dropped from the call, the T.120 resources will be released.
Joining a multimedia conference after T.120 data sharing has been enabled.
If a multimedia conference with T.120 data sharing is already active and it is desired to conference in a
new video endpoint, the new video endpoint can be conferenced into the existing call. The new endpoint
will be allowed into the data conference if there exists sufficient ESM server resources for the new
endpoint. The new endpoint will get voice/video and data sharing if the new endpoint supports the
multi-layer protocol (MLP) data rate chosen by the system when T.120 data collaboration was activated.
If the endpoint does not support the pre-existing MLP data rate, the new endpoint will only receive voice
and video.
Single server or switch data collaboration.
When all parties involved in data collaboration conference are located on the same physical Avaya
DEFINITY® Server or media server, there is no restriction on the type of user. The parties may be any
combination of Enhanced multimedia complexes, Basic multimedia complexes or stand-alone H.320
DVC systems.
Multi-switch data collaboration.
When all parties involved in data collaboration conference are not located on the same physical Avaya
media server, the parties located on the Avaya server hosting the data conference (i.e. the server which
activated mm-datacnf) may be any combination of Enhanced multimedia complexes, Basic multimedia
complexes or stand-alone H.320 DVC systems. All parties on remote servers must not be Enhanced
multimedia complexes: they must be Basic multimedia complexes or stand-alone H.320 DVC systems.
Prior to originating or receiving a multimedia mode call, the mm-basic feature button or feature access
code can be used to dynamically change an Enhanced mode complex into a Basic mode complex and
back again.