So we have four different models of Scopia® Elite MCUs and different MCU bundles
that we can use for system designs that will enable any global business to conduct high
quality and flexible video calling from anywhere broadband Internet is available.
If I'm connecting with XT 5000 endpoint and I'm sitting in a meeting room and I
have as much bandwidth as I want to use for my purposes then I will consume an
entire port. These examples are done via dynamic allocation support so each
one of the connections we are setting up via the MCU support is automatically
connected and we consume the resources we need. There is no reason that a
desktop client that does not need more than 360p connection will suddenly
consume an entire port like what happens with other competitor MCU products.
Check out the video on the Radvision YouTube Channel for more information
about our Flexible Resource Allocation capabilities.
setup and endpoints requiring 480p or 720p use four ports and a 1080p endpoint uses 8
ports. Similar to the previous example, another way to refer to the port consumption for
an MCU with 4X capacity increase is to say that each 360p endpoint uses ¼ of a basic
capacity or a 720p port that would be designated in a 1X capacity design.
By the way, we are only talking here are about the resolutions that the MCU can
encode, decoding can be done without design issues for any resolution.
In short, using the increased capacity option and 480p or 360p for video calls, a
business can achieve greater efficiency with their infrastructure through lower resolution
ports for more connections per MCU. This is a unique differentiator for our products in
the competitive market place. Other competitors may make certain efficiency claims, but
in reality there will be more limitations and less flexibility than what we can offer to our
In designing a video system, one can configure the endpoints or desktop clients to use
a specific resolution or maximum bandwidth. So if you license the Elite MCU with 360p
ports, you should also set the desktop client or endpoint to 360P, so that no endpoint is
consuming more than a single port per user. However users can still connect at 720p or
1080p by using multiple ports.
to maintain 1080p resolution, then this can be set up so that others will be downgraded
to the lower resolutions instead of a selected user who needs to remain at 1080p. So
with the Scopia® Management tools, we can define the caller who should specifically
always is stay with 1080p.
This does not work for down converting 720p and all 30 ports are used and another call
comes in, it will be rejected. For example, 720p calls will not be down converted to 360p
or 480p to create more ports for call overflows.
Viewers also will know when the conference is being locked. You have an option to lock
the conference so if a meeting leader doesn’t want additional users to connect, he can
lock the conference and then no more users can connect. So there is a no entry sign
that will seen by those who are already in the meeting .
There is also a notification for a start or a stop of presentation. You will see an indication
for a person specifically who is presenting. You will also see an indication when
someone is muting or un-muting your audio or your video. So if I am the leader of the
conference, I can choose to mute someone’s audio or video.
And the last one, and perhaps one of the most important things to know is that there are
three keys on the remote control: the #, 0, and * (star) keys. The first one is the # sign
so that when an endpoint over scans the video and you see the edges of the video
being cut off on a display, when you identify the specific user, you just press the # and
the MCU will fix this problem automatically and readjust the layout so you can view all
participants as you choose. It’s like saying to the MCU listen, the video is over-
scanned, please fix this and the MCU will do that.
Using the 0 (zero) key—when you press it, you are actually talking with your own
personal video layout assistant and you can select whether you want a standard video
layout or a different video layout and select how many participants you get to see. So
when you press 0 key you can select how many participants you will see, what is
You can also select only to see the active speaker and it’s important to emphasize that
these layout commands only affect your own personal video layout. The other video
participants will see the main video layout as they have already set it up and others are
not affected by your layout changes. Here there is also a recording indication so
everyone will know when the meeting is being recorded.
call disconnects, it doesn't necessarily mean that the call will end, if this is configured as
virtual room in such a way.
For design purposes consider that the Elite 5230 MCU can support up to 120 resources
and a phone call only uses about a quarter port. And this capability is the maximum
number regardless of the increased capacity option.
room viewing a three or four big screen monitor setup, you will see a video layout on the
big screens with the active speaker images and on the bottom of the screens, you will
also see other important information with certain session statistics. This way you can
see a panoramic image of the telepresence system and connect to other types of clients
while understanding important information. You can set up the sessions to see
everything you need to see.
When cascading two MCUs, one of the MCUs is the master MCU and the second one is
the slave MCU. The difference is mainly around the video experience.
Cascading another MCU is not recommended (meaning three level cascading). The
cascading link is SVC based like any video connection between two Radvision
products. Conference control is available for all meeting participants, regardless of the
MCU they are connected to.
would be rejected. Polycom’s solution have two working modes – Fixed and Flexible
Polycom’s Flexible Allocation Mode has serious flaws. The RMX was designed as an
on-demand platform with scheduling and resource reservations requiring the CMA
application. Polycom CMA does not support the RMX in Flexible Allocation Mode. CMA
cannot dynamically track the amount of resources the RMX is using as it does not
communicate the resource load to CMA. Therefore, the RMX must be configured to
Fixed Allocation Mode where the RMX reserves the same amount of resources whether
an endpoint is an HD room or a lower resolution desktop. This is an extreme waste of
based to help insure the conference performance is good. We are using the SVC
benefits of our technology to keep the bandwidth quality optimized over long distances
and the users in Asia will connect into the MCU setup in Asia and that entire group will
be set up for the video meeting that will link to the North American infrastructure.
This cascading design allows that we only consume one time bandwidth across the long
distance connection from the Asian office with the MCU to NYC and that MCU
compared with multiple endpoints each directly connected to New York from Asia, like in
the scenario where there was only one MCU in NYC for the entire session attendees.
The cascading design is important to keep in mind for this type of system network
design—linking is set up by Scopia Management so this cascading is done
transparently for the users. See the Radvision Scopia® Management course for
From the dial plan perspective, everything is the same for all users no matter their
location. That is the dial plan doesn’t care about locations and the video experience is
maintained as a high-quality experience. Technically, the first MCU is a master CPU and
the rest of the MCUs that are in the system design are slaves to the master MCU in
NYC. Slave participants will see continuous presence coming from the master, and it
will also include the active speaker. There is no option to remove the active speaker like
you can with a personal video layout with the master MCU. However this is the small
limitation of this type of design, and in reality not much of an issue.
We only have one level for cascading; that is, only a master and a slave. So you cannot
connect a slave MCU to another slave. But a master can cascade with up to 32 MCU
slaves, so large systems can be supported.