RMX 2000 Presales Tech Training

RMX 2000 Real-Time Media Conferencing Platform
Pre-Sales Technical Training Course
Advanced Open IP Platform. Simple and Accessible. Ultimate User Experience.

POLYCOM CONFIDENTIAL
Course Objectives
Upon completion of this course the student will able to:
Identify the RMX 2000 key hardware components and functions Identify and clarify the RMX 2000 systems primary features Discuss the first time installation and configuration three key procedures for the RMX 2000 Recall the default conference settings for the RMX 2000 Recall the most common operations performed via the RMX Web Client Identify the five panes associated with the RMX Web Client Discuss the login levels and viewing permissions for the Chairperson, Operator or Administrator State the ways to start a conference using the RMX 2000 Understand how to enable personal layout control with Click&View
RMX 2000 Agenda

Lesson 1: Hardware and System Overview Lesson 2: First Time Installation and Configuration Lesson 3: Basic Operation Lesson 4: Administration (Optional) Lesson 5: Interoperability and System Limitations (Optional) Lesson 6: Summary and Closing Lesson 7: Pre-Sales Technical Assessment*
* Disclaimer: The on-line assessment is required to complete the learning experience and to obtain credit for the Polycom RMX 2000 Pre-Sales Technical Training course!
Lesson 1: Hardware and System Overview

Lesson 1 Learning Objectives

Upon completion of this lesson the student will able to:
Identify the RMX 2000 key hardware components and functions
Management Server (CNTL), Media Processing Modules (MPM) and the Hardware Management Module and IP switching (RTM IP), Power Supplies and Fan Drawers, and internal board LEDs Define the RMX front panel controls and indicators
Identify and clarify the RMX 2000 systems primary features Explain the RMX Advanced Telecom Computing Architecture (ATCA) system architecture
RMX 2000 What is it?

Next Generation Media Server What is a media server?
Scaleable multimedia IP packet processing platform Media processing engine to be controlled by an application server
What makes the RMX 2000 different?

Most media servers are generic processing engines RMX 2000 is optimized for audio and video processing
First application running on RMX2000 is multipoint IP Video and VoIP

RMX Hardware Overview

3U High 19 rack-mountable Input Voltage: 100 - 220v Media Processing Module (MPM) X 2 CPU (CNTL) management server Optional IAM on-board SE200 application server RTM IP HW management module (Shelf Management) and IP switching Power supply and Fan drawers
RMX 2000 ATCA Design
Carrier-grade platform delivers performance, reliability & serviceability Future-focused high BW IP platform for compute intensive apps Ultra high-speed internal and external connectivity Front loading, hot swappable, self configuring modules On board shelf management automates system monitoring and fault resolution
What is ATCA?
Advanced Telecom Computing Architecture (ATCA)
"Advanced Telecom Computing Architecture, or AdvancedTCA is a series of industry standard specifications for the next generation of carrier grade communications equipment. AdvancedTCA incorporates the latest trends in high speed interconnect technologies, next generation processors, and improved reliability, manageability and serviceability, resulting in a new blade (board) and chassis (shelf) form factor optimized for communications." [Intel] With the significant and steady growth of the use of VoIP, ATCA is expected to encompass the multi-billion dollar market by 2009. All major telecom industry hardware manufacturers and providers have incorporated ATCA into their products and product lines.
RMX 2000 ATCA Design

LAN Connectors and Indications
Gigabit Ethernet
LAN ShM
IP Backplane
HW management and diagnostics is available even when the control board is down
FRUs: MPM, CNTL/ IAM, RTM IP, Power Supply Drawer, and Fan Drawer.
MPM
MPM
CNTL
IAM
Active BP Fabric Network
RMX 2000 RTM IP Board
USB Key contains a text file (lan.cfg) holding the factory default IP address parameters
Shelf Management
Monitors, controls, and assures proper operation of Boards, Fans, Power Supply, and the IP backplane Watches over the basic health of the system, reports anomalies, and takes corrective action when needed Retrieves inventory information and sensor readings as well as receive event reports and failure notifications from Boards and other Field Replaceable Units (FAN and Power Supply) Performs basic recovery operations such as power cycle or reset of managed entities
RTM - IP
Network
Gigabit Ethernet (Four Indications pairs (Link/1Gb) for MPM and CPU) High Speed Fabric I/F
Shelf Manager and IPMI controller

Fan controller Power supply controls Memory (System relevant information) Real Time Clock (RTC) Fast Ethernet I/F
12V Power for CPU cards, RTM IP and FANS

Media Processing Module (MPM)

26 TI DM642 720MHz DSP Linux-based Operating System The two MPMs are connected via a fast Fabric network to share uncompressed media Roles
Audio + RTP processing Video Processing
Control Board
Pentium M 1.4GHz with 512MB RAM 1GB Compact flash 60 GB Hard disk Linux OS SW is stored on the flash disk Hard Disk for log files and Call Detail Report (CDR)
Power Supply
Consist of two 48V 300W power supply Total 600W Load sharing Wide range input 90 to 264 V AC Power fail indication to the Shelf Management Power status indication on the fans drawer, bi-color led Thermal auto shut down
Sensors
Card Temperature Voltage Battery MPM CNTL RTM-IP # of Temp Sensors 2 2 3
Each sensor has the following range

Normal Major Critical
RTM IP Board LEDs

ERR Red indication for a major error ACT Amber indication for activity RDY Green indication, the board is ready to work HS Blue indication, the board is ready to be pulled out safely HD Red, hard disk activity (CNTL and IAM)
Multipoint Video Conferencing using an Polycom RMX 2000
RMX 2000 Main Features

Video Display
Dynamic Continuous Presence 24 Video Layouts
RMX 2000 Main Features (Cont.)

Standard Definition (SD) 256Kbps to 2Mbps
SD15 SD resolution at 15 fps SD30 SD resolution at 30 fps Video resolutions is also defined by the Quality settings:
Motion and Sharpness The combination of frame rate and resolution affects the number of ports required on the MCU to support the call.
High Definition (HD) 384Kbps to 4Mbps

HD resolution forces all conference participants to connect using the same conference line rate and HD capabilities
Multiple Switching Modes

Voice, User Forced, Lecture Mode, and Presentation Mode
H.239 / People+Content Media Encryption based on AES 128 Media Encryption and DH 1024 Key Exchange standards IVR-Enabled Conferencing Entry Queue

Conferencing Capabilities and Options
On Demand Conferencing
New Conference setup once, use once. The conference is deleted from the MCU after it ends. Meeting Rooms setup once, use many times. Meeting Rooms are saved in memory (using no resources) and can be activated as many times as needed. Ad Hoc Entry Queue no setup, a new conference is created when a user dials in.
Connection Methods
Dial-out: automatically, to pre-defined participants (line rate detection is automatic) Dial-in:
for participants defined in advance for undefined participants directly to a conference for undefined participants via a single dial Entry Queue

Conference Management and Monitoring Features: Lecture Mode or Presentation Mode in Continuous Presence conferences Far End Camera Control (FECC/LSD) in video conferences Automatic termination of idle (no participants) conferences Automatic extension of conference duration Control of listening and broadcasting audio volume for individual participants Auto Gain Control (AGC) noise and audio volume regulation for individual participants Conference control via DTMF codes from participants endpoint or telephone Entry, exit and end-of-conference indications Media encryption Active display of all conferences and participants Real-time monitoring of each participants connection status and properties Multiple drag & drop of participants Easily accessed Call Detail Records (CDR) for administrator Active display of all system resources
Lesson 2: First Time Installation and Configuration


