SURF Communication Solutions Orion-MCU User Manual

Hide thumbs Also See for Orion-MCU:
Table of Contents

Advertisement

Quick Links

[Pick
SURF Motion Media Platform User Guide
the
date]
Orion-MCU™ User Manual
Version 2.1.1
Document Version: 2.1.1.13
November 2012
www.surf-com.com
a

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Orion-MCU and is the answer not in the manual?

Questions and answers

Summary of Contents for SURF Communication Solutions Orion-MCU

  • Page 1 [Pick SURF Motion Media Platform User Guide date] Orion-MCU™ User Manual Version 2.1.1 Document Version: 2.1.1.13 November 2012 www.surf-com.com...
  • Page 2 Copyright © 2005-2012, SURF Communication Solutions Ltd. This document contains confidential and proprietary information of SURF Communication Solutions Ltd., henceforth referred to as “SURF.” All rights reserved. No part of this documentation may be reproduced in any form or by any means or used to make any derivative work (such as translation, transformation, or adaptation) without written permission from SURF Communication Solutions.
  • Page 3: Table Of Contents

    Topologies .......................... 9 Topology 1 - Orion-MCU via SIP PBX .................. 9 Topology 2 - Orion-MCU via PBX and Direct Connectivity ..........10 Topology 3 - Direct Interaction with Orion-MCU ............. 11 Topology 4 - Connectivity with External Networks ............12 Topology 5 - NAT Traversal Capabilities with Orion-MCU ..........
  • Page 4 9.3.3 RTP Traffic Ports Range ..................50 NAT Traversal in Orion-MCU .................... 51 9.4.1 Near-End NAT Traversal ..................51 9.4.2 Orion-MCU Setting for Near-End NAT Traversal ........... 51 9.4.3 Far-End NAT Traversal ................... 52 Serial Connectivity ......................53 Appendix-A: Precautions & Safety ..................54 11.1 Rack Precautions.......................
  • Page 5 Orion-MCU™ User Manual v.2.1.1 11.3.2 General Safety Precautions ................... 55 Appendix-B- Rack Mounting ....................56 Appendix C- Technical Specification ................... 58...
  • Page 6: About This Manual

    Orion-MCU™ User Manual v.2.1.1 1. About This Manual This manual provides detailed guidance of the Orion-MCU. It includes a description of the product, its functionality, features, configuration, and operation. This document includes the following sections: Section 1: About This Manual –...
  • Page 7: Introduction

    Multiple Video Layout Options: 10 video dynamic layouts are available for equal-presence display and 5 for dominant-based display. The layouts are modified automatically, when a participant enters or leaves the conference.  VIP Participants: Orion-MCU allows VIP participants to join a conference without PIN code authentication.
  • Page 8 Orion-MCU™ User Manual v.2.1.1  Registration: Orion-MCU is provisioned for registration as a SIP endpoint in the network. An authentication option is provisioned for each registration process. SIP clients may register to Orion-MCU’s built-in SIP registrar.  NAT Traversal: Orion-MCU provides near-end and far-end NAT traversal enabling connectivity between entities (Orion-MCU / SIP clients) which are behind not-SIP-aware NATs and firewalls.
  • Page 9: Topologies

    All SIP endpoints at the enterprise register to the PBX. The PBX supports SIP Signaling The Orion-MCU registers as an extension or is configured as a trunk in the PBX. Orion-MCU provides Mixing/Bridging/Switching and signaling interoperability. Voice-only clients can also participate in a video conference, making it a mixed Voice/Video conference.
  • Page 10: Topology 2 - Orion-Mcu Via Pbx And Direct Connectivity

    SIP endpoints are registered to Orion-MCU internal SIP registrar or the PBX. The PBX supports SIP Signaling The Orion-MCU registers as an extension or is configured as a trunk in the PBX. SIP endpoints can call through the PBX, Orion-MCU registrar or directly to the Orion-MCU Orion-MCU provides Mixing/Bridging/Switching and signaling interoperability.
  • Page 11: Topology 3 - Direct Interaction With Orion-Mcu

    3 -3- Topology-3 - Direct Interaction with Orion-MCU Endpoints may be registered to Orion-MCU SIP registrar. SIP endpoints can call through the Orion-MCU registrar or directly to the Orion-MCU (without registration). Orion-MCU provides Mixing/Bridging/Switching and signaling interoperability. Voice-only endpoints can also participate in a video conference, making it a mixed Voice/Video conference.
  • Page 12: Topology 4 - Connectivity With External Networks

    All SIP Endpoints register to the PBX. The PBX supports SIP Signaling. The Orion-MCU registers as an extension or is configured as a trunk in the PBX. Endpoints can also connect via the external network. Orion-MCU provides Mixing/Bridging/Switching and signaling interoperability.
  • Page 13: Topology 5 - Nat Traversal Capabilities With Orion-Mcu

    3 -5: NAT Traversal Capabilities Endpoints can register to the Orion-MCU SIP registrar or to the PBX Remote office (LAN 1) can be connected to the Orion-MCU through the built-in NAT Traversal capabilities. Orion-MCU provides mixing/bridging/switching, signaling interoperability and NAT translation.
  • Page 14: Topology 6 - Connectivity With Remote Endpoints

    ‎ As shown below in Figure 3 -6, Orion-MCU is located behind a NAT, with a private IP address. The participants interact directly with the Orion-MCU, via SIP, to set and initiate a conferencing session. ‎ Figure 3 -6: Connectivity with Remote Endpoints...
  • Page 15: Physical Overview

    4 -1 shows the front view of Orion-MCU: Figure ‎ 4 -1- Front view of the Orion-MCU The Orion-MCU is available in 2 configurations, supporting both small and large enterprises: Orion-MCU 1286 – Orion-MCU 1286 is a small-to-medium enterprise based video/voice conferencing system.
  • Page 16: Control Panel Leds

    Power - Indicates power is being supplied to the system. This LED is illuminated when the system is operating. 4.2.3 I/O Ports Figure 4 -2 shows the I/O ports of Orion-MCU appear at the rear part of the chassis. ‎ Figure ‎ 4 -2- I/O ports...
  • Page 17: Getting Started

    2. Connect the Orion-MCU to the “LAN” port of your computer using a CAT-5/6 cable. 3. Connect the Power Cable first to the Orion-MCU and then to the power outlet. Press the power button located on the front panel of the Orion-MCU to turn on the power. (Boot time is approximately 5 minutes) Figure ‎...
  • Page 18 6. Click OK. The system reboots and the changes are applied. If DHCP was chosen, the simplest way to see the Orion-MCU IP Address is to connect a monitor and restart the machine. The IP Address will appear in the Login Screen at the end of the system load.
  • Page 19 Step 6: Connect to the Orion IP Address from your Network Restore the original network configuration on your computer, and connect the Orion-MCU to your network. Connect to the Orion-MCU Management GUI by entering the Orion-MCU’s IP address in a web browser. The Orion-MCU is now connected to your network...
  • Page 20: Administration And Configuration

    After setting up the system, and prior to conference-service creation, the system needs to be configured according to the steps described in this section. Login After entering the Orion-MCU’s IP address in your web browser, a login screen appears. Enter the default user name and password (admin, admin). Figure ‎ 6 -1- Login screen Note: It is recommended to change the default admin password, before starting to use the system.
  • Page 21: Main Menu

    Orion-MCU™ User Manual v.2.1.1 Main Menu The main menu appears when the user has logged in. The main menu is divided into two major categories: a) System Settings b) Conferences Prior to conference creation, system settings must be configured. Figure ‎ 6 -2- Main Menu...
  • Page 22: User Management

    Orion-MCU™ User Manual v.2.1.1 User Management User Management is the first category under System Settings, on the main screen. The User Management screen allows the administrator to create a new user, update existing user information, or remove a user from the system.
  • Page 23: Creating A New User

    Orion-MCU™ User Manual v.2.1.1 6.4.1 Creating a New User To create a new user: 1. In the System Settings/User Management window, click Create a new User The Create a new User window opens. Figure ‎ 6 -4- Create a New User Window 2.
  • Page 24: Deleting A User

    Orion-MCU™ User Manual v.2.1.1 6.4.3 Deleting a User To delete a user from the system:  In the System Settings/User Management window, click Delete in the Operations column of the user to be removed. System Parameter Settings Before creating a conference, the network and SIP parameters must be provisioned.
  • Page 25 Orion-MCU™ User Manual v.2.1.1 To configure network settings: 1. Select System Settings > Network Settings. 2. Click Edit . Network parameters become editable. Figure ‎ 6 -7- Editing the network settings Note: If the “DHCP” parameter is selected, then only the Hostname parameter can be edited.
  • Page 26 MAC Address MAC address Read only Hostname String The name of the Orion-MCU system in your network. It’s highly important to configure the hostname as defined in the DNS of the LAN or the WAN where the Orion-MCU is deployed. Orion-MCU is using the hostname value in SIP calls with emphsis on NAT Traversal scenarios.
  • Page 27: Configuring Sip Settings

    Orion-MCU™ User Manual v.2.1.1 6.5.2 Configuring SIP Settings SIP settings are configured in the SIP Configuration window. Figure ‎ 6 -9- SIP configuration To configure SIP Settings: 1. Select System Settings > SIP Configuration. 2. Click Edit . SIP settings become editable.
  • Page 28 States whether a proxy server is used. (Yes/No) Use Outgoing In case the Orion-MCU is behind NAT or configured with public IP Proxy Server and NAT traversal (Near or Far end) shall be done in the Orion- MCU Outgoing proxy should not be configured.
  • Page 29 The application restarts. Figure ‎ 6 -12- Restart after modifying SIP configuration 6.5.2.1 Viewing Active Registrations You can view all the active registrations to the Orion-MCU in the SIP Configuration window. To view active registrations:  Click the Registrations Table button.
  • Page 30: Configuring Access Numbers

    A single Orion-MCU supports multiple access numbers. The access numbers are provisioned via the Orion-MCU GUI, as shown in this section. If the number dialed by a participant does not match any of the provisioned access numbers (or conference numbers), the call is declined.
  • Page 31 Orion-MCU™ User Manual v.2.1.1  Normal: CIF (352X288)  High: VGA (640x480)  HD (1280x720) 5. Do one of the following:  To register the access number, continue with the next step.  To complete the configuration procedure, click Save 6.
  • Page 32: Date And Time

    5. To automatically adjust the time for daylight savings time, select Automatically adjust clock for Daylight savings Time. 6. To have an NTP server sync the Orion-MCU with other devices on the network, select a server from the NTP list.
  • Page 33: Maintenance

    Hardware Reset – Reboots hardware. This process is a longer process, taking around 3 minutes. It is recommended to log out and re-log into the system after a Hardware Reset.  Orion-MCU Shutdown – Enables graceful system shut-down. When shut-down, the server will completely power off ...
  • Page 34: Upgrade

    Orion-MCU™ User Manual v.2.1.1 2. Click on Start Diagnostic Trace 3. Enter the interval for information collection in the text-box. The allowed range is between “0” to “300” seconds. If “0” is entered, the system provides a file, which contains all the system logs. Otherwise the information saved includes more detailed information.
  • Page 35 Orion-MCU™ User Manual v.2.1.1 Figure ‎ 6 -21– Upgrade window 2. In URL, t ype the address of the Orion-MCU upgrade server : update.orionmcu.com. If DNS ‎ has not been configured (see “Network Settings” section 6 .5.1 above), please use its IP address: 23.23.229.203.
  • Page 36 Orion-MCU™ User Manual v.2.1.1 ‎ Figure 6 -23- Upgrade occurring 7. Did you select the Reboot option before the software download?  If YES, then the system reboots automatically.  If NO, then click the Reboot button which appears after the upgrade is complete.
  • Page 37: Conferences

    Orion-MCU™ User Manual v.2.1.1 7. Conferences After system parameters have been provisioned, conferences can be set up. Summary Select Conferences > Summary to view the list of the existing active conferences: Figure ‎ 7 -1- List of existing conferences To see the details of a conference: ...
  • Page 38: Conference Settings

    Orion-MCU™ User Manual v.2.1.1 Figure ‎ 7 -2- Conference details Click Leader Dashboard , to open the Leader Dashboard and manage a conference. Conference Settings The parameters of an existing conference can be viewed or modified and new conferences can be created.
  • Page 39: Creating A Conference

    Orion-MCU™ User Manual v.2.1.1 Figure ‎ 7 -3- Conference management screen Note: The three parameters displayed in the Media Type column are as follows:  Multimedia/Voice  Video Quality: Normal: Voice Only, CIF (352X288) / High: VGA (640x480) / HD: (1280x720) ...
  • Page 40: Other Conference Actions

    “Bandwidth Allocation” High parameter will be configured as “Medium”. If the bandwidth in the LAN or WAN, where the Orion-MCU in deployed, is low, please set the conference room’s “Bandwidth Allocation” parameter to “Low”. If there is no bandwidth restrictions, you may use “High” for enhanced video quality.
  • Page 41: Content Sharing

    Orion-MCU™ User Manual v.2.1.1 Parameter Values Remarks registrar. Authenticate? Yes/No If positive then the conference is registered with authentication. Username String If authentication chosen, a username needs to be entered. Password String If authentication chosen, password needs to be entered.
  • Page 42: Dialing Options

    Access Number – 500 Conference Number – 100 Participant PIN Code – 1 Orion-MCU Domain – Orion.com (Domain name or IP address). Participant is registered on PBX: Dial 500  Prompt “Please enter your conference number followed by Calling via access number to a the # key”...
  • Page 43 Orion-MCU™ User Manual v.2.1.1 Participant is not registered: Dial 500@Orion.com  Prompt “Please enter your conference number Calling via access number to a followed by the # key”  Dial 100  Prompt “Please enter the conference with PIN code conference PIN number followed by the # key”...
  • Page 44: Leader Dashboard

    Orion-MCU™ User Manual v.2.1.1 8. Leader Dashboard The Leader Dashboard provides the following capabilities:  Inviting participants to conference.  Modifying conference parameters.  Disconnecting participants from a conference. Leader Login The leader logs into the Leader Dashboard by using the conference number as username and the leader PIN code as password, as shown below in Figure ‎...
  • Page 45: Main Screen

    Orion-MCU™ User Manual v.2.1.1 Main Screen On the main screen of the Leader Dashboard, the meeting information, conference participants list and the parameters for each participant are displayed: Figure ‎ 8 -2- Leader Dashboard main screen The icons displayed on the Leader Dashboard are as follows:...
  • Page 46: Leader's Capabilities

    Orion-MCU™ User Manual v.2.1.1 Figure ‎ 8 -3- Call statistics Leader’s Capabilities The leader can take the following actions:  Invite a participant to join the conference  Modify the status of the participant from dominant to non dominant and vice versa ...
  • Page 47: Modifying The Conference Layout Mode

    Orion-MCU™ User Manual v.2.1.1  name@PBX-IP-Address - If the participant is not a registered participant. For example: 3. Click to add more participants and then click Invite. Click to cancel the invitation. Modifying the Conference Layout Mode To set the conference layout mode, click the Layout tab on the main leader dashboard. The following screen opens, showing the current and the possible layouts: Figure ‎...
  • Page 48: Firewall And Nat

    9.2.1 Orion-MCU in a DMZ When Orion-MCU is located in the DMZ, it allows you to assign to it a public or private IP address. This enables an easy access and direct connectivity with video clients in the public ‎...
  • Page 49: Orion-Mcu Behind A Nat

    Orion-MCU behind a NAT When Orion-MCU system is located behind a NAT, in a private LAN, it is not accessed directly by the other entities in the internet. This causes a better security in one hand and on the other hand it makes the connectivity with outside world more complicated.
  • Page 50: Enabling Sip Sessions

    RTP Traffic Ports Range The range of the UDP ports for the incoming and outgoing RTP packets need to remain open in the firewall/NAT. Orion-MCU communicates through ports in the range 10000-20000, for video, voice and content sharing. The actual range can be restricted within the default one, depending on number of conferences,...
  • Page 51: Nat Traversal In Orion-Mcu

    9.4.1 Near-End NAT Traversal In a deployment scenario where Orion-MCU is located behind a firewall and is configured with private IP address, the signaling sent from the Orion-MCU messeges will contain private IP addresses. Unless the firewall provides VoIP NAT Traversal services, sessions will not connect, as the singling messeges will contain non-routable addresses.
  • Page 52: Far-End Nat Traversal

    6. Near-end NAT traversal is applied. 9.4.3 Far-End NAT Traversal When the SIP client is behind a firewall, Orion-MCU may receive private IP addresses in the ‎ received SDP (for sending the session’s RTP packets) as shown below in Figure 9 -4: ‎...
  • Page 53: Serial Connectivity

    I/O port for a basic troubleshooting. Follow these steps to enable serial communication. Step 1: Physical Connectivity Connect the serial port of your laptop to the Orion-MCU serial port. If no serial I/O port is available on your computer, use a USB adaptor. Step 2: Login Use any Telnet software, for example “PuTTy”, to reach the login prompt of the system:...
  • Page 54: Appendix-A: Precautions & Safety

    Install the heaviest server components at the bottom of the rack first, and then work up.  Use a regulating, uninterruptible power supply (UPS) to protect the Orion-MCU from power surges, voltage spikes and to keep your system operating in case of a power failure.
  • Page 55: General Safety Precautions

    Orion-MCU™ User Manual v.2.1.1  Use only one hand when working with powered-on electrical equipment. This is to avoid making a complete circuit, which will cause electrical shock. Use extreme caution when using metal tools, which can easily damage any electrical components or circuit boards they come into contact with.
  • Page 56: Appendix-B- Rack Mounting

    (i.e. the use of power strips, etc.). Rack Mounting Instructions This section provides information about installing the Orion-MCU into a rack unit. There are a variety of rack units on the market, which may mean the assembly procedure will differ slightly.
  • Page 57 3. Insert the mounting screws into the thru holes in the front of the chassis and through the thru holes in the rack ‎ ‎ Figure 1 2-1- Installing Orion-MCU into a Rack Figure 1 2-2- Installing Orion-MCU into a Telco Rack...
  • Page 58: Appendix C- Technical Specification

    Orion-MCU™ User Manual 13. Appendix C- Technical Specification Dimensions: 9 x 7.5 in (229 x 191 mm) Chassis: 1U Rackmountable Weight: Gross Weight: 10 lbs. (4.5 kg.) System Input Requirements AC Input Voltage: 100-240 VAC (auto-range) Rated Input Current: 3A max.

Table of Contents