Codian MCU MSE 8510 Getting started
Codian MCU MSE 8510 Getting started
Copyright © Codian 2008. All rights reserved. This Getting Started Guide may not be copied, photocopied, translated, reproduced, or converted into any electronic or machine-readable form in whole or in part without prior written approval of Codian Limited. 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.
Table of contents General information ................................................................................................................ 1 About the MSE 8510 Media2 blade ...................................................................... 1 Port and LED location ................................................................................................ 1 LED behavior ................................................................................................................
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.
LED behavior Table 1 describes the behavior of the LEDs.
Installing the Media2 blade 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.
2 3 4 5 iii Slide out the blade or blanking blade. Open 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. Slide the Media2 blade into the blade slot (as shown in Figure 2) until it stops. Simultaneously 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. Using a No.
Installing the Media2 blade Figure 3: Closing the retaining latches on the front of a 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. i Ethernet Ports B, C and D may not be supported in the software supplied with your blade.
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. i Both ends of the Ethernet connection must be configured in the same way.
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: 1 2 3 Log in to the Supervisor’s web interface. Go to Hardware > Blades and click the IP address of the Media2 blade. Click Log in, and then click Change log in and enter the user name admin with no password.
To configure the Media2 blade to use a SIP registrar: 1 2 3 In the web interface, go to Settings > SIP. Configure the settings you require, using the online help for further assistance. Click Apply changes. i Before you configure the Media2 blade to use, and register conferences to, a SIP registrar, you must set up the Media2 blade and its conferences on that SIP registrar.
Using the Media2 blade Using the Media2 blade Creating conferences To create a conference: 1 2 3 In the web interface of the Media2 blade, go to Conferences and click Add new conference. Type a Name for the conference, for example SalesMeeting. Type an optional numeric identifier, for example 123. This will be the telephone number that participants can use to join the conference when calling in to the Media2 blade via a gatekeeper or SIP registrar. i 4 5 6 If you are using a gatekeeper, check H.
Calling participants in to a conference To call participants in to a conference: 1 2 3 4 5 In the web interface of the Media2 blade, go to Conferences and click on the name of an active conference. On the Participants tab, click Add participant to call out to an H.323 or SIP endpoint. In 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.
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. i Note that to use the ‘chat’ facility when streaming a conference, your Media2 blade needs the web conferencing feature key. For more information, refer to your reseller.
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.
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 Errors, warnings and information. For more information about 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.
61-0021-01