Discuss the first time installation and configuration three key procedures for the RMX 2000
Hardware Installation and Setup Gather Network Equipment and Address Information First Entry Configuration
Recall the default conference settings for the RMX 2000

Meeting Rooms Conference Profile IVR Service Entry Queue Entry Queue Service
State where to go for additional help in configuring the RMX 2000
First Time Installation and Configuration

Hardware Installation and Setup
Mount the RMX in a rack using rack brackets or a shelf Connect the LAN cable into LAN port 2 and the power cable
Gather Network Equipment and Address Information

Get the information needed for integrating the RMX into the local network
Control Unit IP Address: 192.168.1.254 default Control Unit Subnet Mask: 255.255.255.0 Control Unit Gateway: 192.168.1.1 default Shelf Management IP Address: 192.168.1.252
First Entry Configuration

1. 2. 3. 4.
Register the RMX by obtaining a Product Activation Key Modify the factory default Management Network settings Edit the lan.cfg file on the USB key using a text editor program First-time Power-up and connection to MCU Configure the Default IP Service settings via the Fast Configuration Wizard
Fast Configuration Wizard

The Fast Configuration Wizard starts automatically whenever one or both of the following conditions occurs:
The RMX cannot access the Default IP Service. This happens during First Time Power-up, before the service has been defined. The Default IP Service has been deleted, followed by an RMX reset.
Successful Configuration for the RMX 2000

Success Message
Confirmation of Reset
System Reset
Default Conference Settings

Entity Description Conferences saved on the MCU without using resources. They are activated when the first participant dials in. All Meeting Rooms are based on a Profile. The maximum number of Meeting Rooms that can be stored in the MCU memory is 200. There are four Meeting Rooms ready for use: Name ID: Maple_Room 1001 Oak_Room 1002 Juniper_Room 1003 Fig_Room 1004 Each Meeting Room uses the default Conference Profile called DefaultVideo384 running at 384Kbps and has a default duration of one hour.
Meeting Rooms
Conference Profile
Name: DefaultVideo384 A Conference Profile is assigned to a Meeting Room to define its conferencing properties. The DefaultVideo384 Profile contains the video conference parameters with a bit rate of 384Kbps, Auto Layout and Polycom Skin. The Profile uses an IVR Service called Conference IVR Service.
IVR Service
Name: Conference IVR Service The Conference IVR Service contains a set of voice prompts in English that automates the participants connection to a conference. The IVR Service includes all the voice messages played during the participant connection process and during the conference.
Default Conferencing Settings (Cont.)

Entity Description
Entry Queue
Name: DefaultEQ 1000 A single dial Routing Lobby for all conferences (optional). A default Entry Queue called DefaultEQ is provided for routing calls from undefined participants to conferences. It uses Entry Queue IVR Service called RMX EQ Service.
Entry Queue Service
Name: Entry Queue IVR Service Includes all the voice messages and video slides used to guide participants though their connection process and route them to their destination conference. Entry Queue IVR Service is the default IVR Service provided for the default Entry Queue. The Entry Queue is also set to Ad Hoc conferencing which allows participants to start new conferences without prior definition by entering a Conference ID that is not used by any on going conference currently running on the MCU, or Meeting Room. The default Welcome Slide displayed at the participants endpoint lists the default Meeting Rooms. The participant can select on of these Meeting Rooms or enter another ID to start a new conference.
Customizing the Default Conferencing Settings

To customize the Voice Prompts and Video Slides To modify the conference bit rate To allow participants to connect to a single dial Entry Queue You can personalize Meeting Rooms You can create your own Address Book
For more information and details on these customized RMX default conferencing settings, please refer to the RMX 2000 Administrators Guide.
Lesson 3: Basic Operation


Recall the most common operations performed via the RMX Web Client
Starting, monitoring and managing conferences Monitoring and managing participants and endpoints as individuals or groups
Identify the five panes associated with the RMX Web Client
Conference List , List Pane, RMX Management, Status Bar, and Address Book
Discuss the login levels and viewing permissions for the Chairperson, Operator or Administrator State the ways to start a conference using the RMX 2000
Clicking the New Conference button Dial in to a Meeting Room Dial in to a Ad Hoc Entry Queue
Understand how to enable personal layout control with Click&View

Basic Operation
The most common operations performed via the RMX Web Client are:
Starting, monitoring and managing conferences Monitoring and managing participants and endpoints as individuals or groups.
Participant A person using an endpoint to connect to a conference. When using a Room System, several participants use a single endpoint. Endpoint A hardware device, or set of devices, that can call, and be called by an MCU or another endpoint. For example, an endpoint can be a phone, a camera and microphone connected to a PC or an integrated Room System (conferencing system). Group A group of participants or endpoints with a common name.
Starting the RMX 2000

User name Password MCU IP Address
http://192.168.1.254 default
Enter your Username and Password

The defaults are both POLYCOM
RMX 2000 Screen Components
You can Login as a Chairperson, Operator or Administrator. Your Login level determines your viewing and system permissions.
Note: The administrators view is shown above. POLYCOM CONFIDENTIAL
Viewing Permissions
Chairperson Conference List List Pane Address Book Status Bar RMX Management Conference Alarms Conference Status Configurations Operator Administrator
System Permissions
Chairperson Start Conferences Monitor Conferences Monitor Participants Solve Basic Problems Modify MCU Config Operator Administrator
Conference List
Lists all the conferences running on the MCU along with their Status, Conference ID, Start Time, and End Time data.
List Pane
Displays a list and number of participants or the system management items selected in the Conference List or RMX Management pane.
RMX 2000 Management

The RMX Management pane lists the parameters that need to be configured to set up and run conferences. The Configuration Pane is divided into two sections:
Frequently Used parameters often configured monitored or modified. Rarely Used parameters configured during initial system set-up and rarely modified afterward.
Only administrators can modify these parameters.
Status Bar
The Status Bar at the bottom of the RMX screen contains System and Participant Alerts tabs as well as a Port Usage Gauge and an MCU State indicator.
System Alerts
This is a list of system problems. The alert indicator flashes red when at least one system problem exists. The flashing continues until an operator or administrator reviews the list. Open the System Alerts pane by clicking the System Alerts button in the left corner of the Status Bar.
Participant Alerts
It is a list of participants that are experiencing connection problems. It is sorted by conference. Open the Participant Alerts pane by clicking the Participant Alerts button on the left side of the Status Bar.
Close the Participant Alerts pane by clicking the Participant Alerts button again.
Port Usage Gauge

The Port Usage Gauge indicates the number of ports in use. It also indicates the number of ports licensed for the system. The red area indicates the capacity usage threshold. The usage threshold represents a percentage of the total number of ports available. The red area flashes and a System Alert is generated when port usage reaches or exceeds the threshold.
The default port usage threshold is 80% and can be set by the system administrator.
MCU State
The MCU State indicator displays one of the following:
Normal The MCU is functioning normally. Minor The MCU has a minor problem but users can keep working. Major The MCU has a major problem. MCU behavior could be effected and attention is required.
Address Book
The Address Book is a list of Participants and Groups that have been defined on the RMX. The information in the address book enables RMX users to easily assign participants to conferences.
Starting a Conference
There are several ways to start a conference:
Clicking the New Conference button in the Conferences pane,. Dialing in to a Meeting Room.
A Meeting Room is a conference that is saved in the MCU. It remains in passive mode until it is activated by the first participant, or the meeting organizer, dialing in.
Dialing in to an Ad Hoc Entry Queue which is used as the access point to the MCU.
Starting a Conference from the Conference Pane

