Codian Limited reserves the right to revise this documentation and to make changes
in content from time to time without obligation on the part of Codian Limited to
provide notification of such revision or change.
Codian Limited provides this documentation without warranty, term, or condition
of any kind, either implied or expressed, including, but not limited to, the implied
warranties, terms or conditions of merchantability, satisfactory quality, and fitness
for a particular purpose. Codian Limited may make improvements or changes to the
product(s) and/or the program(s) described in this documentation at any time.
All other product and company names herein may be trademarks of their respective
owners.
61-0021-01 rev 01
Checking for updates ............................................................................................................12
Troubleshooting and technical support information ...............................................13
Using the event log to help solve a problem ..................................................13
Getting more help ....................................................................................................13
General information
General information
About the MSE 8510 Media2 blade
The MSE 8510 Media2 blade is a technologically advanced media processor that fits
into an MSE 8000 chassis. It can be used as a Multipoint Control Unit (MCU)
combining continuous presence high definition video conferencing and the highest
possible voice quality.
Port and LED location
Figure 1 shows the position of ports and LEDs on the Media2 blade.
Figure 1: Media2 blade front panel
USB Port
& Activity LEDs
Admin Port
Console Port
& Activity LEDs
Alarm LED
Ethernet Ports & Status LEDs
LCD Display
Power LED
Status LED
1
LED behavior
Table 1 describes the behavior of the LEDs.
Table 1: Media2 blade LED behavior
LED ColorIndicates
USB Port Activity GreenReserved for future expansion
Admin Port ActivityGreenReserved for future expansion
StatusGreenThe Media2 blade is operating normally
AlarmRedThe Media2 blade is booting or has
developed a fault, for example:
temperature is outside normal limits
battery failure of the internal clock
Refer to the web interface for more
information about the problem (go to
Status > Health)
Ethernet Port Status, for each
Ethernet port and Admin port:
FDXGreenThe link has been negotiated as a full-
duplex link
ActGreenPackets are being transmitted on this port
LinkGreenThe speed of the link from this port,
which is either 10, 100, or 1000 Mbps
PowerBlueThe Media2 blade is receiving power from
the MSE 8000 chassis
2
Installing the Media2 blade
Important: Before installing the Media2 blade into the MSE 8000, you
must read the safety information for the MSE 8000 chassis at:
http://www.codian.com/safety.htm
Although blades are hot-swappable parts, you must only remove one
!
blade at any time. Remove the power from the MSE 8000, if you need to
remove more than one blade at a time.
Before hot-swapping a blade, shut down the blade using the web interface.
!
Do not shut down a blade during a software upgrade or if the blade is
processing (for example if a conference is taking place on a Media blade).
The MSE8000 backplane uses high performance data connectors. Do not
!
remove Media2 blades unless necessary because doing so may reduce the
life of these connectors.
Make sure that you have the correct power requirements and sufficient
!
power in your PSU; for information on powering the MSE 8000 refer to
the Getting Started Guide that accompanied the chassis.
Installing the Media2 blade
Step one: Install the Media2 blade into the MSE 8000 chassis
You must install either a blade or a blanking blade in each of the ten
!
positions in the chassis.
The Supervisor blade must be installed into slot 1 of the MSE 8000
!
chassis.
1Remove the blade or blanking blade from the slot into which you are going to
install the Media2 blade:
iUsing a No.1 Phillips screwdriver, loosen the screws in the retaining latches
with an anti-clockwise quarter turn.
iiOpen both retaining latches on the front of the blade or blanking blade.
When open, a retaining latch is at a 90
the blade.
° angle perpendicular to the front of
3
iiiSlide out the blade or blanking blade.
2Open both retaining latches on the front of the Media2 blade. When open, a
retaining latch is at a 90
° angle perpendicular to the front of the blade.
3Slide the Media2 blade into the blade slot (as shown in Figure 2) until it stops.
4Simultaneously close both retaining latches on the blade (thereby engaging the
connectors at the rear of the blade) to secure in the chassis as shown in Figure 3.
5Using a No.1 Phillips screwdriver, tighten the screws in the retaining latches
with a clockwise quarter turn.
The power is connected automatically as soon as you close the latches. The LCD
panel displays messages as parts are checked and eventually you see "Waiting for
application to boot" after which the Codian logo appears.
Figure 2: Inserting a blade into the chassis
4
Figure 3: Closing the retaining latches on the front of a blade
Installing the Media2 blade
Step two: Connect to Ethernet Port A
Connect an Ethernet cable from Ethernet Port A to an Ethernet switch (rather than a
hub, to minimize interference from other devices on the network). The Ethernet
port is a 10/100/1000 Mbps auto-sensing connection.
Ethernet Ports B, C and D may not be supported in the software supplied
i
with your blade. Do not connect to these ports unless the web interface
allows you to configure them. Do not connect multiple ports to the same
subnet unless instructed to do so by the web interface.
5
Initial configuration
Step one: Configure Ethernet Port A settings
The default setting for the Media2 blade Ethernet ports is auto-sensing mode. If the
switch ports to which you connect the Media2 blade are not also set to auto-sensing
mode, then you need to configure the Media2 blade Ethernet ports to use the same
speed and duplex mode.
Both ends of the Ethernet connection must be configured in the same
i
way. For example, either configure both ends of the link to be autosensing or configure both ends to operate at the same speed and duplex.
To establish a 1000Mbps connection, both ends of the link must be
i
configured as auto-sensing.
To configure Ethernet Port A, log in to the Supervisor’s web interface and go to
Hardware > Blades. For more information about configuring the port, refer to the
online help accessible from the Supervisor’s web interface.
Step two: Assign an IP address to the Media2 blade
You can use the Supervisor’s web interface to configure the IP addresses of all blades
installed in the MSE 8000. Note that all blades are supplied with DHCP enabled and
therefore the Media blade will attempt to find an IP address. The LCD panel will
show the IP address allocated. You can either keep this setting or assign static IP
addresses to a blade from the Supervisor’s web interface. To view or configure the IP
address of the Media2 blade, log in to the Supervisor and go to
To access the web interface of the Media2 blade, go to
the IP address of that blade.
Hardware > Blades and click
Hardware > Blades.
6
Configuring the Media2 blade
Configuring the Media2 blade
Step one: Log in to the Media2 blade
All administration of the Media2 blade is performed via the web interface.
To log in to the web interface of the Media2 blade:
1Log in to the Supervisor’s web interface.
2Go to
3Click
Step two: Allocate port licences
Port licenses must be assigned to the Media2 blade from the Supervisor's Port
licenses
conferencing, each port requires more than one port license. Use the online help for
assistance.
Hardware > Blades and click the IP address of the Media2 blade.
Log in, and then click Change log in and enter the user name admin with
no password.
Codian recommends that you change the admin account to use a
i
password as soon as possible. To do that, go to
Users, click the admin
link, and provide the required user information.
page: where the MSE 8510 Media2 blade is supporting high definition
Step three: Using an H.323 gatekeeper or SIP registrar
(optional)
If you have H.323 endpoints, using an H.323 gatekeeper can make it easier for
participants to call in to a conference. You can configure the Media2 blade to use an
external gatekeeper or its own built-in gatekeeper. For information about using the
built-in gatekeeper, refer to the online help.
If you have SIP endpoints, using a SIP registrar can make it easier for participants to
call in to a conference.
To configure the Media2 blade to use an H.323 gatekeeper:
1In the web interface of the Media2 blade, go to
2Enable
H.323 gatekeeper usage and configure the settings you require, using
the online help for further assistance.
3Click
Apply changes.
Settings > Gatekeeper.
7
To configure the Media2 blade to use a SIP registrar:
1In the web interface, go to
Settings > SIP.
2Configure the settings you require, using the online help for further assistance.
3Click
Apply changes.
Before you configure the Media2 blade to use, and register conferences
i
to, a SIP registrar, you must set up the Media2 blade and its conferences
on that SIP registrar.
Step four: Add endpoints (optional)
One way to add participants to a conference that you create is to have the Media2
blade automatically call them when the conference starts. To do this, you configure
their endpoints on the Media2 blade. When you set up a conference, you can choose
the endpoints from the
each endpoint’s details every time. Participants that are pre-configured for a
conference will automatically be called by the Media2 blade to join that conference.
To define pre-configured endpoints:
1In the web interface of the Media2 blade, go to
To add a H.323 endpoint, click Add H.323To add a SIP endpoint, click Add SIPTo add a VNC screen, click Add VNC
2Configure the endpoint settings you require, using the online help for further
assistance.
3Click
Add endpoint.
Pre-configured participants list. This is easier than entering
Endpoints:
8
Using the Media2 blade
Using the Media2 blade
Creating conferences
To create a conference:
1In the web interface of the Media2 blade, go to
conference
2Type a
.
Name for the conference, for example SalesMeeting.
3Type an optional numeric identifier, for example
telephone number that participants can use to join the conference when calling
in to the Media2 blade via a gatekeeper or SIP registrar.
There are two types of conference participant: chairperson and guest.
i
IDs and PINs allow participants to connect to conferences as the correct
participant type. Chairperson participants use the Numeric ID and
optionally, the PIN; guest participants use the Guest numeric ID and
optionally, the Guest PIN. For more information, refer to the online help.
Conferences and click Add new
123. This will be the
4If you are using a gatekeeper, check
registrar, check
5Ensure the
SIP registrar.
Maximum duration of the conference is sufficient (the default is one
H.323 gatekeeper; if you are using a SIP
hour).
6All other values can be left at their default settings. Refer to the online help for
further information about the available settings.
Note that if you do not configure the conference to start immediately, it
i
will become a scheduled conference and will be inactive until its start
time.
7Scroll down and click
Add conference.
The conference you have created is now active (if you used the default immediate
start time) and participants can join in one of two ways: either the Media2 blade can
call out to specified endpoints or endpoints can dial in. Any endpoints that have been
added to a conference, as pre-configured participants, will be called in to the
conference by the Media2 blade.
9
Calling participants in to a conference
To call participants in to a conference:
1In the web interface of the Media2 blade, go to
Conferences and click on the
name of an active conference.
2On the
Participants tab, click Add participant to call out to an H.323 or SIP
endpoint.
3In the
Address field:
where there is no H.323 gatekeeper or SIP registrar, type the IP address,
host name, or SIP URI of an accessible endpoint on your network
if you are using an H.323 gatekeeper, enter the number registered with the
gatekeeper for the required endpoint
if you are using a SIP registrar, enter the number registered with the SIP
registrar for the required endpoint
4Leave the other fields as their default values and click
Call endpoint. The
Media2 blade automatically connects to the endpoint.
5If the endpoint is not configured to automatically answer calls, accept the call on
the endpoint.
Calling in to a conference
Participants can call in to conferences in either one of two ways:
if you have given the conference a numeric identifier and you are using an H.323
gatekeeper or SIP registrar, tell participants to dial the numeric identifier from
their endpoint to join that conference
participants can dial the IP address of the Media2 blade to access the auto
attendant of the Media2 blade. Participants will see a menu of available
conferences on their video screen and will hear instructions
10
Using the Media2 blade
Streaming conferences
Streaming is a way of viewing a conference in a standard web browser. The Media2
blade allows streaming of video and, if enabled for a conference, the streaming of
data. You can also conduct a text ‘chat’ and add notes and drawings to the data
stream.
Note that to use the ‘chat’ facility when streaming a conference, your
i
Media2 blade needs the web conferencing feature key. For more
information, refer to your reseller.
You can configure two streaming options on the Media2 blade that will be available
for users to choose between when streaming conferences. For each streaming
option, you must choose a media player (QuickTime, RealPlayer, or Windows Media
Player) and a bit rate.
To configure streaming options:
1In the web interface of the Media2 blade, go to
2Configure the streaming options you require, referring to the online help for
more details about options.
3Click
Apply changes.
Streaming users will need to have installed one of the media players that you have
chosen for the two streaming options. Streaming users might also need to install Java
(from www.java.com).
To stream a conference:
1In a web browser, go to the IP address of the Media2 blade (or if you are already
logged in, go to
2Type in a
and the
3Click
Stream this conference and streaming will start.
Conference ID (the numeric identifier of the conference).
Home and click Streaming-only interface).
Sign-in name (the name by which you will be identified if you ‘chat’)
Settings > Streaming.
11
Instructing conference participants
You need to tell conference participants how to join conferences. You can also tell
them how to use the Far-End Camera Controls (FECC) to navigate menus in the auto
attendant and choose conference layouts. There is a document: Getting Started: Accessing Conferences available in the documentation area of the web site, which you
can print out and give to conference participants.
Checking for updates
It is a good idea to regularly check for updates to the main Media2 blade software
image. This section describes how to upgrade the Media2 blade using the web. Note
that you can also upgrade the Media2 blade using FTP; this can be more reliable if
you are upgrading the device remotely. Upgrading your device via FTP is described
in the release notes that are available alongside the software images in the support
section of the web site.
To check for, and download, updates:
1Log in to the Media2 blade web interface and go to
2Make a note of the software version that is currently installed.
3Go to the support section of the web site and check if a more recent release is
available for the Media2 blade.
4If a more recent release is available, download it and save it locally.
To upgrade the Media2 blade:
1Unzip the software release file that you downloaded.
2In the Media2 blade web interface, go to
3In the
4Click
Main software image section, click Browse and locate the unzipped file.
Upload software image. The browser begins uploading the file to the
Settings > Upgrade.
Media2 blade, and a new browser window opens to indicate the progress of the
upload.
When finished, the browser window refreshes and indicates that the software
upgrade is complete.
5Go to
Settings > Shutdown to shut down and restart the Media2 blade.
Status > General.
12
Note that shutting down the Media2 blade will disconnect all
i
participants.
Troubleshooting and technical support information
Troubleshooting and technical support information
Using the event log to help solve a problem
Unless you are experiencing a problem, all event logging sources should be set to the
default, which is
configuring the event log, refer to the online help accessible from the web interface.
You can use the event log to produce debugging information to assist technical
support in solving your problem. However, we recommend that you only alter the
setting of the event log under the guidance of technical support. In particular, you
should not turn on event logging sources without good cause or advice from
technical support.
Getting more help
If the documentation does not answer your question or you have a problem with one
of our products:
1Refer to the Technical FAQ section of the web site. We keep the Technical FAQ
section up to date with the latest information from our technical support team
regarding the resolution of customer issues.
2Contact your reseller. Our resellers have a wealth of experience with our
products and this is often a quick way of solving a problem.
3If your query remains unsolved, there is a web form in the support area of the
web site that you can complete. Ensure that you provide all the details requested
by the form to assist the technical support team in resolving your problem:
the serial number and product model number (for example: MSE8510) of
the MSE blade
the software build number (to find this, in the web interface, go to Status >
General
where you purchased the MSE bladeyour contact email address or telephone number
Errors, warnings and information. For more information about
)
13
61-0021-01
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.