User manual

ManualsBrandsPolycom ManualsSoftwareStereo Receiver RMX 1500

[Type the document title]

Polycom Document Title 1



Version 7.8 | November 2012 | DOC2702A

Polycom® RealPresence® Collaboration Server

(RMX) 1500/2000/4000 Administrator’s Guide

Summary of content (1010 pages)

PAGE 1
[Type the document title] Version 7.
PAGE 2
Trademark Information POLYCOM® and the names and marks associated with Polycom's products are trademarks and/or service marks of Polycom, Inc., and are registered and/or common law marks in the United States and various other countries. All other trademarks are the property of their respective owners. Patent Information The accompanying product may be protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc.
PAGE 3
Table of Contents Table of Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 About the RMX Administrator’s Guide .............................................................................. 1-1 Who Should Read This Guide? .................................................................................... 1-2 Prerequisites ......................................................................................................
PAGE 4
Polycom RealPresence® Collaboration Server (RMX) 1500, 2000, 4000 Administrator’s Guide Site Names Definition ..................................................................................................2-64 Guidelines ..............................................................................................................2-64 Site Names Display Position ...............................................................................2-65 Message Overlay for Text Messaging .........................
PAGE 5
Table of Contents RMX System Flag Settings .................................................................................. 3-23 RMX Profile Setting .............................................................................................. 3-24 Additional Intermediate Video Resolutions ............................................................. 3-24 Microsoft RTV Video Protocol Support in CP Conferences ........................................... 3-24 Guidelines ....................................
PAGE 6
Polycom RealPresence® Collaboration Server (RMX) 1500, 2000, 4000 Administrator’s Guide Guidelines ......................................................................................................................4-33 Enabling Auto Scan and Customized Polling ..........................................................4-33 Auto Scan ...............................................................................................................4-33 Customized Polling .......................................
PAGE 7
Table of Contents RPX and TPX Video Layouts ...................................................................................... 4-58 Enabling Telepresence Mode ...................................................................................... 4-60 Conference Level .................................................................................................. 4-60 Multiple Cascade Links ...............................................................................................
PAGE 8
Polycom RealPresence® Collaboration Server (RMX) 1500, 2000, 4000 Administrator’s Guide RMX Configuration Enabling ISDN Cascading Links ......................................5-9 Suppression of DTMF Forwarding ....................................................................5-13 Star Cascading Topology .....................................................................................................5-14 Master-Slave Cascading ............................................................................
PAGE 9
Table of Contents Adding a Group from the Address Book to Conferences ........................................ 8-5 Participant Groups ................................................................................................................. 8-6 Managing Groups in the Address Book ...................................................................... 8-6 Managing the Address Book ................................................................................................ 8-7 Guidelines ..........
PAGE 10
Polycom RealPresence® Collaboration Server (RMX) 1500, 2000, 4000 Administrator’s Guide Operator Assistance & Participant Move . . . . . . . . . . . . . . . . . . . . . . . . . . .10-1 Operator Conferences ..........................................................................................................10-1 Defining the Components Enabling Operator Assistance ......................................10-3 Defining a Conference IVR Service with Operator Assistance Options .......
PAGE 11
Table of Contents Viewing the Properties of an Ongoing SVC-based Conference .......................... 13-14 Monitoring Operator Conferences and Participants Requiring Assistance ...... 13-18 Requesting Help ................................................................................................. 13-18 Request to Speak ................................................................................................. 13-19 Participant Alerts List ......................................................
PAGE 12
Polycom RealPresence® Collaboration Server (RMX) 1500, 2000, 4000 Administrator’s Guide User and Connection Management in Ultra Secure Mode .............................................15-8 Managing the System Users ........................................................................................15-9 User Types .............................................................................................................15-9 Disabling/Enabling Users ....................................................
PAGE 13
Table of Contents Obtaining ISDN/PSTN required information ............................................... 16-41 Modifying an ISDN/PSTN Network Service ......................................................... 16-47 Network Security ................................................................................................................ 16-48 RealPresence Collaboration Server (RMX) 1500/RealPresence Collaboration Server (RMX) 4000 .....................................................................
PAGE 14
Polycom RealPresence® Collaboration Server (RMX) 1500, 2000, 4000 Administrator’s Guide Defining a New Conference IVR Service ..........................................................................17-6 Defining a New Conference IVR Service ..................................................................17-6 Entry Queue IVR Service ...................................................................................................17-21 Defining a New Entry Queue IVR Service .............................
PAGE 15
Table of Contents Gateway Redial or Redialing Gateway Calls ......................................................... 19-11 Guidelines ............................................................................................................ 19-11 Redial on Wrong Number ......................................................................................... 19-11 Wrong Destination Number .............................................................................
PAGE 16
Polycom RealPresence® Collaboration Server (RMX) 1500, 2000, 4000 Administrator’s Guide Monitoring Conferences ....................................................................................................20-16 Grouping the Participants by MCU .........................................................................20-17 Start Monitoring/Stop Monitoring ..........................................................................20-18 Modifying the MCU Properties ........................................
PAGE 17
Table of Contents Private MIBs ........................................................................................................ 21-27 Support for MIB-II Sections .............................................................................. 21-27 The Alarm-MIB ................................................................................................... 21-28 H.341-MIB (H.341 – H.323) ............................................................................... 21-28 Standard MIBs ..........
PAGE 18
Polycom RealPresence® Collaboration Server (RMX) 1500, 2000, 4000 Administrator’s Guide Network Intrusion Detection System (NIDS) .................................................21-58 Using the Information Collector ...............................................................................21-58 Step 1: Creating the Information Collector Compressed File ...............................21-59 Step 2: Saving the Compressed File .........................................................................
PAGE 19
Table of Contents Performing Advanced Mode Diagnostics .............................................................. 23-27 Diagnostics Monitoring ............................................................................................. 23-31 MCU Monitor ...................................................................................................... 23-31 Cards Monitor ..................................................................................................... 23-32 Error Buffer ........
PAGE 20
Polycom RealPresence® Collaboration Server (RMX) 1500, 2000, 4000 Administrator’s Guide Purchasing a Certificate ................................................................................................ F-2 Installing the Certificate ................................................................................................ F-4 Creating/Modifying System Flags .............................................................................. F-5 Enabling Secure Communication Mode ...................
PAGE 21
Table of Contents Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H-1 Overview ................................................................................................................................H-1 Conferencing Entities Presence ...................................................................................H-2 Multiple Networks ................................................................................................
PAGE 22
Polycom RealPresence® Collaboration Server (RMX) 1500, 2000, 4000 Administrator’s Guide Modify the MCU Management Network Service to Include the DNS Server ... H-36 Defining a SIP Network Service in the MCU and Installing the Security Certificate ..................................................................................................................... H-37 The Security Certificate ......................................................................................
PAGE 23
Table of Contents Model 1 .............................................................................................................................I-8 Call Flow ...........................................................................................................................I-9 Multipoint call via Service Provider - Model 1 ...................................................I-9 Model 2 .............................................................................................................
PAGE 24
Polycom RealPresence® Collaboration Server (RMX) 1500, 2000, 4000 Administrator’s Guide USB Ports on RealPresence Collaboration Server (RMX) 1500/RealPresence Collaboration Server (RMX) 2000/RealPresence Collaboration Server (RMX) 4000 ....................................................................................................................... J-1 Restore to Factory Security Defaults ....................................................................................
PAGE 25
1 Overview About the RMX Administrator’s Guide The product names, Polycom® RealPresence® Collaboration Server 1500, 2000, 4000 and RMX® 1500, 2000, 4000 are used interchangeably throughout this document. The Polycom® Polycom® RealPresence® Collaboration Server 1500, 2000, 4000 provides instructions for configuring, deploying, and administering Polycom Multipoint Control Units (MCUs) for video conferencing.
PAGE 26
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 The RealPresence Collaboration Server (RMX) 1500/2000/4000 Deployment Guide for Maximum Security Environments provides a deployment methodology for system administrators implementing Maximum Security Environments. Who Should Read This Guide? System administrators and network engineers should read this guide to learn how to properly set up Polycom RMX systems. This guide describes administration-level tasks.
PAGE 27
Chapter 1-Overview About the Polycom RMX System The Polycom RMX 1500/2000/4000 Multipoint Control Unit (MCU) is a high performance, scalable, IP-network (H.323 and SIP) and ISDN/PSTN solution that provides the user with feature-rich and easy-to-use multipoint voice and video conferencing. The RMX 1500/2000/4000 unit can be controlled via the LAN, the RMX Web Client application, Internet Explorer R installed on the user’s workstation, or the RMX Manager application.
PAGE 28
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 IP and ISDN Network Guidelines IP Networks In the RealPresence Collaboration Server (RMX) 1500 and RealPresence Collaboration Server (RMX) 2000, system management and IP conferencing are performed via a single LAN port. The networks can be separated in Maximum Security Environments. In the RealPresence Collaboration Server (RMX) 4000, system management and IP conferencing are performed via two different LAN ports.
PAGE 29
Chapter 1-Overview In the example shown here, the RealPresence Collaboration Server Licensing Mode is CP Licensing, and the Card Configuration Mode is MPMx. Card Configuration Mode Feature Support with MPMx Cards Only Table 1-2 lists the RMX (RMX) features that are only supported with MPMx cards. . Table 1-2 Features Supported with MPMx Card Configuration Mode Only Feature Name Polycom, Inc.
PAGE 30
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 1-2 Features Supported with MPMx Card Configuration Mode Only Feature Name Description Content at HD1080p Resolution Content is supported at HD1080p resolution at 30 fps and 60 fps. HD H.264 Content and H.264 Content for Cascading links Enables conference participants to receive higher quality Content in both standard conferences and cascaded conferences.
PAGE 31
Chapter 1-Overview Table 1-2 Features Supported with MPMx Card Configuration Mode Only Feature Name Polycom, Inc. Description Cascading between RMX Meeting room / Microsoft A/V MCU Microsoft Lync users can connect an RMX Meeting Room to a conference running on the Microsoft A/V MCU. FEC Support Support of Microsoft RTV FEC (Forward Error Correction) that controls and correct packet loss when receiving and sending video streams using the Microsoft Lync Server 2010.
PAGE 32
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Workstation Requirements The RMX Web Client and RMX Manager applications can be installed in an environment that meets the following requirements: • Minimum Hardware – Intel® Pentium® III, 1 GHz or higher, 1024 MB RAM, 500 MB free disk space. • Workstation Operating System – Microsoft® Windows® XP, Vista®, Windows® 7. • Network Card – 10/100 Mbps. • Web Browser - Microsoft® Internet Explorer® Version 7 or higher.
PAGE 33
2 Conference Profiles Profiles stored on the MCU enable you to define all types of conferences. Profiles include conference parameters such as Conferencing Mode, Conference Session Type, Conference Line Rate, People and Content resolution and settings, Video Layout, Encryption, Lost Packet Recovery etc.
PAGE 34
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Media Relay - SVC Conferencing SVC Conferencing is based on the SVC video protocol and SAC audio protocol. SVC Conferencing offers high resolution video conferencing with low end-to-end latency and improved Error Resiliency without video transcoding by the MCU, hence using less video resources.
PAGE 35
Chapter 2-Conference Profiles For conferences with more participants than display squares, the RMX dynamic video mix capability allows the viewed sites to be modified throughout the conference. The displayed layout can be changed during an ongoing conference, allowing a participant to view different screen layouts of the other conference participants. These layout options allow conferences to have greater flexibility when displaying a large number of participants and maximizes the screen’s effectiveness.
PAGE 36
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Video Protocol Support in CP Conferences The video protocol selected by the system determines the video compression standard used by the endpoints. In Continuous Presence conferences, the system selects the best video protocol for each of the endpoint according to he endpoint’s capabilities. The following Video protocols are supported in CP conferences: • H.
PAGE 37
Chapter 2-Conference Profiles Guidelines • Only H.264 Base and High Profile video protocols are supported in Video Switching Conferences. • Video Switching conferences can be set to one of the following resolutions, depending on the capabilities of the endpoints connecting to the conference: • • — H.264 1080p60 (Symmetrically, at bit rates of up to 6Mbps). — HD1080p60 — H.264 1080p30 — H.264 720p30 — H.264 720p60 — H.264 SD 30 — H.264 CIF (from version 7.6) — H.263 CIF (from version 7.6) — H.
PAGE 38
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • Site (endpoint) names, skins, message overlay etc. are not supported in Video Switching. • Video forcing is enabled at the conference and participant levels. • To connect to a Video Switching conference via Entry Queue, the Profile assigned to the Entry Queue must be set to Video Switching. It is recommended to use the same profile for both the destination conference and Entry Queue.
PAGE 39
Chapter 2-Conference Profiles Table 2-3 Video Session Mode by Line Rate and Card type (Continued) Line Rate (kbps) MPM MPM+ MPMx 2560 3072 3584 Video Switching 4096 6144 Not Supported Video Switching AVC Conferencing Parameters Basic Conferencing Parameters When defining a new video Profile, you select the parameters that determine the video display on the participant’s endpoint and the quality of the video.
PAGE 40
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • Video Clarity - Video Clarity feature applies video enhancing algorithms to incoming video streams of resolutions up to and including SD. • Supported resolutions: — H.261 CIF/QCIF – Is supported in Continuous Presence (CP) conferences at resolutions of 288 x 352 pixels (CIF) and 144 x 176 pixels (QCIF). Both resolutions are supported at frame rates of up to 30 frames per second. — H.
PAGE 41
Chapter 2-Conference Profiles • — 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. Telepresence Mode (CP Conferences only) - enables the connection of numerous high definition telepresence rooms and of different models (such as TPX and RPX) into one conference maintaining the telepresence experience. This mode is enabled by a special license.
PAGE 42
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Default Profile Settings in CP Conferencing Mode The RMX is shipped with a default Conference Profile for CP conferences which allows users to immediately start standard ongoing CP conferences. These are also the default settings when creating a new Profile.
PAGE 43
Chapter 2-Conference Profiles Table 2-4 Default Conference Profile Settings (CP Licensing Mode) (Continued) Setting Value Auto Scan Interval Disabled (10) Auto Layout Enabled Echo Suppression Enabled Keyboard Noise Suppression Disabled Audio Clarity Enabled Mute participants except the lecturer Disabled Skin Polycom IVR Name Conference IVR Service Recording Disabled Site Names display Disabled Message Overlay Disabled Network Services - SIP Registration Disabled Network Services
PAGE 44
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide SVC-based Conferencing The SVC-Based conferencing mode provides video without transcoding by the MCU, hence requiring less video resources while providing better error resiliency and lower latency. Using the SVC video protocol, SVC conferences provide video bit streams at different resolutions, frame rates and line rates to SVC-enabled endpoints with various display capabilities and layout configurations.
PAGE 45
Chapter 2-Conference Profiles For instance, an SVC endpoint might want to receive three video streams at different frame rates and resolutions, and create a conference layout with the received video streams. Each SVC-enabled endpoint sends encoded SVC bit streams to the MCU to relay to the other SVC-enabled endpoints in the conference. The endpoints encode the video in multiple resolutions and decodes the multiple video input streams.
PAGE 46
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • Dial-in is available as follows: • — AVC endpoints (participants) can only connect to an AVC conference. When dialing into SVC Only conferences they will be disconnected and the calls fail. — SVC endpoints support both AVC and SVC video protocols. When dialing into SVC Only conferences, they connect as SVC endpoints. When dialing into AVC Only conferences, they connect as AVC endpoints.
PAGE 47
Chapter 2-Conference Profiles MCU Supported Resolutions for SVC Conferencing The MCU automatically selects the resolution and frame rate according to the conference line rate. Table 2-5 details the maximum resolution and frame rates supported by the MCU for each conference line rate. The actual video rate, resolution and frame rates displayed on each endpoints is determined by the endpoint’s capabilities.: Table 2-5 Polycom, Inc.
PAGE 48
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Viewing Profiles Conference Profiles are listed in the Conference Profiles list pane. To list Conference Profiles: 1 In the RMX Management pane, expand the Rarely Used list. 2 Click the Conference Profiles button. The Conference Profiles are displayed in the List pane. Profile Toolbar Profile List The number of the currently defined Conference Profiles appears in the title of the list pane.
PAGE 49
Chapter 2-Conference Profiles Table 2-6 Conference Profiles Pane Columns (Continued) Field Description Routing Name Displays the Routing Name defined by the user or automatically generated by the system. Encryption Displays if media encryption is enabled for the Profile. For more information see "Media Encryption (AVC Only)” on page 4-40.
PAGE 50
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Deleting a Conference Profile To delete a Conference Profile: 1 In the Conference Profiles list, select the Conference Profile you want to delete. 2 Click the Delete Profile ( ) button. or Right-click the Conference Profile to be deleted and select Delete Profile from the drop-down menu. A confirmation dialog box is displayed. 3 Click OK in the confirmation dialog box. 4 The Conference Profile is deleted.
PAGE 51
Chapter 2-Conference Profiles The following Profile Definition procedure assumes that the RMX is in MPMx Mode. Differences in the procedure that are affected by the Card Configuration Mode will be highlighted and explained as and when applicable. Defining AVC Conferencing Profiles To define a new Profile: 1 In the RMX Management pane, click Conference Profiles. 2 Polycom, Inc. In the Conference Profiles pane, click the New Profile button. The New Profile – General dialog box opens.
PAGE 52
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 3 Define the Profile name and, if required, the Profile - General parameters: Table 2-8 New AVC Profile - General Parameters Field/Option Description Display Name Enter a unique Profile name, as follows: • English text uses ASCII encoding and can contain the most characters (length varies according to the field). • European and Latin text length is approximately half the length of the maximum.
PAGE 53
Chapter 2-Conference Profiles Table 2-8 4 Polycom, Inc. New AVC Profile - General Parameters (Continued) Field/Option Description Video Switching If the Operator Conference option is selected, this option is disabled, and the selection is cleared. Select the video protocol and resolution for the conference. When selected, the conference is in a special conferencing mode which implies that all participants must connect at the same line rate and use the same video resolution.
PAGE 54
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The New Profile – Advanced dialog box opens. 5 Define the following parameters: Table 2-9 New AVC Profile - Advanced Parameters Field/Option Description Encryption Select the Encryption option for the conference: • Encrypt All - Encryption is enabled for the conference and all conference participants must be encrypted. • • No Encryption - Encryption is disabled for the conference.
PAGE 55
Chapter 2-Conference Profiles Table 2-9 New AVC Profile - Advanced Parameters (Continued) Field/Option Description LPR When selected (default for CP conferences), Lost Packet Recovery creates additional packets that contain recovery information used to reconstruct packets that are lost during transmission. LPR check box is automatically cleared if High Definition Video Switching is selected, but can be selected if required.
PAGE 56
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 2-9 New AVC Profile - Advanced Parameters (Continued) Field/Option Description TIP Compatibility Select the TIP Compatibility mode when implementing an RMX and Cisco Telepresence Systems (CTS) Integration solution. • None • • Video Only Video & Content The TIP Compatibility mode affects in the user video and content experience.
PAGE 57
Chapter 2-Conference Profiles 6 For CP Conferences only: Click the Gathering Settings tab. 7 Optional. Define the following fields if the conference is not launched by the Polycom Conferencing Add-in for Microsoft Outlook: • If the conference is launched by the Polycom Conferencing Add-in for Microsoft Outlook the field information is received from the meeting invitation and existing field value are overridden. For more information see "Polycom Conferencing for Microsoft Outlook®” on page 12-1.
PAGE 58
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 2-10 New AVC Profile - Gathering Settings Parameters Field Description Displayed Language Select the Gathering Phase slide language: Gathering Phase slide field headings are displayed in the language selected. The Gathering Phase slide can be in a different language to the RMX Web Client.
PAGE 59
Chapter 2-Conference Profiles 8 Click the Video Quality tab. The New Profile – Video Quality dialog box opens. 9 Define the following parameters: Table 2-11 New AVC Profile - Video Quality Parameters Field/Option Description People Video Definition Video Quality Depending on the amount of movement contained in the conference video, select either: • Motion – for a higher frame rate without increased resolution. When selected, Video Clarity is disabled.
PAGE 60
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 2-11 New AVC Profile - Video Quality Parameters (Continued) Field/Option Description Maximum Resolution This setting overrides the Maximum Resolution setting of the Resolution Configuration dialog box. The administrator can select one of the following Maximum Resolution options: • Auto (default) - The Maximum Resolution remains as selected in the Resolution Configuration dialog box.
PAGE 61
Chapter 2-Conference Profiles Table 2-11 New AVC Profile - Video Quality Parameters (Continued) Field/Option Description Content Video Definition Content Settings Select the transmission mode for the Content channel: • Graphics — basic mode, intended for normal graphics • Hi-res Graphics (AVC Only) — a higher bit rate intended for high resolution graphic display • • Live Video (AVC Only) — Content channel displays live video • H.
PAGE 62
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 10 Click the Video Settings tab. The New Profile - Video Settings dialog box opens. Site Names field is only displayed in MPM+ Mode 11 Define the video display mode and layout using the following parameters: Table 2-12 New AVC Profile - Video Settings Parameters Field/Option Description Presentation Mode Select this option to activate the Presentation Mode.
PAGE 63
Chapter 2-Conference Profiles Table 2-12 New AVC Profile - Video Settings Parameters (Continued) Field/Option Description Send Content to Legacy Endpoints When enabled (default), Content can be sent to H.323/SIP/ISDN endpoints that do not support H.239 Content (legacy endpoints) over the video (people) channel. For more information see Chapter 4, “Sending Content to Legacy Endpoints (AVC Only)” on page 4-17. Notes: • This option is enabled in MPM+ and MPMx Card Configuration Modes only.
PAGE 64
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 2-12 New AVC Profile - Video Settings Parameters (Continued) Field/Option Description Same Layout Select this option to force the selected layout on all participants in a conference. Displays the same video stream to all participants and personal selection of the video layout is disabled. In addition, if participants are forced to a video layout window, they can see themselves.
PAGE 65
Chapter 2-Conference Profiles Table 2-12 New AVC Profile - Video Settings Parameters (Continued) Field/Option Description Telepresence Layout Mode The Telepresence Layout Mode drop-down menu enables VNOC operators and Polycom Multi Layout Applications to retrieve Telepresence Layout Mode information from the RMX.
PAGE 66
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 12 To select the Video Layout for the conference, click the required number of windows from the layouts bar and then select the windows array. The selected layout is displayed in the Video Layout pane. Table 2-14 Video Layout Options Number of Video Windows Available Video Layouts 1 2 3 4 5+ 9 10+ Overlay For more information see "Overlay Layouts” on page 2-61.
PAGE 67
Chapter 2-Conference Profiles 13 Click the Audio Settings tab. The New Profile - Audio Settings dialog box opens. 14 Define the video display mode and layout using the following parameters: Table 2-15 New AVC Profile - Audio Settings Parameters Polycom, Inc. Field/Option Description Echo Suppression When enabled (default), an algorithm is used to search for and detect echo outside the normal range of human speech (such as echo) and automatically mute them when detected.
PAGE 68
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 2-15 New AVC Profile - Audio Settings Parameters (Continued) Field/Option Description Keyboard Noise Suppression Select this option to let the system use an algorithm to search for and detect keyboard noises and automatically mute them when detected. Notes: • This option is activated only in MPM+ and MPMx Card Configuration Modes. • Audio Clarity The CMA uses the Profiles that are stored in the RMX.
PAGE 69
Chapter 2-Conference Profiles Table 2-15 New AVC Profile - Audio Settings Parameters (Continued) Polycom, Inc. Field/Option Description Mute participant except lecturer When the Mute Participants Except Lecturer option is enabled, the audio of all participants in the conference except for the lecturer can be automatically muted upon connection to the conference.
PAGE 70
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 15 For CP Conferences only: Click the Skins tab to modify the background and frames. The New Profile - Skins dialog box opens. In Classic View (for the first two skin options) the frames fill the screen with their borders touching 16 Select one of the Skin options. When Telepresence Mode is enabled, the Skin options are disabled as the system uses a black background and the frames and speaker indication are disabled.
PAGE 71
Chapter 2-Conference Profiles The New Profile - IVR dialog box opens. 18 If required, set the following parameters: Table 2-16 New AVC Profile - IVR Parameters Field/Option Description Conference IVR Service The default conference IVR Service is selected. You can select another conference IVR Service if required.
PAGE 72
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The New Profile - Recording tab opens. 20 Define the following parameters: Table 2-17 New AVC Profile - Recording Parameters Parameter Description Enable Recording Select this check box to enable the Recording settings. If no Recording Links are found an error message is displayed. Recording Link Select the Recording Link to be used for conference recording.
PAGE 73
Chapter 2-Conference Profiles The Recording participant does not support H.264 High Profile. If recording a conference set to H.264 High Profile, the Recording participant connects as Audio Only and records the conference Audio. 21 For MPMx Card Configuration Mode and CP Conferences only: Click the Site Names tab to display the Site Names dialog box.
PAGE 74
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 22 Define the following parameters: Table 2-18 New AVC Profile - Site Names Parameters Field Description Display Mode Select the display mode for the site names: • Auto - Display the Site Names for 10 seconds whenever the Video Layout changes. • • On - Display the Site Names for the duration of the conference. Off (default) - Do not display the Site Names.
PAGE 75
Chapter 2-Conference Profiles Table 2-18 New AVC Profile - Site Names Parameters (Continued) Field Description Display Position Select the pre-set position for the display of the Site Names. Selection Site Names Position LeftTop (Default) Top RightTop LeftMiddle RightMiddle Polycom, Inc.
PAGE 76
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 2-18 New AVC Profile - Site Names Parameters (Continued) Field Description Display Position (cont.) LeftBottom Bottom RightBottom 2-44 Custom The current Site Names display position becomes the initial position for Site Names position adjustments using the Horizontal and Vertical Position sliders.
PAGE 77
Chapter 2-Conference Profiles Table 2-18 New AVC Profile - Site Names Parameters (Continued) Field Description Background Transparency Move the slider to the left to decrease the transparency of the background of the Site Names text. 0 = No transparency (solid background color). Move the slider to the right to increase the transparency of the background of the Site Names text. 100 = Full transparency (no background color) Default: 50 Note: This slider is only displayed if a Picture Skin is selected.
PAGE 78
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Message Overlay enables you to send text messages to all participants during ongoing Continuous Presence conferences. The text message is seen as part of the in the participant’s video layout on the endpoint screen or desktop display. For more details, see "Message Overlay for Text Messaging” on page 2-67.
PAGE 79
Chapter 2-Conference Profiles Table 2-19 New AVC Profile - Message Overlay Parameters (Continued) Field Description Color From the drop-down menu select the color and background of the Message Overlay display text. The choices are: MPMx Mode Color Options MPM+ Mode Color Options Default: White Text on Red Background. Vertical Position (MPMx Card Configuration Mode Only) Move the slider to the right to move the vertical position of the Message Overlay downward within the Video Layout.
PAGE 80
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide As the fields are modified the Preview changes to show the effect of the changes. For example: Small Text, White on red, Top, Middle Small Text, White on yellow, Bottom 24 Click the Network Services tab. The New Profile - Network Services tab opens.
PAGE 81
Chapter 2-Conference Profiles 25 Define the following parameters: Table 2-20 New AVC Profile - Network Services Parameters Parameter Description IP Network Services: Service Name This column lists all the defined Network Services, one or several depending on the system configuration. SIP Registration To register the conferencing entity to which this profile is assigned with the SIP Server of the selected Network Service, click the check box of that Network Service in this column.
PAGE 82
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Defining a Video Switching Conference Profile A Video Switching-enabled Profile must be created prior to running Video Switching conferences. Video Switching conferences and Meeting Rooms are created by selecting a Video Switching-enabled Profile and must be set to the same line rate as the target conference. To connect to an Video Switching conference via an Entry Queue, the Entry Queue must be Video Switching enabled.
PAGE 83
Chapter 2-Conference Profiles 3 Define the Profile name and, if required, the Profile - General parameters: Table 2-21 New AVC Profile (VSW) - General Parameters Field/Option Description Display Name Enter a unique Profile name, as follows: • English text uses ASCII encoding and can contain the most characters (length varies according to the field). • European and Latin text length is approximately half the length of the maximum.
PAGE 84
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 2-21 New AVC Profile (VSW) - General Parameters (Continued) Field/Option Description Video Switching If the Operator Conference option is selected, this option is disabled, and the selection is cleared. • Select this check box to create a Video Switching profile. • Then select the video protocol and resolution for the conference. Resolution supported by MPM media cards: • H.
PAGE 85
Chapter 2-Conference Profiles Table 2-21 New AVC Profile (VSW) - General Parameters (Continued) Field/Option Description Operator Conference (CP Only) Select this option to define the profile of an Operator conference. An Operator conference can only be a Continuous Presence conference, therefore when selected, the Video Switching option is disabled and cleared. When defining an Operator Conference, the Send Content to Legacy Endpoints option in the Video Settings tab is cleared and disabled.
PAGE 86
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • — Endpoints that do not support High Profile, connecting to the VSW conference at the exact line rate and exact resolution defined for the conference are connected to the conference as Secondary (audio only). For H.264 Base Profile VSW conferences: — High Profile supporting and non-High Profile supporting endpoints connect to the VSW conference using the H.264 Base Profile video protocol.
PAGE 87
Chapter 2-Conference Profiles Defining SVC Conferencing Profiles To define SVC Only Profile: 1 In the RMX Management pane, click Conference Profiles. 2 In the Conference Profiles pane, click the New Profile button. The New Profile – General dialog box opens. By default, the Profile is set to AVC Only Conferencing Mode. 3 Polycom, Inc. In the Conferencing Mode list, select SVC Only to define an SVC Profile.
PAGE 88
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The profile tabs and options change accordingly and only supported options are available for selection. Unsupported options are disabled (grayed out).
PAGE 89
Chapter 2-Conference Profiles Table 2-23 New SVC Profile - General Parameters (Continued) Field/Option Description Routing Name Enter the Profile name using ASCII characters set. The Routing Name can be defined by the user or automatically generated by the system if no Routing Name is entered as follows: • If an all ASCII text is entered in Display Name, it is used also as the Routing Name.
PAGE 90
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 6 Define the following supported parameters: Table 2-24 New SVC Profile - Advanced Parameters 2-58 Field/Option Description Auto Terminate When selected (default), the conference automatically ends when the termination conditions are met: Before First Joins — No participant has connected to a conference during the n minutes after it started. Default idle time is 10 minutes.
PAGE 91
Chapter 2-Conference Profiles 7 Click the Video Quality tab. The New Profile – Video Quality dialog box opens. 8 Define the following parameters: Table 2-25 New SVC Profile - Video Quality Parameters Field/Option Description Content Video Definition 9 Polycom, Inc. Content Settings Only Graphics is available in SVC Conferencing Mode for transmission of Content. It offers the basic mode, intended for normal graphics For more information, see "H.239” on page 4-2. Content Protocol H.
PAGE 92
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The New Profile - Network Services tab opens. Registration of conferencing entities such as ongoing conferences, Meeting Rooms, and SIP Factories with SIP servers is done per conferencing entity. This allows better control of the number of entities that register with each SIP server.
PAGE 93
Chapter 2-Conference Profiles Table 2-26 New SVC Profile - Network Services Parameters (Continued) Parameter Description Accept Calls To prevent dial in participants from connecting to a conferencing entity when connecting via a Network Service, clear the check box of the Network Service from which calls cannot connect to the conference. 11 Click OK to complete the Profile definition. A new Profile is created and added to the Conference Profiles list.
PAGE 94
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • Overlay Layouts are not selected as defaults by the system. Default layouts are selected as in previous versions and are described in detail in "Auto Layout – Default Layouts” on page 2-33. • The Overlay Layouts are not available for selection when using PCM or Click&View for Personal Layout selection. PCM menus are not affected by the use of Overlay Layouts and are displayed as the top level overlay.
PAGE 95
Chapter 2-Conference Profiles Selecting the Overlay Layouts The Overlay Layouts are selected using the New Profile - Video Settings dialog box. An additional tab, Overlay, has been added and includes the additional layout options. New Tab: Overlay 1 Standalone Endpoint 3 Standalone Endpoints 2 Standalone Endpoints 1 ITP Room ITP Room Names Displayed in Drop-down Menu Polycom, Inc.
PAGE 96
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Site Names Definition Using the Site Name dialog box, you can control the display of the site names by defining the font, size, color, background color and transparency and position within the Video Window. Site Names without Background (Plain Skin) Site Names with Background (Picture Skin) Guidelines • Only MPMx cards are supported. • Site Names display is Off by default in a new profile.
PAGE 97
Chapter 2-Conference Profiles — Picture Skins - Site Names text is displayed with a background. Plain Skins Picture Skins • In MPMx Card Configuration Mode, the Site Names tab options replace the functionality of the System Flags that were used in versions 7.6 and earlier (as for MPM+).
PAGE 98
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • Selecting a preset position from the drop-down menu in the Display Position field. • Moving the Horizontal and Vertical Position sliders. • Selecting Custom and moving the Horizontal and Vertical Position sliders. Selecting a preset position from the drop-down menu in the Display Position field >> In the Display Position drop-down menu select a preset position for Site Names display.
PAGE 99
Chapter 2-Conference Profiles Message Overlay for Text Messaging Message Overlay allows the operator or administrator to send text messages to a single, several or all participants during an ongoing conference. The text message is seen as part of the in the participant’s video layout on the endpoint screen or desktop display.
PAGE 100
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • Participants that have their video suspended do not receive Message Overlays messages. • Message Overlay text messages cannot be sent via the Content channel. • Message Overlay messages are not displayed when the PCM menu is active. • Message Overlay text settings are not saved in the Conference Template when saving an ongoing conference as a Conference Template.
PAGE 101
Chapter 2-Conference Profiles Chinese Font Types On an RMX with an MPMx card a user can select one of several Chinese fonts for use when sending text over video. New fonts can be selected with the following features: • Site Names • Message Overlay • Gathering Phase Slide New Chinese fonts available are: • Heiti (Default) • Songti • Kaiti • Weibei This feature has the following restrictions: Polycom, Inc. • Supported on an RMX with an MPMx card(s).
PAGE 102
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • A participant moved to another conference will be shown the font used by the new conference, even if the conferences use different fonts. Exporting and Importing Conference Profiles Conference Profiles can be exported from one MCU and imported to multiple MCUs in your environment, enabling you to copy the Conference Profiles definitions to other systems.
PAGE 103
Chapter 2-Conference Profiles 3 Click the Export Conference Profiles button or right-click the Conference Profiles pane, and then click Export Conference Profiles. The Conference Profile - Export dialog box is displayed. 4 In the Export Path field, click Browse to navigate to the location of the desired path where you want to save the exported file. 5 In the Profiles file name field, type the file name prefix. The file name suffix (_confProfiles.xml) is predefined by the system.
PAGE 104
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The Conference Profile - Export dialog box is displayed. 3 In the Export Path field, click Browse to navigate to the location of the desired path where you want to save the exported file. 4 In the Profiles file name field, type the file name prefix. The file name suffix (_confProfiles.xml) is predefined by the system. For example, if you type Profiles01, the exported file name is defined as Profiles01_confProfiles.xml.
PAGE 105
Chapter 2-Conference Profiles 3 Click the Import Conference Profiles button or right-click the Conference Profiles pane, and then click Import Conference Profiles. The Conference Profile - Import dialog box is displayed. 4 In the Import Path field, click Browse to navigate to the path and file name of the exported Conference Profiles you want to import. 5 Click OK to import the Conference Profiles.
PAGE 106
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 2-74 Polycom, Inc.
PAGE 107
3 Video Protocols and Resolution Configuration for CP Conferencing Video Resolutions in AVC-based CP Conferencing The following video resolution information applies to AVC Conferencing Mode. For a description of resolutions for SVC Conferencing Mode see "The simulcast media streams supported by the MCU are called operation points and they are fixed for all the SVC conferences. The MCU automatically selects the operation points according to the conference line rate.
PAGE 108
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Video Display with CIF, SD and HD Video Connections Although any combination of CIF, SD and HD connections is supported in all CP conferences, the following rules apply: • In a 1X1 Video Layout: • — SD: 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 participant’s sending resolution.
PAGE 109
Chapter 3-Video Protocols and Resolution Configuration for CP Conferencing • • — For Content Sharing — As an RSS Recording link — With Video Preview HD1080p60 is supported — In Continuous Presence (CP) mode: • At bit rates of up to 4Mbps. • HD1080p60 is supported asymmetrically: The RMX receives HD720p60 and sends HD1080p60. • HD1080p60 is only selectable when Video Quality is set to Motion. System behavior when Video Quality is set to Sharpness is unchanged.
PAGE 110
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The creation of a new H.263 4CIF slide is supported in the IVR Service in addition to the current H.263 IVR slide. If users utilize the default Polycom slides that are delivered with RMX 1500/2000/4000, the slide’s resolution will be as defined in the profile, i.e. SD, HD, CIF, etc. For more information see “High Resolution Slides” on page 17-16. H.263 4CIF Guidelines • H.263 4CIF is supported with H.
PAGE 111
Chapter 3-Video Protocols and Resolution Configuration for CP Conferencing • Video Quality Optimized Video is optimized through higher resolution connections at lower line rates increasing the resource usage at lower line rates. This may decrease the number of participant connections. Video Resource Usage Video resource usage is dependent on the participant’s line rate, resolution and Video Quality settings. H.
PAGE 112
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Figure 3-2 Resolutions used per Line Rates When Resolution Configuration is set to ResourceQuality Balanced Configuration in Sharpness and Motion Mode, MPMx Figure 3-3 Resolutions used per Line Rates When Resolution Configuration is set to Resource Optimized Configuration in Sharpness and Motion Mode, MPM+ 3-6 Polycom, Inc.
PAGE 113
Chapter 3-Video Protocols and Resolution Configuration for CP Conferencing Figure 3-4 Resolutions used per Line Rates When Resolution Configuration is set to Resource Optimized Configuration in Sharpness and Motion Mode, MPMx Figure 3-5 Resolutions used per Line Rates When Resolution Configuration is set to Quality Optimized Configuration in Sharpness and Motion Mode, MPM+ Polycom, Inc.
PAGE 114
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Figure 3-6 Resolutions used per Line Rates When Resolution Configuration is set to Quality Optimized Configuration in Sharpness and Motion Mode, MPMx 3-8 Polycom, Inc.
PAGE 115
Chapter 3-Video Protocols and Resolution Configuration for CP Conferencing H.264 High Profile Decision Matrices (MPMx) The following illustrations show the resolutions used for the various Line Rates for each of the pre-defined optimization settings for H.264 High Profile and Video Quality setting Sharpness and Motion for MPMx Card Configuration Mode.
PAGE 116
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Figure 3-9 Resolutions used per Line Rates When Resolution Configuration is set to Resource Optimized Configuration in Sharpness and Motion Mode, MPMx H.264 Base Profile and High Profile Comparison The following illustrations show a comparison between the resolutions used at various line rates for H.264 baseline and the H.
PAGE 117
Chapter 3-Video Protocols and Resolution Configuration for CP Conferencing Figure 3-11Resolution usage for H.264 High Profile and H.264 Base Profile for Motion at various line rates when Resolution Configuration is set to Video Quality Optimized Figure 3-12Resolution usage for H.264 High Profile and H.264 Base Profile for Motion at various line rates when Resolution Configuration is set to Resource Optimized Polycom, Inc.
PAGE 118
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Default Minimum Threshold Line Rates and Resource Usage Summary The following Table summarizes the Default Minimum Threshold Line Rates and Video Resource usage for each of the pre-defined optimization settings for each Resolution, H.264 Profile, Video Quality setting (Sharpness and Motion) for MPM, MPM+ and MPMx Card Configuration Modes. • • The table above lists resource consumption for H.264. For H.
PAGE 119
Chapter 3-Video Protocols and Resolution Configuration for CP Conferencing Resolution Configuration for CP Conferences The Resolution Configuration dialog box enables RMX administrators to override the default video resolution decision matrix, effectively creating their own decision matrix. The minimum threshold line rates at which endpoints are connected at the various video resolutions can be optimized by adjusting the resolution sliders.
PAGE 120
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Modifying the Resolution Configuration in MPM or MPM+ Card Configuration Mode The Resolution Configuration dialog box shown below is displayed when the RMX is in MPM, MPM+ or MPMx Card Configuration Mode. The Resolution Configuration dialog box opens.
PAGE 121
Chapter 3-Video Protocols and Resolution Configuration for CP Conferencing Limiting Maximum Resolution Before a selection is made in this pane, the Maximum CP Resolution of the system is determined by the MAX_CP_RESOLUTION System Flag. The MAX_CP_RESOLUTION flag value is applied to the system during First Time Power-on and after a system upgrade. The default value is HD1080p60. All subsequent changes to the Maximum CP Resolution of the system are made by selections in this pane.
PAGE 122
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • Video Quality Optimized Video is optimized through higher resolution connections at lower line rates increasing the resource usage at lower line rates. This may decrease the number of participant connections. Use this option when the priority is to use higher video resolutions while decreasing the number of participant connections.
PAGE 123
Chapter 3-Video Protocols and Resolution Configuration for CP Conferencing Modifying the Resolution Configuration in MPMx Card Configuration Mode The Resolution Configuration - Basic Configuration dialog box is the first dialog box displayed when the RMX is in MPMx Card Configuration Mode. Clicking the Detailed Configuration button toggles the display of the Detailed Configuration pane, which displays sliders for modifying minimum connection threshold line rates for endpoints that support H.
PAGE 124
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Maximum CP Resolution Pane In MPMx Card Configuration Mode the RMX can be set to one of the following Maximum CP Resolutions: • HD 1080p60 • HD 1080p30 • HD 720p30 • SD 30 • CIF 30 Limiting Maximum Resolution Before a selection is made in this pane, the Maximum CP Resolution of the system is determined by the MAX_CP_RESOLUTION System Flag. For more information see "Limiting Maximum Resolution” on page 3-15.
PAGE 125
Chapter 3-Video Protocols and Resolution Configuration for CP Conferencing • Base Profile - Endpoints that do not support H.264 High Profile connect at these minimum threshold bit rates. • High Profile - Endpoints that support H.264 High Profile connect at these minimum threshold bit rates. Although the default minimum threshold bit rates provide acceptable video quality, the use of higher bit rates usually results in better video quality.
PAGE 126
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Minimum Frame Rate Threshold for SD Resolution The MINIMUM_FRAME_RATE_THRESHOLD_FOR_SD System Flag can be added and set to prevent low quality, low frame rate video from being sent to endpoints by ensuring that an SD channel is not opened at frame rates below the specified value. For more information see "Modifying System Flags” on page 22-1. H.264 High Profile System Flags (Version 7.0.
PAGE 127
Chapter 3-Video Protocols and Resolution Configuration for CP Conferencing Endpoints will connect at resolutions as set out in the following table, depending on whether they support H.
PAGE 128
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide — With H.323, SIP and ISDN endpoints. H.323 endpoints must identify themselves as Tandberg MXP during capabilities exchange. — In all Video Layouts. — In 1x1 Layout: • When Video Clarity is Off, the RMX transmits the same resolution as it receives. • When Video Clarity is On, the RMX changes the transmitted resolution to w448p. For more information see page 2-9.
PAGE 129
Chapter 3-Video Protocols and Resolution Configuration for CP Conferencing * It is recommend to set the endpoint to Motion to ensure the transmission of the higher frame rates of 25fps/30fps to the RMX. ‡ MXP 990/3000 endpoints transmit 576x448 pixels. Other MXP endpoints may transmit other resolutions eg. CIF. Content Sharing and receiving Content is supported. Bandwidth allocated to the Content channel during Content sharing may cause the video resolution to be decreased as from w448p to w288p.
PAGE 130
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide RMX Profile Setting • On the RMX, the Video Quality field in the New Profile - Video Quality dialog box must be set to Sharpness. For more information see , "Defining New Profiles” on page 2-18.
PAGE 131
Chapter 3-Video Protocols and Resolution Configuration for CP Conferencing • HD720p30 resolution is supported at bit rates greater than 600 kbps. The following table summarizes the resolutions supported at the various bit rates. Table 3-4 RTV - Resolution by Bit Rate Resolution QCIF Bitrate Bitrate <180kbps CIF30 180kbps < Bitrate < 250kbps VGA (SD30) 250kbps < Bitrate < 600kbps * 600kbps < Bitrate * HD720p30 * Dependant on the PC’s capability • System Resource usage is the same as for the H.
PAGE 132
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Participant Settings When defining a new participant or modifying an existing participant, select SIP as the participant’s networking environment Type in the New Participant or Participant Properties General tab. SIP The participants Video Protocol in the New Participant or Participant Properties - Advanced tab should be left at (or set to) its default value: Auto.
PAGE 133
Chapter 3-Video Protocols and Resolution Configuration for CP Conferencing Monitoring RTV RTV information appears in all three panes of the Participant Properties - SDP tab. Controlling Resource Allocations for Lync Clients Using RTV Video Protocol The number of resources used by the system to connect a Lync client with RTV is determined according to the conference line rate and the Maximum video resolution set in the Conference Profile. In versions 7.
PAGE 134
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide To change the default flag setting, add the MAX_RTV_RESOLUTION flag to the System Configuration flags and set its value. For information, see . The following table summarizes the RMX resources allocated to a Lync Client based on the MAX_RTV_RESOLUTION flag setting, the connection line rate and the video resolution.
PAGE 135
Chapter 3-Video Protocols and Resolution Configuration for CP Conferencing The following table describes the number of allocated video resources for each video resolution when using the RTV protocol. Table 3-7 Allocated video resolutions per video resolution Selected Video Resolution Number of Allocated Video Resources HD720p 3 VGA 1.
PAGE 136
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 3-30 Polycom, Inc.
PAGE 137
4 Additional Conferencing Information Various conferencing modes and video features require additional settings, such as system flag settings, conference parameters and other settings. In depth explanations of these additional settings are described in the following sections: • "H.
PAGE 138
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide H.239 / People+Content H.239 The H.
PAGE 139
Chapter 4-Additional Conferencing Information • Video endpoints that do not support SIP Content (such as PVX), can receive Content on the People channel if the conference is set to Send Content to Legacy Endpoints. For more details see, "Sending Content to Legacy Endpoints (AVC Only)” on page 4-17.
PAGE 140
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The RMX’ s Content sharing determined by the System Flag’s settings and SIP Client capabilities are summarized in Table 4-1. Table 4-1 System Flag - SIP_BFCP_DIAL_OUT_MODE SIP Client: BFCP Support Flag Value UDP AUTO (Default) UDP TCP BFCP/UDP selected as Content sharing protocol. Cannot share Content. TCP BFCP/TCP selected as Content sharing protocol. Cannot share Content.
PAGE 141
Chapter 4-Additional Conferencing Information Defining Content Sharing Parameters for a Conference Content parameters are defined in the Conference Profiles - Video Quality dialog box. The parameters change according to the Conferencing Mode. AVC Conferencing Mode SVC Conferencing Mode Polycom, Inc.
PAGE 142
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 1 In the Content Video Definition section, select the Content Settings and Protocol as follows: Table 4-2 H.
PAGE 143
Chapter 4-Additional Conferencing Information Content Settings The Content channel can transmit one of the following modes: • Graphics – for standard graphics. This is the default mode in AVC conferences and the only supported mode for SVC conferences. • Hi-res Graphics (AVC only conferences) – requiring a higher bit rate, for high quality display or highly detailed graphics. • Live Video (AVC only conferences) – highest bit rate, for video clips or live video display.
PAGE 144
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 4-4 summarizes the Maximum Resolution of Content and Frames per Second (fps) for Bit Rate Allocations to the Content Channel as set out in Table 4-3. Table 4-4 Content - Maximum Resolution, Frames/Second per Bit Rate Allocation Bit Rate Allocated to Content Channel (Kbps) Content Maximum Resolution Frames/Second From 64 and less than 512 H.264 HD720p 5 From 512 and less than 768 H.
PAGE 145
Chapter 4-Additional Conferencing Information • Endpoints that do not have at least H.263 capability can connect to the conference but cannot share Content. • This option is not available in SVC Conferencing Mode. H.263 (AVC Only Conferences) Select this option when most of the endpoints support H.263 and some endpoints support H.264. In such a case, all endpoints will share content using the H.263 protocol, and this protocol will not change throughout the conference (fix mode).
PAGE 146
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide A System Flag determines the minimum line rate for each Content Setting: • Graphics • Hi Resolution Graphics • Live Video In order to change the System Flag values, the flags must be manually added to the System Configuration. For more information see "Modifying System Flags” on page 22-1. Table 4-5 H.
PAGE 147
Chapter 4-Additional Conferencing Information H.264 Cascade and SVC Optimized The H.264 Cascade and SVC Optimized option maintains content quality and minimizes the amount of content refreshes that occur in large cascading conferences when participants connect or disconnect from the conference. This option is the only available option automatically selected in SVC Only conferences . The H.264 Cascade and SVC Optimized option uses fixed resolution and frame rate for SVC Only conferences.
PAGE 148
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The Cascade Resolution is a fixed resolution and frame rate for Content sharing in a Cascaded Conference. The Cascade Resolutions that are available for selection are dependent on the Line Rate and Content Settings that have been selected for the conference. AVC Conferencing Mode Table 4-7 summarizes the interaction of these parameters.
PAGE 149
Chapter 4-Additional Conferencing Information Table 4-7 Bit Rate Allocation to Content Channel by Line Rate, Content Settings & Cascade Resolution in AVC Conferencing (Continued) Content Bit Rate Allocation per Conference Line Rate (kbps) Content Settings Cascade Resolution/ fps HD720/5 Live Video 64 96 128 256 384 256 512 384 HD720/30 768 823 1024 1152 1472 1728 1920 2048 4096 6144 512 768 768 768 768 512 768 768 768 768 768 768 1152 1152 HD1080/15 The selection of the approp
PAGE 150
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • If the Content Settings selection is Hi Resolution Graphics. — Only HD720/5 can be selected as the Cascade Resolution with 384 kbps allocated as the conference Content Rate. Only endpoints that connect at a Line Rate of 1024 kbps that is required to support a Content Rate of 384 kbps will receive content in the Content channel.
PAGE 151
Chapter 4-Additional Conferencing Information To Select the Customized Content Rate: Customized Content Rate is enabled in the Profile - Video Quality dialog box. 1 In the Content Settings list, select Customized Content Rate. When selected, a drop-down menu of the available Conference Content Rates is displayed. These Content Line Rates are based on and will vary according to the selected Conference Line Rate. The largest selectable Content Line Rate is 66% of the Conference Line Rate.
PAGE 152
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide If H.264 Cascade and SVC Optimized is the selected Content Protocol, a Cascade Resolution must be selected. 3 Table 4-8 lists the Cascade Resolutions available for the various Conference Content Rates. Table 4-8 H.264 Cascade Optimized - Cascade Resolutions H.
PAGE 153
Chapter 4-Additional Conferencing Information 2 In the MCMS_PARAMETERS tab, double-click the MIN_H239_HD1080_RATE entry. The Update Flag dialog box is displayed. 3 In the Value field, enter the minimum line rate at which HD1080 Resolution Content will be enabled. 4 — Enter 0 to disable this flag and prevent HD Content from being used. Click OK to confirm and exit the Update Flag dialog box. 5 Click Close to exit the System Flags dialog box.
PAGE 154
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide As the resource required for sending Content to legacy endpoints is allocated on the fly, when scheduling a reservation, in rare occasions when the MCU is fully loaded, “Resource deficiency” may be encountered. This may prevent participants from connecting to the conference or from Content being sent to the legacy endpoint.
PAGE 155
Chapter 4-Additional Conferencing Information The RMX user can also change the layout for the participants the legacy endpoints (selecting personal layout). When forcing a video participant to the Content window (instead of Content), the Content display can be restored only by selecting any other video layout. Interoperability with Polycom CMA and DMA The CMA uses the Profiles that are stored in the RMX.
PAGE 156
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Note: Select this option when Avaya IP Softphone will be connecting to the conference. Changing the Default Layout for Displaying Content on Legacy Endpoints The default layout that will be used to display Content on the screens of legacy endpoints is defined by the system flag LEGACY_EP_CONTENT_DEFAULT_LAYOUT. The configured default layout is 1+4 ( CP_LAYOUT_1P4VER).
PAGE 157
Chapter 4-Additional Conferencing Information Table 4-9 LEGACY_EP_CONTENT_DEFAULT_LAYOUT Flag Values (Continued) Layout Flag Value CP_LAYOUT_1P4HOR CP_LAYOUT_1P4VER CP_LAYOUT_1P5 CP_LAYOUT_1P7 CP_LAYOUT_1P8UP CP_LAYOUT_1P8CENT CP_LAYOUT_1P8HOR_UP CP_LAYOUT_3X3 CP_LAYOUT_2P8 CP_LAYOUT_1P12 CP_LAYOUT_4X4 4 Click OK. The flag is updated in the MCMS_PARAMETERS list. 5 Click OK. For flag changes (including deletion) to take effect, reset the MCU.
PAGE 158
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • The Exclusive Content Mode is enabled or disabled by a check box in the in the Advanced tabs of the Conference Profile. The check box is cleared (feature is disabled) by default. AVC Conference Profile - Advanced SVC Conference Profile Advanced • Exclusive Content Mode can be enabled or disabled during an ongoing conference using the Conference Properties - Advanced dialog box.
PAGE 159
Chapter 4-Additional Conferencing Information • • — YES - only the designated Lecturer can be the Content Token holder. The Exclusive Content Mode check box replaces the EXCLUSIVE_CONTENT_ MODE System Flag which was used to control Exclusive Content Mode for the system in previous versions.
PAGE 160
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • In cascaded conferences, a participant functioning as the cascade link cannot be given token ownership. Giving and Cancelling Token Ownership To give token ownership: 1 In the Participants list, right click the endpoint that is to receive Content Token ownership. 2 Select Change To Content Token Owner in the drop-down menu.
PAGE 161
Chapter 4-Additional Conferencing Information To cancel token ownership: 1 In the Participants list, right click the endpoint that currently has Content Token ownership. 2 Select Cancel Content Token Owner in the drop-down menu. Content Token ownership is cancelled for the endpoint. Managing Noisy Content Connections The system can identify participants who send frequent requests to refresh their Content display usually as a result of a problematic network connection.
PAGE 162
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Enter the interval in seconds between the Intra requests sent from the RMX to the endpoint sending the Content to refresh the Content display. Refresh requests that will be received from endpoints within the defined interval will be postponed to the next interval. Default setting: 5 Forcing Other Content Capabilities • The H239_FORCE_CAPABILITIES System Flag in system.
PAGE 163
Chapter 4-Additional Conferencing Information • Only one preview window can be displayed for a single conference and up to four preview windows can be displayed for each media card on different workstations (one per workstation and one per conference). For example, if the RMX contains two media cards, and there are 5 conferences running on the RMX, if five conferences are running on the same media card, only four conferences can be previewed from four different workstations.
PAGE 164
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 3 Click Yes to run the diagnostics. The DirectX Diagnostic Tool dialog box opens. 4 Click the Display tab. To be able to display the video preview window, the DirectDraw Acceleration and Direct3D Acceleration options must be Enabled. If the video card installed in the PC does not support DirectDraw Acceleration, a black window may be viewed in the Video Preview window. 5 4-28 Click the Exit button. Polycom, Inc.
PAGE 165
Chapter 4-Additional Conferencing Information Previewing the Participant Video To preview the participant video: 1 List the conference participants in the Participants pane. 2 Right-click the participant whose video you want to preview and then click one of the following options: — View Participant Sent Video - to display the video sent from the participant to the conference. — View Participant Received Video - to display the video sent from the conference to the participant.
PAGE 166
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Gathering Phase The Gathering Phase of an AVC (CP only) conference is the time period during which participants are connecting to a conference. During the Gathering Phase, a mix of live video from connected endpoints is combined with both static and variable textual information about the conference into a slide which is displayed on all connected endpoints.
PAGE 167
Chapter 4-Additional Conferencing Information Gathering Phase Guidelines • Gathering Phase is only available in AVC only (CP only) conferences. It is not supported in Video Switching conferences and SVC Only conferences. • The Gathering Phase slide can be displayed at any time during the conference by entering the Show Participants DTMF code, *88. Note: When the display of the Gathering Phase slide is removed, the message overlay text is also removed.
PAGE 168
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Gathering Phase Duration The duration of the Gathering Phase can be customized by the administrator so that it is long enough to be viewed by most connected participants yet short enough so as not to over extend into the scheduled conferencing time. The Gathering Phase duration is configured for the RMX, by the following System Flags in system.
PAGE 169
Chapter 4-Additional Conferencing Information Auto Scan and Customized Polling in Video Layout Auto Scan enables a user to define a single cell in the conference layout to cycle the display of participants that are not in the conference layout. Customized Polling allows the cyclic display to be set to a predefined order for a predefined time period. The cyclic display only occurs when the number of participants is larger than the number of cells in the layout.
PAGE 170
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 3 In the video layout cell to be designated for Auto Scan, click the drop-down menu button and select Auto Scan. 4 Select from the Auto Scan Interval(s) drop-down list the scanning interval in seconds. 5 Click the Apply button to confirm and keep the Conference Properties dialog box open. -orClick OK to confirm and close the Conference Properties dialog box.
PAGE 171
Chapter 4-Additional Conferencing Information The dialog box buttons are summarized in Table 4-10. Table 4-10 Customized Polling - Buttons Button Description Add Select a participant and click this button to Add a the participant to the list of participants to be Auto Scanned. The participants name is removed from the All Participants pane. Delete Select a participant and click this button to Delete the participant from the list of participants to be Auto Scanned.
PAGE 172
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The SirenLPR audio algorithm provides CD-quality audio for better clarity and less listener fatigue with audio and visual communication applications. In SVC conferences, the system supports SAC (Scalable Audio Coding) audio algorithm. Guidelines • Siren 22, G.719 and Siren 22Stereo are supported with MPM+ and MPMx cards. • Siren 22 and G.719 are supported in both mono and stereo. • Stereo is supported in H.
PAGE 173
Chapter 4-Additional Conferencing Information Table 4-11 Siren22, G.719 and SirenLPR Mono vs Bitrate (Continued) Audio Algorithm Minimum Bitrate (kbps) Siren22_48K Siren22_32k G.719_48k 256 G.719_32k G.728 16 Siren22_32k G.719_32k 128 G.728 16K SirenLPR 64 SirenLPR 48 SirenLPR 32 Stereo The Siren 22Stereo, G.719Stereo and SirenLPR audio algorithms are supported at the following bit rates. Table 4-12 Siren22Stereo, G.
PAGE 174
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Audio algorithms supported for ISDN Table 4-13 Supported Audio Algorithm vs Bitrate Audio Algorithm Minimum Bitrate (kbps) G.722.1C 48K G.722.1C 32K G.722.1C 24K Siren14 48K Siren14 32K 256 Siren14 24K G.722.1 32K G.722.1 24K G.722.1 16K G.722 48K G.722 56K G.722 64K 256 G.711 56K G.711 64K G.728 16K G.722.1C 32K G.722.1C 24K Siren14 32K Siren14 24K G.722.1 32K G.722.1 24K G.722 48K 128 G.722 56K G.722 64K G.
PAGE 175
Chapter 4-Additional Conferencing Information Table 4-13 Supported Audio Algorithm vs Bitrate (Continued) Audio Algorithm Minimum Bitrate (kbps) G.722.1 16K G.722.1C 24K Siren14 24K G.722 48K G.722 56K 96 G.722 64K G.711 56K G.711 64K G.728 16K G.728 16K 64 Monitoring Participant Audio Properties The audio algorithm used by the participant’s endpoint can be verified in the Participant Properties - Channel Status dialog box.
PAGE 176
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 3 In the Channel Info field, select Audio In or Audio Out to display the audio parameters. 4 Click the OK button. Media Encryption (AVC Only) Encryption is available at the conference and participant levels, based on AES 128 (Advanced Encryption Standard) and is fully H.233/H.234 compliant and the Encryption Key exchange DH 1024-bit (Diffie-Hellman) standards.
PAGE 177
Chapter 4-Additional Conferencing Information • Media Encryption for ISDN/PSTN participants is implemented in RMX systems with MPM+ and MPMx cards. • Conference level encryption must be set in the Profile, and cannot be changed once the conference is running. • If an endpoint connected to an encrypted conference stops encrypting its media, it is disconnected from the conference.
PAGE 178
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The option “Encrypt When Possible” enables the negotiation between the MCU and the endpoints and let the MCU connect the participants according to their capabilities, where encryption is the preferred setting. Defined participants that cannot connect encrypted are connected non-encrypted, with the exception of dial-out SIP participants.
PAGE 179
Chapter 4-Additional Conferencing Information Table 4-14 Connection of Defined and Undefined H.323, SIP and ISDN Participants to the Conference Based on the Encryption Settings (Continued) Defined Participant Conference Encryption Setting Encrypt All Encrypt When Possible Encryption Setting Connection status Auto Connected, encrypted.
PAGE 180
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 4-15 Connection of Undefined Participants to the Entry Queue Based on the Encryption Settings (Continued) Entry Queue Encryption Setting Undefined Participant Connection to the Entry Queue *Flag = No *Flag = YES Encrypt All Connected only if encrypted. Non-encrypted endpoints are disconnected Connected only if encrypted.
PAGE 181
Chapter 4-Additional Conferencing Information Recording Link Encryption Recording Links are treated as regular participants, however the ALLOW_NON_ENCRYPT_RECORDING_LINK_IN_ENCRYPT_CONF System Flag must be set to YES if a non-encrypted Recording Link is to be allowed to connect to an encrypted conference. Table 4-17 summarizes the connection possibilities for a Recording Link that is to be connected to a conference for each of the conference profile and Entry Queue encryption options.
PAGE 182
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Encryption Flag Settings To modify the Encryption flags: 1 Click Setup>System Configuration. The System Flags dialog box opens. 2 In Version 7.6.1 and later: Set the FORCE_ENCRYPTION_FOR_UNDEFINED_PARTICIPANT_IN_WHEN_AVAILA BLE_MODE flag to YES or NO. In Version 7.6 and earlier: Set the ALLOW_NON_ENCRYPT_PARTY_IN_ENCRYPT_CONF flag to YES or NO.
PAGE 183
Chapter 4-Additional Conferencing Information Enabling Encryption in the Profile Encryption for the conference is in the Profile and cannot be changed once the conference is running. To enable encryption at the conference level: >> In the Conference Profile Properties – Advanced dialog box, select one of the following Encryption options: — Encrypt All - Encryption is enabled for the conference and all conference participants must be encrypted. — No Encryption - Encryption is disabled for the conference.
PAGE 184
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide To enable encryption at the participant level: >> In the Participant Properties – Advanced dialog box, in the Encryption list, select one of the following options: Auto, On, or Off. — Auto - The participant inherits the conference/Entry Queue encryption setting. The participant connects as encrypted only if the conference is defined as encrypted. — Yes - The participant joins the conference/Entry Queue as encrypted.
PAGE 185
Chapter 4-Additional Conferencing Information Monitoring the Encryption Status The conference encryption status is indicated in the Conference Properties - General dialog box. The participant encryption status is indicated by a check mark in the Encryption column in the Participants list pane. The participant encryption status is also indicated in the Participant Properties – SDP tab, where SRTP indication is listed for each encrypted channel (for example, audio and video).
PAGE 186
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide For more information about monitoring, see "Conference and Participant Monitoring” on page 13-1. Packet Loss Compensation (LPR and DBA) Lost Packet Recovery (LPR) and Dynamic Bandwidth Allocation (DBA) help minimize media quality degradation that can result from packet loss in the network. Packet loss Compensation is available in AVC Conferencing Mode only and is not supported in SVC Conferencing Mode.
PAGE 187
Chapter 4-Additional Conferencing Information • In LPR-enabled Video Switched conferences: • — H.323 and SIP endpoints are supported. — When cascading between conferences running on RMX and MGC (Polycom legacy MCU), LPR is not supported over the link between the two conferences. — Non-H.323 participants cannot be created, added or moved to LPR-enabled Video Switched conferences.
PAGE 188
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide In the Participant Properties – Channel Status tab, check box indicators show LPR activation in the local and remote (transmit and receive) channels. Network Quality Indication (AVC Only) If network quality issues occur, Network Quality Indicators provide information to participants about their own network quality and that of other participants displayed in the cells of the conference Video Layout.
PAGE 189
Chapter 4-Additional Conferencing Information Guidelines Network Quality Indicators are displayed for: • The Video Channel only in AVC Conferencing Mode. Content, Audio and FECC Channel quality issues are not indicated. • The participant’s own endpoint: • — Network Quality Indicators are displayed by default and can be disabled — For media transmitted to and received from the RMX (Video in / Video out).
PAGE 190
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 4-18 Network Quality Indicator - Indication Threshold Flags (Continued) Flag Description NETWORK_IND_CRITICAL_PERCENTAGE The percentage degradation due to packet loss required to change the indicator from Major to Critical. Default: 5 For more information see "Manually Adding and Deleting System Flags” on page 22-18.
PAGE 191
Chapter 4-Additional Conferencing Information Table 4-19 Network Quality Indicator - Display Customization Flags (Continued) Flag Description CELL_IND_LOCATION Change the location of the display of Network Quality Indicators displayed in the cells of the conference Video Layout. Default: TOP_RIGHT Range: • BOTTOM_LEFT • • • BOTTOM_RIGHT TOP_LEFT TOP_RIGHT For more information see "Manually Adding and Deleting System Flags” on page 22-18.
PAGE 192
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide RMX Telepresence Mode Guidelines System Level • The RMX system must be licensed for Telepresence Mode. • The system must be activated with a Telepresence enabled license key. Conference Level • The Telepresence Mode and Telepresence Layout Mode fields are only displayed in the Conference Profile dialog box if the RMX has a Telepresence license installed.
PAGE 193
Chapter 4-Additional Conferencing Information If an ITP endpoint is detected in such conference, ITP features are applied to all endpoints and the RMX sends conference video with the following options disabled: • Borders • Site names • Speaker indication • Skins • Same Layout • Presentation Mode • Auto Layout • Lecture Mode The ITP features are dynamic, and if all ITP endpoints disconnect from the conference, normal conference video is resumed for the remaining all participants.
PAGE 194
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Gathering Phase with ITP Room Systems When a conference is configured to include a Gathering Phase, only one endpoint name is displayed for the ITP room in the connected participant list of the Gathering slide. The ITP room endpoint with the suffix “1” in its name receives the Gathering slide.
PAGE 195
Chapter 4-Additional Conferencing Information Table 4-20 TPX / RPX – Additional Video Layouts (Continued) Number of Endpoints 4 Layouts 4:3 4:3 4:3 4:3 4:3 4:3 4:3 4:3 4:3 4:3 4:3 4:3 4:3 4:3 4:3 4:3 5 9 10+ Polycom, Inc.
PAGE 196
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The following example illustrates the use of standard and additional RMX Telepresence layouts when connecting four Room Systems as follows: • Two TPX Room Systems — 2 active cameras — 6 screens • Two RPX Room Systems — 8 cameras — 8 screens TPX View 3 Screens 16:9 RPX View 4 Screens 4:3 Standard TPX Layout Camera Zoomed Out Alignment of back-projectors eliminates the display of the vertical blank areas of the video
PAGE 197
Chapter 4-Additional Conferencing Information 3 Define the various profile General, Advanced, Gathering Settings and Video Quality parameters. For more information on defining Profiles, see "Defining New Profiles” on page 2-18. 4 Click the Video Settings tab. 5 In the Telepresence Mode field, select one of the following options: — OFF - When OFF is selected, normal conference video is sent by the RMX. — AUTO (Default) - The ITP features are dynamic.
PAGE 198
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The following modes can be selected (as required by the VNOC and Polycom Multi Layout Applications): — Manual — Continuous presence - Room Continuous Presence (Default) — Room Switch - Voice Activated Room Switching 7 Select the required video layout. When Telepresence Mode is enabled, the Skin options are disabled as the system uses a black background and the frames and speaker indication are disabled. 8 Click OK.
PAGE 199
Chapter 4-Additional Conferencing Information — If the main link is disconnected all sub-links are disconnected and deleted. Reconnecting the main link reconnects all sub-links. — If a sub-link is disconnected it remains disconnected until it is manually reconnected. — The number of Multiple Cascade Links cannot be modified while any of the links are in a disconnected state. All previous links must be deleted before modification is possible.
PAGE 200
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • Directional media flows, A  B, are shown separately for readability purposes. Figure 4-3 RMX Telepresence Layout Mode - Room Switch In Figure 4-4: 4-64 • An HDX endpoint and an OTX Room System connects to RMX A. • An HDX endpoint and an RPX Room System connects to RMX B.
PAGE 201
Chapter 4-Additional Conferencing Information • The current speaker is the HDX endpoint connected to RMX A. Figure 4-4 RMX Telepresence Layout Mode - Continuous Presence For more information see: Polycom, Inc. • "Telepresence Layout Mode” on page 2-33.
PAGE 202
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Creating a Link Participant Link Participant in the Dial Out RMX The Link Participant is defined in the New Participant dialog box. In the General tab: • Dialing Direction must be selected as Dial out. • Type must be selected as H.323. For more information see the RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide, "Creating a Cascade Enabled Dial-out/Dial-in Participant Link” on page 5-15.
PAGE 203
Chapter 4-Additional Conferencing Information In the Advanced tab: (This field is only enabled if the RMX system is licensed for Telepresence Mode.) • In the Cascade drop-down menu, select either Master or Slave. • In the Number of cascaded links (for ITP) drop-down menu, select the maximum number of Multiple Cascade Links required according to the number of Room System endpoints in the cascaded conference. For example if an RPX 4xx is included, the number of links required is 4.
PAGE 204
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Participant Link in the Dial In RMX The call from Participant Link defined in the Dial-out RMX in identified by the Dial-in RMX as having been initiated by a Participant Link.
PAGE 205
Chapter 4-Additional Conferencing Information — The first link is listed as Disconnected in the Participants list of the RMX Web Client / RMX Manager main screen. — Resource deficiency is listed as the Call Disconnection Cause in the Participant Properties - Connection Status dialog box. • If a calling Link Participant is not defined with same number of links as all the other Link Participants in the cascaded conferences: — The call is rejected.
PAGE 206
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Monitoring Telepresence Mode Monitoring Ongoing Conferences An additional status indicator, Telepresence Mode Enabled, is displayed in the Conference Properties - Video Settings tab when monitoring ongoing conferences. The Telepresence Mode Enabled, Telepresence Mode and Telepresence Layout Mode fields are only enabled if the RMX has a Telepresence license installed.
PAGE 207
Chapter 4-Additional Conferencing Information Monitoring Participant Properties An additional status indicator, Telepresence, is displayed in the Participant Properties Advanced tab when monitoring conference participants. The Telepresence mode of the participant is indicated: • RPX - the participant’s endpoint is transmitting 4:3 video format. • TPX - the participant’s endpoint is transmitting 16:9 video format. • None.
PAGE 208
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide — The first link is listed as Disconnected in the Participants list of the RMX Web Client / RMX Manager main screen. — Resource deficiency is listed as the Call Disconnection Cause in the Participant Properties - Connection Status dialog box. • If a calling Link Participant is not defined with same number of links as all the other Link Participants in the cascaded conferences: — The call is rejected.
PAGE 209
Chapter 4-Additional Conferencing Information Lecture Mode (AVC Only) Lecture Mode enables all participants to view the lecturer in full screen while the conference lecturer sees 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. Conference participants cannot change their Personal Layouts while Lecture Mode is enabled.
PAGE 210
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Selecting a defined participant: a Add participants to the conference either from the Address book or by defining new participants. b In the Lecturer field, select the lecturer from the list of the defined participants. Automatic selection of the lecturer: — In the Lecturer field, select [Auto]. In this mode, the conference speaker becomes the lecturer.
PAGE 211
Chapter 4-Additional Conferencing Information Enabling the Automatic Switching Automatic switching between participants viewed on the lecturer’s screen is enabled in the conference Profile, or during the ongoing conference, in the Conference Properties. >> In the Profile Properties - Video Settings dialog box, select the Lecturer View Switching check box. This option is activated when the conference includes more sites than windows in the selected layout.
PAGE 212
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide If the lecturer is disconnected during an Ongoing Conference, the conference resumes standard conferencing. Forcing is enabled at the Conference level only. It applies only to the video layout viewed by the lecturer as all the other conference participants see only the lecturer in full screen. If an asymmetrical video layout is selected for the lecturer (i.e.
PAGE 213
Chapter 4-Additional Conferencing Information • Enable or disable the Lecturer View Switching between participants displayed on the lecturer monitor by selecting or clearing the Lecturer View Switching check box. • Change the video layout for the lecturer by selecting another video layout.
PAGE 214
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Muting Participants Except the Lecturer When the Mute Participants Except Lecturer option in the Conference Profile is enabled, the audio of all participants in the conference except for the lecturer can be automatically muted upon connection to the conference.
PAGE 215
Chapter 4-Additional Conferencing Information Enabling the Mute Participants Except Lecturer Option The Mute Participants Except Lecturer option is enabled or disabled (default) in the Conference Profile or in an ongoing conference in the Profile Properties - Audio Settings tab. When the Mute Participants Except Lecturer option is enabled and a conference has started, the Mute by MCU icon is displayed in the Audio column in the Participants pane of each participant that is muted. Polycom, Inc.
PAGE 216
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Permanent Conference A Permanent Conference is an ongoing AVC or SVC conference with no pre-determined End Time continuing until it is terminated by an administrator, operator or chairperson. Guidelines • Resources are reserved for a Permanent Conference only when the conference has become ongoing. • Resources are allocated to a Permanent Conference according to the Reserve Resources for Video Participants field.
PAGE 217
Chapter 4-Additional Conferencing Information Closed Captions (AVC Only) Endpoints can provide real-time text transcriptions or language translations of the video conference by displaying captions. The captions for a conference may be provided by the captioner who is present in the conference, or the captioner may use a telephone or web browser to listen to the conference audio. When the captioner sends a unit of text, all conference participants see it on the main monitor for 15 seconds.
PAGE 218
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 3 In the New Flag field enter ENABLE_CLOSED_CAPTION. 4 In the Value field enter YES to enable Closed Captions or NO to disable their display. 5 Click OK to close the New Flag dialog box. The new flag is added to the flags list. 6 Click OK to close the System Flags dialog box. For flag changes (including deletion) to take effect, reset the MCU. For more information, see "Resetting the RMX” on page 21-69.
PAGE 219
5 Cascading Conferences Cascading information applies to AVC Conferencing Mode only. Cascading is not supported with SVC Conferencing Mode. Cascading enables administrators to connect one conference directly to one or several conferences, depending on the topology, creating one large conference. 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.
PAGE 220
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 In order to avoid cluttering in the cascaded window, it is advised to select appropriate video layouts in each conference before cascading them. Conference A Conference B Without Cascade During Cascading Video layout of Conf. B in window of Conf. A Video layout of Conf. A in window of Conf.
PAGE 221
Chapter 5-Cascading Conferences Full Screen (1x1) in CP conferences, hence displaying the speaker of one conference to a full window in the video layout of the other conference. Set this flag to NO when cascading between an RMX and an MGC that is functioning as a Gateway, if the participant layouts on the MGC are not to be forced to 1X1.
PAGE 222
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Basic Cascading In this topology, a link is created between two conferences, usually running on two different MCUs. The MCUs are usually installed at different locations (states/countries) to save long distance charges by connecting each participant to their local MCU, while only the link between the two conferences is billed as long distance call.
PAGE 223
Chapter 5-Cascading Conferences The connection between the two conferences is created when a dial out IP participant is defined (added) to conference A whose dial out number is the dial-in number of the conference or Entry Queue running on MCU B. Dialing Directly to a Conference Dial out IP participant in conference A dials out to the conference running on MCU B entering the number in the format: [MCU B Prefix/IP address][conference B ID].
PAGE 224
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 RMX Gateway A RMX Gateway B Figure 5-3 Gateway to Gateway Topology In this topology, an IP participant calls another IP participant over an ISDN link between two gateways. • Gateway to MCU RMX Gateway A RMX MCU B Figure 5-4 Gateway to MCU/ MCU to Gateway Topology In this topology, an IP participant calls a conference running on an MCU via a gateway and over an ISDN link.
PAGE 225
Chapter 5-Cascading Conferences • When a participant joins a conference with active Content, content cannot be viewed by the new participant. Restart the Content. • Cascaded MCUs/Gateways must be registered with the same Gatekeeper or neighboring Gatekeepers. MCUs and endpoints must also be registered with Gatekeepers. • Gateway/MCU calls require definition of IVR Services. For more information see "Defining the IVR Service for Gateway Calls” on page 19-14. In version 7.1, H.
PAGE 226
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 For example: If Central Signaling IP address of Gateway A is 172.22.177.89, SIP participant dials: 9999@ 172.22.177.89* 4444103 and when prompted for the Destination number enters 3456 followed by the pound key (#) using DTMF codes. Gateway to MCU Calls via ISDN Cascading Link When H.
PAGE 227
Chapter 5-Cascading Conferences At this point the Conference A organizer or any other participant in the conference can enter the required information for the IVR session using DTMF codes. For example, the meeting organizer enters the destination conference ID - 12345. Any DTMF input from conference A is forwarded to the Entry Queue on MCU B to complete the IVR session and enable the move of the participant to the destination conference B.
PAGE 228
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 A dial out ISDN participant is defined (added) to conference A. The participant’s dial out number is the dial-in number of the Entry Queue or conference running on MCU B (for example 54145106). MCU A dials out to an Entry Queue or conference B running on MCU B using the Entry Queue number (for example 54145106) or the conference number.
PAGE 229
Chapter 5-Cascading Conferences Table 5-1 Recommended Conference Profile Options Setting (Continued) Line Rate Motion 384  512  Sharpness Encryption LPR    512 512  512  768      768 768  768     Since the remote participant settings are unknown, it is recommended that the gateway or endpoint be configured to support a higher line rate (for example, 768 Kbps) to allow flexibility during endpoint capability negotiations.
PAGE 230
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 5-2 5-12 MCU Interoperability Table (Continued) Scenario Version(s) Codian Gateway RMX Gateway User calls via a Codian Gateway to a Remote User behind RMX Gateway (user to user) RMX v. 7.1 Latest Codian version RMX MCU Radvision Gateway User calls via a Radvision Gateway to a Remote User behind RMX Gateway (user to user) RMX v. 7.
PAGE 231
Chapter 5-Cascading Conferences • • On the Codian gateway Content is not supported with line rates of 128Kbps and below. • Sending Content from a participant over Radvision Gateway to a conference/participant, the GWP20 patch must be installed in the RadVision gateway: On the Radvision gateway, open the GWP20 User Interface. Click Settings/Advanced Commands. In the Command box enter H239OlcPatch. In the Parameters box enter Enable and then click Send. When using the following topology: H.
PAGE 232
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Star Cascading Topology In the Star topology (as well as in the Basic topology), the MCUs are usually installed at different locations (states/countries) and participants connect to their local MCU to facilitate the connection and save long distance call costs. Star Topology Cascading requires that all cascaded MCUs reside on the same network. Although participants in Star Cascading conferences can connect to their local conference using H.
PAGE 233
Chapter 5-Cascading Conferences • When creating a cascading link between two RMXs: • — The RMXs operate in CP (Continuous Presence) mode. When creating a cascading link between MGCs and RMXs: — The MGCs can only operate in VSW mode.
PAGE 234
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 The New Participant - General dialog box is displayed. 3 Define the following parameters: Table 7 New Participant – Dial-out Cascade Link 5-16 Field Description Display Name Enter the participant name Dialing Direction Select Dial-out. Type Select H.323. IP Address Enter the IP address of the Signaling Host of the MCU running the other (second) conference, where the cascade enabled Entry Queue is defined. Polycom, Inc.
PAGE 235
Chapter 5-Cascading Conferences Table 7 New Participant – Dial-out Cascade Link (Continued) Field Description Alias Name If you are using the target MCU IP address, enter the Conference ID of the target conference.
PAGE 236
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 5-18 4 Click the Advanced tab. 5 In the Cascade field, select: 6 — Slave, if the participant is defined in a conference running on a Slave MCU. — Master, if the participant is defined in a conference running on the Master MCU. Click OK. Polycom, Inc.
PAGE 237
Chapter 5-Cascading Conferences To define a Dial-in Participant as the cascade link: This participant is added to the ongoing conference on the Slave MCU. 1 In the Participants list, click the New Participant button( ). The New Participant - General dialog box opens. 2 Define the following parameters: Table 5-1 New Participant – Dial-out Cascade Link 3 Polycom, Inc. Field Description Display Name Enter the participant name Dialing Direction Select Dial-in. Type Select H.323.
PAGE 238
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 The Advanced tab opens. 4 In the Cascaded Link field, select: 5 — Slave, if the participant is defined in a conference running on a Slave MCU. — Master, if the participant is defined in a conference running on the Master MCU. Click the OK button.
PAGE 239
Chapter 5-Cascading Conferences Though the process of cascading conferences mentioned in this section refers to conferences running on two different RMX units, it is possible to cascade conferences running between RMX units and other MCUs. The following features are not supported by the cascaded link and therefore are not supported in the combined conference: • DTMF codes are enabled in cascaded conference, but only in their local conference.
PAGE 240
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 — Set this field to Slave if the Entry Queue is defined on the MCU acting as a Slave, that is, to which the link from the Master MCU (MCU at the center of the topology) is dialing. If you are defining an HD cascaded Entry Queue, it is recommended to select the same Profile that is selected for both conferences. 5 Click OK. The new Entry Queue enabling cascading is created.
PAGE 241
Chapter 5-Cascading Conferences The New Participant - General dialog box is displayed. 3 In the Name field, enter a participant name. 4 In the Dialing Direction field, select Dial-out. 5 In the Type list field, verify that H.323 is selected. 6 There are two methods to define the dialing string: A Using the MCU’s IP Address and the Alias string. B Using only the Alias string (requires a gatekeeper).
PAGE 242
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 F o r E xa m p l e : 9 2 57 84 8 5# 24 0 06 # 12 34 MCU Prefix as registered in the gatekeeper Password (optional) Cascade-enabled EQ ID 7 Click the Advanced tab. 8 In the Cascade field, select: Conference ID — Slave, if the participant is defined in a conference running on a Slave MCU and will connect to the Master MCU (in the center of the topology).
PAGE 243
Chapter 5-Cascading Conferences 2 Set the ENABLE_CASCADED_LINK_TO_JOIN_WITHOUT_PASSWORD flag to YES. 3 Click OK. For more information, see "Modifying System Flags” on page 22-1. >> Reset the MCU for flag changes to take effect. Monitoring Star Cascaded Conferences To monitor both conferences at the same time, two instances of the RMX Web Clients must be opened (one for each MCU) by entering the IP Address of each MCU.
PAGE 244
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 1 In the Participant Properties dialog box, enter a Participant Name, select Dial-out and H.323. 2 Define the dialing string as described in step 6 on page 5-23 (both methods are applicable). 3 In the Advanced tab’s Node Type field, select MCU. 1 + 2 3 4 Click OK. Cascading Conferences - H.239-enabled MIH Topology H.
PAGE 245
Chapter 5-Cascading Conferences • Significant call cost savings to be realized by having participants call local MCUs which in turn call remote MCUs, long distance. Although participants in MIH Cascading conferences can connect using H.323, SIP and ISDN, the MIH Cascading Links must connect via H.323. MIH Cascading Levels The cascading hierarchy topology can extend to up to four levels (Figure 5-9), where the most common configuration includes up to three levels.
PAGE 246
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 • Level 1 DST MCS 4000 MCUs connect as endpoints to the RMXs or MGCs on higher levels. RMX MGC MGC RMX Level 2 or or Level 3 Level 4 DST MCS 4000 MCU For more information about this configuration, see the relevant MGC documentation.
PAGE 247
Chapter 5-Cascading Conferences Figure 5-10MIH Cascading – Master-Slave Relationship Video Session Mode, Line Rate and Video Settings The types of MCUs, their position in the cascade topology and the endpoint capabilities (HD/CIF and H.263/H.264) determine the Video Session Type of the MIH Cascading conference. • When creating a cascading link between two RMXs: • — The RMXs operate in CP (Continuous Presence) mode.
PAGE 248
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 • To enable the connection of the links between cascaded conferences, they must run at the same line rate. • To enable Content sharing between the RMX and the MGC, the rate allocated to the content must be identical in both conferences. Make sure that the line rate set for both conferences, and the Content Settings (Graphics, Hi-res Graphics or Live video) are selected correctly to ensure the compatible rate allocation.
PAGE 249
Chapter 5-Cascading Conferences When cascading two conferences, the video layout displayed in the cascaded conference is determined by the selected layout in each of the two conferences. Each of the two conferences will inherit the video layout of the other conference in one of their windows. In order to avoid cluttering in the cascaded window, it is advised to select appropriate video layouts in each conference before cascading them.
PAGE 250
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Set this flag to NO when cascading between an RMX and an MGC that is functioning as a Gateway, if the participant layouts on the MGC are not to be forced to 1X1. • Setting the AVOID_VIDEO_LOOP_BACK_IN_CASCADE System Flag to YES (default) prevents the speaker’s image from being sent back through the participant link from the cascaded conference. This can occur in cascaded conferences with conference layouts other than 1x1.
PAGE 251
Chapter 5-Cascading Conferences Method I Depending on the dialing direction, the following procedures must be performed: Table 5-3 Set up Procedures according to the Dialing Direction Dialing Direction MGC to RMX RMX to MGC RMX - Level 1 MGC - Level 2 Set the appropriate flags (done once only). Set the appropriate flags (done once only). Define the conference setting and its line rate to be the same as the one set on the RMX.
PAGE 252
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Method II Depending on the dialing direction, the following procedures must be performed: Table 5-4 Set up Procedures according to the Dialing Direction Dialing Direction MGC to RMX MGC Level 1 Set the appropriate flags (done once only). RMX 1500/2000/4000 Level 2 Set the appropriate flags (done once only). Define the cascade-enabled Entry Queue, setting it as Slave.
PAGE 253
Chapter 5-Cascading Conferences rate of the IP Only HD Video Switching conference running on the MGC. In such case, the conference can include IP Only participants. If the flag MIX_LINK_ENVIRONMENT is set to YES, the IP_LINK_ENVIRONMENT flag must be set to NO. If the flag MIX_LINK_ENVIRONMENT is set to NO, the IP_LINK_ENVIRONMENT flag must be set to YES. — H263_ANNEX_T=YES (default) This flag enables/disables the use of Annex T with H263.
PAGE 254
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Method II - Defining the Cascading Entry Queue in the MGC The Entry Queue definition on the MGC is required if the dialing is done from the RMX to the MGC. 1 In the MGC Manager, expand the MCU tree. 2 Right-click the Meeting Rooms, Entry Queues and SIP Factories icon and click New Entry Queue. 3 In the New Entry Queue dialog box, set the Entry Queue parameters and select the Cascade check box.
PAGE 255
Chapter 5-Cascading Conferences In the IP Address field, enter the IP address of the Signaling Host of the RMX hosting the destination conference. In the Alias Name/Type field, enter the ID of the cascade-enabled Entry Queue (EQ), the Conference ID and Password of the destination conference as follows: EQ ID##Destination Conference ID##Password (Password is optional).
PAGE 256
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Defining the Cascade Enabled Entry Queue on the RMX If the dialing is done from the conference running on the MGC that is the Master MCU, a Cascade-enabled Entry Queue must be defined on the RMX setting it as Slave. For more details, see RMX to RMX Cascading. Defining the Cascading Conferences The table below lists the line rates and the video settings that should be used when defining the conferences on the MGC.
PAGE 257
Chapter 5-Cascading Conferences The New Participant - General dialog box is displayed. 3 In the Name field, enter a participant name. 4 In the Dialing Direction field, select Dial-out. 5 In the Type list field, verify that H.323 is selected. 6 There are two methods to define the dialing string: A Using the MCU’s IP Address and the Alias string. B Using only the Alias string (requires a gatekeeper).
PAGE 258
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Method B (Using a gatekeeper): In the Alias Name field, enter the MGC Prefix as registered in the gatekeeper, EQ ID, Destination Conference ID, and Password, as follows: MGC Prefix EQ ID##Conference ID##Password (Password is optional) F o r E x a m p l e : 92 5 10 05 # #2 0 00 6# # 12 34 MCU Prefix as registered in the gatekeeper 5-40 Password (optional) Cascade-enabled EQ ID Conference ID 7 Click the Advanced tab and in the Cascade field,
PAGE 259
6 Meeting Rooms A Meeting Room is a conference saved on the MCU in passive mode, without using any of the system resources. A Meeting Room is automatically activated when the first participant dials into it. Meeting Rooms can be activated as many times as required. Once activated, a Meeting Room functions as any ongoing conference. The Meeting Room conferencing Mode is determined by the Profile assigned to it.
PAGE 260
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 6-1 Default Meeting Rooms List Meeting Room Name ID Default Line Rate Fig_Room 1004 384 Kbps Meeting Rooms List Meeting Rooms are listed in the Meeting Room list pane. To list Meeting Rooms: >> In the RMX Management pane, in the Frequently Used list, click the Meeting Rooms button . The Meeting Rooms List is displayed.
PAGE 261
Chapter 6-Meeting Rooms Table 6-2 Meeting Rooms List Columns (Continued) Field Routing Name Description The ASCII name that registers conferences, Meeting Rooms, Entry Queues and SIP Factories in the various gatekeepers and SIP Servers. In addition, the Routing Name is also: • The name that endpoints use to connect to conferences. • Polycom, Inc. The name used by all conferencing devices to connect to conferences that must be registered with the gatekeeper and SIP Servers.
PAGE 262
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Meeting Room Toolbar & Right-click Menu The Meeting Room toolbar and right-click menus provide the following functionality: Table 6-3 Toolbar button Meeting Room Toolbar and Right-click Menus Right-click menu Description New Meeting Room Select this button to create a new Meeting Room. Delete Meeting Room Select any Meeting Room and then click this button to delete the Meeting Room.
PAGE 263
7 Entry Queues, Ad Hoc Conferences and SIP Factories Entry Queues Entry Queues are supported in AVC Conferencing Mode only. An Entry Queue (EQ) is a special routing lobby to access conferences. Participants connect to a single-dial lobby and are routed to their destination conference according to the Conference ID they enter. The Entry Queue remains in a passive state when there are no callers in the queue (in between connections) and is automatically activated once a caller dials its dial-in number.
PAGE 264
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 To enable ISDN/PSTN participants to dial in to the Entry Queue, an ISDN/PSTN dial-in number must be assigned to the Entry Queue. Up to two dial-in numbers can be assigned to each Entry Queue. The dial-in numbers must be allocated from the dial-in number range defined in the ISDN/PSTN Network Service. You can allocate the two dial-in numbers from the same ISDN/PSTN Network Service or from two different ISDN/PSTN Network Services.
PAGE 265
Chapter 7-Entry Queues, Ad Hoc Conferences and SIP Factories Defining a New Entry Queue You can modify the properties of the default Entry Queue and define additional Entry Queues to suit different conferencing requirements. To define a new Entry Queue: 1 In the RMX Management - Rarely Used pane, click Entry Queues. . 2 Polycom, Inc. In the Entry Queues list pane, click the New Entry Queue The New Entry Queue dialog box opens. button.
PAGE 266
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 3 Define the following parameters: Table 7-2: Entry Queue Definitions Parameters Option Description Display Name The Display Name is the conferencing entity name in native language character sets to be displayed in the RMX Web Client. In conferences, Meeting Rooms, Entry Queues and SIP factories the system automatically generates an ASCII name for the Display Name field that can be modified using Unicode encoding.
PAGE 267
Chapter 7-Entry Queues, Ad Hoc Conferences and SIP Factories Table 7-2: Entry Queue Definitions Parameters (Continued) Option Description Ad Hoc Select this check box to enable the Ad Hoc option for this Entry Queue. IVR Service Provider Only Select this check box to designate this Entry Queue as a special Entry Queue that provides IVR Services to SIP calls on behalf of the DMA. The IVR service provider only EntryQueue does not route the SIP calls to a target conference.
PAGE 268
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Listing Entry Queues To view the list of Entry Queues: >> In the RMX Management - Rarely Used pane, click Entry Queues. The Entry Queues are listed in the Entry Queues pane. You can double-click an Entry Queue to view its properties. Modifying the EQ Properties To modify the EQ: >> In the Entry Queues pane, either double-click or right-click and select Entry Queue Properties of the selected Entry Queue in the list.
PAGE 269
Chapter 7-Entry Queues, Ad Hoc Conferences and SIP Factories To designate an Entry Queue as Transit Entry Queue: 1 In the RMX Management - Rarely Used pane, click Entry Queues. 2 In the Entry Queues list, right-click the Entry Queue entry and then click Set Transit Entry Queue. The Entry Queue selected as Transit Entry Queue is displayed in bold. To cancel the Transit Entry Queue setting: 1 In the RMX Management - Rarely Used pane click Entry Queues.
PAGE 270
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 • Operator Assistance must be disabled in the IVR Service assigned to this Entry Queue. • Only the conference ID prompts should be configured. Other prompts are not supported in IVR Service Provider Only configuration. • PSTN, ISDN, H.323 calls to this Entry Queue are rejected. • The DMA must be configured to locate the IVR Service Provider Only Entry Queue on the RMX.
PAGE 271
Chapter 7-Entry Queues, Ad Hoc Conferences and SIP Factories SIP Factories A 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.
PAGE 272
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 3 Define the following parameters: Table 7-3: New Factory Properties Option Description Display Name Enter the SIP Factory name that will be displayed. The Display Name is the conferencing entity name in native language character sets to be displayed in the RMX Web Client.
PAGE 273
Chapter 7-Entry Queues, Ad Hoc Conferences and SIP Factories SIP Registration & Presence for Entry Queues and SIP Factories Entry Queues and SIP Factories can be registered with SIP servers. This enables Office Communication Server or LYNC server client users to see the availability status (Available, Offline, or Busy) of these conferencing entities and to connect to them directly from the Buddy List. Guidelines • The Entry Queue or SIP Factory must be added to the Active Directory as a User.
PAGE 274
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 When SIP registration is not enabled in the conference profile, the RMX's registering to SIP Servers will each register with an URL derived from its own signaling address. This unique URL replaces the non-unique URL, dummy_tester, used in previous versions. • Failed - Registration with the SIP Server failed.
PAGE 275
8 Address Book The Address Book stores information about the people and businesses you communicate with. The Address Book stores, among many other fields, IP addresses, phone numbers and network communication protocols used by the participant’s endpoint. By utilizing the Address Book you can quickly and efficiently assign or designate participants to conferences. Groups defined in the Address Book help facilitate the creation of conferences.
PAGE 276
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Viewing the Address Book You can view the participants currently defined in the Address Book. The first time the RMX Web Client is accessed, the Address Book pane is displayed. Anchor Pin Address Book pane The Address Book contains two panes: • Navigation pane - contains the hierarchical tree and All Participants list • List pane - displays the list of all the members of the selected group and sub-groups.
PAGE 277
Chapter 8-Address Book participant links are associated with the same definition of the participant in the All Participants list. If the participant properties are changed in one group, they will be changed in all the groups accordingly. Displaying and Hiding the Group Members in the Navigation Pane The currently selected group, whose group members are displayed in the Address Book List pane is identified by a special icon .
PAGE 278
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 8-1 Docked Address Book List Columns (Continued) Field/Option Description Dialing Direction Dial-in – The participant dials in to the conference. Dial-out – The RMX dials out to the participant. Encryption Displays whether the endpoint uses encryption for its media. The default setting is Auto, indicating that the endpoint must connect according to the conference encryption setting.
PAGE 279
Chapter 8-Address Book Adding Participants from the Address Book to Conferences You can add individual participants or a group of participants from the Address Book to a conference. Adding Individual Participants from the Address Book to Conferences You can add a participant or multiple participants to a new conference, ongoing conferences, or to Conference Templates by using the drag-and-drop operation. Multiple selection of group levels is not available.
PAGE 280
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Participant Groups A group is a predefined collection of participants. A group provides an easy way to manage clusters of participants that are in the same organizational structure and 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.
PAGE 281
Chapter 8-Address Book Table 8-2 Groups Drop-down Menu Actions (Continued) Action Description Delete Group Deletes the group and all of its members. This action displays a message requesting confirmation to delete the group and all members connected with the group. Additionally, you can drag a group from one location in the Address Book to another location, moving the group and all its members, including sub-groups, to its new location using the drag-and-drop operation.
PAGE 282
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Adding a new participant to the Address Book Directly You can add a new participant to the “Main” group or to a group in the Address Book. Additionally, you can add a participant from a new conference, ongoing conference, or Conference Template. To add a new participant to the Address Book: 1 In the Address Book - Navigation pane, select the group to where you want to add the new participant.
PAGE 283
Chapter 8-Address Book 3 Define the following fields: Table 8-3 New Participant – General Properties Field Description Name Enter the name of the participant or the endpoint as it will be displayed in the RMX Web Client. The Name field can be modified using Unicode encoding. • English text uses ASCII encoding and can contain the most characters (length varies according to the field). • European and Latin text length is approximately half the length of the maximum.
PAGE 284
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 8-3 New Participant – General Properties (Continued) Field Description IP Address (H.323 and SIP Only) Enter the IP address of the participant’s endpoint. • For H.323 participant define either the endpoint IP address or alias. • For SIP participant define either the endpoint IP address or the SIP address. For RMXs registered to a gatekeeper, the RMX can be configured to dial and receive calls to and from H.
PAGE 285
Chapter 8-Address Book Table 8-3 New Participant – General Properties (Continued) Field Description Endpoint Website IP Address (IP only) Enter the IP address of the endpoint’s internal site to enable connection to it for management and configuration purposes. This field is automatically completed the first time that the endpoint connects to the RMX. If the field is blank it can be manually completed by the system administrator.
PAGE 286
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 5 Define the following Advanced parameters: IP Participant ISDN/PSTN Participant Table 8-4 New Participant – Advanced Properties Field Description Video Bit Rate / Auto (IP Only) The Auto check box is automatically selected to use the Line Rate defined for the conference. Note: This check box cannot be cleared when defining a new participant during an ongoing conference.
PAGE 287
Chapter 8-Address Book Table 8-4 New Participant – Advanced Properties (Continued) Field Description AGC AGC (Auto Gain Control) mechanism regulates noise and audio volume by keeping the received audio signals of all participants balanced. Select this check box to enable the AGC mechanism for participants with weaker audio signals. Notes: • To be enable AGC, set the value of the ENABLE_AGC System Flag in system.cfg to be YES. The flag’s default value is NO.
PAGE 288
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 The Participant Properties window opens. b Click the Add to Address Book button. If the participant name is already listed in the All Participants list, an error message is displayed. In such a case, change the name of the participant before adding the participant to the address book. Modifying Participants in the Address Book When required, you can modify the participant’s properties.
PAGE 289
Chapter 8-Address Book 2 In the Address Book - List pane, double-click the participant’s icon. The Participant’s Properties window is displayed. 3 Modify the necessary properties in the window, such as dialing direction, communication protocol type, and so on. You can modify any property in any of the three tabs: General, Advanced and Info. 4 Click OK. The changes to the participant’s properties are updated.
PAGE 290
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 • Address Book to permanently delete the participant from the address book (all groups). Click OK to perform the delete operation or Cancel to exit the delete operation. Copying or Moving a Participant You can copy or move a participant from one group to another group using the Copy, Cut, and Paste options. A participant can belong to multiple groups. However, there is only one entity per participant.
PAGE 291
Chapter 8-Address Book 5 Right-click the selected group and click one of the following Paste functions from the drop-down menu: Table 8-6 Paste functions Function Description Paste Participant Creates a link to the participant entity in the pasted location. Paste Participant as New Pastes as a new participant into the selected group. This paste action adds “Copy” to the end of the participant name. The Paste functions are only available after a Copy or Cut action has been implemented.
PAGE 292
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Filtering the Address Book The entries in an address book group can be filtered to display only the entries (participants or groups) that meet criteria that you specify and hides entries that you do not want displayed. It enables you to select and work with a subset of Address Book entries. You can filter by more than one column, by adding additional filters (columns). The filter applies to the displayed group.
PAGE 293
Chapter 8-Address Book Example: If the user selects 172.21.41.104 as the matching pattern, the filtered group in the Address Book is displayed as follows: Selected Column Active Filter Indicator 1 Entry matching “172.21.41.104” in filtered group Filtering Address Book Data Using a Custom Pattern To filter the data in an address book group: 1 In the Address Book - Navigation pane, select the group to filter.
PAGE 294
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 4 In the Condition - Column text matches field, enter the filtering pattern. For example, to list only endpoints that include the numerals 41 in their name, enter 41. 5 Optional. Click the Add Condition button to define additional filtering patterns to further filter the list and fine tune your search. To clear a filtering pattern, click the Clear Condition button.
PAGE 295
Chapter 8-Address Book Obtaining the Display Name from the Address Book The MCU can be configured to replace the name of the dial-in participant as defined in the endpoint (site name) with the name defined in the Address Book. In this process, the system retrieves the data (name, alias, number or IP address) of the dialin participant and compares it first with the conference defined dial-in participants and if the endpoint is not found, it then searches for the endpoint with entries in the address book.
PAGE 296
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Importing and Exporting Address Books Address Books are proprietary Polycom data files that can only be distributed among RMX units. The Address Books are exported in XML format, which are editable offline. If no name is assigned to the exported Address Book, the default file name is: EMA.DataObjects.OfflineTemplates.AddressbookContent_.
PAGE 297
Chapter 8-Address Book 3 In the Open dialog box navigate to the desired Address Book file (in XML format) to import. When importing an Address Book, participants with exact names in the current Address Book will be overwritten by participants defined in the imported Address Book. 4 Click Open. You will return to the Import File dialog box. 5 Click OK. The Address Book is imported and a confirmation message is displayed at the end of the process. 6 Click Close.
PAGE 298
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 • The RMX uses the Polycom CMA address book in read-only mode. You can only add or modify CMA address book entries a from the CMA. Entries are also added when endpoints register with the CMA as gatekeeper. The RMX acts as a proxy to all address book requests between the RMX Web Client and the CMA. Ensure that firewall and other network settings allow the RMX access to the CMA server.
PAGE 299
Chapter 8-Address Book Table 8-7 Polycom, Inc. System Flags for CMA Address Book Integration (Continued) Flag Description EXTERNAL_CONTE NT_IP Version 4.x and earlier - enter the IP address of the CMA server. For example: 172.22.185.89. Version 5.0.x and version 6.0.x - enter the IP address of the CMA server in the format: http://[IP address of the CMA server]. For example, http://172.22.185.89. Version 7.0.x and later - enter the IP address of the CMA server. For example: 172.22.185.89.
PAGE 300
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 8-26 Polycom, Inc.
PAGE 301
9 Reservations Reservations are supported in AVC Conferencing Mode only. The Reservations option enables users to schedule conferences. These conferences can be launched immediately or become ongoing, at a specified time on a specified date. Scheduling a conference reservation requires definition of conference parameters such as the date and time at which the conference is to start, the participants and the duration of the conference.
PAGE 302
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide — RealPresence Collaboration Server (RMX) 4000 MPMx-D Mode: 1440 (180 video). From Version 7.1, MPM media cards are not supported. • System resources are calculated according to the RMX’s license. For more information see "Video/Voice Port Configuration” on page 21-10.
PAGE 303
Chapter 9-Reservations • — Sufficient resources are not available in the system. If a problem prevents a Reservation from being activated at its schedule time, the Reservation will not be activated at all. This applies even if the problem is resolved during the Reservation’s scheduled time slot. • A Profile that is assigned to a Reservation cannot be deleted. • Reservations are backed up and restored during Setup > Software Management >Backup /Restore Configuration operations.
PAGE 304
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 9-1 Reservations – Toolbar (Continued) Button Description Back Click to show the previous day or week, depending on whether Show Day or Show Week is the selected. Next Click to show the next day or week, depending on whether Show Day or Show Week is the selected. Today Click to show the current date in the Reservation Calendar in either Show Day or Show Week view.
PAGE 305
Chapter 9-Reservations Today View The current date (Today), highlighted in orange, can be viewed in both Week View and Day View. Current Date (Today) Day View Week View List View List View does not have a calendar based format. All Reservations are listed by: • • • • Display Name ID Internal ID Start Time • • • • End Time Status Conference Password Profile The Reservations can be sorted, searched and browsed by any of the listed fields. Polycom, Inc.
PAGE 306
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Changing the Calendar View To change between Week and Day views: >> In Week View: In the Reservation Calendar toolbar, click Show Day ( Day View. ) to change to or In Day View: In the Reservation Calendar toolbar, click Show Week ( Week View.
PAGE 307
Chapter 9-Reservations To view Today (the current date): >> In Week View or Day View, in the Reservation Calendar toolbar, click the Today ( button to have the current date displayed within the selected view. ) Week View Day View Current Date (Today) To change to List View: 1 In the Reservation Calendar toolbar, click, the Reservations List ( ) button. The Reservations List is displayed. 2 Optional. Sort the data by any field (column heading) by clicking on the column heading.
PAGE 308
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Scheduling Conferences Using the Reservation Calendar Creating a New Reservation There are three methods of creating a new reservation: Each method requires the selection of a starting time slot in the Reservation Calendar. The default time slot is the current half-hour period of local time.
PAGE 309
Chapter 9-Reservations The duration of reservations created by any of the above methods can be modified in the Scheduler tab of the New Reservation dialog box. To create a new reservation: 1 Open the Reservation Calendar. 2 Select a starting time slot. 3 Create the reservation using one of the three methods described above. The New Reservation – General tab dialog box opens.
PAGE 310
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide When a Conference Profile is assigned to a Meeting Room or a Reservation, the Profile’s parameters are not embedded in the Reservation, and are taken from the Profile when the reservation becomes an ongoing conference.
PAGE 311
Chapter 9-Reservations 5 Adjust the new reservation’s schedule by modifying the fields as described in Table 9-3. Table 9-3 New Reservation – Schedule Tab Field Start Time End Time Recurring Meeting Polycom, Inc. Description Select the Start Time of the Reservation. Select the End Time of the Reservation. • The Start/End Times of the Reservation are initially taken from the time slot selected in the Reservation Calendar.
PAGE 312
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 9-3 New Reservation – Schedule Tab (Continued) Field Recurrence Pattern Description Daily If Daily is selected, the system automatically selects all the days of the week. To de-select days (for example, weekends) clear their check boxes. Weekly If Weekly is selected, the system automatically selects the day of the week for the Reservation from the day selected in the Reservation Calendar.
PAGE 313
Chapter 9-Reservations 6 Click the Participants tab. Participants List The fields are the same as for the New Conference – Participants tab, described in the RealPresence Collaboration Server (RMX) 1500/2000/4000 Getting Started Guide, "Participants Tab” on page 3-17.
PAGE 314
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The series number (_0000n) of each reservation is appended to its Display Name.
PAGE 315
Chapter 9-Reservations The cursor changes to a vertical double arrow ( bottom sides of the square. ) when it is moved over the top and Click & Drag to Change Start Time Click & Drag to Move Reservation Click & Drag to Change End Time To move the Reservation to another time slot: 1 Select the Reservation. 2 Hold the mouse button down and drag the Reservation to the desired time slot. 3 Release the mouse button. To change the Reservation’s Start time: 1 Select the Reservation.
PAGE 316
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Adjusting the Start Times of all Reservations When utilizing GMT offset (for example, Daylight Saving Time change), the start time of the reoccurring reservations scheduled before the RMX time change are not updated accordingly (although their start times appear correctly in the Reservations list, when checking the reservation properties the start time is incorrect).
PAGE 317
Chapter 9-Reservations 3 Click the arrows of the Offset - Hours box to indicate the number of hours to add or subtract from the current start time; a positive value indicates adding time, while minus (-) indicates subtracting time. 4 Click the arrows of the Offset - minutes box to indicate the number of minutes to add or subtract from the current start time of the reservations. Increments or decrements are by 15 minutes.
PAGE 318
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Searching for Reservations using Quick Search Quick Search is available only in List View. It enables you to search for Reservations by Display Name. To search for reservations: 1 In the Reservation Calendar toolbar, click in the Quick Search field. The field clears and a cursor is displayed indicating that the field is active. 2 Type all or part of the reservation’s Display Name into the field and click Search.
PAGE 319
10 Operator Assistance & Participant Move Operator conferences and participant move are supported in AVC Conferencing Mode only. Users (operators) assistance to participants is available when: • Participants have requested individual help (using *0 DTMF code) during the conference. • Participants have requested help for the conference (using 00 DTMF code) during the conference. • Participants have problems connecting to conferences, for example, when they enter the wrong conference ID or password.
PAGE 320
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 • The operator can connect participants belonging to the same destination conference to their conference simultaneously by selecting the appropriate participants and moving them to the Home conference (interactively or using the right-click menu). • The operator can move one or several participants from an ongoing conference to the Operator conference for a private conversation.
PAGE 321
Chapter 10-Operator Assistance & Participant Move Defining the Components Enabling Operator Assistance To enable operator assistance for conferences, the following conferencing entities must be adjusted or created: • IVR Service (Entry Queue and Conference) in which Operator Assistance options are enabled. • A Conference Profile with the Operator Conference option enabled. • An active Operator conference with a connected Operator participant.
PAGE 322
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 password request for Dial-in and Dial-out participant connections. For more information, see Table 17-5, “New Conference IVR Service Properties - Conference Password Parameters,” on page 17-10. 10 Select the various audio messages that will be played in each case. For more information, see Table 17-5, “New Conference IVR Service Properties - Conference Password Parameters,” on page 17-10. 11 Click the General tab.
PAGE 323
Chapter 10-Operator Assistance & Participant Move 19 Click the Operator Assistance tab. The Operator Assistance dialog box opens. 20 Select Enable Operator Assistance to enable operator assistance when the participant requires or requests help during the connection process to the conference or during the conference. 21 In the Operator Assistance Indication Message field, select the audio message to be played when the participant requests or is waiting for the operator’s assistance.
PAGE 324
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 9 Click the Video Services tab. The New Entry Queue IVR Service - Video Services dialog box opens. 10 In the Video Welcome Slide list, select the video slide that will be displayed to participants connecting to the Entry Queue. The slide list includes the video slides that were previously uploaded to the MCU memory. 11 Click the Operator Assistance tab. The Operator Assistance dialog box opens.
PAGE 325
Chapter 10-Operator Assistance & Participant Move 2 In the Conference Profiles pane, click the New Profile button. The New Profile – General dialog box opens. 3 Define the Profile name and, if required, the Profile general parameters: Table 10-1 New Profile - General Parameters Field/Option Description Display Name Enter a unique Profile name, as follows: • English text uses ASCII encoding and can contain the most characters (length varies according to the field).
PAGE 326
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 10-1 New Profile - General Parameters (Continued) 4 Field/Option Description Video Switching If the Operator Conference option is selected, this option is disabled, and the selection is cleared. For more information, see "Video Switching (VSW) Conferencing” on page 2-4. Operator Conference Select this option to define the profile of an Operator conference.
PAGE 327
Chapter 10-Operator Assistance & Participant Move Table 10-2 New Profile - Advanced Parameters (Continued) 6 Polycom, Inc. Field/Option Description Auto Terminate When selected (default), the conference automatically ends when the termination conditions are met: Before First Joins — No participant has connected to a conference during the n minutes after it started. Default idle time is 10 minutes.
PAGE 328
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 The New Profile – Video Quality dialog box opens.
PAGE 329
Chapter 10-Operator Assistance & Participant Move Table 10-3 New Profile - Video Quality Parameters (Continued) Field/Option Description Content Video Definition Content Settings Select the transmission mode for the Content channel: • Graphics — basic mode, intended for normal graphics • Hi-res Graphics — a higher bit rate intended for high resolution graphic display • Live Video — Content channel displays live video Selection of a higher bit rate for the Content results in a lower bit rate for the
PAGE 330
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 2 In the Profile field, select a Profile in which the Operator Conference option is selected. Upon selection of the Operator Conference Profile, the Display Name is automatically taken from the RMX User Login Name. This name cannot be modified. Only one Operator conference can be created for each User Login name.
PAGE 331
Chapter 10-Operator Assistance & Participant Move Table 10-4 New Conference – General Options (Continued) Field Description Routing Name Routing Name is the name with which ongoing conferences, Meeting Rooms, Entry Queues and SIP Factories register with various devices on the network such as gatekeepers and SIP servers. This name must be defined using ASCII characters. Comma, colon and semicolon characters cannot be used in the Routing Name.
PAGE 332
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 10-4 New Conference – General Options (Continued) 4 Field Description Enable ISDN/PSTN Dial-in Select this check box if you want ISDN and PSTN participants to be able to connect directly to the Operator conference. This may be useful if participants are having problems connecting to their conference and you want to identify the problem or help them connect to their destination conference.
PAGE 333
Chapter 10-Operator Assistance & Participant Move 2 Click the Save Conference to Template ( ) button. or Right-click and select Save Conference to Template. The conference is saved to a template whose name is taken from the ongoing conference Display Name (the Login name of the RMX User). The Template is displayed with the Operator Conference icon.
PAGE 334
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 2 Click the Start Conference from Template ( ) button. or Right-click and select Start Conference from Template. The conference is started. The name of the ongoing conference in the Conferences list is taken from the Conference Template Display Name. Monitoring Operator Conferences and Participants Requiring Assistance Operator conferences are monitored in the same way as standard ongoing conferences.
PAGE 335
Chapter 10-Operator Assistance & Participant Move Participants in Entry Queues who failed to enter the correct destination conference ID or the conference password will wait for operator assistance (provided that an Operator conference is active). When requiring or requesting operator assistance, the RMX management application displays the following: • The participant’s connection Status changes, reflecting the help request. For more information, see Table 10-5.
PAGE 336
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 This list is used as reference only. Participants can be assisted and moved to the Operator conference or the destination conference only from the Participants list of the Entry Queues or ongoing conference where they are awaiting assistance. The participants are automatically removed from the Participant Alerts list when moved to any conference (including the Operator conference).
PAGE 337
Chapter 10-Operator Assistance & Participant Move • Participants cannot be moved from a Telepresence conference. • Participants cannot be moved from LPR-enabled conferences to non-LPR conferences. Move from non-LPR conferences to LPR-enabled conferences is available. • Move between encrypted and non-encrypted conferences depends on the ALLOW_NON_ENCRYPT_PARTY_IN_ENCRYPT_CONF flag setting, as described in Table 10-6: Table 10-6 Participant Move Capabilities vs.
PAGE 338
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 2 In the Participants list, right-click the icon of the participant to move and select one of the following options: — Move to Operator Conference - to move the participant to the Operator conference. — Move to Conference - to move the participant to any ongoing conference. When selected, the Move to Conference dialog box opens, letting you select the name of the destination conference.
PAGE 339
11 Conference Templates Conference Templates enable administrators and operators to create, save, schedule and activate identical conferences. A Conference Template: • Saves the conference Profile. • Saves all participant parameters including their Personal Layout and Video Forcing settings. • Simplifies the setting up Telepresence conferences where precise participant layout and video forcing settings are crucial.
PAGE 340
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 • Participant properties are embedded in the Conference Template and therefore, if the participant properties are modified in the Address Book after the Conference Template has been created they are not applied to the participant whether the Template becomes an ongoing conference or not.
PAGE 341
Chapter 11-Conference Templates For more information see RealPresence Collaboration Server 1500/2000/4000 Getting Started Guide, “Customizing the Main Screen” on page 10. Clicking the anchor pin ( ) button hides the Conference Templates list as a closed tab. Toolbar Buttons The Conference Template toolbar includes the following buttons: Table 1 Conference Templates – Toolbar Buttons Button Description New Conference Template Creates a new Conference Template.
PAGE 342
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 The New Conference Template - General dialog box opens. 3 The fields of the New Template – General dialog box are identical to those of the New Conference – General dialog box. For a full description of the fields see the RealPresence Collaboration Server 1500/2000/4000 Getting Started Guide, "General Tab” on page 3-14. 4 Modify the fields of the General tab. A unique dial-in number must be assigned to each conferencing entity.
PAGE 343
Chapter 11-Conference Templates The New Template – Participants dialog box opens. The fields of the New Template – Participants dialog box are the same as those of the New Conference – Participant dialog box. For a full description of these fields see the RealPresence Collaboration Server 1500/2000/ 4000 Getting Started Guide, "Participants Tab” on page 3-17. 6 Optional. Add participants to the template from the Address Book. 7 Click the New button. The New Participant – General tab opens.
PAGE 344
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 For a full description of the General tab fields see “Adding a new participant to the Address Book Directly” on page 8. 8 Modify the fields of the General tab. 9 Click the Advanced tab. The New Participant – Advanced tab opens. For a full description of the Advanced tab fields see, “New Participant – Advanced Properties” on page 12. 10 Modify the fields of the Advanced tab. 11 Click the Media Sources tab. The Media Sources tab opens.
PAGE 345
Chapter 11-Conference Templates The Media Sources tab enables you to set up and save Personal Layout and Video Forcing settings for each participant. This is especially important when setting up Telepresence conferences. For a full description of Personal Layout and Video Forcing settings see the RealPresence Collaboration Server 1500/2000/4000 Getting Started Guide, "Changing the Video Layout of a Conference (AVC-Based Conferences)” on page 3-56 and "Video Forcing (AVC-based Conferences)” on page 3-58.
PAGE 346
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 The New Conference Template – Information tab opens. For a full description of the Information fields see the RealPresence Collaboration Server 1500/2000/4000 Getting Started Guide, “Information Tab” on page 20. 16 Click the OK button. The New Conference Template is created and its name is added to the Conference Templates list.
PAGE 347
Chapter 11-Conference Templates The conference is saved to a template whose name is taken from the ongoing conference Display Name (the Login name of the RMX User). The Template is displayed with the Operator Conference icon. Conference Templates saved from an ongoing conference does not include Message Overlay text messages. Starting an Ongoing Conference From a Template An ongoing conference can be started from any Template saved in the Conference Templates list.
PAGE 348
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 The conference is started. If a Conference Template is assigned a dial-in number that is already assigned to an ongoing conference, Meeting Room, Entry Queue or Gateway Profile, when the template is used to start an ongoing conference or schedule a reservation it will not start. However, the same number can be assigned to several conference templates provided they are not used to start an ongoing conference at the same time.
PAGE 349
Chapter 11-Conference Templates The conference is started. The name of the ongoing conference in the Conferences list is taken from the Conference Template Display Name. Scheduling a Reservation From a Conference Template (AVC Conferencing) A Conference Template can be used to schedule a single or recurring Reservation. To schedule a Reservation from a Conference Template: 1 In the Conference Templates list, select the Conference Template you want to schedule as a Reservation.
PAGE 350
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 The Display Name of the Reservation is taken from the Conference Template Display Name. Conference Template and Reservation Name For a full description of the Reservation Properties fields see Table 9-3, “New Reservation – Schedule Tab,” on page 9-11. 3 Modify the fields of the Reservation Properties. 4 Click the OK button. A Reservation is created based on the Conference Template.
PAGE 351
Chapter 11-Conference Templates Deleting a Conference Template One or several Conference Templates can be deleted at a time. To delete Conference Templates: 1 In the Conference Templates list, select the Template(s) you want to delete. 2 Click the Delete Conference Template ( ) button. or Right-click and select Delete Conference Template. A confirmation dialog box is displayed. 3 Click the OK button to delete the Conference Template(s).
PAGE 352
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Exporting Conference Templates Conference Templates are exported to a single XML file that can be used to import the Conference Templates on multiple MCUs.
PAGE 353
Chapter 11-Conference Templates The Conference Templates - Export dialog box is displayed. 3 In the Export Path field, type the path name to the location where you want to save the exported file or click Browse to select the desired path. 4 Optional. Clear the Export includes conference profiles check box when you only want to export Conference Templates. When this check box is cleared, the Conference Templates - Export dialog box is displayed without the Profiles file name field.
PAGE 354
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 2 Right-click the Conference Templates to be exported, and then click Export Selected Conference Templates. . The Conference Templates - Export dialog box is displayed. 3 In the Export Path field, type the path name to the location where you want to save the exported file or click Browse to select the desired path. 4 Optional. Clear the Export includes conference profiles check box when you only want to export Conference Templates.
PAGE 355
Chapter 11-Conference Templates 6 Click OK to export the Conference Templates and Conference Profiles to a file. Importing Conference Templates You can import Conference Templates and Conference Profiles from one MCU to multiple MCUs in your environment. To import Conference Templates: 1 In the RMX Web Client main window, click the Conference Templates tab. The Conference Templates are displayed.
PAGE 356
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 4 In the Import Path field, click Browse to navigate to the path and file name of the Conference Templates you want to import. When clicking the exported templates file you want to import, the system automatically displays the appropriate files in the Templates file name field and the Profiles file name field (when the Import includes conference profiles check box is selected).
PAGE 357
12 Polycom Conferencing for Microsoft Outlook® Polycom Conferencing for Microsoft Outlook is supported in AVC Conferencing Mode only. Polycom Conferencing for Microsoft Outlook is an add-in that enables users to easily organize and invite attendees to Video Enabled meetings via Microsoft Outlook®. Polycom Conferencing for Microsoft Outlook is implemented by installing the Polycom Conferencing Add-in for Microsoft Outlook on Microsoft Outlook® e-mail clients.
PAGE 358
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 A Gathering Slide is displayed to connected participants until the conference starts. Gathering Slide: Displays Meeting Information Until Conference Starts The Gathering Slide displays live video along with information taken from the meeting invitation such as the subject, meeting organizer, duration, dial-in numbers etc. At the end of the Gathering Phase, the conference layout is displayed.
PAGE 359
Chapter 12-Polycom Conferencing for Microsoft Outlook® There are three options that can be used to configure the Exchange Integration Configuration. The option you choose will depend on the configuration of the mailbox in the Exchange Server and the configuration of the Exchange Server itself. — Option 1 - Use this option if the Exchange Server settings have been left at their default values. — Option 2 - Use this option if the Primary SMTP Mailbox is not the default mailbox.
PAGE 360
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 12-1 Exchange Integration Configuration - Option 1 (Continued) b Field Description User Name Enter the User Name of the RMX, as registered in the Microsoft Exchange Server, that the RMX uses to login to its e-mail account. Field length: Up to 80 characters. Password Enter the Password the RMX uses to login to its e-mail account as registered in the Microsoft Exchange Server. Field length: Up to 80 characters.
PAGE 361
Chapter 12-Polycom Conferencing for Microsoft Outlook® a Define the following fields: Table 12-2 Exchange Integration Configuration - Option 2 Field Description Enable Calendaring Service Exchange Server Address User Name These fields are defined as for Option 1 above. Password Domain Accept Appointments Primary SMTP Mailbox (Optional) b Enter the name of the SMTP Mailbox in the Microsoft Exchange Server to be monitored by the RMX.
PAGE 362
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 a Define the following fields: Table 12-3 Exchange Integration Configuration - Option 3 Field Description Exchange Server Address If Exchange Server settings have been modified, enter the full path to the Microsoft Exchange Server where the RMX’s Microsoft Outlook e-mail account is registered, for example if the EWS folder has been renamed EWD: https://labexch01/EWD/Exchange.
PAGE 363
Chapter 12-Polycom Conferencing for Microsoft Outlook® • The meeting organizer can enable recording and/or streaming of the meeting. • If meeting is to be recorded, the Ad Hoc Entry Queue must have recording enabled in its Profile. For more information see "Defining New Profiles” on page 2-18. • Meetings can be single instance or have multiple occurrences. • Attendees that do not have video devices may be invited to the meeting.
PAGE 364
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Creating and Connecting to a Conference Creating a Conference Meetings are organized using the Microsoft Outlook client in the normal manner. If the meeting organizer decides that video participants are to be included in a multipoint video conference, he/she clicks the Polycom Conference button. Conference Information such as the Meeting ID and connection information is automatically added to the existing appointment information.
PAGE 365
Chapter 12-Polycom Conferencing for Microsoft Outlook® Table 12-4 summarizes the RMX’s usage of Microsoft Outlook data fields included in the meeting invitation. Table 12-4 Microsoft Outlook Field Usage Usage by the RMX / DMA Microsoft Outlook Field Subject Conference / Meeting Room Display Name of Conference / Meeting Room. Start/End Time Gathering Slide Meeting Name. Used to calculate the Conference’s Duration. Record Enable Recording in the Conference or Meeting Room Profile.
PAGE 366
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 • Participants outside the office or using PSTN or mobile phones, can use the dial in number in the meeting invitation to manually dial in to the meeting. RMX Standalone Deployment When using a single RMX in a standalone deployment, connection is via an Ad Hoc Entry Queue. The meeting is started when the first participant connects to the RMX.
PAGE 367
13 Conference and Participant Monitoring Skins IVR Info Administrator Operator Tab Chairperson Viewing Permissions You can monitor ongoing conferences and perform various operations while conferences are running. Three levels of monitoring are available with the RealPresence Collaboration Server (RMX): •  •   General Monitoring - You can monitor the general status of all ongoing conferences and their participants in the main window.
PAGE 368
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide General Monitoring Users can monitor a conference or keep track of its participants and progress. For more information, see RealPresence Collaboration Server 1500/2000/4000 Getting Started Guide, "Monitoring Ongoing Conferences” on page 3-39. You can click the blinking Participant Alerts indication bar to view participants that require attention. For more information, see "System and Participant Alerts” on page 21-1.
PAGE 369
Chapter 13-Conference and Participant Monitoring Conference Level Monitoring In addition to the general conference information that is displayed in the Conference list pane, you can view the details of the conference’s current status and setup parameters, using the Conference Properties dialog box. The tabs displayed in the Conference Properties dialog boxes are dependent on the Conferencing Mode and the Card Configuration Mode of the RMX—whether the RMX is configured with MPMx or MPM+ cards.
PAGE 370
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The following information is displayed in the General tab: Table 13-1 Conference Properties - General 13-4 Field Description Display Name The Display Name is the conference name in native language and Unicode character sets to be displayed in the RealPresence Collaboration Server Web Client. Note: This field is displayed in all tabs. Duration The expected duration of the conference using the format HH:MM.
PAGE 371
Chapter 13-Conference and Participant Monitoring Table 13-1 Conference Properties - General (Continued) Field Description Video Switching When selected, the conference is of ultra-high quality video resolution, in a special conferencing mode which implies that all participants must connect at the same line rate and use HD video. This feature utilizes the resources more wisely and efficiently by: • Saving utilization of video ports (1 port per participant as opposed to 4 ports in CP mode).
PAGE 372
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 2 Click the Advanced tab. The Conference Properties - Advanced dialog box opens. 3 The following information is displayed in the Advanced tab: Table 13-2 Conference Properties - Advanced Parameters 13-6 Field/Option Description Encryption Indicates whether the conference is encrypted. Packet Loss Compensation (LPR and DBA) Indicates whether Packet Loss Compensation is enabled.
PAGE 373
Chapter 13-Conference and Participant Monitoring Table 13-2 Conference Properties - Advanced Parameters (Continued) Field/Option Description TIP Compatibility Indicates the TIP Compatibility mode when implementing an RMX and Cisco Telepresence Systems (CTS) Integration solution. • None • • Video Only Video & Content The TIP Compatibility mode affects in the user video and content experience.
PAGE 374
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 5 The following information is displayed: Table 13-3 Profile - Gathering Settings Field/Options Description Enable Gathering Indicates whether the Gathering Phase has been enabled. Display Language Indicates the language of the Gathering Slide field headings.
PAGE 375
Chapter 13-Conference and Participant Monitoring The following information is displayed: Table 13-4 Conference Properties - Video Quality Parameters Field/Option Description People Video Definition Video Quality Indicates the resolution and frame rate that determine the video quality set for the conference. Possible settings are: Motion or Sharpness. For more information, see "Video Resolutions in AVCbased CP Conferencing” on page 3-1.
PAGE 376
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 13-4 Conference Properties - Video Quality Parameters (Continued) Field/Option Description Content Video Definition Content Settings Content Protocol Indicates the Content channel resolution set for the conference. Possible resolutions are: • Graphics – default mode • • • Hi-res Graphics – requiring a higher bit rate • H.
PAGE 377
Chapter 13-Conference and Participant Monitoring 7 Click the Video Settings tab to list the video parameters. Video Settings Administrator Operator Tab Chairperson Viewing Permissions  Table 13-5 Conference Properties - Video Settings Parameters Polycom, Inc. Field Description Presentation Mode When checked, indicates that the Presentations Mode is active. For more information, see "Presentation Mode” on page 2-30.
PAGE 378
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 13-5 Conference Properties - Video Settings Parameters (Continued) Field Description Auto Scan Interval(s) The time interval, 10 - 300 seconds, that Auto Scan uses to cycle the display of participants that are not in the conference layout in the selected cell. Video Layouts (graphic) Indicates the currently selected video layout. 8 Click the Audio Settings tab to view the audio setting for the conference.
PAGE 379
Chapter 13-Conference and Participant Monitoring Table 13-6 Customized Polling - Buttons Button Description Add All Add all participants to the list of participants to be Auto Scanned. All participants’ names are removed from the All Participants pane. Delete All Delete all participant from the list of participants to be Auto Scanned. All participants’ names are moved back to the All Participants pane. Up Select a participant and click this button to move the participant Up in the Scanning Order.
PAGE 380
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Viewing the Properties of an Ongoing SVC-based Conference To view the parameters of an ongoing SVC conference: 1 In the Conference list pane, double-click the SVC conference or right-click the SVC conference and then click Conference Properties. The Conference Properties - General dialog box with the General tab opens.
PAGE 381
Chapter 13-Conference and Participant Monitoring 3 Polycom, Inc. Field Description Conference Password Conference Password is not supported in SVC conferences. Chairperson Password Chairperson Password is not supported in SVC conferences. ID The conference ID. Profile The name of the conference Profile from which conference parameters were taken. Line Rate The maximum transfer rate, in kilobytes per second (Kbps) of the call (video and audio streams).
PAGE 382
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The Conference Properties - Advanced dialog box opens. 4 The following information is displayed in the Advanced tab: Table 13-7 Conference Properties - Advanced Parameters 5 13-16 Field/Option Description Encryption Encryption is not supported in SVC conferences. Packet Loss Compensation (LPR and DBA) Packet Loss Compensation is not supported in SVC conferences.
PAGE 383
Chapter 13-Conference and Participant Monitoring The Conference Properties - Video Quality dialog box opens. The following information is displayed: Table 13-8 Conference Properties - Video Quality Parameters Field/Option Description People Video Definition Video Quality Indicates the resolution and frame rate that determine the video quality set for the conference. In SVC conferencing, only Sharpness is supported.
PAGE 384
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 6 Click the Information tab to view general information defined for the conference. Changes made to this information once the conference is running are not saved to the CDR. 7 Click OK to close the Conference Properties dialog box. Monitoring Operator Conferences and Participants Requiring Assistance Operator conferences are monitored in the same way as standard ongoing conferences.
PAGE 385
Chapter 13-Conference and Participant Monitoring The following icons and statuses are displayed in the Participant Status column: Table 13-9 Participants List Status Column Icons and Indications Icon Status indication Description Awaiting Individual Assistance The participant has requested the operator’s assistance for himself/herself. Awaiting Conference Assistance The participant has requested the operator’s assistance for the conference.
PAGE 386
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • The duration of the icon display cannot be modified. Participant Alerts List The Participant Alerts list contains all the participants who are currently waiting for operator assistance.
PAGE 387
Chapter 13-Conference and Participant Monitoring Participant Level Monitoring In addition to conference information, you can view detailed information regarding the status and parameters of each listed participant, using the Participant Properties dialog box. Participant properties can be displayed for all participants currently connected to a conference and for defined participants that have been disconnected. Properties differ for IP and ISDN/PSTN participants.
PAGE 388
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The Media Sources dialog box enables you to mute participant’s audio, suspend participant’s video transmission and select a personal Video Layout for the participant.
PAGE 389
Chapter 13-Conference and Participant Monitoring Table 13-10 Participant Properties - Media Sources Parameters (Continued) Field Description Mute/Suspend Indicates if the endpoint’s audio and/or video channels have been muted/ suspended. The entity that initiated audio mute or video suspend is also indicated. • MCU – Audio or Video channel has been muted/suspended by the MCU. • • User – Channels have been muted/suspended by the RMX user.
PAGE 390
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 13-11 Participant Properties - Connection Status Parameters (Continued) 3 Field Description Connection Time The date and time the participant connected to the conference. Note: The time format is derived from the MCU’s operating system time format. Disconnection Time The date and time the defined participant disconnected from the conference.
PAGE 391
Chapter 13-Conference and Participant Monitoring SIP Participant (AVC-based and SVC-based) Channel Status Administrator Operator Tab Chairperson Viewing Permissions  Table 13-12 Participant Properties - H.245/SDP Parameters 4 Polycom, Inc. Field Description Remote Capabilities Lists the participant’s capabilities as declared by the endpoint. Remote Communication Mode Displays the actual capabilities used by the endpoint when establishing the connection with the MCU (Endpoint to MCU).
PAGE 392
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 13-13 Participant Properties - Channel Status Parameters 13-26 Field Description Channels Used When checked, indicates the channel type used by the participant to connect to the conference: Incoming channels are endpoint to MCU, Outgoing channels are from MCU to endpoint. Channels: • H.225/Signaling - The call-signaling channel. • H.245/SDP - The Control channel.
PAGE 393
Chapter 13-Conference and Participant Monitoring Table 13-13 Participant Properties - Channel Status Parameters (Continued) Polycom, Inc. Field Description Sync Status Channel - The channel type: Video or Content. Source - The name of the participant currently viewed by this participant. Position - The video layout position indicating the place of each participant as they appear in a conference.
PAGE 394
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 5 Click the Channel Status Advanced tab to view additional information for selected audio and video channels.
PAGE 395
Chapter 13-Conference and Participant Monitoring Table 13-14 Participant Properties - Channel Status Advanced Parameters (Continued) Polycom, Inc. Field Description Participant IP Address The IP address and the transport protocol (TCP/UDP) of the participant and the port number allocated to the media stream on the participant side. ICE RMX IP Address The IP address, port number, and transport protocol of the MCU used to pass through the media when ICE is functional.
PAGE 396
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 6 Optional for H.323 AVC-based participants. Click the Gatekeeper Status tab to view its parameters. Administrator Operator Tab Gatekeeper Status Chairperson Viewing Permissions  Table 13-15 Participant Properties - Gatekeeper Status Parameters 13-30 Field Description Requested Bandwidth The bandwidth requested by the MCU from the gatekeeper.
PAGE 397
Chapter 13-Conference and Participant Monitoring 7 Optional for SIP AVC-based and SVC-based participants. Click the Call Admission Control tab to view its parameters. Administrator Operator Tab Gatekeeper Status Chairperson Viewing Permissions  Table 13-16 Participant Properties - Gatekeeper Status Parameters Polycom, Inc. Field Description Requested Bandwidth The bandwidth requested by the MCU from the SIP server.
PAGE 398
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Monitoring SIP BFCP Content In the SIP Participant Properties dialog box, BFCP status information appears in: • All three panes of the SDP tab. • The Channel Status tab. • The Channel Status -Advanced tab. SDP Channel Status Channel Status - Advanced For more information see "Participant Level Monitoring” on page 13-21. 13-32 Polycom, Inc.
PAGE 399
Chapter 13-Conference and Participant Monitoring Monitoring ISDN/PSTN Participants Using the Participant Properties dialog box, you can monitor and verify the properties of an ISDN/PSTN participant. The dialog box’s tabs contain information that is relevant to the participant’s status only while the conference is running and is used to monitor the participant’s status when connection problems occur. Maximum line rate at which ISDN endpoints can connect to a conference is 768 kbps.
PAGE 400
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The Participant Properties - Media Sources dialog box is displayed. Table 13-18 ISDN/PSTN Participant Properties - Media Sources Field Description Mute/Suspend Indicates if the endpoint’s audio and/or video channels from the endpoint have been muted/suspended. The entity that initiated audio mute or video suspend is also indicated. • MCU – Audio or Video channel has been muted/suspended by the MCU.
PAGE 401
Chapter 13-Conference and Participant Monitoring 2 Click the H.221 tab to view additional information that can help to resolve connection issues. List’s the endpoint’s capabilities as retrieved from the remote site Displays the endpoint’s actual capabilities used for the connection Displays the MCU’s capabilities used for connection with the participant Table 13-19 Participant Properties - H.221 Parameters Polycom, Inc.
PAGE 402
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 3 Click the Connection Status tab to view general information regarding the participant connection and disconnection causes of the participant to the conference. Table 13-20 ISDN/PSTN Participant Properties - Connection Status 13-36 Field Description Status Indicates the connection status of the participant to the conference. If there is a problem, the appropriate status is displayed, for example, Disconnected.
PAGE 403
Chapter 13-Conference and Participant Monitoring 4 Click the Channel Status tab to view the status of a participant’s channels. Table 13-21 ISDN/PSTN Participant Properties - Channel Status Polycom, Inc. Field Description Connected Media Indicates if the participant is connected with Audio, Video and Content media channels. Channels Used • Channel – Indicates the channel used by the participants and whether the channel is connected (indicated with a check mark) or disconnected.
PAGE 404
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 13-21 ISDN/PSTN Participant Properties - Channel Status Field Description Content Token A check mark indicates that the participant is the current holder of the Content Token.
PAGE 405
14 Recording Conferences Conference recording is available in AVC Conferencing Mode only. Conferences running on the RMX can be recorded using a Polycom® RSS™ Recording and Streaming Server (RSS). The recording system can be installed at the same site as the conferencing MCU or at a remote site. Several MCU’s can share the same recording system. Recording conferences is enabled via a Recording Link, which is a dial-out connection from the conference to the recording system.
PAGE 406
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Creating Multiple Virtual Recording Rooms on the RSS If the environment includes a Polycom® RSS™ 4000 Version 6.0 Recording and Streaming Server (RSS) and you want to associate Recording Links on the RMX with Virtual Recording Rooms (VRR), created and saved on the Polycom® RSS™ 4000 Version 6.0 perform the following operations on the RSS: 1 Modify the parameters of a recording Template to meet the recording requirements.
PAGE 407
Chapter 14-Recording Conferences The New Recording Link dialog box is displayed. 3 Define the following parameters: Table 14-1 Recording Link Parameters Parameter Description Name Displays the default name that is assigned to the Recording Link. If multiple Recording Links are defined, it is recommended to use a descriptive name to be indicate the VRR to which it will be associated. Default: Recording Link Type Select the network environment: • H.
PAGE 408
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 4 Click OK. The Recording Link is added to the RMX unit. Enabling the Recording Features in a Conference IVR Service To record a conference, a Conference IVR Service in which the recording messages and DTMF codes are activated must be assigned to the conference.
PAGE 409
Chapter 14-Recording Conferences 7 To modify the DTMF code or permission for a recording function: a Select the desired DTMF name (Start, Stop or Pause Recording), click the DTMF code entry and type a new code.
PAGE 410
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 4 Select the Enable Recording check box. 5 Define the following parameters: Table 14-3 Conference Profile Recording Parameters Parameter Description Enable Recording Select to enable Recording Settings in the dialog box. Recording Link Select a recording link for the conference from the list.
PAGE 411
Chapter 14-Recording Conferences Recording Link Encryption The Recording Link can be encrypted when recording an encrypted conference. The encryption of the Recording Link is enabled when Encryption is selected in the Conference Profile on the RMX and on the RSS, and the system flag ALLOW_NON_ENCRYPT_RECORDING_LINK_IN_ENCRYPT_CONF is set to NO. Recording Link Encryption Guidelines: • The Recording Link connection type must be H.323. • The Recording Link uses the AES encryption format.
PAGE 412
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Recording Link Settings The recording of encrypted conferences via an encrypted Recording Link is enabled in the Conference Profile by: • Selecting the Encryption option (Encrypt All or Encrypt when Possible) in the Advanced tab. For more details, see "Media Encryption (AVC Only)” on page 4-40. • Setting the Recording options in the Recording tab. For more details, see "Enabling the Recording in the Conference Profile” on page 14-5. .
PAGE 413
Chapter 14-Recording Conferences Recording Link Layout When the video layout of the conference is set to Auto Layout, the recording of the conference will now include all the conference participants and not n-1 participants as in previous versions. In the new Auto Layout algorithm, the Recording Link is counted as a “participant” and therefore it is excluded from the layout display used for the recording. The layout used for the other participants will behave as in the “standard” Auto Layout behavior.
PAGE 414
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Using the RealPresence Collaboration Server Web Client to Manage the Recording Process To manage the recording process using the right-click menu: >> Right-click the Recording participant in the conference and select from one of the following options: The Recording participant does not support H.264 High Profile.
PAGE 415
Chapter 14-Recording Conferences To manage the recording process using the Conference toolbar: >> In the Conferences pane, click one of the following buttons in the Conference tool bar. The recording buttons will only be displayed in the conference tool bar for a conference that is recording-enabled. Table 14-2 Conferences List - Recording Tool bar buttons Button Description Start/Resume recording. This button toggles with the Pause button. Stop recording. Pause recording.
PAGE 416
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Once added to the conference, the MCU automatically connects the participant (the link to Codian VCR) and the recording is automatically started on the Codian VCR. A connection can also be defined on the Codian VCR, dialing into the recorded conference using the MCU prefix and the Conference ID as for any other dial-in participant in the conference.
PAGE 417
15 Users, Connections and Notes Users RealPresence Collaboration Server Web Client Users are defined in the User’s table and can connect to the MCU to perform various operations. A maximum of 100 users can be defined per MCU.
PAGE 418
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Chairperson A Chairperson can only manage ongoing conferences and participants. The Chairperson does not have access to the RMX configurations and utilities. Auditor An Auditor can only view Auditor Files and audit the system. Machine Account User names can be associated with servers (machines) to ensure that all users are subject to the same account and password policies.
PAGE 419
Chapter 15-Users, Connections and Notes • The server hosting an application-user whose password is about to expire will receive a login response stating the number of days until the application-user’s password expires. This is determined by the value of the PASSWORD_EXPIRATION_WARNING_DAYS System Flag. The earliest warning can be displayed 14 days before the password is due to expire and the latest warning can be displayed 7 days before passwords are due to expire.
PAGE 420
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The Users pane is displayed. The list includes three columns: User Name, Authorization Level and Disabled. The User Name is the login name used by the user to connect to the MCU. The Authorization indicates the Authorization Level assigned to the User: Administrator, Administrator Read-only, Operator, Chairperson or Auditor.
PAGE 421
Chapter 15-Users, Connections and Notes 4 In the User Name text box, enter the name of the new user. This is the login name used by the user when logging into the system. 5 In the Password text box, enter the new user’s password. This will be the user’s password when logging into the system. 6 In the Authorization Level list, select the user type: Administrator, Administator ReadOnly, Operator, Chairperson or Auditor. 7 Optional.
PAGE 422
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 3 Enter the Old Password (current), New Password and Confirm the New Password. The Password must be in ASCII. 4 Click OK. The user’s password is changed. Disabling a User An administrator can disable an enabled user. An indication is displayed in the Users List when the User is disabled. An administrator can enable a disabled User. To disable a user: 1 In the RMX Management pane, click the Users ( ) button.
PAGE 423
Chapter 15-Users, Connections and Notes 2 Right-click the user to be enabled and select Enable User. A confirmation box is displayed. 3 Click YES. The User status in the Users list - Disabled column changes to NO. Renaming a User To rename a user: 1 In the RMX Management pane, click the Users ( ) button. The Users pane is displayed. 2 Right-click the user to be renamed and select Rename User. The Rename User dialog box is displayed.
PAGE 424
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Connections The RealPresence Collaboration Server enables you to list all connections that are currently logged into the MCU, e.g. users, servers or API users. The MCU issues an ID number for each login. The ID numbers are reset whenever the MCU is reset. A maximum of 50 users can be concurrently logged in to the MCU.
PAGE 425
Chapter 15-Users, Connections and Notes • Locking out User. • Displaying the User Login record. Controlling the user sessions includes: • Limiting the maximum number of concurrent user sessions. • User session timeout. • Limiting the maximum number of users that can connect to the system.
PAGE 426
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Managing the User Login Process Implementing Strong Passwords Strong Passwords can be implemented for logging into the RMX management applications. They can be implemented when the system is in standard security mode or when in Ultra Secure Mode.
PAGE 427
Chapter 15-Users, Connections and Notes Implementing Password Re-Use / History Rules Users are prevented from re-using previous passwords by keeping a list of previous passwords. If a password is recorded in the list, it cannot be re-used. The list is cyclic, with the most recently recorded password causing the deletion of the oldest recorded password. • The number of passwords that are recorded is determined by the value of the PASSWORD_HISTORY_SIZE System Flag. Possible values are between 0 and 16.
PAGE 428
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Defining Password Change Frequency The frequency with which a user can change a password is determined by the value of the MIN_PWD_CHANGE_FREQUENCY_IN_DAYS System Flag. The value of the flag is the number of days that users must retain a password. • Possible retention period is between 0 and 7 days. In Ultra Secure Mode the retention period is between 1 (default) and 7.
PAGE 429
Chapter 15-Users, Connections and Notes A system reset does not reset the Login attempts counter. The time period during which the three consecutive Login failures occur is determined by the value of the USER_LOCKOUT_WINDOW_IN_MINUTES System Flag. A flag value of 0 means that three consecutive Login failures in any time period will result in User Lockout. Value can be between 0 and 45000. The duration of the Lockout of the user is determined by the value of the USER_LOCKOUT_DURATION_IN_MINUTES System Flag.
PAGE 430
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Any attempt to exceed the maximum number of management sessions per system results in the display of an error message: Maximum number of permitted user connections has been exceeded. New connection is denied. The log in attempt is recorded as an Audit Event.
PAGE 431
Chapter 15-Users, Connections and Notes 2 In the Notes toolbar, click the New Note ( Notes window and select New Note. ) button, or right-click anywhere inside the 3 In the Note dialog box, type the required text and click OK. The new note is saved and closed. The Notes list is updated, listing the new note and its properties: — Note – The beginning of the note’s text. — Last Modified – The date of creation or last modification. — Modified By – The Login Name of the user who last modified the note.
PAGE 432
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 15-16 Polycom, Inc.
PAGE 433
16 Network Services To enable the RealPresence Collaboration Server (RMX) to function within IP and ISDN/ PSTN network environments, network parameters must be defined for both the IP Network Services and ISDN/PSTN Network Services. The IP Network Service must be defined for the RMX, while the ISDN/PSTN Network Service definition is optional and is done when the RTM ISDN cards are installed in the MCU.
PAGE 434
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • IPv6 & IPv4 When IPv4 is selected, IPv6 fields are not displayed and conversely when IPv6 is selected, IPv4 fields are not displayed. When IPv6 & IPv4 is selected both IPv6 and IPv4 fields are displayed. For the purposes of comprehensive documentation, all screen captures in this chapter show the dialog boxes as displayed with IPv6 & IPv4 selected.
PAGE 435
Chapter 16-Network Services For more information, see the RealPresence Collaboration Server (RMX) 1500/2000/4000 Getting Started Guide, "Procedure 1: First-time Power-up” on page 2-25. Changes made to any of these parameters only take effect when the RMX is reset. An Active Alarm is created when changes made to the system have not yet been implemented and the MCU must be reset.
PAGE 436
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 3 Modify the following fields: Table 16-1 Default Management Network Service – IP Field Description Network Service Name Displays the name of the Management Network. This name cannot be modified. Note: This field is displayed in all Management Network Properties tabs. IP Version IPv4 Select this option for IPv4 addressing only. IPv6 Select this option for IPv6 addressing only.
PAGE 437
Chapter 16-Network Services Table 16-1 Default Management Network Service – IP (Continued) Field Description Control Unit IP Address IPv4 The IPv4 address of the RMX. This IP address is used by the RealPresence Collaboration Server Web Client to connect to the RMX. The IPv6 address of the MCU. This IP address is used by the RealPresence Collaboration Server Web Client to connect to the RMX.
PAGE 438
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 4 Click the Routers tab. 5 Modify the following fields: Table 16-2 Default Management Network Service – Routers Field Description Default Router IP Address IPv4 IPv6 16-6 Enter the IP address of the default router. The default router is used whenever the defined static routers are not able to route packets to their destination. The default router is also used when host access is restricted to one default router.
PAGE 439
Chapter 16-Network Services Table 16-2 Default Management Network Service – Routers (Continued) Field Description Static Routes IPv4 Only Table The system uses Static Routes to search other networks for endpoint addresses that are not found on the local LAN. Up to five routers can be defined in addition to the Default Router. The order in which the routers appear in the list determines the order in which the system looks for the endpoints on the various networks.
PAGE 440
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 6 Click the DNS tab. 7 Modify the following fields: Table 16-3 Default Management Network Service – DNS Field Description MCU Host Name Enter the name of the MCU on the network. Default name is RMX DNS Select: • Off – if DNS servers are not used in the network. • Specify – to enter the IP addresses of the DNS servers. Note: The IP address fields are enabled only if Specify is selected.
PAGE 441
Chapter 16-Network Services RMX 1500/4000 : If you want to modify the LAN Port Speed Settings on an RMX 1500/ 4000 see "Ethernet Settings” on page 16-24. 9 View or modify the following fields: Table 16-4 Management Network Properties – LAN Ports Parameters Field Port Speed Polycom, Inc. Description The RealPresence Collaboration Server (RMX) 2000 has 3 LAN ports. The administrator can set the speed and transmit/receive mode manually for LAN 2 Port only. Port The LAN port number: 1, 2 or 3.
PAGE 442
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 10 Click the Security tab. 11 Modify the following fields: Table 16-5 Management Network Properties – Security Parameters Field Description Secured Communication Select to enable Secured Communication. The RMX supports TLS 1.0 and SSL 3.0 (Secure Socket Layer). A SSL/TLS Certificate must installed on the RMX for this feature to be enabled. For more information see "Secure Communication Mode” on page F-1.
PAGE 443
Chapter 16-Network Services Modifying the Default IP Network Service The Default IP Service parameters need to be modified if you want to change the: • Network type that the RMX connects to • IP address of the RMX Signaling Host • IP addresses of the RMX Media boards • Subnet mask of the RMX’s IP cards • Gatekeeper parameters or add gatekeepers to the Alternate Gatekeepers list • SIP server parameters Fast Configuration Wizard The Fast Configuration Wizard enables you to configure the Default I
PAGE 444
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 3 Modify the following fields: Table 16-6 Default IP Network Service – IP Field Description Network Service Name The name Default IP Service is assigned to the IP Network Service by the Fast Configuration Wizard. This name can be changed. Note: This field is displayed in all IP Signaling dialog boxes and can contain character sets that use Unicode encoding.
PAGE 445
Chapter 16-Network Services 4 Click the Routers tab. With the exception of IP Network Type, the field definitions of the Routers tab are the same as for the Default Management Network. For more information see "Click the Routers tab.” on page 16-6. 5 Optional. Click the DNS tab. Settings in this dialog box are relevant to Multiple Network Services only. For more information see "Multiple Network Services” on page 16-49. Polycom, Inc.
PAGE 446
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 6 Click the Gatekeeper tab. 7 Modify the following fields: Table 16-7 Default IP Service – Conferencing – Gatekeeper Parameters 16-14 Field Description Gatekeeper Select Specify to enable configuration of the gatekeeper IP address. When Off is selected, all gatekeeper options are disabled. Primary Gatekeeper IP Address or Name Enter either the gatekeeper’s host name as registered in the DNS or IP address.
PAGE 447
Chapter 16-Network Services Table 16-7 Default IP Service – Conferencing – Gatekeeper Parameters (Continued) Field Description Refresh Registration every __ seconds The frequency with which the system informs the gatekeeper that it is active by re-sending the IP address and aliases of the IP cards to the gatekeeper. If the IP card does not register within the defined time interval, the gatekeeper will not refer calls to this IP card until it reregisters. If set to 0, re-registration is disabled.
PAGE 448
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The port range recommended by IANA (Internet Assigned Numbers Authority) is 49152 to 65535. The RMX uses this recommendation along with the number of licensed ports to calculate the port range.
PAGE 449
Chapter 16-Network Services 10 If required, click the QoS tab. Quality of Service (QoS) is important when transmitting high bandwidth audio and video information. QoS can be measured and guaranteed in terms of: • Average delay between packets • Variation in delay (jitter) • Transmission error rate DiffServ and Precedence are the two QoS methods supported by the RMX. These methods differ in the way the packet’s priority is encoded in the packet header.
PAGE 450
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 16-9 Default IP Service – Conferencing – QoS Parameters (Continued) Field Description Type DiffServ and Precedence are two methods for encoding packet priority. The priority set here for audio video and IP Signaling packets should match the priority set in the router. • DiffServ: Select when the network router uses DiffServ for priority encoding. The default priorities for both audio and video packets is 0x88.
PAGE 451
Chapter 16-Network Services 12 Click the SIP Servers tab. 13 Modify the following fields: Table 16-10 Default IP Network Service – SIP Servers Field Description SIP Server Select: • • SIP Server Type Off – if SIP servers are not present in the network. Select: Generic - for non Microsoft environments. • • Polycom, Inc. Specify – to manually configure SIP servers. Microsoft - for Microsoft environments.
PAGE 452
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 16-10 Default IP Network Service – SIP Servers (Continued) Field Description Create Certificate This button is used to create a Certificate Request to be sent to a Certification Authority. Certificate Method Select the method for sending the Certificate to the RMX: • CSR • PEM/PFX For more information see "The Security Certificate” on page H-37.
PAGE 453
Chapter 16-Network Services 14 Click the Security tab. 15 Modify the following fields: Table 16-11 Default IP Network Service – Security (SIP Digest) Field Description SIP Authentication Select to enable SIP server authentication. User Name Enter the conference, Entry Queue or Meeting Room name as registered with the proxy. Password Enter the conference, Entry Queue or Meeting Room password as defined with the proxy. H.323 Authentication Select to enable H.323 server authentication.
PAGE 454
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 16 Optional. To configure the ICE environment, click the SIP Advanced tab. 17 Modify the following fields: Table 16-12 Default IP Network Service – SIP Advanced Field Description Server User Name Enter the RMX User name as defined in the Active Directory. For example, enter rmx1234. This field is disabled if the ICE Environment field is set to None.
PAGE 455
Chapter 16-Network Services The network service Properties dialog box is displayed. 19 Modify the following fields: Table 16-13 Network Service - V35 tab Field Description V35 Gateway IP Address Enter the Management IP address of the management interface of the Serial Gateway. For more information see the Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Deployment Guide for Maximum Security Environments, "Deploying a Polycom RMX™ Serial Gateway S4GW” on page 19-29.
PAGE 456
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Ethernet Settings In the RMX 1500/4000 the automatically identified speed and transmit/receive mode of each LAN port used by the system can be manually modified if the specific switch requires it. These settings can be modified in the Ethernet Settings dialog box and they are not part of the Management Network dialog box as for the RealPresence Collaboration Server (RMX) 2000.
PAGE 457
Chapter 16-Network Services The Ethernet Settings dialog box opens. RealPresence Collaboration Server (RMX) 1500 RealPresence Collaboration Server (RMX) 4000 RMX 1500/4000 : Although the RTM LAN (media card) ports are shown as Port 1 in the Ethernet Settings and Hardware Monitor, the physical LAN connection is Port 2. Polycom, Inc.
PAGE 458
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 2 Modify the following field: Table 16-15 Ethernet Settings Parameters Field Speed 3 16-26 Description The RMX has 3 LAN ports on the RTM-IP (Management, Signaling and Shelf Management), and additional LAN ports on each media card (RTM LAN) and RTM ISDN cards. The administrator can set the speed and transmit/receive mode manually for these ports. Port The LAN port number.
PAGE 459
Chapter 16-Network Services IP Network Monitoring The Signaling Monitor 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. To monitor signaling status: 1 In the RMX Management pane, click Signaling Monitor ( ). 2 In the Signaling Monitor pane, double-click Default IP Service.
PAGE 460
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 16-16 IP Network Services Properties – RMX CS IP (Continued) Field IPv6 Description Scope Default Router IP Address 3 IP Address Global The Global Unicast IP address of the RMX. Site-Local The IP address of the RMX within the local site or organization. The IP address of the default router. The default router is used whenever the defined static routers are not able to route packets to their destination.
PAGE 461
Chapter 16-Network Services Table 16-17 IP Network Services Properties – H.323 (Continued) Field Registration Interval 4 Description The interval in seconds between the Signaling Host’s 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. Role Active - The active gatekeeper. Backup - The backup gatekeeper that can be used if the connection to the preferred gatekeeper fails.
PAGE 462
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 16-18 IP Network Services Properties – SIP Servers (Continued) 5 Field Description Status The connection state between the SIP Server and the Signaling Host. Not Available - No SIP server is available. Auto - Gets information from DHCP, if used. Click the ICE Servers tab.
PAGE 463
Chapter 16-Network Services Table 16-19 IP Network Services Properties – ICE Servers (Continued) Field Description Status 1/2/3/4 A status is displayed for each media card installed in the RMX: • Connection O.K.
PAGE 464
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Using IPv6 Networking Addresses for RMX Internal and External Entities IPv6 addresses can be assigned to both RMX (Internal) and External Entity addresses.
PAGE 465
Chapter 16-Network Services Configuration Requirements LAN Redundancy is available by default and is enabled by connecting the appropriate LAN cables to the LAN ports on the RMX as follows: RealPresence Collaboration Server (RMX) 1500 • Connect the additional LAN cable to LAN 1 port on the RTM IP. RealPresence Collaboration Server (RMX) 2000 On a RealPresence Collaboration Server (RMX) 2000, an RTM LAN card is required.
PAGE 466
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • LAN 1 port can be used to define a second Network Service or for LAN Redundancy Redundant ports LAN 1 LAN 2 Figure 16-1 RealPresence Collaboration Server (RMX) 1500 - RTM IP 1500 on Rear Panel On the RealPresence Collaboration Server (RMX) 2000 and RealPresence Collaboration Server (RMX) 4000, the LAN 1 and LAN 2 port on the RTM LAN card can be used as redundant media ports.
PAGE 467
Chapter 16-Network Services Signaling and Management Redundancy RealPresence Collaboration Server (RMX) 1500 On the RealPresence Collaboration Server (RMX) 1500, for Signaling and Management Redundancy, the MNG port is redundant to the MNG B port and must have a LAN cable connected.
PAGE 468
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 16-21 RMX 1500 / 4000 - Signaling and Management Redundancy - System Flags Port Usage Flag / Value LAN_REDUNDANCY = YES MULTIPLE_SERVICES = YES LAN 2 / MNG B (RMX 1500) LAN 3 / MNG (RMX 1500) Management Management Hardware Monitor Indications When LAN Redundancy is enabled on the RMX, LAN 2 port is Active.
PAGE 469
Chapter 16-Network Services Three Network Traffic Control Flags are added: • ENABLE_TC_PACKAGE When the flag is set to NO (default), Network Traffic Control is disabled on the RMX. Set the flag to YES to enable Network Traffic Control. • TC_BURST_SIZE This flag regulates the Traffic Control buffer or maxburst size as a percentage of the participant line rate. In general, higher traffic rates require a larger buffer.
PAGE 470
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide RealPresence Collaboration Server (RMX) Network Port Usage The following table summarizes the port numbers and their usage in the Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000: Table 16-23 RMX Network Port Usage Summary 16-38 Connection Type Port Number Protocol Description Configurable HTTP 80 TCP Management between the RMX and RealPresence Collaboration Server Web Client.
PAGE 471
Chapter 16-Network Services Table 16-23 RMX Network Port Usage Summary (Continued) Polycom, Inc. Connection Type Port Number Protocol Description Configurable Alternative SIP server 5060 60000 UDP, TCP Connection to the alternate SIP Server. Sometimes port 60000 is used when the system cannot reuse the TCP port. This port can be set in the Central signaling (CS) configuration file. Yes - in the IP service. SIP Outbound proxy 5060 60000 UDP, TCP Connection to the SIP outbound proxy.
PAGE 472
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide ISDN/PSTN Network Services To enable ISDN and PSTN participants to connect to the MCU, an ISDN/PSTN Network Service must be defined. A maximum of two ISDN/PSTN Network Services, of the same Span Type (E1 or T1) can be defined for the RMX. Each Network Service can attach spans from either or both cards.
PAGE 473
Chapter 16-Network Services Adding/Modifying ISDN/PSTN Network Services The system administrator can use the RMX Management – ISDN/PSTN Network Services section of the RealPresence Collaboration Server Web Client to add a second ISDN/PSTN Network Service or modify the first ISDN/PSTN Network Service. A new ISDN/PSTN Network Service can be defined even if no RTM ISDN card is installed in the system.
PAGE 474
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The Fast Configuration Wizard sequence begins with the ISDN/PSTN dialog box: 3 Define the following parameters: Table 16-24 ISDN Service Settings Field Description Network Service Name Specify the service provider’s (carrier) name or any other name you choose, using up to 20 characters. The Network Service Name identifies the ISDN/PSTN Service to the system.
PAGE 475
Chapter 16-Network Services The PRI Settings dialog box is displayed: 5 Define the following parameters: Table 16-25 PRI Settings Polycom, Inc. Field Description Default Num Type Select the Default Num Type from the list. The Num Type defines how the system handles the dialing digits. For example, if you type eight dialing digits, the Num Type defines whether this number is national or international.
PAGE 476
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 16-25 PRI Settings (Continued) 6 Field Description Dial-out Prefix Enter the prefix that the PBX requires to dial out. Leave this field blank if a dial-out prefix is not required. The field can contain be empty (blank) or a numeric value between 0 and 9999. Default: Blank Click Next.
PAGE 477
Chapter 16-Network Services Table 16-26 Span Definition (Continued) Field Description Line Coding Select the PRI line coding method from the list. • For T1 spans, default is B8ZS. • Switch Type For E1 spans, default is HDB3. Select the brand and revision level of switch equipment installed in the service provider’s central office. • For T1 spans, default is AT&T 4ESS. • For E1 spans, default is EURO ISDN. Note: For T1 configurations in Taiwan, Framing must be set to ESF and Line Coding to B8ZS.
PAGE 478
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • • A range must include at least two dial-in numbers. A range cannot exceed 1000 numbers. 11 Click OK. The new range is added to the Dial-in Phone Numbers table. 12 Optional. Repeat steps 8 to 10 to define additional dial-in ranges. 13 Enter the MCU CLI (Calling Line Identification). In a dial-in connections, the MCU CLI indicates the MCU’s number dialed by the participant.
PAGE 479
Chapter 16-Network Services 16 Attach spans to existing Network Services, by marking the appropriate check boxes in the Attached field. Each ISDN/PSTN card can support 7 E1 or 9 T1 PRI lines. 17 Click Save & Close. Modifying an ISDN/PSTN Network Service To Modify an ISDN/PSTN Network Service: 1 In the RMX Management pane, click the ISDN/PSTN Network Services ( ) icon. 2 In the ISDN/PSTN Network Services list, double-click the ISDN or right-click the ISDN entry and select Properties.
PAGE 480
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide — Spans • Attached All other ISDN Properties can only be modified only by deleting the ISDN/PSTN network service and creating a new PSTN service using the Fast Configuration Wizard. For more information, see "To Add an ISDN/PSTN Network Service:” on page 16-41.
PAGE 481
Chapter 16-Network Services RealPresence Collaboration Server (RMX) 1500/RealPresence Collaboration Server (RMX) 4000 On the RealPresence Collaboration Server (RMX) 1500 and RealPresence Collaboration Server (RMX) 4000, Media, Signaling and Management Networks are physically separated to provide enhanced security. The IP Network Service and the Default Management Network have been logically and physically separated from each other.
PAGE 482
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Figure 16-5 RealPresence Collaboration Server (RMX) 4000 - Multiple Network Topology Sample Guidelines • Multiple Services system mode is a purchasable option and it is enabled in the MCU license. • Multiple Services system mode is enabled when the system configuration flag MULTIPLE_SERVICES is added and set to YES. The MULTIPLE_SERVICE System Flag cannot be set to YES when IPv6 Addressing is enabled.
PAGE 483
Chapter 16-Network Services • On the RealPresence Collaboration Server (RMX) 1500, up to two Network Services, one per LAN port, can be associated with each Media card. • On the RealPresence Collaboration Server (RMX) 2000/RealPresence Collaboration Server (RMX) 4000, RTM ISDN or RTM LAN can be used for Multiple Services configuration.
PAGE 484
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • Participants are associated with a Network Service and use it resources as follows: — Dial-in participants - according to the network used to place the call and connect to the RMX. — Dial-out participant - according to the Network Service selected during the participant properties definition or during conference definition, according to the Network Service selected as default.
PAGE 485
Chapter 16-Network Services 2 Collaboration Server (RMX) 1500/2000/4000 Getting Started Guide Getting Started Guide, "Gather Network Equipment and Address Information” on page 2-1. Hardware Installation and Setup 3 — Mount the RMX in a rack. For more details see the RealPresence Collaboration Server (RMX) 1500/2000/4000 Getting Started Guide Getting Started Guide, "Hardware Installation and Setup” on page 2-8. — Connect the necessary cables.
PAGE 486
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 4 Modify the required System Flag to enable Multiple Services, DO NOT reset the MCU yet. 5 Connect the additional network cables to the RMX and change existing connections to match the required configuration as described in the "RealPresence Collaboration Server (RMX) Hardware Installation” on page 16-55. At this point, the Management Network can be modified to match the required local network settings.
PAGE 487
Chapter 16-Network Services Table 16-30 Network Equipment and Address Information per IP Network Service (Continued) Parameter Local Network Settings Media Board IP address (MPM 4) RealPresence Collaboration Server (RMX) 4000 only Note If more than one media card is associated with this Network Service Gatekeeper IP address (optional) DNS IP address (optional) Only one DNS can be defined for the entire Network topology SIP Server IP address (optional) RealPresence Collaboration Server (RMX) Hardware
PAGE 488
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Connecting the cables to the RTM LAN: Table 16-32 LAN Connections to the RTM LAN RTM LAN Port Description LAN 1 Signaling and Media - additional (second) Network Service LAN 2 Signaling and Media - existing (first) Network Service Figure 16-6 shows the cables connected to the RealPresence Collaboration Server (RMX) 4000 rear panel, when one RTM ISDN and three RTM LAN cards are installed providing IP and ISDN connect
PAGE 489
Chapter 16-Network Services RealPresence Collaboration Server (RMX) 2000 Multiple Services Configuration Connecting the cables to the RTM IP: The following cables are connected to the RTM IP on the rear panel of the RealPresence Collaboration Server (RMX) 2000: Table 16-33 LAN Connections to the RTM IP RTM IP Port Description LAN 1 – LAN 2 Management LAN 3 Modem Connecting the cables to the RTM LAN: If RTM LAN or RTM ISDN cards are not installed on the RMX, they must be installed before connecting
PAGE 490
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Figure 16-7 shows the cables connected to the RealPresence Collaboration Server (RMX) 2000 rear panel, when two RTM LAN cards are installed providing IP connectivity. In this case, only one IP network Service can be associated with each RTM LAN card.
PAGE 491
Chapter 16-Network Services System Flags and License Settings The MULTIPLE_SERVICES System Flag determines whether the Multiple Services option will be activated once the appropriate license is installed. Possible Values: YES / NO Default: NO This flag must be manually added to the system configuration and set to YES to enable this option. For more information see "Manually Adding and Deleting System Flags” on page 22-18.
PAGE 492
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The New IP Service - Networking IP dialog box opens. 3 Define the following fields: Table 16-36 IP Network Service - IP Parameters Field Description Network Service Name Enter the IP Network Service name. Note: This field is displayed in all IP Signaling dialog boxes and can contain character sets that use Unicode encoding. IP Network Type Select the IP Network environment. You can select: • H.323: For an H.
PAGE 493
Chapter 16-Network Services Table 16-36 IP Network Service - IP Parameters Field Description Media Card 1 Port 1 IP Address If only one network is connected to this media card, it is enough to assign one media card to this Network Service. In such a case, enter one IP address for the media card according to the LAN Port used for the connection. If each of the LAN ports on one media card is used with two different networks, each port is assigned to its own Network Service.
PAGE 494
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 16-36 IP Network Service - IP Parameters 4 Field Description Subnet Mask Enter the subnet mask of the RMX in that network service. Default value: 255.255.255.0. Optional. Some system flags can be defined per Network Service, depending on the network environment. To modify these flags, click the Service Configuration button. The Service Configuration dialog box opens.
PAGE 495
Chapter 16-Network Services — — — — — — — — — — — — — — Polycom, Inc. SIP_FREE_VIDEO_RESOURCES FORCE_CIF_PORT_ALLOCATION MS_ENVIRONMENT SIP_FAST_UPDATE_INTERVAL_ENV SIP_FAST_UPDATE_INTERVAL_EP H263_ANNEX_T H239_FORCE_CAPABILITIES MIX_LINK_ENVIRONMENT IP_LINK_ENVIRONMENT FORCE_STATIC_MB_ENCODING FORCE_RESOLUTION SEND_WIDE_RES_TO_IP DISABLE_WIDE_RES_TO_SIP_DIAL_OUT SEND_SIP_BUSY_UPONRESOURCE_THRESHOLD 5 Click the Routers tab.
PAGE 496
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 8 Modify the following fields: Table 16-37 Default Management Network Service – DNS Field Description Service Host Name Enter the host name of this network Service. Each Network Service must have a unique Host Name otherwise an error message is displayed. DNS Select: • Off – if no DNS server is used in this network. • Specify – to enter the IP address of the DNS server used by this network service.
PAGE 497
Chapter 16-Network Services 13 Click the SIP Servers tab. 14 Define the Primary and Alternate SIP Server for this network Service. • Starting with Version 7.1, Registration of conferencing entities with the SIP Servers was moved to the conferencing entities and is defined in the Conference Profile. • If Microsoft Office Communications or Lync server are part of this network service, a certificate must be created for this network service.
PAGE 498
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide To designate an IP Network Service as the default IP Network Service: 1 In the Device Management pane, click IP Network Services ( ). 2 In the Network Services list pane right-click the IP Network Service to be set as the default, and then click Set As H.323 Default, or Set As SIP Default. The next time you access this menu, a check mark is added next to the network service type to indicate its selection as default.
PAGE 499
Chapter 16-Network Services Conference Profile Registration of conferencing entities such as ongoing conferences, Meeting Rooms, Entry Queues, SIP Factories and Gateway Sessions with SIP servers is done per conferencing entity. This allows better control on the number of entities that register with each SIP server by selecting for each of the conferencing entities whether it will register with the SIP server. The registration is defined in the Conference Profile - Network Services tab.
PAGE 500
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Gateway Profiles To enable the RMX to call the destination endpoint/MCU via IP connection, the Network Service for the call must be selected in the Gateway Profile dialog box. The Network Service set as default is used if no other Network Service is selected. If the same Network Service is used for H.323 and SIP calls, the Network Service Environment must include both H.323 and SIP settings.
PAGE 501
Chapter 16-Network Services Signaling Monitor The Signaling Monitor pane includes the list of the IP Network Services defined in the system (up to two in the RealPresence Collaboration Server (RMX) 1500/RealPresence Collaboration Server (RMX) 2000 and up to four in the RealPresence Collaboration Server (RMX) 4000). Double-clicking a Network Service, displays it properties and status. Conferencing Each conference on the RMX can host participants from the different IP Network networks simultaneously.
PAGE 502
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Reserving Video Resources for a Conference When defining a new ongoing conference or a conference reservation, you can select the Network Service that will be used to reserve the required resources. If no Network Service is selected, the default Network Service is used.
PAGE 503
Chapter 16-Network Services Resource Report The Resource Report displays the resource usage in total and per Network Service in a table format. The Resources per Service table provides the actual information on resource usage and availability per network Service and provides an accurate snapshot of resources usage in the system. You can select the graph to display: select either Totals (default) or the Network Service.
PAGE 504
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide NAT (Network Address Translation) Traversal NAT Traversal is a set of techniques enabling participants behind firewalls to connect to conferences, hosted on the RMX, remotely using the internet. Session Border Controller (SBC) All signaling and media for both SIP and H.323 will be routed through an SBC.
PAGE 505
Chapter 16-Network Services Table 16-40 Remote Connection (Continued) Enterprise Client CMA Client Environment Registered SBC SIP / H.323 No SAM Only  Registered Environment No H.323 Business to Business Connections The following Business to Business connection call flow options are supported: Table 16-41 Business to Business Connection Enterprise A Client Polycom, Inc. Enterprise B Client Environment Registered SBC SBC Registered Environment H.323 Yes RPAD  RPAD Yes H.
PAGE 506
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide FW (Firewall) NAT Keep Alive The RMX can be configured to send a FW NAT keep alive message at specific Intervals for the RTP, UDP and BFCP channels. This is necessary because port mappings in the firewall are kept open only if there is network traffic in both directions. The firewall will only allow UDP packets into the network through ports that have been used to send packets out.
PAGE 507
17 IVR Services IVR Services are supported in AVC Conferencing Mode only. Interactive Voice Response (IVR) is an application that allows participants to communicate with the conferencing system via their endpoint’s 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.
PAGE 508
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 The list pane displays the Conference IVR Services list and the total number of IVR services currently defined in the system.
PAGE 509
Chapter 17-IVR Services Table 17-1 IVR Toolbar buttons Button Button Name Descriptions Add Supported Languages Adds languages to the IVR module, enabling you to download voice prompts and messages for various languages. Replace/Change Music File To replace the currently loaded music file that is used to play background music, the MCU is shipped with a default music file.
PAGE 510
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 The New Language dialog box opens. 5 In the New Language box, enter the name of the new language. The language name can be typed in Unicode and cannot start with a digit. Maximum field length is 31 characters. 6 Click OK. The new language is added to the list of Supported Languages.
PAGE 511
Chapter 17-IVR Services Table 17-2 lists the Message Types for each category: Table 17-2 IVR Message Types by Message Category Polycom, Inc. Message Category Message Type Message Conference Password Request Conference Password Requests the participant to enter the conference password. Request Conference Password Retry A participant who enters an incorrect password is requested to enter it again. Request Digit Requests the participant to enter any digit in order to connect to the conference.
PAGE 512
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 8 Select the appropriate *.wav audio file, and then click the Open button. The name of the selected file is displayed in the Install field in the Install File dialog box. 9 Optional. You can play a .wav file by selecting the Play button ( ). 10 Click Yes to upload the file to the MCU. The system returns to the Add Message File dialog box. 11 Repeat step 6 to 10 for each additional audio file to be uploaded to the MCU.
PAGE 513
Chapter 17-IVR Services 2 Define the following parameters: Table 17-3 Conference IVR Service Properties - Global Parameters Polycom, Inc. Field/Option Description Conference IVR Service Name Enter the name of the Conference IVR Service. The maximum field length is 20 characters and may be typed in Unicode. Language For IVR Select the language of the audio messages and prompts from the list of languages defined in the Supported languages. The default language is English.
PAGE 514
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 3 Click the Welcome tab. The New Conference IVR Service - Welcome dialog box opens. 4 Select the Enable Welcome Messages check box to define the system behavior when the participant enters the Conference IVR queue. When participants access a conference through an Entry Queue, they hear messages included in both the Entry Queue Service and Conference IVR Service.
PAGE 515
Chapter 17-IVR Services 7 Click the Conference Chairperson tab. The New Conference IVR Service - Conference Chairperson dialog box opens. 8 Select the Enable Chairperson Messages check box to enable the chairperson functionality. If this feature is disabled, participants are not able to connect as the chairperson. When both Conference Password and Chairperson Password options are enabled and defined, the system first plays the prompt "Enter conference password".
PAGE 516
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 10 Click the Conference Password tab. The New Conference IVR Service - Conference Password dialog box opens. 11 Select the Enable Password Messages check box to request the conference password before moving the participant from the conference IVR queue to the conference. When both Conference Password and Chairperson Password are enabled and defined, the system first plays the prompt "Enter conference password".
PAGE 517
Chapter 17-IVR Services 14 Click the General tab. The New Conference IVR Service - General dialog box opens. The General dialog box lists messages that are played during the conference. These messages are played when participants or the conference chairperson perform various operations or when a change occurs. 15 To assign the appropriate audio file to the message type, click the appropriate table entry, in the Message File column. A drop-down list is enabled.
PAGE 518
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 17-6 Conference IVR Service Properties - General Voice Messages (Continued) 17-12 Message Type Description Change Password Failure A message played when the participant enters an invalid password, for example when a password is already in use. Change Passwords Menu This voice menu is played when the participants requests to change the conference password. This message details the steps required to complete the procedure.
PAGE 519
Chapter 17-IVR Services Table 17-6 Conference IVR Service Properties - General Voice Messages (Continued) Message Type Description Mute All On Informs all participants that they are muted, with the exception of the conference chairperson. Note: This message is played only when the Mute All Except Me option is activated. No Video Resources Audio Only. Informs the participant of the lack of Video Resources in the RMX and that he/she is being connected as Audio Only.
PAGE 520
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 tones: Entry Tone and Exit tone. When the Tone Notifications option is enabled, no recording of the participant names will occur and the conference chairperson will not be able to ask for a name review during the conference. From version 7.6, the selection of tones in the IVR Service definition replaces the functionality of the system flag IVR_ROLL_CALL_USE_TONES_INSTEAD_OF_VOICE.
PAGE 521
Chapter 17-IVR Services Table 17-7 Conference IVR Service Properties - Roll Call Messages (Continued) Roll Call Message Description Roll Call Joined A voice message stating that the participant has joined the conference. Note: In versions prior to 7.6, when the system flag IVR_ROLL_CALL_USE_TONES_INSTEAD_OF_VOICE is set to YES, the system does not playback the Roll Call names when participants enter the conference. However, the voice message will be played, unless it is replaced with tone file.
PAGE 522
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 b From the list, select the audio file to be assigned to the event/indication. If the Tones option is enabled, you must assign the appropriate audio files to all notification types. The RMX system is shipped with two default tones: Entry_tone.wav and Exit_tone.wav. If required, you can upload customized audio files that will be played when participants join or leave the conference.
PAGE 523
Chapter 17-IVR Services Table 17-8 IVR Slide - Input / Output Formats (Continued) Format Slide Resolution Input Slides Low 4CIF (4:3) or CIF (4:3) Generated Slides 4SIF SIF CIF — The source images for the high resolution slides must be in *.bmp or *.jpg format. — If the uploaded slides are not of the exact SD or HD resolution, an error message is displayed and the slides are automatically cropped or enlarged to the right size.
PAGE 524
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 17-9 New Conference IVR Service Properties - Video Services Parameters (Continued) Video Services Description Invite Participant See "Inviting Participants using DTMF” on page 17-33. Dial out protocols order Select the order of the network protocols that will be used by the system to dial the destination number.
PAGE 525
Chapter 17-IVR Services 26 Click the DTMF Codes tab. The New Conference IVR Service - DTMF Codes dialog box opens. • This dialog box lists the default DTMF codes for the various functions that can be performed during the conference by all participants or by the chairperson. Table 17-10 New Conference IVR Service Properties - DTMF Codes Polycom, Inc.
PAGE 526
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 17-10 New Conference IVR Service Properties - DTMF Codes Operation DTMF String Permission Invite Participant *72 Everyone Disconnect Last Invited Participant #72 Chairperson Change To Chairperson *78 Everyone Increase Listening Volume *76 Everyone Decrease Listening Volume #76 Everyone Override Mute All Configurable Everyone Start Recording *3 Chairperson Stop Recording *2 Chairperson Pause Recording *1 Chairp
PAGE 527
Chapter 17-IVR Services 28 Click the Operator Assistance tab. The Operator Assistance dialog box opens. 29 Select Enable Operator Assistance to enable operator assistance when the participant requires or requests help during the connection process to the conference or during the conference. 30 In the Operator Assistance Indication Message field, select the audio message to be played when the participant requests or is waiting for the operator’s assistance.
PAGE 528
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 The New Entry Queue IVR Service - Global dialog box opens. 3 Fill in the following parameters: Table 17-11 Entry Queue IVR Service Properties - Global Parameters Option Description Entry Queue Service Name (Mandatory) Enter the name of the Entry Queue Service. The name can be typed in Unicode. Maximum field length is 80 ASCII characters. Language Select the language in which the Audio Messages and prompts will be heard.
PAGE 529
Chapter 17-IVR Services 4 Click the Welcome tab. The New Entry Queue IVR Service - Welcome dialog box opens. If the files were not uploaded prior to the definition of the IVR Service or if you want to add new audio files, click Add Message File to upload the appropriate audio file to the RMX. 5 Define the appropriate parameters. This dialog box contains options that are identical to those in the Conference IVR Service - Welcome Message dialog box.
PAGE 530
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 9 — In the Message File column, click the table entry, and then select the appropriate audio message. Click the General tab. The New Entry Queue IVR Service - General dialog box opens. The administrator can enable an audio message that informs the participant of the lack of Video Resources in the RMX and that he/she is being connected as Audio Only. The message states: All video resources are currently in use. Connecting using audio only.
PAGE 531
Chapter 17-IVR Services 11 Click the Video Services tab. The New Entry Queue IVR Service - Video Services dialog box opens. 12 In the Video Welcome Slide list, select the video slide that will be displayed to participants connecting to the Entry Queue. The slide list includes the video slides that were previously uploaded to the MCU memory. 13 To view any slide, click the Preview Slide ( ) button.
PAGE 532
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 16 Select Enable Operator Assistance to enable operator assistance when the participant requires or requests help during the connection process. 17 In the Operator Assistance Indication Message field, select the audio message to be played when the participant requests or is waiting for operator’s assistance.
PAGE 533
Chapter 17-IVR Services Alternatively, in the Conference IVR Services list, right-click the Entry Queue IVR Service and then select Set Default Entry Queue IVR Service. The default Entry Queue IVR Service is displayed in bold, indicating that it is the current default service. Modifying the Conference or Entry Queue IVR Service Properties You can modify the properties of an existing IVR Service, except the service name and language.
PAGE 534
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 2 In the IVR Services list toolbar, click the Replace/Change Music File ( The Install Music File window opens. 3 Click the Browse button to select the audio file (*.wav) to upload. ) button. The Open dialog box opens. 4 Select the appropriate audio *.wav file and then click the Open button. The selected file name is displayed in the Install Music File dialog box. 5 Optional.
PAGE 535
Chapter 17-IVR Services To define the format settings for audio messages: • The format settings for audio messages need to be set only once. The settings will then be applied to any new audio messages recorded. • The utility or facility used to record audio messages must be capable of producing audio files with the formats and attributes as shown in the following procedure, namely, PCM, 16.000kHz, 16Bit, Mono. Windows® XP® Sound Recorder is one of the utilities that can be used.
PAGE 536
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 6 To save this format, click the Save As button. The Save As dialog box opens. 7 Select the location where the format will reside, enter a name and then click OK. The system returns to the Sound Selection dialog box. 8 Click OK. The system returns to the Properties for Sound dialog box. 9 Click OK. The system returns to the Sound–Sound Recorder dialog box. You are now ready to record your voice message.
PAGE 537
Chapter 17-IVR Services The Save As dialog box opens. 7 Verify that the Format reads: PCM 16.000 kHz, 16Bit, Mono. If the format is correct, continue with step 10. If the format is incorrect, click the Change button. The Sound Selection dialog box is displayed. 8 In the Name field, select the name of the format created in step 7 on page 17-30. 9 Click OK. The system returns to the Save As dialog box. 10 In the Save in field, select the directory where the file will be stored.
PAGE 538
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Creating a Welcome Video Slide The video slide is a still picture that can be created in any graphic application. To create a welcome video slide: 1 Using any graphic application, save your image in either *.jpg or *.bmp file format.
PAGE 539
Chapter 17-IVR Services Inviting Participants using DTMF A participant in a video or audio conference can invite another participant to the conference using the touch-tone DTMF numeric keypad on the participant’s endpoint. You can invite a participant using various communication devices, such as a mobile phone, an IP phone, PSTN phones, laptops, or connect to another conference running on another PBX or MCU.
PAGE 540
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 defined in the IVR Services - Global tab, the system will attempt to receive the required input. When all the retries have failed, the call to the invited participant is cancelled. Guidelines • Participants can be invited to CP and VSW conferences. • All network protocols are supported (H.323, SIP, ISDN, and PSTN). It is recommended to select PSTN and not ISDN if PSTN is the only destination protocol.
PAGE 541
Chapter 17-IVR Services The Conference IVR Services - General tab is displayed. 3 In the Message File column of the Invite Participant entry, click the drop-down arrow and select the required voice message. The file Enter_Destination_Number.wav that is shipped with the system can be used for this message. To upload a new file, click the Add Message File. For more details, see "Creating Audio Prompts and Video Slides” on page 17-28. 4 Click the Video Services tab.
PAGE 542
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 5 Define the following parameters: Table 17-13 IVR Services Properties - Video Services Parameters - Invite Participants 6 Video Services Description Dial out protocols order Select the order of the network protocols that will be used by the system to dial the destination number.
PAGE 543
Chapter 17-IVR Services 8 If required, determine who can invite other participants to the conference using DTMF codes by changing the permissions to either Chairperson or Everyone. 9 Click OK. Disabling the Invite Participant Option To disable the Invite Participant option: 1 From the IVR Services - DTMF Codes tab, delete the DTMF digits from the DTMF Code column. 2 Click OK.
PAGE 544
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 17-14 Default IVR Messages (Continued) 17-38 Message Type Message Text File Name First to Join “You are the first person to join the conference.” First to Join.wav Mute All On “All conference participants are now muted.” Mute_All_On.wav Mute All Off “All conference participants are now unmuted.” Mute_All_Off.wav End Time Alert “The conference is about to end.” End_Time_Alert.
PAGE 545
Chapter 17-IVR Services Table 17-14 Default IVR Messages (Continued) Polycom, Inc. Message Type Message Text File Name Participant Help Menu “The available touch-tone keypad actions are as follows: • To exit this menu press any key. Participant_Help_Menu.wav • To request private assistance, press star, zero. • • To mute your line, press star, six. • To increase your volume, press star, nine. • To decrease your volume, press pound, nine. To unmute your line, press pound, six.
PAGE 546
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Volume Control of IVR Messages, Music and Roll Call The volume of IVR music, IVR messages and Roll Call is controlled by the following system flags: • IVR_MUSIC_VOLUME • IVR_MESSAGE_VOLUME • IVR_ROLL_CALL_VOLUME To control the volume of IVR music, messages and Roll Call: >> Modify the values of the System Flags listed in Table 17-15 by clicking the menu Setup > System Configuration.
PAGE 547
18 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 value of the fields that support Unicode values, such as the info fields, will be stored in the CDR file in UTF8. The application that reads the CDR must support Unicode.
PAGE 548
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The following is a sample of an unformatted CDR file: Conference summary record Event code Event records Figure 18-1 Unformatted CDR File • 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 is displayed in a separate line, together with its name.
PAGE 549
Chapter 18-The Call Detail Record (CDR) Utility Multi-Part CDR Files By default, the maximum CDR (Call Data Record) file size is limited to 1MB. When a CDR file reaches a size of 1MB the file is saved and further call data recording is stopped and the additional data is lost. The RMX can be configured to keep recording the data in multiple CDR file set of 1MB each. Multi-Part CDR ensures that conference call data from long duration or permanent conferences is recorded and not lost.
PAGE 550
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Appendix C: "CDR Fields - Unformatted File” on page C-1, contains a full list of the events, fields and values that appear in the unformatted file. This appendix can be referred to for information regarding the contents of fields in the unformatted text file, but does not reflect the exact contents of the formatted text file.
PAGE 551
Chapter 18-The Call Detail Record (CDR) Utility Table 18-1 Conference Record Fields (Continued) Field Description Reserved Start Time The reserved start time of the conference. If the conference started immediately this is the same as the Start Time. Reserved Duration The time the conference was scheduled to last. Discrepancy between the scheduled and the actual duration may indicate that the conference duration was prolonged or shortened. Status The conference status.
PAGE 552
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • Files included in a Multi-Part CDR file sets have the same Display Name. The first file of the set is numbered 1 with each additional CDR file numbered in an ascending numeric sequence. Refreshing the CDR List To refresh the CDR list: • Click the Refresh button, or right-click on any record and then select Refresh. Updated conference CDR records are retrieved from the MCU memory.
PAGE 553
19 Gateway Calls Gateway calls are supported in AVC Conferencing Mode only. The RealPresence Collaboration Server (RMX) can be used as a gateway that provides connectivity across different physical networks and translates multiple protocols for pointto-point rich media communications. The RMX supports the widest range of video and audio algorithms.
PAGE 554
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • Up to 80 gateway calls (same as conferences) may be run on a fully configured MCU. • Gateway Profiles are included in the Backup and Restore Configuration operations. • CDR files are generated for Gateway Sessions in the same way as for conferences. • Cascading. To support cascading, the gateway indicates a lower number than the MCU for master-slave relation (directly or through DMA).
PAGE 555
Chapter 19-Gateway Calls Dialing from H.323 Endpoints Figure 19-1Dialing String and Call Flow from H.323 Endpoint to One, Two or Three Endpoints The calling endpoints can dial to one, two or several endpoints (up to ten) in one dialing string. The dialing string includes the following components: [MCU prefix in GK] - the prefix with which the RMX is registered to the gatekeeper.
PAGE 556
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Dialing from SIP Endpoints Figure 19-2Dialing String and Call Flow from SIP Endpoint to One, Two or Three Endpoints The calling endpoints can dial to one, two or several endpoints (up to ten) in one dialing string. The dialing string includes the following components: [MCU Prefix in SIP Proxy] - The prefix with which the RMX is registered to the SIP Proxy. This component is optional and is not required in most cases.
PAGE 557
Chapter 19-Gateway Calls Optional: [MCU prefix in SIP Proxy][GW Profile ID]*[Destination Number, first participant]*[Destination Number, second participant]**[destination number]......*[Destination Number, tenth participant]@domain name For example, if the GW Profile ID is 2000, the domain name is service.polycom.com, and the destination number is 3456, enter: 2000*3456@service.polycom.com. If using the IP address of the RMX signaling host (for example, 172.22.188.
PAGE 558
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide To enter an IP address as the destination number, replace the periods (.) with asterisks (*) in the format n*n*n*n followed by the # key. For example, if the IP address is 172.22.188.22, enter 172*22*188*22#. Dialing from SIP Endpoints Optional. [MCU prefix in SIP Proxy] - the prefix with which the RMX is registered to the gatekeeper.
PAGE 559
Chapter 19-Gateway Calls When the flag is set to NO (default), if the Gatekeeper is not functioning, the RMX dials to the endpoint using the endpoint’s IP address configured in the IP Address field of the New Participant/Participant Properties - General dialog box. IP Address field If no IP address is defined in the Participant Properties, the call will fail.
PAGE 560
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 19-2 GK_MANDATORY_FOR_CALLS_IN - System Flag (Continued) Flag Value YES Gatekeeper Available YES Results Dial-in call is connected using the Gatekeeper. Enabling or Disabling Direct IP Dialing The direct IP dialing is enabled by default.
PAGE 561
Chapter 19-Gateway Calls If the call is not completed after trying all possible protocols, the system displays the number that was dialed on the calling endpoint’s screen and the reason for not completing the call. For details, see "Connection Indications” on page 19-22. Dialing from ISDN/PSTN Endpoints Figure 19-4Dialing String and Call Flow from ISDN Endpoint to IP Endpoint [GW Profile ISDN/PSTN number] - the dial-in number assigned to the Gateway Profile, including the required country and area codes.
PAGE 562
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Calling an IP Endpoint via Gateway If the call destination is an IP endpoint, the endpoints must be registered to the same gatekeeper to which the RMX is registered.
PAGE 563
Chapter 19-Gateway Calls For more details on Dialing Rules definition in the CMA, see the Polycom CMA System Operations Guide, “Dial Rule Operations”. Gateway Redial or Redialing Gateway Calls Additional Redial options and IVR messages have been included for Gateway Calls to numbers that are wrong, adding functionality to the RMX’s Gateway capabilities when used in conjunction with communication servers (H.323, SIP, ISDN) such as Polycom’s CMA and DMA.
PAGE 564
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 19-3 Call Failure Reasons - H.323, SIP, ISDN (Continued) H.323 SIP ISDN Bad Format Address 404 - Not Found 18 - No User Responding Adaptive Busy 414 - Request-URI Too Long 28 - Invalid Number Format Admission Rejected (ARJ) Reason: Request Denied Item 1: Cannot find location.
PAGE 565
Chapter 19-Gateway Calls Disconnect on Wrong Number In previous versions, if a call failed due to no answer at the destination, the call was disconnected with no notification. When using this version, the user receives the Disconnect on Wrong Number IVR message: “Incorrect Destination Number” followed by Reorder Tone. The call is then disconnected.
PAGE 566
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Defining the IVR Service for Gateway Calls The system is shipped with a default Conference IVR Services for gateway calls named GW IVR Service that enables you to run gateway calls without defining a new Conference IVR Service.
PAGE 567
Chapter 19-Gateway Calls 10 For a gateway IVR Service, select the audio file for the following message types: Table 19-4 Conference IVR Service Properties - Gateway General Voice Messages Message Type Description Enter Destination ID Prompts the calling participant for the destination number. Default message prompts the participant for the conference ID (same message as in the Entry Queue IVR Service).
PAGE 568
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 19-5 New Conference IVR Service Properties - Video Services Parameters (Continued) Video Services Description Video Welcome Slide Select the video slide file to be displayed when participants connect ) to the conference. To view any slide, click the Preview Slide ( button. If the video slide file was not uploaded to the MCU prior to the IVR Service definition, click the Add Slide button.
PAGE 569
Chapter 19-Gateway Calls Defining the Conference Profile for Gateway Calls The Conference Profile that will be later assigned to the Gateway Profile determine the parameters of the gateway call, such as the line rate and video resolution and if to automatically terminate the gateway session when one participant or no participants are connected to the Gateway Session. From Version 7.2, Gathering phase is not supported in gateway calls, even if it is defined in the Profile assigned to the Gateway Profile.
PAGE 570
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Defining the Gateway Profile A Gateway Profile is a conferencing entity, based on the Conference Profile assigned to it, that enables endpoints to dial-in and initiate Gateway Sessions. The system is shipped with a default Gateway Profile, named Default_GW_Session.
PAGE 571
Chapter 19-Gateway Calls 3 Define the following parameters: Table 19-6 New Gateway Profile Properties Option Description Display Name Enter a unique-per-MCU name for the Gateway Profile in native language character sets to be displayed in the RealPresence Collaboration Server Web Client. The system automatically generates an ASCII name for the Display Name field that can be modified using Unicode encoding.
PAGE 572
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 19-6 New Gateway Profile Properties (Continued) 19-20 Option Description IP Network Service Select the IP Network Service to be used with this Gateway. If this is not selected the default IP Network Service will be used. Enable ISDN/PSTN Access Select this check box to allocate dial-in numbers for ISDN/PSTN connections.
PAGE 573
Chapter 19-Gateway Calls Table 19-6 New Gateway Profile Properties (Continued) 4 Option Description Forward Prefix Enter the DMA prefix or the RMX prefix in the Gatekeeper for use in automatic dial string generation. This prefix replaces the digits that are truncated from the dial-in strings and to which the remaining dial in digits are appended to create the destination number. For example, if the DMA Prefix in the Gatekeeper is 26, enter this prefix in this field.
PAGE 574
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Monitoring Ongoing Gateway Sessions Ongoing Gateway Sessions that are created when calling the Gateway Profile, are listed in the ongoing Conferences list pane. Gateway Sessions are monitored in the same way as the conferences. For more details on monitoring conferences, see RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide, "Conference Level Monitoring” on page 13-3.
PAGE 575
Chapter 19-Gateway Calls • Rejected - the far endpoint has rejected the call. In such a case, the system will try to connect using another communication protocol. • Unreached - the number could not be resolved by the gatekeeper or the SIP proxy or could not be found on the network. In such a case, the system will try to connect using another communication protocol. • Failed - any reason causing the system not to complete the connection process.
PAGE 576
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide When dialing to specific IP endpoints you can simplify the dialing process by creating the appropriate Meeting Room. If CMA is involved, dialing can be simplified even further by configuring the appropriate dialing Rule in the CMA.
PAGE 577
Chapter 19-Gateway Calls • ISDN/PSTN access is enabled and a dial-in number is assigned to the Meeting Room. • The dial-out IP endpoint is added to the Meeting Room’s Participants list. Dialing to Polycom® DMA™ 7000 Two dialing methods are available to ISDN/PSTN participants calling the DMA: Polycom, Inc. • Direct with automatically generated destination dial strings from dial-in strings. This option is available only from version 7.1 and only to RMX with MPM+ and MPMx cards. • Via Gateway IVR.
PAGE 578
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide In addition, PSTN participants can dial the Gateway IVR and can use the MCU or DMA prefix in the gatekeeper together with the conference ID/endpoint alias as the destination string to simplify the input. This is one of the methods for PSTN participants to connect to a virtual Meeting Room on the DMA. For more details, see "PSTN Dial-in Using GK Prefix” on page 19-9.
PAGE 579
Chapter 19-Gateway Calls As part of this solution, the RMX acts as a gateway for the DMA that supports H.323 calls. The PSTN or ISDN endpoint dials the virtual Meeting Room on the DMA via the Gateway Profile on the RMX. Both the RMX and the DMA must be registered with the same gatekeeper. The dialing string of the destination conference on the DMA must be communicated to the dialing endpoint and used during the connection to the Gateway Profile on the RMX.
PAGE 580
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Figure 20 Call Flow from ISDN Endpoint to Polycom DMA with Automatically Generated Forwarded Dial String Example: Figure 1 shows the call flow assuming the following parameters: First Dial-in Number 5705550 Last Dial-in Number 5705560 Use Dial-in Numbers as Destination ID Selected PSTN participant dials (212)5705555 Destination Prefix (DMA Gatekeeper) 26 Number of Rightmost Digits to Append 4 DMA Meeting Room
PAGE 581
Chapter 19-Gateway Calls Table 19-7 summarizes the PSTN participant’s DTMF input depending on the flag value. Table 19-7 PSTN Participant input via DTMF FLAG: USE_GK_PREFIX_FOR_PSTN_CALLS= Configuration NO Standalone RMX Conference ID= 1234 PSTN participant enters: 1234#.
PAGE 582
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 19-30 Polycom, Inc.
PAGE 583
20 RMX Manager Application The RMX Manager is the Windows version of the RealPresence Collaboration Server Web Client. It can be used instead of the RealPresence Collaboration Server Web Client for routine RMX management and for RMX management via a modem connection. For more information on using the RMX Manager via a modem connection, see "Connecting to the MCU via Modem” on page G-7.
PAGE 584
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Installing the RMX Manager The RMX Manager application can be downloaded from one of the RealPresence Collaboration Server systems installed in your site or from Polycom web site at http://www.polycom.com/support. Upgrade Notes • When upgrading the RMX Manager application, it is recommended to backup the MCU list using the Export RMX Manager Configuration option.
PAGE 585
Chapter 20-RMX Manager Application The installer verifies the application’s requirements on the workstation. The Install dialog box is displayed. 3 Click Install. The installation proceeds. The installation completes, the application loads and the RMX Manager - MCUs screen is displayed. MCUs Toolbar MCUs Pane The first time you start the RMX Manager application, the MCUs pane is empty. Polycom, Inc.
PAGE 586
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Starting the RMX Manager Application Once installed, the RMX Manager can be run using the http:// (non-secured) or https:// (secured) command in the browser’s address line or the Windows Start menu. To use the browser: 1 In the browser’s command line, enter: http:///RMXManager.html or https:///RMXManager.html 2 Press Enter.
PAGE 587
Chapter 20-RMX Manager Application — Product Type - The MCU type: RealPresence Collaboration Server (RMX) 1500/ RealPresence Collaboration Server (RMX) 2000/RealPresence Collaboration Server (RMX) 4000. Before connecting to the MCU for the first time, the RMX type is unknown so “RMX” is displayed instead as a general indication. To display the RMX Manager main screen you must connect to one of the listed RMXs. For more details, see "Connecting to the MCU” on page 20-5.
PAGE 588
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide If you are connecting to the MCU from the MCUs opening screen and have defined the Username and Password for the connecting MCU, the system connects to the RMX, and the RMX Manager Main Screen is displayed.
PAGE 589
Chapter 20-RMX Manager Application RMX Manager Main Screen The RMX Manager Main Screen is displayed only when at least one MCU is connected. This screen is similar to the RealPresence Collaboration Server Web Client Main Screen with the addition of the MCUs pane. As in the RealPresence Collaboration Server Web Client, the panes are displayed according to the Authorization Level of the logged in User. The MCUs pane is displayed to all users.
PAGE 590
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide For each listed MCU, the system displays the following information: • MCU Display Name - the name of the MCU and its icon according to its type and connection status. The following icons are available: Table 20-1 MCU Icons and Statuses Icon Description RealPresence Collaboration Server (RMX) 1500, disconnected. RealPresence Collaboration Server (RMX) 1500, connected.
PAGE 591
Chapter 20-RMX Manager Application MCUs Toolbar The MCUs toolbar contains the following buttons: Add MCU Connect MCU Export Configuration Disconnect MCU Import Configuration Delete MCU MCU Properties Conferences Pane The Conferences pane lists all the ongoing conferences from all the MCUs that are connected and monitored along with their MCU, Status, Conference ID, Start Time and End Time data. The number of ongoing conferences is displayed in the pane’s title.
PAGE 592
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The RMX Management 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. List Pane The List pane displays details of the participants connected to the conferences selected in the Conferences pane or the item selected in RMX Management pane.
PAGE 593
Chapter 20-RMX Manager Application The Participant Alerts pane is opened and closed by clicking the Participant Alerts button in the left corner of the Status Bar. Port Usage Gauges The Port Usage gauges display for the selected MCU: • The total number of Video or Voice ports in the system according to the Video/Voice Port Configuration. The Audio gauge is displayed only if Audio ports were allocated by the administrator, otherwise only the Video port gauge is displayed.
PAGE 594
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Adding MCUs to the MCUs List The RMX Manager can connect to one or several RMXs simultaneously. If the site’s configuration includes more than one MCU, or when a new MCU is added to your configuration, and you want to monitor and control all MCUs from within the same window, you must add the MCU to the MCUs list.
PAGE 595
Chapter 20-RMX Manager Application Table 21 MCU Properties (Continued) Field Description Password Enter the password as defined for the user name with which you will login to the MCU. The system is shipped with a default User whose password is POLYCOM. Secure Mode Optional. Select this check box to connect to the RMX with SSL and work in Secure Mode.
PAGE 596
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • Dialing in to an Ad Hoc Entry Queue defined on one of the MCUs which is used as the access point to the MCU. For a detailed description of Ad Hoc Entry Queues, see "Entry Queues” on page 7-1. • Start a Reservation: — If the Start Time of the Reservation is past due the conference becomes ongoing immediately.
PAGE 597
Chapter 20-RMX Manager Application If you are the meeting chairperson or organizer using the RealPresence Collaboration Server Web Client to start your own meeting, you need to communicate the default conference ID (or the one you created) to the other conference participants so they can dial in. You can use the New Conference - General dialog box to modify the conference parameters. If no defined participants are to be added to the conference, or you do not want to add additional information, click OK.
PAGE 598
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Starting an Ongoing Conference or Reservation From a Template An ongoing conference or a Reservation can be started from any Conference Template saved in the Conference Templates list of the selected MCU. To start an ongoing conference or a reservation from a Template: 1 In the MCUs pane, select the MCU to run the conference.
PAGE 599
Chapter 20-RMX Manager Application Conferences selected for monitoring MCU Name. can be used for sorting by clicking on the column heading Group by Conference Grouping the Participants by MCU The Participants can be grouped by MCU and then by conferences. To change the display mode for the Participants pane: >> On the RMX Menu, click View > Group by MCU. Polycom, Inc.
PAGE 600
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The Participants pane display changes accordingly. Group by MCU Group by Conference To toggle between the two display modes, click View > Group by MCU. Start Monitoring/Stop Monitoring By default, all conferences running on connected RMXs are monitored.
PAGE 601
Chapter 20-RMX Manager Application To start monitoring again, click the check box in the Monitored column in the MCUs pane, or right-clicking the MCU icon and selecting Start Monitoring. Modifying the MCU Properties You can view the currently defined MCU settings, and modify them when required, for example, change the MCU name, IP address or Secured mode.
PAGE 602
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide b Right-click the MCU icon and then click Disconnect MCU. The MCU icon changes to disconnected and any ongoing conference running on that MCU will not be monitored in this RMX Manager; they are removed from the Conferences pane. This MCU can still be monitored and controlled by other users. Removing an MCU from the MCUs Pane An MCU can be removed from the RMX Manager.
PAGE 603
Chapter 20-RMX Manager Application The Multilingual Settings dialog box opens, displaying the current language selection. 2 Click the check box of the required language. Only one language can be selected. 3 Click OK. 4 Restart the RMX Manager application to implement the language change.
PAGE 604
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 2 Click the Browse button to select the location of the save file, or enter the required path in the Export Path box. The selected file path is displayed in the Export Path box. 3 Click OK to export the RMX Manager configuration.
PAGE 605
Chapter 20-RMX Manager Application Click OK to import the file. 4 Installing RMX Manager for Secure Communication Mode The RMX Manager cannot be downloaded from a site, operating in Secure Communication Mode, without a valid TLS certificate. The following procedure describes how to obtain a TLS certificate and download the RMX Manager from a site operating in Secure Communication Mode.
PAGE 606
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The Security tab is displayed. d 2 Clear the Secured Communication check box. Click the DNS tab. MCU Host Name Local Domain Name 3 Enter the Local Domain Name. The Local Domain Name must be the same as the MCU Host Name. If the content of these two fields are not identical an active alarm is created. 20-24 Polycom, Inc.
PAGE 607
Chapter 20-RMX Manager Application 4 Create a Certificate Request. For more information, see "Purchasing a Certificate” on page F-2. Certificates can also be created and issued using an Internal Certificate Authority. For more information see "Using an Internal Certificate Authority” on page 20-27. 5 Install the certificate. For more information, see Appendix F, "Installing the Certificate” on page F-4. 6 Polycom, Inc.
PAGE 608
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The Management Network Properties dialog box is displayed. c Click on the Security tab. The Security tab is displayed. 20-26 d Select the Secured Communication check box. e Click OK. Polycom, Inc.
PAGE 609
Chapter 20-RMX Manager Application 7 Reset the RMX: a In the RMX Management pane, click the Hardware Monitor button. The Hardware Monitor pane is displayed. b 8 Click the Reset ( ) button. Install the RMX Manager. For more information see "Installing the RMX Manager” on page 20-2. Using an Internal Certificate Authority If your TLS certificate was created and issued by an Internal Certificate Authority, it may not be seen as having been issued by a trusted Certificate Authority.
PAGE 610
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The Certificate Export Wizard is displayed. 5 Click the Next button. The Export File Format dialog box is displayed. 20-28 6 Select Base-64 encoded X.509 (.CER). 7 Click the Next button. Polycom, Inc.
PAGE 611
Chapter 20-RMX Manager Application The File to Export dialog box is displayed. 8 In the File Name field, enter the file name for the exported certificate. 9 Click the Next button. The final Certificate Export Wizard dialog box is displayed. 10 Click the Finish button. The successful export message is displayed. 11 Click the OK button. Polycom, Inc.
PAGE 612
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 20-30 Polycom, Inc.
PAGE 613
21 RealPresence Collaboration Server (RMX) Administration and Utilities System and Participant Alerts The MCU alerts users to any faults or errors the MCU encountered during operation. Two indication bars labeled System Alerts and Participant Alerts signal users of system errors by blinking red in the event of an alert. System Alerts indication bar Participant Alerts indication bar The System Alerts indication bar blinks red prompting the user to view the active alarms.
PAGE 614
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide System Alerts System Alerts are activated when the system encounters errors such as a general or card error. The system errors are recorded by the RMX and can be generated into a report that can be saved in *.txt format. To view the System Alerts list: 1 Click the red blinking System Alerts indication bar. The Active Alarms pane opens. This screen indicates what events have not been resolved.
PAGE 615
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities Table 21-1 Active Alarms Pane Columns (Continued) Field Description 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. For more information about the Active Alarms, see Appendix B: "Alarms and Faults” on page B-1.
PAGE 616
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The Participant Alerts pane opens. The Participant Alerts pane displays similar properties to that of the Participant List pane. For more information, see the RMX 2000/4000 Getting Started Guide, "Participant Level Monitoring” on page 3-45. 2 To resolve participant issues that created the Participant Alerts, the administrator can either Connect , Disconnect or Delete a participant.
PAGE 617
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities Table 21-2 RMX Time – Fields Properties Field Description GMT Date The date at Greenwich, UK. Local Time The MCU’s local time settings, are calculated from the GMT Time and the GMT Offset. GMT Time The MCU’s current GMT Time settings. Select the Up or Down arrows to alter the GMT Time on the MCU. GMT Offset The time zone difference between Greenwich and the RMX’s physical location in hours and minutes.
PAGE 618
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Resource Management Resource Capacity The RealPresence Collaboration Server (RMX) 1500 supports one card type: MPMx. Three assembly variations, MPMx-S, MPMx-D and MPMx-Q, differing in resource capacity, are available for the RealPresence Collaboration Server (RMX) 1500. The RealPresence Collaboration Server (RMX) 2000 can support three card types: MPM, MPM+ and MPMx.
PAGE 619
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities Table 21-4 summarizes the resource capacities of fully configured MCUs with the various card types per line rate in VSW Conferencing mode.
PAGE 620
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide In Fixed Resource Capacity mode, the maximum number of resources is based on the system license and the hardware configuration of the RMX. By default, these resources are allocated as HD720p30 resources, the first time Fixed Resource Capacity mode is activated.
PAGE 621
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities Table 21-5 AVC Video Resource Usage vs. Resolution (MPM, MPM+, MPMx) (Continued) Video Resources Used Resolution/fps MPM MPM+ MPMx WSD/30 4CIF/30 4SIF/30 WVGA/30 WVGA/25 4 2.66 1.5 480X352/30 SD/30 WSD/60 HD720p/30 4 3 CIF/60 SIF/60 WSIF/60 WCIF/60 2.66 1.
PAGE 622
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Video/Voice Port Configuration The Video/Voice Port Configuration enables you to configure the resources per resource type and if in MPM+ or MPMx System Card Configuration Mode, select the Resource Capacity Mode. To enable SVC-based conferencing, use the Flexible Resource Capacity Mode.
PAGE 623
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities Configuring the Video/Voice Resources in MPM Mode • Resource re-configuration should only be performed when no conferences are running on the MCU. • Updating the configuration sequentially requires a 10 seconds wait between updates, to let the system complete the update process. From Version 7.1 MPM media cards are not supported. To allocate Voice resources: 1 In the RMX menu, click Setup > Video/Voice Port Configuration.
PAGE 624
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Flexible Resource Capacity Flexible Resource Capacity is the default resource allocation mode in MPM+ and MPMx Mode and is functionally identical to the MPM Flexible Resource Capacity described above. On the RMX1500 MPMx-Q assembly, the use of HD with Continuous Presence requires an additional license.
PAGE 625
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities The Video/Voice Port Configuration dialog box opens. Number of Resources allocated to each type Maximum Number of Resources from License and Hardware On the RMX1500 MPMx-Q assembly, the use of HD with Continuous Presence requires an additional license. In the Resource Report and Resolution Configuration panes, HD settings are displayed but are not enabled and if HD is selected the system will enable SD by default.
PAGE 626
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide On the slider bars, red areas to the left of the blue slider buttons indicate allocated resources and purple areas to the right of the blue slider buttons indicate unallocated resources in the system.
PAGE 627
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities b • Reconfigure the resource allocation. • Click OK to activate the new resource allocation. Optional. Click the Cancel button to accept the resource allocation. The System Alert remains active. Forcing Video Resource Allocation to CIF Resolution You can set the MCU to allocate one CIF video resource to an endpoint, regardless of the resolution determined by the Conference Profile parameters.
PAGE 628
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 2 In the MCMS_PARAMETERS tab, double-click or select the flag FORCE_CIF_PORT_ALLOCATION and click the Edit Flag button. 3 In the New Value field, clear the value entries. 4 Click OK. Reset the MCU for changes to take effect.
PAGE 629
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities Table 21-6 Resource Report Fields Parameters (Continued) Column Description Occupied The number of MCU resources that are used by connected AVC and SVC-based participants or reserved for defined participants. Free The number of MCU resources available for connecting AVC and SVC-based endpoints.
PAGE 630
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The actual number of occupied or free resources can also be displayed by moving the cursor over the columns of the bar graph. Moving the cursor over the Video bar displays the following: 8 Occupied Video Resources 64 Free Video Resources Port Gauges In Flexible Resource Capacity mode, the Port Gauges in the Status Bar show 0 of the 40 Audio (Voice) resources as occupied and 8 of the 72 Video resources as occupied.
PAGE 631
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities The Resource Report is displayed as follows: Total Number of Audio Resources = 18 Total Number of Video Resources = 47 The actual number of occupied or free resources can also be displayed by moving the cursor over the columns of the bar graph (as explained above for Flexible Resource Capacity).
PAGE 632
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 21-7 lists the ISDN supported bit rates and their respective participant connection capacities per RTM ISDN card: Table 21-7 ISDN – E1/T1 Connection Capacity vs.
PAGE 633
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities — In Flexible Resource Capacity Mode, CMA/DMA receive information about how many Video (CIF) and Audio resources are occupied per conference or MCU according the request type sent by the CMA and DMA. — In Fixed Resource Capacity™ Mode, DMA receives information about the number of occupied resources per resource type (Audio Only, CIF, SD, HD 720p, HD 1080p) and per conference or MCU according the request type sent by the DMA.
PAGE 634
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide SIP Dial-in Busy Notification When the system flag SEND_SIP_BUSY_UPON_RESOURCE_THRESHOLD is set to YES (NO is the default), it enables the RMX to send a busy notification to a SIP audio endpoint or a SIP device when dialing in to the RMX whose audio resource usage exceeded the Port Usage threshold.
PAGE 635
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities Port Usage Gauges The Port Usage Gauges are displayed in the Status Bar at the bottom of the RMX Web Client screen. Status Bar Port Usage Gauges The Port Usage gauges indicate: • The total number of Video or Voice ports in the system according to the Video/Voice Port Configuration. The Audio gauge is displayed only if Audio ports were allocated by the administrator, otherwise only the Video port gauge is displayed.
PAGE 636
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Video Ports Gauge • In Flexible Capacity Mode: All video resource usage is converted to the equivalent CIF resource usage. The fraction displayed indicates the exact number of video resources in use out of the total number of video resources in the system. • In Fixed Capacity Mode: All video ports are treated as a single group of Video resources regardless of their differing consumption of CIF video resources.
PAGE 637
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities The System Information properties box displays the following information: Table 21-8 System Information Field Description Total Number of CP Resources Displays the number of video participants licensed for the system. Each CP resource represents one CIF video resource. Each SVC resource is equivalent to one CIF video resource.
PAGE 638
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 21-8 System Information (Continued) Field Description Card Configuration Mode Indicates the MCU configuration as derived from the installed media cards: • MPM: Only MPM cards are supported. MPM+ and MPMx cards in the system are disabled. It is the mode used in previous RMX versions. From Version 7.1, MPM media cards are not supported. • MPM+: Only MPM+ cards are supported.
PAGE 639
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities SNMP (Simple Network Management Protocol) SNMP enables managing and monitoring of the MCU status by external managing systems, such as HP OpenView or through web applications. The RMX’s implementation of SNMPv3 is FIPS 140 compliant. MIBs (Management Information Base) MIBs are a collection of definitions, which define the properties of the managed object within the device to be managed.
PAGE 640
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 21-9 Supported MIB-II Sections (Continued) Section Object Identifier interfaces mib-2 2 ip mib-2 4 The Alarm-MIB MIB used to send alarms. When a trap is sent, the Alarm-MIB is used to send it. H.341-MIB (H.341 – H.323) • Gives the address of the gatekeeper. • Supports H.341-MIB of SNMP events of H.323. Standard MIBs This section describes the MIBs that are included with the RMX.
PAGE 641
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities MIB Name Description MIB-II/RFC1213-MIB (RFC1213.MIB) Holds basic network information and statistics about the following protocols: TCP, UDP, IP, ICMP and SNMP. In addition, it holds a table of interfaces that the Agent has. MIB-II also contains basic identification information for the system, such as, Product Name, Description, Location and Contact Person. ENTITY-MIB (ENTITY.
PAGE 642
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 21-30 Table 22 Unified MIB SNMP Fields (Continued) Name Type Description ServiceISDN Integer Indicates the status of SIP capabilities: 1 - The service is enabled and operational. 2 - The service is enabled but is not operational. 3 - The service is disabled. RsrcAllocMode Fixed/ Flexible The resource allocation method which determines how the system resources are allocated to the connecting endpoints.
PAGE 643
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities Traps Three types of traps are sent as follows: 1 ColdStart trap. This is a standard trap which is sent when the MCU is reset. coldStart notification received from: 172.22.189.154 at 5/20/ 2007 7:03:12 PM Time stamp: 0 days 00h:00m:00s.00th Agent address: 172.22.189.154 Port: 32774 Transport: IP/UDP Protocol: SNMPv2c Notification Manager address: 172.22.172.
PAGE 644
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 3 Alarm Fault trap. The third trap type is a family of traps defined in the POLYCOMRMX-MIB file, these traps are associated with the RMX active alarm and clearance (proprietary SNMP trap). rmxFailedConfigUserListInLinuxAlarmFault notification received from: 172.22.189.154 at 5/20/2007 7:04:22 PM Time stamp: 0 days 00h:01m:11s.71th Agent address: 172.22.189.
PAGE 645
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities The RMX-SNMP Properties - Agent dialog box is displayed. This dialog box is used to define the basic information for this MCU that will be used by the SNMP system to identify it. 2 In the Agent dialog box, click the SNMP Enabled check box. 3 Click the Retrieve MIB Files button to obtain a file that lists the MIBs that define the properties of the object being managed. The Retrieve MIB Files dialog box is displayed.
PAGE 646
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 9 Click the Traps tab. The RMX-SNMP Properties – Traps dialog box opens. Version 3 Versions 1 & 2 Traps are messages sent by the MCU to the SNMP Managers when events such as MCU Startup or Shutdown occur. Traps may be sent to several SNMP Managers whose IP addresses are specified in the Trap Destinations box.
PAGE 647
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities Table 21-2 SNMPv3 - Traps (Continued) Field Trap Destination Description This box lists the currently defined IP addresses of the Manager terminals to which the message (trap) is sent. IP Enter the IP address of the SNMP trap recipient.
PAGE 648
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The RMX-SNMP Properties – Security dialog box opens. Version 3 Versions 1 & 2 This dialog box is used to define whether the query sent to the MCU is sent from an authorized source. When the “Accept SNMP packets from all Hosts” is disabled, a valid query must contain the appropriate community string and must be sent from one of the Manager terminals whose IP address is listed in this dialog box. 21-36 Polycom, Inc.
PAGE 649
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities 14 Define the following parameters: Table 21-3 SNMP - Security Field Polycom, Inc. Description Send Authentication Trap Select this check box to send a message to the SNMP Manager when an unauthorized query is sent to the MCU. When cleared, no indication will be sent to the SNMP Manager.
PAGE 650
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 15 To specifically define one or more valid terminals, ensure that the Accept SNMP Packets from any Host option is cleared and then click the Add button. The Accepted Host IP Address dialog box opens. 16 Enter the IP Address of the Manager terminal from which valid queries may be sent to the MCU, and then click OK. Click the Add button to define additional IP Addresses.
PAGE 651
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities • Gateway Profiles • IVR services (excluding .wav files) • Recording Link • Profiles • IP Network Settings: — — — — — H.323 settings SIP settings DNS settings Fix Ports (TCP, UDP) settings QoS settings Guidelines Polycom, Inc. • Both Master and Slave MCUs must have the same software version installed. • The Users list and Passwords must be the same on both the Master and Slave MCUs.
PAGE 652
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Enabling Hot Backup To enable Hot Backup: 1 On the RMX menu, click Setup > Hot Backup. The RMX Hot Backup dialog box is displayed. 2 Complete or modify the following fields: Table 21-4 Hot Backup Field Description Hot Backup Enabled Select this check box to enable Hot Backup. MCU Role: This setting determines the role of the MCU in the Hot Backup configuration.
PAGE 653
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities Guidelines • Hot Backup triggers should be configured on both the Master and Slave MCUs. • Hot Backup triggers are not synchronized between the Master and Slave MCUs. Configuring the Hot Backup Triggers The Hot Backup triggers are configured in the Hot Backup dialog box for the Master MCU when the Hot Backup feature is enabled.
PAGE 654
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 2 Select the appropriate Hot Backup Triggers check boxes: Table 21-5 Hot Backup Triggers 3 Hot Backup Trigger Description Lost connection with management port Initiates the Hot Backup switch from the Master to the Slave MCU when the connection to the management port is lost on the Master MCU. This trigger is always set.
PAGE 655
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities Audible Alarms In addition to the visual cues used to detect events occurring on the RMX, an audible alarm can be activated and played when participants request Operator Assistance. Using Audible Alarms The Audible Alarm functionality for Operator Assistance requests is enabled for each MCU in either the RMX Web Client or RMX Manager.
PAGE 656
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Configuring the Audible Alarms User Customization The operators and administrators can: • Enable/Disable the Audible Alarm. • Select whether to repeat the Audible Alarm. • Define the number of repetitions and the interval between the repetitions. To Customize the Audio Alert on the RMX Client or RMX Manager: 1 On the RMX menu, click Setup > Audible Alarms > User Customization. The User Customization window opens.
PAGE 657
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities Replacing the Audible Alarm File Each RMX is shipped with a default tone file in *.wav format that plays a specific tone when participants request Operator Assistance. This file can be replaced by a *.wav file with your own recording. The file must be in *.wav format and its length cannot exceed one hour. Only the User with Administrator permission can download the Audible Alarm file.
PAGE 658
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Multilingual Setting Each supported language is represented by a country flag in the Welcome Screen and can be selected as the language for the RMX Web Client. Customizing the Multilingual Setting The languages available for selection in the Login screen of the RMX Web Client can be modified using the Multilingual Setting option.
PAGE 659
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities The Banner Configuration dialog box allows the administrator to select a Login Banner from a drop-down menu. Login Banner Menu One of the the following Login Banners can be selected: • Non-Modifiable Banners • — Sample 1 — Sample 2 — Sample 3 — Sample 4 Modifiable Banner — Custom (Default) Guidelines • The Login Banner cannot be disabled when the RMX is in Ultra Secure Mode.
PAGE 660
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide − Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG authorized purpose. − This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.
PAGE 661
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities Customizing Banners The Login and Main Screen banners can be customized to display conference information, assistance information or warning text as required in the Ultra Secure Mode. To customize the banners: 1 In the RMX menu, click Setup > Customize Display Settings > Banners Configuration. The Banners Configuration dialog box opens.
PAGE 662
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Banner Display Login Screen Banner The Login screen banner can display any text, for example the terms and conditions for system usage (default text) that is required in the Ultra Secure Mode.
PAGE 663
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities Main Screen Banner The Main Screen banner is displayed at the bottom of the screen, as follows: Banner When the RMX is configured to work in Ultra Secure Mode, such as the Maximum Security environment, the display banner includes the following default text: THIS IS A DOD SYSTEM AND IS SUBJECT TO MONITORING, UNAUTHORIZED USE MAY SUBJECT YOU TO ADMINISTRATIVE ACTION OR CRIMINAL PROSECUTION AND PENALTIES.
PAGE 664
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide — — — — — — — — — — — — • Profiles Reservations System Flags Resource Allocation IVR messages, music RMX Web Client user setting - fonts, windows RMX Web Client global settings – notes, address book, language Private keys and certificates (TLS) Conference participant settings Operation DB (administrator list) SNMP settings Time configuration CDR files are not included in the backup process and should be backed up manuall
PAGE 665
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities Ping RMX The Ping administration tool enables the RMX Signaling Host to test network connectivity by Pinging IP addresses. Guidelines • The IP addressing mode can be either IPv4 or IPv6. • Both explicit IP addresses and Host Names are supported. • The RMX Web Client blocks any attempt to issue another Ping command before the current Ping command has completed.
PAGE 666
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Notification 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 alarm’s list. A welcome message is displayed to the RMX user upon connection.
PAGE 667
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities Table 21-10 Notification Settings Parameters (Continued) Field Description Welcome Message A welcome message after user/administrator logon. Active Alarms Update Updates you of any new alarm that occurred. Fault List Updated Updates you when the faults list is updated (new faults are added or existing faults are removed). 2 Enable/Disable All Notifications or Custom to select specific notifications to display.
PAGE 668
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The following tasks can be performed: Table 21-11 Diagnostic File Button Options Button Description Refresh List Refreshes the list and adds newly generated logger files. Select All Selects all the logger files listed. Browse Selects the destination folder for download. Retrieve Files Saves files to the destination folder.
PAGE 669
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities 4 Click the Retrieve Files button. The log files (in *.txt format) are saved to the defined directory and a confirmation caption box is displayed indicating a successful retrieval of the log files. Viewing the Logger Files: To analyze the log files generated by the system, open the retrieved *.txt files in any text editor application, i.e. Notepad, Textpad or MS Word.
PAGE 670
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The data collected is saved into a single compressed file containing all the information from each system component in its relative format (.txt, .xml, etc...). In case the disk is malfunctioning, the file will be written to the RAM (involves only a small amount of information where the RAM size is 1/2 a gigabyte). The zipped file (info.tgz) can be opened with the following applications: WinRAR and WinZip.
PAGE 671
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities Step 1: Creating the Information Collector Compressed File To create the compressed file: 1 In the RMX menu, click Administration > Tools > Information Collector. The Information Collector dialog box is displayed. Standard Security Mode Ultra Secure Mode 2 In the From Date and Until Date fields, use the arrow keys to define the date range of the data files to be included in the compressed file.
PAGE 672
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Step 2: Saving the Compressed File 1 The compressed file is automatically saved in the directory selected in the Information Collector dialog box. The file is named info.tgz. A success information box is displayed. 2 Click the OK button. Step 3: Viewing the Compressed File The compressed file is saved in .tgz format and can be viewed with any utility that can open files of that format, for example WinRAR® 3.80.
PAGE 673
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities Auditor Files Auditor Event History File Storage All audit events are saved to a buffer file on hard disk in real time and then written to a file on hard disk in XML in an uncompressed format.
PAGE 674
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Size (Bytes) First Message – date and time of the first audit event in the file Last Message – date and time of the last audit event in the file StartUp: • True – file was created when the system was started • False – file was created when previous audit event file reached a size of 2 MB or was more than 24 hours old — File Retrieved: • True - file was previously retrieved. • False - file was never previously retrieved.
PAGE 675
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities If you previously double clicked an Auditor Event File in the Auditor Files list, that file is automatically opened. Local File Event List (ID) Request Transaction Tree Response Transaction Tree The following fields are displayed for each event: Table 21-12 Auditor Event Columns Field Description Event ID The sequence number of the event generated by the RMX.
PAGE 676
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 21-12 Auditor Event Columns (Continued) Field Description Event Type Auditor events can be triggered by: • API • • Event RMX Internal Event The process, action, request or transaction that was performed or rejected.
PAGE 677
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities Audit Events Alerts and Faults Table 1 lists Alerts and Faults that are recorded by the Auditor. Table 21-13 Alerts and Faults Event Attempt to exceed the maximum number of management session per user Attempt to exceed the maximum number of management sessions per system Central Signaling indicating Recovery status. Failed login attempt Failed to open Apache server configuration file.
PAGE 678
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 21-13 Alerts and Faults (Continued) Event Restoring Factory Defaults. Secured SIP communication failed. Session disconnected without logout SSH is enabled. System Configuration modified. System is starting. System Resets. TCP disconnection Terminal initiated MCU reset. The Log file system is disabled. The software contains patch(es). USB key used to change system configuration.
PAGE 679
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities Table 21-14 Transactions (Continued) Transaction TRANS_ISDN_SERVICE:SET_DEFAULT_ISDN_SERVICE TRANS_ISDN_SERVICE:UPDATE_ISDN_SERVICE TRANS_MCU:BEGIN_RECEIVING_VERSION TRANS_MCU:COLLECT_INFO TRANS_MCU:CREATE_DIRECTORY TRANS_MCU:FINISHED_TRANSFER_VERSION TRANS_MCU:LOGIN TRANS_MCU:LOGOUT TRANS_MCU:REMOVE_DIRECTORY TRANS_MCU:REMOVE_DIRECTORY_CONTENT TRANS_MCU:RENAME TRANS_MCU:RESET TRANS_MCU:SET_PORT_CONFIGURATION TRANS_MCU:SET_REST
PAGE 680
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide ActiveX Bypass At sites that, for security reasons, do not permit Microsoft® ActiveX® to be installed, the MSI (Windows Installer File) utility can be used to install .NET Framework and .NET Security Settings components on workstations throughout the network. All workstation that connect to RMX systems must have both.NET Framework and .NET Security Settings running locally.
PAGE 681
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities Resetting the RMX System Reset saves system configuration changes and restarts the system with the latest settings. To reset the RMX: 1 In the RMX Management pane, click the Hardware Monitor button. The Hardware Monitor pane is displayed. 2 Click the Reset ( ) button. When the RMX system is reset, during RMX startup the Progress Bar appears at the bottom of the RMX Status pane.
PAGE 682
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Restore Factory Defaults You can erase the current RMX configuration and restore default factory settings. There are two Restore levels: • Standard Restore • Comprehensive Restore This tool is intended for Administrator users, to be performed prior to RMA.
PAGE 683
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities • USB key This method is used when the user cannot login with Administrator or Support system permissions. To Restore Factory Default Settings using Administration Tools in the RMX menu: 1 In the RMX menu, click Administration > Tools > Restore Factory Defaults. The Restore Factory Defaults dialog box appears. 2 Select Standard Restore or Comprehensive Restore.
PAGE 684
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The Backup Configuration Dialog box opens. a Click Browse to select the Backup Directory Path and select Backup. The system initiates the backup of RMX configuration files. b Optional. To exit click Close. 5 When the backup completes, a confirmation dialog box is displayed. 6 Click Yes to restore the RMX. An Active Alarm is activated. 7 Click Yes, to reset the RMX.
PAGE 685
Chapter 21-RealPresence Collaboration Server (RMX) Administration and Utilities To Restore Factory Default Settings using the USB key: Restoring to factory defaults using the USB key method always results in a Comprehensive Restore. Obtain the RestoreToFactoryDefault.txt file from you next level of support and add it to the USB key. Polycom, Inc. 1 Insert the USB key in the workstation. 2 Check that the lan.cfg file on the USB key contains the correct settings for the Management Network Service.
PAGE 686
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 21-74 Polycom, Inc.
PAGE 687
22 System Configuration Flags The system’s overall behavior can be configured by modifying the default values of the System Flags. For flag changes (including deletion) to take effect, the MCU must be reset. For more information, see "Resetting the RMX” on page 21-69. The following System Flags do not require an MCU reset: • IVR_MESSAGE_VOLUME • • IVR_MUSIC_VOLUME IVR_ROLL_CALL_VOLUME Modifying System Flags To modify system flags: 1 On the RMX menu, click Setup > System Configuration.
PAGE 688
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 2 In the MCMS_PARAMETERS tab, the following flags can be modified: Table 22-1 System Flags – MCMS_PARAMETERS Flag Description ALLOW_NON_ENCRYPT_P ARTY_IN_ENCRYPT_CONF If YES, allows non-encrypted participants to connect to encrypted conferences. Default: No Note: From Version 7.6.1, this flag is replaced by the Encryption option “Encrypt when Possible” in the conference Profile - Advanced dialog box. Flag setting is ignored.
PAGE 689
Chapter 22-System Configuration Flags Table 22-1 System Flags – MCMS_PARAMETERS (Continued) Polycom, Inc. Flag Description CONTENT_SLAVE_LINKS_I NTRA_SUPPRESSION_IN_S ECONDS Defines the interval, in seconds, during which the RMX is allowed to forward an Intra Request received from any of the Slave Cascading Links. The Slave Cascading Link can be connected to the local RMX, to an MCU on a higher cascade level or to the Content sharer.
PAGE 690
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-1 System Flags – MCMS_PARAMETERS (Continued) 22-4 Flag Description ENABLE_AGC Set this flag to YES to enable the AGC option. (Default setting is NO.) When disabled, selecting the AGC option in the Participant Properties has not effect on the participant audio. For more information see "Managing the Address Book” on page 8-7.
PAGE 691
Chapter 22-System Configuration Flags Table 22-1 System Flags – MCMS_PARAMETERS (Continued) Flag Description FORCE_CIF_PORT_ALLOC ATION Sets the MCU to allocate one CIF video resource to an endpoint, regardless of the resolution determined by the Conference Profile parameters. You can specify the endpoint types for which resource allocation can be forced to CIF resource, enabling other types of endpoints to use higher resolutions in the same conference.
PAGE 692
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-1 System Flags – MCMS_PARAMETERS (Continued) 22-6 Flag Description HIDE_SITE_NAMES From version 7.6.1, in MPMx Card Configuration Mode, this flag has been replaced by the Enable Site Names option in the Conference Profile - Site Names dialog box. It allows you to enable or disable the display of site names in conferences per conference. From Version 7.
PAGE 693
Chapter 22-System Configuration Flags Table 22-1 System Flags – MCMS_PARAMETERS (Continued) Flag Description ISDN_RESOURCE_POLICY The flag value determines how the ISDN B-channels within configured spans are allocated. The robustness of the ISDN network can be improved by allocating channels evenly (load balancing) among the spans, minimizing the effect of channel loss resulting from the malfunction of a single span.
PAGE 694
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-1 System Flags – MCMS_PARAMETERS (Continued) Flag Description ITP_CROPPING If the conference is set to TelePresence mode, cropping of the image is done according to this flag value: • ITP (default) - Cropping is done as follows: • • • • Left/right sides: no cropping Top/Bottom: the calculated area to be stripped will be split and cropped equally from the top and the bottom of the display area.
PAGE 695
Chapter 22-System Configuration Flags Table 22-1 System Flags – MCMS_PARAMETERS (Continued) Flag Description IVR_MESSAGE_VOLUME The volume of IVR messages varies according to the value of this flag. Possible value range: 0-10 (Default: 6). 0 – disables playing the IVR messages 1 – lowest volume 10 – highest volume Notes: • It is not recommended to disable IVR messages by setting the flag value to 0.
PAGE 696
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-1 System Flags – MCMS_PARAMETERS (Continued) Flag Description LAST_LOGIN_ATTEMPTS If YES, the system displays a record of the last Login of the user. Default: NO. For more details, see "User Login Record” on page 15-13. LEGACY_EP_CONTENT_DE FAULT_LAYOUT Defines the video layout to be displayed on the screen of the legacy endpoints when switching to Content mode. Default value: CP_LAYOUT_1P7 (1+7).
PAGE 697
Chapter 22-System Configuration Flags Table 22-1 System Flags – MCMS_PARAMETERS (Continued) Polycom, Inc. Flag Description MAX_NUMBER_OF_MANAG EMENT_SESSIONS_PER_S YSTEM Defines the maximum number of concurrent management sessions (http and https connections) per system. Value: 4 - 80 Default: 80 MAX_NUMBER_OF_MANAG EMENT_SESSIONS_PER_U SER Defines the maximum number of concurrent management sessions (http and https connections) per user.
PAGE 698
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-1 System Flags – MCMS_PARAMETERS (Continued) 22-12 Flag Description MIN_TIP_COMPATIBILITY_L INE_RATE This flag determines the minimum line rate at which conferencing entities such as an Entry Queue or Meeting Room can be TIP-enabled and TIP-enabled endpoints can connect to them.
PAGE 699
Chapter 22-System Configuration Flags Table 22-1 System Flags – MCMS_PARAMETERS (Continued) Flag Description NUMERIC_CHAIR_PASS_D EFAULT_LEN This flag enables or disables the automatic generation of chairperson passwords and determines the number of digits in the chairperson passwords assigned by the MCU. Possible values are: • 0 disables the automatic password generation in both Standard Security Mode or Ultra Secure Mode.
PAGE 700
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-1 System Flags – MCMS_PARAMETERS (Continued) Flag Description NUMERIC_CONF_PASS_DE FAULT_LEN This flag enables or disables the automatic generation of conference passwords and determines the number of digits in the conference passwords assigned by the MCU. Possible values are: • 0 disables the automatic password generation in both Standard Security Mode or Ultra Secure Mode.
PAGE 701
Chapter 22-System Configuration Flags Table 22-1 System Flags – MCMS_PARAMETERS (Continued) Polycom, Inc. Flag Description PASSWORD_EXPIRATION_ DAYS_MACHINE Enables the administrator to change the password expiration period of Application-user’s independently of regular users. Default: 365 (days). PASSWORD_EXPIRATION _WARNING_DAYS Determines the display of a warning to the user of the number of days until password expiration. Value: between 0 and 14 days.
PAGE 702
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-1 System Flags – MCMS_PARAMETERS (Continued) Flag Description SESSION_TIMEOUT_IN_MI NUTES If there is no input from the user or if the connection is idle for longer than the number of minutes specified by this flag, the connection to the RMX is terminated. Value: 0-99 0 - Session Timeout is disabled, however this feature cannot be disabled when the RMX is in Ultra Secure Mode.
PAGE 703
Chapter 22-System Configuration Flags Table 22-1 System Flags – MCMS_PARAMETERS (Continued) Flag Description SYSTEM_LISTENING_VOLU ME This value is used when the system flag FORCE_SYSTEM_LISTENING_VOLUME is set to YES. Determines the default audio level with which the participants connects and receives audio from the conference. The volume scale is from 1 to 10, where 1 is the weakest and 10 is the strongest. The default value is 5. Each unit change represents an increase or decrease of 3 dB (decibel).
PAGE 704
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-1 System Flags – MCMS_PARAMETERS (Continued) Flag Description USER_LOCKOUT_DURATIO N_IN_MINUTES Defines the duration of the Lockout of the user. Value: 0 - 480 0 means permanent User Lockout until the administrator reenables the user within the system. Default: 0 USER_LOCKOUT_WINDOW _IN_MINUTES Defines the time period during which the three consecutive Login failures occur.
PAGE 705
Chapter 22-System Configuration Flags The following flags can be manually added to the MCMS_PARAMETERS tab: Table 22-2 Manually Added System Flags – MCMS_PARAMETERS Flag Description ACCEPT_VOIP_DTMF_TYP E Defines the type of DTMF tones (inband) or digits (outband) that the RMX will accept in VOIP calls. Range: • 0 - Auto (default): Inband or outband DTMF tones/digits are accepted depending on the endpoint's current setting.
PAGE 706
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-2 Manually Added System Flags – MCMS_PARAMETERS (Continued) Flag Description BONDING_DIALING_METH OD • (ISDN) When set to: SEQUENTIAL The MCU initiates channel connections sequentially until it reaches the number of channels defined by the BONDING_NUM_CHANNELS_IN _GROUP flag. When a channel is connected, dialing begins for the next channel in the group.
PAGE 707
Chapter 22-System Configuration Flags Table 22-2 Manually Added System Flags – MCMS_PARAMETERS (Continued) Flag Description CELL_IND_LOCATION Change the location of the display of Network Quality Indicators displayed in the cells of the conference Video Layout. Default: TOP_RIGHT Range: • BOTTOM_LEFT • • • Polycom, Inc. BOTTOM_RIGHT TOP_LEFT TOP_RIGHT CFG_KEY_ENABLE_FLOW_ CONTROL_REINVITE Used to enable or disable sending a re-INVITE to endpoints to adjust their data rate.
PAGE 708
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-2 Manually Added System Flags – MCMS_PARAMETERS (Continued) Flag Description CPU_BONDING_MODE Sets the Bonding Mode of the Signalling and Management network interface controllers. Mode=6, balance-alb, (Adaptive Load Balancing) includes balance-tlb, (Transmit Load Balancing) and balance-rlb (Receive Load Balancing) for IPV4 traffic. No special switch support is required. Receive Load Balancing is achieved by ARP negotiation.
PAGE 709
Chapter 22-System Configuration Flags Table 22-2 Manually Added System Flags – MCMS_PARAMETERS (Continued) Polycom, Inc. Flag Description DISABLE_WIDE_RES_TO_S IP_DIAL_OUT When set to NO (default), the RMX sends wide screen resolution to dial-out SIP endpoints. Endpoint types that do not support wide screen resolutions are automatically identified by the RMX according to their product type and version and will not receive the wide resolution even if the flag is set to YES.
PAGE 710
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-2 Manually Added System Flags – MCMS_PARAMETERS (Continued) 22-24 Flag Description ENABLE_H239 When set to YES, Content is sent via a separate Content channel. Endpoints that do not support H.239 Content sharing will not be able to receive When set to NO, the Content channel is closed. In such a case, H.239 Content is sent via the video channel (“people” video) enabling endpoints that do not support H.
PAGE 711
Chapter 22-System Configuration Flags Table 22-2 Manually Added System Flags – MCMS_PARAMETERS (Continued) Polycom, Inc. Flag Description ENABLE_SIRENLPR_SIP_E NCRYPTION Enables the SirenLPR audio algorithm when using encryption with the SIP protocol. Range: YES / NO Default: NO ENABLE_TC_PACKAGE Enables or disables Network Traffic Control. Range: YES / NO Default: NO ENABLE_TEXTUAL_CONFE RENCE_STATUS Set the value of this flag to NO to disable Text Indication.
PAGE 712
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-2 Manually Added System Flags – MCMS_PARAMETERS (Continued) Flag Description EXTERNAL_DB_PASSWOR D The password associated with the user name defined for the RMX on the external database server. Default: POLYCOM EXTERNAL_DB_PORT The external database server port used by the RMX to send and receive XML requests/responses. For secure communications set the value to 443. Default: 5005.
PAGE 713
Chapter 22-System Configuration Flags Table 22-2 Manually Added System Flags – MCMS_PARAMETERS (Continued) Polycom, Inc. Flag Description FORCE_G711A Setting this flag forces the use of the G711A Audio Codec. Possible values: YES / NO Default: NO FORCE_RESOLUTION Use this flag to specify IP (H.323 and SIP) endpoint types that cannot receive wide screen resolution and that were not automatically identified as such by the RMX. Possible values are endpoint types, each type followed by a semicolon.
PAGE 714
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-2 Manually Added System Flags – MCMS_PARAMETERS (Continued) 22-28 Flag Description H264_BASE_PROFILE_MIN _RATE_HD720P30_SHARP NESS Not supported from Version 7.0.2. Prior to Version 7.0.2, this flag set the minimum bitrate threshold for endpoints that did not support H.264 High Profile for HD720P30 resolution using Sharpness Video Quality.
PAGE 715
Chapter 22-System Configuration Flags Table 22-2 Manually Added System Flags – MCMS_PARAMETERS (Continued) Flag Description HIDE_CONFERENCE_PASS WORD • If set to YES (default in Ultra Secure Mode): Conference and Chairperson Passwords that are displayed in the RMX Web Client or RMX Manager are hidden when viewing the properties of the conference.
PAGE 716
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-2 Manually Added System Flags – MCMS_PARAMETERS (Continued) 22-30 Flag Description MAX_TRACE_LEVEL This flag indicates the debugging level for RMX support. The flag’s values have been modified for version 7.8 and is not backward compatible with previous versions. Possible values: From version 7.8 - TRACE = t, DEBUG = d, INFO_NORMAL = n, INFO_HIGH = i, WARN = w, ERROR = e, FATAL = f, OFF = o. From version 7.
PAGE 717
Chapter 22-System Configuration Flags Table 22-2 Manually Added System Flags – MCMS_PARAMETERS (Continued) Polycom, Inc. Flag Description MS_CAC_AUDIO_MIN_BR The minimum bit rate for audio using the Microsoft CAC (Call Admission Control) protocol. When the bit rate is lower than the MS_CAC_AUDIO_MIN_BR, the call is not connected. Range: 0 - 384 Default: 30 MS_CAC_VTDEO_MIN_BR The minimum bit rate for video using the Microsoft CAC (Call Admission Control) protocol.
PAGE 718
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-2 Manually Added System Flags – MCMS_PARAMETERS (Continued) 22-32 Flag Description PARTY_GATHERING_DURA TION_SECONDS The value of this System Flag sets the duration, in seconds, of the display of the Gathering slide for participants that connect to the conference after the conference start time. Range: 0 - 3600 Default: 15 For more information see "Video Preview” on page 4-26.
PAGE 719
Chapter 22-System Configuration Flags Table 22-2 Manually Added System Flags – MCMS_PARAMETERS (Continued) Flag Description REMOVE_H323_EPC_CAP_ TO_NON_POLYCOM_VEND OR Used to disable EPC protocol. Use of Polycom’s proprietary protocol, High Profile, EPC, may result in interoperability issues when used with other vendors’ endpoints. Possible values: YES / NO Default: NO REMOVE_H323_HIGH_PRO FILE_CAP_TO_NON_POLY COM_VENDOR Used to disable High Profile protocol.
PAGE 720
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-2 Manually Added System Flags – MCMS_PARAMETERS (Continued) Flag Description SELF_IND_LOCATION Change the location of the display of the Network Quality Indicator of the participant’s own endpoint.
PAGE 721
Chapter 22-System Configuration Flags Table 22-2 Manually Added System Flags – MCMS_PARAMETERS (Continued) Flag Description SEND_WIDE_RES_TO_ISD N When set to YES, the RMX sends wide screen resolution to ISDN endpoints. When set to NO (default), the RMX does not send wide screen resolution to ISDN endpoints. Default: NO.
PAGE 722
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-2 Manually Added System Flags – MCMS_PARAMETERS (Continued) 22-36 Flag Description SET_DTMF_SOURCE_DIFF _IN_SEC If the ACCEPT_VOIP_DTMF_TYPE flag is set to 0 (Auto) this flag determines the interval, in seconds after which the RMX will accept both DTMF tones (inband) and digits (outband).
PAGE 723
Chapter 22-System Configuration Flags Table 22-2 Manually Added System Flags – MCMS_PARAMETERS (Continued) Flag Description SIP_FREE_VIDEO_RESOU RCES For use in Avaya and Microsoft Environments. When set to NO (required for Avaya and Microsoft environments), video resources that were allocated to participants remain allocated to the participants as long as they are connected to the conference even if the call was changed to audio only.
PAGE 724
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-2 Manually Added System Flags – MCMS_PARAMETERS (Continued) 22-38 Flag Description SUPPORT_HIGH _PROFILE_WITH_ISDN Enables or disables the support of High Profile video protocol for ISDN participants in CP conferences. This flag is specific to CP conferences and has no effect on VSW conferences.
PAGE 725
Chapter 22-System Configuration Flags Table 22-2 Manually Added System Flags – MCMS_PARAMETERS (Continued) Flag Description WRONG_NUMBER_DIAL_ RETRIES The number of re-dial attempts for a wrong destination number or a wrong destination number time-out. Range: 0 - 5 Default: 3 A flag value of 0 means that no redials are attempted. 4 Click OK to close the New Flag dialog box. The new flag is added to the flags list. 5 Click OK to close the System Flags dialog box.
PAGE 726
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-3 Manually Added Flags - CS_MODULE_PARAMETERS Tab Flag Description MS_UPDATE_CON TACT_REMOVE • When the flag value is set to: YES - The Contact Header is removed from the UPDATE message that is sent periodically to the endpoints. This is required when the SIP Server Type field of the IP Network Service is set as Microsoft. Removal of the Contact Header from the UPDATE message is required specifically by OCS R2.
PAGE 727
Chapter 22-System Configuration Flags Auto Layout Configuration The Auto Layout option lets the RMX automatically select the conference video layout based on the number of participants currently connected to the conference. You can modify the default selection of the conference video layout to customize it to your conferencing preferences. Customizing the Default Auto Layout The default Auto Layout is controlled by 13 flags: PREDEFINED_AUTO_LAYOUT_0, ...
PAGE 728
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-4 Flags: PREDEFINED_AUTO_LAYOUT_0,...,10 (Continued) Flag Name: PREDEFINED_AUTO_LAYOUT_n (n = Number of Participants) n Default Value Possible Values CP_LAYOUT_1P4VER CP_LAYOUT_1P5 CP_LAYOUT_1P7 CP_LAYOUT_1P8UP CP_LAYOUT_1P8CENT CP_LAYOUT_1P8HOR_UP CP_LAYOUT_3X3 CP_LAYOUT_2P8 CP_LAYOUT_1P12 CP_LAYOUT_4X4 22-42 Polycom, Inc.
PAGE 729
Chapter 22-System Configuration Flags Example: Table 22-5 illustrates the effect of modifying the PREDEFINED_AUTO_LAYOUT_5 flag in conferences with fewer or more participants than the number of windows selected in the default layout.
PAGE 730
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-6 LEGACY_EP_CONTENT_DEFAULT_LAYOUT Flag Values (Continued) Layout Flag Value CP_LAYOUT_1X2 CP_LAYOUT_1X2HOR CP_LAYOUT_1X2VER CP_LAYOUT_2X1 CP_LAYOUT_1P2HOR CP_LAYOUT_1P2HOR_UP CP_LAYOUT_1P2VER CP_LAYOUT_2X2 CP_LAYOUT_1P3HOR_UP CP_LAYOUT_1P3VER CP_LAYOUT_1P4HOR_UP CP_LAYOUT_1P4HOR CP_LAYOUT_1P4VER CP_LAYOUT_1P5 CP_LAYOUT_1P7 CP_LAYOUT_1P8UP CP_LAYOUT_1P8CENT CP_LAYOUT_1P8HOR_UP CP_LAYOUT_3X3 22-44 Polycom, Inc.
PAGE 731
Chapter 22-System Configuration Flags Table 22-6 LEGACY_EP_CONTENT_DEFAULT_LAYOUT Flag Values (Continued) Layout Flag Value CP_LAYOUT_2P8 CP_LAYOUT_1P12 CP_LAYOUT_4X4 CS_ENABLE_EPC Flag Endpoints that support People+ may require a different signaling (for example, FX endpoints). For these endpoints, manually add the flag CS_ENABLE_EPC with the value YES (default value is NO) to the CS_MODULE_PARAMETERS tab.
PAGE 732
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 be activated using the existing passwords. Only new conferencing entities will be affected by the change. Do not enable this option in an environment that includes a Polycom DMA system.
PAGE 733
Chapter 22-System Configuration Flags Table 22-7 Automatic Password Generation Flags (Continued) Flag Description NUMERIC_CONF_PASS_DEFAULT_L EN This flag enables or disables the automatic generation of conference passwords. The length of the automatically generated passwords is determined by the flag value. Possible values: • 0 – 16, 6 default (non-secured mode) • 0 and 9 – 16, 9 default (Ultra Secure Mode). Enter 0 to disable the automatic generation of passwords.
PAGE 734
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Flags Specific to Maximum Security Environments - Ultra Secure Mode The RMX can operate in one of two modes: Standard Security Mode or Ultra Secure Mode. In Ultra Secure Mode the enhanced security features of the version are rigorously enforced. The Ultra Secure Mode is enabled or disabled depending on the value of the ULTRA_SECURE_MODE System Flag.
PAGE 735
Chapter 22-System Configuration Flags • The ULTRA_SECURE_MODE System Flag affects the ranges and defaults of the System Flags that control: — Network Security — User Management — Strong Passwords — Login and Session Management — Cyclic File Systems Table 22-8 lists the effect that setting the ULTRA_SECURE_MODE System Flag to YES has on all the other Ultra Secure Mode Specific System Flags. For flag descriptions see "ULTRA_SECURE_MODE System Flag Descriptions” on page 22-51.
PAGE 736
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-8 ULTRA_SECURE_MODE Flag Value – Effect on System Flags (Continued) ULTRA_SECURE_MODE = Flag YES NO Range Default Range Default 1-90 30 0-90 0 FORCE_STRONG_PA SSWORD_POLICY YES YES YES/NO NO HIDE_CONFERENCE_ PASSWORD YES/NO NO YES/NO NO HIDE_CONFERENCE_ PASSWORD YES/NO NO YES/NO NO MAX_CONF_PASSWO RD_REPEATED_CHA R 1-4 2 MAX_PASSWORD_RE PEATED_CHAR 1-4 2 MIN_PASSWORD_LE NGTH 15-20 15 0-20 0 MIN_PWD_
PAGE 737
Chapter 22-System Configuration Flags Table 22-8 ULTRA_SECURE_MODE Flag Value – Effect on System Flags (Continued) ULTRA_SECURE_MODE = Flag YES NO Range Default Range Default YES/NO YES YES/NO NO Cyclic File Systems ENABLE_CYCLIC_FIL E_SYSTEM_ALARMS ULTRA_SECURE_MODE System Flag Descriptions Table 22-9 ULTRA_SECURE_MODE System Flag Descriptions Flag Description Network Security SEPARATE_MNGT_NET WORK When this System Flag is set to YES, all signaling between IP endpoints and the RMX is via
PAGE 738
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 22-9 ULTRA_SECURE_MODE System Flag Descriptions Flag Description USER_LOCKOUT User Lockout can be enabled to lock a user out of the system after three consecutive Login failures with same User Name. The user is disabled and only the administrator can enable the user within the system.
PAGE 739
Chapter 22-System Configuration Flags Table 22-9 ULTRA_SECURE_MODE System Flag Descriptions Flag Description MIN_PWD_CHANGE_F REQUENCY_IN_DAYS The frequency with which a user can change a password is determined by the value of this System Flag. The value of the flag is the number of days that users must retain a password. It cannot be set to NO when the RMX is in Ultra Secure Mode. NUMERIC_CHAIR_PAS S_MIN_LEN The length of the Chairperson password is determined by the value of this System Flag.
PAGE 740
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 22-54 Polycom, Inc.
PAGE 741
23 RMX Hardware Monitoring The status and properties of the RMX hardware components can be viewed and monitored in the Hardware Monitor list pane. Viewing the Status of the Hardware Components The Hardware Monitor’s status column displays the present status of the hardware components. In addition to the status, temperature and voltage indications are provided for each component. The MCU’s Shelf Management Server is what users are connecting to when accessing the Hardware Monitor pane.
PAGE 742
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 The Hardware Monitor pane displays the following RMX hardware component’s status columns: Table 23-1 HW Monitor Pane Status Columns Field Description Slot Displays an icon according to the HW component type and the slot number. The icon displays the hardware status as follows: • An exclamation point (!) indicates errors in the HW component. • Card icon with the reset button ( is currently resetting.
PAGE 743
Chapter 23-RMX Hardware Monitoring Table 23-2 HW Monitor Pane Tool Bar Buttons (Continued) Button Name Description Logger Mode Diagnostics Tests selection and Tests monitoring. Note: This button is only displayed when connecting directly to the Shelf Management server and logged in as a special support user. Viewing the Properties of RealPresence Collaboration Server (RMX) 1500 Hardware Components The properties displayed for the hardware components will vary according to the type of component viewed.
PAGE 744
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 To view the MCU Properties: 1 In the Hardware Monitor pane, either double-click or right-click and select Properties for RMX 1500, slot 0. The following information is displayed: Table 23-3 MCU Properties - General Info 2 23-4 Field Description Chassis File ID The ID assigned to the MCU’s chassis file. Chassis Serial Number The serial number assigned to the MCU’s chassis. Part Number The chassis part number.
PAGE 745
Chapter 23-RMX Hardware Monitoring The logged events can be saved to a *.xls file by clicking the Save Event Log button. It is not possible to save individual or multiple selected events; the entire log file must be saved. Table 23-4 MCU Properties - Event Log 3 Column Description Record ID The recorded ID number of the logged event. Time Stamp Lists the date and time that the event occurred. Type Displays the type of event recorded in the log.
PAGE 746
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 To view the Card Properties: 1 In the Hardware Monitor pane, either double-click or right-click and select properties for the desired hardware component. The following information is displayed: Table 23-5 Card Properties - General Info Field Description Hardware Version The hardware component’s version number. Software Version The version number of the software installed on card. Serial Number The hardware component’s serial number.
PAGE 747
Chapter 23-RMX Hardware Monitoring To View the Supporting Hardware Components Properties: 1 In the Hardware Monitor pane, either double-click or right-click and select properties for the desired supporting hardware component. The component’s properties dialog box will appear with the General Info tab displayed. Backplane Properties: The RMX unit’s backplane properties provides the following information: Table 23-6 Backplane Properties - General Info Polycom, Inc.
PAGE 748
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 FAN Properties: The RMX unit’s chassis contains 3 fans that regulate the unit’s temperature. If the temperature increases, the fans speed will increase and vice-versa. A “Critical” condition in the fans operation will result in a system shut down. Table 23-7 FANS Properties - General Info Field Description General Settings Min. Speed Level (rpm) The minimum speed level of the fans. Max.
PAGE 749
Chapter 23-RMX Hardware Monitoring LAN 1, LAN 2, LAN 3 Properties: The RMX unit’s chassis contains 3 external LAN connectors which register the following information listed below. The information will be refreshed every 8 seconds and also contains a peek detector to log the maximal values, since the last peek values reset. 2 Click Close to return to the HW Monitor pane.
PAGE 750
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 The Hardware Properties dialog box has the following structure: Slot number HW component type Component Information (changes according to selected type) To view the MCU Properties: 1 In the Hardware Monitor pane, either double-click or right-click and select properties for RMX 2000, slot 0.
PAGE 751
Chapter 23-RMX Hardware Monitoring Table 23-8 MCU Properties - General Info (Continued) 2 Field Description Chassis Serial Number The serial number assigned to the MCU’s chassis. Part Number The chassis part number. The Part Number contains the letter A/B/C/ D that represents the chassis type. Card Type The name of the hardware product or component, i.e. RMX 2000, Backplane. Chassis HW Version Indicates the MCU’s current chassis hardware version. Turn SSH Enables/disables the SSH monitor.
PAGE 752
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 23-9 MCU Properties - Event Log (Continued) 3 Column Description Ipmb Address(hex) Contains all the internal IPMI network addresses on the IPMB bus, i.e. 0x20 (Switch), 0x86 (MFA), etc... Click the Active Alarms tab to view alarms related to the RMX, i.e. temperatures and main power sensors. The Active Alarms dialog box displays fields that relate to faults and errors detected on the RMX by sensors.
PAGE 753
Chapter 23-RMX Hardware Monitoring Table 23-10 Card Properties - General Info (Continued) 2 Field Description Serial Number The hardware component’s serial number. Card Type Displays the type of card that occupies the slot. Card Part Number The part number of the HW component’s board. Card MAC Address 1 Specific hardware address of the component. This address is burnt onto the component and is automatically identified by the system. Card MAC Address 2 (If applicable) second Mac address.
PAGE 754
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 23-11 Backplane Properties- General Info (Continued) Field Description Card Part Number The Backplane’s part number. Card Mac Address 1 The Backplane’s hardware address. Card Mac Address 2 (If applicable) second Backplane Mac address. FAN Properties: The RMX unit’s chassis contains 3 fans that regulate the unit’s temperature. If the temperature increases, the fans speed will increase and vice-versa.
PAGE 755
Chapter 23-RMX Hardware Monitoring LAN 0, LAN 1, LAN 2 Properties: The RMX unit’s chassis contains 3 external LAN connectors which register the following information listed below. The information will be refreshed every 8 seconds and also contains a peek detector to log the maximal values, since the last peek values reset. 2 Click Close to return to the HW Monitor pane.
PAGE 756
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 The Hardware Properties dialog box has the following structure: Slot number HW component type Component Information (changes according to selected type) To view the MCU Properties: 1 In the Hardware Monitor pane, either double-click or right-click and select Properties for RMX 4000, slot 0.
PAGE 757
Chapter 23-RMX Hardware Monitoring Table 23-13 MCU Properties - General Info (Continued) 2 Field Description Part Number The chassis part number. The Part Number contains the letter A/B/C/ D that represents the chassis type. Card Type The name of the hardware product or component, i.e. RMX 4000, Backplane. Chassis HW Version Indicates the MCU’s current chassis hardware version. Turn SSH Enables/disables the SSH monitor.
PAGE 758
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 3 Click the Active Alarms tab to view alarms related to the RMX, i.e. temperatures and main power sensors. The Active Alarms dialog box displays fields that relate to faults and errors detected on the RMX by sensors. The Active Alarms dialog box is divided into two sections: HW Alarm List and SW Alarm List. Each section’s alarm list can be saved as a *.xls file by clicking the Save HW Alarm List and Save SW Alarm List buttons respectively.
PAGE 759
Chapter 23-RMX Hardware Monitoring 2 Click the Event Log tab to view a log of events that was recorded by the system on the HW component. For more information, see "MCU Properties - Event Log” on page 23-11. 3 Click the Active Alarms tab to view alarms related to the hardware component, i.e. temperatures and main power sensors. For more information, see “Active Alarms” on page 23-12. 4 Click Close to return to the HW Monitor pane.
PAGE 760
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 23-16 Backplane+ Properties- General Info (Continued) Field Description Board Mac Address 2 (If applicable) second Backplane Mac address. FAN Properties: The RMX unit’s chassis contains 3 fans that regulate the unit’s temperature. If the temperature increases, the fans speed will increase and vice-versa. A “Critical” condition in the fans operation will result in a system shut down.
PAGE 761
Chapter 23-RMX Hardware Monitoring LAN 0, LAN 1, LAN 2 Properties: The RMX unit’s chassis contains 3 external LAN connectors which register the following information listed below. The information will be refreshed every 8 seconds and also contains a peek detector to log the maximal values, since the last peek values reset. 2 Click Close to return to the HW Monitor pane. Diagnostic Mode (RMX 1500/2000/4000) • • You cannot run diagnostics on the MPM card. On all RMX systems with version 7.0.2 & 7.6.
PAGE 762
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Access the RMX browser and click Hardware Monitor. The Hardware Monitor pane opens. On the Hardware Monitor toolbar click the Shelf Manager icon. Type in the URL address of the Shelf Management (IP address). For example; 172.22.189.51. You must also Login as an “Administrator” user to run diagnostics Login to the Shelf Manager. On the Hardware Monitor toolbar select either the Basic Mode or Advanced Mode diagnostics.
PAGE 763
Chapter 23-RMX Hardware Monitoring 1 In the list pane tool bar, click the Basic Mode ( ) button. RMX 2000/4000 & RealPresence Collaboration Server (RMX) 1500 Hardware Monitor panes Polycom, Inc. 2 In the Reset Confirmation dialog box, click Yes. 3 The RMX resets. Re-enter the Shelf Manager IP address in the browser and Login under POLYCOM or with an “Administrator” Login.
PAGE 764
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 After login the following screen appears. RMX 2000/4000 & RealPresence Collaboration Server (RMX) 1500 Hardware Monitor panes The MPM+/MPMx cards indicate “Resetting” and later switch to “Diagnostics”. The status of RTM-IP/RTM IP 1500/RTM-IP 4000 and CNTL/CNTL 1500/CNTL 4000 components change to “Diagnostics”.
PAGE 765
Chapter 23-RMX Hardware Monitoring 5 Run Diagnostic Tests & Tests Monitoring by clicking the Run Tests button. In the Hardware Monitor pane, the toolbar and card statuses change to Tests in progress. Table 23-18 Run Tests - Parameters Parameter Description Diagnostic Status Basic Diagnostic Status: • Ready - ready to run diagnostics • • Test in Progress - running diagnostics Passed/Failed - Passed/Failed the diagnostics tests Estimated Duration Estimated time needed to run Basic Diagnostic tests.
PAGE 766
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 6. The Diagnostics Summary pane is displayed at the bottom of the Hardware Monitoring pane. Figure 23-1RMX 2000/4000 Diagnostics Tests & Monitoring Tests Figure 23-2RealPresence Collaboration Server (RMX) 1500 Diagnostics Tests & Monitoring Tests 7 Select the Run all Tests box and then click Run Selected Tests.
PAGE 767
Chapter 23-RMX Hardware Monitoring Performing Advanced Mode Diagnostics To run Diagnostics you are required to Login with administrator permissions. To run Advanced Mode Diagnostics on a Hardware Component: • Most of the user interfaces illustrated in this section show the RealPresence Collaboration Server (RMX) 2000 with MPMx cards. The Advanced Mode for other RMXs with MPM+ card(s) are identical.
PAGE 768
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 3 The RMX resets. Re-enter the Shelf Manager IP address in the browser and Login using an “Administrator” Login. The MPM+/MPMx cards indicate “Resetting” and later switch to “Diagnostics”. The status of RTM-IP/RTM IP 1500/RTM-IP 4000 and CNTL/CNTL 1500/CNTL 4000 components change to “Diagnostics”.
PAGE 769
Chapter 23-RMX Hardware Monitoring You can view Diagnostic Tests & Tests Monitoring by clicking the Advanced Diagnostics Tab. Advanced Diagnostics Tab When you click the Advanced Mode the RMX enters a “Diagnostics Mode”. The Advanced Mode can be exited by pressing the yellow System Reset icon. The RMX then resets. The Diagnostics Tests & Monitoring Tests panes are displayed on the right side of the window pane.
PAGE 770
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Run all Test Selection Diagnostics Test Monitoring Figure 23-4 RealPresence Collaboration Server (RMX) 1500 Diagnostics Tests & Monitoring Tests 5 When the RMX enters “Diagnostics Mode”, the status MPM+/MPMx, CNTL/CNTL 1500/CNTL 4000 and RTM IP/RTM IP 1500/RTM IP 4000 changes to “Diagnostics”.
PAGE 771
Chapter 23-RMX Hardware Monitoring Table 23-20 Tests Selection - Additional Test Parameters (Continued) 7 Parameter Description Run All Test Runs all tests listed in the TestActive column for the hardware component. The selected tests are initialized. In the Tests Monitoring pane there is an indication of the Connection Status of the Tests. Connection Status 8 This process may take some time. Click Stop Running Test to end all the diagnostic tests.
PAGE 772
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Table 23-21 Tests Monitoring - MCU Monitor Parameters Column Description Card The card’s slot number, i.e. 5 - slot where the RTM IP card resides. Pass Indicates the number of tests that the card passed successfully. Fail Indicates the number of tests that the card failed. Status The card’s current test status: No test running or Test in progress.
PAGE 773
Chapter 23-RMX Hardware Monitoring Error Buffer The Error Buffer tab displays the errors encountered during testing of the cards. Table 23-23 Tests Monitoring - Card Monitor Parameters Polycom, Inc. Column Description Testid The test ID number. ErrorString Indicates the error encountered during testing.
PAGE 774
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Temperature Thresholds On each RMX card or there are temperature sensors that are placed near specific components on the card. In the Hardware Monitor you can view the properties of each card together with their temperature statuses. By right clicking on any card and viewing the cards Properties, the Active Alarms tab displays all the card sensors, their statuses and lists each sensor’s temperature specifications.
PAGE 775
Chapter 23-RMX Hardware Monitoring RMX RTM-IP 1500/RTM-IP/RTM IP 4000 Card Properties To view the RMX RTM-IP 1500/RTM-IP/RTM IP 4000 Properties: 1 In the Hardware Monitor pane, right-click the RTM IP entry and then select Properties. Right clicking on any RMX card will display the cards Properties. 2 Click Active Alarms. Figure 23-7RealPresence Collaboration Server (RMX) 2000 RTM-IP Temperature Sensors The RTM-IP is populated with 4 temperature sensors numbered: Sensor 14-17.
PAGE 776
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 2 Click Active Alarms. Figure 23-8RealPresence Collaboration Server (RMX) 2000 CNTL Temperature Sensors The hottest capacity sensor on the CNTL card is sensor 10, and when this sensor reaches 70° (degrees) Centigrade, it triggers an "Upper Major" event. The Sensor numbering and Temperature listings may vary on RMX systems depending on card’s Hardware Version and Software Version number.
PAGE 777
Chapter 23-RMX Hardware Monitoring MPM+ Card Properties The MPM+ card does not support version 7.6.1 features or look & feel. To view the MPM+ Properties: 1 In the Hardware Monitor pane, right-click the MPM+ entry and then select Properties. Right clicking on any RMX MPM+ card will display the cards Properties. 2 Click Active Alarms. Figure 23-9RealPresence Collaboration Server (RMX) 2000 MPM+80 Properties The MPM+80 card has 7 temperature sensors numbered: 11-17.
PAGE 778
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 MPMx Card Properties To view the MPMx Properties: 1 In the Hardware Monitor pane, right-click the MPMx entry and then select Properties. Right clicking on any RMX MPMx card will display the cards Properties. 2 Click Active Alarms.
PAGE 779
Appendix A Disconnection Causes If a participant was unable to connect to a conference or was disconnected from a conference, the Connection Status tab in the Participant Properties dialog box indicates the call disconnection cause. In some cases, a possible solution may be displayed. A video participant who is unable to connect the video channels, but is able to connect as an audio only participant, is referred to as a Secondary participant.
PAGE 780
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table A-1 A-2 Call Disconnection Causes (Continued) Disconnection Cause Description H323 call closed. Small bandwidth The gatekeeper allocated insufficient bandwidth to the connection with the endpoint. H323 call closed. No port left There are no free ports left in the IP card. Caller not registered The calling endpoint is not registered in the gatekeeper. H323 call closed.
PAGE 781
Chapter A-Disconnection Causes Table A-1 Polycom, Inc. Call Disconnection Causes (Continued) Disconnection Cause Description H323 call closed. Remote sent bad capability There was a problem in the capabilities sent by the endpoint. H323 call closed. Local capability wasn't accepted by remote The endpoint did not accept the capabilities sent by the gatekeeper. H323 failure Internal error occurred. H323 call closed. Remote stop responding The endpoint stopped responding. H323 call closed.
PAGE 782
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table A-1 A-4 Call Disconnection Causes (Continued) Disconnection Cause Description SIP client error 407 The endpoint sent a SIP Client Error 407 (Proxy Authentication Required) response. The client must first authenticate itself with the proxy. SIP client error 409 The endpoint sent a SIP Client Error 409 (Conflict) response.
PAGE 783
Chapter A-Disconnection Causes Table A-1 Polycom, Inc. Call Disconnection Causes (Continued) Disconnection Cause Description SIP forbidden The SIP server rejected the request. The server understood the request, but is refusing to fulfill it. SIP global failure 603 A SIP Global Failure 603 (Decline) response was returned. The participant's endpoint was successfully contacted, but the participant explicitly does not wish to or cannot participate.
PAGE 784
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table A-1 A-6 Call Disconnection Causes (Continued) Disconnection Cause Description SIP server error 500 The SIP server sent a SIP Server Error 500 (Server Internal Error) response. The server encountered an unexpected condition that prevented it from fulfilling the request. SIP server error 501 The SIP server sent a SIP Server Error 501 (Not Implemented) response.
PAGE 785
Chapter A-Disconnection Causes ISDN Disconnection Causes Table A-2 ISDN Disconnection Causes Disconnection Cause Number 1 Summary Description Unallocated (unassigned number) No route to the number exists in the ISDN network or the number was not found in the routing table. • Ensure that the number appears in the routing table. • 2 No route to specified transit network (national use) The route specified (transit network) between the two networks does not exist.
PAGE 786
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table A-2 ISDN Disconnection Causes (Continued) Disconnection Cause Number A-8 Summary Description 22 Number Changed Same as Cause 1. The diagnostic field contains the new called user number. Cause 1 is used if the network does not support this cause value. 26 Non-Selected User Clearing The incoming call has not been assigned to the user.
PAGE 787
Chapter A-Disconnection Causes Table A-2 ISDN Disconnection Causes (Continued) Disconnection Cause Number Polycom, Inc. Summary Description 53 Outgoing Calls Barred Within Closed User Group (CUG) Outgoing calls are not permitted for this member of the CUG. 55 Incoming Calls Barred within CUG Incoming calls are not permitted for this member of the CUG. 57 Bearer Capability Not Authorized A bearer capability has been requested that the user is not authorized to use.
PAGE 788
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table A-2 ISDN Disconnection Causes (Continued) Disconnection Cause Number A-10 Summary Description 86 Call Having the Requested Call Identity Has Been Cleared A RESUME message cannot be executed by the network as a result of the call having been cleared while suspended. 87 User Not Member of CUG A CUG member was called by a user who is not a member of the CUG or a CUG call was made to a non CUG member.
PAGE 789
Chapter A-Disconnection Causes Table A-2 ISDN Disconnection Causes (Continued) Disconnection Cause Number Polycom, Inc. Summary Description 103 Parameter NonExistent or Not Implemented – Passed On (national use) A message was received containing parameters that are not defined or of a type that is defined but not implemented. 110 Message with Unrecognized Parameter Discarded A message was discarded because it contained a parameter that was not recognized.
PAGE 790
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide A-12 Polycom, Inc.
PAGE 791
Appendix B Alarms and Faults Alarms Table B-1 Alarms Alarm Code Alarm Description A new activation key was loaded. Reset the system. A new activation key was loaded: Reset the MCU. A new version was installed. Reset the system. A new version was installed: Reset the MCU. Alarm generated by a Central Signaling component A system alert was generated by a component of the Central Signaling. Alarm generated by an internal component A system alert was generated by an internal system component.
PAGE 792
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table B-1 Alarms (Continued) Alarm Code Alarm Description Card not found This occurs when: the system does not receive an indication about the card (since it does not exist…) usually when the card was removed from the MCU and the system did not have a chance to recalculate it resources. Card not responding Possible reasons for the card not responding: • No connection with MPM card.
PAGE 793
Appendix B-Alarms and Faults Table B-1 Alarms (Continued) Alarm Code Alarm Description DMA not supported by IDE device Possible explanations: • DMA (direct memory access) not supported by IDE device: Incompatible flash card / hard disk being used. • Flash card / hard drive are not properly connected to the board / one of the IDE channels is disconnected. • DMA was manually disabled for testing. DNS configuration error DNS not configured in IP Network Service Encryption Server Error.
PAGE 794
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table B-1 Alarms (Continued) Alarm Code Alarm Description Fallback version is being used Fallback version is being used. Restore current version. Version being used: [running version]; Current version: [current version]. File error Possible reasons for the file error: • XML file does not exist [file name]; Error no: [error number]. • • • Not authorized to open XML file [file name]; Error no: [error number].
PAGE 795
Appendix B-Alarms and Faults Table B-1 Alarms (Continued) Alarm Code Alarm Description Gatekeeper failure (cont.) • • • • • • • • • • • • Gatekeeper rejected RRQ due to invalid terminal alias. Gatekeeper rejected RRQ due to resource unavailability. Gatekeeper rejected RRQ due to Security Denial. Gatekeeper rejected RRQ due to terminal type. Gatekeeper rejected RRQ due to unsupported Additive Registration. Gatekeeper rejected RRQ due to unsupported feature.
PAGE 796
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table B-1 Alarms (Continued) Alarm Code Alarm Description MPL startup failure. Management Network configuration not received.
PAGE 797
Appendix B-Alarms and Faults Table B-1 Alarms (Continued) Alarm Code Alarm Description Restoring Factory Defaults. Default system settings will be restored once Reset is completed Default system settings will be restored once Reset is completed. RTM ISDN card not found RTM ISDN card is missing. RTM ISDN card startup procedure error The RTM ISDN card cannot complete its startup procedure (usually after system reset) Secured SIP communication failed Security mode failed. Certificate has expired.
PAGE 798
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table B-1 Alarms (Continued) Alarm Code Alarm Description SIP TLS: Registration server not responding This alarm is displayed when the MCU does not receive a response from the OCS to the registration request in the expected time frame. Possible causes are: SIP TLS: Registration transport error • The MCU FQDN name is not defined in the OCS pool, or is defined incorrectly.
PAGE 799
Appendix C CDR Fields - Unformatted File The CDR (Call Detail Records) utility is used to retrieve conference information to a file. The CDR utility can retrieve conference information to a file in both formatted and unformatted formats. Unformatted CDR files contain multiple records. The first record in each file contains information about the conference in general, such as the conference name and start time.
PAGE 800
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The Conference Summary Record The conference summary record (the first record in the unformatted CDR file) contains the following fields: Table C-1 Conference Summary Record Fields Field Description File Version The version of the CDR utility that created the file. Conference Routing Name The Routing Name of the conference. Internal Conference ID The conference identification number as assigned by the system.
PAGE 801
Appendix C-CDR Fields - Unformatted File Table C-1 Conference Summary Record Fields (Continued) Field Description GMT Offset The time zone difference between Greenwich and the MCU’s physical location in hours and minutes. Together with the GMT Offset Sign field the GMT Offset field is used to define the MCU local time.
PAGE 802
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Event Types The table below contains a list of the events that can be logged in the CDR file, and indicates where to find details of the fields that are specific to that type of event. The event code identifies the event in the unformatted CDR file, and the event name identifies the event in the formatted CDR file. Table C-2 CDR Event Types Event Code Event Name Description 1 CONFERENCE START The conference started.
PAGE 803
Appendix C-CDR Fields - Unformatted File Table C-2 CDR Event Types (Continued) Event Code Event Name Description 10 DEFINED PARTICIPANT Information about a defined participant, that is, a participant who was added to the conference before the conference started. For more information about the fields, see Table C-14, “Event Fields for Events 10, 101, 105 - DEFINED PARTICIPANT, USER ADD PARTICIPANT, USER UPDATE PARTICIPANT,” on page C-20.
PAGE 804
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table C-2 CDR Event Types (Continued) Event Code Event Name Description 28 SIP PRIVATE EXTENSIONS Contains SIP Private Extensions information. GATEKEEPER INFORMATION Contains the gatekeeper caller ID, which makes it possible to match the CDR in the gatekeeper and in the MCU. 30 For more information about the fields, see Table C-25, “Event Fields for Event 28 - SIP PRIVATE EXTENSIONS,” on page C-31.
PAGE 805
Appendix C-CDR Fields - Unformatted File Table C-2 CDR Event Types (Continued) Event Code Event Name Description 101 USER ADD PARTICIPANT A user added a participant to the conference during the conference. For more information about the fields, see Table C-14, “Event Fields for Events 10, 101, 105 - DEFINED PARTICIPANT, USER ADD PARTICIPANT, USER UPDATE PARTICIPANT,” on page C-20. 102 103 104 105 USER DELETE PARTICIPANT A user deleted a participant from the conference.
PAGE 806
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table C-2 Event Code Event Name Description 109 OPERATOR ATTEND PARTY The MCU User moved the participant to the Operator conference. For more information, see Table C-35, “Event Fields for Events 107 and 109 - OPERATOR MOVE PARTY FROM CONFERENCE and OPERATOR ATTEND PARTY,” on page C-34. 111 OPERATOR BACK TO CONFERENCE PARTY The MCU User moved the participant back to his Home (source) conference.
PAGE 807
Appendix C-CDR Fields - Unformatted File Table C-2 Event Code Event Name Description 2012 RESERVED PARTICIPANT CONTINUE 2 Additional information about a DEFINED PARTICIPANT event. USER ADD PARTICIPANT CONTINUE 1 Additional information about a USER ADD PARTICIPANT event. USER ADD PARTICIPANT CONTINUE 2 Additional information about a USER ADD PARTICIPANT event. USER UPDATE PARTICIPANT CONTINUE 1 Additional information about a USER UPDATE PARTICIPANT event.
PAGE 808
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table C-2 CDR Event Types (Continued) Event Code Event Name Description 5001 CONFERENCE START CONTINUE 4 Additional information about a CONFERENCE START event. For more information about the fields, see Table C-5, “Event Fields for Event 5001 - CONFERENCE START CONTINUE 4,” on page C-14.
PAGE 809
Appendix C-CDR Fields - Unformatted File Table C-3 Polycom, Inc. Event Fields for Event 1 - CONFERENCE START (Continued) Field Description Auto Terminate Indicates whether the conference was set to end automatically if no participant joins the conference for a predefined time period after the conference starts, or if all participants disconnect from the conference and the conference is empty for a predefined time period. Possible values are: 0 - The conference was not set to end automatically.
PAGE 810
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table C-3 Field Description T120 Rate Not supported. Always contains the value 0. Table C-4 C-12 Event Fields for Event 1 - CONFERENCE START (Continued) Event Fields for Event 2001 - CONFERENCE START CONTINUE 1 Field Description Audio Tones Not supported. Always contains the value 0. Alert Tone Not supported. Always contains the value 0.
PAGE 811
Appendix C-CDR Fields - Unformatted File Table C-4 Polycom, Inc. Event Fields for Event 2001 - CONFERENCE START CONTINUE 1 (Continued) Field Description Minimum Number of Participants The number of participants for which the system reserved resources. Additional participants may join the conference without prior reservation until all the resources are utilized. Currently the only value is 0.
PAGE 812
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table C-4 Event Fields for Event 2001 - CONFERENCE START CONTINUE 1 (Continued) Field Description Lecture Mode Type Indicates the type of Lecture Mode, as follows: 0 - None 1 - Lecture Mode 3 - Presentation Mode Lecturer Note: This field is only relevant if the Lecture Mode Type is Lecture Mode. The name of the participant selected as the conference lecturer.
PAGE 813
Appendix C-CDR Fields - Unformatted File Table C-6 Field Description Encryption Indicates the conference encryption setting, as follows: 0 - The conference is not encrypted. 1 -The conference is encrypted. Table C-7 Event Fields for Event 11001 - CONFERENCE START CONTINUE 10 Field Description Display Name The Display Name of the conference.
PAGE 814
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table C-9 Event fields for Event 3 - ISDN/PSTN CHANNEL CONNECTED (Continued) Field Description Call Type The call type, as follows: 68 - 56 KBS data call 72 - 1536kbs data call (PRI only) 75 - 56 KBS data call 77 - Modem data service 79 - 384kbs data call (PRI only) 86 - Normal voice call Network Service Program The Network Service program, as follows: 0 - None 1 - ATT_SDN or NTI_PRIVATE 3 - ATT_MEGACOM or NTI_OUTWA
PAGE 815
Appendix C-CDR Fields - Unformatted File Table C-9 Event fields for Event 3 - ISDN/PSTN CHANNEL CONNECTED (Continued) Field Description Calling Participant Phone Number The telephone number used for dial-in.
PAGE 816
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table C-11 Event fields for Event 5 - ISDN/PSTN PARTICIPANT CONNECTED (Continued) Field Description Participant ID The identification number assigned to the participant by the MCU. Participant Status The participant status, as follows: 0 -Idle 1 -Connected 2 - Disconnected 3 - Waiting for dial-in 4 -Connecting 5 - Disconnecting 6 - Partially connected. Party has completed H.
PAGE 817
Appendix C-CDR Fields - Unformatted File Table C-11 Event fields for Event 5 - ISDN/PSTN PARTICIPANT CONNECTED (Continued) Field Description Secondary Cause (cont.) 15 - Video stream violation due to incompatible annexes or other discrepancy.
PAGE 818
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table C-13 Event Fields for Event 2007 - PARTICIPANT DISCONNECTED CONTINUE 1 Field Description Mux Board ID Not supported. Always contains the value 0. Mux Unit ID Not supported. Always contains the value 0. Audio Codec Board ID Not supported. Always contains the value 0. Audio Codec Unit ID Not supported. Always contains the value 0. Audio Bridge Board ID Not supported. Always contains the value 0.
PAGE 819
Appendix C-CDR Fields - Unformatted File Table C-14 Event Fields for Events 10, 101, 105 - DEFINED PARTICIPANT, USER ADD PARTICIPANT, USER UPDATE PARTICIPANT (Continued) Field Description Dialing Direction The dialing direction, as follows: 0 - Dial-out 5 - Dial-in Bonding Mode Not supported. Always contains the value 0. Number Of Channels Note: This field is only relevant to ISDN/PSTN participants. Net Channel Width Not supported. Always contains the value 0.
PAGE 820
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table C-14 Event Fields for Events 10, 101, 105 - DEFINED PARTICIPANT, USER ADD PARTICIPANT, USER UPDATE PARTICIPANT (Continued) Field Description Number of MCU Phone Numbers Note: This field is only relevant to ISDN/PSTN participants. Party and MCU Phone Numbers Note: This field is only relevant to ISDN/PSTN participants. Identification Method Note: This field is only relevant to dial-in participants.
PAGE 821
Appendix C-CDR Fields - Unformatted File Table C-15 Event Fields for Events 2010, 2011, 2015 - DEFINED PARTICIPANT CONTINUE 1, USER ADD PARTICIPANT CONTINUE 1, USER UPDATE PARTICIPANT CONTINUE 1 Field Description Undefined Participant Indicates whether are not the participant is an undefined participant, as follows: 0 - The participant is not an undefined participant. 2 - The participant is an undefined participant.
PAGE 822
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table C-16 Event Fields for Event 2011 - DEFINED PARTICIPANT CONTINUE 2, Event 2012 - USER ADD PARTICIPANT CONTINUE 2, Event 2016 - USER UPDATE PARTICIPANT CONTINUE 2 Field Description Encryption Indicates the participant’s encryption setting as follows: 0 - The participant is not encrypted. 1 - The participant is encrypted. 2 - Auto. The conference encryption setting is applied to the participant.
PAGE 823
Appendix C-CDR Fields - Unformatted File Table C-18 Event Fields for Events 17, 23 - H323 PARTICIPANT CONNECTED, SIP PARTICIPANT CONNECTED Field Description Participant Name The name of the participant. An empty field “” denotes an unidentified participant or a participant whose name is unspecified. Participant ID The identification number assigned to the participant by the MCU.
PAGE 824
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table C-18 Event Fields for Events 17, 23 - H323 PARTICIPANT CONNECTED, SIP PARTICIPANT CONNECTED (Continued) Field Description Secondary Cause Note: This field is only relevant if the Participant Status is Secondary.
PAGE 825
Appendix C-CDR Fields - Unformatted File Table C-19 Event Fields for Event 18 - NEW UNDEFINED PARTICIPANT (Continued) Field Description Restrict Not supported. Always contains the value 0. Audio Only Indicates the participant’s Audio Only setting, as follows: 0 - The participant is not an Audio Only participant 1 - The participant is an Audio Only participant 255 - Unknown Default Number Type Note: This field is only relevant to ISDN/PSTN participants. The type of telephone number.
PAGE 826
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table C-19 Event Fields for Event 18 - NEW UNDEFINED PARTICIPANT (Continued) Field Description Chair Not supported. Always contains the value 0. Video Protocol The video protocol, as follows: 1 - H.261 2 - H.263 4 - H.264 255 -Auto Broadcasting Volume The broadcasting volume assigned to the participant. The value is between 1 (lowest) and 10 (loudest). Each unit movement increases or decreases the volume by 3 dB.
PAGE 827
Appendix C-CDR Fields - Unformatted File Table C-19 Event Fields for Event 18 - NEW UNDEFINED PARTICIPANT (Continued) Field Description H.323 Participant Alias Type/SIP Participant Address Type Note: This field is only relevant to IP participants. For H.323 participants, the alias type, as follows: 7 - E164 8 - H.323 ID 13 - Email ID 14 - Participant number For SIP participants, the address type, as follows: 1 - SIP URI 2 - Tel URL H.
PAGE 828
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table C-22 Event Fields for Event 21 - SET PARTICIPANT DISPLAY NAME Field Description Participant Name The original name of the participant, for example, the name automatically assigned to an undefined participant, such as, “_(000)”. Participant ID The identification number assigned to the participant by the MCU.
PAGE 829
Appendix C-CDR Fields - Unformatted File Table C-24 Event fields for Event 26 - RECORDING LINK (Continued) Field Description Recording Link Name The name of the Recording Link. Recording Link ID The Recording Link ID. Start Recording Policy The start recording policy, as follows: 1 - Start recording automatically as soon as the first participant connects to the conference.
PAGE 830
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table C-27 Event fields for Event 31 - PARTICIPANT CONNECTION RATE (Continued) Field Description Participant Current Rate The participant line rate in Kbps. Table C-28 Event Fields for Event 32 Field Description IP V6 IPv6 address of the participant’s endpoint. Table C-29 Event fields for Event 33 - PARTY CHAIR UPDATE Field Description Participant Name The participant name.
PAGE 831
Appendix C-CDR Fields - Unformatted File Table C-31 Event Fields for Event 35 - SVC SIP PARTICIPANT CONNECTED Field Description Participant Name The name of the participant. An empty field "" denotes an unidentified participant or a participant whose name is unspecified Participant ID The identification number assigned to the participant by the MCU.
PAGE 832
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table C-33 Event Fields for Events 102,103, 104 - USER DELETE PARTICIPANT, USER DISCONNECT PARTICIPANT, USER RECONNECT PARTICIPANT Field Description User Name The login name of the user who reconnected the participant to the conference, or disconnected or deleted the participant from the conference.
PAGE 833
Appendix C-CDR Fields - Unformatted File Table C-36 Event Fields for Events 108, 112 - OPERATOR MOVE PARTY TO CONFERENCE, OPERATOR ATTEND PARTY TO CONFERENCE (Continued) Field Description Party ID The identification number assigned to the participant by the MCU. Connection Type The connection type, as follows: 0 - Dial-out 5 - Dial-in Bonding Mode Note: This field is only relevant to ISDN/PSTN participants.
PAGE 834
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table C-36 Event Fields for Events 108, 112 - OPERATOR MOVE PARTY TO CONFERENCE, OPERATOR ATTEND PARTY TO CONFERENCE (Continued) Field Description Net SubService Name Note: This field is only relevant to dial-out, ISDN/PSTN participants. The network sub-service name. An empty field “” means that MCU selects the default sub-service.
PAGE 835
Appendix C-CDR Fields - Unformatted File Table C-36 Event Fields for Events 108, 112 - OPERATOR MOVE PARTY TO CONFERENCE, OPERATOR ATTEND PARTY TO CONFERENCE (Continued) Field Description Video Protocol The video protocol, as follows: 1 - H.261 2 - H.263 3 - H.264* 4 - H.264 255 -Auto Audio Volume The broadcasting volume assigned to the participant. The value is between 1 (lowest) and 10 (loudest). Undefined Type The participant type, as follows: 0 - Defined participant.
PAGE 836
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table C-36 Event Fields for Events 108, 112 - OPERATOR MOVE PARTY TO CONFERENCE, OPERATOR ATTEND PARTY TO CONFERENCE (Continued) Field Description H.323 Party Alias Type/SIP Party Address Type Note: This field is only relevant to IP participants. For H.323 participants, the alias type, as follows: 7 - E164 8 - H.
PAGE 837
Appendix C-CDR Fields - Unformatted File Table C-39 Event Fields for Event 3010 - PARTICIPANT INFORMATION Field Description Info1 Info2 Info3 Info4 The participant information fields. These fields enable users to enter general information about the participant, such as the participant’s e-mail address. The maximum length of each field is 80 characters. VIP Not supported. Always contains the value 0.
PAGE 838
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table C-40 Disconnection Cause Values (Continued) C-40 Value Call Disconnection Cause 153 H323 call close. DRQ timeout 154 H323 call close. Alt Gatekeeper failure 191 H323 call close. Remote busy 192 H323 call close. Normal 193 H323 call close. Remote reject 194 H323 call close. Remote unreachable 195 H323 call close. Unknown reason 198 H323 call close. Small bandwidth 199 H323 call close.
PAGE 839
Appendix C-CDR Fields - Unformatted File Table C-40 Disconnection Cause Values (Continued) Polycom, Inc.
PAGE 840
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table C-40 Disconnection Cause Values (Continued) Value Call Disconnection Cause 500 SIP server error 500 501 SIP server error 501 502 SIP server error 502 503 SIP server error 503 504 SIP server error 504 505 SIP server error 505 600 SIP busy everywhere 603 SIP global failure 603 604 SIP global failure 604 606 SIP global failure 606 MGC Manager Events that are not Supported by the MCU The following M
PAGE 841
Appendix D Ad Hoc Conferencing and External Database Authentication The RealPresence Collaboration Server (RMX) Ad Hoc conferencing feature enables participants to start ongoing conferences on-the-fly, without prior definition when dialing an Ad Hoc-enabled Entry Queue. The created conference parameters are taken from the Profile assigned to the Ad Hoc-enabled Entry Queue.
PAGE 842
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 4 The MCU checks whether a conference with the same Conference ID is running on the MCU. If there is such a conference, the participant is moved to that conference. If there is no ongoing conference with that Conference ID, the system creates a new conference, based on the Profile assigned to the Entry Queue, and connects this participant as the conference chairperson.
PAGE 843
Appendix D-Ad Hoc Conferencing and External Database Authentication Entry Queue Level - Conference Initiation Validation with an External Database Application Starting a new conference with external database application validation entails the following steps: IP Endpoint MCU 92 51 00 0 IP Endpoint MCU Prefix in Gatekeeper - 925 925DefaultEQ Network 1001 1200 On Going Conference with this ID? 1300 9 00 10 25 Name: DefaultEQ Numeric ID: 1000 IP Endpoint New Conference ID: 1300 Figure D-2 Confere
PAGE 844
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide — Conference Information, such as the contact person name. These fields correspond to Info 1, 2 and 3 fields in the Conference Properties - Information dialog box. — Maximum number of participants allowed for the conference — Conference Owner These parameters can also be defined in the conference Profile. In such a case, parameters sent from the database overwrite the parameters defined in the Profile.
PAGE 845
Appendix D-Ad Hoc Conferencing and External Database Authentication Conference access authentication can be performed as: • Part of the Ad Hoc conferencing flow where the participants must be authorized before they can enter the conference created in the Ad Hoc flow • Independent of Ad Hoc conferencing where conference access is validated for all conferences running on the MCU regardless of the method in which the conference was started.
PAGE 846
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • • If the Conference IVR Service is configured to prompt for the chairperson identifier and password, the participant is requested to enter the chairperson identifier. — If no identifier is entered, the participant connects as a standard, undefined participant. If the chairperson identifier is entered, the participant is requested to enter the chairperson password.
PAGE 847
Appendix D-Ad Hoc Conferencing and External Database Authentication • • • • • If the Conference IVR Service is configured to prompt for the Conference password, the participant is requested to enter the conference password. In this flow, the conference password is not validated with the external database application, only with the MCU. — If the wrong password is entered, he/she is disconnected from the conference.
PAGE 848
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • Ad Hoc - enabled Entry Queue Ad Hoc conferencing must be enabled in the Entry Queue and a Profile must be assigned to the Entry Queue. In addition, an Entry Queue IVR Service supporting conference ID request. For details, see "Entry Queues” on page 7-1.
PAGE 849
Appendix D-Ad Hoc Conferencing and External Database Authentication MCU Configuration to Communicate with an External Database Application To enable the communication with the external database application, several flags must be set in the System Configuration. To set the System Configuration flags: 1 On the Setup menu, click System Configuration. The System Flags dialog box opens. 2 Modify the values of the following flags: Table D-1 Flag Values for Accessing External Database Application Polycom, Inc.
PAGE 850
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Enabling External Database Validation for Starting New Ongoing Conferences The validation of the participant’s right to start a new conference with an external database application is configured in the Entry Queue IVR Service - Global dialog box. >> Set the External Server Authentication field to Numeric ID.
PAGE 851
Appendix E Participant Properties Advanced Channel Information The following appendix details the properties connected with information about audio and video parameters, as well as, problems with the network which can affect the audio and video quality. Table E-1 Participant Properties - Channel Status Advanced Parameters Field Description Media Info Polycom, Inc. Algorithm Indicates the audio or video algorithm and protocol.
PAGE 852
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table E-1 Participant Properties - Channel Status Advanced Parameters Field Description RTP Statistics Actual loss Out of Order E-2 The number of missing packets counted by the IP card as reported in the last RTP Statistics report. If a packet that was considered lost arrives later, it is deducted from the packet loss count.
PAGE 853
Appendix E-Participant Properties Advanced Channel Information Table E-1 Participant Properties - Channel Status Advanced Parameters Polycom, Inc. Field Description Fragmented Indicates the number of packets that arrived to the IP card fragmented (i.e., a single packet broken by the network into multiple packets). This value can indicate the delay and reordering of fragmented packets that require additional processing, but is not considered a fault.
PAGE 854
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide E-4 Polycom, Inc.
PAGE 855
Appendix F Secure Communication Mode The RealPresence Collaboration Server (RMX) can be configured to work in Secure Mode by configuring the MCU and the RealPresence Collaboration Server (RMX) Web Client to work with SSL/TLS. In this mode, a SSL/TLS Certificate is installed on the MCU, setting the MCU Listening Port to secured port 443. TLS is a cryptographic protocol used to ensure secure communications on public networks.
PAGE 856
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide — Client Authentication — Server Authentication The certificate template used by your CA server may need modification to meet the RMX requirements. Certificate Requirements for Polycom Devices Each Polycom device must have security certificates for the entire Chain Of Trust. The RMX must have: • The public certificate of each server in the CA Chain or hierarchy that issued its certificate.
PAGE 857
Appendix F-Secure Communication Mode The Create Certificate Request dialog box is displayed. 2 Enter information in all the following fields: Table F-2 Create Certificate Request 3 Polycom, Inc. Field Description Country Name Enter any 2 letter code for the country name. State or Province Enter the full name of the state or province. Locality Enter the full name of the town/city/location. Organization Enter the full name of your organization for which the certificate will be issued.
PAGE 858
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The MCU creates a New Certificate Request and returns it to the Create Certificate Request dialog box along with the information the user submitted. 4 Click Copy Request to copy the New Certificate Request to the workstation’s clipboard. 5 Connect to your preferred Certificate Authority’s website using the web browser. 6 Follow the purchasing instructions at the Certificate Authority’s website.
PAGE 859
Appendix F-Secure Communication Mode 4 Click the Send Certificate button to send the certificate to the MCU. The MCU validates the certificate. — If the certificate is not valid, an error message is displayed. — If the certificate matches the private key, and the task is completed, a confirmation message indicating that the certificate was created successfully is displayed. A System Restart is not required at this point. The certificate expiry date is checked daily.
PAGE 860
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • A secure communication indicator ( ) is displayed in the browser’s status bar. To enable secure communications mode: 1 In the RMX Management pane, click IP Network Services. 2 In the IP Network Services list pane, double-click the Management Network entry. 3 Click the Security tab. The Management Security Properties dialog box is displayed. 4 Select the Secured Communication check box. 5 Click OK.
PAGE 861
Appendix F-Secure Communication Mode Ultra Secure Mode ULTRA_SECURE_MODE System Flag The Ultra Secure Mode is enabled or disabled depending on the value of the ULTRA_SECURE_MODE System Flag. WARNING: Once Ultra Secure Mode is enabled it can only be undone by performing a Restore to Factory Defaults. Also, to implement a Maximum Security environment, other Polycom products on the network must be similarly configured. For more information see "Restoring Defaults” on page J-1.
PAGE 862
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide It is important to verify that the external database application is operating in secure mode before enabling secure external database communications on the MCU. The MCU checks the validity of external database’s certificate before communicating. If there is a certificate error an Active Alarm is raised with Error in external database certificate in the description field.
PAGE 863
Appendix F-Secure Communication Mode Offline Certificate Validation Offline Certificate Validation has been enhanced to include the following rules and procedures: Peer Certificates The diagram below illustrates the peer certificate validation procedure. • The credentials of each certificate received from a networked peer are verified against a repository of trusted certificates. (Each networked entity contains a repository of trusted certificates.
PAGE 864
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • The date of the MCU’s certificate is checked for validity during power-up and when connecting to management applications (RealPresence Collaboration Server Web Client and RMX Manager). Certificate Revocation List • Each certificate received from a networked peer is verified against a repository of revoked certificates. (Each networked entity contains a repository of revoked certificates.
PAGE 865
Appendix F-Secure Communication Mode 4 Clear the Skip certificate validation for user logging session check box. 5 Click the OK button. Default IP Network Service The steps needed to add a certificate to the Default IP Network Service are described in the RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide,"Modifying the Default IP Network Service” on page 16-11. Polycom, Inc.
PAGE 866
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Managing Certificates in the Certification Repository A Certification Repository dialog box has been added to enable the administrator to add remove and monitor certificates on the MCU. It is accessed via the RealPresence Collaboration Server Web Client / RMX Manager, Setup menu.
PAGE 867
Appendix F-Secure Communication Mode Double-clicking on a certificate in any if the displayed lists, displays the certificate’s properties: Adding Trusted Certificates and CRLs to the Certification Repository Trusted Certificates and CRLs added to the Certification Repository are not automatically activated. They remain in the Trusted Certificates and CRL Lists until the Activate Certificate button is clicked, at which time all Trusted Certificates and CRLs in the list are activated simultaneously.
PAGE 868
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The Send Certificate dialog box is displayed. 2 Send the certificate to the MCU. Two options are available for sending the certificate to the MCU: — Paste Certificate and Send Certificate Use this option if the certificate has been received from the Certification Authority in text format. — Send Certificate File Use this option if the certificate has been received from the Certification Authority in file format. Option.
PAGE 869
Appendix F-Secure Communication Mode Option. Send Certificate File After you have received the certificate file from the Certificate Authority: a Click Send Certificate File. The Install File dialog box is displayed. File Types b Select the Certificate File Format: PEM, DER, PKCS#7/P7B or PKCS#12PFX. c Enter the certificate file name in the Install File field or click the Browse button. The Open file dialog box is displayed. The files are filtered according to the file type selected in Step b.
PAGE 870
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Personal Certificates (Management and Signaling Certificates) Default Management and Default IP Network Service certificates can be viewed in the Personal Certificates tab. They are listed alongside the service to which they are attached.
PAGE 871
Appendix F-Secure Communication Mode Adding a CRL To add a CRL to the repository: Repeat steps 1 - 7 for each CRL that is to be added to the Certification Repository. 1 In the CRL List tab, click the Add button. 2 The Install File dialog box is displayed. File Types 3 Select the Certificate File Format: PEM or DER. 4 Enter the certificate file name in the Install File field or click the Browse button. 5 The Open file dialog box is displayed.
PAGE 872
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide When the Activate Certificate button is clicked, all added Trusted Certificates and CRLs are installed and the MCU displays an RealPresence Collaboration Server Web Client/RMX Manager disconnection confirmation dialog box. 9 Click the OK button. 10 Login to the MCU to proceed with further management tasks Removing a CRL To remove a CRL: 1 In the certificate list, select the CRL List to be removed.
PAGE 873
Appendix F-Secure Communication Mode Directory and Database Options Ultra Secure Mode Internal MCU database and Active Directory Authentication is first attempted using the internal MCU database. If it is not successful authentication is attempted using the Active Directory. Standard Security Mode Internal MCU database + External Database First authentication is via the internal MCU database. If it is not successful, authentication is via the External Database.
PAGE 874
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • In Standard Security Mode multiple accounts of all user types are supported. In Ultra Secure Mode, enabling Active Directory integration is only permitted if the MCU only has one local Administrator User. • Multiple Machine Accounts with various roles are supported. • Microsoft Active Directory is the only directory service supported. • Active Directory integration is configured as part of the Management Network.
PAGE 875
Appendix F-Secure Communication Mode Table F-4 Directory Services - Configuration (Continued) 3 Field Description Search Base DN Enter the starting point when searching for User and Group information in the Active Directory. For example if the Domain Name is: mainoffice.bigcorp.com.uk The entry in this field should be: CN=Users,DC=mainoffice,DC=bigcorp,DC=come,DC=uk Authentication Type Only NTLM can be used. Click the Role Mapping tab. The Directory Services - Role Mapping dialog box is displayed.
PAGE 876
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Restoring the RealPresence® Collaboration Server (RMX®) 1500/2000/4000 Using the USB Port When the RMX is in Ultra Secure Mode, the Restoring the RealPresence® Collaboration Server Using the USB Port procedure can be used to set the RMX back to its factory default settings, if for any combination of factors the system becomes unstable or unmanageable. For more information see "Ultra Secure Mode” on page F-7.
PAGE 877
Appendix G Configuring Direct Connections to RealPresence Collaboration Server (RMX) Direct connection to the RealPresence Collaboration Server (RMX) is necessary if you want to: • Modify the MCU’s Factory Default Management Network settings without using the USB key. • Connect to the MCU’s Alternate Management Network for support purposes. • Connect to the MCU via a modem. Direct connections to the MCU are not supported when the MCU is in Ultra Secure Mode.
PAGE 878
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Once logged in, the RealPresence Collaboration Server Web Client behaves as if the administrator had logged in on the Management Network. Connection to the Alternate Management Network bypasses LAN and Firewall security. Strict control of access to LAN 3 port is recommended. The Alternate Management Network is only available if Network Separation has not been performed.
PAGE 879
Appendix G-Configuring Direct Connections to RealPresence Collaboration Server (RMX) 3 In the Local Area Connection Status dialog box, click the Properties button. 4 In the Local Area Connection Properties dialog box, select Internet Protocol [TCP/IP] > Properties. 5 In the Internet Protocol (TCP/IP) Properties dialog box, select Use the following IP address. 6 Enter the IP address, Subnet mask and Default gateway for the workstation.
PAGE 880
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Example: IP address – near 192.168.1.nn None of the reserved IP addresses listed in Table G-1 should be used for the IP Address. The Subnet mask and Default gateway addresses should be the same as those for the MCU’s Management Network. The addresses needed for connection to either the MCU’s Default Management Network or Alternate Management Network are listed in Table G-1.
PAGE 881
Appendix G-Configuring Direct Connections to RealPresence Collaboration Server (RMX) The Fast Configuration Wizard starts.
PAGE 882
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Connecting to the Alternate Management Network Access to the Alternate Management Network is via a cable connected to a workstation. The Alternate Management Network is accessible only via the dedicated LAN 3 port. LAN 3 Port To connect to the Alternate Management Network: 1 Connect the cable between the MCU’s LAN 3 port and the LAN port configured on the workstation.
PAGE 883
Appendix G-Configuring Direct Connections to RealPresence Collaboration Server (RMX) Connecting to the MCU via Modem Remote access to the MCU’s Alternate Management Network is supported via an external PSTN <=> IP modem. To connect via modem to the Alternate Management Network the following procedures must be performed: 1 Procedure 1: Install the RMX Manager – the web client enables direct access to the MCU for support purposes.
PAGE 884
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Procedure 3: Create a Dial-up Connection To create a dial-up connection: This procedure is performed once. Only the Dial field in the Connect applet (see step 10 on page G-11) is modified for connection to different modems. G-8 1 In Windows, navigate via the Control Panel to the Network Connections applet and select Create a new connection. 2 When the New Connection Wizard is displayed, click the Next button.
PAGE 885
Appendix G-Configuring Direct Connections to RealPresence Collaboration Server (RMX) Polycom, Inc. 4 In the Getting Ready box, select Set up my connection manually and click the Next button. 5 In the Internet Connection box, select Connect using dial-up modem and click the Next button. 6 In the Connection Name box, enter a Name for the modem connection (e.g. Modem Connection) and click the Next button.
PAGE 886
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide G-10 7 In the Phone Number to Dial box, enter the Phone Number for the modem and click the Next button. 8 In the Connection Availability box, select Anyone’s use and click the Next button. 9 In the Internet Account Information box, complete the Username, Password and Confirm Password fields and click the Next button. Polycom, Inc.
PAGE 887
Appendix G-Configuring Direct Connections to RealPresence Collaboration Server (RMX) 10 The Connection applet is displayed with the field values filled in as specified by the New Connection Wizard. 11 Click the Dial button to establish a connection to LAN 3 Port via the modem. The Windows – Network Connections applet displays Connected status for the new connection. Polycom, Inc.
PAGE 888
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Procedure 4: Connect to the MCU To Connect using the RMX Manager: To use the browser: 4 In the browser’s command line, enter http:/// RmxManager.html and press Enter. To use the Windows Start menu: 1 Click Start. a If the MCU Manager is displayed in the recently used programs list, click RMX Manager in the list to start the application. or b Click All Programs.
PAGE 889
Appendix H Setting the MCU for Integration Into Microsoft Environment Integration into Microsoft environment (using Lync endpoints) is supported in AVC Conferencing Mode only. Overview The Polycom® Visual Communications offers high quality video and audio multipoint conferencing by integrating the Polycom network devices and endpoints into Microsoft® platforms.
PAGE 890
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide TLS certificates can be generated using the following methods: CSR, PFX and PEM; each giving different options for Encryption Key length. Table H-1 lists the SIP TLS Encryption Key length support for the various system components.
PAGE 891
Appendix H-Setting the MCU for Integration Into Microsoft Environment Figure H-1 MCU Multiple Networks Topology ICE is supported with this configuration from Version 7.8 onward. One Network Service including ICE can be configured per media card installed in the MCU as shown in Table H-2.
PAGE 892
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Interactive Connectivity Establishment (ICE) Interactive Connectivity Establishment (ICE) provides a structure/protocol to unify the various NAT Traversal techniques that are used to cross firewalls. It enables SIP based endpoints to connect while traversing a variety of firewalls that may exist between the calling endpoint (local) and the MCU or called endpoint (remote).
PAGE 893
Appendix H-Setting the MCU for Integration Into Microsoft Environment Remote - a connection between MCU that resides within the organization and an endpoint that resides outside of the organization (on a WAN). For example, an endpoint on the internet that calls the MCU in Zone A. In such a case, the call has to traverse at least one firewall. Federation - a connection between MCU that resides within one organization and an endpoint that resides within another organization.
PAGE 894
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Integrating the MCU into the Microsoft Office Communications Server Environment From Version 7.0.x, Microsoft R1 is not supported with MCU systems. When the MCU is integrated into the Office Communications Server environment, calls to conferences running on the MCU can be routed using Matched URI dialing and/or Numerical dialing.
PAGE 895
Appendix H-Setting the MCU for Integration Into Microsoft Environment For example, if company B wants to set up federation with company A and receive and send SIP calls that will be handled by the Polycom SIP signaling domain in company A, you need to add the FQDN of the company A Office Communications Server domain as well as the SIP signaling domain of company A to the list of Internal SIP Server domains supported by the company B Office Communications Server environment.
PAGE 896
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 3 Right-click the server pool icon, click Properties > Front End Properties. The Pool Front End Properties dialog box opens. 4 H-8 Click the Host Authorization tab. Polycom, Inc.
PAGE 897
Appendix H-Setting the MCU for Integration Into Microsoft Environment 5 Click the Add button to add the MCU as trusted host. The Add Authorized Host dialog box opens. 6 In the Add Authorized Host dialog box, enter the MCU FQDN name as defined in the DNS and will be used in the Static Routes definition. 7 In the Settings section, select the Throttle as Server and Treat As Authenticated check boxes. 8 Click OK.
PAGE 898
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 11 In the Matching URI section, enter the Domain name for the MCU. Any domain name can be used. 12 In the Next hop section enter the MCU FQDN name as defined in the DNS and is used in the Host Authorization definition. 13 In the Transport field, select TLS to enable the dial-out from conferences to SIP endpoints. 14 Click OK. The new Route is added to the list of routes in the Front End Properties—Routes dialog box.
PAGE 899
Appendix H-Setting the MCU for Integration Into Microsoft Environment 3 Right-click the Load icon, click Properties > Front End Properties. The Load Front End Properties dialog box opens. The definition procedure is the same as for setting the MCU as trusted and define Static routes in the OCS. For details, see “Setting the Trusted Host for MCU in the Office Communications Server” on page 7. Make sure that when defining the Static Route it is pointing to the OCS pool and not to the MCU directly.
PAGE 900
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Dialing to an Entry Queue, Meeting Room or Conference Using the Matched URI Method Once the MCU is configured for integration in the OCS environment (for details, see "Configuring the RMX 1500/2000/4000 for Microsoft Integration” on page H-36), the preferred dialing mode to the conferencing entities such as Meeting Rooms, conferences and Entry Queues is direct dial in using the domain name defined in the OCS Static Routes.
PAGE 901
Appendix H-Setting the MCU for Integration Into Microsoft Environment • Establishing a Voice Route to the MCU “Voice” Gateway - The Voice Route to the MCU (or DMA) must be configured in the OCS infrastructure. If the MCU was previously defined as a Trusted Host for matching URI dialing method, this definition must be removed before configuring the MCU as a voice gateway. It will be defined as trusted host as part of the voice gateway configuration. For more details, see Optional.
PAGE 902
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 3 In the Trusted Hosts list, click the MCU entry and then click the Remove button. 4 Click OK. Configuring the MCU as a Routable Gateway The MCU must be set as a routable voice gateway in the Office Communications Server infrastructure. This does not restrict the MCU to just voice operation, rather it means that the MCU can be set as a destination for a voice route in the Office Communications Server infrastructure.
PAGE 903
Appendix H-Setting the MCU for Integration Into Microsoft Environment 3 Run the following command: cscript OCSTrustEntry.vbs /action:add /type:trustedservice / fqdn: /service:MediationServer /port:5061 /version:4 /routable:TRUE Where is the FQDN of your MCU system. The script automatically generates the GUID discover the proper Active Directory container to store the object.
PAGE 904
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The Office Communications Server Voice Properties dialog box opens. 2 Click the Routes tab. Office Communications Server Voice Properties - Routes dialog box opens. 3 Click the Add button. The Add Route dialog box opens. 4 In the Name field, enter a name that will identify this voice route. 5 Optional. In the Description field, enter a description.
PAGE 905
Appendix H-Setting the MCU for Integration Into Microsoft Environment If you have not defined such a prefix in the IP Network Service in the MCU configuration, you can add it later, using value entered here. 7 In the Gateways - Addresses box, click the Add button. The Add Route Gateway dialog box opens. 8 Select the MCU gateway address that was set up in Configuring the MCU as a Routable Gateway that appears in the drop down list of gateways.
PAGE 906
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Configuring Office Communicator Users for Enterprise Voice Each of the endpoints in the OCS environment must be set to use the voice route. The setting is done in the Office Communications Server management console for all required users (endpoints) simultaneously or in the Active Directory for each of the Users (endpoints).
PAGE 907
Appendix H-Setting the MCU for Integration Into Microsoft Environment 10 On the Configure Enterprise Voice Settings and Location Profile dialog box, select Change Enterprise Voice Policy for selected users. 11 Select an Enterprise Voice policy from the list. 12 Select Change location profile for selected users. 13 Select a location profile from the list, and then click Next. 14 On the Ready to Configure Users dialog box, review the settings, and then click Next.
PAGE 908
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide To Configure Office Communicator Users for Enterprise Voice in the in the Active Directory: 1 Open the Active Directory and navigate to the endpoint whose properties require changing. H-20 2 Right-click the endpoint and select Properties. The Properties dialog box opens. 3 Click the Communications tab. 4 Click the Telephony Settings - Configure button. The Telephony Options dialog box opens.
PAGE 909
Appendix H-Setting the MCU for Integration Into Microsoft Environment Starting a Conferencing Call from the MOC 1 In the Office Communicator application, enter the number to dial, for example, 113344. This number is composed of the MCU Prefix in the Gatekeeper (for example, 11) and the Meeting Room ID, as defined on the MCU (for example, 3344). 2 Click Call, and then click Other.
PAGE 910
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide PFX Method - Creating the Security (TLS) Certificate in the OCS and Exporting the Certificate to the MCU Workstation If you are using the PFX method to create and send the security certificate to the MCU, certificate files rootCA.pem, pkey.pem and cert.pem must be sent to the MCU unit. These files can be created and sent to the MCU in two methods: • The files rootCA.pem, pkey.pem and cert.
PAGE 911
Appendix H-Setting the MCU for Integration Into Microsoft Environment 4 Select Create a New Certificate and click Next. The Delayed or Immediate Request window appears. 5 Select Send the Request immediately to an online certificate authority and click Next. The Name and Security Settings window appears. Polycom, Inc.
PAGE 912
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 6 In the Name field, select the MCU name you entered in the FQDN field when defining the trusted host or as defined in the DNS server. 7 Select the Mark cert as exportable check box. 8 Click Next. The Organization Information window appears. 9 Enter the name of the Organization and the Organization Unit and click Next. Your Server’s Subject Name window appears. H-24 Polycom, Inc.
PAGE 913
Appendix H-Setting the MCU for Integration Into Microsoft Environment 10 In the Subject name field, select the FQDN name of the MCU from the list or enter its name. Keep the default selection in the Subject alternate name field and click Next. 11 If an error message is displayed, click Yes to continue. The Geographical Information window appears. 12 Enter the geographical information as required and click Next. The Choose a Certification Authority window appears. Polycom, Inc.
PAGE 914
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 13 Ensure that the Select a certificate authority from the list detected in your environment option is selected and that the local OCS front end entity is selected. 14 Click Next. The Request Summary window appears. 15 Click Next to confirm the listed parameters and create the requested certificate. The Assign Certificate Task window appears. H-26 Polycom, Inc.
PAGE 915
Appendix H-Setting the MCU for Integration Into Microsoft Environment 16 Select Assign certificate later and click Next (MS R2). The Certificate Wizard Completed window appears (MS R2). 17 Click Finish (MS R2). Retrieving the Certificate from the OCS to be sent to the MCU Workstation 1 In the OCS Enterprise Pools tree, expand the Pools list and the Server Pool list. 2 Right-click the pool Front End entity, and select Certificate. The Available Certificate Tasks window appears.
PAGE 916
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 4 Select the certificate Subject Name of the MCU and click Next. The Export Certificate window appears. 5 Enter the path and file name of the certificate file to be exported or click the Browse button to select the path from the list. The new file type must be *.pfx and its name must include the .pfx extension. 6 Select the Include all certificates in the certification path if possible check box and then click Next.
PAGE 917
Appendix H-Setting the MCU for Integration Into Microsoft Environment 7 If required, enter any password. For example, Polycom. Write down this password as you will have to manually create a password file in which this password will appear. Click Next. The Certificate Wizard Completed window appears. 8 Click Finish. The created *.pfx file is added in the selected folder. Optional. Creating the Certificate Password File (certPassword.txt) If you have used a password when creating the certificate file (*.
PAGE 918
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Supporting Remote and Federated Users in Office Communications Server ICE Environment To enable the remote and Federation connections the following operations must be performed: • Create an Active Directory account for the MCU that will be used for registering and operating in the MS ICE environment • Enable the MCU User Account for Office Communication Server • Configure the MCU for ICE dialing for more details, see
PAGE 919
Appendix H-Setting the MCU for Integration Into Microsoft Environment 3 In the New User wizard, define the following parameters: Table H-4 Active Directory - New User Parameters for the MCU Polycom, Inc. Field Description First Name Enter the name for the MCU user. This name will be used in the configuration of the ICE environment in the MCU. Full Name Enter the same name as entered in the First Name field.
PAGE 920
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 7 Click Next. The system displays summary information. 8 Click Finish. The new User is added to the Active Directory Users list. Enabling the MCU User Account for Office Communication Server The new MCU user must be enabled for registration with the Office Communications Server.
PAGE 921
Appendix H-Setting the MCU for Integration Into Microsoft Environment 3 In the Sign in name field, enter the MCU user name in the format SIP:rmx user name (for example sip:rmx1234) and select the domain name (for example, ilsnd.vsg.local) as entered in the New User dialog box. 4 Select the Server or Pool from the list. 5 Click Apply and then OK. Configure the MCU for ICE dialing For details, see "Configuring the MCU for Federated (ICE) Dialing” on page H-63. Polycom, Inc.
PAGE 922
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide MCU Integration into the Microsoft Lync Server 2010 and Lync Server 2013 Environments From Version 7.8, the RMX interoperability level with Lync 2013 is identical to Lync 2010. Lync 2013 is backward compatible with all RMX Lync 2010 features. From Version 7.1, MCU systems can be integrated into the Microsoft Lync Server 2010 (Wave 14) environment.
PAGE 923
Appendix H-Setting the MCU for Integration Into Microsoft Environment FEC Support Microsoft RTV FEC (Forward Error Correction) is supported in the MCU to control and correct packet loss when receiving and sending video streams using the Microsoft Lync Server 2010 communications software. All RTV resolutions and options, including B Frame, are supported. Redundant video packets are sent over the network during video stream transmission.
PAGE 924
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Configuring the RMX 1500/2000/4000 for Microsoft Integration The MCU is integrated in Microsoft Office Communications Server R2 (Wave 13) and Microsoft Lync Server environments by setting its Transport Type (in the SIP server configuration) to TLS and creating a certificate that is sent to the MCU. This procedure is also required when encryption of SIP signaling is used. From Version 7.0.
PAGE 925
Appendix H-Setting the MCU for Integration Into Microsoft Environment 6 View or modify the following fields: Table 9 Management Network Properties – DNS Parameters Field Description MCU Host Name Enter the name of the MCU on the network. This name must be identical to the FQDN name defined for the MCU in the OCS and DNS. Default name is MCU. Shelf Management Host Name Displays the name of the entity that manages the MCU hardware. The name is derived from the MCU host name. Default is RMX_SHM.
PAGE 926
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The CSR Method In the CSR method, the security certificate is created as part of the SIP Server configuration in the IP Network Service configuration. Using the CSR Method, the following processes are performed: • Creating the certificate request (in the Default IP Network Service - SIP Server dialog box). • Sending the certificate request to a Certificate Authority.
PAGE 927
Appendix H-Setting the MCU for Integration Into Microsoft Environment The Default IP Service - Networking IP dialog box opens. 4 Make sure the IP Network Type is set to H.323 & SIP even though SIP will be the only call setup used with Office Communications Server 2007.
PAGE 928
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 6 Click the SIP Servers tab. 7 In the SIP Server, select Specify. 8 In the SIP Server Type, select Microsoft. 9 Enter the IP address of the Office Communications Server 2007 or Lync Server 2010 and the Server Domain Name as defined in the OCS/Lync Server and in the Management Network for the DNS. 10 If not selected by default, change the Transport Type to TLS.
PAGE 929
Appendix H-Setting the MCU for Integration Into Microsoft Environment CSR Method - Creating the Certificate 12 Click the Create Certificate button. The Create Certificate Request dialog box is displayed. 13 Enter information in all the following fields: Table H-1 Create Certificate Request Field Description Country Name Enter any 2 letter code for the country name. State or Province Enter the full name of the state or province. Locality Enter the full name of the town/city/location.
PAGE 930
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide The MCU creates a New Certificate Request and returns it to the Create Certificate Request dialog box along with the information the user submitted. 15 Click Copy Request to copy the New Certificate Request to the workstation’s clipboard. 16 Connect to your preferred Certificate Authority’s website using the web browser. 17 Follow the purchasing instructions at the Certificate Authority’s website.
PAGE 931
Appendix H-Setting the MCU for Integration Into Microsoft Environment CSR Method - Sending the certificate After you have received the certificate from the Certificate Authority: If you have closed the IP Network Service - SIP Servers dialog box, repeat steps 1 to 11 in the procedure "Defining a SIP Network Service in the MCU and Installing the Security Certificate” on page H-37.
PAGE 932
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide — If the certificate matches the private key, and the task is completed, a confirmation message indicating that the certificate was created successfully is displayed. Once the certificate is installed in the MCU you can complete the definition procedure or continue with the MCU configuration for ICE dialing. For details, see "Configuring the MCU for Federated (ICE) Dialing” on page H-63.
PAGE 933
Appendix H-Setting the MCU for Integration Into Microsoft Environment 28 Click the Browse button. The Open dialog box appears, letting you select the certificate file(s) to send to the MCU. Depending on the method used when the certificate file(s) were created, send the certificate file(s) to the MCU according to the contents of the file set that was created: — The certificate files pkey.pem, cert.pem and a certPassword.txt.
PAGE 934
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 33 In the Reset Confirmation dialog box, click No to modify the required system flags before resetting the MCU, or click Yes if the flag was already set. Reset can be performed after setting the system flags (for example, setting the MS_ENVIRONMENT flag). After system reset the MCU can register to the OCS server and make SIP calls. Sometimes the system fails to read the *.
PAGE 935
Appendix H-Setting the MCU for Integration Into Microsoft Environment In some configurations, the following flags may require modifications when MS_ENVIRONMENT flag is set to YES: Table H-2 Additional Microsoft Environment Flags in the MCU MCMS_PARAMETERS_USER Tab Flag Name Value and Description SIP_FREE_VIDEO_RESOURCES Default value in Microsoft environment: NO.
PAGE 936
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • G711A/U or G722 – Set this flag value according to the hosting workstation capabilities. If the MCU detects single core host during capabilities exchange it will assign a G.711 or G.722 Audio algorithm according to the flag value.
PAGE 937
Appendix H-Setting the MCU for Integration Into Microsoft Environment Table H-3 Selected video resolution based on flag setting and conference line rate and core processor (Continued) Selected Video Resolution Per Core Processor Maximum Resolution Value Line Rate VGA CIF QCIF Quad Dual Single > 600 kbps VGA 30fps VGA 30fps VGA 15fps 250 kbps - 600 kbps VGA 30fps VGA 30fps VGA 15fps 180 kbps - 249 kbps CIF CIF CIF 64 kbps - 179 kbps QCIF QCIF QCIF > 600 kbps CIF CIF CIF 250 kbp
PAGE 938
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide HD Frame Rate Flag Settings using the RTV Video Protocol The system flag MAX_ALLOWED_RTV_HD_FRAME_RATE defines the threshold Frame Rate (fps) in which RTV Video Protocol initiates HD resolutions. Flag values are as follows: • Default: 0 (fps) - Implements any Frame Rate based on Lync RTV Client capabilities If the MAX_RTV_RESOLUTION flag is set to AUTO dual core systems always view VGA.
PAGE 939
Appendix H-Setting the MCU for Integration Into Microsoft Environment Adding Presence to Conferencing Entities in the Buddy List Registration of conferencing entities (Meeting Rooms, Entry Queues and SIP Factories) with the SIP server adds these conferencing entities to the buddy list with their presence.
PAGE 940
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • In Multiple Networks configuration, an IP Network Service that is enabled for registration in a Conference Profile cannot be deleted. • Upgrading from previous versions to version 7.1 and later requires manual update of the registration in the Conference Profiles that are assigned to the conferencing entities.
PAGE 941
Appendix H-Setting the MCU for Integration Into Microsoft Environment 3 In the New User wizard, define the following parameters: Table H-5 Active Directory - New User Parameters for the MCU Field Description First Name Enter the name of the conferencing entity user. This name will appear in the buddy list of the Office Communication Server or Lync server. For example, vmr10. Notes: • This name must be the identical to the Routing Name assigned to the conferencing entity in the MCU system.
PAGE 942
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Enabling the Conferencing Entity User Account for Office Communication Server or Lync Server The new Conferencing Entity user must be enabled for registration with the Office Communications Server or Lync Server. To enable the Conferencing Entity User Account for Office Communication Server: 1 In the Active Directory Users and Computers window, right-click the conferencing entity user and then click Properties.
PAGE 943
Appendix H-Setting the MCU for Integration Into Microsoft Environment 8 Select the following parameters: — In Assign users to a pool field, select the required pool. — In the Generate user SIP URI, define the SIP URI of the conferencing entity using one of the following methods: • Select the Specify a SIP URI option and enter the conferencing entity user portion of SIP URI defined in the active directory. This SIP URI must match the conferencing entity Routing Name configured in MCU.
PAGE 944
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Selective registration is enabled by assigning a conference Profile in which registration is enabled to the conferencing entities that require registration. Assigning a conference Profile in which registration is disabled (registration check box is cleared) to conferencing entities will prevent them from registering.
PAGE 945
Appendix H-Setting the MCU for Integration Into Microsoft Environment Verifying the MCU Conferencing Entity Routing Name and Profile MCU conferencing entity can be dialed directly from the buddy list of the Office Communications client or the Lync client if its routing name matches the user name of Active Directory account you created and Registration is enabled in the Conference Profile assigned to it.
PAGE 946
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide the SIP server may be down, or any other reason the affects the connection between the MCU or the SIP Server to the network. • Registered - the conferencing entity is registered with the SIP Server.
PAGE 947
Appendix H-Setting the MCU for Integration Into Microsoft Environment Conferencing Entity Properties Registration status is reflected in the Properties - Network Services dialog box: Figure H-7 Ongoing conference Properties - Network Services - SIP Registration Figure H-8 Meeting Room Properties - Network Services - SIP Registration Figure H-9 Entry Queue Properties - Network Services - SIP Registration Polycom, Inc.
PAGE 948
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide MCU Configuration for CAC Implementation Enabling CAC Implementation CAC is enabled by manually adding the flags to the system Configuration and setting their values as follows: • • To enable the Call Admission Control implementation in the MCU: — CAC_ENABLE=YES In addition, to ensure that endpoints such as HDX remain connected to the conference for its duration when the RMX is configured with FQDN address and the Lync se
PAGE 949
Appendix H-Setting the MCU for Integration Into Microsoft Environment For example, if a participant with a line rate of 900Kbps connects to the conference to which all other participants are connected at a line rate of 1024kbps, the line rate of all participants will decrease to 900Kbps. When this participant disconnects, the line rate of the remaining participants will increase to 1024Kbps.
PAGE 950
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Connecting an MCU Meeting Room to a Microsoft AV-MCU Conference Microsoft Lync users can connect an MCU Meeting Room to a conference running on the Microsoft A/V MCU. This allows MCU Lync users to connect with a conference in progress on the A/V MCU and be an active participant in the conference. The connection to the A/V MCU is the same configuration as a cascading conference between multiple MCU MCUs.
PAGE 951
Appendix H-Setting the MCU for Integration Into Microsoft Environment Configuring the MCU for Federated (ICE) Dialing The MCU Default IP Network Service must be configured to work with the Office Communication Server/Lync Server as the SIP Server and the MCU user defined in the Active Directory must also be defined in the MCU ICE environment parameters to enable remote dialing in a federated (ICE) environment, .
PAGE 952
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 7 Click the SIP Advanced tab. 8 In the ICE Environment field, select MS (for Microsoft ICE implementation) to enable the ICE integration. This field is disabled if the MCU is running in MPM Card Configuration Mode. 9 In the Server User Name field, enter the MCU User name as defined in the Active Directory. For example, enter rmx111. This field is disabled if the ICE Environment field is set to None.
PAGE 953
Appendix H-Setting the MCU for Integration Into Microsoft Environment Monitoring the Connection to the STUN and Relay Servers in the ICE Environment 1 In the MCU Web browser, in the MCU Management pane, click Signaling Monitor. 2 In the Signaling Monitor pane, click the IP Network Service entry. 3 Click the ICE Servers tab. The system lists the ICE servers to which it is connected and the status of the connection of each of the MCU media cards (status 1, status 2, etc) to ICE servers.
PAGE 954
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 2 Click the Channel Status - Advanced tab. The following connection information is displayed: Table H-8 Participant Properties - ICE Connection Parameters H-66 Field Description MCU IP Address The local IP address and port (in the format IP address:Port) of the MCU. Participant IP Address The local IP address and port (in the format IP address:Port) of the endpoint.
PAGE 955
Appendix H-Setting the MCU for Integration Into Microsoft Environment Table H-8 Participant Properties - ICE Connection Parameters (Continued) Field Description ICE Participant IP Address The IP address and the Port number of the endpoint used to pass through the media. This information changes according to the ICE connection type: • When ICE connection type is local, it is identical to the IP address:Port displayed in the Participant IP Address.
PAGE 956
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table H-9 New Active Alarms (Continued) Alarm Code Alarm Description SIP TLS: Registration transport error This alarm indicates that the communication with the SIP server cannot be established.
PAGE 957
Appendix H-Setting the MCU for Integration Into Microsoft Environment ICE Active Alarms When ICE environment is enabled in the MCU, failure to communicate with a required component triggers the display of an Active Alarm in the System Alerts pane. The following table lists these active alarms: Table 9 Polycom, Inc. ICE Environment - MCU Active Alarms Active Alarm Phase Alarm Displayed When Troubleshooting ICE failure: Failed to register with OCS. Check the MCU Server Name.
PAGE 958
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 9 ICE Environment - MCU Active Alarms Active Alarm Phase Alarm Displayed When ICE failure: A/V Edge server URI cannot be resolved Service The MCU failed to resolve The remote address of the Edge server URI. ICE failure: Service credential denied. A/V Edge server credentials rejected by the OCS. Service This alarm indicates that the OCS does not configure with the. Generated by the ICE stack.
PAGE 959
Appendix H-Setting the MCU for Integration Into Microsoft Environment Known Issues • Selecting Pause my Video in OC client causes the call to downgrade to audio only call if the call was not in Audio Only mode at all (the call was started as a video call). If the call is started as an audio only call and video is added to it, or if the call was started as video call and during the call it was changed to Audio Only and back to video, selecting Pause my Video will suspend it as required.
PAGE 960
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide H-72 Polycom, Inc.
PAGE 961
Appendix I Polycom Open Collaboration Network (POCN) Working in the Open Collaboration Server and TIP protocol are supported in AVC Conferencing Mode only. Collaboration With Cisco’s Telepresence Interoperability Protocol (TIP) TIP is a proprietary protocol created by Cisco for deployment in Cisco TelePresence systems (CTS). Since TIP is not compatible with standard video communication systems, interoperability between Cisco and other vendors’ telepresence systems was initially impossible.
PAGE 962
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide TIP-enabled endpoints must support TIP Version 7 or higher. Calls from endpoints supporting older versions of TIP will be rejected. Deployment Architectures The following multipoint topologies are given as examples. Actual deployments will depend on user requirements and available infrastructure: • Single company with Polycom and Cisco Infrastructure • — CTS and Polycom Telepresence Rooms in a corporate environment.
PAGE 963
Appendix I-Polycom Open Collaboration Network (POCN) The following table lists components and versions of the MCU and Cisco Telepresence Systems (CTS) Integration Solution Architecture. Table I-1 Solution Architecture Components Component Version Description 8.5.1, 8.6.2 Cisco Unified Communication Manager: CUCM must be configured to: • Route calls to DMA (if present). CISCO Equipment CUCM • Polycom, Inc. Route all H.323 calls to the gatekeeper, which can be either CMA or IOS. IOS 15.
PAGE 964
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table I-1 Solution Architecture Components Component Version Description Polycom Equipment DMA 7000 4.0 Polycom Distributed Media Application • DMA is an optional component but is essential if Content sharing is to be enabled. • • • MCU DMA should be configured to route SIP calls (with CTS destination) to CUCM. If DMA is not present in the solution architecture, SIP endpoints must register to CUCM as gatekeeper.
PAGE 965
Appendix I-Polycom Open Collaboration Network (POCN) Call Flows Multipoint call with DMA In this example: Polycom, Inc.
PAGE 966
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Multipoint call without DMA In this example: I-6 • MCU prefix in the gatekeeper 72 • CUCM According to its Dial Plan forwards calls with prefix 72 to the MCU Polycom, Inc.
PAGE 967
Appendix I-Polycom Open Collaboration Network (POCN) Company to Company Models Using a Service Provider Using this topology, both companies connect to a Service Provider via a Cisco Session Border Controller (SBC). The Service Provider functions as a B2B Telepresence Exchange, enabling multipoint calls between the two companies and their respective video and audio endpoints using the MCU as the conference bridge.
PAGE 968
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Model 1 The deployment architecture in Figure I-2 shows two companies: Company A and Company B. Company A - has deployed a Polycom solution including: • DMA • MCU • MLA • CMA Gatekeeper • Polycom telephony and desktop endpoints. The roles of the Polycom components are described in the Polycom Equipment section of Table I-1 on page I-3.
PAGE 969
Appendix I-Polycom Open Collaboration Network (POCN) Call Flow Multipoint call via Service Provider - Model 1 In this example: Polycom, Inc.
PAGE 970
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Model 2 The deployment architecture in Figure I-3 shows two companies: Company A and Company B. Company A - has the same deployment architecture as shown in "Single Company Model Polycom and Cisco Infrastructure” on page I-2. Company B - has deployed a Cisco solution including: • CTS 1000 • CTS 3000 • Cisco telephony endpoints. Figure I-3 Company to Company via Service Provider - Model 2 I-10 Polycom, Inc.
PAGE 971
Appendix I-Polycom Open Collaboration Network (POCN) The deployment architecture includes: Company A For a full description of Company A’s deployment, see "Single Company Model - Polycom and Cisco Infrastructure” on page I-2. Differing or additional configuration requirements for each element of this deployment model are listed below: Table I-2 Solution Architecture Components Component Version Description 8.
PAGE 972
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Call Flow Multipoint call via Service Provider - Model 2 In this example: I-12 • MCU prefix in the gatekeeper 72 • Virtual Meeting Room in DMA 725123 • CUCM According to its Dial Plan forwards calls with prefix 72 to the MCU Polycom, Inc.
PAGE 973
Appendix I-Polycom Open Collaboration Network (POCN) Administration The various deployment combinations and settings within the various Deployment Architectures affects the administration of the system. Gatekeepers Standalone Polycom CMA System as a Gatekeeper The Polycom CMA system can be used as the only gatekeeper for the network. Bandwidth and call admission control of endpoints registered with the CMA system is split between the CMA system and the CUCM.
PAGE 974
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Configuring the Cisco and Polycom Equipment MLA (Multipoint Layout Application) is required for managing CTS 3XXX layouts whether Polycom TPX, RPX or OTX systems are deployed or not. MLA is a Windows® application that allows conference administrators to configure and control video layouts for multipoint calls involving Polycom Immersive Telepresence (ITP) systems.
PAGE 975
Appendix I-Polycom Open Collaboration Network (POCN) For more information see "Procedure 4: Configuring a TIP Enabled Profile on the MCU” on page I-19. Cisco Equipment To configure the various Cisco entities the following procedures are required. CUCM 1 Configure the CUCM to send and receive calls from the H.323 network.
PAGE 976
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table I-5 Supported current Polycom products Immersive Telepresence Systems: V3.0.3 • • • • RPX 200 and 400 systems Requires TIP option key. OTX 300 system Requires Polycom Touch Control. TPX HD 306 system ATX HD 300 system HDX Systems: V3.0.3 • • • • Requires TIP option key. 7000 HD Rev C 8000 HD Rev B 9006 4500 The following Polycom peripheral: • 1.3.
PAGE 977
Appendix I-Polycom Open Collaboration Network (POCN) 12 Configuring CMA to route H.323 calls to CUCM 13 Configuring CMA to route non-H.323 calls to CUCM The procedures for configuring CMA are described in detail in the Polycom Unified Communications Deployment Guide for Cisco Environments. Endpoints 14 Configuring H.323 endpoints to register to the CMA or IOS gatekeeper The procedures for configuring H.
PAGE 978
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide b The Port field must be set to it’s default value: 5060. (By default, the Outbound Proxy Server is the same as the SIP Server.) When configuring MCU to statically route SIP calls to DMA or CUCM, it is important to also configure the MCU’s H.323 Network Service to register with CMA gatekeeper. For more information see "Procedure 3: Configuring the MCU’s H.323 Network Service to register with CMA gatekeeper” on page I-18.
PAGE 979
Appendix I-Polycom Open Collaboration Network (POCN) 2 In the MCU Prefix in Gatekeeper field, enter the prefix that the MCU uses to register with the gatekeeper. Procedure 4: Configuring a TIP Enabled Profile on the MCU TIP enabled profiles must be used for the Entry Queues and Meeting Rooms defined on the MCU. (Different Profiles can be assigned to Entry Queues and Meeting Rooms, however they must be TIP enabled.) 1 Polycom, Inc. Create a New Profile for the Meeting Room.
PAGE 980
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide I-20 2 In the New Profile - General tab, set the Line Rate to a value of at least that specified for the MIN_TIP_COMPATIBILITY_LINE_RATE System Flag in Procedure 1. 3 Click the Advanced tab. 4 Select the TIP Compatibility mode: Video and Content is recommended. Polycom, Inc.
PAGE 981
Appendix I-Polycom Open Collaboration Network (POCN) Tables 10, 11 and 12 list the system’s Content sharing behavior for the various combinations of TIP Compatibility mode settings and the following endpoints: Polycom Immersive Telepresence Systems (ITP) Version 3.0.3: • RPX 200 • RPX 400 • OTX 300 • TPX HD 306 • ATX HD 300 Polycom video conferencing endpoints (HDX) Version 3.0.3 • 7000 HD Rev C • 8000 HD Rev B • 9006 • 4500 Cisco TelePresence® System (CTS) Versions 1.7 / 1.
PAGE 982
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 5 Click the Video Quality tab. Content Settings is disabled if TIP Compatibility is set to Video and Content in the Advanced tab. I-22 Polycom, Inc.
PAGE 983
Appendix I-Polycom Open Collaboration Network (POCN) 6 Click the Video Settings tab. If the TIP Compatibility Mode was set to Video and Content, the Send Content to Legacy Endpoints disabled. This setting cannot be changed. 7 Set the Telepresence Mode to Auto. 8 Assign the New Profile to the Meeting Room. For more information see "Creating a New Meeting Room” on page 6-4.
PAGE 984
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 2 In the New Entry Queue or Entry Queue Properties dialog box, ensure that Ad Hoc is selected. 3 Ensure that the Entry Queue is designated as the Transit Entry Queue as described in "Setting a Transit Entry Queue” on page 7-6. Procedure 6: Configuring a Meeting Room on the MCU The Profile for the Meeting Room must be TIP enabled as described in Procedure 4.
PAGE 985
Appendix I-Polycom Open Collaboration Network (POCN) b Click the Advanced tab. c Ensure that: • • • Video Bit Rate is set to Automatic or at least equal to or greater than the value specified by the MIN_TIP_COMPATIBILITY_LINE_RATE System Flag. Resolution is set to Auto or at least HD 720. Video Protocol is set to Auto or at least H.264.
PAGE 986
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • Cisco TelePresence® System (CTS) Versions 1.7 / 1.8 — CTS 1300 — CTS 3010 Deployment Architecture • DMA is required as all calls are dial-in to Virtual Meeting Rooms (VMR) provisioned on the DMA. • Microsoft and Cisco clients dial the same VMR number to connect to the conference.
PAGE 987
Appendix I-Polycom Open Collaboration Network (POCN) Component Version CMA 6.0.1 CMAD 5.2.3 ITP (OTX, RPX, ATX, TPX) 3.0.5 Conferencing for Outlook (PCO) 1.0.7 Touch Control 1.3 Microsoft OCS 2007 R2 3.5.6907.236 Lync 2010 4.0.7577.183 CU4 OC 2007 R2 client 3.5.6907.236 Lync 2010 client 4.0.7577.4051 CU4 Exchange 2007 R2 SP3 8.3.213.1 Exchange 2010 SP2 14.2.247.5 Outlook 2007 12.0.6557.5001 SP2 Outlook 2010 14.0.6112.5000 Cisco CUCM 8.5, 8.6.
PAGE 988
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Call Flow Multipoint Calls using DMA In this example: • Endpoint registration to either DMA, Lync or CUCM. • DMA dial in Prefix 72 • Virtual Meeting Room in DMA 725123 • DMA Meeting NumberGenerated by DMA Administration The various deployment combinations and settings within the Deployment Architecture affects the administration of the system. I-28 Polycom, Inc.
PAGE 989
Appendix I-Polycom Open Collaboration Network (POCN) DMA The DMA system can be configured as a SIP proxy and registrar for the environment as well as a Gatekeeper for dial in H.323 calls. When configured as a Gateway for dial in H.323 calls, it enables H.323 endpoints to connect to the same VMR as SIP clients.
PAGE 990
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide iiiBrowse to the saved Certificate on the Workstation and click the Yes button to install the certificate. For more information see: • • 3 I-30 "Setting the MCU for Integration Into Microsoft Environment” on page H-1. Polycom Unified Communications Deployment Guide for Microsoft Environments, “Configuring Your MCU System for use with the Lync Server”. Register the MCU with the Lync Server.
PAGE 991
Appendix I-Polycom Open Collaboration Network (POCN) i In the Outbound Proxy Servers table, the Port field must be set to 5061. (The same value as entered in Step g.) For more information see the Polycom Unified Communications Deployment Guide for Microsoft Environments. 4 Set the MIN_TIP_COMPATIBILITY_LINE_RATE System Flag. The MIN_TIP_COMPATIBILITY_LINE_RATE System Flag determines the minimum line rate at which a Profile can be TIP enabled. CTS version 1.
PAGE 992
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide For more information see the Polycom Unified Communications Deployment Guide for Cisco Environments, “Direct Registration of Polycom Telepresence Systems with the Cisco Unified Communications Manager”. 13 Register HDX endpoints to the DMA as Gatekeeper For more information see the Polycom® DMA™ 7000 System Operations Guide.
PAGE 993
Appendix I-Polycom Open Collaboration Network (POCN) c Click the Advanced tab. d Select the TIP Compatibility mode: Video and Content is recommended. Tables I-1, I-2 and I-3 list the system’s Content sharing behavior for the various combinations of TIP Compatibility mode settings and the following endpoints: Polycom Immersive Telepresence Systems (ITP) Version 3.0.3: • RPX 200 • RPX 400 • OTX 300 • TPX HD 306 • ATX HD 300 Polycom video conferencing endpoints (HDX) Version 3.0.
PAGE 994
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table I-2 TIP Compatibility - Video Only Content Receiver Video Only Content Sender HDX / ITP CTS HDX / ITP H.239 None CTS None None Table I-3 TIP Compatibility - Video & Content Content Receiver Video & Content Content Sender HDX / ITP CTS HDX / ITP CTS H.239 TIP Content TIP Content TIP Content Selecting TIP Compatibility as Video and Content disables Content Settings in the Video Quality tab.
PAGE 995
Appendix I-Polycom Open Collaboration Network (POCN) Encryption Set the encryption setting in the conference Profile to Encrypt When Possible. Set the FORCE_ENCRYPTION_FOR_UNDEFINED_PARTICIPANT_IN_WHEN_AVAILABLE_M ODE System Flag to NO These setting will enable encrypted and non-encrypted H.323 participants to connect to encrypted or non-encrypted conferences. For more information see “Encryption” on page 2-52. e Click the Video Quality tab.
PAGE 996
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide If the TIP Compatibility Mode was set to Video and Content, the Send Content to Legacy Endpoints disabled. This setting cannot be changed. g Set the Telepresence Mode to Auto. 16 Configure a Virtual Meeting Room (VMR) on the DMA The procedures for configuring DMA are described in detail in the Polycom Unified Communications Deployment Guide for Cisco Environments.
PAGE 997
Appendix I-Polycom Open Collaboration Network (POCN) 19 Configure SIP endpoints to register to: • DMA as SIP Proxy • Lync Server as SIP Proxy • CUCM as SIP Proxy The procedures for configuring SIP endpoints are described in detail in the Polycom Unified Communications Deployment Guide for Cisco Environments.
PAGE 998
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Operations During Ongoing Conferences Moving participants between TIP enabled meetings and non TIP enabled meetings is not possible. Monitoring CTS Participants 1 In the Participant List pane double-click the participant entry. Alternatively, right-click a participant and then click Participant Properties. The Participant Properties - General dialog box opens. 2 Click the SDP tab.
PAGE 999
Appendix I-Polycom Open Collaboration Network (POCN) When viewing CTS systems in the Participants list, the individual video screens and the Audio Channel (AUX) of the CTS system are listed as separate participants. The Participant list below shows a connected CTS 3000, a 3-screen system. Video Audio Lync Participants (RTV) 1 In the Participant List pane double-click the participant entry. Alternatively, right-click a participant and then click Participant Properties.
PAGE 1000
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide 3 Click the Channel Status - Advanced tab 4 In the Channel Info drop-down menu select Video Out. Media Info displays RTV Channel Status parameters: I-40 Polycom, Inc.
PAGE 1001
Appendix I-Polycom Open Collaboration Network (POCN) Known Limitations The following may occur in the collaborative environment: Polycom, Inc. • Artifacts and ghosting may appear when Lync Clients and CTS endpoints connect to the VMR. Frequency: Seldom. • Lync Client receives fast updates (Intra) from CTS 500 endpoints causing the screen to refresh repeatedly. Frequency: Often. • Audio volume and video quality decreases on CTS endpoints. Frequency: Seldom.
PAGE 1002
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide I-42 Polycom, Inc.
PAGE 1003
Appendix J Restoring Defaults USB Restore Defaults The USB port of an MCU in Ultra Secure Mode can be used to: • Restore the MCU to Factory Security Defaults mode (https  http).
PAGE 1004
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide • RealPresence Collaboration Server (RMX) 2000 - at the bottom right corner of the RTM IP card on the back panel. • RealPresence Collaboration Server (RMX) 4000 - at the bottom right corner of the RTM IP 4000 card on the back panel.
PAGE 1005
Appendix J-Restoring Defaults 2 Power the MCU Off and then On. 3 Login using http://. Comprehensive Restore to Factory Defaults Inserting a USB key containing a file named RestoreToFactoryDefault.txt and a lan.cfg file will cause the MCU to exit Secure Mode and perform a Comprehensive Restore to Factory Defaults.
PAGE 1006
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Procedure A: Backup Configuration Files The Software Management menu is used to backup and restore the MCU's configuration files and to download MCU software. To backup configuration files: 1 On the RMX Menu, click Administration > Software Management > Backup Configuration. The Backup Configuration dialog box opens. 2 Browse to the Backup Directory Path and then click Backup.
PAGE 1007
Appendix K SIP RFC Support Table K-1 Polycom, Inc. SIP RFC Support in RealPresence Collaboration Server (RMX) Systems SIP RFC Description Note 1321 MD5 2032 RTP Payload for H.261 2205 RSVP 2327 Session Description Protocol (SDP) 2429 RTP Payload for H.
PAGE 1008
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table K-1 K-2 SIP RFC Support in RealPresence Collaboration Server (RMX) Systems (Continued) SIP RFC Description 4566 Session Description Protocol(SDP) 4568 SDP Security Descriptions 4573 H.
PAGE 1009
Appendix L Homologation for Brazil H.323 & SIP Protocol Flag Options Using a set of system flags, the user has the ability to select either Polycom proprietary or H.323/SIP standard protocol settings. H.323 & SIP Flag Settings Three flags are enabled on the MCU, allowing the user to define and select either standard or proprietary H.323 and SIP protocol settings. Flag name: SIP_TIMERS_SET_INDEX Description: SIP Timer type timeout settings according to standard or proprietary protocol.
PAGE 1010
Polycom RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide Table 1 SIP Timer Types & their Values (Continued) Value (in milliseconds) SIP TIMER Types TimerK POLYCOM (flag default) Standard Recommended 5000 5000 Flag name: H323_TIMERS_SET_INDEX Flag description: Enables or disables H.323 index timer according to standard or proprietary H.323 protocol. Section CS_MODULE_PARAMETERS Possible values: 0 - Sets the H.