Click the New Conference button
Note: The duration default is 1:00 hour and the system automatically generates a unique conference name.
Participant Tab Optional

Define participants Name, IP address, Alias Name/SIP Address, Interface, Connection, Encryption, and Lecturer.
To add participants from the Address Book

In the Participants List, click the Add from Address Book button to open the Participants Address Book.
To drag & drop participants into the Participants List

Open the Address Book, Select, drag and drop the participant that you wish to add to the conference directly from the Participant Address Book into the Participant List.
Information Tab (Optional)

This information is written to the Conference Data Record (CDR) when the conference is launched. Changes made to this information once the conference is running are not saved to the CDR.
Connecting to a Conference
Dial-in H.323 Participants

For H.323 participants, the dialing string is composed of the MCU prefix in the Gatekeeper and the conference ID. For example:
Gatekeeper Prefix 925 Conference ID 1001 Conference Name Maple_Room
The participant dials 9251001 or 925Maple_room. If there is no gatekeeper defined for the network, H.323 participants dial the MCUs signaling host IP address and the conference ID, separated by ##. For example:
MCU (Signaling Host) IP address 172.22.30.40 Conference ID 1001
The participant dials 172.22.30.40##1001

Dial-in SIP Participants

For SIP participants the dialing string is composed of the conference name and domain name in the following format: conference_name@domain_name. For example:
Maple_room@polycom.com
Conference Access Via an Entry Queue
Dialing is done in the same way as for conferences, where the Entry Queue ID/Name replaces the Conference ID/Name.
Ad Hoc Conferencing
The Entry Queue can also be used for Ad Hoc conferencing. If the Ad Hoc option is enabled for the Entry Queue, when the participant enters the target conference ID the system checks whether a conference with that ID is already running on the MCU. If not, the system automatically creates a new ongoing conference with that ID. An Ad Hoc conference is a conference that is started instantly, without a prior conference definition. The conference parameters are based on a Profile linked to the Entry Queue. As opposed to Meeting Rooms, that are predefined conferences saved on the MCU, Ad Hoc conferences are not stored on the MCU. Once an Ad Hoc conference is started it becomes an ongoing conference, and it is monitored and controlled as any standard ongoing conference.
Conference and Participant Monitoring

Three levels of monitoring are available with the RMX:
General Monitoring - You can monitor the general status of all ongoing conferences and their participants in the main window. Conference Level Monitoring - You can view additional information regarding a specific conference and modify its parameters if required, using the Conference Properties option. Participant Level Monitoring - You can view detailed information on the participant's status, using the Participant Properties option.
General Monitoring On Going Conferences

General monitoring enables you to keep track of conferences and their participants.
If all participants are correctly connected and whether errors or faults have occurred.
During conferences you can view the endpoint site names in the endpoints video layout windows. Endpoints can display up to 33 characters of the sites name, depending on the windows layout (size).
Monitoring and Operations Methods
Multi-selected Conferences
Using multi-select, you can monitor and perform simultaneous operations on multiple participants in multiple conferences.
Conference Level Monitoring

Conference level monitoring is available to the administrator, operator and chairperson.
Conference Properties
Additional information about the conference can be viewed when accessing the conference properties.
HD icon
Participant Level Monitoring

When a conference is selected in the Conference List, details of its participants appear in the List pane.
The following participant indicators and properties are displayed:

Name, Status, Role, IP, Alias Name/SIP Address, Network, Direction, Audio, Video, Encryption, FECC Token, and Content Token
Operations Performed During On Going Conferences

Conference Level Operations
Changing the Duration of a Conference Changing the Video Layout of a Conference Video Forcing
Participant Level Operations

Enables you to modify and control the connections and statuses of participants in on going conferences. Personal Layout Control With Click&View
Changing the Duration of a Conference

Extend a conference manually
Terminate a conference manually
Changing the Video Layout of a Conference

While the conference is running you can change the video layout and select one of 24 video layouts supported by the RMX.
Video Forcing
The chairperson or operator can select which participant appears in each of the video layout windows for any participant by using Video Forcing. Conferences start with the layout defined in the Conference Profile. Video Forcing applies to Dynamic Continuous Presence conferences. Video Forcing works on two levels:
Conference Level Applies to all conference participants. All participants have the same video layout. Participant Level The participants video layout is changed. All other conference participants video layouts are not affected.
Video Forcing can be cancelled by individual participants via Personal Layout Control without affecting other participants.
Video Forcing Guidelines

A participant cannot appear in two or more windows at the same time. Participant level video forcing overrides conference level video forcing. A participant can view him/herself in a layout window, by selecting the Same Layout option. When different size video windows are used in video layouts such as 1+2, 1+3, 1+4, etc., a participant can only be forced, in Personal Layout, to a video window of the same size as that selected for him/her in Conference Layout. When changing the Video Layout at the conference level, the video forcing settings are not applied to a new layout, and video switching is audio-activated. The video forcing setting are saved and applied the next time the layout is selected. Windows that are not assigned any participant display the current speaker and last speakers.
To Video Force a Participant to Window

In the Video Layout pane, in the window to which you want to force a participant, select the participants name from the list of conference participants.
To cancel Video Forcing for a window: simply select Auto Select from the participants list. In such a case, switching between participants is audio activated.
Participant Level Operations

Participant Level Operations enables you to modify and control the connections and statuses of participants in on going conferences.
New Participant, Add Participant From Address Book, Connect Participant, Disconnect Participant, Audio Mute, Unmute Audio, Suspend Video, Resume Video, Block Audio, Unblock Audio, Add Participant to Address Book, Abort H.239 Session, Change to Chairperson, Change to Regular Participant, and Participant Properties.
Personal Layout Control With Click&View

With the Click&View application, participants can change their Personal Layouts via DTMF codes entered from their endpoints. This option is available only if the Click&View option is selected in the IVR Service used in the conference.
Personal Layout Options Menu

Enable Click&View on the endpoints keypad, enter
* *.
Note: For a Polycom VSX endpoint the entry
sequence is *,
* *.
DTMF Code 4
Video Layout Options
Lesson 4: Administration (OPTIONAL)


Recall how to modify conference profiles within the RMX Web Client Discuss the conference modes and features for the RMX Recall how to define and view conference profiles Explain why the entry queue is a special routing lobby to access conferences Discuss how to add a participant to the address book Explain how to enable cascading conferences between two MCUs Describe how Interactive Voice Response (IVR) Services and Languages can be modified for a given environment Compare and Contrast RMX System and Participant Alerts State how to monitor the RMX hardware and run diagnostics
Conference Profiles
Profiles are conference templates stored on the MCU that enable you to define all types of conferences.
Conferencing Entities
The default conference profile is automatically assigned to the conferencing entities: meeting rooms and entry queue.
Conferencing Modes Standard Conferencing

