Codian MCU 4500 Series
Codian MSE 8510 Series
Online help (printable format)
Software version 2.4(1)
Download from Www.Somanuals.com. All Manuals Search And Download.
1
Download from Www.Somanuals.com. All Manuals Search And Download.
2
Download from Www.Somanuals.com. All Manuals Search And Download.
3
Download from Www.Somanuals.com. All Manuals Search And Download.
4
Download from Www.Somanuals.com. All Manuals Search And Download.
5
Download from Www.Somanuals.com. All Manuals Search And Download.
The Codian MCU web interface is used for administering the MCU device, managing conferences, users, and pre-
defined endpoints. You can also perform many conference-related tasks using the web interface that you cannot
otherwise do.
When connecting to the Codian MCU web interface, you must log in so that the MCU can associate the session with
your configured user and a set of access privileges. The MCU has a set of configured users, and each user has an ID
and password that are used for logging in.
1. Using a web browser, enter the host name or IP address of the MCU.
2. Click the
3. To log in as the administrator, click the
link on the top right of the screen.
button and enter your assigned User name and Password.
The main menu appears, restricting the available options based on your access privileges. Administrators have full
access; standard users can create new conferences and manage their profiles; guest users typically can access publicly
available conferences.
6
Download from Www.Somanuals.com. All Manuals Search And Download.
Depending on how your system administrator has configured the MCU and conferences on it, you might be able to
join conferences by simply dialing a phone number.
Your system administrator may have configured the MCU to allow you to use your video endpoint to directly dial the
conference by dialing a phone number. You will be required to enter the conference ID, and PIN if required. Or you
may be able to dial by IP address and connect to the auto attendant. See Using an auto attendant for details.
Note that some video endpoints require that you activate the keypad before dialing. For example, you might need to
press the # key.
If your phone system allows calls to the MCU, you may use your regular phone to join conferences as an audio-only
contributor. You must enter the conference ID (and PIN, if required).
If your regular phone number is linked to your video endpoint, then when you use your phone to join a conference,
the video portion of the conference will automatically appear on your video endpoint's screen. You can continue to
use your regular phone for the audio portion of the conference. To do this, the video endpoint must be configured as
that user's associated video endpoint. For more information, refer to Adding and updating users.
The advantages to this method are that you are able to use the same method and phone to make video calls as you do
traditional audio calls. You also may have improved audio signaling. However, this method requires significant
configuration and setup from the system administrator. Your company's network may not have all the components
available to support this method.
When in a conference using an audio-only phone, pressing *6 mutes your phone such that you will not be
contributing audio to the conference; pressing *6 again unmutes you phone.
Audio-only conference participants can show a recording from a Codian IP VCR as their video contribution. To do
this:
1. Either register the MCU and the IP VCR with the gatekeeper or add the IP VCR as an H.323 gateway.
2. Go to
>
and add the recording as an H.323 endpoint:
i.
Set the address as the recording number.
ii.
If you are using a gatekeeper, leave the other fields at their default settings; if the IP VCR is set up
as an H.323 gateway, choose the VCR from the H.323 gateway list and leave all other settings as
default.
3. Go to
>
setting the associated video endpoint as the IP VCR recording.
7
Download from Www.Somanuals.com. All Manuals Search And Download.
Your system administrator may have set up an auto attendant for you to use to join conferences. An auto attendant
presents you with a series of menus from which you can choose a conference to join.
For further information about accessing conferences (including the use of DTMF tones), refer to the document
"Accessing Conferences", available in the Documentation area of the web site.
There are typically two ways to call an auto attendant using your video endpoint. Your system administrator should
provide you with information about which method you should use:
Enter the IP address or host name of the MCU device
Dial using a standard E.164 phone number
When you successfully connect to the MCU, the main menu displays on your video screen, and you should also hear
the audio instructions.
Navigate the auto attendant using the Far-End Camera Controls (FECC) on your video endpoint. Use the up and
down controls to highlight the option or item you require; use right to make your selection. To return to a previous
menu from a sub-menu, use left.
You can jump to the end of the menu when at the start by using the up control; similarly, you will loop back to the
start if you are at the end and use the down control. Note that there is a scroll bar in the bottom right of the video
display to indicate where you are in the auto attendant menu. From anywhere in the menu, you can jump to the first
entry with #2 and to the last entry with #8.
By default, the number keys on your endpoint are used to join a conference by dialing its numeric ID, followed by a
'#'. If a conference has both a Numeric ID and a Guest numeric ID set, you may enter either ID, and will join the
conference as either a chairperson or guest as appropriate. As you start to enter a numeric ID, the sequence you have
typed will be shown at the base of the auto attendant screen. You may cancel the numeric ID entry (for instance to
correct an error) by pressing '*'.
If you have connected to the auto attendant using an endpoint that has no FECC capability (for example many SIP
endpoints), you can use the number keys on your endpoint to navigate the menus; this is called "DTMF navigation
mode". DTMF navigation mode enables you to use the number keys: 2, 4, 6, and 8 in the place of up, left, right, and
down respectively.
To enter DTMF navigation mode:
on connecting to the auto attendant, press the pound (hash) key twice as follows:
##
The message "DTMF menu navigation enabled" appears briefly at the bottom of the auto attendant display.
To exit DTMF navigation mode:
press the pound (hash) key twice as follows:
##
The message "DTMF menu navigation disabled" appears briefly at the bottom of the auto attendant display.
8
Download from Www.Somanuals.com. All Manuals Search And Download.
When in DTMF navigation mode, you will not be able to use the number keys to enter the numeric ID of a
conference.
Typically, you will have these options:
This option enables you to start a new conference that takes place immediately (an "ad hoc" conference). When
creating this conference, you'll need to add a conference ID and optional PIN (to restrict access to the conference).
Other participants are then free to join the conference as they would any other, for example by using the auto
attendant, or by calling in directly (see Calling into conferences).
As the system administrator, you can disable this option so it is not available on an auto attendant.
All permanent conferences or conferences scheduled to take place (at this time) display here, listed by the conference
name. Your system administrator can limit the conferences that display here. So, if you do not see the conference you
want to join, verify the conference name, start time, and finally verify that your system administrator has enabled the
conference here.
Your system administrator may allow this auto attendant to access additional auto attendants, giving you access to
additional conferences.
After you join a conference, the in-conference controls and features are the same regardless of how you joined the
conference (see Using in-conference features).
When you want to leave a conference, you can either simply hang up, or if you joined the conference from an auto
attendant and want to return to the auto attendant:
if you are using FECC, press zoom out. The zoom out menu is displayed; choose
if you are using DTMF tones, press 7. The zoom out menu is displayed. Press 8 to navigate down through
the options and 6 to select
9
Download from Www.Somanuals.com. All Manuals Search And Download.
The streaming interface enables you to enter the ID of a conference and view it in a web browser on your PC. You do
not have to have a user account on the MCU to be able to do this.
If you do need to log in to the MCU, use the
link on the top right of the screen.
A name by which you will be identified should
you use the text chat facility.
Note that text chat will not be available unless the
MCU has the Web conferencing feature key
The numeric ID that uniquely identifies the
conference you want to stream.
If the conference that you want to stream is
protected by a PIN, enter it here.
Select the streaming rate you prefer to use.
There are usually two configured options for
streaming rate from which you can choose.
When enabled, multicast will be used when
streaming this conference.
This option is not available if the streaming rate
specifies that Windows Media Player will be
used.
When enabled, the MCU's streaming page will
attempt to access the multicast meadi stream for
the chosen conference. Note that if the streaming
page fails to stream the conference, you can
return to the this page and uncheck this option;
doing so will cause the MCU to attempt to
stream the conference using unicast.
Check this option to stream the audio and video. If you uncheck this option, then neither the audio
nor video will play.
Choose a size (resolution) for the video.
This option affects the size of the media player
when it opens.
Check this option to stream the content channel. If you uncheck this option, the content channel
will not play. Unchecking this option also disables
text chat.
Note that text chat will not be available unless the
MCU has the Web conferencing feature key; and
that without the Web conferencing feature key,
this option is grayed out.
Choose a size for the content channel.
10
Download from Www.Somanuals.com. All Manuals Search And Download.
The Codian MCU supports streaming, which involves sending conference media (audio and video) to a remote
computer, allowing the user to watch and listen to a conference. The media flows in just one direction, so it is not
possible to actually contribute to a conference via streaming.
The streaming video may be delayed by approximately 4-10 seconds compared to the real-time video.
To view an active conference using streaming:
1. Go to
and click
next to the conference name.
2. Choose the Streaming rate. Refer to the table below for tips.
3. If you want to display and choose advanced streaming settings, click the link. Choose the settings you
require, referring to the table below for tips.
4. Click
to display the conference.
The configured options for streaming video.
The two options available here have been
configured on the page.
>
If multicast is enabled for the selected streaming Multicast streaming allows an unlimited number
rate on the page and you of viewers to watch a conference on a MCU.
select Prefer multicast, then multicast will be used Note that you cannot use Windows Media Player
when streaming this conference. to stream in multicast mode on the MCU.
>
Check this option to stream the audio and video. If you uncheck this option, then neither the audio
nor video will play.
Choose a size (resolution) for the video.
This option affects the size of the media player
when it opens.
Check this option to stream the content channel. If you uncheck this option, the content channel
will not play. Unchecking this option also disables
text chat. Note that text chat will not be available
unless you have the Web conferencing feature
key; and that without the Web conferencing
feature key, this option is grayed out.
Choose a size (resolution) for the content
channel.
This option affects the size of the media player
when it opens.
11
Download from Www.Somanuals.com. All Manuals Search And Download.
After you join a conference, you can control many conference features directly from your video endpoint. (For
information about in-conference features using the web interface, see Controlling in-conference features).
Understanding in-conference status icons
The conference welcome message
For further information about accessing conferences (including the use of DTMF tones), refer to the document
"Accessing Conferences", available in the Documentation area of the web site.
Your video endpoint typically has navigation keys, such as up/down and left/right (on a keyboard or remote
control), that allow you to control the camera viewing angles. When connected to a conference, you can also use
these controls to scroll through participants and conference layout formats (see Understanding how participants
display in layout views).
When you join a conference, you will have a set of available layout options from which you can choose to display the
conference participants. Typically you can choose from two primary groupings of layouts:
— in these formats, all conference participants display in the same size pane on the video
screen and thus have the same level of focus or importance. For example, a conference with four participants
might display each in a pane sized to be a quarter (1/4) the size of your video screen.
— in these formats, conference participants display in various pane sizes on the video
screen depending on their ―importance‖. For example, a layout might display the participant who is speaking
in a pane larger than the other conference participants. Or, you might choose to focus on a particular
participant (see Selecting participants)
To switch among available conference views:
1. Change the camera control to ―far‖.
2. Use the up/down navigation keys to toggle through the available format options.
3. Refer to the table below for assistance interpreting the icons that appear on-screen.
12
Download from Www.Somanuals.com. All Manuals Search And Download.
You are scrolling up through the layout views.
You are scrolling down through the layout views.
You have stopped scrolling through the layout views.
When viewing a conference with variable-size panes (see Variable-size panes), you can choose which participant to
display in the larger panes on the video screen; when viewing a conference with equal-sized panes, you can choose
which participant displays in the top left pane. You do this by selecting the participant following these steps:
1. Change the camera control to ―far‖.
2. Choose a layout view.
3. Use the left/right navigation keys to scroll through the focused participants.
4. Refer to the table below for assistance interpreting the icons that appear on-screen.
You are scrolling through the participant list in a counter-clockwise direction.
You are scrolling through the participant list in a clockwise direction.
Speaking participant has the focus.
13
Download from Www.Somanuals.com. All Manuals Search And Download.
During the conference, various icons might appear in the pane of specific participants. Refer to the table below for
assistance interpreting these icons.
This participant has been given priority in the layout views.
A participant is made "important" using controls on the MCU web pages.
The audio quality from this participant is poor.
The audio quality from this participant is good.
The video quality from this participant is poor.
The video quality from this participant is good.
While in a conference, you might need to change the camera settings for one of the conference participants. For
example, if you want to zoom in on a particular speaker in a large group, or if you cannot see the speaker. To do this:
1. Change the camera control to ―far‖.
2. Select the largest displayed participant pane.
3. Press Zoom. The far-end camera control icon appears, and you can now control the far-end camera.
4. Refer to the table below for assistance interpreting the icons that appear on-screen.
You are now controlling the viewing angle of the far-end video camera.
You are moving the remote far-end camera down.
You are moving the far-end video camera up.
You are moving the far-end video camera to the left.
You are moving the far-end video camera to the right.
You are zooming in with the far-end video camera.
You are zooming out with the far-end video camera.
14
Download from Www.Somanuals.com. All Manuals Search And Download.
During the conference, various icons might appear in top left of the conference display. The appearance of these icons
is controlled on the
below for assistance interpreting these icons.
There are both encrypted and unencrypted participants in this conference or there are streaming viewers of
this encrypted conference.
This conference is being recorded.
There are audio-only participants in this conference. The number of audio-only participants is displayed
next to the icon.
There are streaming participants in this conference.
The zoom out menu provides access to a number of in-conference options. Access the following options by pressing
zoom out if you are using FECC, or 7 on a DTMF keyboard (on an endpoint that does not have an FECC channel):
widescreen mode (whether this option is available or not depends on the
setting on the
page and on the capabilities of the endpoint)
borders
mute audio
mute video
clear text chat (this option only appears if there is text chat on the screen)
return to auto attendant (this option only appears if the participant joined the conference from the auto
attendant)
You can configure a welcome message on the MCU and a duration for that message. Participants joining a conference
on the MCU will see the message displayed at the bottom of their endpoint's display. After the configured message
duration has elapsed, the message will be removed.
The
controls are on the
conference settings).
The welcome message will only be displayed to streaming viewers if the duration is configured as permanent.
If you change the welcome message when there are active participants, any participants’ currently displayed welcome
messages will only change if the new message is configured as
.
15
Download from Www.Somanuals.com. All Manuals Search And Download.
Depending on how your video endpoint is configured, an incoming video call might come through to your regular
phone or to your video endpoint (see Calling into conferences for a brief description of the difference). Note that
even if a video call arrives on your regular phone, the video portion of the call will appear on your associated video
endpoint (if one is configured).
As with any other type of incoming call, you can choose to answer the call or not.
16
Download from Www.Somanuals.com. All Manuals Search And Download.
The default behavior of the Codian MCU is to display the "loudest" participants in the most prominent layout panes.
If there are more contributors than there are panes available, then the "quietest" participants are not shown.
However, different styles of layout introduce slight subtleties to this behavior, and in addition there are a few ways in
which participants or conference administrators may change the system used for pane assignment. In particular, you
may want to set the pane placement for a conference yourself.
In this section:
H.243 floor control
This layout can be seen as the most traditional video-conferencing view. Each participant is displayed in the same
sized pane as the other participants. If there are more than four participants, the four most significant (the four
loudest) are displayed, with one pane each.
By contrast, these example layouts have some larger panes, and the participants shown in those panes are seen as
more significant than the other contributors. When allocating participants to panes, the MCU always fills the largest
panes first. If there are more participants than panes then there will never be empty big panes and non-empty small
panes.
To reduce the number of view changes when different participants speak (for example, when people change from
being active speakers to inactive contributors), the MCU duplicates participant views for layouts with more than four
small panes. For the three example layouts shown above, the participant(s) shown in the large pane(s) of the first two
layouts will be duplicated in the surrounding small panes. However, the four small panes of the third layout will show
different participants to those displayed in the three big panes. This reduces the impact of audio volume changes on
the composed layout while not needlessly wasting view space. However, it is possible to configure the MCU not to
duplicate participant views in this way if so desired (see Configuring global conference settings).
17
Download from Www.Somanuals.com. All Manuals Search And Download.
When considering which participants to show in which panes, a participant's self view has the lowest priority. This
has two main implications:
When choosing participants to display, the MCU considers the viewer last. This prevents the participant
who is the active speaker from seeing only themselves. In this case, while everyone else will see the active
speaker, the active speaker will see the previous active speaker in their biggest view pane.
When the MCU is required to choose a layout from a view family, it does so based on the number of video
contributors to the conference. However, when calculating the number of video contributors for a
particular view, the MCU does not consider any video stream being received from the viewer.
Thus, with five participants in a conference and everyone seeing the standard equal-sized view family (2x2,
3x3 or 4x4), each of the five contributing participants will always see the 2x2 view with themselves
excluded. However, streaming viewers will see the conference display using the 3x3 view with five panes in
use.
You may configure the MCU never to show participants their own video stream in small panes (see Configuring
global conference settings). If this is the case, then participants viewing layouts with some panes larger than others
will never see their own video stream in any of the small panes, even if there are free slots. They may still appear in
large panes, for example if the view focus is manually changed to show their video.
Using the tilt (up and down) Far End Camera Controls on a connected video endpoint causes the view to change,
cycling through the available families and then the conference-wide or per-participant custom layouts (if enabled).
In addition, the pan (left and right) Far End Camera Controls on a connected video endpoint can be used to focus the
view on a particular participant, as opposed to the MCU allocating participants to panes based solely on the volume of
the audio being received from them.
To reduce the disruption of the view when cycling through conference participants, there is a short delay after
selecting a new focused participant before the rest of the view layout reverts to the "correct" arrangement of
participants in panes.
For each conference, one active participant can be set as "important". This means that the MCU considers this
participant first when deciding which contributors to show in which layout panes, rather than their position in the list
being set by how loudly they are speaking. See the Control setting in the conference participant list.
18
Download from Www.Somanuals.com. All Manuals Search And Download.
Both "Changing view focus" and "Important participants" above involve a single specific participant being shown in
the biggest pane available, even if that participant is not currently the loudest speaker. This causes a potential conflict,
which is resolved dependant on the type of layout.
In this type of view (a layout in which all panes are of equal size), the focused participant is shown in the first pane,
the one at the top left. The important participant is shown in the "next" pane, normally the one immediately to the
right of the first pane.
This type of layout displays a single big pane and several small panes. If the view focus has been changed (for instance
with left and right Far End Camera Control operations), then the big pane shows the selected participant. If a
conference participant has been set to "important" then its video stream is shown in the big pane.
However, if a participant has been set to "important" and the view is focused on a (different) specific participant, the
focused participant is shown in the big pane, and the "important" participant is shown in one of the small panes.
If the view has been focused on a participant and the same participant is also set as "important" then that participant is
shown in the big pane.
These layouts have two large panes and several smaller ones. If the view focus has been changed (for instance with left
and right Far End Camera Control operations), then the upper or left large pane shows the focused participant. If a
participant has been set to "important" then that video stream appears in the lower or right large pane.
If the same participant is focused and "important", that video stream appears in the upper or left pane.
For these layouts, if the view has been focused on a particular participant, that participant appears in the upper or left
large pane. If a participant has been selected as "important", that participant will be shown in the lower or right large
pane.
In layouts with three large panes, even if the view is focused on a specific participant and another has been set to
"important", one large pane remains. This pane displays the "loudest" remaining participant.
19
Download from Www.Somanuals.com. All Manuals Search And Download.
The majority of the conference layouts defined by the Codian MCU, for example:
have in common that all of their panes, whether big or small, have the same aspect ratio as the view itself. That is, the
panes' widths and heights are in the same proportion as the width and height of the encompassing view.
By comparison, there are some defined conference layouts, for example:
in which this aspect ratio preservation does not occur. In these cases, the MCU scales the participant video stream
according to the larger dimension of the pane.
For example, in the layout to the left, the size of the top left pane is one half of the view width and two thirds of the
view height. Because two thirds is greater than one half, the MCU scales the participant video stream to two thirds of
its size and thus a small amount of the left and right of the original image will not appear in the final composed layout.
For video conference participants, the image that displays in the layout view pane is either the live video stream (if
viewing from the video endpoint) or a captured video image from the current video stream (if viewing from the web
interface).
However, audio-only participants do not have any associated video to display. Instead, you can assign a fixed image
(in bitmap format) to a specific participant. When the participant joins a conference as an audio-only participant, this
image appears in the layout pane. To enable this feature, the participant must be added as a user to the MCU, have an
associated E.164 telephone, and have a designated image file uploaded. See Adding and updating users.
Participants who have had their audio muted from the web interface do not contribute audio to the conference.
Additionally, muted participants are not considered when the MCU calculates the loudest speakers to display in the
largest panes, even if the participant had previously been in one of those positions.
Note that other participants will not have an indication that a participant has been muted. They simply will no longer
hear that participant speaking.
Participants who have had their video muted from the web interface do not contribute video to the conference. They
will continue to contribute audio as normal, unless it is muted separately.
20
Download from Www.Somanuals.com. All Manuals Search And Download.
Some H.323 endpoints support a feature known as floor and chair control that is encompassed by the H.243
protocol. This is not currently supported by SIP.
The MCU supports the following H.243 features:
a participant can "take the floor" in a conference. On "taking the floor" their video contribution is sent to all
conference participants as a "1 x 1 view" (full-screen view). If the active floor (temporarily or permanently)
has no video channel established to the MCU then endpoints will see their "normal" continuous presence
view; if there is a video channel from the active floor participant, everyone will see that video, and this will
override any view family or custom layout setting
a participant can "take the chair". On "taking the chair", a participant can:
o
nominate a "broadcaster"; that is, they can choose which participant's video will be sent to all other
participants in "1 x 1 view" (full-screen view)
o
decide to disconnect any other participant(s)
Note that the ability of a participant to "take the chair" is affected by how they joined the
conference. A participant who joined the conference as a guest will not be able to "take the chair".
an endpoint can receive the names of the other endpoints in the same conference. Different endpoints act on
this in different ways.
Whether or not these features are supported in a conference depends on the individual conference settings
(
) and the global "H.243 floor and chair control setting" (
). Refer
to Adding and updating conferences and Global conference settings.
Where a conference supports floor and chair control, or floor control only:
the MCU will advertise the ability to handle H.243 when establishing (and receiving) H.323 connections
any H.243-capable endpoint can request the floor, and all endpoints (be they chairperson or guest) will be
granted it as long as no other endpoint in that conference has already done so
Where the conference supports floor and chair control:
any H.243-capable endpoint can request the chair, and any participant who has joined the conference as a
chairperson will be granted it as long as no other endpoint in that conference has already done so
If an active participant in a conference has taken the chair or the floor, it is indicated in the status column of the
page.
If you change the "Floor and chair control" for a conference currently taking place, there will be no immediate effect.
That is, an existing floor or chair participant will not have that status removed.
For ad hoc conferences, you can alter the "Floor and chair control" setting, which is "Allow floor control only" by
default, through that conference's configuration page when it is active.
21
Download from Www.Somanuals.com. All Manuals Search And Download.
The Conference List displays information about active, scheduled, and completed conferences. To access this list,
choose
.
Review this information for explanations about the details that display:
Completed conferences
Active conferences are currently in progress. The following information is displayed for each conference:
Displays the conference streaming page. This
option is not necessarily available for every
conference; some users do not have access to
other user's conferences. Some conferences may
require a PIN to access this feature.
more information.
The name of the conference, which is either the Specialized conference types are described below
name entered when the conference was
scheduled, or, in the case of certain specialized
types of conferences, a name chosen
in Description.
Click the conference name to display detailed
information about the conference and
participants.
automatically by the MCU when created.
Additional information about the conference,
which can assist users joining conferences.
You can add the description when scheduling a
conference. If you do not add a description or the
conference has not been scheduled in advance, the
Description displays one of the following:
The conference has been scheduled in
advance using the MCU web interface,
but the owner has not entered a
description.
The conference was created dynamically
during an auto attendant session and will
end when the last participant using the
auto attendant exits the conference.
This type of conference indicates that a
participant is currently connected to the
auto attendant and navigating the menus.
The configured owner of the conference.
information.
22
Download from Www.Somanuals.com. All Manuals Search And Download.
The status of a conference with respect to its
H.323 gatekeeper and/or SIP registration.
If the MCU can connect to an H.323 gatekeeper,
each numeric ID (for both chairperson and guest
Depending on the conference settings, there is a privileges) for a conference can be registered with
maximum of four registrations for each
conference: H.323 numeric ID, H.323 guest
numeric ID, SIP numeric ID, and SIP guest
numeric ID. The Registration field will show
that gatekeeper as a different directory number.
This allows H.323 users to dial directly into a
particular conference (with the correct privileges)
instead of connecting first to the MCU's auto
failed if any of the registrations has not completed attendant and navigating the menu system.
successfully.
Likewise, if the MCU can connect to a SIP
registrar, each conference can be registered with
This conference is not configured to be
registered with a gatekeeper or SIP
registrar; because of this, there is no
applicable registration status to show
that registrar using either (or both) Numeric ID
and Guest ID. This allows SIP users to dial
directly into a particular conference (with the
correct privileges) instead of connecting first to
the MCU's auto attendant and navigating the
menu system. Note that for SIP, unlike H.323,
the conferences must be configured on the SIP
registrar before the MCU can register them.
This conference is in the process of
registering with the gatekeeper or SIP
registrar
There is a maximum of four registrations for each
conference: H.323 numeric ID, H.323 guest
numeric ID, SIP numeric ID, and SIP guest
numeric ID. To view further details about the
registrations for a conference, click the
conference name and then the Statistics tab to
At least one of the registrations for this
conference has failed
All IDs associated with this conference
have been registered successfully with
the gatekeeper / SIP registrar
One or more of the IDs associated with
this conference has been configured to
be registered with the gatekeeper or SIP
registrar, but that registration has not
been attempted due to another setting
taking precedence. This might occur if
either of the H.323 gatekeeper usage or ID
registration for scheduled conferences options
For tips on configuring gatekeepers, see
For tips on configuring SIP registrars, see
For more information about configuring
conferences (and chairperson and guest IDs and
on the
page is set
to Disabled
Note that when there is a problem with the
registration, the status is a link to the conference's
Statistics page.
The number of currently active contributors to
the conference. This value does not include
If a conference is protected by a PIN, the number
of participants is hidden until the PIN is entered.
streaming viewers or any other endpoints that are In this case, the Participants value displays as
viewing only and not contributing any media to <PIN required>.
the conference.
If a limit on the number of participants has been
set for the conference, the participants value is
shown as
, where is the number of active
participants and is the configured limit. If it has
not been possible to reserve all of the required
23
Download from Www.Somanuals.com. All Manuals Search And Download.
ports for a conference (for instance because of a
configuration error), this value will display in red
as an error indication.
When the conference began. If the conference
started before today, the date also displays.
How long the conference still has to run. If the
conference does not have a limited duration, this
column displays as <forever>.
Scheduled conferences are either in progress or are yet to start. You can review this list and make some changes to it:
To remove a scheduled conference, select the conference via its associated checkbox and click
.
To schedule a new conference, click
The MCU supports up to 200 scheduled conferences.
The name of the conference chosen when the
conference was scheduled.
Click the conference name to display detailed
information about the configuration of the
conference and, if it is currently active, its
participants.
The number that you can dial to join the
conference.
Whether a PIN is required to join the conference.
The configured owner of the conference.
information.
Whether a conference is:
There is no explicit status for "finished" – when a
conference is not in progress and is not scheduled
to become active again then it is moved to the
Completed conferences list.
The conference's configured start time
has not yet arrived.
The conference is running and is
available for video conferencing
endpoints to join. A scheduled
conference in this state will also appear
in the Active conferences list.
The conference is not currently running,
but has been previously active and is now
waiting to be re-activated when the time
of its next repetition is reached.
When the conference began. If the conference
started before today, the date also displays.
When the conference will end.
24
Download from Www.Somanuals.com. All Manuals Search And Download.
Completed conferences have finished and are not scheduled to repeat.
To remove specific conferences from the list, select the conferences via their associated checkboxes and click
.
To remove all conferences from the list, click
.
The name of the conference chosen when the
conference was scheduled.
Click the conference name to display detailed
information about the configuration of the
conference.
The configured owner of the conference.
information.
When the conference began. If the conference
started before today, the date also displays.
When the conference ended.
25
Download from Www.Somanuals.com. All Manuals Search And Download.
The information required to add or update a conference is nearly identical. Refer to these topics for details:
Using IDs and PINs
To add a conference:
1. Go to
2. Complete the fields referring to the table below for the most appropriate settings for the conference.
3. Click to add the conference and return to the Conference List. The recently added
.
conference appears either in the Active or Scheduled Conferences depending on its scheduled start time.
Ad hoc conferences (if you allow them) are added by users in the auto attendant.
To update an existing conference:
1. Go to
2. Click a Conference name and then click the
3. Edit the fields referring to the table below for the most appropriate settings for the conference.
4. Click to add the conference and return to the Conference List. The updated conference
.
tab.
appears either in the Active or Scheduled Conferences depending on its scheduled start time.
The following settings can also be updated for ad hoc conferences:
PIN
Layout control via FECC/DTMF
Streaming
Encryption
Floor and chair control
Mute on join
See the table below for more information:
26
Download from Www.Somanuals.com. All Manuals Search And Download.
The name that users will see on auto attendant
screens and on the MCU's web interface.
Conference names must be unique; conferences
cannot share names.
Only scheduled conferences have a configurable
Name; ad hoc conferences do not have one.
Additional information about the conference,
which can assist users joining conferences.
Use the description to provide more detailed
information about the conference than the name
alone conveys.
This is an optional field for scheduled
conferences; ad hoc conferences cannot be given
a description.
The unique identifier used for dialing in to the
When connected to an auto attendant,
conference (as a chairperson participant) using an participants can join a conference by typing its
auto attendant or through an H.323 gatekeeper or numeric identifier.
SIP registrar. This number can also be used to
If you plan to allow audio-only participants, then
stream the conference from the Streaming-only
you will need to enter either a Numeric ID or a
interface. For more information about
Guest numeric ID.
If H.323 gatekeeper registration is enabled for a
conference, the MCU attempts to register the
conference with an E.164 telephone number,
which is comprised of the Registration prefix and
the numeric identifier.
If SIP registration is enabled for a conference,
then the Numeric ID is registered with the SIP
registrar.
Conferences that are simultaneously active must
not share a Numeric ID. For example, a conference
on a Tuesday and a conference on a Thursday can
share a Numeric ID, whereas two permanent
conferences cannot share a Numeric ID. The same
number can be used for the Guest numeric ID, if
there are two different PINs. Additionally,
because the numeric identifier is used in
gatekeeper registration, conferences and auto
attendants cannot share a numeric identifier
value.
For more information, refer to Using IDs and
For ad hoc conferences created via the auto
attendant, the number allocated by the
conference creator becomes the Numeric ID. If ad
hoc conferences are registered with the
gatekeeper (and for this to work, the Register ad
hoc conferences with gatekeeper control must be
27
Download from Www.Somanuals.com. All Manuals Search And Download.
enabled on the
page),
participants can dial in using this number. Note
that the actual number that participants will dial
depends on whether prefixes are used in the
page.
For an active ad hoc conference, you cannot
configure the Numeric ID.
Provides a level of security to conference access. If a conference has a PIN set, users cannot join
the conference or change its configuration
without entering the correct PIN. Depending on
the conference settings, it may be possible for
participants to join a conference as a chairperson
(using the Numeric ID and PIN), or as a guest
(using the Guest numeric ID and Guest PIN).
For an ad hoc conference, you can configure a
PIN while the conference is running.
The unique identifier used for dialing in to the
When connected to an auto attendant,
conference (as a guest participant) using an auto participants can join a conference by typing its
attendant or through an H.323 gatekeeper or SIP Guest numeric ID.
registrar. This number can also be used to stream
If you plan to allow audio-only participants, then
the conference from the Streaming-only interface.
you will need to enter either a Numeric ID or a
For more information about chairpersons and
Guest numeric ID.
If H.323 gatekeeper registration is enabled for a
conference, and you have entered a Guest
numeric ID, the MCU attempts to register the
conference with an E.164 telephone number,
which is comprised of the Registration prefix and
the Guest numeric ID.
If SIP registration is enabled for a conference, and
you have entered a Guest numeric ID, then the
Guest numeric ID is registered with the SIP
registrar.
Conferences that are simultaneously active must
not share a Numeric ID. For example, a conference
on a Tuesday and a conference on a Thursday can
share a Numeric ID, whereas two permanent
conferences cannot share a Numeric ID. The same
number can be used for the Guest numeric ID, if
there are two different PINs. Additionally,
because the numeric identifier is used in
gatekeeper registration, conferences and auto
attendants cannot share a numeric identifier
value.
For more information, refer to Using IDs and
Ad hoc conferences cannot be configured with
Guest numeric IDs or PINs.
28
Download from Www.Somanuals.com. All Manuals Search And Download.
Provides secure access to conferences for guest
participants.
If a conference has a PIN set, users cannot join
the conference or change its configuration
without entering the correct PIN. Participants
joining as guests have restricted privileges. For
Ad hoc conferences cannot be configured with
Guest numeric IDs or PINs.
Enables the MCU to attempt to register the
Numeric ID and/or Guest numeric ID with the
configured H.323 gatekeeper and/or SIP
registrar.
This setting applies to both the Numeric ID and
Guest numeric ID (if you have set both). For
For ad hoc conferences, whether or not they are
registered with the gatekeeper depends on the
Register ad hoc conferences with gatekeeper setting on
the
page.
Controls what happens to the conference when
This setting applies to scheduled conferences that
the last participant with chairperson status leaves include guest participants (that is, those who have
the conference. The options are:
joined the conference using the Guest numeric ID
(and PIN if one was set).
: this is the
default option. When the last participant
with chairperson status leaves the
conference, all other participants will be
disconnected
: all participants may
continue the conference until the last
one disconnects
Controls "Floor and chair control" settings for
this conference. The options are:
Some H.323 endpoints support a feature known
as floor and chair control that is encompassed by
the H.243 protocol. For more information, refer
: the
use of floor and chair controls is not
allowed in this conference
If you change the "Floor and chair control"
setting for a scheduled conference currently
taking place, there will be no immediate effect.
That is, an existing floor or chair participant will
not have that status removed.
: only floor
control is allowed in this conference;
chair control is not allowed. Any
participant can 'take the floor' so long as
no other participant has currently 'taken
the floor'
If the unit-wide "Floor and chair control" setting
Disabled, it will not be possible to use floor or
chair control operations in any conference.
: both floor
and chair control are allowed in this
conference. Any participant can take the
floor, and any chairperson participant
can take the chair so long as no other
participant has currently done so
The owner of the conference, usually the user ID You may or may not be able to change the
of the user account that the person who scheduled conference owner, depending on your privilege
the conference logged in with.
information.
This setting does not apply to ad hoc conferences.
29
Download from Www.Somanuals.com. All Manuals Search And Download.
Indicates the visibility of the conference on the
For private conferences not visible on an auto
auto attendant and the web interface. The options attendant, participants will still be able to join the
are:
conference if they know the PIN.
: the conference will be listed in
the auto attendant and be visible to all
users of the web interface
: the conference will not be listed
in any auto attendant except for auto
attendants specifically set to show it. The
conference will also only be visible in the
web interface to the conference owner
and to the admin user
Note that only admin users can choose which
conferences are visible on a given auto attendant.
This setting is only available for schedules
conferences. For ad hoc conferences, whether or
not they are listed on the auto attendant depends
on the settings of that auto attendant. For more
information, refer to Adding and updating an
The encryption setting for this conference, if you If encryption is enabled unit-wide (through the
have the encryption feature key enabled.
>
page), you can set one of:
: encryption must be used for
this conference
: encryption is optional for this
conference
This setting is grayed-out if encryption is disabled
on the
>
page.
Note that to be able to use encryption, the
Encryption feature key must be present on the
MCU.
Prevents or permits conference participants
You may wish to prevent participants from
changing their view layout or focused participant changing their view layout in a managed
using Far-End Camera Controls or DTMF tones. conference, or classroom environment.
This is a per-conference option, but
FECC/DTMF layout control may still be enabled
or disabled on a per-participant basis using the
web interface.
When calling out to endpoints, the endpoints'
layout control configuration overrides this
setting, and therefore it applies only to endpoints
which connect to the conference via an auto
attendant or by dialing in directly.
Indicates when the MCU should invite any pre- Select which option fits your requirements best.
configured endpoints into a conference. The
options are:
Calling pre-configured endpoints at the start of the
conference is most appropriate for repeating
conferences with a particular start time.
Calling pre-configured endpoints when at least one
other participant is present is most appropriate for
permanent conferences; such conferences are
typically un-attended for much of the time, and it
may only be useful to invite pre-configured
Pre-configured participants will be called
as soon as the conference starts.
Pre-configured endpoints will only be
called after at least one other participant endpoints when others are present.
joins the conference.
This setting only applies to scheduled
conferences.
30
Download from Www.Somanuals.com. All Manuals Search And Download.
Select to initially mute audio and/or video from If you select to mute audio on join, when a
all participants when they join the conference.
participant dials-in to a conference, he will not be
able to contribute audio to the conference. If you
select to mute video on join, when a participant
dials-in to a conference, he will not be able to
contribute video to the conference. You can mute
both audio and video if required.
This can be altered during the course of the
conference by going to
and clicking
on the name of a conference and altering a
participant's settings. For more information about
altering a participant's settings during a
conference, refer to Viewing the conference
Note that for pre-configured participants and for
participants to whom the MCU dials out, the
Initial video status and Initial audio status settings
will be used to determine whether or not audio
and video contributions are muted. For more
information about dialing out to participants,
information about pre-configured participants,
For an ad hoc conference, you can configure the
Mute on join setting while the conference is active.
Individually allow unicast and multicast streaming See Configuring streaming settings for additional
access to conferences.
information.
If Enabled, this conference is able to support an
additional video stream, sent potentially to all
connected endpoints, intended for showing
content video.
information on MCU-wide content configuration
parameters.
For ad hoc conferences, whether or not content
channel video is allowed is controlled by the
Content for ad hoc conferences setting on the
page.
This content video is typically high resolution,
low frame rate data such as a presentation formed
of a set of slides. Such presentation data can be
sourced by:
an endpoint specifically contributing a
separate content video stream,
the MCU being configured to use an
endpoint's main video stream as the
conference's content channel,
a dedicated VNC connection,
or user-generated markup data (the
markup is normally, though not always,
used in conjunction with content video
or VNC data).
31
Download from Www.Somanuals.com. All Manuals Search And Download.
Whether, by default, endpoints are permitted to If this setting is Disabled, it is still possible to
contribute the content channel for a conference enable content contribution on a per-endpoint
through the mechanism of opening a content
video channel.
basis when the conference is active. Similarly, it is
possible to disable content contribution from
specific endpoints, either while they are
connected or via their configuration. For more
information about endpoint configuration, refer
Configuring SIP endpoints.
There can only be one endpoint contributing
content video at any one time, and the MCU
arbitrates between them. Therefore, even with
this parameter set to Enabled, the ability of the
endpoint to contribute content video will be
affected by other endpoints' behavior.
This setting only applies to scheduled
conferences.
When the MCU is not in port reservation mode, If you do not want to limit the number of
this parameter sets a limit on the number of participants who can join this conference and use
endpoints which can connect to the conference as video, leave this field blank.
video participants.
This field is only shown if the MCU is not in port
A participant counts (as a single unit) towards the reservation mode.
video limit whether the MCU is sending a video
stream to that participant or a video stream is
being received.
This field only applies to scheduled conferences.
When the MCU is not in port reservation mode, If you do not want to limit the number of
this parameter sets a limit on the number of participants who can join this conference to use
endpoints which can connect to the conference as just audio, leave this field blank.
audio-only participants.
This field is only shown if the MCU is not in port
A participant counts (as a single unit) towards the reservation mode.
audio limit whether the MCU is sending an audio
stream to that participant or an audio stream is
being received.
This field only applies to scheduled conferences.
In port reservation mode, this parameter specifies This value is both a reservation and a limit; the
the number of video ports to reserve.
MCU guarantees that this many video participants
can connect to the conference, but no more than
this will be able to join.
A participant counts (as a single unit) towards the
video reservation value whether the MCU is
sending a video stream to that participant or a
video stream is being received.
This field is only shown if the MCU is in port
reservation mode.
In port reservation mode, this parameter specifies This value is both a reservation and a limit; the
the number of audio-only ports to reserve.
MCU guarantees that this many audio-only
participants can connect to the conference, but
no more that this will be able to join.
A participant counts (as a single unit) towards the
audio reservation value whether the MCU is
sending an audio stream to that participant or an This field is only shown if the MCU is in port
audio stream is being received.
reservation mode.
The time at which the conference will begin.
The date on which the conference will begin.
32
Download from Www.Somanuals.com. All Manuals Search And Download.
Sets the conference start time to the current time The current time on the MCU is determined by
on the MCU.
the settings in the
page, which
can only be modified by the administrator. See
Displaying general status for additional
information.
Allows you to retain a conference and its settings
for an infinite period of time.
Limits the duration of the conference for one
instance of the conference.
These fields are not available or necessary for
conferences set to permanent.
Which days and / or weeks the conference
repetitions will occur.
The start date is taken into account when
determining when the first repetition should
occur. For instance, if the start date is a
Wednesday and the conference is scheduled to
repeat every Monday, Tuesday and Wednesday
then it will occur only on Wednesday in the first
week and on all three specified days in subsequent
weeks.
The repetitions will always start at the same time
of day: the conference's configured Start time (see
above), and will last for the same amount of time:
the configured Maximum duration.
If a conference is set to repeat, its repetitions can The first activation of a conference counts as a
be configured to go on forever, stop after a "repetition", so configuring a conference to
certain date, or to occur only a certain number of repeat but terminate after 1 repetition is
times. equivalent to it not repeating at all.
You can choose to pre-configure endpoints to be part of a conference. These endpoints will be automatically invited
into the conference by the MCU. This is useful if you regularly invite the same participants into a conference. To
select which previously configured endpoints will be pre-configured for this conference, press
. (This button may also show a number in parentheses to indicate the number of participants that are
currently pre-configured). Refer to Adding participants for more details.
There are two types of conference participant: chairperson and guest. IDs and PINs allow participants to connect to
conferences as the correct participant type.
Chairperson participants use Numeric ID and optionally, PIN; guest participants use Guest numeric ID and optionally,
Guest PIN.
A conference will not begin until the first chairperson joins. This means that guests will see a black screen/hear
silence with on screen text 'Waiting for conference chairperson' and an audio prompt after five seconds and then every
minute thereafter. Streaming viewers will see a black screen/hear silence although mark-up and text chat will work.
You can control the behavior when the last chairperson leaves the conference (that is the When only guests remain
setting). The two options are:
33
Download from Www.Somanuals.com. All Manuals Search And Download.
all participants are disconnected (default)
all participants may continue the conference until the last one disconnects (take no action)
If you set both Numeric ID and PIN, you must set either:
both Guest numeric ID and Guest PIN
or
neither Guest numeric ID nor Guest PIN
If you use a Guest PIN, you must use a PIN. If you use a Guest numeric ID, you must use a Numeric ID.
Note that for a conference Numeric ID and Guest numeric ID can be the same only if the two PINs are different;
likewise, both PINs can be the same if the IDs are different.
Note that participants dragged and dropped into a conference on the web interface will be chairperson participants.
Where no IDs or PINs are configured for a conference, all participants will be chairpersons regardless of how they
join.
Both Numeric ID and Guest numeric ID can be registered with an H.323 gatekeeper and/or SIP registrar to enable
participants to dial in to conferences directly and as the correct participant type. The Numeric ID registration setting
applies to both IDs.
Audio-only participants can be guest or chairperson participants by connecting to a conference using either a Guest or
Chairperson ID. In the case of an audio-only guest, if no chairperson has yet joined the conference, they will hear an
audio prompt informing them of that. The conference will start when the first chairperson joins.
34
Download from Www.Somanuals.com. All Manuals Search And Download.
Each scheduled conference (i.e. conferences that are configured via the web interface with a start time and,
optionally, a duration and repetition) has an associated owner. This owner is the ID of a configured user, and normally
corresponds to the user who scheduled the conference.
Conference ownership affects only web interface control of conferences - in particular, it plays no part in validating
video conferencing endpoints' attempts to join conferences when they connect to the MCU via H.323. Restricting
conference entry in this situation is accomplished via conference (or auto attendant) PINs, as before.
The actual implications of conference ownership depend on the privilege of the user; specifically:
Users with these privilege levels are able to create and own conferences, and are
able to exercise full control of all conferences.
Users with these privilege levels are able to create and own conferences. They
have full control of conferences they own, and limited control of conferences
owned by other users.
Users with these privilege levels are able to create and own conferences. They
have full control of conferences they own, but no control of conferences owned
by other users.
Users with these privilege levels are not able to own conferences or change any
conference's configuration.
35
Download from Www.Somanuals.com. All Manuals Search And Download.
As described above, a user privilege level confers a certain level of control over a conference, with that level of
control possibly depending on whether that user is the conference owner or not. These conference control levels
have the following meaning:
This level of control permits the following operations:
With full conference control, a user is able to disconnect participants, connect
new participants to the conference, and end the conference whenever they want
to.
A user with full conference control can view and modify any aspect of the
conference's configuration. This includes the start time, end time, or repetition
characteristics, whether streaming is enabled, and which endpoints are pre-
configured as participants.
When the conference is in progress, a user with full control is permitted to send a
text message to all connected participants' video displays and change the
Conference custom layout.
Additionally, full control includes all of the operations covered by limited control,
detailed below.
This level of control permits the following operations:
The participant list shows the names of the endpoints currently connected to the
conference, a summary of that endpoint's status and, if they are a video
participant, a thumbnail preview image of the video stream they are supplying.
Thumbnail previews are shown by default, but you can configure the user
interface not to show them. The setting that controls this is the Show video
thumbnail images option on the
page. Note that the MCU
will not show thumbnail previews on the participant list page if encryption is
required for a conference. However, thumbnail previews will be shown for
conferences where encryption is optional and there are encrypted participants.
Via the participant list, it is also possible to mute (or stop muting) individual
disable the participants' ability to affect their own layouts via Far-End Camera
Control or DTMF tones.
This includes being able to choose what view layout (or family) is used for
constructing the conference view being sent to a participant, changing the
36
Download from Www.Somanuals.com. All Manuals Search And Download.
video to that endpoint.
The web interface can be used to send control commands (e.g. pan and tilt) to a
remote participant's camera.
Waveforms of audio channels being sent to, and received from, the participant
can be viewed, audio gain applied, and participant audio can be muted if required.
Textual messages can be sent to an individual participant, and will appear on their
displays.
This allows details of the media streams being sent to, and received from,
participants to be viewed, plus endpoint-specific characteristics to be examined.
This means that none of the above operations are possible. Depending on the
specific privilege level, either the list of scheduled conferences will not be shown
to the user, or the list will be shown but conferences over which the user has no
control will be presented as names rather than hyperlinks.
A user whose privilege level is either conference creation and full control or administrator is also able to change the owner
of a conference. A conference owner can be changed to either a user with conference creation rights or to "none",
signifying that no user should be considered the owner of that conference. Also, when scheduling new conferences,
users with these privileges are able to choose which owner is initially associated with the conference.
If a user account is deleted, any conferences owned by that user have their owner reset to "none".
37
Download from Www.Somanuals.com. All Manuals Search And Download.
The MCU is able, if required, to allocate its available media ports in advance to specific conferences. This means that
it is able to guarantee that a certain number of participants will be able to join that conference, irrespective of how
many other people are using the MCU for other conferences at the same time.
There are three types of media ports available on the MCU,
.
,
, and
For information about the number and type of ports provided by each MCU model, refer to MCU port matrix.
The term video port refers to a port that can be used by a video-conferencing endpoint for a call. Thus, a video port
includes both video
audio streams (bidirectionally) and so the number of video ports available represents the
number of "normal" video calls that the MCU is able to maintain simultaneously.
In general, each endpoint in a conference is able to use either a video port or an audio-only port, though normally the
MCU will assign video ports to video-capable devices and audio-only ports to audio-only devices.
If a video-capable device joins a conference which has just audio-only ports available, the MCU will assign it an audio-
only port – that participant will be able to listen to other people and contribute their own audio to the conference but
the MCU will not transmit video to it (and will not use any video received from it). If an audio-only device such as a
simple telephone joins a conference which has just video ports available, the MCU will assign it a video port, which
includes audio capability. The video capability of that allocation will not be used, but the audio device will be able to
participate as normal in the conference. The exception to this is VNC - because this is a video-only protocol, the
MCU does not permit VNC connections to use audio-only ports.
Streaming a conference requires use of a
or a
. Where streaming and
content channel ports are provided, streaming viewers and conferences' content channel (H.239 or BFCP) video
allocations will use the streaming and content channel ports rather than the available video ports; where streaming
and content channel ports are not provided, streaming viewers and content channel allocations will use available
video ports.
If a streaming and content channel port or a video port is unavailable (or not allocated in advance when the MCU is in
Reserved mode), it will not be possible to stream that conference. If a video port has been allocated for streaming a
conference, any number of streaming viewers will be able to view that conference via streaming, at any combination
of available bit rates.
The total number of media ports available depends on the MCU model; refer to the product datasheets available on
38
Download from Www.Somanuals.com. All Manuals Search And Download.
How MCU media ports are allocated, and which options and settings are available, is controlled by the Media port
reservation setting on the Conference settings page.
This is the mode that the unit runs in when the Media port reservation setting is configured as
that the MCU uses by default. With this scheme, you can specify a maximum value for the number of video and
audio-only ports each conference is allowed to use on the Conference configuration page. These limits are optional,
and by default there is no configured limit.
, and is the mode
The configured limits are strictly maximum values; in particular, setting such a limit does not guarantee that that many
participants will be able to join the conference. It is perfectly possible to set these values such that the sum of the
configured limits across all active conferences exceeds the total number of ports available on the MCU.
This is the mode that the unit runs in when the Media port reservation setting is configured as
. With this
scheme, each conference must be configured with a number of video ports to reserve and a number of audio-only
ports to reserve. These values differ from the maximum port values set in Unreserved mode in a number of ways:
As well as being maximum values (i.e. enforcing limits on the number of conference participants), port
reservation values also guarantee that that many endpoints are able to participate in the conference.
In unreserved mode, it is not necessary to specify a number of video or audio-only ports for a conference. In
reserved mode, however, every conference must have configured reservations for both video and audio-only
ports.
Port reservations guarantee that a certain number of participants will be able to join a conference; because of
this, the MCU will not permit these reservations to be configured such that the total number of reserved
ports at any given time exceeds the total number of ports available. See Clashing reservations for additional
information.
In order to honor configured port reservations, the MCU must ensure that at any given time the number of reserved
ports does not exceed the total media capacity. This entails some level of clash detection when conferences are
scheduled or their configuration changed.
Two conferences are considered to clash if they can ever be active simultaneously. When validating a conference
schedule, the MCU looks at the maximum number of ports reserved by other conferences which can be active at the
same time, and checks that the number of ports requested by the conference being added or changed is guaranteed to
be available. If, for instance, the MCU has 20 video ports available in total, it will not be possible to set up two
conferences which require 15 video ports each if they are scheduled such that they ever overlap.
In the simple case of conferences which start at specific times and end at specific times (or, indeed, are permanent), it
is easy to see whether they clash. The more complex cases involve repetition, and it is important to bear in mind that
39
Download from Www.Somanuals.com. All Manuals Search And Download.
port reservations are only permitted when the MCU can guarantee them for
repetition of a conference. As an
example, a conference scheduled to run from 08:00 to 10:00 on the second Monday of each month will be deemed to
clash with a conference configured to run from 09:00 to 09:30 every Monday, even though the former will only really
clash with the latter every fourth or fifth week.
In general, to make best use of the available MCU media ports, conferences should not be scheduled for longer than
they are needed, and repetitions should be limited, either by end date or number, wherever possible.
Because port reservations are mandatory in
every active conference must have configured values for
the number of video ports and the number of audio-only ports to reserve for it. In turn this means that every active
conference must be configured, and therefore ad hoc conferences are not permitted when in
.
This affects the operation of the MCU in the following ways:
In reserved mode, the Create new conference option will not be shown on video auto attendant menus,
even for auto attendants configured to display this option.
When configuring new or existing auto attendants via the web interface, the Creation of new conferences
parameter will not be available.
This setting on the Conference settings page also offers a Create new conference option. This is not available in
reserved mode and becomes equivalent to the Disconnect caller option.
If a participant calls in to the MCU and connects to an auto attendant, the MCU does not know which conference
they will join until they make a selection from the auto attendant menu.
In Unreserved mode, the auto attendant connection allocates a media port from those not currently in use. If all of
the media ports are in use, the endpoint's connection will be dropped by the MCU.
In Reserved mode, the auto attendant connection effectively "borrows" a media port from those not currently in use.
However, this borrowed media port has a lower priority than a media port used by a conference participant, and if
the auto attendant connection "borrows" the last remaining media port, then that connection will be dropped if
another endpoint connects directly to a conference and requires a reserved media port.
In general, changing port reservation mode when there are active connections is not recommended. The effects of
changing mode include, but are not necessarily limited to:
Any ad hoc conferences in progress will be destroyed when changing to port reservation mode and their
Participants in a scheduled conference may be disconnected. For each conference, the maximum port usage
values (for unreserved mode) and the ports to reserve (for reserved mode) are configured and stored
separately. Therefore when changing port reservation mode, it is possible that there are more active
participants than allowed in the particular mode. In this case, participants are disconnected to reduce the
number to that allowed.
40
Download from Www.Somanuals.com. All Manuals Search And Download.
The Codian MCU supports an additional video channel known as the content channel for each conference. This feature
encompasses:
H.239 video streams sent from the MCU to viewing H.323 endpoints
Sourcing the content channel from a H.323 endpoint's H.239 video stream, a SIP endpoint supporting
content using BFCP, or a VNC connection
Showing the content as part of the main video channel, where an endpoint cannot, for whatever reason,
receive the content channel as an additional video channel. That is, the participant will see the content as a
pane in the conference layout.
Streaming the content channel to users' desktop machines as a pane in the conference view
Streaming the content channel to users' desktop machines as a separate window (where markup and text
chat can also be used)(*)
Allowing graphical and textual "markup" of the content channel (*)
Text chat between conference participants (*)
- these features require the web conferencing feature key.
The H.239 protocol allow the MCU to support an additional video stream to or from each connected endpoint.
Therefore, there are potentially three media streams between each endpoint and the MCU: audio, main video and
content video.
SIP endpoints will always receive the content as part of the main video channel. That is, SIP endpoints will not receive
the content channel as a separate video channel, but will see the content as a pane in the main video channel.
The main video is the normal multi-pane conference view showing participants' video streams composed within the
selected layout. The differences between the content channel video and the main video are:
Each participant in a conference can normally select their own individual main video layout (e.g. a 2 x 2 grid
of other participants, one large focused pane plus eight smaller panes) and they are free to change this layout
as many times as desired while they are connected to the conference.
By comparison the content channel video always shows just a single video stream, "full screen", and each
viewing endpoint will see the same stream. The stream which constitutes the content channel can change any
number of times during the conference, but there can be at most one contributing stream at any given
moment.
Each participant's main video stream is encoded independently; this means that each endpoint can be
receiving its main video stream at a different bit rate, codec, or resolution to that being sent to other
participants.
However, there is a single content video stream per-conference: the MCU sends the same bit rate and
resolution to all endpoints receiving content. The bit rate and resolution used is chosen to maximize the
number of viewers - for instance the resolution might be reduced if a new endpoint joins the conference and
its content receive capabilities are more limited than those of the other participants. Note that in conferences
41
Download from Www.Somanuals.com. All Manuals Search And Download.
that use encryption, the MCU can send encrypted and unencrypted content to different participants in the
same conference (albeit with the same encryption key for every participant receiving encrypted content).
The range of bit rates, resolutions and frame rates available to the MCU for sending the content channel via
H.239 to H.323 video conferencing endpoints is potentially as wide as that for the main video channel.
However, in general, the main video channel is used for motion video (i.e. high frame rate streams) and the
content channel for less dynamic video such as an accompanying presentation - typically high resolution, low
frame rate.
However, the MCU allows flexibility in terms of nominating which of the available streams forms the
content channel, as well as allowing control over which endpoints are permitted to start contributing
content video.
For the main video channel, a video conferencing endpoint would normally be both contributing (sending) a
video stream to the MCU and receiving a video stream from it.
However the content channel works differently in that an endpoint can either be sending content video or
receiving content video, but not both. A given endpoint may switch between being the contributor and a
viewer during the conference, but it will never be both simultaneously.
For H.323 endpoints, depending on the specific endpoint and how it is configured, the content video stream may be
displayed on a separate screen, or the endpoint may show the main video and the content video streams side by side
on the same screen.
Irrespective of its content receive capability, an endpoint may or may not be able to contribute the content channel -
typically, for this to be possible it will either need a second camera or some other video input such as a VCR or
"video in" connection.
Some H.323 endpoints may have no support for the H.239 protocol and the MCU does not send the content channel
video to SIP endpoints. However, it is still possible for such endpoints to display the content channel - the MCU is
able to show the content channel within a normal view pane in the same way as it displays other conference
participants. This ability is controlled by the unit-wide Display content in normal video channel setting (see Configuring
content settings).
As described above, a conference's content channel as sent to the set of receiving endpoints has a single source. There
are several possible content channel sources:
This is the most conventional content channel behavior - a H.323 conference participant opens a H.239
channel to the MCU and contributes a video stream, such as that supplied by a second camera or an attached
PC.
Because there can be at most one content channel source, the H.323 endpoint needs to make a request to
the MCU, and have that request accepted, before actual content channel contribution can start. If the
conference already has an active content channel (for example, another endpoint is contributing H.239
video), the new request will be rejected by the MCU - it will be necessary to wait for the active contributor
to cease sending H.239 video before the new endpoint is able to start.
BFCP (Binary Floor Control Protocol) is a protocol that allows for an additional video channel (known as the
42
Download from Www.Somanuals.com. All Manuals Search And Download.
content channel) alongside the main video channel in a video-conferencing call that uses SIP. A SIP
conference participant opens a BFCP channel to the MCU and contributes a video stream, such as that
supplied by a second camera or an attached PC.
Because there can be at most one content channel source, the SIP endpoint needs to make a request to the
MCU, and have that request accepted, before actual content channel contribution can start. If the
conference already has an active content channel (for example, another endpoint is contributing content
video), the new request will be rejected by the MCU - it will be necessary to wait for the active contributor
to cease sending content video before the new endpoint is able to start. Note that the MCU does not send
the content channel to SIP endpoints as a separate video channel, but can show the content channel within a
normal view pane in the same way as it displays other conference participants. This ability is controlled by
A VNC connection is one where the MCU has made a connection to a remote device (normally a desktop
PC) and is receiving a video stream from that device - this is typically used for including a slide-based
presentation in a conference.
By default, if a conference is configured with content channel support and a VNC "participant" is added to
that conference, the MCU will attempt to use the VNC video as the content channel. This is normally the
desired behavior; however, there are a couple of caveats:
o
If there is a video conferencing endpoint actively contributing content video then it will not be
possible to immediately switch over to using the VNC video instead - the switch over will occur
when the participant closes its content channel.
o
With more than one active VNC connection in a conference, the first will be used as the content
channel source, and subsequent connections will be shown in main video layout panes, just as if the
conference had no content channel facility. If the currently active VNC connection is either
disconnected or its use as the content channel disabled, another VNC video stream will start to be
used as the content channel.
It is also possible for the MCU to use a endpoint's main video channel as the conference's content channel.
This has the same caveats as the use of a VNC connection for the content channel, as described above.
Whichever of the content channel sources mentioned above is active, the MCU provides the facility for users
to add markup to the video channel. This markup consists of an additional video overlay on to which graphics
may be drawn and text added - content channel viewers see the content channel source video plus this
overlay. The overlay can be cleared later leaving the source video unaltered.
At the unit-wide level, the MCU can be configured to disallow the use of conference content channels completely. If
the content channel facility is enabled, the MCU can be separately configured not to allow textual or graphical
markup of the content, and whether to make text chat visible to connected endpoints.
You can choose to enable encryption on the MCU. When encryption is used, the content channel will be encrypted.
For more information on these configuration parameters, see Configuring content settings and Configuring
encryption settings.
43
Download from Www.Somanuals.com. All Manuals Search And Download.
Assuming that content is enabled on the MCU unit-wide, each scheduled conference can be independently configured
to allow content channel operations or not. If enabled, this has an impact on the conference's port usage - if disabled,
then all attempts by participants in that conference to open a content channel to the MCU will be unsuccessful.
If the MCU is configured to allow encryption, each individual conference can be configured to either require
encryption or to optionally use encryption. The MCU can send either encrypted or unencrypted content to different
participants in a conference depending on the capabilities of those participants' endpoints.
For more information on the conference configuration parameters relevant to the content channel, see Adding and
updating conferences.
Content contribution refers to the ability of video conferencing devices to contribute the content channel video for a
conference via the mechanism of opening a separate video channel, distinct from its main video stream. Specifically,
this section does not deal with the use of content by the MCU when sending content channels to viewing devices or
the use of other protocols such as VNC to supply the content channel video for a conference.
For a conference configured with content channel video enabled, each endpoint in that conference is either permitted
or prohibited from being able to contribute content video. H.239 is the protocol used by H.323 video conferencing
endpoints to supply or receive content channel video; BFCP is the protocol used by SIP video conferencing endpoints
to supply content channel video. Other content channel source configurations, such as the use of a VNC connection,
do not depend on any H.239 or BFCP contribution parameters.
Remember that what is termed Content contribution is more precisely described as the ability to
contributing
content channel video via H.239/BFCP. The nature of the H.239 and BFCP protocols used between the MCU and
endpoints is such that once an endpoint has successfully become the content source for a conference, the MCU is not
then able to force that endpoint to stop contributing the content channel video.
While an endpoint is supplying the content channel for a conference, it is considered to be holding the virtual content
token for the conference - this token must be relinquished before either another endpoint can start contributing video
via H.239 or BFCP or a content channel source such as VNC become active. This token is normally released via a
specific endpoint operation (e.g. a "stop content " option) or by that endpoint leaving the conference.
By default, participants' ability to contribute content video (technically, as above, to
BFCP video) is determined by the per-conference Content contribution from endpoints setting (
contributing H.239 or
>
).
The per-conference default Content contribution from endpoints setting can be overridden by individual endpoints'
configuration. If such an endpoint's Content contribution setting is <use conference default> then the endpoint's ability to
contribute content channel video will be determined initially from the conference setting. If the endpoint setting is
<enabled> or <disabled> then this will override the conference setting and that endpoint will either always be
prevented from using content, or always permitted (assuming the conference of which it is part is configured with
content channel support). As well as being part of each endpoint's configuration, the Content contribution setting can
also be specified when calling out to an endpoint by address.
44
Download from Www.Somanuals.com. All Manuals Search And Download.
Irrespective of per-conference or per-endpoint configuration parameters, if a conference is configured to allow
content channel operations then it is possible to explicitly enable or disable individual conference participants' ability
to use content via the web browser interface (assuming a user login with full conference control).
To change the content contribution setting for an active conference participant via the web interface, first navigate to
that participant's
page (go to
and click the conference you want and then click on the name of
the participant whose settings you want to change). If the conference has content enabled and the endpoint in
question has content capabilities, you should be able to use one of the following controls:
allow participant to contribute content video
do not allow participant to contribute content video
If an endpoint's ability to contribute content video has been explicitly enabled or disabled via this mechanism, that
enablement or disablement will take precedence over any current or future conference or participant configuration,
even if the endpoint later moves to a different conference.
In addition to supporting the H.239 and BFCP protocols by which endpoints in a conference can supply the content
channel video, the MCU also allows a participant's main video channel to be used for the content stream. This is
essentially what happens by default for VNC connections in a conference configured to allow content channel video.
As detailed above, it is not possible to force an endpoint that has started to contribute content video to relinquish the
virtual token that it holds. Thus, if an endpoint's main video channel is configured to be the content channel source,
this will only take effect if no other endpoint is supplying the content channel video stream (whether by H.239,
BFCP, or through use of its main video stream).
To control the use of a participant's main video as the conference content channel source, these following controls are
displayed on the per-conference participant list (next to the preview image of the video stream to which they relate):
use this participant's main video stream as the content channel
(this is set by default for VNC connections)
stop using this participant's main video stream as the content channel
(revert to more conventional content channel behavior such as H.239)
If more than one participant's main video channel is configured to provide the content channel, then all but the active
(normally, first) one will be marked with the status:
You might also see this warning if there is more than one VNC connection in a conference, because, when
establishing a new VNC connection, the MCU will automatically configure its main (in fact, sole) video channel to be
used as the content channel source if possible. To choose between multiple potential main video channels as the
content source for the conference, ensure that you use the disablement control:
on all but the source you wish to use for this.
45
Download from Www.Somanuals.com. All Manuals Search And Download.
As well as the content stream (used for sending to H.323 endpoints), the MCU also generates a Codian proprietary
format version of the content channel video which can be viewed in conjunction with PC-based video streaming. This
ensures that, if desired, all participants and viewers for a conference are able to access all of its associated media.
Content channel streaming also allows participants using H.323 video conferencing endpoints without H.239
capability, or SIP endpoints to view a high resolution version of the content channel. Content channel streaming also
provides some features not available via the H.239 protocol:
"Markup" is the overlaying of graphics and text onto the content channel video; this could be used, for instance, to
draw attention to a specific element of a presentation slide. Markup can only be performed through the content
channel streaming interface, and is accomplished via the simple mechanism of clicking and dragging with the mouse,
with extra controls for changing the drawing color or clearing the markup when its usefulness has passed.
Content channel markup also has the following characteristics:
All content streaming viewers have equal markup capabilities. This means that either all viewers are able to
perform markup on the content channel video (or clear it), or all are unable to do so - it is not possible to
restrict markup to just a subset of active viewers.
The video markup, although it can only be edited by streaming viewers, will be seen by content channel
streaming viewers, by participants connected via H.323 endpoints that are receiving the content channel,
and by any participants that are viewing the content as part of their main video.
Video markup is normally used as an overlay to content channel video as supplied by a H.239, BFCP, or
VNC connection. However, for a conference with content channel operations enabled, it is also possible to
form a content channel comprising just the markup applied to an otherwise blank video stream. This can be
accomplished simply by starting to stream the conference's content channel and performing the usual
markup operations on the (empty) content channel displayed. Adding markup to such a blank channel
"activates" it, and will cause a video channel to be opened to those H.323 conference endpoints which have
H.239 capabilities.
The ability of content channel streaming viewers to perform markup is governed by the unit-wide Markup of content
channel video setting on the
page.
In parallel with, though in many senses independently of, content channel streaming, the MCU also provides a
mechanism for those streaming a conference's content channel to communicate with other conference participants via
text messages. Beneath the window showing the content channel video, streaming viewers are able to type messages
that will be sent to all other streaming viewers, as well as see messages that other users type.
In order that users contributing text messages can be identified, each content streaming viewer has an associated user
ID, and this ID is pre-pended to each message when it is sent out to other viewers' displays. If the content channel
streaming has been initiated via the streaming-only interface, each user is required to supply a Sign-in name before
streaming starts, and this sign-in is used as their text chat identifier. If streaming has been initiated via the Stream
control on the MCU conference list, the user's web interface login ID will be used as their text chat identifier.
46
Download from Www.Somanuals.com. All Manuals Search And Download.
The text chat facility provided via web browser-based content streaming is two-way in that any content channel
streaming viewer is able to both contribute text and see all messages typed by other viewers. Although there is no
mechanism by which endpoints are able to contribute text chat messages, the MCU is able to display the most recent
text messages within endpoints' main video channels. This is intended to be of use when a presenter is connected to
an MCU conference via a video endpoint and wishes to field questions raised by (content channel) streaming viewers.
In this situation, the text typed by content channel streaming viewers is overlaid on the normal, multi-pane,
conference layout, though restricted to approximately the lowest 1/3 of the screen.
For streaming viewers to have the option of contributing and/or reading text messages, the View content channel
option must be selected. This option is one of the
available to users when they select to
stream a conference.
The display of text chat in endpoints' views is governed by the unit-wide Content channel text chat option which is an
setting on the page. The text chat facility itself, and display of typed text to all
content channel streaming viewers' windows, cannot be disabled.
Some of the above content channel features require the MCU to have been configured with the
feature key. The following features are only available with the Web conferencing key:
Streaming the content channel to users' desktop machines as a separate window (rather than as a pane in the
conference view)
Markup of content channel video
Text chat
If the MCU is operating in reserved mode, enabling content for a conference does not use a video port; instead,
content uses one of the additional 'Streaming and content' ports provided by your MCU. A single 'Streaming and
content' port is needed for all content channel operations, irrespective of how many viewers there are; for example, a
conference involving five video endpoints (one of which is contributing a content stream and the other four viewing
it) will require five video ports and one 'Streaming and content' port - Video ports to reserve should be set to 5, and
Content channel video set to "Enabled" in this specific example.
In reserved mode, a conference with content enabled will require a 'Streaming and content' port for content
operations even if no current participants are actively making use of content.
For more information about the number and types of ports provided by your MCU, refer to MCU port matrix.
If the MCU is operating in unreserved mode, enabling content for a conference works in a similar way to streaming in
that it will require a port to be allocated when content channel operations are first attempted for that conference. For
instance, this could be when a participant opens a content channel or a user starts viewing the content channel via
their web browser. When the port is no longer needed for the conference's content channel (e.g. when the last
remaining participant disconnects) the port will be released for use by future participants or conferences.
47
Download from Www.Somanuals.com. All Manuals Search And Download.
The streaming of the content channel is performed using the port allocated for content rather than the port allocated
for streaming. This means that it is possible to stream the content channel (for example, to use the video markup
feature) for conferences which do not have streaming enabled. Enabling both streaming and content for a conference
will mean that two additional ports will be required for that conference, over and above the video and audio-only
ports used by endpoints participating in that conference.
See port reservation for more information.
All of the above-mentioned features, for instance content video streams between the MCU and video conferencing
endpoints, markup of content channel video and text chat, are available for use with both scheduled and ad hoc
conferences.
However, whereas for scheduled conferences the availability of content is determined by a per-conference
configuration setting, for ad hoc conferences it is only possible to enable or disable content on a device-wide basis.
This is accomplished via the Content for ad hoc conferences option on the Content settings web page — if this is
"Enabled" then any ad hoc conference on the MCU may use content; if "Disabled" then none may do so.
In software versions prior to 1.4(1), it was not possible to use content channel features (including the H.239 protocol
between the MCU and H.323 video conferencing endpoints) with ad hoc conferences. It remains the case that ad hoc
conferences are not permitted when operating in reserved mode.
48
Download from Www.Somanuals.com. All Manuals Search And Download.
You can control many conference features from the MCU web browser:
Sending messages to all participants
You can add a participant to a conference in two ways: either as a "one-off" participant in to an active conference now
or by adding their endpoint to the conference configuration, in which case the endpoint will be called every time the
conference occurs. Their endpoint must be pre-configured for you to be able to do this, see Adding pre-configured
participants.
To call an endpoint immediately you can either put in their endpoint details or select a pre-configured endpoint and
call out. Their endpoint can be an H.323, SIP or VNC endpoint. Refer to the first three links below for details:
Adding pre-configured participants
Note that participants called by the MCU will have chairperson privileges. For more information about chairperson
and guest privileges, refer to Adding a conference.
To call a participant with an H.323 endpoint in to an active conference:
1. Go to
2. Click a Conference name and then click
To add a new endpoint (one that you have not added as a configured endpoint):
to display the Conference List.
.
o
i.
Select the
radio button and do one of the following:
.
For
, enter the IP address, E.164 number, or H.323 alias of the
participant's endpoint.
For , enter the number configured on an H.323 gateway for the
participant and select the from the drop down list. For more
.
information about configuring H.323 gateways, refer to Adding and updating
.
For
, enter an H.323 gateway and E.164 number in the form <gateway
address>!<E.164 number>. This allows to you make a call via a H.323 gateway
that has not been pre-configured on the MCU.
ii.
iii.
Click
.
o
To invite an existing (configured) H.323 endpoint, scroll down to the Endpoints section, select the
check box next to the endpoint name and click
.
49
Download from Www.Somanuals.com. All Manuals Search And Download.
To call a participant with a SIP endpoint in to an active conference:
1. Go to to display the Conference List.
2. Click a Conference name and then click
To add an new endpoint (one that you have not added as a configured endpoint):
.
o
i.
Select the
radio button and do one of the following:
.
For
, enter the IP address, or SIP URI of the participant's endpoint (in
the format 1234@codian.com)
.
For
, enter the number registered with the SIP registrar and check
(ensuring that you have configured a SIP registrar on the
>
page)
Click
ii.
iii.
.
o
To invite an existing (configured) SIP participant, scroll down to the Endpoints section, select the
check box next to the SIP endpoint name and click
.
To call a VNC endpoint in to an active conference:
1. Go to
to display the Conference List.
2. Click a Conference name and then click
.
o
To invite a new VNC endpoint:
i.
Enter the host name or IP address of the VNC host and the VNC server password for the
computer you are adding.
ii.
Enable
if you want the participant to be disconnected from the
conference if another participant disconnects and only participants configured to be
automatically disconnected remain in the conference.
iii.
Click
.
o
To invite an existing (configured) VNC endpoint, scroll down to the Endpoints section, click next
to the VNC endpoint name and click
.
You can choose participants whose endpoints have been configured previously to be part of a scheduled conference.
These participants will be automatically invited into the conference by the MCU every time the conference runs. This
is useful if you regularly invite the same participants into a conference.
The MCU will attempt to call pre-configured endpoints every minute for the first 5 minutes and then every 5
minutes until 20 minutes into the conference, at which point it will stop trying.
To add previously configured endpoints to a conference:
1. Go to
2. Click a Conference name and then click the
3. Click the button. The pre-configured participants page will be displayed. This
to display the Conference List.
tab.
page lists all the endpoints that have been configured on the MCU (see Configuring an H.323 endpoint and
4. Select which endpoints you would like to add as pre-configured participants in this conference.
5. Press
.
6. Make any other changes you require to the conference configuration, then press
. (If you
do not press
steps.)
, you will lose the selections of configured endpoints made in the previous
50
Download from Www.Somanuals.com. All Manuals Search And Download.
You can select custom layouts to use for all conference participants. To use this option:
1. Go to
2. Click a Conference name and then click the
.
tab.
3. Click on the layout you want to use from those shown in the Available layouts. There are different numbers of
panes and pane configurations to choose from.
The chosen layout is displayed enlarged to the left in the Conference custom layout section of the page and the
radio button is selected.
4. If you want to select the participants who appear in a pane manually rather than letting the MCU make the
most appropriate selection, click
.
5. To have all participants see this layout when they join the conference click
.
6. If you also want all participants to see this view now, click
.
The following table explains the details that display.
Whether a custom layout can be used for this
participant.
When you click a new layout from the Available
layouts, is automatically chosen with the
most recent layout selected.
New participants joining this conference will view If a participant has chosen to use a custom
participant's layout display).
update and switch to the new view.
To force all participants to use this layout, click
.
Displays all the conference layouts that are
available. Click a layout to select it and make it
available.
You can only select one custom layout at a time.
To have more control over which participant appears in which pane, you can use the Pane placement function. Pane
placement works on a per conference basis.
Pane placement works on the selected custom layout in the
page - see Customizing layout
views. The chosen custom layout is shown with the panes numbered. The largest (and therefore most important)
panes have the lowest numbers. Because the largest number of panes in any custom layout is 20, there are twenty
drop down lists, one per pane. If the number of panes in the chosen layout is less than this, a gray line separates the
panes that are used from those that do not apply to this layout.
The first time you open the pane placement page for a conference all the panes are set to <default>. The MCU
decides which participant will appear in panes with this setting. See Understanding how participants display in layout
views for more information.
51
Download from Www.Somanuals.com. All Manuals Search And Download.
For each pane you can select an alternative setting:
<blank>: no participant appears in this pane
<rolling>: this pane shows conference participants, automatically changing at the configured "Pane rolling
interval" frequency from the
page. All participants contributing video are shown in
rolling panes except for any participants explicitly placed in other panes
<loudest speaker>: the participant who is speaking the loudest at any time appears in this pane
<content>: this pane is reserved for the content channel (see Ccontent channel video support). If the
content channel is not used in this conference, this pane will be blank.
<name>: the name of each pre-configured endpoint in this conference, and (if the conference is active) the
names of all active participants whose endpoints were not pre-configured is displayed in the lists. If you
select a specific participant (endpoint), that participant appears in this pane at all times.
To use pane placement:
1. Click
.
2. For each pane that you want to control, select an entry from the drop down list.
3. For panes that you no longer want to control individually, select <default>
4. Click
.
5. To return to the Custom layout page, click
When you use pane placement, bear in mind that:
Pane placement only applies to conference custom layouts. If they are disabled so is pane placement.
You can mix panes set to <default> with panes that have other settings
Any panes that you configure keep their setting even if you change the custom layout view. Therefore if you
configure all the panes in the 20 pane layout and then move to one with only five panes, panes 1 to 5 will
have the same settings as before. Panes 6 to 20 will also keep their settings, it is just that they are not used.
Therefore if you subsequently move to a layout with say 10 panes, all ten panes have their settings pre-
configured.
This does mean that if you have participants who need to be seen at all times, you should configure them in
the lower numbered panes
You must set up pane placement for each conference that you want to use it with
You can set up pane placement before a conference starts and configure pre-configured endpoints in to
particular panes. However you can only configure active participants whose endpoints are not pre-
configured when the conference is running
Pane placement persists over conference repetitions. If you set pane placement once, the same placements
are ready to be used when the conference next repeats
If you select a particular participant for a pane and they are disconnected for any reason, that pane appears
blank
After you set up pane placement, you can still change the layout for individual participants - and they can
change their layout using the far end camera controls unless you disable this for each participant individually.
The left and right controls on a participant's far end camera control, used to select a focused participant,
have no effect when pane placement is in use
Potentially, when pane placement is in use, a participant may appear in two panes at the same time. This
happens for example if a pane is configured to show a particular participant and another pane is configured to
show the loudest speaker; each time that participant is the loudest speaker, he will appear in both panes.
52
Download from Www.Somanuals.com. All Manuals Search And Download.
There is a setting on the MCU's
page to control this behavior called Loudest speaker
pane placement behavior
53
Download from Www.Somanuals.com. All Manuals Search And Download.
You can display statistics about a conference and use the information to quickly see how many participants are
currently in the conference.
To access this option:
1. Go to
.
2. Click a Conference name and then click the
tab.
If the conference is active, statistics for that conference will be displayed. If the conference is completed only ―No
longer active‖ will be displayed.
Refer to the table below for information on interpreting this information.
When the conference started.
When the conference will complete. This will be the time at which the maximum duration of
the conference will have elapsed. This setting displays as <permanent> if it has been
configured to last forever.
The duration of this conference.
The status of a conference with respect to its H.323 gatekeeper and/or SIP registrations. The
possible states are:
This conference is not configured to be registered with a gatekeeper or SIP registrar;
because of this, there is no applicable registration status to show.
The conference has been registered successfully with the gatekeeper or SIP registrar
and can be contacted using the number indicated.
This conference is in the process of registering with the gatekeeper or SIP registrar.
The conference is in the process of unregistering with the gatekeeper or SIP
registrar. This might occur if:
o
Gatekeeper registration has been turned off (either for that conference only
or for the entire MCU)
o
The configured gatekeeper has just been changed and the MCU is in the
process of unregistering from the previous gatekeeper before registering its
conferences with the new one.
If the MCU fails to register a conference with the gatekeeper or SIP registrar, it
enters these states temporarily before re-attempting the registration.
This ID has been specifically configured to be registered with the gatekeeper or SIP
registrar, but some other configuration has overridden this, causing the registration
to not be attempted. This state might occur if either of the H.323 gatekeeper usage or
ID registration for scheduled conferences options on the
page is set
to Disabled.
The conference is configured to register with a gatekeeper or SIP registrar, but has
not had a numeric identifier set.
54
Download from Www.Somanuals.com. All Manuals Search And Download.
The current number of contributing audio/video participants.
The largest number of contributing audio/video participants who have been in the conference
at the same time.
The current number of contributing audio-only participants.
The largest number of contributing audio-only participants who have been in the conference
at the same time.
The current number of streaming participants watching the conference.
The largest number of streaming participants who have been watching the conference at the
same time.
55
Download from Www.Somanuals.com. All Manuals Search And Download.
You can send messages to all participants in a conference simultaneously. To access this option:
1. Go to
.
2. Click a Conference name and then click the
tab.
This message appears overlaid on each participant's view, including participants viewing the conference via streaming.
Enter the message to send to all conference
participants.
Messages must be fewer than 256 characters, but
depending on the viewing screen, messages at the
higher-end of this limit might not display
properly. Therefore, consider limiting messages
to approximately 180 characters. Messages longer
than 256 characters will not be truncated; they
will not display at all.
You can disable this setting from
The vertical position of the message on the
conference display.
Choose from the top, middle, or bottom of the
conference display.
How long the message appears on participants'
video screens.
The default setting is 30 seconds. To remove all
messages before they time out, click
.
56
Download from Www.Somanuals.com. All Manuals Search And Download.
You can view detailed information about conference participants:
Moving a participant
The Participant list displays information about active and previous participants in the conference. To access this list,
go to
and click a Conference name. This page explains the information available in the participant list.
Pre-configured participants
Watching the conference
Above the list of participants, certain information about the conference is displayed:
: If the conference is being recorded on an IP VCR, this message will
: Each conference may have either imposed limits on the maximum number of media ports it is
appear.
able to use, or a certain number of media ports reserved for its use. This section shows the video port and
audio-only port reservation or limit.
See the full description of Port reservation for additional information.
: Whether streaming is in use or not for this conference.
: Whether the content channel is in use or not for this conference.
: If you have the encryption feature key enabled, the encryption status of the conference will be
shown, which will either be not required or required.
57
Download from Www.Somanuals.com. All Manuals Search And Download.
A locked conference is one where new participants cannot dial in and you cannot start to stream the conference.
Existing participants and streaming viewers will maintain their connection to the conference. If a conference is
locked, an icon will indicate this on the auto attendant. The auto attendant will also display the text: 'This conference
is locked'.
Note that participants that are pre-configured via the API will be able to dial in to the conference even if it is locked.
This allows conferences to be restricted to specific participants (known as whitelisting).
Admin users and the conference owner can lock and unlock a conference. The conference will be automatically
unlocked by the MCU when the final participant leaves.
When a conference is locked, admin users and the conference owner will still be able to connect new endpoints and
disconnect participants.
To lock a conference:
1. Go to
List displays.
2. Click the
and click on the name of the conference you want to lock. The Conference's Participant
button in the top right-hand corner of the page.
Refer to the table below for details about the active participant list, which you can modify in the following ways:
You can end the conference, forcing all participants (including unicast streaming viewers) to be dropped, by
clicking
.
For conferences that are "scheduled" rather than "ad hoc", ending the conference in this way causes any
configured repetition to be cancelled. The ended conference would move from the "Scheduled conferences"
list to the "Completed conferences" list. The configured duration of a completed conference reflects the
actual duration of the conference rather than its original configured duration. For example, if a conference
was scheduled to run from 09:00 until 10:00 (one hour) and the conference ended at 09:25, the configured
duration would be changed to 25 minutes.
You can add a new H.323 or SIP video conferencing endpoint to the conference (either creating a new
endpoint or by choosing an existing one) by clicking
You can add a new VNC endpoint to the conference (either by creating a new endpoint or by choosing an
Indicates whether the participant's endpoint is an
H.323, SIP, or VNC endpoint.
Displays the name of the endpoint.
The following may also be displayed:
User names only display if the participant list is
being viewed by an administrator, because only
administrators have access to the configured user
database.
If the participant has been resolved to a particular
configured user (for instance by matching the
participant's E.164 phone number against a
configured value), then the appropriate user id
will be shown here.
58
Download from Www.Somanuals.com. All Manuals Search And Download.
Configured endpoint names only display if the
participant list is being viewed by a user whose
privilege level is administrator or conference creation
and full control; only users with these privilege
levels have access to the configured endpoint
database.
This indicates that this participant corresponds to
a pre-defined endpoint. The <name> shown is
the endpoint's configured name.
When you make a participant "important", it sets
this participant as the focused participant. For
example, this participant is considered the
Makes participant important
Makes participant unimportant
loudest participant even if they are not speaking.
Only one participant can be identified as
"important", and no participant is set to
"important" by default.
This option affects the layout views for the
conference and individual participants. See
Customizing layout views.
If the content channel is made "important", one
participant can still be important. On endpoints
that support content, the content channel will be
displayed in the content channel window and the
important participant will be given the focus in
the main video window. On endpoints that do
not support content, the important participant
will be ignored as the content channel will be
given the focus.
The presence of these controls is controlled by
Prevents other participants from hearing
this participant (mute).
the
setting on the
page (refer to
Allows other participants to hear this
participant's audio (stop muting).
Prevents others from seeing this
participant's video contribution (mute).
Allows others to see this participant's
video contribution (stop muting).
You can configure the MCU to require
confirmation when someone attempts to
disconnect an individual participant from a
conference. This setting is on the
page.
Disconnects a participant from the
conference.
59
Download from Www.Somanuals.com. All Manuals Search And Download.
Displays the time at which a participant
connected to the conference. If a participant is
If this column is selected as the sorting field, the
listing is ordered according to when the
not yet fully connected (for example, if the MCU participants connected to the conference.
has called a participant but it has not yet
answered), then that is indicated here. The
resolution of the participant's video stream is also
displayed.
When ClearVision is enabled on the
page, the original and enhanced
video resolutions are shown in the "Rx:" line; the
original resolution is displayed in a highlighted
The following additional indications may also be form and the enhanced resolution is shown when
displayed:
the user's mouse pointer is moved to this
highlighted resolution.
Indicates that the conference is being recorded.
Next to the encryption indication is the AES
check code. This can be used in combination with
information displayed by some endpoints to
check that the encryption is secure.
Indicates that all media streams in both directions
(to and from the endpoint and the MCU) are
encrypted.
Indicates that all media streams received from this
participant are encrypted.
Indicates that all media streams sent to this
participant are encrypted.
See Adding pre-configured participants for
additional information on adding endpoints to
conferences in this way.
This indicates that this participant is in the
conference because of a pre-configured endpoint.
These messages indicate that the MCU has not
opened a media channel to a participant's
endpoint because it has no capability to receive
that type of channel. For example, if the endpoint
is a simple telephone, you might expect to see
"No video capabilities" shown here.
This is most likely to occur if you have disabled
one or more codecs in the "Audio codecs from
MCU" or "Video codecs from MCU"
configuration on the Advanced conference
settings web page.
These messages indicate that the remote endpoint
had declared media capabilities, but the MCU was
not permitted to open a channel that the endpoint
was prepared to receive.
This could occur if, for instance, the far end's
advertised receive video sizes were all 4CIF (704
x 576 pixels) or above, and the MCU was set to
not transmit above CIF (352 x 288 pixels).
These messages indicate that the remote endpoint
had declared media capabilities including codecs
that the MCU was permitted to send, but that the
MCU was unable to transmit the specific formats
declared.
60
Download from Www.Somanuals.com. All Manuals Search And Download.
Indicates that the MCU was unable to open a
media channel to the endpoint because the only
possible channels it would be able to open were
invalid due to a symmetry clash. This clash occurs
when the remote endpoint declared that it is only
able to receive certain types of media if it is also
sending the same format, and the format in
question is one that the MCU is able to send but
not receive.
These messages occur if a channel was unable to
be opened solely because doing so would have
exceeded the port limit. This limit may be a per-
conference restriction or, for those conferences
which impose no such limit, it could be that all of
the MCU's available ports were in use.
Indicates that the MCU is unable to receive the
media format that the endpoint is trying to
transmit.
If the MCU has received information that the
endpoint has been muted at the far end, this will
be indicated in the Rx row as "muted remotely".
These status rows show details of the audio and
(main) video streams being sent to or received
from the endpoint.
Tx refers to media streams sent by the MCU, and
Rx means media streams being received by the
MCU.
No Content tx status will be shown if the
conference does not have content channel video
enabled, or if the endpoint has no content
capabilities.
This row (if present) shows one of two things: the
characteristics of the content video channel being
sent by the MCU to a participant, or the reason
why no such stream is currently being
transmitted. The status values that can be shown
here are:
You may change whether the MCU is prepared to
send the conference content channel stream to an
endpoint using content using the enable or disable
control here. If sending of content video to an
endpoint is currently not allowed, you will see
the enable option, otherwise you will see the
disable option.
The MCU is able to send content video to the
participant but is not currently doing so. This is
normally because there is no active content
channel video source for the conference. This
status will also be shown for a participant which is
the content channel video source and is also
capable of receiving the currently active content
video stream.
For more information about using content, refer
61
Download from Www.Somanuals.com. All Manuals Search And Download.
Content is enabled for this conference, but this
participant is not allowed to receive it. To enable
content for this participant, configure the Content
video receive setting for this participant's endpoint
the enable control for an active call.
There is a unit-wide setting that determines
which video codec is used by the MCU for
outgoing content channels. The Outgoing content
video codec is on the
page.
This message means that the endpoint is able to
receive content video, but not using the same
codec as the MCU is configured to transmit.
For each conference, the MCU uses a single video
stream for all outgoing content connections to
endpoints. This entails considering all endpoints'
receive capabilities and deciding which resolution
and bit rate to send in order to maximize the
number of content channel viewers. These
messages mean that the MCU has been unable to
include this endpoint in the set of content viewers
because of its limitations with regard to format
(video resolution) or bit rate. Note that it is
possible to configure a lower limit on the
bandwidth of the shared content video encoding
which will cause a bit rate mismatch where an
endpoint is only able to receive a low bit rate
The MCU supports only presentation mode for its
content channels; specifically, H.239 live mode is
not supported. This status message indicates that
the endpoint is content-capable but does not
support presentation mode.
The MCU is unable to send encrypted content
video to this participant.
The MCU has detected that the content link to
this endpoint is experiencing problems, and has
62
Download from Www.Somanuals.com. All Manuals Search And Download.
stopped sending video keyframes in response to
Fast Update Requests (FURs) to avoid degrading
the content video sent to other conference
participants. The MCU will only enter this state if
the Video fast update request filtering setting is
The associated participant is currently supplying
the conference's content channel video.
Use of this participant's main video source as the
content (content channel) source has failed. This
is normally because there is already a source for
the content channel; either another participant's
main video channel which has been configured in
the same way (VNC participants are set up this
way by default) or a content video channel
contributed by a connected endpoint.
Click
to open the Participant statistics page
This message appears if packet loss is detected
between the MCU and the endpoint.
and display details about the connection, for
example the packet errors. See Displaying
For more information, refer to H.243 floor and
This endpoint has requested and been granted the
chair.
For more information, refer to H.243 floor and
The endpoint has requested and been granted the
floor and its media is being broadcast to all
endpoints in the conference.
This situation can occur when an endpoint
requested the floor, was granted the floor, and
was then moved to another conference where
there was already an active floor participant.
This endpoint believes it has been granted the
floor, but its media is not being shown to all
endpoints in the conference.
For more information, refer to H.243 floor and
This situation can occur if another endpoint,
while chair, has issued H.243 commands to make
that endpoint the floor.
This endpoint's media is being broadcast to all
endpoints in the conference, although it did not
request the floor itself.
For more information, refer to H.243 floor and
Indicates that this connection is a cascade link to
or from another conference.
63
Download from Www.Somanuals.com. All Manuals Search And Download.
Displays a sample still video capture of the
participant.
Click the picture to update it.
Note that conferences that are configured to
require encryption do not show previews. Also
note that previews can be disabled on the
information on H.239 and BFCP.
These controls are only available if the conference
is configured with content enabled, and if the
participant is contributing a main video channel.
This control causes the MCU to
attempt to use the participant's main
video channel as the conference's
content channel source. This will not
be possible if the conference already
has an active content channel source
(either an endpoint's content video
channel or another participant's main
video activated via this control).
This control causes the MCU to stop
attempting to use the participant's
main video channel as the conference's
content channel source. It is necessary
to use this control to switch to using a
different endpoint's primary video
channel or to enable content video
contribution from endpoints.
Although you may use the controls described above to manage one participant at a time, for example to mute that
participant's audio, or to make them important, you may wish to manage all participants at once. The all-participant
controls permit you to do this. Note that you may continue to use the per-participant controls in conjunction with
the all-participant controls. Refer to the table below for details of the controls available:
Makes all participants unimportant
If no participants are currently important, then
this control will be unavailable.
This stops all audio in the conference
(mute).
If no participants are currently muted, the stop
muting controls will be unavailable. If all
participants are currently muted, the mute
controls will be unavailable.
Allows all participants to hear the
64
Download from Www.Somanuals.com. All Manuals Search And Download.
audio in the conference (stop muting). The presence of these controls is controlled by
the
setting on the
page (refer to
Prevents others from seeing all
participants' video contribution
(mute).
Allows others to see all participants'
video contribution (stop muting).
Disconnects all participants from the
conference.
If this conference was created ad hoc, then
disconnecting all the participants will terminate
the conference as well.
Selects voice-switched view for all
participants (see Customizing a
If all participants are watching the voice-switched
view, then this control will be unavailable.
Selects full screen view for all
participants.
Displays the layout selection panel
from which you can select a layout
view that all current participants will
see. This panel offers the same choices
as going to
. (See Customizing layout
Prevents participants from changing
their own view layout from their
endpoint.
If no participants may control their own view
layout, the prevent control will be unavailable. If
all participants may control their own layout, the
allow control will be unavailable.
Allows participants to change their
own view layout from their endpoint.
Refer to the table below to get details about the previous participant list. To erase this list, click
.
Indicates whether the participant is an H.323,
SIP, or VNC endpoint.
Displays the name of the participant (endpoint).
A previous participant can only be re-connected
to a conference if their endpoint is a pre-
Re-connects a participant to the
conference.
65
Download from Www.Somanuals.com. All Manuals Search And Download.
configured endpoint.
Note that if the original call to the conference was
from the endpoint rather than the endpoint being
invited by the MCU, then for the MCU to
recognize it, that endpoint must be configured
with Call-in match parameters. If the ** ERROR **
did not recognize that the call was from a pre-
configured endpoint then the re-connect control
will not be available.
For more information about configuring
Displays the time at which a participant
disconnected from the conference and who
initiated the disconnect.
Refer to the table below to get details about pre-configured endpoints.
Indicates whether the participant is an H.323,
SIP, or VNC endpoint.
Displays the name of the endpoint.
Displays the connection status of the pre-
configured participant.
This field shows which participants have
connected, which have disconnected, and reasons
for failure if a participant has failed to connect to
the conference.
You may wish to inform participants about conference details such as start time, and so on. Click the
icon to display further details about a conference. This information may be copied to the clipboard for
convenience.
Click this icon to watch the conference. This is exactly the same as clicking the
link in the Conference list.
Both take you to the conference streaming page. See Using streaming to view conferences for more information.
66
Download from Www.Somanuals.com. All Manuals Search And Download.
Every person viewing a conference (whether they are contributing video of their own or using streaming to watch
other participants) sees a conference layout view. This view divides the video screen into a collection of panes with
participants' video streams displayed in those panes. You can customize this view by choosing this option:
1. Go to
.
2. Click a Conference name and then click on a participant's name.
3. Click the
tab.
Displays static sample of video screen in the Click on the image to refresh the picture
currently selected layout.
Adds a border thickness to display around the If the image is displaying off the edges of the
video image.
participant's screen, add a border until the
image displays properly.
Give prominence to one participant over the The number of contributing conference
others.
participants determines the size of the large
pane.
Displays a single participant.
Displays the four most active participants
without seeing them scaled down to a small
size if there are lots of other participants.
Used when there are five or more video
participants.
Gives equal prominence to up to 20
conference contributors, and is useful for a
"roll call" of active participants.
The MCU automatically changes the layout to
the 3 x 3 arrangement, and will continue to
use this layout for up to 9 participants. With
10 or more participants, the 4 x 4 view is
used, and with 17 or more participants the 5 x
4 view will be used. The MCU will then
continue to use this layout even if there are
more than 20 participants.
Gives prominence to two participants in the This view is useful for observing a dialog
center of the view while showing smaller between two participants or for viewing slides
versions of other participants' video streams and a presenter.
above and below.
Click
to be used by any participant.
67
Download from Www.Somanuals.com. All Manuals Search And Download.
Click
layout for this participant.
Prevents this participant from changing their A participant can still change their layout view
own conference layout using the far-end
camera controls on their video endpoint.
using the web interface.
Allows this participant to control their own
conference view.
Send "normal" format video to this participant The available options for the resolution of
- this means that the video is intended to be
displayed on a screen whose dimensions
(width and height) are in the ratio 4:3.
transmitted video are controlled by the
setting which
can be configured for the whole unit on the
page or per
Send "widescreen" format video to this
participant - this means that the video is
intended to be displayed on a screen whose
dimensions (width and height) are in the ratio
16:9.
configured endpoint (refer to Configuring an
Do not allow this participant to start
contributing content channel video.
For more information, see Content per-
participant parameters.
Allow this participant to start contributing
content channel video.
Indicates which participant appears in the
largest pane.
Depending on the types of participant in the
conference (i.e. content channel, endpoint,
audio-only participant), you can select from
these options:
: the loudest
participant will given the largest
pane in the conference (the default
setting)
: the content
channel will be given the largest pane
in the conference
: the participant
that you select will be given the
largest pane in the conference
This setting will be overridden if a participant
is identified as "important" on the Conference
Participants List (see Viewing the conference
68
Download from Www.Somanuals.com. All Manuals Search And Download.
You can control the viewing angle, zoom, and focus of the camera on a participant's video endpoint. You can
customize this view by choosing this option:
1. Go to
2. Click a Conference name and then click on a participant's name.
3. Click the tab.
.
Click on one of the directional arrows to change Not all endpoints will respond to these controls.
the view direction of the camera.
In particular, endpoints with fixed cameras such
as most webcams.
Click on one of the magnifying options to zoom Not all endpoints will respond to the zoom
the view in or out.
controls, possibly including those that do respond
to the Movement controls
Click on one of the adjustment options to
improve the clarity of the image.
Not all endpoints will respond to the focus
controls, possibly including those that do respond
to the Movement controls
You may not want a participant to be visible in a conference, for example if they are only supervising, but not
contributing. The MCU allows this. Refer to the table below for details of the controls available:
Prevents others from seeing this participant's
video in conference views (mute).
This setting applies only to conference views. The
participant's video will still appear in the
conference participant list (see Viewing
attendant if a conference is not PIN-protected
Allows others to see this participant's video in
conference views (stop muting)
69
Download from Www.Somanuals.com. All Manuals Search And Download.
In general, the audio settings are for advanced troubleshooting. You can view these settings by selecting this option:
1. Go to
2. Click a Conference name and then click on a participant's name.
3. Click the tab.
.
These settings can help you resolve audio problems in conferences. For example:
Waveforms display a snapshot of the audio waveform received from the participant's endpoint. If the
participant is silent or speaking very quietly, the preview displays a horizontal green line. If the participant is
speaking, the line is wavy.
: use this setting if participants are too loud or too quiet. For example, if a participant is shouting
on the remote end, but is barely audible to others in the conference.
: a volume control which raises the decibel level by the specified amount. Enter a positive
value to raise the volume of the participant and a negative value to reduce it.
: a control to prevent DTMF tones being transmitted to other participants.
The MCU will still detect and act on the DTMF tones; this control prevents the tones from being audible to
participants.
You may mute a participant's audio. Refer to the table below for details of the controls available.
Prevents others from hearing this participant
(mute).
Allows others to hear this participant's audio (stop
muting).
70
Download from Www.Somanuals.com. All Manuals Search And Download.
You can add a custom layout to the choice of layouts available for this participant. You can customize this view by
choosing this option:
1. Go to
2. Click a Conference name and then click on a participant's name.
3. Click the tab.
.
Indicates whether a custom layout can be used for this When you click a new layout from the Available
participant. layouts, is automatically chosen with the
most recent layout selected.
Displays all pre-configured layouts that are available to You can only select one custom layout per
the participant. Click a layout to select it and make it participant.
available for the participant.
These layouts are designed to be suitable for all video conferencing situations:
These layouts are designed to be suitable for displaying composed views of standard (4:3) video streams on
widescreen (16:9) displays:
Note that the layouts depicted with slightly darker shading for the 'picture in picture' participants indicate those
layouts where the non-focused participants are slightly transparent and the focused participant can be seen 'through'
the non-focused participants. These layouts are:
and
71
Download from Www.Somanuals.com. All Manuals Search And Download.
You can view statistics about the video and audio streams between individual participants (endpoints) and the MCU
by choosing this option:
1. Go to
2. Click a Conference name and then click on a participant's name.
3. Click the tab.
.
If the participant is participating in the conference using audio only, the values for the video settings are not
populated.
Media statistics provide detailed information about the actual voice and video streams (Realtime Transport Protocol
(RTP) packets).
When examining media statistics for a conference's streaming viewers, there are many fewer applicable values and so
a different, more limited, set of information is displayed. In this case, the MCU shows how many streams of each
outgoing audio and video format are being transmitted.
Refer to the table below for additional information.
The audio codec in use, along with the current If the MCU has received information that an
packet size (in milliseconds) if known.
endpoint has been muted at the far end, this
will be indicated here.
The IP address and port from which the media
is originating.
Whether or not encryption is being used on the This field will only appear if the encryption
audio receive stream by this endpoint. feature key is present on the MCU.
The apparent variation in arrival time from that You should expect to see small values for this
expected for the media packets (in
milliseconds). The current jitter buffer also
displays in parentheses.
setting. Consistently large numbers typically
imply potential network problems.
The jitter buffer shows the current playout
delay added to the media to accommodate the
packet arrival jitter. Large jitter values indicate
a longer buffer.
Represents the audio volume originating from
the endpoint.
The number of audio packets destined for the
MCU from this endpoint.
72
Download from Www.Somanuals.com. All Manuals Search And Download.
The number of packet errors, including
You should expect to see small values for this
sequence errors, and packets of the wrong type. setting. Consistently large numbers typically
imply potential network problems.
Frame errors, as A/B where A is the number of A frame is a unit of audio, the size of which is
frame errors, and B is the total number of
dependent on codec.
frames received.
You should expect to see small values for this
setting. Consistently large numbers typically
imply potential network problems.
If the time stamps or marker bits (or both) are This field is not displayed when there is no
detected to be unreliable in the incoming video problem with the time stamps and marker bits.
stream, information will be displayed here.
Where there is a problem the following text is
displayed: "Media timestamps unreliable",
"Media marker bits unreliable", or both if both
conditions detected.
The audio codec being sent from the MCU to
the endpoint, along with the chosen packet size
in milliseconds.
The IP address and port to which the media is
being sent.
Whether or not encryption is being used on the This field will only appear if the encryption key
audio transmit stream by this endpoint.
is present on the MCU.
A count of the number of packets that have
been sent from the MCU to the endpoint.
The codec in use and the size of the picture that
the MCU is receiving from the specific
participant. If the picture is a standard size (for
example, CIF, QCIF, 4CIF, SIF) then this name
is shown in parentheses afterwards.
If ClearVision is enabled on the
page, and if it is in use on this
video stream, then the original and enhanced
resolutions are both displayed here.
The IP address and port (<IP address>:<port>)
of the device from which video is being sent
Whether or not encryption is being used on the This field will only appear if the encryption key
video receive stream from this endpoint.
is present on the MCU.
The negotiated bit rate available for the
endpoint to send video in.
This value represents the maximum amount of
video traffic that the remote endpoint will send
to the MCU. It may send less data than this (if it
does not need to use the full channel bit rate or
the MCU has requested a lower rate), but it
should not send more.
73
Download from Www.Somanuals.com. All Manuals Search And Download.
The bit rate (in bits per second) that the MCU This value might be less than the Channel bit rate
has requested that the remote endpoint sends. if:
The most-recently measured actual bit rate
displays in parentheses.
the MCU detects that the network
path to the remote endpoint has
insufficient capacity to maintain a
higher traffic rate
that endpoint's video stream's position
in the active conference compositions
does not require it
it has been necessary to reduce the
video bit rate because of the overall
call bit rate; the audio bit rate plus the
video bit rate should not exceed the
call bit rate
For example, if all participants in the
conference were watching a single participant at
full screen, no other participants' video streams
would be needed at all. So the MCU would
request that those streams were sent at a low
bit rate in order to avoid needless use of
network bandwidth.
If the receive bit rate has been limited to below
the maximum channel bit rate, the reason for
this limitation can be seen by moving over the
icon.
Represents the variation in video packet at
arrival time at the MCU.
The number of video packets destined for the
MCU from this endpoint
Video packet-level errors such as sequence
discontinuities, incorrect RTP details, and so
on. This is not the same as packets where the
content (the actual video data) is somehow in
error.
This value does not represent packets in which
the actual video data in the packets is in error.
The frame rate of the video stream currently
being received from the endpoint.
The number of frames with errors versus the
total number of video frames received.
The codec, size and type of video being sent
from the MCU to the endpoint.
The IP address and port of the device to which
the MCU is sending video.
74
Download from Www.Somanuals.com. All Manuals Search And Download.
Whether or not encryption is being used on the This field will only appear if the encryption key
video transmit stream to this endpoint.
is present on the MCU.
The negotiated available bandwidth for the
MCU to send video to the endpoint in.
The bit rate the MCU is attempting to send at The Transmit bit rate value might be less than the
this moment, which may be less than the
channel bit rate which is an effective maximum.
The actual bit rate, which is simply the
measured rate of video data leaving the MCU,
displays in parentheses.
Channel bit rate if :
the remote endpoint receiving the
video stream from the MCU has sent
flow control commands to reduce the
bit rate
it has been necessary to reduce the
primary video bit rate to allow
sufficient bandwidth for a content
video stream
If the transmit bit rate has been limited to
below the maximum channel bit rate, the
reason for this limitation can be seen by moving
over the
icon.
The number of video packets sent from the
MCU to this endpoint.
The frame rate of the video stream currently
being sent to the endpoint.
A number that represents the tradeoff between A smaller number implies that the MCU
video quality and frame rate.
prioritizes sending quality video at the expense
of a lower frame rate. A larger number implies
that the MCU is prepared to send lower quality
video at a higher frame rate.
Control statistics provide information about the control channels that are established in order that the endpoints can
exchange information about the voice and video streams (Real Time Control Protocol (RTCP) packets). Refer to the
table below for additional information.
The IP address and port to which RTCP (Real
Time Control Protocol) packets are being
received for the audio and video streams
A count of the number of "receiver report" type A single RTCP packet may contain more than one
RTCP packets seen by the MCU.
report of more than one type. These are generally
sent by any device receiving RTP (Real Time
Protocol) media from the network and are used
for auditing bandwidth, errors, and so on by the
MCU.
75
Download from Www.Somanuals.com. All Manuals Search And Download.
Media packet loss reported by receiver reports
sent to the MCU by the far end.
A count of the number of "sender report" type
RTCP packets received by the MCU.
These are typically sent by any device that is
sending RTP media.
A count of the number of reports seen by the
MCU that are neither sender nor receiver
reports.
The IP address and port to which the MCU is
sending RTCP packets about this stream.
The number of packets sent.
The IP address and port to which RTCP (Real
Time Control Protocol) packets are being sent for
the audio and video streams.
A count of the number of "receiver report" type A single RTCP packet may contain more than one
RTCP packets seen by the MCU.
report of more than one type. These are generally
sent by any device receiving RTP (Real Time
Protocol) media from the network and are used
for auditing bandwidth, errors, and so on by the
MCU.
A count of the reported packet loss on the control
channel.
A count of the number of "sender report" type
RTCP packets sent by the MCU.
These are typically sent by any device that is
sending RTP media.
A count of the number of reports seen by the
MCU that are neither sender nor receiver
reports.
The IP address and port to which the MCU is
sending RTCP packets about this stream.
The number of packets sent.
The number of fast update requests sent and
received.
The number of flow control messages sent and
received.
76
Download from Www.Somanuals.com. All Manuals Search And Download.
You can send a short text message to a specific participant currently in the conference by choosing:
1. Go to
2. Click a Conference name and then click on a participant's name.
3. Click the tab.
.
This message appears overlaid on the participant's view, even if the participant is viewing the conference via
streaming.
Enter the message to send to this participant.
Messages must be fewer than 256 characters, but
depending on the viewing screen, messages at the
higher-end of this limit might not display
properly. So, consider limiting messages to about
180 characters. Messages longer than 256
characters will not be truncated; they will not
display at all.
You can disable this setting from
The vertical position of the message on the
conference display.
Choose from the top, middle, or bottom of the
conference display.
Indicates how long the message appears on the
endpoint's video screen.
The default setting is 30 seconds. To remove a
message before it times out, click
.
77
Download from Www.Somanuals.com. All Manuals Search And Download.
You can view diagnostics for an individual participant's connection to the MCU by choosing this option:
1. Go to
2. Click a conference name and then click on a participant's name.
3. Click the tab.
.
This page shows various low-level details pertaining to the endpoint's communication with the MCU. You are not
likely to need to use any of the information on this page except when troubleshooting specific issues under the
guidance of technical support.
78
Download from Www.Somanuals.com. All Manuals Search And Download.
You can move participants between conferences. Participants can be moved to any conference, but although
participants can be moved from auto attendants they cannot be moved to them.
To move a participant:
1. Go to
>
.
2. Click and drag the name of the participant to the required destination conference.
Note that participants dragged and dropped into a conference on the web interface will be chairperson participants.
(For more information about chairperson and guest participants, refer to Adding and updating conferences.)
To move multiple participants:
1. Go to
>
.
2. Check the tick boxes for every participant you want to move and drag them to the required destination
conference.
To disconnect a participant from a conference:
1. Go to
>
.
2. Click and drag the name of the participant in to
area at the bottom of that page.
Note that dragging and dropping a participant in to the
area simply disconnects the participant
from the conference. It does not remove them from a scheduled conference. That is, when the conference next runs
that participant will be called if their endpoint is a pre-configured endpoint for that conference.
79
Download from Www.Somanuals.com. All Manuals Search And Download.
The Codian MCU allows you to configure auto attendants on it, which allows users to more easily join conferences.
Adding a custom banner
You can display an overview of the configured auto attendants on the MCU:
1. Go to
.
2. Click the
tab.
The name of the auto attendant
The number that you can dial to connect to the
auto attendant
The status of an auto attendant with respect to its For tips on configuring gatekeepers, see
This auto attendant is not configured to
be registered with the gatekeeper;
because of this, there is no applicable
registration status to show.
This auto attendant is in the process of
registering with the gatekeeper.
The auto attendant is in the process of
unregistering with the gatekeeper. This
might occur if:
o
Gatekeeper registration has
been turned off (either for that
auto attendant only or for the
entire MCU)
o
The configured gatekeeper has
just been changed and the MCU
is in the process of
unregistering from the previous
gatekeeper before registering
its auto attendants with the new
one.
/
If the MCU fails to register an auto
80
Download from Www.Somanuals.com. All Manuals Search And Download.
attendant with the gatekeeper, it enters
these states temporarily before re-
attempting the registration.
The auto attendant has been registered
successfully with the gatekeeper and can
be contacted using the number
indicated.
SIP registration. The possible states are:
This auto attendant is not configured to
be registered with the SIP registrar;
because of this, there is no applicable
registration status to show.
This auto attendant is in the process of
registering with the SIP registrar.
The auto attendant is in the process of
unregistering with the SIP registrar. This
might occur if:
o
SIP registration has been turned
off (either for that auto
attendant only or for the entire
MCU)
o
The configured SIP registrar has
just been changed and the MCU
is in the process of
unregistering from the previous
SIP registrar before registering
its auto attendants with the new
one.
/
If the MCU fails to register an auto
attendant with the SIP registrar, it enters
these states temporarily before re-
attempting the registration.
The auto attendant has been registered
successfully with the SIP registrar and
can be contacted using the number
indicated.
Whether a PIN has been configured to restrict
access to the auto attendant
The total number of calls received by the auto
attendant since the last restart
A thumbnail of the custom banner, if one has
been specified
81
Download from Www.Somanuals.com. All Manuals Search And Download.
Auto attendants simplify the way participants can join conferences. By calling an auto attendant using their video
endpoint, a participant can choose from menu options and join or start conferences. No gateway or gatekeeper is
required. (The auto attendant is configured on the MCU.)
To add an auto attendant:
1. Go to
2. Click the
3. Click
.
tab.
.
4. Refer to the table below for the most appropriate settings for the auto attendant.
5. After entering the settings, click
.
To update an existing auto attendant:
1. Go to
2. Click the
.
tab.
3. Click the name of an auto attendant.
4. Refer to the table below for the settings to change for this auto attendant.
5. After updating the settings, click
.
The name of the auto attendant.
An optional title to be shown at the top of the
screen when an endpoint calls in to this auto
attendant.
The number with which to register the auto
attendant on the gatekeeper and/or SIP registrar. details.
Check
if you want the Numeric Note that for SIP, you must configure the ID with
ID registered with the H.323 gatekeeper; check the SIP registrar for the MCU to be able to
if you want the Numeric ID registered register that ID.
with the SIP registrar.
Assigns a password to the auto attendant.
If you set a PIN, all participants using the auto
attendant will be required to enter this password.
Verifies the password.
If Enabled, displays the Create new conference option If disabled, participants will not be able to create
on the auto attendant so that the participant can new conferences from the auto attendant.
create new ad hoc conferences using the auto
attendant.
Note that this option will not be available if you
82
Download from Www.Somanuals.com. All Manuals Search And Download.
have enabled
on the
page. When using port
reservation mode, there can be no ad hoc
conferences. For more information about port
reservation, refer to Reservation of MCU media
If Enabled, displays ad hoc conferences as well as If disabled, participants can only view scheduled
scheduled conferences as options on the auto
attendant.
conferences; ad hoc conferences will not be
shown.
Note that this option will not be available if you
have enabled
on the
page. When using port
reservation mode, there can be no ad hoc
conferences. For more information about port
reservation, refer to Reservation of MCU media
Enables all auto attendant participants to join any
conferences scheduled to start while they are
using the auto attendant.
Choose the conferences to list on the auto
attendant by selecting check boxes.
If a scheduled conference has been configured as a
private conference, it will not appear in this list.
To configure a conference as private:
1. Go to the
the name of the conference.
2. On the tab, set the
option to Private.
and click on
Check the name of any other configured auto attendant that you want to be accessible from the auto
attendant that you are adding.
83
Download from Www.Somanuals.com. All Manuals Search And Download.
You can add a custom banner image to any auto attendant configured on the MCU as follows:
1. Go to
2. Click the
.
tab.
3. Click the name of a configured auto attendant.
4. Click the tab.
5. Refer to the table below to determine the most appropriate settings.
Chooses the default Codian MCU graphic to use
for your banner.
The custom banner identified for this auto
Nothing displays here until you upload the
to remove this custom graphic as described below.
after
attendant. Click
graphic as the banner. Click
uploading a new graphic.
The custom graphic to be used for a banner. Click The image file can be a JPEG, GIF or Windows
to locate the file on your hard drive.
BMP format with a maximum size of 1600 x
1200 pixels. If the file is smaller than this size, the
MCU will scale it to fit in the auto attendant's
banner area. Click
to display.
84
Download from Www.Somanuals.com. All Manuals Search And Download.
To display the Endpoint List, go to
.
The Endpoint List displays all endpoints that have been configured within the MCU.
To add a new H.323 endpoint, select
To add a new SIP endpoint, select
To add a new VNC endpoint, select
.
.
.
To delete configured endpoints, check the ones you want to delete and select
.
The name of the endpoint.
The IP address, host name, H.323 ID, E.164 number, or SIP URI of the endpoint.
Whether it is an H.323, SIP, or VNC endpoint.
85
Download from Www.Somanuals.com. All Manuals Search And Download.
You can configure H.323 endpoints to work with the MCU by choosing
. This makes it easier
to add endpoints to conferences because you can choose names from a list rather than adding network addresses.
A Codian IP VCR can be configured as an H.323 endpoint and added as a participant in a conference. If the IP VCR is
configured to do so, it will start recording as soon as the conference starts. You can also configure a folder's
Recording ID as an endpoint and in this way, when a conference starts, the IP VCR can start recording directly into a
specific folder. For more information about using the IP VCR in this way, refer to the IP VCR's online help.
Recordings on a Codian IP VCR can be configured as H.323 endpoints. In this way, an audio-only participant can
contribute an IP VCR recording as his video stream (using the associated endpoint function, see Adding and updating
users). This function is also useful where you have a recording that you might like to view within a conference.
Refer to the table below for tips on adding an H.323 endpoint to the MCU. After entering the settings, click
.
The name of the endpoint.
The IP address, host name, or an E.164 address You can configure this endpoint as needing to be
(phone number).
reached via an H.323 gateway without that
gateway being already configured on the MCU.
To do this, set this field to be <gateway
address>!<E.164>.
The gateway through which the endpoint
connects.
To configure a gateway on the MCU, go to
. For more information, refer to
These fields are used to identify incoming calls as The endpoint is recognized if all filled-in fields in
being from the endpoint:
this section are matched. Fields left blank are not
considered in the match.
Name: This must be the name that the
When you configure Call-in match parameters, an
endpoint will be recognized as this pre-configured
endpoint and the Conferencing parameters will be
applied to a call from this endpoint.
endpoint sends to the MCU
IP address: The IP address of the endpoint
E.164: The E.164 number with which
the endpoint is registered with the
gatekeeper
The name that will be displayed in a conference The name you enter here will override any
as a label for this endpoint.
default name configured on the endpoint. It will
also override any other default name that might
appear for an endpoint. For example, an
endpoint's default name can be the name of the
gateway through which the call was placed, or if
the endpoint is called-in via a gatekeeper, its
E.164 number.
Note that once an endpoint has connected, you
cannot change the display name.
86
Download from Www.Somanuals.com. All Manuals Search And Download.
Choose whether to use the unit-wide setting for The settings for motion (frames per second) and
motion/sharpness trade off, or configure an
individual setting for use with this endpoint.
Choose from:
sharpness (frame size or resolution) are
negotiated between the endpoint and the MCU.
This setting controls how the MCU will negotiate
the settings to be used with this endpoint.
<use box-wide setting>: this is the default
value. In this case, the connection to the
endpoint will use the motion /
sharpness tradeoff setting from the
page.
Favor motion: the MCU will try and use a
high frame rate. That is, the MCU will
strongly favor a resolution of at least 25
frames per second
Favor sharpness: the MCU will use the
highest resolution that is appropriate for
what is being viewed
Balanced: the MCU will select settings
that balance resolution and frame rate
(where the frame rate will not be less
than 12 frames per second)
Choose the setting for transmitted video
Retain the default setting (use box-wide setting)
resolutions from the MCU to this endpoint. This unless you are experiencing problems with the
setting overrides the unit-wide setting on the
page
display of certain resolutions by this endpoint.
Endpoints advertise the resolutions that they are
able to display. The MCU then chooses from
those advertised resolutions, the resolution that it
will use to transmit video. However, some
endpoints do not display widescreen resolutions
optimally. Therefore, you might want to use this
setting to restrict the resolutions available to the
MCU for transmissions to this endpoint.
Whether this endpoint is permitted to contribute This setting is provided to allow you to
the conference content channel. Choose from:
individually configure whether or not an
endpoint is allowed to contribute content to a
conference.
<use conference default>: this endpoint will use the
Content contribution from endpoints setting from the
per-conference configuration.
To use the content channel, the Content status
must be enabled at the unit-wide level (on the
page) and for any given
conference Content channel video must also be
Enabled: This endpoint is allowed to contribute
the content channel, even if content contribution
from endpoints is disabled in the per-conference
configuration.
Disabled: This endpoint is not allowed to
contribute the conference channel, even if
content contribution from endpoints is enabled in
the per-conference configuration.
87
Download from Www.Somanuals.com. All Manuals Search And Download.
Whether this endpoint is allowed to receive a
separate content stream when in a conference.
This setting is provided to allow you to
individually configure whether or not an
endpoint is allowed to receive content from a
conference.
To use the content channel, the Content status
must be enabled at the unit-wide level (on the
page) and for any given
conference Content channel video must also be
Choose a border size for video transmitted to this This sets a border thickness to display around the
endpoint.
video image. This is useful where the image is
displaying off the edges of the participant's
screen; use a border to force the image to display
properly.
Applying a border size here means that this
border size will always be used for this endpoint's
transmitted video. Note that you can also apply a
border to a participant in a conference from the
page.
Sets the layout family to be used when calling out If this is set to Use box-wide setting then the default
to this endpoint.
view family that has been configured via the
Conference settings page will be used.
The network capacity (measured in bits per
These settings take priority over the Default
second) used by the media channels established by bandwidth from MCU setting configured in the
the MCU to a single participant.
global Conference settings (see Conference
The maximum combined media bandwidth
advertised by the MCU to endpoints.
These settings take priority over the Default
bandwidth to MCU setting configured in the global
Whether this endpoint is able to change their
view layout via Far-End Camera Controls or
DTMF tones.
This setting takes precedence over the per-
conference layout control setting for conferences
that the endpoint is invited into.
Set the initial audio status of an endpoint to be
either active or muted.
If set to muted, when the endpoint joins a
conference, it will not be able to contribute audio
to the conference. For example, you can mute
audio from an endpoint if somebody wants to be
seen in the conference, but does not want to
contribute verbally. You can mute both audio and
video if required. This can be altered during the
course of the conference by going to
and clicking on the name of a conference and
altering this participant's settings.
Set the initial video status of an endpoint to be
either active or muted.
If set to muted, when the endpoint joins a
conference, it will not be able to contribute video
88
Download from Www.Somanuals.com. All Manuals Search And Download.
to the conference. For example, you can mute
video from an endpoint if somebody wants to see
the conference, but not be seen themselves. You
can mute both audio and video if required. This
can be altered during the course of the
conference by going to
and clicking
on the name of a conference and altering this
participant's settings.
When a participant disconnects from a
conference and only endpoints set to Automatic
disconnection are left, all those participants are
disconnected.
Set to enabled if you want this endpoint to be
automatically disconnected from conferences
when only endpoints set to Automatic disconnection
remain in a conference when any other
participant has disconnected.
Note that this setting is useful where you have
configured a Codian IP VCR as an endpoint so
that the IP VCR can be automatically called into a
conference to record the session. In this case, the
IP VCR will stop recording when the conference
ends (that is, when everyone has left the
conference). For more information about using
the IP VCR in this way, refer to the IP VCR
online help.
Can be used to ensure only specific codecs are
permitted on calls to (and received from) this
endpoint.
If Enabled, you can choose which codecs are
allowed to be used when communicating with
this endpoint. When enabled this setting
overrides the unit-wide codec selection on the
page.
89
Download from Www.Somanuals.com. All Manuals Search And Download.
To configure the SIP endpoints to work with the MCU, go to
. This makes it easier to add
endpoints to conferences because you can choose names from a list rather than adding network addresses.
Refer to the table below for tips on adding a SIP endpoint to the MCU. After entering the settings, click
.
The name of the endpoint.
The IP address, host name, directory number, or The address of the SIP endpoint can be a
SIP URI (in the format 1234@codian.com).
directory number if you are using a SIP registrar.
Allows calls to this endpoint to use a directory
number (in the Address field) and the SIP registrar. SIP registrar on the
If you have this enabled, you must configure the
page.
Select the protocol to be used for call control
messages for outgoing call connections to this
endpoint.
If you want this endpoint to use the unit-wide
outgoing transport setting, select box-wide default
transport. If this endpoint uses TCP, select TCP as
the outgoing transport. If this endpoint uses
UDP, select UDP as the outgoing transport. If
this endpoint uses TLS, select TLS. Note that if
you want the MCU to use TLS for call setup, you
must have the encryption feature key (or the
Secure management feature key) and the TLS
service must be enabled on the
page.
Using TLS for call setup is not sufficient for the
call to be considered encrypted such that it can
participate in a conference which requires
encryption. Where encryption is required in the
conference configuration, a SIP call must use
SRTP. For more information about SIP
settings.
This setting overrides the unit-wide setting for
Outgoing transport on the
page. For
more information about configuring SIP, refer to
These fields are used to identify incoming calls as The endpoint is recognized if all filled-in fields in
being from the endpoint:
this section are matched. Fields left blank are not
considered in the match.
Username: This must be the username
that the endpoint sends to the MCU
IP address: The IP address of the endpoint
Note that in some cases a SIP registrar can cause a
call to appear to come from the IP address of the
registrar rather than the IP address of the
90
Download from Www.Somanuals.com. All Manuals Search And Download.
endpoint. In this case, to use call-in match
parameters, leave the IP address field blank and
enter the correct username. The call will be
matched by username.
When using LCS, the username that will be
matched is the user's display name (e.g. Peter
Rabbit) rather than the sign-in name
(bluecoat@codian.com).
The name that will be displayed in a conference The name you enter here will override any
as a label for this endpoint.
default name configured on the endpoint. It will
also override any other default name that might
appear for an endpoint. For example, an
endpoint's default name can be the name of the
gateway through which the call was placed, or if
the endpoint is called-in via a gatekeeper, its
E.164 number.
Note that once an endpoint has connected, you
cannot change the display name.
Choose whether to use the box-wide setting for The settings for motion (frames per second) and
motion/sharpness trade off, or configure an sharpness (frame size or resolution) are
individual setting for this endpoint. Choose from: negotiated between the endpoint and the MCU.
This setting controls how the MCU will negotiate
the settings to be used with this endpoint.
Use box-wide setting: this is the default
value. In this case, the endpoint will use
the motion/sharpness tradeoff setting
from the
page
Favor motion: the MCU will try and use a
high frame rate. That is, the MCU will
strongly favor a resolution of at least 25
frames per second
Favor sharpness: the MCU will use the
highest resolution that is appropriate for
what is being viewed
Balanced: the MCU will select settings
that balance resolution and frame rate
(where the frame rate will not be less
than 12 frames per second)
Choose the setting for transmitted video
Retain the default setting (use box-wide setting)
resolutions from the MCU to this endpoint. This unless you are experiencing problems with the
setting overrides the unit-wide setting on the
page.
display of certain resolutions by this endpoint.
Endpoints advertise the resolutions that they are
able to display. The MCU then chooses from
those advertised resolutions, the resolution that it
will use to transmit video. However, some
endpoints do not display widescreen resolutions
optimally. Therefore, you might want to use this
setting to restrict the resolutions available to the
MCU for transmissions to this endpoint.
91
Download from Www.Somanuals.com. All Manuals Search And Download.
Whether this endpoint is permitted to contribute This setting is provided to allow you to
the conference content channel. Choose from:
individually configure whether or not an
endpoint is allowed to contribute content to a
conference.
<use conference default>: this endpoint will use the
Content contribution from endpoints setting from the
per-conference configuration.
To use the content channel, the Content status
must be enabled at the unit-wide level (on the
page) and for any given
conference Content channel video must also be
Enabled: This endpoint is allowed to contribute
the content channel, even if content contribution
from endpoints is disabled in the per-conference
configuration.
Disabled: This endpoint is not allowed to
contribute the conference channel, even if
content contribution from endpoints is enabled in
the per-conference configuration.
Currently, all content is sent to SIP endpoints in
the main video channel.
Choose a border size for video transmitted to this This sets a border thickness to display around the
endpoint.
video image. This is useful where the image is
displaying off the edges of the participant's
screen; use a border to force the image to display
properly.
Applying a border size here means that this
border size will always be used for this endpoint's
transmitted video. Note that you can also apply a
border to a participant in a conference from the
page.
Sets the layout family to be used when calling out If this is set to Use box-wide setting then the default
to this endpoint.
view family that has been configured via the
Conference settings page will be used.
The network capacity (measured in bits per
These settings take priority over the Default
second) used by the media channels established by bandwidth from MCU setting configured in the
the MCU to a single participant.
global Conference settings (see Conference
The maximum combined media bandwidth
advertised by the MCU to endpoints.
These settings take priority over the Default
bandwidth to MCU setting configured in the global
Sets whether this endpoint is able to change their This setting takes precedence over the per-
view layout via Far-End Camera Controls or
DTMF tones.
conference layout control setting for conferences
that the endpoint is invited into.
Set the initial audio status of an endpoint to be
either active or muted.
If set to muted, when the endpoint joins a
conference, it will not be able to contribute audio
to the conference. For example, you can mute
audio from an endpoint if somebody wants to be
92
Download from Www.Somanuals.com. All Manuals Search And Download.
seen in the conference, but does not want to
contribute verbally. You can mute both audio and
video if required. This can be altered during the
course of the conference by going to
and clicking on the name of a conference and
altering this participant's settings.
Set the initial video status of an endpoint to be
either active or muted.
If set to muted, when the endpoint joins a
conference, it will not be able to contribute video
to the conference. For example, you can mute
video from an endpoint if somebody wants to see
the conference, but not be seen themselves. You
can mute both audio and video if required. This
can be altered during the course of the
conference by going to
and clicking
on the name of a conference and altering this
participant's settings.
When a participant disconnects from a
conference and only endpoints set to Automatic
disconnection are left, all those participants are
disconnected.
Set to enabled if you want this endpoint to be
automatically disconnected from conferences
when only endpoints set to Automatic disconnection
remain in a conference when any other
participant has disconnected.
Can be used to ensure only specific codecs are
permitted on calls to (and received from) this
endpoint.
If Enabled, you can choose which codecs are
allowed to be used when communicating with
this endpoint. When enabled, this setting
overrides the unit-wide codec selection on the
page.
93
Download from Www.Somanuals.com. All Manuals Search And Download.
You can configure a VNC (Virtual Network Computing) endpoint on the MCU by choosing
.
This makes it easier to add a VNC session to conferences because you can choose its name from a list rather than type
its network address.
You can add VNC endpoints to the MCU. This enables you to have software applications running on a remote
computer added to a conference. For example, if a speaker has a set of slides to present during a conference, you can
add them as a VNC endpoint. After entering the settings, click
.
The name of the computer used for the VNC
application (VNC endpoint).
The IP address or host name of the computer
used for the VNC application (VNC endpoint).
The port used for communication to the VNC
endpoint.
The VNC server password for the computer
you're trying to view.
Re-enter the VNC password.
When a participant disconnects from a
conference and only endpoints set to Automatic
disconnection are left, all those participants are
disconnected.
Set to enabled if you want this endpoint to be
automatically disconnected from conferences
when only endpoints set to Automatic disconnection
remain in a conference when any other
participant has disconnected.
94
Download from Www.Somanuals.com. All Manuals Search And Download.
You can configure the Codian MCU to work with one or more H.323 gateways. The MCU can then effectively call
through these configured gateways to one or more endpoints which are registered with the gateway but would not be
reachable directly from the MCU.
For example, an IP PBX could be configured as a gateway, and the MCU could then call its registered E.164
numbers. An ISDN gateway can be configured as a gateway on the MCU allowing calls to ISDN endpoints and
telephones.
You can add a Codian IP VCR as a gateway. This enables the MCU automatically call the IP VCR into a conference
without the need for a gatekeeper; and in this way, the IP VCR can record directly into the folder you specify. For
more information about using the IP VCR in this way, refer to the IP VCR online help.
The gateway list shows all of the currently configured H.323 gateways. To access this list, go to
.
The descriptive name of the gateway.
The IP address or host name of the gateway.
The configured preferred bandwidth to the MCU from the gateway, or <default value> if no
preference has been specified.
The configured preferred bandwidth from the MCU to the gateway, or <default value> if no
preference has been specified.
To delete configured gateways, check the ones you want to delete and select
.
95
Download from Www.Somanuals.com. All Manuals Search And Download.
You can configure the Codian MCU with one or more H.323 gateways:
To add an H.323 gateway, go to
. After entering the settings described
below, click
.
To update an existing H.323 gateway, go to
settings described below, click
and click on a gateway name. After updating the
.
The descriptive name of the gateway.
All gateways must have a unique name.
The IP address or host name of the gateway.
Choose whether to use the unit-wide setting for The settings for motion (frames per second) and
motion/sharpness trade off, or configure an sharpness (frame size or resolution) are
individual setting for this gateway. Choose from: negotiated between the endpoint and the MCU.
This setting controls how the MCU will negotiate
the settings to be used with this endpoint.
Use unit-wide setting: this is the default
value. In this case, connections to the
gateway will use the motion/sharpness
tradeoff setting from the
page
Favor motion: the MCU will try and use a
high frame rate. That is, the MCU will
strongly favor a resolution of at least 25
frames per second
Favor sharpness: the MCU will use the
highest resolution that is appropriate for
what is being viewed
Balanced: the MCU will select settings
that balance resolution and frame rate
(where the frame rate will not be less
than 12 frames per second)
The network capacity (measured in bits per
second) used by the media channels established by
the MCU to a single participant.
Sets the bandwidth that the endpoint will
advertise to the MCU when it calls it.
96
Download from Www.Somanuals.com. All Manuals Search And Download.
The MCU contains a built-in gatekeeper with which devices can register multiple IDs. IDs can be numbers, H.323
IDs (e.g. Fredsendpoint) or prefixes.
Up to 25 devices can be registered without a feature key. Feature keys can be purchased to increase this number.
: The MCU can register with its own built-in gatekeeper. The MCU then counts as one registered device. See
Configuring gatekeeper settings.
To start the gatekeeper, go to
gatekeeper. (On the MCU, ports are not open by default for security reasons.) Then go to
in the Status field and click
and select the H.323 gatekeeper check box to open a port for the
, select Enabled
. If you attempt to enable the built-in gatekeeper without opening the port,
an error message is displayed.
You can optionally configure the built-in gatekeeper with up to two neighboring gatekeepers. This means that if the
built-in gatekeeper receives a request (known as an Admission Request or ARQ) to resolve an ID to an IP address and
that ID is not currently registered with it then it will forward that request to its neighbor gatekeeper(s), as a Location
Request (LRQ). The built-in gatekeeper will then use the information received from the neighbor(s) to reply to the
original request.
You can also configure the behavior of the built-in gatekeeper on receipt of LRQs from another gatekeeper. It can:
send LRQs regarding unknown IDs to its neighbor(s)
reply to LRQs from other gatekeepers
accept LCFs (Locations Confirms) from non-neighboring gatekeepers
Refer to this table for assistance when configuring the built-in gatekeeper:
Enables or disables the built-in
gatekeeper.
To use the built-in gatekeeper, you must enable it
here.
Enter the IP address(es), or
hostname(s) (or <host>:<port
These are the gatekeepers to which the built-in
gatekeeper will send an LRQ if it has received an
number> to specify a port other than ARQ to resolve an ID which it does not currently
the default of 1719 on the neighboring have registered. The built-in gatekeeper will then
gatekeeper), of the neighboring
gatekeeper(s).
use the information received from the neighbor(s)
to reply to the original request.
Configures the built-in gatekeeper to These requests can come from any gatekeeper
reply to LRQs from other gatekeepers. which has the MCU's built-in gatekeeper
configured as one of its neighbors.
97
Download from Www.Somanuals.com. All Manuals Search And Download.
Configures the built-in gatekeeper to Unless you have selected to Accept LRQs, you
send (or not to send) LRQs regarding cannot configure the MCU to forward any LRQs.
unknown IDs to its neighbor(s).
Choose from the options:
Enabling using received return address can be a
significant security risk. Only use this setting with
proper cause.
Disabled: The MCU will only
respond to LRQs about IDs
registered with itself. It will
not forward LRQs about IDs
that are not registered with
itself to neighboring
gatekeepers.
Enabled, using local return
address: The MCU will put, in
the LRQ, its own address as
the return address for the
LCF.
Enabled, using received return
address: The MCU will put, in
the LRQ, the address of the
gatekeeper that originated the
request as the return address
for the LCF. Use this option
only if you are configuring the
MCU to operate in an
environment with a multiple-
level gatekeeper hierarchy.
For example, the 'received
address' is required by the
national gatekeepers
connected to the Global
Dialing Scheme (GDS).
This setting enables the built-in
gatekeeper to accept LCF message
responses from any IP address.
This setting is for use in environments with a
multiple-level gatekeeper hierarchy. For
example, this feature is required by the national
gatekeepers connected to the Global Dialing
Scheme (GDS).
Enabling this setting can be a significant security
risk. Only use this setting with proper cause.
The number of registered devices is shown in the format X / Y where Y is the number of registered devices that your
built-in gatekeeper is licensed for. Equally, the total number of registered IDs is shown as Z / 1000, where 1000 is
the maximum number of registrations allowed over all registered devices.
98
Download from Www.Somanuals.com. All Manuals Search And Download.
Below these summary figures is a table showing individual registrations. Registrations can be viewed by registered ID
(the "ID view") or by device (the "Registration view"), giving complete and easily searchable lists. Switch between
the views by clicking on the appropriate button.
The Registration view shows the summary per device (also known as the registrant), while the ID view shows
individual registrations. This means that registrations from the same device are not necessarily listed together in the
ID view but the view can be sorted by Registrant or Index to help you identify IDs belonging to the same registrant.
The ID which the registrant has registered with
the gatekeeper.
IDs can be numbers, H.323 IDs or prefixes.
One of: E.164 (digits), H.323 ID or Prefix.
The type of registration.
This registrations index within the total number In the format X / Y where Y is the number of
of registrations that this registrant has made with registrations that this registrant has made with the
the gatekeeper.
built-in gatekeeper, and X is this particular
registration's position within the total. Therefore,
if a device registered 3 IDs with the gatekeeper
and this was the second registration to be made,
the Index would be 2 / 3.
The IP address of the device that this registration If the remote device has indicated via the RAI
was made from.
(Resource Availability Indication) mechanism that
it is close to its resource limit, the Registrant will
be labeled as "almost out of resources".
This view shows a one-line summary for each device registered with the built-in gatekeeper.
To deregister one or more devices (and all registrations for these devices), select the check boxes for the appropriate
entries and then click
.
The IP address of the device.
If the remote device has indicated via the RAI
(Resource Availability Indication) mechanism that
it is close to its resource limit, the Registrant will
be labeled as "almost out of resources".
The registered H.323 ID of the device.
To help identify registering devices, if the
registrant has registered a H.323 ID (which will
typically be its device name) that H.323 ID is
shown here. If the device has registered multiple
H.323 IDs, only the first is displayed.
The number of registrations that this device has Click
to display individual registrations for
made with the built-in gatekeeper.
the selected device. (The format is the same as
the ID view, but the table only includes entries
for one device.)
The time today or date and time of the last
registration.
99
Download from Www.Somanuals.com. All Manuals Search And Download.
The MCU is pre-configured with two user accounts ("admin" and "guest"), but you can also add other users (see
Adding and updating users). Refer to the table below for descriptions of the pre-configured users.
The MCU must have at least one configured user After logging into the MCU for the first time (see
with administrator privileges. By default, the
User ID is "admin" and no password is required. the User ID and password for this account. The
privilege level is fixed at administrator for the
admin user - who can see all the pages and change
settings.
The MCU must have at least one configured user You cannot change the name of the "guest" User
with access privileges below administrator. The
fixed User ID for this user is "guest" and by
default no password is required.
ID, but you can add a password.
You can modify the system defined user accounts if you need to. For example, for security, you should add a
password to the admin account.
Note that you can also create new accounts with administrator or lower access privileges in addition to these pre-
Refer to these topics for assistance in modifying these users:
Modifying the "guest" User
The "admin" user is the default login account initially used to access the web interface.
1. Go to
2. Click
.
.
3. Refer to the table below to determine the most appropriate settings for the user.
4. After entering the settings, click
.
The log-in name used to access the MCU web
browser.
The required password, if any.
Verifies the required password.
The privilege level, which is fixed at administrator. See User privileges for detailed explanations.
100
Download from Www.Somanuals.com. All Manuals Search And Download.
1. Go to
2. Click
.
.
3. Refer to the table below to determine the most appropriate settings for the user.
4. After entering the settings, click
.
The log-in name used to access the MCU web
browser. This is fixed at "guest"
The required password, if any.
Verifies the required password.
level except administrator.
101
Download from Www.Somanuals.com. All Manuals Search And Download.
Every configured user in the MCU has an associated privilege level. There are seven defined privilege levels which
determine the amount of control the user has over the MCU and its settings. Refer to the table below for details.
The main difference between an administrator and users with lower privilege levels is that
administrators can change settings that affect all conferences and the configuration of the MCU itself,
whereas other users only have access to individual conferences and to their own profiles.
Users with administrator access can:
View MCU-wide status (
Access all settings pages (
Perform software upgrades (
)
)
)
Change system-wide conference settings (
View the Event log (
)
)
Configure H.323 gateways (
)
Configure the built-in gatekeeper (
)
Manage users (
)
Manage endpoints (
)
Configure auto attendants (
Fully control conferences (
)
)
Users with this privilege level can:
Change their own profile (
)
View the list of active conferences (
View conferences via streaming (
)
)
View participant lists for active conferences (
Schedule new conferences (
Fully control and modify all conferences (
)
)
)
Configure H.323 gateways (
Manage endpoints (
)
)
Users with this privilege level can:
Change their own profile (
)
View the list of active conferences (
View conferences via streaming (
)
)
View participant lists for active conferences (
Schedule new conferences (
Fully control and modify conferences they own (
Exercise limited control of conferences owned by other users (
)
)
)
)
by limited control.
102
Download from Www.Somanuals.com. All Manuals Search And Download.
Users with this privilege level can:
Change their own profile (
)
View the list of active conferences (
View conferences via streaming (
)
)
View participant lists for active conferences (
)
Schedule new conferences (
)
Fully control and modify conferences they own (
)
Users with this privilege level can:
Change their own profile (
)
View the list of active conferences (
View conferences via streaming (
View participant lists for active conferences (
)
)
)
)
Users with this privilege level can:
Change their own profile (
)
View the list of active conferences (
View conferences via streaming (
)
)
Users with this privilege level can:
Change their own profile (
)
View the list of active conferences (
103
Download from Www.Somanuals.com. All Manuals Search And Download.
The User list gives you a quick overview of all configured users on the MCU and provides a brief overview of some of
their settings. To display this list, go to . Refer to the table below for assistance.
The log-in name that the user needs to use to access the MCU web browser.
The full name of the user.
The access privileges associated with this user.
The associated E.164 telephone number.
The associated video endpoint.
The configured image to display for this user.
104
Download from Www.Somanuals.com. All Manuals Search And Download.
You can add users to and update users on the MCU. Although most information is identical for both tasks, some fields
differ. The MCU supports up to 200 users.
To add a user:
1. Go to
2. Click
.
.
3. Complete the fields referring to the table below to determine the most appropriate settings for the user.
4. After entering the settings, click
.
To update an existing user:
1. Go to
.
2. Click a user name.
3. Edit the fields as required referring to the table below to determine the most appropriate settings for the
user.
4. After entering the settings, click
.
Identifies the log-in name that the user will use to Although you can enter text in whichever
access the MCU web browser.
character set you require, note that some
browsers and FTP clients do not support Unicode
characters.
The full name of the user.
The required password, if any.
Although you can enter text in whichever
character set you require, note that some
browsers and FTP clients do not support Unicode
characters.
Note that passwords are stored in the
configuration.xml file as plain text unless the
MCU is configured to hash store passwords. For
Verifies the required password.
Prevents user from changing password.
The access privileges to be granted to this user.
This is useful where you want multiple users to
be able to use the same user ID.
105
Download from Www.Somanuals.com. All Manuals Search And Download.
Associates an E.164 telephone number with a
user account.
If the MCU receives a call from the E.164 phone
number provided, it matches the number to the
user account. This allows the MCU to take the
appropriate action if one (or both) of the
following fields are completed.
Associates a configured endpoint with the user. If you set an associated video endpoint for a user,
This is used when a participant's video stream is when a call is received from the E.164 phone
from a separate device such as a web camera on a number, the MCU knows that that call is audio-
PC or a recording from a Codian IP VCR.
only. To provide the user with a video stream,
the MCU calls the endpoint entered in this field.
The user then has the complete conference
experience with the audio on the telephone and a
separate video stream for example on a computer
with a web camera installed. The audio and video
steams are matched so that the layout views for
all participants reflect the level of audio received
on the call from the E.164 phone number.
Do not set the user's E.164 phone number and
Associated video endpoint as the same number. If a
user is going to be a normal video endpoint user,
simply enter the E.164 phone number and leave
the associated video endpoint field set to None.
If required, a user's video contribution can be a
recording on a Codian IP VCR. In this case the
recording must first be configured as an H.323
endpoint on the MCU.
about adding endpoints.
The image to be used if a user joins a conference This option is only available after you add the
as an audio-only participant calling from the
E.164 phone number specified above and there is
no Associated video endpoint.
user.
Because there is no video stream for the user, you
can choose to display a still image in the pane
where the participant would normally appear.
The maximum size of the picture is 176 x 144
pixels and the maximum file size is 500k.
Click
to locate the image (jpg, gif, or
Windows bmp file). Then, click
upload the image to the MCU.
to
The bitmap will only display if the user calls in to
the MCU from the E.164 phone number using an
audio-only device and there is no associated video
endpoint.
106
Download from Www.Somanuals.com. All Manuals Search And Download.
You can make some changes to your user profile. To do this, go to
tips.
. Refer to the table below for
Your name, which identifies you to other users. Changing this field does not change your log-in
User ID.
You can enter a new password.
Verify the new password.
Associates an E.164 telephone number with your This limits the setup you will need to do each
user account.
time you join a video conference. When the
MCU receives a call from this number, it will be
recognized as coming from your phone. If the
device is an audio-only phone, you can set up an
associated video endpoint and/or upload a
picture file.
This field is not available for the system admin
account.
Associates a configured H.323 endpoint with your If you call in to the MCU from your E.164 phone
user account.
number using an audio-only device, the MCU
calls your associated video endpoint and sends the
conference video stream to that associated video
endpoint (and receives a video-only stream from
that endpoint).
This field is not available for the system admin
account.
You can upload an image which will display in the Click
conference when you join conferences in audio- click
mode only.
to locate the bitmap image. Then,
to upload the image to the MCU.
The bitmap will only display if you call in to the
MCU from your E.164 phone number using an
audio-only device and you do not have an
associated video endpoint.
107
Download from Www.Somanuals.com. All Manuals Search And Download.
You can modify the global conference settings for the MCU choosing by
. However, many of
these values can be overwritten by other MCU settings, for example individual conference, participant, or endpoint
settings.
In this section:
Advanced settings
Refer to this table for assistance configuring the conference settings. After making any configuration changes, click
.
Identifies the greatest video size that the MCU
will send and receive when connected to a video
endpoint.
Choose the unit-wide setting for
motion/sharpness trade off. The options are:
: the MCU will try and use
The settings for motion (frames per second) and
sharpness (frame size or resolution) are
negotiated between the endpoint and the MCU.
This setting controls how the MCU will negotiate
the settings to be used with an endpoint.
a high frame rate. That is, the MCU will
strongly favor a resolution of at least 25
frames per second
Note that the Motion/sharpness trade off setting for
an individual endpoint will override this unit-
wide setting for calls to/from that endpoint.
: the MCU will use the
highest resolution that is appropriate for
what is being viewed
: the MCU will select settings
that balance resolution and frame rate
(where the frame rate will not be less
than 12 frames per second)
Choose the unit-wide setting for transmitted
Retain the default setting (Allow all resolutions)
video resolutions. This setting can be overridden unless you are experiencing problems with the
by individual configured endpoint settings.
display of certain resolutions by endpoints.
Endpoints advertise the resolutions that they are
able to display. The MCU then chooses from
those advertised resolutions, the resolution that it
will use to transmit video. However, some
endpoints do not display widescreen resolutions
optimally. In these cases, you might want to use
this setting to restrict the resolutions available to
the MCU.
Note that you can configure this setting for
individual configured endpoints if you do not
need to restrict transmitted video resolutions for
all endpoints.
108
Download from Www.Somanuals.com. All Manuals Search And Download.
Identifies the network capacity (measured in bits When the MCU makes a call to an endpoint, the
per second) used by the media channels
established by the MCU to a single participant.
MCU chooses the maximum bandwidth that is
allowed to be used for the media channels which
comprise that call. This field sets that maximum
bandwidth, and is the total bandwidth of the
audio, video, and content channels combined.
This setting can be overridden by individual
endpoints' Preferred bandwidth from MCU values.
Sets the bandwidth that the MCU will advertise to This setting can be overridden by individual
the endpoint when it calls it. endpoints' Preferred bandwidth to MCU values.
connecting to conferences.
can cycle through the available families using the
Far End Camera Controls. See Understanding
When there are only two participants, each
If selected, when there are only two participants
participant will see the other in full-screen view. in a conference, this will apply regardless of
which layout was originally chosen for the
conference. If you do not select this setting, then
the default family view is used with unused panes
blank.
When in a conference, there is generally one
participant that the MCU recognizes as the active
speaker, notionally the person currently speaking
the loudest. This setting determines how the
MCU displays that participant in conference
views.
With this setting, no special action is
taken when displaying the active
speaker.
Displays a red border around the active
speaker.
Displays a green border around the
active speaker.
Determines whether the MCU is operating in
Reserved mode (Media port reservation
Unreserved mode (Media port reservation
).
See Port reservation modes for additional
) or information.
Allows various audible in-conference features to The options are:
be enabled or disabled.
: audible messages to
indicate when the conference's
scheduled end time is approaching.
: audible
messages indicating when other
109
Download from Www.Somanuals.com. All Manuals Search And Download.
participants join and leave the
conference.
: audible status
messages for example indicating to a
participant that he is the only participant
in a conference.
Allows various in-conference icons to be
displayed on participants' endpoints.
Depending on the check boxes that are selected,
in-conference icons appear:
: a crown icon
appears on all participants' endpoints in
the pane of the participant that has
become important.
: encrypted
participants in a conference where
encryption is optional see an icon
indicating that there are other
participants who are unencrypted:
This icon is also visible to participants of
an encrypted conference if there are
people streaming that conference.
: an arrow icon
appears on their endpoint when one
participant uses the far end camera
control to control another's camera.
: an icon appears on
their endpoint when a participant
changes their layout view.
: an icon (a red dot)
appears near the top left of the
conference display to indicate that the
conference is being recorded. For the
recording indicator to display, the
recording must be made by a Codian IP
VCR running software version 2.1 or
later, and the connection between the IP
VCR and the MCU must be using
H.323.
: an icon appears near
the top left of the conference display to
indicate if there are any audio-only
participants. To the right of the icon, the
number of such participants will be
displayed. If enabled, the icon will only
display if there are one or more audio
participants.
Audio-only participants are participants
that cannot be viewed; either the
participant's endpoint cannot send
video, the MCU has not allocated a
110
Download from Www.Somanuals.com. All Manuals Search And Download.
video port to the participant, or the
participant has muted their endpoint's
video channel to the MCU.
: an icon appears
in the top left of the conference display
to indicate if there are any streaming
participants in the conference. If
enabled, the icon will only display if
there are one or more streaming
participants. Streaming participants are
people who are viewing and listening to
the conference using a web browser.
: an icon (video camera
with a cross through it) appears when a
participant is experiencing high packet
loss or if the network link's bandwidth is
too low for the type of channel to the
MCU that the endpoint has established.
endpoints to see all in-conference icons and their
descriptions.
Allow various in-conference features to be
enabled or disabled.
Depending on the check boxes that are selected,
in-conference messages appear:
: messages appear
when the conference's scheduled end
time is approaching and when other
participants join and leave the
conference. Status messages can also be
played for example when you are the
only participant in a conference
: a message appears
when the conference's scheduled end
time is approaching
: messages
appear when other participants join and
leave the conference
: allows a message sent
using the web interface to be displayed
on participants' endpoints
: messages that
users can send one another via the
content channel are displayed on
participants' endpoints. Note that this
functionality is only available if the web
conferencing option (WCO) is activated
on your MCU.
111
Download from Www.Somanuals.com. All Manuals Search And Download.
This setting controls for how long (if at all) the
When displayed, the Codian logo appears in the
Codian logo is displayed to participants joining a bottom right of a participant's conference display.
conference. Choose from:
Allows you to enter a message that will be seen The duration of the message is configured using
by participants joining conferences on the MCU. the
The message is displayed at the bottom of a
participant's conference display.
control.
This setting controls for how long (if at all)
participants joining a conference will see the
conference welcome message. Choose from:
If you want streaming viewers to see the
welcome message, you must configure the
duration as permanent.
This setting controls whether (and for how long) The "Conference welcome message" (described
participants shown in view panes are accompanied above) and any other overlaid textual messages
by their supplied name.
(for instance information on how soon the
conference is going to end, or endpoints leaving
and joining the conference) will take priority over
the displaying of participant names for the
duration of those messages.
You typically only need to modify these advanced settings if you are working with a support engineer or setting up
more complicated configurations.
Restricts the MCU's choice of audio codecs to be When communicating with an endpoint, the
used for transmitting audio to endpoints.
MCU receives a list of supported audio codecs
from the endpoint. The MCU chooses an audio
codec from those available, and sends audio data
to the endpoint in that format.
Note that the Custom codec selection setting for an
individual endpoint will override this unit-wide
setting for calls to that endpoint.
112
Download from Www.Somanuals.com. All Manuals Search And Download.
Determines which audio codecs the MCU
advertises to remote endpoints, restricting the
Note that the Custom codec selection setting for an
individual endpoint will override this unit-wide
endpoints' choice of channels available for sending setting for calls from that endpoint.
audio data to the MCU.
Restricts the MCU's choice of video codecs to be When communicating with an endpoint, the
used for transmitting video to endpoints.
MCU receives a list of supported video codecs
from the endpoint. The MCU chooses a video
codec from those available, and sends video data
to the endpoint in that format.
Note that the Custom codec selection setting for an
individual endpoint will override this unit-wide
setting for calls to that endpoint.
Determines which video codecs the MCU
advertises to remote endpoints, restricting the
Note that the Custom codec selection setting for an
individual endpoint will override this unit-wide
endpoints' choice of channels available for sending setting for calls from that endpoint.
video data to the MCU.
When enabled, the MCU will upscale video
streams from participants who are sending low
The MCU uses intelligent resolution upscaling
technology to improve the clarity of low-
resolution video with the purpose of making best resolution video. Check this setting to enable it
use of the MCU's HD video capabilities. to do so.
Allows the MCU to vary the resolution and codec With this option enabled, the MCU can, for
of the video being sent to a remote endpoint
within the video channel established to that
endpoint. The options are:
instance, decide to send CIF video within a 4CIF
channel if this will increase the viewed video
quality.
The circumstances under which decreasing the
video resolution can improve the video quality
include:
: Do not allow video size to be
changed during transmission
: Allow video
size to be optimized during transmission
if the original size of the viewed video is
smaller than the outgoing channel
if the remote endpoint has used flow
control commands to reduce the
bandwidth of the MCU video
transmission
: Allow
video size to be optimized during
transmission and/or dynamic codec
selection
Typically, lowering the resolution means that the
MCU can transmit video at a higher frame-rate.
This setting can be used to influence the choice of You should leave this at Default unless your
outgoing video resolution made by the MCU in environment dictates 448p or w448p resolutions
certain circumstances.
only.
The MCU will use its normal internal
algorithms to dynamically decide which
resolution to send in order to maximize
the received video quality.
113
Download from Www.Somanuals.com. All Manuals Search And Download.
The MCU will heavily favor sending
448p or w448p video (resolutions of
576 x 448 and 768 x 448 pixels
respectively) to those endpoints that are
known to work best with these
resolutions.
Sets the format for video transmitted by the
MCU.
This option should be set to match your
endpoints' video configuration. If you set this
incorrectly, the smoothness of the video both to
and from the endpoints might suffer.
The MCU will transmit video at 30
frames per second (or a fraction of 30,
for example: 15fps)
NTSC is typically used in North America, while
PAL is typically used in the UK and Europe.
The MCU will transmit video at 25
frames per second (or a fraction of 25,
for example: 12.5fps)
Sets the maximum payload size (in bytes) of the Typically, you only need to set this value to
packets sent by the MCU for outgoing video
streams (from the MCU to connected video
endpoints).
lower than the default (1400 bytes) if there was a
known packet size restriction in the path between
the MCU and potential connected endpoints.
Video streams generally contain packets of
different lengths. This parameter only sets the
maximum size of a transmitted network datagram.
The MCU optimally splits the video stream into
packets of this size or smaller. Thus, most
transmitted packets will not reach this maximum
size.
Controls whether the MCU restricts video
resolutions in order to reduce the effect of
interlacing artifacts.
You should only enable this option if you are
seeing video interlacing artifacts or on the advice
of Codian technical support. Note that all
resolution restrictions imposed by this setting
apply only to video being sent from endpoints to
the MCU.
Enables the MCU to send bandwidth control
The MCU can send these messages to endpoints
messages to optimize the video bandwidth being requesting that the bandwidth of the video that
used.
they are sending be decreased or increased, up to
the maximum bandwidth of the channel.
If the participant is very prominent, then the
MCU will ask the endpoint to send video at a
high bandwidth. If the participant is not being
viewed at all (or only being viewed in very small
view panes), the MCU will request that the video
is sent at a lower rate to conserve network
bandwidth.
114
Download from Www.Somanuals.com. All Manuals Search And Download.
Enables the MCU to request that the endpoint
The MCU can send these messages to endpoints
send lower speed video if it fails to receive all the requesting that the bandwidth of the video that
packets which comprise the far end's video
stream.
they are sending be decreased based on the
quality of video received by the MCU.
If there is a bandwidth limitation in the path
between the endpoint and the MCU, it is better
for the MCU to receive every packet of a lower
rate stream than to miss some packets of a higher
rate stream.
Prevents the MCU from showing conference
participants their own video in small panes of
variable-sized pane views.
When using a conference view with some large
and some small panes, if this option is set, then
participants will never appear in any of the small
panes, even if there are free slots available. They
may still appear in larger panes, however, for
example if the view focus is manually changed to
show their video. See Understanding how
participants display in layout views for more
details.
Prevents the MCU from duplicating large-pane When using a conference view with some large
participants in small panes.
and some small panes, the MCU will typically
duplicate in a small pane the video of a
participant shown in a large pane. This is done to
minimize the switching of small panes in response
to changes of participant focus in the large pane.
If you would prefer not to duplicate participants
in small panes in this way, check this option. For
more details of view layouts, see Understanding
Any new content channel in a conference will be When this setting is enabled, any endpoint
treated as important and displayed prominently successfully contributing content content to a
to all participants who see the content channel in conference is immediately treated as important.
their conference layout.
This has the same affect as using the 'crown' icon
in the content channel row of a conference's
page.
An administrator can remove the importance
from the content channel at any time in the
conference.
This setting does not affect participants who view
the content channel independently from their
conference panes (for example, those viewing the
content channel on a separate video screen).
This setting will not affect those participants
using pane placement. Participants using pane
placement who have not allocated a pane to the
content channel, will not see the content channel
even if it is 'important'.
115
Download from Www.Somanuals.com. All Manuals Search And Download.
When pane placement is in use, this option affects For more details of view layouts, see
configured to show the conference's current
active speaker.
A pane set to show the loudest speaker
will never show a participant that is
specifically configured to be displayed in
another layout pane. If another layout
pane has been configured to show the
participant which is the current active
speaker, panes set to show the loudest
speaker will instead show the
conference's previous loudest speaker.
If you never want a pane that is set to
<loudest speaker> to duplicate a
participant shown in another layout
pane, choose this setting.
This is the default setting; panes
configured to show the loudest speaker
will be able to show participants that are
configured to be displayed in one or
more small panes for that layout, but not
those shown in big panes. This is most
appropriate when using layouts with
more than one big pane, in order to
make best use of the screen area.
Panes set to <loudest speaker> will always
show the current active speaker for a
conference, whether or not any other
layout panes have been specifically
configured to show that participant.
When pane placement is in use, this option
determines how often panes set to "rolling"
change which participant they are showing.
For more details of view layouts, see
Determines how easy it is for a participant to
A value of 0 means that it is very difficult for the
replace the active speaker for a conference based active speaker to be replaced; a value of 100
on how loudly they are speaking.
means the active speaker can be replaced very
easily.
When selected, audio will be delayed to be
transmitted at the same rate as video.
A setting used only to rectify some types of 'lip
sync' issues sometimes found with certain
endpoints. Leave at default setting, unless advised
to alter it by Codian technical support or a
reseller.
116
Download from Www.Somanuals.com. All Manuals Search And Download.
Select the delay to be applied to audio relative to A setting used only to rectify some types of 'lip
video.
sync' issues sometimes found with certain
endpoints. Leave at default setting, unless advised
to alter it by Codian technical support or a
reseller.
Controls whether connected endpoints are
This option acts as a unit-wide control over
allowed to use floor and chair control operations. whether any H.243 floor and chair control
operations are permitted. Individual conferences
may have their own floor and chair control
policies set; however, if this setting is Disabled
then no floor or chair control operations will be
possible within conferences. Changing this setting
will only affect new calls - existing calls will
continue with the setting in force when they
became active.
For more information, refer to H.243 floor and
Sets the default action when endpoints call into This option can make it easier for callers to create
the MCU using an unknown E.164 number; i.e. ad hoc conferences if Create new conference is
one the does not correspond to any configured
conference.
selected. If you do not wish callers to be able to
create conferences in this way, select one of the
other options.
The endpoint will enter the default auto
attendant from which they may join
existing conferences or potentially
create a new conference (see Using an
same as if the endpoint had called the
MCU using its IP address rather than an
E.164 number.
Endpoints are not allowed to call
unknown E.164 numbers, and the call
will be terminated.
A new conference will be created with
the E.164 number called as its numeric
identifier. The endpoint automatically
joins this new conference. This option is
reservation mode.
When enabled, if the MCU is calling out to an
Without this option selected, the caller ID is the
H.323 endpoint, the caller ID that the endpoint name of the MCU.
will see is the conference name.
Instructs the MCU to request conference
participants dialing into protected conferences
You may wish participants joining a conference
via a gatekeeper not to need to enter a PIN, even
using an E.164 number via an H.323 gatekeeper for protected conferences. If this is the case, do
to enter a PIN before they may join the not set this option. If you wish conferences to be
117
Download from Www.Somanuals.com. All Manuals Search And Download.
conference.
protected, regardless of how participants
connect, ensure you set this option.
When this option is set, participants calling into a
protected conference will be presented with PIN-
entry screen instead of the normal conference
view. The option has no effect for conferences
with no PIN set.
If this option is checked, ad hoc conferences
It may be useful to register ad hoc conferences
created using either an auto attendant or via calls individually with the gatekeeper to facilitate load-
to an E.164 number associated with the MCU
service prefix will be registered individually with
the configured gatekeeper.
balancing between multiple MCU devices which
have registered the same prefix.
If the MCU is operating in Port reservation
mode, this option will be present but will be
ignored as ad hoc conferences are not allowed in
port reservation mode.
If this option is checked, ad hoc conferences
You will need to pre-configure numeric IDs for
created using an auto attendant will be registered ad hoc conferences on the SIP registrar, or
individually with the configured SIP registrar.
configure the SIP registrar such that it will
recognize unknown numbers.
The numeric ID used for the conference will be
registered as the SIP registrar ID (displayed on
the Conference statistics page).
If the MCU is operating in Port reservation
mode, this option will be present but will be
ignored as ad hoc conferences are not allowed in
port reservation mode..
The timeout setting for a participant entering a
PIN for an ad hoc conference that they are
currently creating:
This global setting may be useful where
participants creating ad hoc conferences rarely
need to configure a PIN.
Participants will never be prompted to
enter a PIN when creating an ad hoc
conference.
Participants will be prompted for a PIN
when creating an ad hoc conference. If
the participant does not enter a PIN
during the configured time period, the
conference will be created without a
PIN.
Participants will be prompted for a PIN
when creating an ad hoc conference.
They must either enter a PIN to create
an ad hoc conference with a PIN or press
the hash/pound key (#) to create the
conference without a PIN.
118
Download from Www.Somanuals.com. All Manuals Search And Download.
To configure gatekeeper settings, go to
.
You can configure the MCU to use a gatekeeper, which can make it easier for end-users to join conferences using
directory numbers rather than requiring them to know the IP address or host name of the MCU. The MCU can
register up to 100 IDs with the gatekeeper; these IDs comprise conferences' Numeric IDs, the MCU service prefix, and
the H.323 ID. If you need to register more than 100 IDs, use a prefix for MCU registrations to route calls to the MCU,
rather than registering individual conferences with the gatekeeper. The use of prefixes is described further in the table
below.
In this section:
Gatekeeper settings
Gatekeeper status
Refer to this table for assistance configuring the gatekeeper settings. After making any configuration changes, click
.
Enables the MCU to use an H.323 gatekeeper for When set to Disabled then no gatekeeper
registration of numeric identifiers for its
conferences and/or auto attendants.
registrations are attempted (and existing
registrations are torn down), regardless of other
gatekeeper or per-conference settings.
When set to Enabled registrations with the
gatekeeper are attempted, and the gatekeeper is
contacted for incoming and outgoing calls. If the
gatekeeper does not respond, calls are still
connected if possible. When set to Required
registrations with the gatekeeper are attempted
but calls are not connected if the gatekeeper
cannot be contacted.
Identifies the network address of the gatekeeper This can be specified either as a host name or as
to which MCU registrations should be made.
an IP address.
This field will have no effect if H.323 Gatekeeper
usage (see above) is set to Disabled.
The gatekeeper can be either the built-in
gatekeeper enabled on the
page (see
gatekeeper enter "127.0.0.1". For an external
gatekeeper, enter its host name or IP address.
Controls how the MCU identifies itself when
registering with its configured gatekeeper.
Codian recommends that you use the Terminal /
gateway option unless you are using a service
prefix (in this case, use Gateway). Only use a
different option if you are:
119
Download from Www.Somanuals.com. All Manuals Search And Download.
having specific problems
using the Cisco Gatekeeper (with or
without a service prefix), in which case
use Gateway (Cisco GK compatible)
using the VCON MXM Gatekeeper
(with or without a service prefix), in
which case use MCU (compatible)
Refer to the list of Frequently Asked Questions
(FAQ) in the Support section of the web site for
more details about interoperability with
gatekeepers.
Whether a call involves consultation with the
configured gatekeeper also depends on the Port A
and Port B settings. For all incoming calls, and
outgoing calls dialed by address rather than by
E.164 phone number, the gatekeeper will be used
to validate the connection only if the network
port over which the connection is made is
selected here.
Specifies an identifier that the MCU can use to
register itself with the H.323 gatekeeper.
Before the MCU can register any IDs with the
H.323 gatekeeper, it must make a unit-wide
registration.
This field is required for the gatekeeper
registration.
This will have no effect if H.323 gatekeeper usage is
disabled.
If the configured gatekeeper required password Note that where password authentication is used,
authentication from registrants, check the Use
password box and type the password.
the (Mandatory) H.323 ID to register will be used as
the username.
Specifies an optional group of digits that are
Conferences and auto attendants registered with a
added to the beginning of each conference or auto gatekeeper have a Numeric identifier. The numeric
attendant's numeric identifier before registering it identifier is a unique sequence of digits entered
with the H.323 gatekeeper.
from a video-conferencing endpoint to connect
directly to the conference or auto attendant. This
eliminates the need for users to navigate
additional menus or to know the IP address of the
MCU.
To usefully partition the dialing space, you might
need to ensure that all registrations from a single
MCU start with the same sequence of digits.
Using registration prefixes also can benefit large-
scale dial plan changes. For example, you can
change all MCU registrations to begin with "121"
instead of "11" by changing a single MCU
configuration field rather than individually
amending every conference or auto attendant's
120
Download from Www.Somanuals.com. All Manuals Search And Download.
associated numeric identifier.
If H.323 gatekeeper usage is disabled, this field will
have no effect.
Note that if you are also intending to use the
MCU service prefix (see below), Codian
recommends that you set both prefixes to the
same number.
If required, specify a group of digits which the
This field is optional. If set, users dialing any
H.323 gatekeeper may use to identify calls to be number beginning with this prefix will have their
routed to the MCU.
call directed to the MCU. This might be useful if
you wish to create conferences in response to
unknown E.164 numbers.
Any numbers following the prefix will be
identified by the MCU as a conference or auto
attendant number. For example, if a conference
has Numeric ID "3333" and you have set the
service prefix to be "121", then a user dialing
"1213333" will be connected to that conference.
This field will have no effect if H.323 gatekeeper
usage is disabled.
Note that if you are also intending to use the
Prefix for MCU registrations (see above), Codian
recommends that you set both prefixes to the
same number.
If the MCU is unable to match a call to a
conference or auto attendant, the action for
Incoming calls to unknown E.164 number will be
applied. This is a setting on the
page (see Configuring global
Create new ad hoc conference.
This field controls whether any scheduled
This would normally be Enabled - by setting it to
conferences' configured numeric IDs are allowed Disabled, an administrator can prevent users from
to be registered with the gatekeeper.
adding to the set of IDs registered with the
configured gatekeeper, even if those users enable
the gatekeeper Numeric ID registration setting for
conferences they control. This may be desired
when working with certain types of H.323
gatekeeper whose behavior in some modes is to
disconnect active calls when the set of registered
IDs changes.
This setting only affects registration of numeric
IDs configured for scheduled conferences -
registration of ad hoc conferences' IDs with the
gatekeeper is controlled by the Register ad hoc
conferences with gatekeeper setting on the
121
Download from Www.Somanuals.com. All Manuals Search And Download.
page (see Configuring global
This field will have no effect if H.323 Gatekeeper
usage is set to Disabled.
Select this option if you want the MCU to inform The ability of the MCU to send resource
the gatekeeper about its availability or non-
availability messages is useful in a network where
availability. This information will be used by the there are multiple MCUs or where there are
gatekeeper when it is selecting where to place ad several media blades in an MSE.
hoc conferences.
In an environment with multiple conferencing
devices registered with the same gatekeeper, that
Only use this option where multiple MCUs are
gatekeeper should favor devices in the available
registered with the same MCU service prefix on
the same gatekeeper.
state when choosing where to place new calls.
For example, when one MCU sends the
gatekeeper a message indicating that it is not
If you select this option, you must configure the
available, the gatekeeper will then attempt to use
thresholds for conferences and/or video ports.
a different MCU for new ad hoc conferences.
Thresholds:
Resource availability indications are most useful
where the thresholds are configured such that the
MCU informs the gatekeeper that it is unavailable
when its resources are nearly used up.
: Enter any number of
conferences between 0 and 200. (A
value of 0 will mean that the MCU will
always indicate 'unavailable'.)
Conferences without any active participants do
not contribute to the conference count; any video
port in use is added to the video port count.
: Enter a number between 0
and the number of video ports on your
MCU; for example, on an MCU 4205,
there are 12 video ports, so enter a
number between 0 and 12. (A value of 0
will mean that the MCU will always
indicate 'unavailable'.)
When either threshold is equaled or exceeded,
the MCU sends a message to indicate that it is not
available; when the resource usage drops such
that neither threshold is equaled or exceeded, the
MCU sends a message indicating that it is
available.
You might choose to only configure one of the
thresholds. You are probably aware of how your
video conferencing resources tend to be used by
participants and you need to consider this when
configuring the thresholds. For example, you
could have four people who have each started an
ad hoc conference; you might know that it is
usual for such conferences to end up having ten
participants. In this case, on a 40-port MCU you
could set the conference threshold to 4 to
indicate that it will be out-of-resources very
soon. On the same MCU if you set the video port
threshold to 35 and left the conference threshold
empty, another four or more people could begin
ad hoc conferences on this MCU before the
participants expected in the original four
conferences had dialed in.
122
Download from Www.Somanuals.com. All Manuals Search And Download.
The MCU also displays brief status information about its registrations with the configured gatekeeper.
To display a complete list of all IDs that the MCU is attempting to register with the configured H.323 gatekeeper,
click the
link in the Number of active registrations row of the gatekeeper status table; this takes you to the Active
registrations page.
Displays the IP address of the gatekeeper
currently being used by the MCU.
This information might be useful if the gatekeeper
has been specified with a host name rather than
with an IP address.
If the MCU has been unable to reach the
configured gatekeeper and has instead registered
with an alternate gatekeeper, the status displayed
here will be "registered with alternate gatekeeper
<IP address>".
Displays the local IP address and port number that This information might be useful if the MCU has
the MCU has registered with the gatekeeper.
more than one IP address, for instance if both
Ethernet interfaces are in use.
Displays the number of 'alternate' gatekeepers
Where the configured gatekeeper has told the
configured on the H.323 gatekeeper. This figure MCU about any configured 'alternate'
comes from the gatekeeper itself; if there are any gatekeepers and if the MCU loses contact with
'alternate' gatekeepers configured, the gatekeeper the configured gatekeeper, the MCU will attempt
tells the MCU their IP addresses.
to register with each of the 'alternates' in turn. If
none of the 'alternate' gatekeepers responds, the
MCU will report that the registration has failed.
If the MCU successfully registers with an
'alternate' gatekeeper:
the H.323 gatekeeper status will indicate
that registration is with an 'alternate'
the list of 'alternates' received from the
new gatekeeper will replace the
previous list
the MCU will only revert back to the
original gatekeeper if the 'alternate' fails
and only if the original gatekeeper is
configured as an 'alternate' on the
current gatekeeper's list of 'alternates'
Note that if the MCU registers with an 'alternate'
that does not itself supply a list of 'alternates', the
MCU will retain the original list and if it loses
contact with the current gatekeeper, each one
will be attempted from the top again as before.
123
Download from Www.Somanuals.com. All Manuals Search And Download.
Displays whether the gatekeeper is configured to The possible statuses are:
send resource availability indications and if it is, it
displays the current state of the resource
availability status of the MCU.
Displays the number of E.164 numbers plus
H.323 IDs plus prefixes that the MCU has
registered with the gatekeeper.
It also shows how many registrations are in
progress but are not fully registered yet.
Full information on the gatekeeper registrations
being made by the MCU can be seen by clicking
on
; this takes you to the Active
registrations page.
Displays the identifier that the MCU has used to For more information about the H.323 ID, refer
register itself with the H.323 gatekeeper.
to the table above.
Displays the identifier that the gatekeeper has
registered for calls to be routed to the MCU.
For more information about this prefix, refer to
the table above.
124
Download from Www.Somanuals.com. All Manuals Search And Download.
To display a complete list of all IDs that the MCU is attempting to register with the configured H.323 gatekeeper, go
to
to the
and click
, shown next to the Number of active registrations status entry. You are taken
page. This page shows the complete set of IDs that the MCU is attempting to register with
the configured H.323 gatekeeper, and includes the H.323 ID, prefixes, and specific E.164 number registrations for
active conferences and configured auto attendants.
You can configure filters so that only specific registrations are shown in the list. This may help you to find a
registration whose number or name you know if the list is very long.
The filtered registration list is automatically updated when you change the ID and name filters; to stop filtering the
list either delete the filters or click
. If both the ID filter and the name filter are defined, the registration
list will show only those entries which match both filters.
Type the ID, or a part of the ID for which you
want to see details.
The filtered registration list is automatically
updated when you change the ID and name
filters.
Type the text, or a part of the text that will
appear in the "Details" column of the
Registrations table. For example, type
'Conference' to filter the registrations to show all
conferences that the MCU is attempting to
register with the gatekeeper.
Applying a filter will filter all registrations and
display any that match, even if those registrations
are not on the page currently displayed.
The registration list shows, for each registered ID, the type of that ID (H.323 ID, prefix or E.164 number), the
object it relates to, and the status of that registration. If you want to modify or remove a specific registered ID, click
on the link in its Details column to be taken to the relevant configuration page.
125
Download from Www.Somanuals.com. All Manuals Search And Download.
To configure SIP settings on the MCU, go to
.
To allow conference participants with SIP endpoints to connect to the MCU by dialing a directory number rather
than an IP address, you must configure a SIP registrar. The settings on this page control the MCU's interaction with
the SIP registrar and with SIP endpoints.
A SIP call will select the audio and video codecs to use from the set of those both allowed on the
page and supported by SIP, unless the call is with an endpoint configured with a Custom codec (refer to
Configuring SIP endpoints for more information).
Refer to this table for assistance configuring the SIP settings. After making any configuration changes, click
.
Specifies the level of SIP registration for the
MCU.
Can be set to:
No registration: The MCU will not
register with the SIP registrar. This
means that a user with a SIP endpoint
can only connect to the MCU by dialing
its IP address or hostname
Register MCU only: Enables conference
participants to dial in to the auto
attendant of the MCU
Allow conference registration: Enables
conference participants to dial directly in
to conferences. For this to work, you
must configure the SIP registrar with
conference IDs
Identifies the network address of the SIP registrar This can be specified either as a host name or as
to which MCU registrations should be made.
an IP address. This field will have no effect if
is set to No registration.
Choose between:
Your choice is dependent on the type of SIP
registrar you are using.
Standard SIP: for non-Microsoft SIP
registrars
Microsoft OCS/LCS: for Microsoft SIP
registrars
If you are using Microsoft OCS or LCS, you will
also need to configure the OCS or LCS to
recognize the IP address of the MCU and treat it
as authenticated.
This field will have no effect if
is set to No registration.
Select this option to force the MCU to present its Often, the SIP registrar will not require the local
local certificate when registering with the SIP
registrar.
certificate from the MCU. Only select this option
if your environment dictates that the SIP registrar
must receive the local certificate.
The login name for the MCU on the SIP registrar. You need to configure the SIP registrar with
details of the devices that will register with it and
create a login for each device.
126
Download from Www.Somanuals.com. All Manuals Search And Download.
If you are using Microsoft OCS or LCS, you need
to enter the full URI (for example,
MCU@mylcs.com).
Note that this username will be used anywhere
where one is required in a SIP call; for example,
it will be used where authentication is required
with a SIP server where no registrar is used.
The password for the MCU on the SIP registrar. You need to configure the SIP registrar with
details of the devices that will register with it and
create a login for each device. The password
configured on this page needs to match the
password in the SIP registrar. For Microsoft OCS
or LCS, do not enter a password.
Note that this username will be used anywhere
where one is required in a SIP call; for example,
it will be used where authentication is required
with a SIP server where no registrar is used.
Identifies the network address of the SIP proxy. If set, the proxy is used for all SIP calls, whether
through a registrar or not.
Select a maximum bit rate to use from Microsoft Microsoft OCS/LCS clients will try to use the
OCS/LCS clients.
maximum bit rate that the MCU advertises
during the initial call setup. In most scenarios,
you will not want OCS/LCS clients to use the
Default bandwidth from MCU that is configured on
the
select an appropriate bit rate for Microsoft
OCS/LCS clients.
<limit disabled> will cause the MCU to advertise
the Default bandwidth from MCU.
Identifies the protocol to be used for call control If your SIP devices use TCP, select TCP as the
messages for outgoing call connections.
outgoing transport. If your SIP devices use UDP,
select UDP as the outgoing transport. If you want
to use encrypted SIP, select TLS. Note that if you
want to use TLS, you must have the encryption
feature key (or the Secure management feature
key) and the TLS service must be enabled on the
page.
Note that this unit-wide setting can be overriden
on a per-configured endpoint basis if you require
different settings for individual endpoints. For
more information about configuring SIP
endpoints, refer to Configuring SIP endpoints
Using TLS for call setup is not sufficient for the
call to be considered encrypted such that it can
participate in a conference which requires
127
Download from Www.Somanuals.com. All Manuals Search And Download.
encryption. Where encryption is required in the
conference configuration, a SIP call must use
SRTP. For more information about SIP
settings.
The MCU can accept connections on TCP, UDP,
and TLS providing those services are enabled on
the
128
Download from Www.Somanuals.com. All Manuals Search And Download.
You can configure two streaming options that will be available for users to choose between when streaming
conferences. For each streaming option, you must choose a media player and a bit rate.
You can configure the MCU to support either (or both of) unicast or multicast streaming. Unicast streaming involves
a direct connection between the MCU and the individual user. Multicast streaming involves transmitting a single copy
of the video or audio stream to multiple recipients. When choosing to support multicast streaming, ensure that your
network has been properly configured to avoid network flooding.
To access streaming settings, choose
.
Controls the ability of the MCU to stream
conferences.
If this setting is Enabled, you can configure
streaming on a per-conference basis from
individual conferences' configuration pages. For
more information about configuring an individual
conference, refer to Adding and updating
If this setting is Disabled, it will not be possible to
stream any conferences.
Permits or prohibits streaming of conferences that Changing this setting will have no effect on
are generated either through the "Create new currently active ad hoc conferences; however,
conference" option in video auto attendants, or when an ad hoc conference is running, whether
calling the MCU with an unknown E.164
number.
or not streaming is allowed for that conference
can be configured (go to
conference you require and select the
tab).
, select the
reservation is enabled - if the MCU is operating in
port reservation mode then this streaming option
will not be shown.
The MCU is configured with two streaming rates, The name is optional - if not specified, the
each comprising audio and video encoding
formats (codecs) and overall (i.e. combined)
media bit rate. The names you enter are the
choices offered to users when streaming.
choices offered to users will simply show the
details of the audio and video codecs, together
with the overall media bit rate.
This is intended to make the choice easier for
potentially non-technical users; for instance, one
rate could be named "low bit rate" and the other
"high bit rate".
Choose from the available media players.
It is not possible to use Windows Media Player to
stream conferences in multicast mode.
129
Download from Www.Somanuals.com. All Manuals Search And Download.
Sets the audio and video combination to use, and Typically, when two streaming rates are used,
the overall media bit rate.
one is set up as a low bit rate combination and the
other configured to use a higher bit rate. This
enables those users with a low bandwidth
connection to achieve useful streaming while at
the same time allowing those with a high
bandwidth link to take advantage of enhanced
video.
The available options vary depending on which
media player you have chosen.
Choose whether to use the specified streaming
rate for multicast.
Setting any Multicast parameters to "Enabled" will
only be useful if the multicast media IP addresses
and port numbers are also configured - see
below.
If this is set to Enabled then for any conference
with Streaming set to "Multicast" or "Unicast and
multicast", multicast audio and video streams will It is not possible to use Windows Media Player to
be transmitted according to the corresponding
stream conferences in multicast mode.
Streams setting.
Identifies the range of IP addresses to which
multicast streaming media should be sent.
If this address range is not configured, the MCU
cannot transmit multicast conference media.
Sets the range of port numbers to which the
media will be sent.
This UDP port number range is used in
conjunction with the Media transmit IP address.
You must set both the start and end port numbers
to transmit multicast conference media.
Identifies the protocol used by Windows Media MMS over UDP is a low latency/ high
Player to stream data. Note that v11 only throughput protocol, while MMS over TCP
supports HTTP; it no longer supports MMS over includes extra reliability, though extra processing
UDP or MMS over TCP.
power is required. Both use the streaming port,
so if a restrictive firewall is present HTTP may be
necessary.
Auto negotiation attempts to open the most
efficient connection, switching protocols if unable
to do so, but on some systems this is not efficient.
Codian recommends that you select to use
UDP/TCP/HTTP rather than auto-negotiation.
130
Download from Www.Somanuals.com. All Manuals Search And Download.
The content settings affect the behavior of the MCU with regard to H.239 and BFCP (Binary Floor Control
Protocol).
H.239 is the protocol that allows for an additional video channel (known as the content channel) alongside the main
video channel in a video-conferencing call that uses H.323; BFCP is a protocol that allows for an additional video
channel (known as the content channel) alongside the main video channel in a video-conferencing call that uses SIP.
For example, a conference participant may want to contribute a slide presentation from a laptop within a video
conference.
Note that BFCP uses the TCP port (5070); if you want to use BFCP, you must enable that service on the
To access these settings, choose
.
Refer to this table for assistance configuring the content settings. After making any configuration changes, click
.
Controls whether the MCU as a whole is
permitted to use content.
If this setting is Enabled, you can still enable or
disable the use of content on a per-conference
basis. For more information about configuring
updating conferences.
If this setting is Disabled, no conference will be
able to use content.
If this setting is H.239 only, no conference will be
able to use BFCP content.
Certain video conferencing endpoints and
infrastructure such as gatekeepers may not
operate correctly when communicating with
equipment (such as the Codian MCU) which
declares H.239 capability. It may therefore be
necessary to set this to Disabled in order to work
with legacy devices (this will, of course, also
prevent content video streams being used with
any H.239- or BFCP-aware equipment).
If this setting is Enabled, content channel video
will be permitted in ad hoc conferences as well as
scheduled conferences.
Ad hoc conferences are those created using either
the
option within an auto
attendant or via calls to an E.164 number
associated with the configured MCU service prefix.
131
Download from Www.Somanuals.com. All Manuals Search And Download.
This field sets which video codec is used for
conferences' content video streams.
A single content video stream is used for each
conference, and this stream will be sent to all
viewing endpoints. If an endpoint is unable to
receive content video using the codec configured
here, no content channel will be opened to that
endpoint.
This field sets a lower limit on the bandwidth of A single content video stream is used for each
the shared content video encoding sent to content conference, and this stream will be sent to all
receivers in a conference.
endpoints receiving the content channel as a
separate video channel. If some endpoints are
only able to receive low bit rate streams (for
instance if they have called into the MCU at a low
call rate), it is sometimes preferable to exclude
those endpoints completely from the content
stream rather than force all viewers to see a
reduced bit rate channel.
Changing this setting when there are connected
participants causes the MCU to re-assess whether
there should be content video channels to those
endpoints; the MCU will close existing channels
and open new ones as appropriate.
If you do not wish to exclude endpoints from
viewing the shared content video channel in a
conference, make sure this is set to <no
minimum>, which is the default setting.
Where an endpoint cannot, for whatever reason,
receive the content channel as an additional video
channel, the MCU can show the content channel
as part of the main video channel. That is, the
participant will see the content as a pane in the
conference layout. This functionality is controlled
by the Display content in normal video channel
setting (see below).
Note that during a call, an endpoint can send a
'flow control message' to the MCU that could
cause the MCU to reduce the bit rate to that
endpoint to below the configured Minimum content
channel bit rate; in this case, the MCU will close
the content channel to that participant. To re-
enable content (which has been disabled in this
way) to this participant, go to the conference's
Participant list and use the content enable
control. For more information about altering a
participant's settings during a conference, refer to
Sets whether the MCU will render content
If there is an active content channel for a
channel data in endpoints' main video channels. conference, it may be that the MCU is unable to
open a content channel to a particular endpoint.
For instance, that endpoint may have no content
capability, or might not support the video format
specified by the Outgoing content video codec setting
132
Download from Www.Somanuals.com. All Manuals Search And Download.
(see above).
In these cases, if this option is set to Enabled, the
MCU will display the content channel video
within a pane of the currently selected conference
layout. In these cases, you might also want to
enable the Automatically make content channel
important option in the
page which will make the content channel
important at the same time.
If this option is Enabled, the MCU will ignore fast When this mode is active, it can prevent a large
update requests for a conference's content video number of keyframes being sent in the shared
channel received from endpoints whose
connections are experiencing problems.
content video encoding in response to fast update
requests from a single endpoint. A high number
of keyframes may reduce the video quality of the
content channel for all conference participants,
including those with good connections to the
MCU.
Sets the bandwidth of the content channel video Just as there is a single content video stream sent
stream sent to streaming viewers.
to all content-capable videoconferencing
endpoints in a conference, there is a single
content channel video stream sent to all
streaming viewers.
This option is only available if the MCU web
conferencing (WCO) feature key is present.
This option allows the bandwidth of the streamed
content channel video to be set. While in general
a higher value means a greater frame rate (and
thus better video quality), it is important to not
set this value too high (i.e. higher than the
available TCP network bandwidth between the
MCU and viewers' machines) to avoid
degradation resulting from lost data.
If Enabled, people viewing the content channel
stream via a web browser will be able to add
markup to that video stream such as graphics and
text. This markup will then be visible to all
content channel viewers, both those viewing via
streaming and those connected via
Changing this setting has an immediate effect:
if changed to Disabled, it will not be
possible for existing viewers to complete
markup currently in progress
if changed to Enabled, existing streaming
viewers will gain the ability to add
markup
videoconferencing endpoints.
This option is only available if the MCU web
conferencing (WCO) feature key is present.
133
Download from Www.Somanuals.com. All Manuals Search And Download.
You can configure the MCU to encrypt connections to and from H.323 and SIP endpoints.
The encryption technology that the MCU uses for encryption to and from H.323 endpoints is Advanced Encryption
Standard (AES).
The encryption technology that the MCU uses for encryption to and from SIP endpoints is Secure Real-time
Transport Protocol (SRTP).
To use encryption, you must have the Encryption feature key present on the MCU. For information about installing
feature keys, refer to Upgrading the firmware. To access encryption settings, go to
.
Encryption is used where both devices in a call agree to use encryption; by default if one of the devices cannot use
encryption (for example if SIP endpoint does not support SRTP), the MCU will allow the call to be unencrypted,
unless the conference configuration dictates that encryption is Required. Where encryption is required, calls that
cannot used encryption will not be allowed.
When encryption is in use to and from H.323 endpoints, the MCU will encrypt audio, video, and content media. It
does not encrypt control or authentication information.
When encryption is in use to and from SIP endpoints, the MCU will encrypt audio and video media using SRTP.
Control or authentication information can also be encrypted using TLS. For more information refer to Using
encryption with SIP, below.
You can:
configure the MCU to advertise its ability to encrypt connections, such that it will use encryption if an
H.323 endpoint can use AES encryption
configure the MCU to advertise its ability to encrypt connections, such that it will use encryption if a SIP
endpoint can use SRTP encryption
configure the MCU so that the default encryption option for new conferences is either
or
. Be aware that anyone creating a new conference will be able to set the encryption setting for the
conference to either
or
force new ad hoc conferences to use encryption
Note that using encryption does not affect the number of ports that are available on the MCU.
Note that the MCU will not show thumbnail previews on the Conference participant page if encryption is required
for a conference. If you have the Show thumbnail images option selected on the
page,
thumbnail previews will be shown for conferences where encryption is optional and there are encrypted participants.
Refer to this table for assistance configuring the encryption settings. After making any configuration changes, click
.
134
Download from Www.Somanuals.com. All Manuals Search And Download.
Whether the MCU is able to use encryption or
not.
When encryption status is Enabled, the MCU
advertises itself as being able to use encryption
and will use encryption if required to do so by an
endpoint. If this setting is Enabled, you can enable
or disable the use of encryption on a per-
conference basis.
If this setting is Disabled, no conference will be
able to use encryption.
The default encryption setting for new scheduled When you (or another user) create a new
conferences (on the
page).
>
conference (by choosing
and clicking
), you can set the encryption
setting for the conference to be either Allowed or
Required. This control defines which option is
selected by default. However, when creating a
conference this can be changed.
When enabled, this setting forces encryption to Changing this setting will have no effect on
be used for new ad hoc conferences.
currently active ad hoc conferences; however,
when an ad hoc conference is running, whether
or not encryption is required for that conference
can be configured (go to
conference you require and select the
tab).
, select the
Select the setting for media encryption for SIP
calls:
For more information refer to Using encryption
with SIP, below.
When disabled, the MCU will not advertise that
it is able to encrypt using SRTP. It is only
necessary to disable SRTP if it is causing
problems.
All transports: If encryption is used for a
call, the media will be encrypted using
SRTP regardless of transport mechanism
used for call control messages.
Secure transports (TLS) only: If encryption
is used for a call, the media will only be
encrypted in calls that are set up using
TLS.
Disabled: SRTP will not be used for any
calls. The MCU will not encrypt media
for SIP calls.
135
Download from Www.Somanuals.com. All Manuals Search And Download.
The MCU supports the use of encryption with SIP. When encryption is in use with SIP, the audio and video media
are encrypted using Secure Real-time Transport Protocol (SRTP). When using SRTP, the default mechanism for
exchanging keys is Session Description Protocol Security Description (SDES). SDES exchanges keys in clear text, so it
is a good idea to use SRTP in conjunction with a secure transport for call control messages. You can configure the
MCU to also use Transport Layer Security (TLS) which is a secure transport mechanism that can be used for SIP call
control messages.
Using TLS for call setup is not sufficient for the call to be considered encrypted such that it can participate in a
conference which requires encryption. Where encryption is required in the conference configuration, a SIP call must
use SRTP.
To configure the MCU to use SRTP to encrypt media in calls that are set up using TLS:
1. You must have the encryption feature key installed on your MCU.
2. Go to
and set:
Encryption status to Enabled.
o
o
o
Default setting for new scheduled conferences to Required.
SRTP encryption to Secure transports (TLS) only.
and set Outgoing transport to TLS.
3. Go to
Note that to allow the MCU to accept incoming calls that use TLS, go to
and ensure that Incoming
Encrypted SIP (TLS) is selected.
136
Download from Www.Somanuals.com. All Manuals Search And Download.
To configure the network settings on the MCU and check the network status, go to
.
or
The MCU has two Ethernet interfaces, Port A and Port B. The configuration pages for the two interfaces look and
behave similarly, and so are described together. Differences will be noted as appropriate.
Port A can be configured to be allocated its IP address by DHCP. Port B cannot use DHCP. Connect Port A to your
local network and connect Port B to a second subnet or the internet depending on your application of the MCU.
In this section:
Ethernet status
These settings determine the IP configuration for the appropriate Ethernet port of the MCU. When you have
finished, click
and then reboot the MCU.
Whether the port is enabled or disabled. When Port A can never be disabled because it is the
enabled, the port will allow IP traffic to flow;
when disabled, IP traffic will not pass into or out
of the MCU on this port.
primary interface of the MCU.
Specifies a name for the MCU.
Depending on your network configuration, you
may be able to use this host name to
communicate with the MCU, without needing to
know its IP address.
Specifies whether the MCU obtains its own IP
address for this port automatically via DHCP
(Dynamic Host Configuration Protocol), or
whether or if it should use the values that you
specify in the Manual configuration fields below.
Click
to request a new IP address if
you have selected automatic configuration.
Identifies the dot-separated IPv4 address for this You only need to specify this option if you have
port, for example 192.168.4.45.
chosen Manual IP configuration, as described
above.
For Port A, if the IP configuration setting is set to
Automatic by DHCP this setting will be ignored
Identifies the subnet mask required for the IP
address you wish to use, for example
255.255.255.0.
Identifies the IP address of the default gateway on
this subnet, for example 192.168.4.1.
137
Download from Www.Somanuals.com. All Manuals Search And Download.
Identifies the IP address of the name server.
Identifies an optional second name server.
The secondary DNS server is only used if the first
is unavailable. If the first returns that it does not
know an address, the secondary DNS server will
not be queried.
Specifies an optional suffix to add when
performing DNS lookups.
This can allow you to use non-fully qualified host
names when referring to a device by host name
instead of IP address.
For example, if the domain name is set to
codian.com, then a request to the name server to
look up the IP address of host endpoint will
actually lookup endpoint.codian.com.
Use the IP Status fields to verify the current IP settings for the appropriate Ethernet port of the MCU, which were
Host name
DHCP
IP address
Subnet mask
Default gateway
Name server (DNS)
Secondary name server (DNS)
Domain name (DNS suffix)
These settings determine the Ethernet settings for the appropriate port of the MCU. Refer to the table for assistance
with these settings. When you have finished, you must press
effect.
to make the changes take
Specify whether you want this Ethernet port to
It is important that your Ethernet settings match
automatically negotiate its Ethernet settings with those of the device to which this port is
the device it is connected to, or if it should use
the values that you specify in the Manual
configuration fields below.
connected. For example, both devices must be
configured to use automatic negotiation, or both
configured with fixed and matching speed and
duplex settings (see below).
Identifies the connection speed: 10 Mbit/s or 100 The connection speed must match that of the
Mbit/s. Use automatic negotiation if a connection device to which this port is connected.
speed of 1000 Mbit/s is required.
You only need to select this option if you have
chosen manual Ethernet settings, as described
above.
138
Download from Www.Somanuals.com. All Manuals Search And Download.
Identifies the connection duplex mode:
The duplex setting must match that of the device
to which this port is connected.
Both devices can send data to each other
at the same time
You only need to select this option if you have
chosen manual Ethernet settings, as described
above.
Only one device can send to the other at
a time
Indicates whether this Ethernet port is connected
to or disconnected from the network.
Shows the speed (10/100/1000 Mbit/s) of the
network connection to the MCU on this port.
This value is negotiated with the device to which
this port is connected or based on your manual
configuration, depending on the settings you
chose above.
Shows the duplex mode (full/half duplex) of the This value is negotiated with the device to which
network connection to this port.
this port is connected or based on your manual
configuration, depending on the settings you
chose above.
Shows the fixed hardware MAC (Media Access
Control) address of this port.
This value cannot be changed and is for
information only.
Displays a count of the total number of packets
When troubleshooting connectivity issues, this
sent from this port by the MCU. This includes all information can help you confirm that the unit is
TCP and UDP traffic.
transmitting packets into the network.
Displays a count of the total number of packets
When troubleshooting connectivity issues, this
received by this port of the MCU. This includes information can help you confirm that the unit is
all TCP and UDP traffic. receiving packets from the network.
These fields display further statistics for this port. Use these fields for advanced network
diagnostics, such as resolution of problems with
Ethernet link speed and duplex negotiation.
Multicast packets sent
Multicast packets received
Total bytes sent
Total bytes received
Receive queue drops
Collisions
Transmit errors
Receive errors
139
Download from Www.Somanuals.com. All Manuals Search And Download.
If the Video Firewall feature is enabled (see Upgrading the firmware), you will need to set up one or more routing
settings to control how IP traffic flows in and out of the MCU.
It is important that these settings are configured correctly, or you may be unable to make calls to or from the MCU
or access the web interface.
To configure the route settings, go to
In this section:
.
Current IP status
If both Ethernet ports are enabled, it is necessary to specify which port is used in certain special circumstances. Make
the appropriate selections described below, then click
to make any changes take effect.
The IP address to which the MCU will send
packets in the absence of more specific routing
makes sense to have precisely one default
gateway, even though different default gateways
may have been configured for Ports A and B. Use
this option to decide which port's default gateway
configuration to use as the unit's default gateway.
If Ethernet Port B is disabled, you cannot specify
that port as the default gateway preference.
Selecting Port B as default gateway preference
then disabling Port B will cause the preference to
revert to Port A.
The IP address to which the MCU will send
If Ethernet Port B is disabled, you cannot specify
requests to look up unrecognized host names in that port as the name server preference.
order to determine their corresponding IP
addresses. Only one name server (and associated
secondary name server) may be used, even
though different name servers may have been
configured for Ports A and B. Use this option to
decide which port's name server configuration to
use as the unit's name server.
Selecting Port B as name server preference then
disabling Port B will cause the preference to
revert to Port A.
140
Download from Www.Somanuals.com. All Manuals Search And Download.
In this section you can control how IP packets should be directed out of the MCU. You should only change this
configuration if you have a good understanding of the topology of the network(s) to which the MCU is connected.
Configuration of routes is divided into two sections: addition of new routes, and the display and removal of existing
routes.
To add a new route, first enter the details using the table below for reference. When you are satisfied with the details
entered, click
to make the addition. If the route already exists, or aliases (overlaps) an existing route,
you will be prompted to correct the problem and try again.
Use these fields to define the type of IP addresses To route all IP addresses in the range
to which this route applies.
192.168.4.128 to 192.168.4.255 for example,
specify the IP address as 192.168.4.128 and the
mask length as 25, to indicate that all but the last
seven bits address are fixed.
The IP address pattern must be in the dot-
separated IPv4 format, while the mask length is
chosen from a drop-down list.
The mask field specifies how many bits of the
address are fixed; unfixed bits must be set to zero
in the address specified.
Use this field to control how packets destined for Selecting Port A results in matching packets being
addresses matching the specified pattern are routed to Port A's default gateway (see
If the latter option is selected, you must specify will cause matching packets to be routed to Port
the IP address of the gateway to which you want B's default gateway.
packets to be directed.
If Ethernet Port B is disabled, the option to route
packets to Port B will be disabled.
Configured routes are listed below the Add IP route controls. For each route, the following details are shown:
The IP address pattern and mask
Where matching packets will be routed, with the possibilities being:
o
o
o
Port A - meaning the default gateway configured for Port A
Port B - meaning the default gateway configured for Port B
IP address - a specific address has been chosen
Whether the route has been configured automatically as a consequence of other settings, or added by the
user as described above.
141
Download from Www.Somanuals.com. All Manuals Search And Download.
The default route is configured automatically in correspondence with the default gateway preference field (see Port
preferences) and cannot be deleted. Any packets not covered by manually configured routes will be routed according
to this route.
Manually configured routes may be deleted by selecting the appropriate checkbox and clicking
.
If the default gateway preference is set to Port B and that port is disabled, the default route will be updated
automatically to route packets not covered by any manually configured route via Port A.
If a manually configured route specifies Port B and that port is disabled, packets matching that route
automatically routed via Port A, but discarded. You should take care to avoid this situation.
be
This table shows the current default gateway and name server(s) for Ethernet Ports A and B. No fields can be
changed, and are provided for reference when configuring the other parameters described in the sections above.
142
Download from Www.Somanuals.com. All Manuals Search And Download.
To configure IP services, go to
.
Use this page to control the type of services that may be accessed via Ethernet Ports A and B. You might use this if
one Ethernet port is connected to a network outside your organization's firewall, and you wish to restrict the level of
access that external users are entitled to, for example, by disabling FTP access via Port B. Refer to the table below for
more details.
In addition to controlling the Ethernet interfaces over which a service operates, this page also allows an administrator
to specify the port number on which that service is provided. If the port number for a service is changed, it is
necessary to ensure that the new value chosen does not clash with the port number used by any of the other services;
it is not, however, normally necessary to use anything other than the pre-configured default values.
Note that by default SNMP Traps are sent to port UDP port 162 (on the destination network management station);
this is configurable. For more information, refer to Configuring SNMP settings.
To reset all values back to their factory default settings, click the
.
button and then click
Enable/disable web access on the specified
Web access is required to view and change the
interface or change the port that is used for this MCU web pages and read online help files. If you
service.
disable web access on both Ports A and B you will
need to use the serial console interface to re-
enable it.
Note that QuickTime uses RTSP by default which
is listed as Streaming (other) on the
page. However, the QuickTime player
can be configured to use HTTP (that is it will
come from the web service port) instead.
If a port is disabled, this option will be
unavailable.
Enable/disable secure (HTTPS) web access on
This field is only visible if the MCU has the Secure
the specified interface or change the port that is management (HTTPS) feature key or an Encryption
used for this service.
feature key installed. For more information about
installing feature keys, refer to Upgrading the
By default, the MCU has its own SSL certificate
and private key. However, you can upload a new
private key and certificates if required. For more
information about SSL certificates, refer to
If a port is disabled, this option will be
unavailable.
143
Download from Www.Somanuals.com. All Manuals Search And Download.
Allow/reject incoming calls to the MCU using
H.323 or change the port that is used for this
service.
Disabling this option will not prevent outgoing
calls to H.323 devices being made by the MCU.
That is, the MCU will need to dial out to
conference participants who are using H.323.
If a port is disabled, this option will be
unavailable.
Allow/reject incoming calls to the MCU using
Disabling this option will not prevent outgoing
SIP over TCP or change the port that is used for calls to SIP devices being made by the MCU. That
this service.
is, the MCU will need to dial out to conference
participants who are using SIP over TCP.
If a port is disabled, this option will be
unavailable.
Allow/reject incoming encrypted SIP calls to the Disabling this option will not prevent outgoing
MCU using SIP over TLS or change the port that calls to SIP devices being made by the MCU. That
is used for this service.
is, the MCU will need to dial out to conference
participants who are using SIP over TLS.
If a port is disabled, this option will be
unavailable.
Allow/reject content streams using BFCP (Binary Disabling this option will prevent BFCP content
Floor Control Protocol).
being used in any conferences. BFCP can be used
to allow SIP endpoints to contribute and receive
Allow/disable streaming from the MCU to
If a port is disabled, this option will be
Windows Media Player or change the port that is unavailable.
used for this service.
For more information about streaming, refer to
Allow/disable RTSP (Real Time Streaming
Protocol) streaming from the MCU to
QuickTime or RealPlayer or change the port that
is used for this service.
If a port is disabled, this option will be
unavailable.
For more information about streaming, refer to
Enable/disable FTP access on the specified
FTP can be used to upload and download MCU
interface or change the port that is used for this configuration.
service.
You should consider disabling FTP access on any
port that is outside your organization's firewall.
If a port is disabled, this option will be
unavailable.
144
Download from Www.Somanuals.com. All Manuals Search And Download.
Allow/reject incoming and outgoing calls to the Disabling this option will prevent calls using SIP
MCU using SIP over UDP or change the port that over UDP.
is used for this service.
If a port is disabled, this option will be
unavailable.
You must use the same port number for both
Port A and Port B. The number is automatically
refreshed for Port B. You cannot change the Port
B UDP port numbers and they are always grayed-
out; if you want to allow incoming and outgoing
SIP (UDP) calls on Port B, ensure that you have
the video firewall as an activated feature (refer to
the tickbox for SIP (UDP) on Port B.
Enable/disable the receiving of the SNMP
protocol on this port or change the port that is
used for this service.
If a port is disabled, this option will be
unavailable.
You must use the same port number for both
Port A and Port B. The number is automatically
refreshed for Port B. You cannot change the Port
B UDP port numbers and they are always grayed-
out; if you want to enable the receiving of the
SNMP protocol on Port B, ensure that you have
the video firewall as an activated feature (refer to
the tickbox for SNMP on Port B.
Note that by default SNMP Traps are sent to port
UDP port 162 (on the destination network
management station); this is configurable. For
Enable/disable access to the built-in H.323
If a port is disabled, this option will be
gatekeeper or change the port that is used for the unavailable.
built-in H.323 gatekeeper.
You must use the same port number for both
Port A and Port B. The number is automatically
refreshed for Port B. You cannot change the Port
B UDP port numbers and they are always grayed-
out; if you want to open Port B for the H.323
gatekeeper, ensure that you have the video
firewall as an activated feature (refer to
the tickbox for H.323 gatekeeper on Port B.
145
Download from Www.Somanuals.com. All Manuals Search And Download.
To configure monitoring using SNMP, go to
.
The MCU sends out an SNMP trap when the device is shut down or started up. The SMNP page allows you to set
various parameters; when you are satisfied with the settings, click
Note that:
.
The 'system up time' that appears in the trap is the time since SNMP was initialized on the MCU (and
therefore will differ from the Up time reported by the MCU on the
>
page).
The SNMP MIBs are read-only.
Identifies the MCU in the SNMP system MIB.
The location that appears in the system MIB.
Usually you would give every device a unique
name. The default setting is:
Codian MCU
An optional field. It is useful where you have
more than one MCU to identify where the unit is
located. The default setting is:
Unknown
The contact details that appear in the system MIB. An optional field. The default setting is:
Unknown
Add the administrator’s email address or name to
identify who to contact when there is a problem
with the device. If SNMP is enabled for a port on
the public network, take care with the details you
provide here.
A description that appears in the system MIB.
An optional field, by default this will indicate the
model number of the unit. Can be used to
provide more information on the MCU.
146
Download from Www.Somanuals.com. All Manuals Search And Download.
Select this check box to enable the MCU to send If you do not check this box, no traps will be
traps.
sent.
Select this check box to enable authentication
failure traps.
You cannot select this check box unless you have
selected to Enable traps above. Authentication
failure traps are generated and sent to the trap
receivers when someone tries to read or write a
MIB value with an incorrect community string.
Enter the IP address or hostname for up to four The traps that are sent by the MCU are all SNMP
devices that will receive both the general and the v1 traps. You can configure trap receivers or you
authentication failure traps.
can view the MIB using a MIB browser. You can
set the UDP port number for the trap in the
format <IP address>: <port number>. By
default the UDP port number is 162.
Community string/password that gives read-only Note that SNMP community strings are not
access to all trap information.
secure. They are sent in plain text across the
network.
Community string/password that gives
read/write access to all trap information.
It is advisable to change the community strings
before enabling SNMP as the defaults are well
known.
Community string/password that is sent with all Some trap receivers can filter on trap
traps.
community.
147
Download from Www.Somanuals.com. All Manuals Search And Download.
To configure Quality of Service (QoS) on the MCU for audio and video, go to
.
QoS is a term that refers to a network's ability to customize the treatment of specific classes of data. For example,
QoS can be used to prioritize audio transmissions and video transmissions over HTTP traffic. These settings affect all
audio and video packets to H.323 and SIP endpoints, and to streaming viewers. All other packets are sent with a QoS
of 0.
The MCU allows you to set six bits that can be interpreted by networks as either Type of Service (ToS) or
Differentiated Services (DiffServ).
: Do not alter the QoS settings unless you need to do so.
To configure the QoS settings you need to enter a six bit binary value.
Further information about QoS, including values for ToS and DiffServ, can be found in the following RFCs, available
on the Internet Engineering Task Force web site www.ietf.org:
RFC 791
RFC 2474
RFC 2597
RFC 3246
In this section:
Default settings
The table below describes the settings on the
page.
Six bit binary field for prioritizing audio data
packets on the network.
Do not alter this setting unless you need to.
Do not alter this setting unless you need to.
Six bit binary field for prioritizing video data
packets on the network.
148
Download from Www.Somanuals.com. All Manuals Search And Download.
ToS configuration represents a tradeoff between the abstract parameters of precedence, delay, throughput, and
reliability.
ToS uses six out of a possible eight bits. The MCU allows you to set bits 0 to 5, and will place zeros for bits 6 and 7.
Bits 0-2 set IP precedence (the priority of the packet).
Bit 3 sets delay: 0 = normal delay, 1 = low delay.
Bit 4 sets throughput: 0 = normal throughput, 1 = high throughput.
Bit 5 sets reliability: 0 = normal reliability, 1 = high reliability.
Bits 6-7 are reserved for future use and cannot be set using the MCU interface.
You need to create a balance by assigning priority to audio and video packets whilst not causing undue delay to other
packets on the network. For example, do not set every value to 1.
DiffServ uses six out of a possible eight bits to set a codepoint. (There are 64 possible codepoints.) The MCU allows
you to set bits 0 to 5, and will place zeros for bits 6 and 7. The codepoint is interpreted by DiffServ nodes to
determine how the packet is treated.
The default settings for QoS are:
Audio 101110:
o
For ToS, this means IP precedence is set to 5 giving relatively high priority. Delay is set to low,
throughput is set to high, and reliability is set to normal.
o
For Diff Serv, this means expedited forwarding.
Video 100010:
o
For ToS, this means IP precedence is set to 4 giving quite high priority (but not quite as high as the
audio precedence). Delay is set to normal, throughput is set to high, and reliability is set to normal.
For DiffServ, this means assured forwarding (codepoint 41).
o
To return the settings to the default settings, click
.
149
Download from Www.Somanuals.com. All Manuals Search And Download.
The system date and time for the MCU can be set manually or using the Network Time Protocol (NTP).
To configure Time settings, go to
.
Note that changing the time or NTP settings will have an effect on the recorded times in the Call Detail Records log.
The current system date and time is displayed.
If you do not have NTP enabled and need to update the system date and/or time manually, type the new values and
click
.
The MCU supports the NTP protocol. If you are using it, configure the settings as required, and then click
.
The MCU re-synchronizes with the NTP server via NTP every hour.
If there is a firewall between the MCU and the NTP server, configure the firewall to allow NTP traffic to UDP port
123.
If the NTP server is local to Port A or Port B then the MCU will automatically use the appropriate port to
communicate with the NTP server. If the NTP server is not local, the MCU will use the port that is configured as the
default gateway to communicate with the NTP server, unless a specific IP route to the NTP server's network/IP
address is specified. To configure the default gateway or an IP route, go to
.
If selected, use of the NTP protocol is Enabled on
the MCU.
The offset of the time zone that you are in from You must update the offset manually when the
Greenwich Mean Time.
clocks go backwards or forwards: the MCU does
not adjust for daylight saving automatically.
The IP address or hostname of the server that is
acting as the time keeper for the network.
If NAT is used between the MCU and the NTP server, with the MCU on the NAT's local network (and not the NTP
server), no extra configuration is required.
If NAT is used between the MCU and the NTP server, with the NTP server on the NAT's local network, then
configure the NAT forwarding table to forward all data to UDP port 123 to the NTP server.
150
Download from Www.Somanuals.com. All Manuals Search And Download.
If you need to upgrade the firmware or activate features on the MCU, refer to these topics:
Storing user passwords securely
The main MCU software image is typically the only firmware component that you will need to upgrade.
Follow these steps to upgrade this image:
1. Check the Current version field to verify the currently installed version.
3. Download the latest available image and save it to a local hard drive.
4. Unzip the image file.
5. Log on to the MCU web browser interface.
6. Go to
7. Click
8. Click
.
to locate the unzipped file on your hard drive.
. The browser begins uploading the file to the MCU, and a new browser
window opens to indicate the progress of the upload. When finished, the browser window refreshes and
indicates that the "Main image upgrade completed."
9. The upgrade status displays in the MCU software upgrade status field.
10. Shutdown and restart the MCU.
Upgrades for the Loader software image are not typically available as often as upgrades to the main software image.
Follow these steps to upgrade this image:
1. Check the Current version field to verify the currently installed version.
2. Go to the software download pages of the web site to identify whether a more recent image is available.
3. Download the latest available image and save it to a local hard drive.
4. Unzip the image file.
5. Click
6. Click
to locate the unzipped file on your hard drive.
. The browser begins uploading the file to the MCU, and a new browser
window opens to indicate the progress of the upload. When finished, the browser window refreshes and
indicates that the "Loader image upgrade completed."
7. The upgrade status displays in the Loader upgrade status field.
8. Shutdown and restart the MCU.
151
Download from Www.Somanuals.com. All Manuals Search And Download.
The MCU requires activation before most of its features can be used. (If the MCU has not been activated, the banner
at the top of the web interface will show a prominent warning; in every other respect the web interface will look and
behave normally.)
Advanced MCU features (such as Video Firewall) are not enabled as standard, and require additional activation. For
information about configuring the video firewall, refer to the FAQ section in the support pages of the web site.
If this is a new MCU you should receive the unit already activated; if it is not, you have upgraded to a newer firmware
version, or you are enabling a new feature, you may need to contact your supplier to obtain an appropriate activation
code. Activation codes are unique to a particular MCU so ensure you know the unit's serial number such that you
may receive a code appropriate to your MCU.
Regardless of whether you are activating the MCU or enabling an advanced feature, the process is the same:
1. Check the Activated features (MCU activation is shown in this same list) to confirm that the feature you
require is not already activated.
2. Enter the new feature code into the Activation code field exactly as you received it, including any dashes.
3. Click
. The browser window should refresh and list the newly activated feature, showing the
activation code beside it. Activation codes may be time-limited. If this is the case, an expiry date will be
displayed, or a warning that the feature has already expired. Expired activation codes remain listed, but the
corresponding feature will not be activated.
If the activation code is not valid, you will be prompted to re-enter it.
4. It is recommended that you record the activation code in case you need to re-enter it in the future.
Successful MCU or feature activation has immediate effect and will persist even if the unit is restarted.
Note that you can remove MCU feature keys by clicking the
page.
link next to the feature key on the
You can configure the MCU to hash user passwords before storing them in the configuration.xml file. The
configuration.xml file is used for Backing up and restoring the configuration of the MCU. If you do not select to hash
stored passwords, all user passwords are stored in plain text in the configuration.xml; this might be a security issue. If
you select to hash stored passwords, they will not be stored anywhere on the MCU in plain text; instead the
passwords will be stored as hash sums. Note that hashing user passwords is an irreversible process.
To hash stored user passwords:
1. Go to
2. Select Hash stored passwords and click
and scroll down to the Security settings section.
. You will see a warning telling you that this is
an irreversible step. If you are sure you want to hash stored user passwords, click
.
152
Download from Www.Somanuals.com. All Manuals Search And Download.
It is sometimes necessary to shut down the MCU, generally to restart as part of an upgrade (see Upgrading the
firmware). You should also shut down the MCU before intentionally removing power from the MCU.
Shutting down the MCU will cause all conference participants to be disconnected, and allows the MCU to ensure that
all data (such as Call Detail Records) is stored correctly. You will lose network connectivity with the MCU for a few
minutes while you restart the unit.
To shut down the MCU, follow these steps:
1. Go to
2. Click the
.
button.
3. Confirmation of shutdown is required; the button changes to
.
4. Click again to confirm.
5. The MCU will begin to shut down. The banner at the top of the page will change to indicate this.
When the shutdown is complete, the button changes to
.
6. Click this button a final time to restart the MCU.
153
Download from Www.Somanuals.com. All Manuals Search And Download.
The General Status displays an overview of the MCU status. To access this information, go to
Refer to the table below for details of the information displayed
The specific Codian MCU model.
The unique serial number of the MCU.
The installed software version. You will need to provide this information when speaking to
Technical support.
The build version of installed software. You will need to provide this information when
speaking to Technical support.
The time since the last restart of the MCU.
The host name assigned to the MCU.
The IP address assigned to the MCU.
The current processor utilization of the MCU.
An overview of the current media loading of the MCU.
If the total load is consistently high, you might need to add an additional MCU to better
handle your video conferencing needs. Also, the total load may increase during periods of
peak conference use. A low video load with high audio load implies that most of the
conference participants have connected with audio-only endpoints.
The system time on the MCU. Click
to modify this value. The
page
opens in which you can update the system date and time manually or refresh the time from
an NTP server. For more information about the
The system log displays the last eight shutdown and upgrade events in date order with the
most recent system log event at the top of the list.
User
requested
shutdown
User
requested
upgrade
Unknown
The log will also display "unknown" if there has been an unexpected reboot or power
failure, which you should report to Technical support if it happens repeatedly.
154
Download from Www.Somanuals.com. All Manuals Search And Download.
The conference status page displays the status of active and completed conferences and video and audio processing.
To access this information, go to
.
Refer to the table below for assistance in interpreting the information displayed:
For information about the number and type of ports provided by each MCU model, refer to MCU port matrix.
In many cases, the values displayed on this page are shown in the format
; this represents:
– the current value of this statistic
– the maximum achieved value of this statistic (since last reset)
– the maximum allowable number for this statistic (this varies by MCU model)
Statistics for which there is no set maximum will be displayed as just
described above.
, where and have the meanings as
Where the highest value attained is shown in parentheses (i.e. in the above example), this value can be reset by
selecting
. These values can be useful in monitoring peak MCU usage over a period of time.
Conference status displays an overview of active and completed conferences.
The number of conferences that are currently configured on the MCU.
The number of auto attendants that are currently in use. If you dial in with an
endpoint to the auto attendant, this will go up by one. It does not reflect the
number of configured auto attendants.
The number of conferences that were once active but are now not.
The total number of calls into an auto attendant, excluding any in progress. If you
call an auto attendant and enter into a conference or hang up the call, this number
increases by one.
The number of people currently in conferences.
The number of people who were previously participating in a conference (since
the last time the MCU restarted).
The number of people currently watching conferences via a streaming application,
such as Apple QuickTime or RealPlayer.
The number of streaming sessions out of the Active streaming viewers value shown
above which are using TCP media transport rather than UDP.
155
Download from Www.Somanuals.com. All Manuals Search And Download.
shows the number of video ports in use. This corresponds to the number of
connected participants that are either contributing or being sent video, plus the
number of conferences for which streaming is active.
shows the number of audio-only ports in use. This corresponds to the number of
connected participants that are contributing or being sent audio but not video.
This value is shown if the model of MCU provides content channel and streaming
content ports in use across the currently active conferences.
the total number of video ports reserved across the currently active conferences.
Note that each conference for which streaming is enabled requires use of a video
streaming and content channel ports are provided, streaming viewers and
conferences' content channel video allocations will use the streaming and content
channel ports rather than the available video ports; where streaming and content
channel ports are not provided, streaming viewers and content channel allocations
will use available video ports.
If a streaming and content channel port or a video port is unavailable (or not
allocated in advance when the MCU is in Reserved mode), it will not be possible
to stream that conference. If a video port has been allocated for streaming a
conference, any number of streaming viewers will be able to view that conference
via streaming, at any combination of available bit rates. These streaming
allocations are included in the total displayed.
the total number of audio-only ports reserved across the currently active
conferences.
This value is shown if the model of MCU provides content channel and streaming
about the ports your MCU provides, refer to MCU port matrix.
This value shows the total number of streaming and content ports reserved across
the currently active conferences.
of the number of video ports reserved, how many are actually being used by
active conference participants or streaming allocations.
of the number of audio-only ports reserved, how many are actually being used by
active conference participants.
This value is shown if the model of MCU provides content channel and streaming
about the ports your MCU provides, refer to MCU port matrix.
This value shows the total number of streaming and content ports in use across
the currently active conferences.
156
Download from Www.Somanuals.com. All Manuals Search And Download.
Video status displays an overview of current video resource use.
The number of video streams being received by Unicast indicates video streams sent directly to
the MCU.
the MCU (incoming) or directly to the endpoints
(outgoing) rather than multicast streams
broadcast to the network and captured or sent by
the MCU.
The number of video streams being sent by the
MCU.
The total video data rate being received by the
MCU.
The total video data rate being sent by the MCU.
Audio status displays an overview of current audio resource use.
The number of audio streams being received by Unicast indicates audio streams sent directly to
the MCU.
the MCU (incoming) or directly to the endpoints
(outgoing) rather than multicast streams
broadcast to the network and captured or sent by
the MCU.
The number of audio streams being sent by the
MCU.
Displays active audio participants using neither
G.711 or G.722.
At most half of the MCU's allowable participants
are permitted to use complex audio channels.
A participant is considered to be using complex
audio if either it is transmitting a complex audio
channel or the MCU is sending complex audio to
it.
157
Download from Www.Somanuals.com. All Manuals Search And Download.
The
this page, go to
information and on the
page shows various status items related to a conference's content channel. To view
click the name of the conference about which you want more
tab, click the Content channel link.
The displayed information is split into three sections:
This section shows a graphical representation of the current content channel. If there is no active content channel,
inactive will be shown here. Where there is an active content channel, clicking on this preview window will cause it to
update.
This section details the characteristics of the video stream supplying the content channel. This stream will either be a
H.239 channel from one of the H.323 conference participants, or a BFCP (Binary Floor Control Protocol) channel
from a SIP conference participant, or a main video channel configured for use as the content channel source (for
instance, a VNC connection to a PC).
While there is at most one source video stream for a conference's content channel, the content channel can be viewed
by several people, either via H.239 or BFCP to video conferencing endpoints, or via streaming (DJPEG) to desktop
PCs. The Transmitted video section of this page shows the number of viewers of each type, plus some statistics on the
currently active H.239/BFCP video stream and DJPEG channel.
It is possible to retrieve a set of diagnostics relating to the conference's content channel. This is accomplished by
clicking on the Download content channel diagnostics control beneath the main table. You should not need to access these
diagnostics except when directed to by Codian support personnel.
158
Download from Www.Somanuals.com. All Manuals Search And Download.
The Health Status displays information about the hardware components of the MCU. To access this information, go
to
Note that the Worst status seen conditions are those since the last time the unit was restarted.
To reset these values, click
. Refer to the table below for assistance in interpreting the information displayed.
Displays two possible states:
OK
– component is functioning properly
– Check with your support
provider; component might require
service
Out of spec
If the
spec", but
column displays "Out of
is "OK", monitor the
States indicate both
conditions.
and
status regularly to verify that it was only a
temporary condition.
Displays three possible states:
– temperature of the MCU is within
the appropriate range
– Check the ambient
OK
temperature (should be less than 34
degrees Celsius) and verify that the air
vents are not blocked
Out of spec
Critical
– temperature of MCU is too
high. An error also appears in the event
log indicating that the system will
shutdown in 60 seconds if the condition
persists
States indicate both
conditions.
and
If the
spec", but
column displays "Out of
is "OK", monitor the
status regularly to verify that it was only a
temporary condition.
159
Download from Www.Somanuals.com. All Manuals Search And Download.
The port provision of the various MCU models is shown in the table below. Each video port can be used by one
video-conferencing participant. Each audio port can be used by one voice-only participant in a video conference.
Where streaming and content ports are provided, when streaming and content ports are used up, video ports will not
be allocated to streaming viewers or providers of content; where streaming and content ports are not provided,
conferences with streaming viewers and conferences with content will use available video ports.
6
6
6
0
12
20
30
40
6*
12
20
30
40
40
20
12
20
30
40
6*
12
20
30
40
40
20
0
0
0
6
12
20
30
40
0
20
* This is increased to 12 when running in SD mode
160
Download from Www.Somanuals.com. All Manuals Search And Download.
If you are experiencing complex issues that require advanced troubleshooting, you may need to collect information
from the MCU logs. Typically, you will be working with Technical support who can help you obtain these logs.
The last 2000 status messages generated by the MCU are displayed in the Event log page. In general these messages
are provided for information, and occasionally Warnings or Errors may be shown in the Event log. The presence of
such messages is not cause for concern necessarily; if you are experiencing a specific problem with the operation or
performance of the MCU, Technical support can interpret logged messages and their significance for you.
You can:
Change the level of detail collected in the traces by editing the Capture filter page. You should not modify
these settings unless instructed to do so by Technical support
Display the log as text: go to
and click
Change which of the stored Event log entries are displayed by editing the Display filter page
Send the event log to one or more syslog servers on the network for storage or analysis. The servers are
defined in the Syslog page. For more information, refer to Logging using syslog
Empty the log by clicking
The capture filter allows you to change the level of detail to collect in the Event log traces.
.
Normally, the capture filter should be set to the default of Errors, Warnings and Information for all logging sources.
There is no advantage in changing the setting of any source without advice from Technical support. The diagnostic
information generated by the MCU can be very verbose and enabling excessive debugging without advice can cause
the Event log to become full very quickly and is not advised.
The display filter allows you to view or highlight stored Event log entries. Normally, you should not need to view or
modify any of the settings on this page.
You can configure the MCU to send event messages to up to four syslog servers. To add or remove a syslog server,
go to
and make the changes you require. See Logging using syslog.
161
Download from Www.Somanuals.com. All Manuals Search And Download.
The H.323/SIP log page records every H.323 and SIP message received or transmitted from the MCU. The log can
be exported in an .xml file. By default the H.323/SIP log is disabled because it affects performance, but Techincal
support may ask you to enable it if there is a problem with a unit in your network.
In addition to the logs described above, the MCU can also store Call Detail Records (CDR) which may be used for
auditing and billing purposes. Events in the log are displayed in the CDR log page. See Working with Call Detail
Records for more details.
162
Download from Www.Somanuals.com. All Manuals Search And Download.
To configure the syslog facility, go to
In this section:
Using syslog
Refer to this table for assistance when configuring Syslog settings:
Enter the IP addresses of up to four Syslog
receiver hosts.
The number of packets sent to each configured
host will be displayed next to its IP address.
A configurable value for the purposes of
identifying events from the MCU on the Syslog
host. Choose from the following options:
0 - kernel messages
Choose a value that you will remember as being
the MCU.
: Various operating system daemons and
processes have been found to utilize Facilities 4,
10, 13 and 14 for security/authorization, audit,
and alert messages which seem to be similar.
1 - user-level messages
2 - mail system
3 - system daemons
4 - security/authorization messages (see
Note 1)
5 - messages generated internally by
syslogd
: Various operating systems have been found
to utilize both Facilities 9 and 15 for clock
(cron/at) messages.
6 - line printer subsystem
7 - network news subsystem
8 - UUCP subsystem
9 - clock daemon (see Note 2)
10 - security/authorization messages
(see Note 1)
Processes and daemons that have not been
explicitly assigned a Facility value may use any of
the "local use" facilities (16 to 21) or they may
use the "user-level" facility (1) - and these are the
values that we recommend you select.
11 - FTP daemon
12 - NTP subsystem
13 - log audit (see Note 1)
14 - log alert (see Note 1)
15 - clock daemon (see Note 2)
16 - local use 0 (local0)
17 - local use 1 (local1)
18 - local use 2 (local2)
19 - local use 3 (local3)
20 - local use 4 (local4)
21 - local use 5 (local5)
22 - local use 6 (local6)
23 - local use 7 (local7)
163
Download from Www.Somanuals.com. All Manuals Search And Download.
The events that are forwarded to the syslog receiver hosts are controlled by the event log capture filter.
To define a syslog server, simply enter its IP address and then click
sent to each configured host is displayed next to its IP address.
. The number of packets
: Each event will have a severity indicator as follows:
0 - Emergency: system is unusable (unused by the MCU)
1 - Alert: action must be taken immediately (unused by the MCU)
2 - Critical: critical conditions (unused by the MCU)
3 - Error: error conditions (used by MCU error events)
4 - Warning: warning conditions (used by MCU warning events)
5 - Notice: normal but significant condition (used by MCU info events)
6 - Informational: informational messages (used by MCU trace events)
7 - Debug: debug-level messages (used by MCU detailed trace events)
If the MCU is being managed by a remote management system, for instance Tandberg TMS, information on that
remote system may be shown on this page. In certain circumstances you may need to remove the link between the
external system and the MCU using the "Clear" button here.
164
Download from Www.Somanuals.com. All Manuals Search And Download.
The MCU implements SIP as defined in RFC 3261. Any product wishing to establish SIP calls with the MCU should
implement INVITE, ACK, BYE, and CANCEL messages along with responses from 1xx to 6xx. The MCU acts as a
client and does not return 5xx and 6xx responses itself; however, proxies and other intermediaries may do so.
To use a SIP registrar in conjunction with the MCU, you must register an ID for the MCU with the SIP registrar. The
MCU can register itself, and individual conferences and auto attendants with a SIP registrar.
For video Fast Update Requests, the MCU uses a type that involves sending an INFO message with an XML body.
This only applies to video endpoints, but these endpoints should be able to correctly reply to INFO requests whether
or not they understand them as Fast Update Requests.
The username and password that you provide on the
page are the authentication details for all SIP
authentication from the MCU. That is, for the SIP registrar and any SIP proxy. If you have individual conferences
registered with the SIP registrar, the username will be the numeric identifier of the conference and the password will
be the one entered on the
page.
165
Download from Www.Somanuals.com. All Manuals Search And Download.
The MCU is able to generate Call Detail Records (CDR) which may be used for auditing and billing purposes. When
logging is enabled, records are generated whenever a conference starts or finishes, when participants join and leave
conferences and so forth.
To use the CDR feature, there must be a 256 Mb compact flash card in the slot in the front of the unit. If there is no
compact flash card present, and you have enabled CDR logging, errors will be recorded in the Event log.
When enabled, the CDR log is stored on the compact flash card and displayed on the
page. You can
either view the CDR log on that page, or you can download it as an XML file. You cannot read from the compact
flash card using any device other than the MCU.
When enabled, CDRs are flushed to the compact flash card every five minutes; when the card is full, the oldest logs
are overwritten.
To view and control the CDR log, go to
and click the
tab. Refer to the tables below for details of the
options available and for a description of the information displayed.
Call Detail Record log
The CDR log can contain a lot of information. The controls in this section will help you to select the information for
display that you find most useful. When you have finished making changes, press
to make those
changes take effect. Refer to the table below for a description of the options:
This field indicates whether CDR logging is
enabled or disabled. Use the two buttons (
Enabling or disabling CDR logging has immediate
effect. There is no need to press
after pressing one of these buttons.
and
) to change status.
When you enable logging, the MCU writes the
CDRs to the compact flash card.
Ensure there is a compact flash card in the slot on
the front of the unit.
The current number of CDRs in the log.
Use this field to limit the scope of the displayed The filter string applies to the Message field in the
Call Detail Records. The filter string is not case- log display. If a particular record has expanded
sensitive.
details, the filter string will apply to these as well.
By default, the CDR log shows only brief details Selecting will show the greatest amount of
of each event. Select from the options listed to
display more details (when available).
detail for all messages, regardless of which other
options are checked.
166
Download from Www.Somanuals.com. All Manuals Search And Download.
This table shows the logged Call Detail Records, subject to any filtering applied (see Call Detail Record log controls,
above). The fields displayed and the list's associated controls are described below:
CDR log display
The CDR log includes all stored Call Detail Records, and all available details, regardless of the current filtering and
display settings. It is possible to download all or part of the CDR log in XML format using the web interface.
To download the CDR log, click
or
. (Note that if there are a large
number of logged Call Detail Records, it may take several seconds to download and display them all.)
To clear the CDR log, click
. This will permanently remove Call Detail Records X to Y. Due to the way
the CDR log works it may not be possible to delete all records; the button name indicates which records can be
deleted.
The CDR log list shows some or all of the stored records, depending on the filtering and display settings (see Call
Detail Record log controls). You may click on the column headings to sort by that field. Refer to the table below to
understand the fields displayed in the CDR log list:
This is the unique index number for this Call
Detail Record.
This field gives the time at which the Call Detail Records are created as different conference
Record was created.
events occur. The time the record was created is
the time that the event occurred.
Changing the time or NTP settings of the MCU
will affect the displayed time for the Call Detail
This is the number of the conference to which this Each new conference is created with a unique
record applies
numeric index. All records pertaining to a
particular conference display the same conference
number. This can make auditing conference
events much simpler.
This shows the type of the Call Detail Record,
and brief details if available.
The display settings allow you to display more
extensive details for different record types.
The filter string allows you to select for display
only records where a particular word or string
occurs.
167
Download from Www.Somanuals.com. All Manuals Search And Download.
The CDR log time stamp is stored in UTC time and not local time like the Event log, but converted to local time
when displayed in the CDR log.
Changing the time and NTP’s UTC Offset (on the
>
page) will affect the CDR log time in the
following ways:
Changing the time, either changing the system time or via an NTP update will cause new CDR logs to show
the new time but no change will be made to existing logged CDR events
With NTP enabled, setting a UTC offset will change the displayed time for all the CDR events; the stored
time will remain the same because it is stored in UTC and the offset is applied for display purposes
Enabling or disabling NTP when an offset is configured will cause the display time to change for all existing
events and the UTC time will change for logging future CDR events. This is because, when NTP is disabled,
the current time is treated as UTC with an offset of 0
168
Download from Www.Somanuals.com. All Manuals Search And Download.
In this section:
Controlling the auto-refreshing of status pages on the MCU
Controlling the display of thumbnail preview images
Controlling the confirmation of participant disconnections
Controlling the audio and visual muting of conference participants
Customizing voice prompts on the MCU
The MCU provides you with options for customizing the voice prompts, the viewing of thumbnail previews, and for
controlling the auto-refreshing of user interface pages.
: the user interface (that is the text you see on the web interface of the MCU) can be localized by Codian or by
your reseller. This type of customization is the localization of the text on the web interface and these online help
pages. That is, the text has been translated into your local language. In the case where you have a localized unit, the
Use localization package check box will be checked. For more information refer to Customization: more information.
The MCU allows you to type using any character set when entering text into the web interface. For example, when
naming endpoints or users, you can use any character set you require.
To control the auto-refreshing of status pages on the MCU:
1. Go to
.
2. Choose the time interval for page auto-refreshes or, to stop pages from auto-refreshing, choose
.
The status pages affected by this control are as follows:
o
o
o
o
o
o
o
3. Click
.
To control the display of thumbnail preview images on the MCU:
1. Go to
.
2. Choose whether you want to Show video thumbnail images or not. This controls whether or not you will see a
preview of what an endpoint sees in the conference and participants pages that can show a preview of the
conference. Note that thumbnail images will not be shown for conferences where encryption is required.
3. Click
.
169
Download from Www.Somanuals.com. All Manuals Search And Download.
The default settings for the MCU allow you to disconnect, without confirmation, individual participants from a
conference on the page. On the page, you can
configure the MCU to display an "Are you sure?" confirmation box when attempting to disconnect an individual
participant. Note that all-participant disconnections always require confirmation.
To control the confirmation of individual-participant disconnections:
1. Go to
.
2. If you want attempted individual-participant disconnections to require confirmation, enable the Confirm
individual participant disconnections option and click
.
Using the default settings of the MCU, a conference's
controls that allow the muting of a participant's audio and/or video contribution. The
page displays
page
allows you to control the presence or absence of these controls.
To control the presence or absence of audio and visual muting controls:
1. Go to
.
2. For Participant list controls, select the control(s) that you want to appear on the
page.
By default the MCU includes English voice prompts spoken by a female American voice. You may wish to replace
these prompts with your own in order to change the wording, language or accent used. Alternative prompts may be
uploaded individually using the web interface. Alternatively, a collection of voice prompts may be uploaded in one go
by means of a resource package (see Uploading a customization package).
The customization of voice prompts is controlled via the web interface. Go to
. Refer to the
sections below for details of the options available and for a description of the information displayed:
Using default US English voice prompts
Uploading a customization package
Viewing the available voice prompts
Uploading and downloading customized voice prompts
Voice prompt specification
Making the best possible recordings
170
Download from Www.Somanuals.com. All Manuals Search And Download.
The default set of voice prompts is provided in US English and is the standard set of voice prompts supplied with the
MCU. These are spoken by a female voice in Americanized English. If your unit is using customized voice prompts
and you want to return to using the default set of voice prompts:
1. Go to
2. In the
.
section, uncheck Use customized voice prompts.
3. If your unit was provided to you as a localized unit, uncheck Use localization package.
4. Click
.
The default voice prompts will be applied immediately, although it may take a few seconds before everyone
connected to the MCU is able to hear the new prompts.
It is possible to upload a collection of alternative voice prompts to the MCU with a single upload operation, using a
customization package. Such a package may have been supplied to you by Codian or one of its representatives, or you
may have created the package yourself (see Downloading a customization package).
To upload a package:
1. Go to
2. In the
3. Click
.
section, click
and locate the .package file on your computer.
.
The upload may take several seconds, depending on the size of the package file and the speed of your network
connection. When the upload is complete, a status screen will be shown, displaying some or all of the individual voice
prompt customizations included in the package if the upload was a success, or an error message if the upload failed for
some reason.
To apply the uploaded customization package:
In the
section, check Use customized voice prompts.
: If you were already using uploaded alternative voice prompts on the MCU, then these will be immediately
replaced by those in the customization package. If a particular customized file is not included in the package, then any
existing customization is unchanged. This allows customization sets to be built up using several different packages if
required.
You may review the voice prompt customizations available in the table headed Voice prompts. The
list
displays all voice prompt customizations, providing details for those which have alternatives uploaded. Because these
lists can be quite long, by default they are hidden. Instead, the number of customizations (files) available is shown. If
any have been modified (meaning an alternative customization has been uploaded, either individually, or as part of a
package), then this is indicated by an asterisk after the table name.
171
Download from Www.Somanuals.com. All Manuals Search And Download.
To expand any list to show all customizations, click
.
; you may subsequently hide it again by clicking
In the expanded state, the table shows, for each customization, a description of the file, the standard MCU filename
for the customization, and the length and date modified (uploaded) of alternative customizations present. Extra
information is provided by the following symbols:
Customizations where an alternative is available that can be individually uploaded or downloaded are
indicated by two asterisks (**) after their name
Customizations where an alternative is available that cannot be uploaded or downloaded individually are
indicated by one asterisk (*) (these are files that have been provided by Codian or by your reseller)
Customizations that are part of a localization package from Codian or your reseller are indicated by a plus
sign (+)
Refer to the sections below for details of further functionality provided by the
list:
Uploading individual voice prompts
Downloading individual voice prompts
Downloading a customization package
Deleting customized voice prompts
You may upload individual voice prompts. To do this:
1. Go to
2. In the
.
section, click
and locate the voice prompt
file you require.
3. For that voice prompt, click
already been uploaded.
. You may do this regardless of whether an alternative customization has
4. You will be presented with a new screen, allowing you to locate and upload the customization of your
choice. Click button to locate the voice prompt file on your computer. Voice prompt files must be
in the following format:
o
o
o
o
o
Microsoft WAVE (.WAV) format
16kHz (16000Hz) sample rate
Mono
Uncompressed
Maximum 10 seconds long
If you upload a file that is not in this format, the upload may fail or the voice prompt may sound distorted
when heard by users. Use an audio editing package of your choice to make any conversions required. See
Making the best possible recordings for how to obtain the best possible voice prompts for your MCU
customization.
Note that in addition to the 10 second length limit per prompt, there is a total length limit of 4 minutes for
the full set of prompts. That is, if all samples were played back-to-back, it should take no more than 240
seconds.
172
Download from Www.Somanuals.com. All Manuals Search And Download.
5. When you have located the file you wish to upload, click
. If the upload is successful, a
page displaying the size of the file uploaded will be displayed; otherwise an error will be shown. If the
upload fails, check your audio file matches the specification above before contacting your support
representative.
You may wish to review a customization that has been previously uploaded to the MCU. To do this,
1. Go to
2. In the
3. For that voice prompt, right-click
.
section, locate the voice prompt file you require.
and choose
(or your web browser's equivalent
operation). The file will be downloaded to your computer for reference.
Only alternative customizations can be downloaded in this way; the default voice prompts may not be downloaded.
In addition, only customizations uploaded as individual files may be downloaded; those uploaded as part of a package
may not be downloaded.
Once you are satisfied with your customizations, you may wish to apply the entire set to another MCU. Rather than
individually uploading the alternative voice prompts to each one, you may create a customization package.
To create a customization package containing all of the alternative voice prompts previously uploaded:
1. Go to
2. Click
.
at the bottom of the
list. The customization package will
be downloaded to your computer.
A package may only contain resources uploaded as separate files; those uploaded as part of another package may not
be included. The package download option may be unavailable if no voice prompts qualify for inclusion.
If you are dissatisfied with a voice prompt that you have uploaded to the MCU, you may delete it in the following
manner:
1. Locate the voice prompt of interest in the list.
2. Click the check box to the left of the voice prompt.
3. Click
to remove the voice prompt.
Only alternative voice prompts may be deleted in this way; the default voice prompts cannot be deleted. If you delete
an alternative customization, it will immediately revert to the default prompt, even if you have selected Use customized
voice prompts at the top of the page.
You may wish to delete all customizations. To do this, press
. Remember that you may revert to the default
set of voice prompts without needing to delete any alternative customizations (see Using default US English voice
prompts).
173
Download from Www.Somanuals.com. All Manuals Search And Download.
Below is a complete list of the voice prompts that may be customized. The default wording is shown for each prompt.
You do not have to use exactly the same wordings if they are not appropriate for your needs, and are provided only as
a guide.
I'm sorry, there is already a conference with that number
Your conference is now over. Goodbye
I'll connect you to your conference now
Please enter the conference code now
Please enter the conference number followed by the pound key,
or press star to create a new conference
Please enter the security PIN for this conference now
Please enter the conference number for the conference you are
creating, followed by the pound key
Please enter the PIN for the conference you are creating,
followed by the pound key; if you don't want a PIN, just press
the pound key
Please enter the security PIN
To join a conference you may use the far end camera controls on
your remote
You are the first participant to join the conference
Sorry, I did not recognize that security PIN, please try again
Thank you, your conference is starting now
Your conference is scheduled to end in two minutes
Sorry, I did not recognize that conference code, please try again
Waiting for conference chairperson
Hello, welcome to the conferencing system
There are many factors to consider when recording alternative voice prompts in order to get the best results. Below
is a brief summary of the points to bear in mind, though a more detailed document is available from Codian on
request.
It is best to make each recording with the ideal settings and hence avoid any sample-rate or resolution changes. As
discussed, the ideal format is Microsoft Wave (.WAV) format, uncompressed, mono, at 16 kHz and 16-bit
resolution.
If you are unable to make mono recordings, the MCU can convert stereo recordings.
174
Download from Www.Somanuals.com. All Manuals Search And Download.
It is important to minimize background noise (hiss) as much as possible. This includes ambient noises such as road
noise and slamming doors etc. but also try to keep fan noise and similar to a minimum.
When played back by the MCU, samples with background noise are very apparent.
If possible, record all voice prompts in one session. This will ensure that all voice and background conditions remain
constant and the recorded voice will sound similar from prompt to prompt.
Record prompts using a relatively constant loudness of voice. Although it may take some trial and error, the best
recordings will result from speaking loud enough that the voice is recorded loudly compared to any residual
background noise, but not so loudly that it sounds distorted when played back.
175
Download from Www.Somanuals.com. All Manuals Search And Download.
There are three customization levels on the unit (for voice-prompts, web interface, help pages, and text messages):
the factory default files that are provided in US English
localization files that are sometimes installed by a reseller
customized voice prompts files that can be uploaded and downloaded by you
For every customizable file:
1. If there is a customization file present and
2. Otherwise, if
is checked, that file will be used.
is checked, the unit will use the localized file.
3. If 1 and 2 are not true, then the unit will use the default US English file.
The files that compose the default file set for the web interface, the voice prompts, the help pages, and text messages
cannot be deleted. If you are using your own customization files or a localized unit you can return the unit to using
the default file set:
To return to the defaults:
1. Go to
2. Ensure both
.
and
are both unchecked.
Note that the default voice prompts will be used where there is no alternative voice prompt available, even if
is selected.
In some parts of the world, units are available where the help pages, the voice prompts, the text messages, and some
of the web interface are in the local language. In this case, Codian or the reseller has uploaded a package that provides
localized files to replace files in the default file set. This localization process can only be performed by Codian or by a
reseller. If you have a localized unit, you are able to select to return to the default US English file set (see above).
Localization is a global change and affects all customizable files. If you have a localized unit, you cannot upload and
download localized files on a file by file basis.
Customization files for voice prompts can be recorded and uploaded by any admin user of the MCU. These files can
be uploaded one by one or as a package. You can create your own package by uploading all the files you require to an
MCU and then downloading them as a package. For more information, refer to Customizing the user interface. A
customization package does not have to include a complete set of files. Where a file name duplicates an existing
uploaded voice prompt file, that file will be overwritten.
176
Download from Www.Somanuals.com. All Manuals Search And Download.
You can save the configuration of the MCU to a file that you can store away from the unit. If necessary this file can be
used to restore the configuration of the unit.
1. Ensure that the FTP service is enabled on the
page.
2. Connect to the MCU using an FTP client. When asked for a user name and password, enter the same ones
that you use to log in to the unit's web interface as an administrator.
You will see a file called configuration.xml. This contains the complete configuration of your unit.
3. Copy this file and store it somewhere safe.
The backup process is now complete.
1. Locate the copy of the configuration.xml file that you want to restore.
2. Ensure that the FTP service is enabled on the
page.
3. Connect to the MCU using an FTP client. When asked for a user name and password, use the same ones that
use to log in to the unit's web interface as an administrator.
4. Upload your configuration.xml file to the unit, overwriting the existing file on the unit.
The restore process is now complete.
Note that the same process can be used to transfer a configuration from one unit to another. However, before doing
this, be sure to keep a copy of the original feature keys from the unit whose configuration is being replaced.
If you are using the configuration file to configure a duplicate unit, for example in a network where you have more
than one MCU, be aware that if the original unit was configured with a static address, you will need to reconfigure
the IP address on any other units on which you have used the configuration file.
177
Download from Www.Somanuals.com. All Manuals Search And Download.
The
page can be used for troubleshooting issues that arise because of problems in the network
between the MCU and a remote video conferencing device being called (or a device from which a user is attempting
to call the MCU).
The
page enables you to attempt to 'ping' another device from the MCU's web interface and
perform a 'traceroute' of the network path to that device. The results show whether or not you have network
connectivity between the MCU and another device. You can see from which port the MCU will route to that address.
For a hostname, the IP address to which it has been resolved will be displayed.
To test connectivity with a remote device, go to
hostname of the device to which you want to test connectivity and click
. In the text box, enter the IP address or
.
For each successful 'ping', the time taken for the ICMP echo packet to reach the host and for the reply packet to
return to the MCU is displayed in milliseconds (the round trip time). The TTL (Time To Live) value on the echo
reply is also displayed.
For each intermediate host (typically routers) on the route between the MCU and the remote device, the host's IP
address and the time taken to receive a response from that host is shown. Not all devices will respond to the messages
sent by the MCU to analyse the route; routing entries for non-responding devices is shown as <unknown>. Some
devices are known to send invalid ICMP response packets (e.g. with invalid ICMP checksums); these responses are
not recognized by the MCU and therefore these hosts' entries are also shown as <unknown>.
: The ping message is sent from the MCU to the IP address of the endpoint that you enter. Therefore, if the
MCU has an IP route to the given IP address, regardless of whether that route lies out of port A or port B, the ping
will be successful. This feature allows the MCU’s IP routing configuration to be tested, and it has no security
implications.
: If you are unable to ping the device then check your network configuration especially any firewalls using NAT.
178
Download from Www.Somanuals.com. All Manuals Search And Download.
If the MCU has the Secure management (HTTPS) or Encryption feature key installed, and you enable the secure web
service on the page, you will be able to access the web interface of the MCU using HTTPS. The
MCU has a local certificate and private key pre-installed and this will be used by default when you access the unit
using HTTPS. However, we recommend that you upload your own certificate and private key to ensure security as
all MCUs have identical default certificates and keys.
To upload your own certificate and key, go to
. Note that you must upload a certificate and key simultaneously. After uploading a new certificate
and key, you must restart the MCU.
, complete the fields and click
If you have uploaded your own certificate and key, you can remove it later if necessary; to do this, click
.
The details of the business to which the certificate has been
issued:
: the country where the business is registered
: the state or province where the business is located
: the locality or city where the business is located
: the legal name of the business
: the organizational unit or department
: the common name for the certificate, or the
domain name
The details of the issuer of the certificate.
Where the certificate
has been self-issued,
these details will be the
same as for the Subject.
The date on which the certificate was issued.
The date on which the certificate will expire.
Whether the private key matches the certificate.
Your web browser uses
the SSL certificate's
public key to encrypt
the data that it sends
back to the MCU. The
private key is used by
the MCU to decrypt
that data. If the Private
key field says 'Key
matches certificate'
then the data is
securely encrypted in
both directions.
179
Download from Www.Somanuals.com. All Manuals Search And Download.
If your organization has bought a certificate, or you have your
own way of generating certificates, you can upload it. Browse
to find the certificate file.
Browse to find the private key file that accompanies your
certificate.
If your private key is stored in an encrypted format, you must
enter the password here so that you can upload the key to the
MCU.
You can upload a 'trust store' of certificates that the MCU will Note that uploading a
use to verify the identity of the other end of a TLS connection. new trust store
replaces the existing
store.
The trust store must be in '.pem' format.
Choose to what extent the MCU will verify the identity of the The trust store contains
far end for a connection:
: all outgoing connections are
'master' certificates that
can be used to verify
the identity of a
certificate presented by
the far end.
permitted to proceed, even if the far end does not
present a valid and trusted certificate.
: outgoing connections are
Outgoing connections
are connections such as
SIP calls which use
TLS.
only permitted if the far end has a certificate which is
trusted.
: outgoing
connections and incoming connections for SIP calls
using TLS must have a certificate which is trusted
otherwise the MCU will not allow the connection to
proceed.
180
Download from Www.Somanuals.com. All Manuals Search And Download.
Please refer to the following sections for details of where to get further help and for additional software license
information:
Software licenses
The Codian MCU firmware is Copyright © Codian 2003-2008 except where specifically mentioned below. All rights
reserved.
For further assistance and updates please visit the Codian web site: www.codian.com.
This product contains an authentication function which uses an encrypted digital signature and a public key
infrastructure. It is your responsibility to ensure that any import into or export from your territory and any use of the
product in your territory is in compliance with your local laws. This product may not be exported to any country
embargoed by the US or any member of the European Union without the prior written consent of Codian.
The Codian MCU includes software developed by the NetBSD Foundation, Inc. and its contributors (specifically the
NetBSD operating system), software developed by Spirit Corporation (specifically G.728 audio codec
implementation) , software developed by Tecgraf, PUC-Rio (specifically Lua), software developed by the Internet
Systems Consortium, Inc (specifically DHCP), and software developed by Polycom, Inc. (specifically Polycom®
Siren14™ audio codec).
This product can use HMAC-SHA1 to authenticate packets and AES to encrypt them.
The following copyright notices are reproduced here in order to comply with the terms of the respective licenses.
NetBSD
Spirit Corporation
AES
HMAC
SHA1
Lua
DHCP
Polycom Inc
Fraunhofer IIS
181
Download from Www.Somanuals.com. All Manuals Search And Download.
Copyright © 1999-2004 The NetBSD Foundation, Inc. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the
following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following
acknowledgement: This product includes software developed by the NetBSD Foundation, Inc. and its contributors.
4. Neither the name of The NetBSD Foundation nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
The Codian MCU includes software developed by the authors listed below. These notices are required to satisfy the
license terms of the software mentioned in this document. All product names mentioned herein are trademarks of
their respective owners.
The University of California, Berkeley and its contributors.
The University of California, Lawrence Berkeley Laboratory and its contributors.
The NetBSD Foundation, Inc. and its contributors.
Jonathan R. Stone, Manuel Bouyer, Charles M. Hannum, Christopher G. Demetriou, TooLs GmbH,
Terrence R. Lambert, Theo de Raadt, Christos Zoulas, Paul Kranenburg, Adam Glass, Winning Strategies,
Inc, Frank van der Linden, Jason R. Thorpe, Chris Provenzano.
Copyright © 1990-2007 Info-ZIP. All rights reserved.
For the purposes of this copyright and license, "Info-ZIP" is defined as the following set of individuals:
Mark Adler, John Bush, Karl Davis, Harald Denker, Jean-Michel Dubois, Jean-loup Gailly, Hunter Goatley, Ed
Gordon, Ian Gorman, Chris Herborth, Dirk Haase, Greg Hartwig, Robert Heath, Jonathan Hudson, Paul Kienitz,
David Kirschbaum, Johnny Lee, Onno van der Linden, Igor Mandrichenko, Steve P. Miller, Sergio Monesi, Keith
Owens, George Petrov, Greg Roelofs, Kai Uwe Rommel, Steve Salisbury, Dave Smith, Steven M. Schweda,
Christian Spieler, Cosmin Truta, Antoine Verheijen, Paul von Behren, Rich Wales, Mike White.
182
Download from Www.Somanuals.com. All Manuals Search And Download.
This software is provided "as is," without warranty of any kind, express or implied. In no event shall Info-ZIP or its
contributors be held liable for any direct, indirect, incidental, special or consequential damages arising out of the use
of or inability to use this software.
Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter
it and redistribute it freely, subject to the above disclaimer and the following restrictions:
1. Redistributions of source code (in whole or in part) must retain the above copyright notice, definition,
disclaimer, and this list of conditions.
2. Redistributions in binary form (compiled executables and libraries) must reproduce the above copyright
notice, definition, disclaimer, and this list of conditions in documentation and/or other materials provided
with the distribution. The sole exception to this condition is redistribution of a standard UnZipSFX binary
(including SFXWiz) as part of a self-extracting archive; that is permitted without inclusion of this license, as
long as the normal SFX banner has not been removed from the binary or disabled.
3. Altered versions--including, but not limited to, ports to new operating systems, existing ports with new
graphical interfaces, versions with modified or added functionality, and dynamic, shared, or static library
versions not from Info-ZIP--must be plainly marked as such and must not be misrepresented as being the
original source or, if binaries, compiled from the original source. Such altered versions also must not be
misrepresented as being Info-ZIP releases--including, but not limited to, labeling of the altered versions with
the names "Info-ZIP" (or any variation thereof, including, but not limited to, different capitalizations),
"Pocket UnZip," "WiZ" or "MacZip" without the explicit permission of Info-ZIP. Such altered versions are
further prohibited from misrepresentative use of the Zip-Bugs or Info-ZIP e-mail addresses or the Info-ZIP
URL(s), such as to imply Info-ZIP will provide support for the altered versions.
4. Info-ZIP retains the right to use the names "Info-ZIP," "Zip," "UnZip," "UnZipSFX," "WiZ," "Pocket
UnZip," "Pocket Zip," and "MacZip" for its own source and binary releases.
Codian software is based in part on the work of the Independent JPEG Group
The authors make NO WARRANTY or representation, either express or implied, with respect to this software, its
quality, accuracy, merchantability, or fitness for a particular purpose. This software is provided "AS IS", and you, its
user, assume the entire risk as to its quality and accuracy.
This software is copyright © 1991-1998, Thomas G. Lane. All Rights Reserved except as specified below.
Permission is hereby granted to use, copy, modify, and distribute this software (or portions thereof) for any purpose,
without fee, subject to these conditions:
1. If any part of the source code for this software is distributed, then this README file must be included, with
this copyright and no-warranty notice unaltered; and any additions, deletions, or changes to the original files
must be clearly indicated in accompanying documentation.
2. If only executable code is distributed, then the accompanying documentation must state that "this software is
based in part on the work of the Independent JPEG Group".
3. Permission for use of this software is granted only if the user accepts full responsibility for any undesirable
consequences; the authors accept NO LIABILITY for damages of any kind.
These conditions apply to any software derived from or based on the IJG code, not just to the unmodified library. If
you use our work, you ought to acknowledge us.
183
Download from Www.Somanuals.com. All Manuals Search And Download.
Permission is NOT granted for the use of any IJG author's name or company name in advertising or publicity relating
to this software or products derived from it. This software may be referred to only as "the Independent JPEG
Group's software".
We specifically permit and encourage the use of this software as the basis of commercial products, provided that all
warranty or liability claims are assumed by the product vendor.
Copyright (c) 1998-2007 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the
following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following
acknowledgment: This product includes software developed by the OpenSSL Project for use in the OpenSSL
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products
derived from this software without prior written permission. For written permission, please contact
5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their
names without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes
software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
===============================================================
=====
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes
software written by Tim Hudson (tjh@cryptsoft.com).
184
Download from Www.Somanuals.com. All Manuals Search And Download.
Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com) All rights reserved.
This package is an SSL implementation written by Eric Young (eay@cryptsoft.com). The implementation was
written so as to conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The
following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just
the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except
that the holder is Tim Hudson (tjh@cryptsoft.com).
Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package
is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be
in the form of a textual message at program startup or in documentation (online or textual) provided with the
package.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the
following conditions are met:
1. Redistributions of source code must retain the copyright notice, this list of conditions and the following
disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following
acknowledgement: "This product includes cryptographic software written by Eric Young
(eay@cryptsoft.com)" The word 'cryptographic' can be left out if the rouines from the library being used are
not cryptographic related :-).
4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application
code) you must include an acknowledgement: "This product includes software written by Tim Hudson
(tjh@cryptsoft.com)"
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The licence and distribution terms for any publically available version or derivative of this code cannot be changed.
i.e. this code cannot simply be copied and put under another distribution licence [including the GNU Public
Licence.]
185
Download from Www.Somanuals.com. All Manuals Search And Download.
Copyright © 1995-2003, SPIRIT
The Codian MCU includes a G.728 audio codec used under license from Spirit Corporation.
Copyright (c) 2001, Dr Brian Gladman, Worcester, UK.
All rights reserved.
The free distribution and use of this software in both source and binary form is allowed (with or without changes)
provided that:
1. distributions of this source code include the above copyright notice, this list of conditions and the following
disclaimer;
2. distributions in binary form include the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other associated materials;
3. the copyright holder's name is not used to endorse products built using this software without specific written
permission.
This software is provided 'as is' with no explicit or implied warranties in respect of its properties, including, but not
limited to, correctness and fitness for purpose.
Issue Date: 29/07/2002
Copyright (c) 2002, Dr Brian Gladman, Worcester, UK. All rights reserved.
The free distribution and use of this software in both source and binary form is allowed (with or without changes)
provided that:
1. distributions of this source code include the above copyright notice, this list of conditions and the following
disclaimer;
2. distributions in binary form include the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other associated materials;
3. the copyright holder's name is not used to endorse products built using this software without specific written
permission.
ALTERNATIVELY, provided that this notice is retained in full, this product may be distributed under the terms of
the GNU General Public License (GPL), in which case the provisions of the GPL apply INSTEAD OF those given
above.
186
Download from Www.Somanuals.com. All Manuals Search And Download.
This software is provided 'as is' with no explicit or implied warranties in respect of its properties, including, but not
limited to, correctness and/or fitness for purpose.
Issue Date: 26/08/2003
Copyright (c) 2002, Dr Brian Gladman, Worcester, UK. All rights reserved.
The free distribution and use of this software in both source and binary form is allowed (with or without changes)
provided that:
1. distributions of this source code include the above copyright notice, this list of conditions and the following
disclaimer;
2. distributions in binary form include the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other associated materials;
3. the copyright holder's name is not used to endorse products built using this software without specific written
permission.
ALTERNATIVELY, provided that this notice is retained in full, this product may be distributed under the terms of
the GNU General Public License (GPL), in which case the provisions of the GPL apply INSTEAD OF those given
above.
This software is provided 'as is' with no explicit or implied warranties in respect of its properties, including, but not
limited to, correctness and/or fitness for purpose.
Issue Date: 01/08/2005
Lua 5.0 license
Copyright © 2003-2004 Tecgraf, PUC-Rio.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit
persons to whom the Software is furnished to do so, subject to the following conditions:
1. The above copyright notice and this permission notice shall be included in all copies or substantial portions
of the Software.
187
Download from Www.Somanuals.com. All Manuals Search And Download.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH
THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Copyright © 2004 Internet Systems Consortium, Inc. ("ISC")
Copyright © 1995-2003 Internet Software Consortium.
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the
following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of ISC, ISC DHCP, nor the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY INTERNET SYSTEMS CONSORTIUM AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
IN NO EVENT SHALL ISC OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
The Polycom® Siren14™ audio coding technology, including patents relating to that technology, is licensed from
Polycom, Inc.
MPEG-4 AAC audio coding technology licensed by Fraunhofer IIS
188
Download from Www.Somanuals.com. All Manuals Search And Download.
|
Sharp Fax Machine UX 340L User Manual
Sonic Alert Clock Radio SBT600ss User Manual
Sony Camcorder Accessories 56 User Manual
Sony CRT Television PVM 20L1 User Manual
Sony Security Camera SNT EP154 User Manual
Southern Pride Smoker SPK 700 SL User Manual
Star Manufacturing Boiler 6115RCBD User Manual
StarTechcom Switch DS154 User Manual
Stoves Stove 82757004 User Manual
Sun Microsystems Switch MDS 9222i User Manual