User's Manual

Design and deployment
44 Administering Avaya Video Conferencing Solutions 6.1
DRAFT
● If you drop all but two of your video-enabled parties, video returns.
No Bandwidth is available
When all the available bandwidth has been used up by the endpoints on existing calls, the
Avaya 1000 series video endpoints display a message No Bandwidth.
Transfer to MGC/RMX is being used for ad-hoc video conferencing.
In this situation, avoid scenarios where a user attempts to transfer to a meeting room where
tandem Communication Manager systems link the user to the Polycom MGC/RMX. Multiple
Communication Manager shuffling (if allowed) may legitimately block the transfer. A
reattempted transfer should succeed.
Deployment of ad-hoc video conferencing with Polycom RMXs must be
distributed.
If customers with a network of PBXs trunked together wants to deploy ad-hoc video
conferencing with Polycom RMXs in the future, they should distribute them.
In this situation, ad-hoc video conferencing requires at least one Polycom RMX per active
Communication Manager system to support future ad-hoc video conferencing via the
Conference button.
Additional media resources are allocated for Communication Manager
systems used for tandem multimedia calls.
In a typical hub-and-spoke arrangement of Communication Manager systems, the core PABX
doing the tandem calls between remote PABX systems requires additional media resources
because shuffling to direct-ip is blocked for multimedia calls. If you do not add media resources,
expect higher use of media resources on tandem Communication Manager systems.