When defining a new video Profile, you select the parameters that determine the video display on the participants endpoint and the quality of the video. The main parameters that define the quality of a video conference are:
Bit Rate - The transfer rate of video and audio streams. The higher the bit rate, the better video quality that can be viewed. Audio Algorithm - The audio compression algorithm determines the quality of the conference audio. Video protocol, video format, frame rate, annexes, and interlaced video mode - These parameters define the quality of the video images. The system selects the appropriate video setting for each endpoint according to the endpoint capabilities when connecting to the conference. For example, H.264 protocol provides better compression of video images in bit rates lower than 384 Kbps and it will be automatically selected for the endpoint if it supports H.264.
Standard Conferencing (Cont.)

Standard Definition (SD) video - A high quality video protocol which uses the H.264 video algorithm. It enables HD compliant endpoints to connect to Continuous Presence conferences at resolutions of 720X576 for PAL systems and 720X480 for NTSC systems. Bit rates for SD range from 256Kbps to 2Mbps. High Definition (HD) video An ultra-high quality video resolution enabling compliant endpoints to connect to conferences at resolutions of 1280x720 (720p) and at bit rates ranging from 384kbp to 4Mb.
Supplemental Conferencing Features

H.239 Allows compliant endpoints to transmit and receive two simultaneous streams of conference data to enable Content sharing. Lecture Mode The lecturer is seen by all participants in full screen while the lecturer views all conference participants in the selected video layout. Presentation Mode When the current speakers speech exceeds a predefined time (30 seconds), the conference layout automatically changes to full screen, displaying the current speaker as the conference lecturer on all the participants endpoints. During this time the speakers endpoint displays the previous conference layout. When another participant starts talking, the Presentation Mode is cancelled and the conference returns to its predefined video layout. Presentation mode is available with Auto Layout and Same Layout.
If the speaker in a video conference is an Audio Only participant, the Presentation Mode is disabled for that participant. Video forcing works in the same way as in Lecture Mode when Presentation Mode is activated, that is, forcing is only enabled at the conference level, and it only applies to the video layout viewed by the lecturer.
Encryption Used to enhance media security at conference and participant levels.

Viewing Profiles
Conference Profiles are listed in the Conference Profiles list pane.
Defining Profiles
Profiles are the basis for the definition of all ongoing conferences, Meeting Rooms, and Entry Queues and they contain only conference properties.
Define a New Profile: 1. Click Conference Profiles 2. Click New Profile 3. Define Profile name and general parameters 4. Click the Video Settings tab 5. Define display mode and layout 6. Select number of windows for Video layout 7. Click the Skins tab and modify the background and frames 8. Select one of the Skins 9. Click the IVR tab 10. Set the profile properties for IVR (if required) 11. Click OK to complete the profile definition
Defining a New Profile (Cont.)

Video Settings tab
Video Layout pane

Skins tab

IVR tab
Meeting Room Main Window

All Meeting Rooms are based on a Profile. The maximum number of Meeting Rooms that can be stored in the MCU memory is 200.
Creating a New Meeting Room

In the Meeting Rooms pane click the New Meeting Room button or right-click an empty area in the pane and select the New Meeting Room option from the drop menu.
Defining a New Entry Queue

The Entry Queue is a special routing lobby to access conferences. It can also be used for Ad Hoc conferencing.
Define a New Entry Queue: 1. Double-click Entry Queues in the RMX Managements rarely used pane 2. Click the New Entry Queue button 3. Define the Entry Queue definition parameters: Name Profile ID Entry Queue Service Ad Hoc Cascade
Transit Entry Queue

A Transit Entry Queue is an Entry Queue to which calls with dial strings containing incomplete or incorrect conference routing information are transferred. Calls are routed to the Transit Entry Queue when:
A Gatekeeper is not used, or where calls are made directly to the RMXs Signaling IP Address, with incorrect or without a Conference ID. When a Gatekeeper is used and only the prefix of the RMX 2000 is dialed, with incorrect or without a Conference ID. When the dial prefix is followed by an incorrect conference ID
When no Transit Entry Queue is defined, all calls are rejected by the RMX 2000. In the Transit Entry Queue, the Entry Queue IVR Service prompts the participant for a destination conference ID. Once the correct information is entered, the participant is transferred to the destination conference.
Setting a Transit Entry Queue

The RMX 2000s factory default settings define the Default Entry Queue also as the Transit Entry Queue. You can designate another Entry Queue as the Transit Entry Queue. Only one Transit Entry Queue may be defined per RMX and selecting another Entry Queue as the Transit Entry Queue automatically cancels the previous selection.
To designate an Entry Queue as Transit Entry Queue

The Entry Queue selected as Transit Entry Queue is displayed in bold.
SIP Factories
SIP Factory is a conferencing entity that enables SIP endpoints to create Ad Hoc conferences. The system is shipped with a default SIP Factory, named DefaultFactory. When a SIP endpoint calls the SIP Factory URI, a new conference is automatically created based on the Profile parameters, and the endpoint joins the conference. The SIP Factory URI must be registered with the SIP server to enable routing of calls to the SIP Factory. To ensure that the SIP factory is registered, the option to register Factories must be selected in the Default IP Network Service.
Creating SIP Factories

SIP Factory Properties
Name Enter the SIP Factory name. Profile Select the conference Profile from the list of Profiles defined in the MCU. The default Profile is selected by default. A new conference is created using the parameters defined in the Profile. Automatic Connection Select this check box to immediately accept the conference creator endpoint to the conference. If the check box is cleared, the endpoint is redirected to the conference and then connected.
Viewing the Address Book

By default, the Address Book pane is docked to the right of the screen when logging into the Polycom RMX 2000. You may also click the Address Book icon in the RMX Management pane for an enlarged view of the listed participants.
Participant Address Book Properties
Adding a Participant to the Address Book

Adding a new participant to the address book. Add a participant from an ongoing conference to the address book. You can add as many new participants to the address book as needed.
Adding a New Participant to the Address Book

In the Address Book pane, click the New Participant button.
New Participant Advanced Parameters

Name Video Protocol Broadcasting Volume Listening Volume Encryption AGC Cascaded Link
Add a Participant from an Ongoing Conference to the Address Book

Double-click the participants icon or right-click the participant icon and select participant properties.
Participant Groups
A group is a predefined collection of participants. A group provides an easy way to connect a combination of endpoints to a conference. For example, if you frequently conduct conferences with the marketing department, you can create a group called Marketing Team that contains the endpoints of all members of the marketing team.
Creating or Deleting a New Group in the Address Book

Creating
Deleting
Modifying a Group in the Address Book

Create New Participant Click the New button to create a new participant in the Address Book and have them included in the group. Add Participant Add one or more participants to the group by clicking the Add from Address Book button and selecting the participants from the Participants Address Book dialog box. Remove Participant Select the one or more desired participants in the Group properties dialog box and click the Remove button. Multiple selection of participants using Microsoft Windows conventions is enabled for (adding/removing) participants (to/from) the Group.
Importing and Exporting Address Books

Address Book databases are proprietary Polycom data files that can only be distributed among RMX units. The databases are exported in XML format, which are editable offline. If no name is assigned to the exported database, the default file name is:
EMA.DataObjects.OfflineTemplates.AddressbookContent_.xml
Importing
Exporting
Note: When importing an Address Book, participants with exact names in the current Address Book will be overridden by the imported Address Book. POLYCOM CONFIDENTIAL
Standard Definition (SD)

System resources (ports) are allocated according to endpoint capability and are optimized by allocating SD resources only to endpoints capable of receiving SD resolution.
Video Display with SD and CIF video Connections

Although any combination of CIF and SD connections is supported in all CP conferences, the following rules apply:
In a 1X1 layout, if the speaker transmits CIF, the MCU will send CIF to all participants, including the SD participants. In any other layout the MCU will transmit to each participant at the participants sending resolution. In asymmetrical layouts, a participant in the large frame that sends CIF is displayed in CIF. In panoramic layouts, participants that send CIF also receive CIF.
SD with specialized features

H.239 Encryption and FECC Lecture Mode Supported by the Cascaded link
Enabling SD
For the MCU to allocate SD resources to endpoints all of the following criteria must be met:
The MAX_CP_RESOLUTION flag must be set to SD15 or SD30. The endpoints resolution capabilities must be higher than CIF. The appropriate Quality parameter must be selected in the conference Profile. The RMX must have available resources (ports).
High Definition (HD)

Prior to running HD conferences, an HD enabled Profile must be created. To connect to an HD conference via an Entry Queue, the Entry Queue must be HD enabled and must be set to the same bit rate as the target conference. Video Display in HD Conferences
The only supported layout is 1x1. Displayed aspect ratio is 4x3 or 16x9. Personal layout, site names, skins, etc... are not supported in HD. Video forcing is enabled only at the conference level.
HD (Cont.)
Specialized Features Supported in HD
H.239 is supported with HD. When an endpoint starts a Content session, the video bit rate will be decreased according to the Content allocation settings, and this may result in a lower frame rate. Encryption and FECC are supported in HD. Lecture Mode is supported in HD. HD is supported by the cascaded link. If the API attempts to send a parameter or value that is illegal within the HD definition, the MCU will override the API and force the parameter or value defined in the current HD conference profile.
Enabling HD
For the MCU to run HD conferences the following criteria must be met:
The HD_THRESHOLD_BITRATE flag must be set in the system configuration. The endpoints must support HD. The appropriate Line rate (same or above defined threshold) and HD parameters must be selected in the conference Profile. The RMX must have available resources (ports).
Default HD Threshold Bit Rate (range 384kbps to 4Mbs, default is 768 Kbps)
To run HD conferences, define the minimum bit rate required by endpoints to connect to an HD conference in the System Configuration. Endpoints that cannot support this bit rate are connected as audio only.
Creating HD Profiles
High Definition conferences, Entry Queues and Meeting Rooms are created by selecting an HD-enabled Profile. If Conferences /Meeting Rooms are accessed via an Entry Queue, it is recommended to use the same Profile for both the target conference and Entry Queue.
Monitoring HD Conferences
HD conferences appear with the HD ( ) icon in the conferences list to indicate the currently running HD conference(s).
H.239
The H.239 protocol allows compliant endpoints to transmit and receive two simultaneous video streams:
People Conference Continuous Presence conference Content Conference Video Switching conference for content sharing
By default, all Conferences, Entry Queues, and Meeting Rooms launched on the RMX have H.239 capability. To view Content, endpoints must use the same Bit Rate, Protocol, and Resolution. An endpoint may not send Content while connecting to an Entry Queue. Endpoints without H.239 capability can connect to the video conference without Content. Simple cascade links do not declare H.239 capabilities. Content can only be shared in the local conference. The highest common Content bit rate is calculated for the conference each time an endpoint connects.
If an endpoint connects to an ongoing conference at a lower bit rate than the current bit rate, the Content bit rate for the current conference is recalculated and decreased.
Content Resolution and Bit Rate

The content algorithm is H.263 Annex T, supporting the following resolutions: QCIF, CIF, 4CIF, VGA, SVGA, XGA and SD. The content channel can transmit one of the following modes:
Graphics default mode, for standard graphics Hi-res Graphics requiring a higher bit rate, for high quality display or highly detailed graphics Live Video highest bit rate, for video clips or live video display
Bit rate allocation is dynamic during the conference and when the Content channel closes, the video bit rate of the People conference is restored to its maximum. An endpoint cannot increase its bit rate but it can change its Content resolution during a conference. The RMX can decrease the allocated content bit rate during a conference.
Bite rate allocated to the Content Channel

The following table shows the bit rate allocated to the Content channel from the video channel in each of the three Content modes:
Lecture Mode
Lecture Mode enables all participants to view the lecturer in full screen while the conference lecturer see all the other conference participants in the selected layout while he/she is speaking. When the number of sites/endpoints exceeds the number of video windows in the layout, switching between participants occurs every 15 seconds. Automatic switching is suspended when one of the participants begins talking, and it is resumed automatically when the lecturer resumes talking. Lecture Mode is enabled at the conference level by selecting the lecturer. Automatic switching between participants viewed on the Lecturers screen is enabled in the conference Profile.
Lecture Mode Enabled

When Lecture Mode is enabled for the conference, the lecturer is indicated by an icon ( ) in the Role column of the Participants list.
Media Encryption
Encryption is available at the conference and participant levels, based on AES 128 Media Encryption and DH 1024 Key Exchange standards. Media Encryption guidelines:
Encryption is not available in all countries and it is enabled in the MCU license. Contact Polycom Support to enable it. Endpoints must support both AES 128 encryption and DH 1024 key exchange standards which are compliant with H.235 (H.323) to encrypt and to join an encrypted conference. Encryption can be applied at the conference level or participant level. System handling of encrypted and non-encrypted participants are enabled in the configuration file. The encryption mode of the endpoints is not automatically recognized, therefore the encryption mode must be set for the conference or the participants (when defined). Conference level encryption must be set in the Profile, and cannot be changed once the conference is running. Mixing encrypted and non-encrypted endpoints in one conference is supported only for H.323 defined participants. Different states of encryption for predefined IP participants is possible, based on a system flag settings (ALLOW_ENCRYPT_IN_PARTY_LEVEL). In Cascaded conferences, to encrypt the conference the link between the cascaded conferences must be encrypted.
Encryption Options
When enabled, encryption can be applied at the conference level and at the participant level. In addition, you can define whether access to conferences for encrypted and non-encrypted IP participants is done at the conference level or at the participant level.
Cascading Conferences
Cascading enables administrators to connect one conference directly to another conference using an H.323 connection. The conferences can run on the same MCU or different MCUs. There are many reasons for cascading conferences, the most common are:
Connecting two conferences on different MCUs at different sites. Utilizing the connection abilities of different MCUs, for example, different communication protocols, such as, serial connections, ISDN, etc....
Cascaded Conferences
Cascading two conferences requires that the following procedures are implemented:
Creating the cascade-enabled Entry Queue Creating a cascade-enabled Dial-out link
Note: In order to avoid cluttering in the cascaded window, it is advised to select appropriate video layouts in each conference before cascading them.
Unsupported features with Cascaded Conferences

DTMF codes are enabled in cascaded conference, but only in their local conference. The operations executed via DTMF codes are not forwarded between linked conferences. H.239 (Content channels will only broadcast in their local MCU). FECC (Far End Camera Control will only apply to conferences running in their local MCU).
Monitoring Cascaded Conferences
Cascading linked (
) icon ) icon
Cascaded Conference (
Creating the Dial-out Link from a conference running on the MGC to the conference running on the RMX
Polycom RMX 2000 User Connection Levels

Users are Polycom RMX 2000 Web Clients that are defined in the Polycom RMX 2000 user database and can connect to the system to perform various operations.
A Chairperson can only manage new conferences, Meeting Rooms, and participants. The Chairperson does not have access to the Polycom RMX 2000 configurations and utilities. Operators can perform all the Polycom RMX 2000 tasks a Chairperson does. In addition, Operators can also view the Polycom RMX 2000 configurations. Administrators can perform all the tasks of a Chairperson and an Operator. In addition, Administrators can define and delete other users, and perform all configuration and maintenance tasks. Administrators and Operators can verify which users are defined in the system. Neither of them can view the user passwords, but an Administrator can change a password.
Default Administrator user: POLYCOM, Password: POLYCOM

Listing and Adding New Users

User pane
You can view the list of users that are currently defined in the system.
In the RMX Management pane, click the Users option.
Administrators can add new users to the system by clicking on the New User ( ) button.
Note: Users can also be deleted by an authorized administrator. However if you attempt to delete the last remaining Administrator account in the User List pane it will not be permitted as a security precaution. POLYCOM CONFIDENTIAL
User Properties
Changing a Users Password

An Administrator can change his/her own password and other users passwords. An Operator can change his/her own password.
Network Services
To enable the Polycom RMX 2000 to function within IP network environments, network parameters must be defined in the IP Services List. To list the IP Network Service, in the Polycom RMX 2000 Management pane click Network Services.
IP Services
Two IP Services are defined for the RMX unit.
Management Network Default IP Service (Conferencing Service)
The Management Network is used to control the RMX, mainly via the Polycom RMX 2000 Web Client application. The Management Network contains the network parameters that connect between the Polycom RMX 2000 and the Polycom RMX 2000 Web Client. Management Network parameters include the IP address of the Control Unit, whose IP address can be used by the administrator, or control unit service personnel, to connect to the Control Unit should the RMX become corrupted or inaccessible. During First Time Power-up, the Management Network parameters can be set either via a USB key or by using a cable to create a private network.
Default IP Service (Conferencing Service)

The Default IP Service (Conferencing Service) is used to configure and manage communications between the RMX and conferencing devices such as endpoints, gatekeepers, SIP servers, etc. The Default IP Service contains parameters for:
Signaling Host Address MPM boards (media processors) External Conferencing Devices
Calls from all external entities are made to the Signaling Host, which initiates call set-up and assigns the call to the appropriate MPM board. Conferencing related definitions such as environment (H.323 or SIP) are also defined in this service. Most of the Default IP Service is configured by the Fast Configuration Wizard, which runs automatically should the following occur: First Time Power-up Default IP Service is deleted, followed by an RMX reset.
Modifying IP Services (Management Network and Default IP Services

The Management Network parameters need to be modified if you want to:
Connect directly to the MCU from a workstation Modify routes Modify DNS information Default IP Services
The Default IP Service parameters need to be modified if you want to change the:
Network type that the Polycom RMX 2000 connects to IP address of the Polycom RMX 2000 Signaling Host Media boards Subnet mask of the Polycom RMX 2000s IP cards
Network Monitor
Central Signaling is the RMX entity used for monitoring the status of external network entities such as the Gatekeeper, DNS, SIP proxy and Outbound Proxy and their interaction with the MCU.
Connection State The state of the connection between Signaling host and the Gatekeeper. Registration Interval The interval in seconds between the Signaling hosts registration messages to the gatekeeper. This value is taken from either the IP Network Service or from the Gatekeeper during registration. The lesser value of the two is chosen.
1. 2. 3.
Click Signal Monitor Double-click Default IP Service Select H.323 or SIP
Monitoring Central Signaling SIP Servers

SIP Server display fields
Role Active or Backup Name The name of the SIP Server IP The SIP Servers IP address Status The connection state (Not Available or Auto) between the SIP Server and the Signaling host.
Interactive Voice Response (IVR) Services

Interactive Voice Response (IVR) is an application that allows participants to communicate with the conferencing system via their endpoints input device (such as a remote control). The IVR Service includes a set of voice prompts and a video slide used to automate the participants connection to a conference or Entry Queue. It allows customization of menu driven scripts and voice prompts to meet different needs and languages. The IVR module includes two types of services:
Conference IVR Service that is used with conferences IVR Service that is used with Entry Queues
The system is shipped with one default Conference IVR Service and one default Entry Queue IVR Service. Both services include voice messages and video slides in English.
Note: Up to 40 IVR Services can be defined for a single Polycom RMX 2000 unit!
Customize the IVR Messages and Video Slide

To customize the IVR messages and video slide perform the following operations:
Record the required voice messages and create a new video slide. Optional. Add the language to the list of languages supported by the system. Upload the voice messages to the MCU (This can be done as part of the language definition or during the IVR Service definition). Create the conference IVR Service and upload the video slide, and if required any additional voice messages. Optional. Create the Entry Queue IVR Service and upload the required video slide and voice messages.
Note: The video slide must be in a .jpg or .bmp file format.
IVR Services List

You can view the currently defined Conference IVR and Entry Queue IVR Services in the IVR Services list pane.
IVR Toolbar buttons
Note: The music file must be in *.wav format and its length cannot exceed one hour.
Adding Languages
You can define different sets of audio prompts in different languages, allowing the participants to hear the messages in their preferred language. The RMX is shipped with a default language (English) and all the prompts and messages required for the default IVR Services, conference and Entry Queues shipped with the system. You can add languages to the list of languages for which different messages are downloaded to the MCU and IVR Services are created. This step is required before the creation of additional IVR messages using languages that are different from English, or if you want to download additional voice files to existing files in one operation and not during the IVR service definition.
The Call Detail Record (CDR) Utility

The Call Detail Record (CDR) utility enables you to view summary information about conferences, and retrieve full conference information and archive it to a file. The file can be used to produce reports or can be exported to external billing programs. The Polycom RMX can store details of up to 1000 conferences. When this number is exceeded, the system overwrites conferences, starting with the earliest conference. To save the conferences information, their data must be retrieved and archived. The frequency with which the archiving should be performed depends on the volume of conferences run by the MCU. Each conference is a separate record in the MCU memory. Each conference is archived as a separate file. Each conference CDR file contains general information about the conference, such as the conference name, ID, start time and duration, as well as information about events occurring during the conference, such as adding a new participant, disconnecting a participant or extending the length of the conference. Note: The Call Detail Report (CDR) is backward compatible to MGC version 8.
CDR File Format Unformatted Data

Unformatted data Unformatted CDR files contain multiple records in raw data format. The first record in each file contains general conference data. The remaining records contain event data, one record for each event. Each record contains field values separated by commas. This data can be transferred to an external program such as Microsoft Excel for billing purposes.
CDR File Format Formatted Text

Formatted text Formatted CDR files contain multiple sections. The first section in each file contains general conference data. The remaining sections contain event data, one section for each event. Each field value appears in a separate line, together with its name. This data can be used to generate a summary report for a conference.
RMX Utilities System and Participant Alerts

The System Alerts indication bar blinks red prompting the user to view the active alarms. The Participants Alerts indication bar blinks red indicating participant connection difficulties in conferences.
System Alerts
System Alerts are activated when the system encounters errors such as a general or card error.
Reports: Active Alarms Fault List Save to Text file
Active Alarm pane columns:

Time Lists the date and time that the error occurred. Category Lists the type of error (File, Card, Exception, General, Assert, and Startup). Level Indicates the severity of the problem. There are three fault indicators: Major Error, Minor Error, and Startup Error Indicator. Code Indicates the problem, as indicated by the error category. Process Name Lists the type of functional process involved. Description When applicable, displays a more detailed explanation of the cause of the problem.
Participant Alerts
Participant Alerts enables users, participants and conferences to be prompted and currently connected. This includes all participants that are disconnected, idle, on standby or waiting for dial-in. Alerts are intended for users to quickly see all participants that need their attention.
Connect Disconnect Delete
System Configuration Modifying System Flags

Aspects of the systems overall behavior can be configured by modifying the default values of system flags.
RMX Time
To ensure accurate conference scheduling, the RMX MCU has a clock that can function in standalone mode, or in synchronization with up to three Network Time Protocol (NTP) servers.
Note: After resetting the MCU a delay may occur when synchronizing the external NTP server.
Licensing
System Serial Number Stored on the backplane License Number Shipped with the system Activation Key Generated from the Polycom Resource Center
License Number
Note: The license key will need to be installed each time you upgrade the system.
Licensing (Cont.)
The system Serial Number (SN) is stored in the chassis CFS Key is per SN and stored in the chassis after the registration Changing the CNTL unit does not affect licensing Current license is per port count and encryption If the encryption is not activated the GUI will not contain this functionality
On the installation the license number and the system serial number are registered at the Polycom Resource Center
Product Activation
The site will generate a key to activate the system
Notifications Settings
The RMX can display notifications when:
A new RMX user connects to the MCU. A new conference is started. Not all defined participants are connected to the conference or when a single participant is connected A change in the MCU status occurs and an alarm is added to the alarms list.
A welcome message is displayed to the RMX user upon connection.
Configure Notifications
RMX Notification fields

New Connection New Conference Created Conference Not Full Welcome Message Active Alarms Update Fault List Update
Resource Report
The Resource Report details the current availability and usage of the system resources. The Resource Report generates a report that displays the number of ports that can be allocated to participants and the number of ports that cannot be used.
Resource Report fields: Type Total Occupied Free
Software Management
The Software Management utility is used to backup and restore the RMX's configuration files and to download MCU software.
Functionality Upgrade
SW version upgrade is done via the GUI A version sent to the field (including a patch) will always be a complete version, and its copy is stored in the R&D configuration management system Major versions will require an upgrade to the license key
SW Upgrade (Internal Structure on the Flash)

3 copies of the SW (OS + MCU)
Current- the last installed version Previous- the version before the last SW update Factory- the version sent out from the factory
While booting the application may downgrade automatically if the SW failed a checksum test The configuration is version agnostic
Factory Previous Current

1.03.412 V2.01.101 V2.01.121
Configuration Files
Configuration Directory Content

IVR
Configuration Tones Music File Roll Call Recordings Slides Messages Temporary Recordings
IP Services System.cfg License Copy System time setting Users list Address Book
Meeting Rooms list Profiles
Restore Configuration Files

To restore configuration files:
In the Administration menu, click Software Management and click Restore Config. Enter (or Browse to) the Restore Directory Path where the backed up configuration files are stored and click Yes.
To download MCU software files:

In the Administration menu, click Software Management and click Software Download. Enter (or Browse to) the Install Path and click Yes.
Troubleshooting Concept
Central logger repository on the system for all the various components Traces are captured continuously by the device The admin can easily download a file with all the required information Embed support and R&D tools in the system GUI for remote and on-site advanced debugging Admin users are set at the Shelf Management and the Control Unit OS to allow additional privileges SUPPORT user type for all the advanced tools
Remote Management
The support/R&D can access the device via the public internet using port 80 The admin will add the SUPPORT user with ADMIN privileges We may have a GUI version on a CD to overcome BW issue when operating remotely
Logger Diagnostic Files

The Logger utility is a troubleshooting tool that continually records MCU system messages and saves them to files in the MCU hard drive. For each time interval defined in the system, a different data file is created. The files may be retrieved from the hard drive for offline analysis and debugging purposes. The Logger utility is activated at the MCU startup. The Logger is disabled when the MCU is reset manually or when there is a problem with the Logger utility, e.g errors on the hard drive where files are saved. In such cases, data cannot be retrieved. When the MCU is reset via the RMX, the files are saved on the MCU hard drive.
Access to Logger Diagnostic Files

Diagnostic File Button Options
Refresh List Select All Browse Get Files
Hardware Monitoring
The status and properties of the RMX hardware components can be viewed and monitored in the Hardware Monitor list pane.
HW Monitor List Pane Toolbar: System Reset System Shutdown System Startup Diagnostic Mode
Note: A critical condition temperature invokes a system shut down.

Viewing Hardware Components Properties

MCU Properties (RMX) Card Properties (MPM-F, CNTL, RTM-IP) Supporting Hardware Components Properties (Backplane, FANS, LAN)
Note: No properties are provided for Power Supply (PWR).

Diagnostic Mode
Diagnostic Mode is a debugging tool for performing hardware diagnostics that detect malfunctions in the hardware components performance. Diagnostics are performed only for the MFA, CPU and Switch (Cards: MPM, CNTL and RTM IP). When Diagnostic Mode is initialized, the MCU is reset and upon restarting, the MCU will enter Diagnostic Mode. Entering this mode causes the MCU to terminate all active conferences and prohibits conferences from being established. Diagnostic Mode is only enabled when connecting directly to the Shelf Management server. To do so, type the Shelf Management IP address in the URL address.
Performing Diagnostics
Diagnostic mode
Diagnostic Pane
Test Parameters: Quick Test Mode Loop Test Stop On Fail Run All Test
Diagnostic Monitoring
A hardware components test status can be viewed in the Diagnostics Test Monitoring section before, during and after tests have been initiated. Test results will only be displayed after tests are completed. The Diagnostic Tests Monitoring section is comprised of three tabs: MCU Monitor, Cards Monitor and Error Buffer.
MCU Monitor
The MCU Monitor tab lists the status of all the cards that can be tested in Diagnostic Mode.
Card Monitor
The Cards Monitor tab displays the status of the selected tests being run on the currently viewed card.
Error Buffer
The Error Buffer tab displays the errors encountered during testing of the cards.
RMX 2000 Administrators Guide Appendixes

Disconnection Causes Appendix A Active Alarms Appendix B CDR Fields - Unformatted File Appendix C Ad Hoc Conferencing and External Database Authentication Appendix D Participant Properties Advanced Channel Information Appendix E Configuring Direct Connections to RMX Appendix F Third Party Software Licenses Appendix G
Lesson 5: Interoperability and System Limitations (OPTIONAL)


Recall the RMX 2000 Interoperability and known System Limitations
Interoperability with the RMX 2000

Gatekeeper/Proxies Polycom PathNavigator Cisco gatekeeper Radvision ECS gatekeeper Microsoft LCS SIP proxy Iptel proxy ReadiManager SE200 Polycom PathNavigator Recorder Polycom RSS 2000 MCUs and Call Managers Cisco Call Manager Tandberg MCU
Version 7.0.0.03 12.3 3.5.2.5 2005 ver. 2.0.5470.0 0.9.6 1.0.2 7.0.0.03 Version 1.01.002 Version 4.1 D3.9
Endpoints Polycom
Device Polycom PVX Polycom VS 512 Polycom VSSP 128 Polycom VSSP 384 Polycom VS EX Polycom VS FX Polycom V500 Polycom V500 Pal Polycom VSX 3000 Polycom VS 4000
Version 8.0.2.0235 7.5.2 7.5.2 7.5.2 6.0.5.4 6.0.5.4 8.5.2 8.5.2 8.5.2 6.04
Device Polycom VS 5000 Polycom VSX 7000 Polycom VSX 8000
Version 8.5.2 8.5.2 8.5.2
Polycom iPower 9000 6.1.0.51 Polycom iPower 600 Polycom iPower 900 Polycom HDX 9001 Polycom HDX 9002 Polycom HDX 9004 6.1.0.51 6.1.0.51 301-1.02 301-1.02 301-1.02
Endpoints Others
Device Aethra VegaStar Gold Sony PCS1 TX MXP TA B TA E LifeSize MS OC Microsoft Windows MSN Messenger VCON3000 VCON5000
Version 6.0.49 3.3 F5.0 10.1 5.2 LS_RMI_2.5.1(1) 1.0.559 5.1 6.0.49 3.5.61
System Limitations
Category
Cascading
Description
In cascaded conferences the MCU connection may lose video.
ID VNGR#
2507
CDR
When the conference termination Time is changed, the CDR is not updated.
1569
Encryption
The Encryption field is missing from the CDR section.
3011
Entry Queue
When a Participant enters an Ad Hoc Entry Queue and creates an Ad Hoc conference with an ID that already exists as a conference name, the participant remain in the Entry Queue.
1528
System Limitations
Category
Entry Queue
Description
Defined dial-in participants are Not recognized when connecting to a conference via an Entry Queue.
ID VNGR#
321
Gateway
All endpoints that dial-in to a Conference using a Gateway Receive identical names in the Participants pane,
1011
General
Legacy endpoints that support Only H.261 do not connect or connect as Secondary.
978
General
During RMX restart there is no indication or message of the systems reset.
3198
System Limitations
Category
HD
Description
In HD conferences, Tandberg endpoints may connect as Secondary when HD frame rate capabilities are less than 7.5 frames per second.
ID VNGR#
3089
NTP
RMX Time dialog box: While Operating the external NTP (enable/disable) the clock is updated after 2 minutes. When updating the time manually, the clock is updated after 10 seconds.
3629
System Limitations
Category
SD
Description
In SD calls the fourth skin (the one with circles) is replaced by the third skin (the one with triangles).
ID VNGR#
3719
SIP
SIP participants cannot connect to a conference when the conference name contains blank spaces.
3276
Web Client
Windows Explorer >Internet Options> Security settings must be set to Medium or less when using the RMX Web Client.
2473
Note: It is highly possible the system limitations identified in this pre-sales technical course have been resolved by engineering and technical support. Therefore, It is highly recommend you routinely check the Polycom Support site for more details.
Lesson 6: Summary and Closing

RMX 2000 Pre-Sales Technical Training Course Objectives

Upon completion of this course the student will able to:
Identify the RMX 2000 key hardware components and functions Identify and clarify the RMX 2000 systems primary features Discuss the first time installation and configuration three key procedures for the RMX 2000 Recall the default conference settings for the RMX 2000 Recall the most common operations performed via the RMX Web Client Identify the five panes associated with the RMX Web Client Discuss the login levels and viewing permissions for the Chairperson, Operator or Administrator State the ways to start a conference using the RMX 2000 Understand how to enable personal layout control with Click&View
RMX 2000 Real-time Media Conferencing Platform

A Completely New System Architecture To Support Todays & Tomorrows Conferencing Market
Advanced Open IP Platform
Advanced Telecom Computing Architecture (ATCA) is a new industry standard that utilizes technologies designed to achieve carrier class reliability, serviceability, scalability and performance IP Multimedia Subsystem (IMS) distributed architecture enables the separation of application control, signaling and media processing functions making it easy to develop 3rd party applications and desktop integration
Simple & Accessible Conferencing

Intuitive end-user interfaces - On demand & scheduled conferencing Easy to install, manage, and maintain
Ultimate User Experience

Highest quality audio, video and content Very low latency for a more real, spontaneous conferencing experience
The World Leader in Multipoint Conferencing
Questions
More additional support and information on the Polycom RMX 2000 Real-Time Media Conferencing Platform
Contact certification@polycom.com
Congratulations!

Lesson 7: Pre-Sales Technical Test

Disclaimer: Please proceed to the on-line test to complete the learning experience and to obtain credit for the Polycom RMX Pre-Sales Technical Training course! POLYCOM CONFIDENTIAL
Polycom RMX 2000 Pre-Sales Technical

Now that you have completed the course, click on the green right arrow button to advance to the test.
To start the test select Take test for:
Congratulations!


RMX 2000 Presales Tech Training

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

RMX 2000 Presales Tech Training

Загружено:

Авторское право:

Доступные форматы

RMX 2000 Real-Time Media Conferencing Platform

Pre-Sales Technical Training Course

Advanced Open IP Platform. Simple and Accessible. Ultimate User Experience.

RMX 2000 Agenda

RMX 2000 Real-Time Media Conferencing Platform

Lesson 1: Hardware and System Overview

Advanced Open IP Platform. Simple and Accessible. Ultimate User Experience.

Lesson 1 Learning Objectives

RMX 2000 What is it?

What makes the RMX 2000 different?

First application running on RMX2000 is multipoint IP Video and VoIP

RMX Hardware Overview

RMX 2000 ATCA Design

RMX 2000 ATCA Design

Active BP Fabric Network

RMX 2000 RTM IP Board

Shelf Manager and IPMI controller

12V Power for CPU cards, RTM IP and FANS

Media Processing Module (MPM)

Each sensor has the following range

RTM IP Board LEDs

Multipoint Video Conferencing using an Polycom RMX 2000

RMX 2000 Main Features

RMX 2000 Main Features (Cont.)

High Definition (HD) 384Kbps to 4Mbps

Multiple Switching Modes

RMX 2000 Main Features (Cont.)

RMX 2000 Main Features (Cont.)

RMX 2000 Real-Time Media Conferencing Platform

Lesson 2: First Time Installation and Configuration

Advanced Open IP Platform. Simple and Accessible. Ultimate User Experience.

Lesson 2 Learning Objectives

Recall the default conference settings for the RMX 2000

State where to go for additional help in configuring the RMX 2000

First Time Installation and Configuration

Gather Network Equipment and Address Information

First Entry Configuration

Fast Configuration Wizard

Successful Configuration for the RMX 2000

Default Conference Settings

Default Conferencing Settings (Cont.)

Entry Queue Service

Customizing the Default Conferencing Settings

RMX 2000 Real-Time Media Conferencing Platform

Lesson 3: Basic Operation

Advanced Open IP Platform. Simple and Accessible. Ultimate User Experience.

Lesson 3 Learning Objectives

Understand how to enable personal layout control with Click&View

Starting the RMX 2000

Enter your Username and Password

RMX 2000 Screen Components

RMX 2000 Management

Only administrators can modify these parameters.

Port Usage Gauge

Starting a Conference from the Conference Pane

Participant Tab Optional

To add participants from the Address Book

To drag & drop participants into the Participants List

Information Tab (Optional)

Dial-in H.323 Participants

The participant dials 172.22.30.40##1001

Dial-in SIP Participants

Conference Access Via an Entry Queue