Download Print this page

Polycom RealPresence 1800 Administration Manual

Polycom RealPresence 1800 Administration Manual

Collaboration server

Hide thumbs Also See for RealPresence 1800:

Administrator's manual (1113 pages)

,

Getting started manual (70 pages)

,

Hardware manual (18 pages)

Table Of Contents

page of 449

/ 449
Contents
Table of Contents
Bookmarks

Table of Contents

Advertisement

Quick Links

Download this manual See also: Administrator's Manual

ADMINISTRATION GUIDE

8.8 | December 2018 | 3725-74900-000B1

®

RealPresence

Collaboration Server

1800/2000/4000/Virtual Edition

Table of Contents

Advertisement

Table of Contents

Need help?

Need help?

Do you have a question about the RealPresence 1800 and is the answer not in the manual?

Questions and answers

Summary of Contents for Polycom RealPresence 1800

Page 1 ADMINISTRATION GUIDE 8.8 | December 2018 | 3725-74900-000B1 ® RealPresence Collaboration Server 1800/2000/4000/Virtual Edition...
Page 2 Polycom up to three (3) years after the distribution date of the applicable product or software at a charge not greater than the cost to Polycom of shipping or distributing the software to you. To receive software information, as well as the open source software code used in this product, contact Polycom by email at OpenSourceVideo@polycom.com.
Page 3: Table Of Contents
Polycom and Partner Resources ........
Page 4 Import a Conference Template ..........39 Polycom, Inc.
Page 5 Giving Exclusive Content Sharing Ownership ........64 Canceling Exclusive Content Sharing Ownership ....... 64 Polycom, Inc.
Page 6 MIH Cascading Guidelines in CP Licensing ....... . 92 Master - Slave Conferences 92 Video Session Mode, Line Rate and Video Settings 93 Polycom, Inc.
Page 7 Audible Alarm for Notifying on Required Assistance ....... 125 Polycom, Inc.
Page 8 ActiveX Bypass ............158 Polycom, Inc.
Page 9 Ad Hoc Conferencing ............172 Gateway to Polycom® RealPresence Distributed Media Application™ (DMA™) System . . .
Page 10 Appendix - Polycom Lab Features ........
Page 11 Contents Enable and Disable this Polycom Lab Feature ......326 Popup Site Name on Participant Join/Leave ........327 Description of Feature .
Page 12 Enabling RDP Content ..........363 Polycom MCU Video Quality Dialog on DMA ......363 IP Network Services - SIP Servers Dialog .
Page 13 Configuring the Cisco and Polycom Equipment ........
Page 14 Resource Allocation ........... . 405 Configuring Microsoft, Cisco and Polycom Components ......405 Content Sharing Behavior .
Page 15 Flag name: H323_TIMERS_SET_INDEX ....... . . 428 Flag name: DISABLE_DUMMY_REGISTRATION ......428 Polycom, Inc.
Page 16: Before You Begin
Before You Begin The Polycom Collaboration Server (RMX) Administrator Guide provides instructions to ® ® RealPresence configure and administer your RealPresence Collaboration Server (RMX) 1800, 2000, 4000, and Virtual Edition Multipoint Control Unit (MCU). Audience, Purpose, and Required Skills The primary audience for this guide is system administrators and network engineers who configure, maintain, and support the telecommunications infrastructure and video conferencing environment.
Page 17 Is customer personal data shared with any third parties and if so, who? If personal data is made available when working with Polycom support, this data may be shared with contracted third-party engineering companies.
Page 18 Alias Name/SIP Address TRANS_CDR_FULL APIs • Lync/Skype user name to retrieve CDRs. All RMX APIs are available at Polycom Support page. See the RMX API SDK for your version of the product. User All of the following: Login and authentication •...
Page 19 MMARY_LIST API for audit files and TRANS_LOG_FILE_LIST for log files. All RMX APIs are available at Polycom Support page. See the RMX API SDK for your version of the product.S How admin can be informed of any security anomalies (including data breach)
Page 20: Getting Help
Standard restore – simple delete section in this guide. Comprehensive restore – System hard disk file partition is formatted Getting Help For more information about installing, configuring, and administering Polycom products, see the Polycom Document Library. Polycom and Partner Resources See the following Polycom documentation for related information on this product: ●...
Page 21: The Polycom Community
Participate in discussion forums to share ideas and solve problems with your colleagues. To register with the Polycom Community, simply create a Polycom online account. When logged in, you can access Polycom support personnel and participate in developer and support forums to find the latest information on hardware, software, and partner solutions topics.
Page 22: Product Overview
This enables RealPresence Collaboration Servers to split a larger number of participants and resources. Microsoft Lync or Skype for Business users can also connect (via Polycom RealConnect) to a RealPresence Collaboration Server meeting room to a conference running on the Microsoft AVMCU.
Page 23: Supported Network Configurations
(DBA) help minimize media quality degradation that can result from packet loss in the network. The Polycom LPR algorithm uses Forward Error Correction (FEC) to create additional packets that contain recovery information. DBA allocates the bandwidth needed to transmit the additional packets.
Page 24: Isdn (Audio/Video) Conferencing Network
RealPresence Collaboration Server, • .Net Framework 2.0 SP1 or higher is required and installed Virtual Edition automatically. • Internet Explorer must be enabled to allow the running of Signed ActiveX. If ActiveX installation is blocked, see ActiveX Bypass. Polycom, Inc.
Page 25: System User Types
RealPresence DMA system to log into the RealPresence Collaboration Server. However, for security reasons, Polycom strongly recommends immediately setting up a new administrator account on both the RealPresence Collaboration Server and the RealPresence DMA system and deleting the default administrator account.
Page 26: Operator
            Information             Recording             Polycom, Inc.
Page 27: Navigating The System
The MCU pane is available to all users. Only one RealPresence Collaboration Server can be selected in the MCU pane. The menu items, RMX management, address book, conference templates, and all properties that are applicable to the selected MCU are available. Polycom, Inc.
Page 28: The Mcu Pane
To stop monitoring the conferences running on this MCU and the participants, clear the Monitored check box. Video The number of video resources available for conferencing. Resources Audio The number of audio resources available for conferencing. Resources Polycom, Inc.
Page 29: Mcu Icons And States
Conferences List The Conferences List includes all the conferences currently running on the MCU along with the Status, Conference ID, Start Time, and End Time data. The number of ongoing conferences is displayed in the title of the pane. Polycom, Inc.
Page 30: Conferences List Toolbar Options
The MCU State indicator displays one of the following: MCU State Indicator Option Description The MCU is starting up. The time remaining until the system start-up is complete. The Time remaining is displayed within parentheses. The blue progress indicator bar indicates the start-up progress. Polycom, Inc.
Page 31: Port Usage Gauges
The port information in the system according to the video or voice port configuration. The Audio gauge is displayed only if audio ports are allocated by the administrator, otherwise only the video port gauge is displayed. ● Number of video and voice ports in use ● High port usage threshold Polycom, Inc.
Page 32: List Pane
MCU. The information in the Address Book can be modified only by an administrator. All system users can view and use the Address Book to assign participants to conferences. The Quick Search field displays all the available options in the Address Book. Polycom, Inc.
Page 33: Rmx Management Pane
RealPresence Collaboration Server to run conferences. Only users with administrators permission can modify these parameters. The RMX Management pane is divided into two sections: ● Frequently Used – Parameters often configured, monitored, or modified. Polycom, Inc.
Page 34: Frequently Used And Rarely Used Sections
A conference template does the following: ● Saves the conference profile ● Saves all participant parameters including the Personal Layout and Video Forcing settings ● Simplifies telepresence conference setup where precise participant layout and video forcing settings are crucial Polycom, Inc.
Page 35: Toolbar Buttons
For more information see Scheduling Conferences Using the Reservation Calendar. The Conferences List toolbar includes the following button: Conferences List – Toolbar Button Button Description Save Conference to Template Saves the selected ongoing conference as a Conference Template. Polycom, Inc.
Page 36: Getting Started
Windows-based system or the RMX Web Client application using Internet Explorer. For the most part, Polycom recommends using RMX Manager to configure and manage the RealPresence Collaboration Server. However, use the RMX Web Client when direct access to a single RealPresence Collaboration Server, Appliance Edition is required.
Page 37: Add An Mcu
1 In RMX Manager, go to Setup > RMX Time. 2 Configure these settings, as necessary. Field Description GMT Date The UK, Greenwich date. Local Time The MCU local time settings calculated from GMT Time and GMT Offset. Polycom, Inc.
Page 38: Requesting And Adding Certificates
4 Complete the following fields CSR Information Description Country Name Two letter code for the country of State or Province Specifies the state or province where your organization is located. Locality Specifies the city where your organization is located. Polycom, Inc.
Page 39 Note: The system supports only one OU field. If you want the CA-signed certificate to include more than one OU, download and manually edit the CSR. Common Name (DNS) Specifies the system name. Polycom recommends the following guidelines for this field:. •...
Page 40: Installing The Certificate
Manager system and a RealPresence DMA system along with one or more RealPresence Collaboration ® ® Servers), integrate your RealPresence Collaboration Server with the Polycom RealPresence Resource Manager system and set it us as the device (endpoint and server) application manager. The Resource Manager system can also manage users and conference participants.
Page 41: Overlay A Custom Logo On Conference Displays
In general, you configure the RealPresence Collaboration Server using the user interface. However, you will likely need to configure the MCU for specific application and operational needs by adding predefined RealPresence Collaboration Server system flags and setting them to the required values. Polycom, Inc.
Page 42: Integrate With The Realpresence Dma System
Manager system and a RealPresence DMA system along with one or more RealPresence Collaboration ® ® Servers), integrate your RealPresence Collaboration Server with the Polycom RealPresence system and set it us as the call control for the conferencing network. Configure the RealPresence DMA system as the H.323 gatekeeper and/or SIP server, endpoint registrar and virtual meeting room manager.
Page 43: Integrate With Harman Media Suite
Getting Started Integrate with HARMAN Media Suite RealPresence Collaboration Server can dial out to a HARMAN Media Suite (previously Polycom RealPresence Media Suite) for conference recording if you first establish a dial-out Recording Link, which is a dial-out connection from the MCU to the HARMAN Media Suite.
Page 44: Customizing The Rmx Manager User Interface
You can view the RMX Management section either as a list or as a toolbar. To switch between RMX Management Toolbar and List Views: » In RMX Manager, go to the RMX Management section and toggle the upward or downward arrow to change from list view to toolbar view respectively. Polycom, Inc.
Page 45: Move Items In The Rmx Management Section
You can restore the RMX Manager user interface to its factory default configuration when needed. To restore the RMX Manager user interface to its default configuration: » In RMX Manager, go to View > Restore RMX Display Defaults. Polycom, Inc.
Page 46: Conference Profiles And Templates
● Content sharing features ● Recording features ● Endpoint protocol(s) supported ● Conference messaging ● Polycom Lost Packet Recovery (LPR) and Dynamic Bandwidth Allocation (DBA) ● Encryption The following topics describe RealPresence Collaboration Server conference profiles. View the List of Conference Profiles A RealPresence Collaboration Server has three default conference profiles based on conferencing mode.
Page 47: Add A New Conference Profile
Message Overlay Parameters - Not available when SVC Only conferencing mode is selected  Network Services Parameters  Layout Indications Parameters - Not available when SVC Only conferencing mode is selected For detailed information about the conferencing parameters, see Conference Profile Parameters 5 Click OK to save the new profile. Polycom, Inc.
Page 48: Conference Profile Parameters
All endpoints must connect at the same line rate. Those that don’t support the specified line rate are connected in voice-only mode. • You can also enable H.264 high profile, which allows the conference to use Polycom’s bandwidth-conserving H.264 High Profile codec. Operator Not available when Video Switching is enabled.
Page 49 Specifies that when receiving calls through a firewall or session border controller (SBC), the Alive MCU should send media stream keep-alive messages to the RTP, UDP and BFCP channels at the interval specified. The acceptable interval is within the range of 1 - 86400 seconds. Polycom, Inc.
Page 50 Info 1 Optional free-form text fields to display on the gathering phase slide. On a 16:9 endpoint, a maximum of 96 characters can be displayed for each field, and fewer on Info 2 a 4:3 endpoint. Info 3 Polycom, Inc.
Page 51 If you choose a custom content rate, specify the line rate reserved for the content. AS SIP Available only when CP (Continuous Presence) conferencing mode is selected. Content Enables content sharing using AS-SIP security and the Multiple Content Resolutions option, which is not supported in any other content sharing mode. Polycom, Inc.
Page 52 Skype client shares RDP content, the RDP translator delivers H.264 content to the MMCU. Notes: • For Polycom RealConnect calls to work, set ‘AllowMultiView’ to TRUE on the Skype for Business Front End Server. This will enable the participants to connect and receive multiple video streams.
Page 53 When selected, the system automatically selects the conference layout based on the number of participants currently connected to the conference. When a new video participant connects or disconnects, the conference layout automatically changes to reflect the new number of video participants. Polycom, Inc.
Page 54 Dial Out Conference recording requires a recording system such as a Polycom RealPresence Media Recording Link Suite or Polycom Capture Server. Select the recording link for the device to be used for conference recording. Start Recording Select when to start the recording: •...
Page 55 Recording Icon them that the conference is being recorded. Skype for Business users connected to the conference via Polycom RealConnect technology get notified when a Skype for Business user starts recording the meeting by displaying a recording icon within the video layout.
Page 56: Conference Templates
When enabled, the MCU displays a recording indicator (a red dot) to all participants to inform them that the conference is being recorded. Skype for Business users connected to the conference via Polycom RealConnect technology get notified when a Skype for Business user starts recording the meeting by displaying a recording icon within the video layout.
Page 57: Add A New Conference Template
MCU dials out to him, the MCU creates a second participant in the Participants list and still attempts to dial out to the participant. If the dial-out participant was designated as the conference lecturer, the MCU cannot replace that participant with the dial-in participant that is connected to the conference. Polycom, Inc.
Page 58: Additional Conference Profile And Conference Template Tasks
If your environment includes multiple MCUs, you will likely want all of the same conference profiles available on all MCUs, so conferences can successfully cascade over multiple MCUs. The RealPresence Collaboration Server allows you to export conference profiles from one MCU as a single XML file and import them to other MCUs. Polycom, Inc.
Page 59: Import A Conference Profile
 The conference profile requires an IVR service that is not present on the MCU . Edit a Conference Template You cannot edit a conference template. Delete a Conference Template You can delete one or several conference templates at a time. Polycom, Inc.
Page 60: Export A Conference Template
_confProfiles.xml suffix predefined as required by the MCU. Import a Conference Template You can import conference templates (and associated conference profiles) from one to multiple MCUs in your environment. To import a conference template: 1 In RMX Manager, click Conference Templates. Polycom, Inc.
Page 61: Save An Ongoing Conference As A Template
1 In the RMX Manager Conferences List, select the conference to be saved as a template. 2 Right-click and select Save Conference to Template. The MCU saves the template with a name derived from the ongoing conference display name. Operator conference templates are displayed with the operator conference icon. Polycom, Inc.
Page 62: Advanced Conferencing Profile Features
The RealPresence DMA system has more flexibility, as it can associate conferencing experiences with users, conference rooms, or enterprise groups. It also offers more features and functions including MCU cascading and integration with Polycom RealConnect. Enable Recording in the Conference Profile Enable conference recording on the RealPresence Collaboration Server as part of the conference profile by first configuring the dial-out recording link.
Page 63: Change Position Of The Conference Indicators
 Packet loss less than 1% is considered Normal  Packet loss in the range of 1% - 5% is considered Major  Packet loss above 5% is considered Critical. Conference indicators, shown below, are displayed on AVC endpoints only for CP or mixed conferences. Polycom, Inc.
Page 64: Indicators For Microsoft Skype For Business Users
5 Click OK. Indicators for Microsoft Skype for Business Users Microsoft Skype for Business and Lync users see the same conference indicators other Polycom RealConnect conference participants do provided the video stream sent to the their endpoint is compatible. However, the indications are not embedded in the video sent to the link, so as to preserve the Skype for Business or Lync user experience.
Page 65: Binary Floor Control Protocol (Bfcp) Support For Tip Endpoints
The NoiseBlock feature is supported for AVC endpoints only in Continuous Presence (CP) and in Mixed CP and SVC conferences. In mixed CP and SVC conferences, the RealPresence Collaboration Server blocks audio towards AVC-based endpoints only. Polycom, Inc.
Page 66 YES/NO. MCU reset is not required when changing the system flag value. ● If your conferencing environment includes Polycom DMA, the conferences started from the DMA do not include the NoiseBlock parameter as it is not part of the DMA Profiles. In such a case, when the parameter setting is unknown, the system enables/disables the NoiseBlock according to the system flag setting - if the flag is set to YES, it is enabled in the conference.
Page 67: Conference Management
® Resource Manager, which has a Web Scheduler feature, or another scheduling application such as Microsoft Outlook or the Polycom Conferencing Add-in for Microsoft Outlook, Polycom recommends that you create and schedule conferences using one of these standard scheduling applications and not the MCU.
Page 68 Profiles and Templates Unique ID number for the conference on the MCU. If left blank, the MCU automatically assigns an ID number once the conference starts. Polycom recommends you allow the MCU to assign the Routing Name automatically. Communicate this conference ID to dial-in participants to enable them to dial in to the conference.
Page 69 6 Click Participants and add participants from the Address Book or click New and enter the required information for new participants. 7 If required, chose a participant as a lecturer and as needed enable Dial Out Manually, so the MCU can dial out to the lecturer. Polycom, Inc.
Page 70: Starting An Ad Hoc Conference
Info2, Info3, or Billing Info text boxes. 7 Click OK to start the conference. Unless otherwise specified, the system automatically assigns the conference an ID when the conference starts. 8 Communicate the conference ID to conference dial-in participants. Polycom, Inc.
Page 71: Other Ways To Start A Conference
● By copying and pasting a conference in the Conferences list. ● From Microsoft Outlook using the Polycom Conferencing Add-in for Microsoft Outlook. 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®.
Page 72: Working With Active Conferences
Working with Active Conferences If your environment has a standalone RealPresence Collaboration Server, you can use it to manage active conferences. IMPORTANT: If your organization uses another conference management application such as the Polycom ® RealPresence ® Resource Manager, Polycom recommends that you create and schedule conferences using that applications and not the MCU.
Page 73: Unlocking A Conference
RMX Manager displays the Participants List and the status of each participant including: Column Icon/Description Name Displays the name and type (icon) of the participant: Audio Participant – Connected via IP phone or ISDN (audio/video). Video Participant – Connected with audio and video channels. Polycom, Inc.
Page 74 (operator) has been requested to join the conference. Connected, Noisy – Participant’s endpoint is requesting too many intras, resulting in the MCU ceasing to send intras to the endpoint to preserve conference quality for all other participants. Polycom, Inc.
Page 75 The IP participant’s IP address or the ISDN (audio/video) participant’s phone number. Alias Name/ The participant’s Alias Name or SIP URI. SIP Address The alias of a Polycom ® RealPresence ® Media Suite if the participant is functioning as a recording link.
Page 76: Adding Participants To An Active Conference
To add a participant or group to an active conference: 1 In the RMX Manager Conferences List, select the active conference of interest. 2 Click Participants and then: a Click Add from Address Book, select the required groups and participants, and click Add Polycom, Inc.
Page 77: Moving Participants Between Conferences
1 In the RMX Manager Conferences List, select the active conference of interest. 2 In the Participant list, select the participant to move. 3 Right-click and select one of the following options:  Move to Operator Conference - To move the participant(s) to an Operator conference. Polycom, Inc.
Page 78: Sending A Message To Participants During A Conference
8 Specify the font size, color, position, and transparency. 9 Specify the speed at which the text should move (static, slow, or fast) and how often it should repeat. Polycom, Inc.
Page 79: Restricting Content Sharing
You can enable or disable the Mute Participants Except Lecturer option at any time after the start of the conference. When enabled, conference participants are not muted until the lecturer joins the conference. Muted participants can only be unmuted by: ● A RealPresence Collaboration Server administrator or operator or Polycom, Inc.
Page 80: Previewing A Participant's Video
The video preview is displayed in a separate independent window with no disruption to the conference and the video preview window size and resolution are adjusted to the resolution of the PC on which it is displayed. Polycom, Inc.
Page 81: Enabling Auto Scan
Auto Scan only takes effect when the number of participants is larger than the number of cells in the conference layout. RealPresence Collaboration Server supports Auto Scan in AVC CP conferences only Polycom, Inc.
Page 82 3 If Auto Layout is enabled, clear it. 4 In the video layout cell to be designated for Auto Scan, select Auto Scan from the drop-down menu. 5 Select the scanning interval from the Auto Scan Interval(s) list . 6 Click Apply or OK. Polycom, Inc.
Page 83: Enabling Customized Polling
To define the scanning order in the Customized Polling tab: 1 In the RMX Manager Conferences List, select the active conference of interest. and click Conference Properties. 2 Right-click and in the Conference Properties - General dialog, click Customized Polling. Polycom, Inc.
Page 84: Canceling A Message Overlay
3 Right-click and select Add Participant to Address Book. Viewing the List of Participants Awaiting Help The Participant Alerts section at the bottom of RMX Manager flashes when participants are awaiting help. Double-click on the Participant Alert title to view the list of participants awaiting help. Polycom, Inc.
Page 85: Content Sharing Management Tasks
You can only start and stop recording for an active conference when the conference profile assigned to the conference has recording enabled and has a recording link set up. For more information on enabling recording via the conference profile see . Polycom, Inc.
Page 86 If you edit the conference profile that is being used for active conferences to enable recording, that change will apply to the active conference, but it will also apply to all other active conferences and future conferences using that profile, which may not be desirable. If an active conference is using the Polycom, Inc.
Page 87: Cascading 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. Polycom, Inc.
Page 88: Guidelines
Cascaded links in 1x1 video layout use SD resolution. ● When the Mute Participants Except Lecturer option is enabled in the Conference Profile, all participants (including the link participants) except the lecturer are muted. ● Gathering phase is not supported in Cascading Conferences. Polycom, Inc.
Page 89: Flags Controlling Cascade Layouts
The tone used to notify that the cascading link connection has been established cannot be customized. The option to play a tone when the cascading link is established is enabled by setting the System Flag CASCADE_LINK_PLAY_TONE_ON_CONNECTION to YES. Default value: NO. Polycom, Inc.
Page 90: Possible Cascading Topologies
● The configuration can include two Collaboration Servers or one Collaboration Server and one MGC. ● Multiple Cascade Links enabling Cascading between MCUs hosting conferences that include Immersive Telepresence Rooms (ITP), such as Polycom’s OTX and RPX Room Systems, can be defined. For more information see Creating Multiple Cascade Links Between Telepresence Conferences.
Page 91: Basic Cascading Using Ip Cascaded Link
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. Polycom, Inc.
Page 92: Automatic Identification Of The Cascading Link
In this topology, an IP participant calls another IP participant over an ISDN-video link between two gateways. ● Gateway to MCU 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-video link. Polycom, Inc.
Page 93: Guidelines For Isdn-Video Cascaded Links
Gateway B. [GW Profile ISDN (audio/video) number] - The dial-in number assigned to the Gateway Profile defined on Gateway B, including the required country and area codes. Information required that is not part of the dialing string: Polycom, Inc.
Page 94: Gateway To Mcu Calls Via Isdn-Video Cascading Link
Information required that is not part of the dialing string: [Destination Conference ID] - Only if using the Entry Queue on MCU B for routing calls or creating new ad hoc conferences. The ID of the destination conference on MCU B. The dialing string format: Polycom, Inc.
Page 95: Mcu To Mcu Calls Via Isdn-Video Cascading Link
To enable Gateway-to-Gateway, Gateway-to-MCU and MCU-to-MCU calls over ISDN-video Cascading links, the following configurations are required: ● Modifying the IP Network Service to include the MCU Prefix in the Gatekeeper (in the Gatekeepers dialog box). For more details, see Modifying the Default IP Network Service. Polycom, Inc.
Page 96 ● Defining the dial-in ISDN-video participant in MCU B and Dial-out ISDN-video participant in MCU A (for MCU-to-MCU cascading conferences). A dial out ISDN-video 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). Polycom, Inc.
Page 97: Conference Profile Definition
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. Conference Profile Definition The following table lists the recommended Meeting Room/Conference Profile parameters setting when routing ISDN-video cascaded calls. Recommended Conference Profile Options Setting Line Rate Motion Sharpness Encryption Polycom, Inc.
Page 98: Mcu Interoperability Table
User calls directly to a remote user behind Collaboration Server v. 7.1 Server Gateway a Gateway (User to User) Collaboration Codian Dial out participants use a fixed rule Collaboration Server v. 7.1 Server MCU Gateway behind the Codian Gateway. Latest Codian version Polycom, Inc.
Page 99 User calls directly to a DMA controlled Collaboration Server v. 7.1 Server Gateway environment Collaboration Collaboration A dial out participants calls to a remote Collaboration Server v. 7.1 Server MCU Server Gateway conference on a DMA controlled environment Polycom, Inc.
Page 100: Suppression Of Dtmf Forwarding
This flag is defined on MCU A (the calling MCU). If a flag is not listed in the System Flags list it must be added to the system.cfg file before it can be modified. For more details on defining system flags, see Modifying System Flags. Polycom, Inc.
Page 101: Star Cascading Topology
 MGC with version 9.0.4 can be used in level 2, if Collaboration Server version 7.0.2 and higher, is deployed in level 1. ● If an MGC is deployed on level 1:  MGC or Collaboration Server can be used on level 2. Polycom, Inc.
Page 102 To establish the links between two Collaboration Servers requires the following procedures be performed: ● Establish the Master-Slave relationships between the cascaded conferences by defining the dialing direction. ● Create the Master and Slave conferences, defining the appropriate line rate. Polycom, Inc.
Page 103: Cascade Enabled Participant Link
New Participant - General New Participant – Dial-out Cascade Link Field Description Name Enter the participant’s name. This field may not be left blank. Duplicate participant names, comma, and semi-colon characters may not be used in this field. Polycom, Inc.
Page 104 If the conference has a password and you do not want to include the password in the dial string, set the ENABLE_CASCADED_LINK_TO_JOIN_WITHOUT_PASSWORD flag to YES. For more information see Modifying System Flags. Alias Type Select E.164 (digits 0-9, *, #). Polycom, Inc.
Page 105 Cascading Conferences Advanced tab Polycom, Inc.
Page 106 If a gatekeeper is not used: Enter the ID of the MCU running the other (second) conference. Alias Type If a gatekeeper is used: H.323 ID If a gatekeeper is not used: Select E.164 (digits 0-9, *, #). Polycom, Inc.
Page 107: Cascading Via Entry Queue
(Conference A) connects to the second conference (Conference B) via a special cascaded Entry Queue (EQ). When MCU A dials out to the cascaded link to connect it to conference A, it actually dials out to the cascaded Entry Queue defined on MCU B. Cascaded Conferences - Star Topology Polycom, Inc.
Page 108: Enabling Cascading
B) Entry Queue defined on the MCU hosting the destination cascaded conference. The dial-out participant can be defined in the Address Book and added to the conference whenever using the same cascade-enabled Entry Queue and a destination conference (with the same ID and Password). Polycom, Inc.
Page 109  Using only the Alias string (requires a gatekeeper) - Method B. Method B In this method a gatekeeper is used: In the Alias Name field, enter the Prefix of MCU B, EQ ID, Destination Conference ID, and Password, as follows: <MCU Prefix EQ ID>#<Conference ID>#<Password> (Password is optional) Polycom, Inc.
Page 110: Monitoring Star Cascaded Conferences
The Conferences List panes in each of the two conferences will display a cascaded conference icon ( indicating that a conference running on the MCU is presently cascading with another conference running on the same or another MCU. The cascaded conference icon is displayed for a short duration. Polycom, Inc.
Page 111: H.239-Enabled Mih Topology
● Utilizing the connection abilities of different MCUs, for example, different communication protocols, such as, serial connections, ISDN-video, etc. ● Significant call cost savings to be realized by having participants call local MCUs which in turn call remote MCUs, long distance. Polycom, Inc.
Page 112: Mih Cascading Levels
 MGC version 9.0.4 can be used on level 2 and level 3,  DST MCS 4000 and other MCUs can be deployed on levels 3 and 4. ● If an MGC is deployed on level 1:  MGC or RMX can be used on level 2. Polycom, Inc.
Page 113: Mih Cascading Guidelines In Cp Licensing
● When the DST MCS 4000 is on level 3 and acting as slave to level 2, the RMX on level 2 must dial out to it in order for the DST MCS 4000 to be identified as slave. The link between the two MCU (dial out participant) is defined as a standard participant and not as a cascading link. Polycom, Inc.
Page 114: Video Session Mode, Line Rate And Video Settings
 MGC does not support H.264 High Profile, therefore when MGC is part of the Cascading topology, do not select High Profile on the RMX system.  DTMF codes should be defined with the same numeric codes in the IVR services assigned to the cascading conferences. Polycom, Inc.
Page 115 Level 2 CP/VSW -HD 1.5Mb/s, 1Mb/s, 2Mb/s Level 3 MCS 4000 Level 2 CP - CIF 768kb/s, 2Mb/s Level 3 MCS 4000 * When MGC is on Level 3, Content cannot be shared between Level 2 and Level 3. Polycom, Inc.
Page 116: Mgc To Collaboration Server Cascading
MCU and the name of the master conference The alias that will be used to identify the running on the Collaboration Server. dial-in participant can be the name of the calling slave conference. Set the Cascading option as Master. Polycom, Inc.
Page 117: Method Ii
Define the conference setting and its line rate to rate to be the same as the one set on the be the same as the one set on the MGC. Collaboration Server. Define the dial-out participant (Cascaded Link) to the conference running on the Collaboration Server. Polycom, Inc.
Page 118 MGC. Collaboration Server. Define the dial-out participant (Cascaded Link) to the conference running on the MGC, setting the participant Cascade parameter to Slave. Polycom, Inc.
Page 119: User Management
A full administrator can define and delete other users and perform all configuration and maintenance tasks. The RealPresence Collaboration Server ships with a default Administrator user called POLYCOM, whose password is POLYCOM. However, once you have defined other authorized Administrator users, it is recommended to remove the default user. Administrator Read-only...
Page 120: View The List Of Current Users
Add a User Administrators can add a new user to the system. To add a user: 1 In the RMX Management pane, click (Users). 2 Click (New User). 3 In the User Properties dialog box, enter the following information. Polycom, Inc.
Page 121: Edit A User
Administrators can change their own passwords and other users’ passwords. Operators can change their own passwords. To change a user’s password: 1 In the RMX Management pane, click (Users). 2 In the Users list, select the user, right-click, and select Change User Password. Polycom, Inc.
Page 122: Disable A User
Machine accounts are only supported when TLS security is enabled and Request peer certificate is selected. Administrators add machine accounts to the system as a special class of user known as application users. Polycom, Inc.
Page 123: View Mcu Connections
Check this option for machine accounts only Common Name (CN) Enter the FQDN of the server/machine hosting the application for which the added application user is defined--for example, dma1.polycom.com 4 Click OK. View MCU Connections The RealPresence Collaboration Server allows you to list all connections that are currently logged into the MCU including users, servers or API users.
Page 124: Address Book
Address Book participants in conferences. IMPORTANT: ® ® If you have a Polycom RealPresence Resource Manager system, integrate your RealPresence Collaboration Server with it and manage users and conference participants in the RealPresence Resource Manager system rather than the MCU.
Page 125: Adding A Group To The Address Book
 General Participant Properties  Advanced Participant Properties 4 To add general information about the participant, such as e-mail address or company name, click Information and enter the necessary details in the Info 1-4 fields. 5 Click OK. Polycom, Inc.
Page 126: Participant Properties
For SIP participant enter either the endpoint IP address or the endpoint SIP address. For Collaboration Servers registered to a gatekeeper, the MCU can be configured to dial and receive calls to and from H.323 endpoints using the IP address in the event that the Gatekeeper is not functioning. Polycom, Inc.
Page 127 • SIP URI - Uses the format of an E-mail address, typically containing a user name and a host name: sip:[user]@[host]. For example, sip:dan@polycom.com. Note: If the SIP Address field contains an IPv6 address, it must be surrounded by square brackets, for example, [::1].
Page 128 3 dB (decibel). The volume scale is from 1 to 10, where 1 is the weakest and 10 is the strongest. The default connection value is 5. Polycom, Inc.
Page 129: Adding Participants From The Address Book To A Conference
2 From the Hierarchy, select the group from which to add participants. 3 Select the participant(s) to be added to the conference and drag them to the Participants list. Editing a Participant’s Address Book Information When required, you can edit a participant’s Address Book information or properties. Polycom, Inc.
Page 130: Deleting A Participant From The Address Book
Address Book to another by dragging and dropping the participant to its new location. Filtering the Address Book Filter the Address Book to display only the entries (participants or groups) that meet criteria you specify. This allows you to select and work with a subset of Address Book entries. Polycom, Inc.
Page 131: Exporting An Address Book
If your environment includes multiple MCUs, you will likely want all MCUs to use the same Address Book. The RealPresence Collaboration Server allows you to export the Address Book from one MCU as a single proprietary formatted XML file and import it to other MCUs. Polycom, Inc.
Page 132: Importing An Address Book
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. 3 Click Open and then click OK. The MCU displays a confirmation message when the Address Book is imported. 4 Click Close. Polycom, Inc.
Page 133: Operator Conference And Assistance
This service is designed usually for large conferences that require the personal touch. Operator Conference Guidelines ● An Operator conference can only run in Continuous Presence mode. Polycom, Inc.
Page 134: Defining Components Prerequisite For Operator Assistance
To enable operator assistance for conferences, the following conferencing components 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. Polycom, Inc.
Page 135 15 Enable the Roll Call feature and assign the appropriate audio file to each message type. For more information, see Conference IVR Service Properties - Roll Call Messages. 16 Open the Video Services tab. 17 Define the Video Services parameters. For more information, see New Conference IVR Service Properties - Video Services Parameters. Polycom, Inc.
Page 136 In such a case, the operator joins the conference. 20 Open the Operator Assistance tab. 21 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. Polycom, Inc.
Page 137 12 Select Enable Operator Assistance to enable operator assistance when the participant requires or requests help during the connection process. 13 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. Polycom, Inc.
Page 138 2 In the Conference Profiles pane, click New Profile. 3 Define the Profile name and, if required, the Profile general parameters. For more details, see New AVC CP Profile - General Parameters. 4 Select the Operator Conference check box. 5 Open the Advanced tab. Polycom, Inc.
Page 139 A new Profile is created and added to the Conference Profiles list. To start a conference from the Conference pane: 1 In the Conferences pane, click New Conference. 2 In the Profile field, select a Profile in which the Operator Conference option is selected. Polycom, Inc.
Page 140 Define the duration of the conference in hours using the format HH:MM (default 01:00). Notes: • The Operator conference is automatically extended up to a maximum of 168 hours. Therefore, the default duration can be used. • This field is displayed in all tabs. Polycom, Inc.
Page 141 Maximum Number of Enter the maximum number of participants that can connect to an Operator Participants conference (you can have more than two), or leave the default selection (Automatic). Maximum number of participants that can connect to an Operator conference: Polycom, Inc.
Page 142: Saving An Operator Conference To A Template
To save an ongoing Operator conference as a template: 1 In the Conferences list, select the Operator conference you want to save as a Template. 2 Click Save Conference to Template. Right-click and select Save Conference to Template. Polycom, Inc.
Page 143: Starting An Operator Conference From A Template
You can only start an Operator conference from a template whose name is identical to your Login Name. For example, if your Login name is Polycom, you can only start an Operator conference from a template whose name is Polycom.
Page 144: Monitoring Operator Conferences And Participants Awaiting Assistance
A participant can request help using the appropriate DTMF code from his/her touch tone telephone or the endpoint’s DTMF input device. The participant can request Individual Assistance (default DTMF code *0) or Conference Assistance (default DTMF code 00). Polycom, Inc.
Page 145: Participant Alerts List
The Participant Alerts list contains all the participants who are currently waiting for operator assistance. Participants are automatically added to the Participants Alerts list in the following circumstances: ● The participant fails to connect to the conference by entering the wrong conference ID or conference password and waits for the operator’s assistance Polycom, Inc.
Page 146: Audible Alarm For Notifying On Required Assistance
The participants are automatically removed from the Participant Alerts list when moved to any conference (including the Operator conference). Audible Alarm for Notifying on Required Assistance An audible alarm can be activated and played when participants request Operator Assistance. For more details on Audible alarms and their configuration, see Audible Alarms. Polycom, Inc.
Page 147: Administration And Utilities
Administration and Utilities This section describes the tasks that you may need to administer and maintain the Polycom RealPresence Collaboration Server. System and Participant Alerts The MCU alerts users to any faults or errors 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.
Page 148  To an XML file, click Save to XML The Save to XML button is only available when logged in as a special support user. 4 Select a destination folder and enter the file name. 5 Click Save. Polycom, Inc.
Page 149: Viewing Participant Alerts
● Displaying Resource Report ● MCU Resource Management by RealPresence Resource Manager, and Polycom RealPresence DMA System 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 150: Viewing The Resource Report
The following table demonstrates the actual resource capacity utilization for both CP only and mixed CP and SVC conferences in AVC HD720p30 units. Resource Capacity Allocation Per Port Type Port Type Non-Mixed Conferences Mixed CP and SVC Conferences AVC HD 1.5 * AVC SD 0.75 * AVC CIF 0.333 0.75 * Polycom, Inc.
Page 151: Resource Reports For Collaboration Servers 1800/2000/4000
Resource Reports for Collaboration Servers 1800/2000/4000 Collaboration Servers 2000/4000 do not differentiate between Video and Voice (Audio) resources. These MCUs allocate the same amount of system resources to Voice (Audio) participants, as those allocated to CIF Video participants. Polycom, Inc.
Page 152: Setting The Port Usage Threshold
The administrator can monitor the MCU port capacity usage via the Port Gauge in the Status Bar of the RMX Manager. The Port Usage Gauge displays for the Collaboration Server: ● The total number of Video ports in the system. ● The number of Video ports in use. ● The High Port Usage threshold. Polycom, Inc.
Page 153: View System Information
Manager and are saved on the MCU hard disk. Only users defined as Administrator can define or modify the SNMP security parameters in the RMX Manager. To enable the SNMP option: 1 In RMX Manager, go to Setup > SNMP. The RMX SNMP Properties - Agent dialog is displayed. Polycom, Inc.
Page 154 Specifies the version, either Version 1 2 or 3 of the traps being sent to the IP Host. Polycom software supports the standard SNMP version 1 and 2 traps, which are taken from RFC 1215, convention for defining traps for use with SNMP.
Page 155 Trap. If the Engine ID field (Version 3) is empty when Enable Trap Inform has been selected, the Engine ID is set by the Client. Community Name Enter the Community Name of the manager terminal used to monitor the 1, 2 MCU activity Polycom, Inc.
Page 156 This dialog box is used to define whether the query sent to the MCU is sent from an authorized source. When 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. Polycom, Inc.
Page 157 16 To specifically define valid terminals, de-select the Accept SNMP Packets from any Host check box, and click Add. The Accepted Host IP Address dialog opens. 17 Enter the IP Address of the Manager terminal from which valid queries may be sent to the MCU, and click OK. Polycom, Inc.
Page 158: Hot Backup
● Reservations ● Meeting Rooms ● Entry Queues ● SIP Factories ● Gateway Profiles ● IVR services (excluding .wav files) ● Recording Link ● Profiles ● IP Network Settings:  H.323 settings  SIP settings  DNS settings Polycom, Inc.
Page 159: Enabling Hot Backup
Select either Master MCU or Slave MCU from the drop-down menu. Paired MCU IP Address Enter the Control Unit IP Address of the: • Slave MCU (if this MCU is the Master) • Master MCU (if this MCU is the Slave) Polycom, Inc.
Page 160: Configuring The Hot Backup Triggers
Master MCU. This trigger is always set. Lost connection with media port Initiates the Hot Backup switch from the Master to the Slave MCU when the connection with an active media port is lost on the Master MCU. Polycom, Inc.
Page 161: Modifying The Master Mcu Configuration
The Audible Alarm played when Operator Assistance is requested, is enabled and selected using Setup > Audible Alarm > User Customization. When an Audible Alarm is activated, the *.wav file selected in the User Customization is played, and is repeated according to the number of repetitions defined in the User Customization. Polycom, Inc.
Page 162: Configuring Audible Alarms
When cleared, the Audible Alarm will not be repeated and will be played only once. Number of Repetitions Define the number of times the audible alarm will be played. Default number of repetitions is 4. Polycom, Inc.
Page 163: Replacing The Audible Alarm File
1 In RMX Manager, go to Setup > Customize Display Settings > Multilingual Setting. 2 Select the check boxes of the languages to be available for selection, and click OK. 3 Log out from the RMX Web Client and log into for the customization to take effect. Polycom, Inc.
Page 164: Banner Display And Customization
● The following parameters, settings and files are backed up:  MCMS configuration files (/mcms/Cfg):  Network and service configurations  Rooms  Profiles  Reservations  System Flags  Resource Allocation Polycom, Inc.
Page 165: Restore Configuration Files
● Both explicit IP addresses and Host Names are supported. ● The RMX Manager blocks any attempt to issue another Ping command before the current Ping command has completed. Multiple Ping commands issued simultaneously from multiple RMX Web Clients are also blocked. Polycom, Inc.
Page 166: Configure Notification Settings
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). Polycom, Inc.
Page 167: Retrieve Logger Diagnostic Files
3 In the Logger Diagnostic Files dialog, click Browse to select the directory location from which to retrieve the Logger files, and click OK. 4 In the Logger Diagnostic Files dialog, click Retrieve Files, and once complete, click OK. Polycom, Inc.
Page 168: Information Collector
Signaling Trace files (H.323 & SIP) • Cards info: HW version, state and status • Central Signaling logs • SW version number • Processes internal state and statistics • System Log Files • Processes internal state and statistics • • Full faults Polycom, Inc.
Page 169: Ultra Secure Mode
(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. The entire zipped file is then sent to Polycom’s Network Systems Division for analysis and troubleshooting. Ultra Secure Mode The Information Collector logs information from the Collaboration Server’s Network Intrusion Detection...
Page 170 Information Collector - Standard Security Mode Information Collector - 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. Polycom, Inc.
Page 171: Auditor
Collaboration Server system. Auditor operates in real time, recording all administration activities and login attempts from the following Collaboration Server modules: ● Control Unit ● Shelf Manager For a full list of monitored activities, see Audit Events. Polycom, Inc.
Page 172: Auditor Files
You can open the Auditor file directly from the Auditor Files list or you can retrieve the files and save them to a local workstation. To access Auditor Files: 1 In RMX Manager, go to Administration > Tools > Auditor Files. Polycom, Inc.
Page 173 2 Select the file(s) to be retrieved, or click Select All to retrieve all the files. (Windows multiple selection techniques can be used.) 3 Click Retrieve Files. The selected files are copied to the selected directory on the workstation. Polycom, Inc.
Page 174: Auditor File Viewer
The Auditor File Viewer enables Auditors and Administrators to view the content of and perform detailed analysis on auditor event data in a selected Auditor Event File. You can view an Auditor Event File directly from the Auditor Files list or by opening the file from the Auditor File Viewer. Polycom, Inc.
Page 175 The name (alias) of the workstation used to send the request that triggered the event. IP Address (Workstation) The IP address of the workstation used to send the request that triggered the event. Event Type Auditor events can be triggered by: • • HTTP • Collaboration Server Internal Event Polycom, Inc.
Page 176 To open an auditor event file stored on the workstation: 1 Click Local File ( 2 Navigate to the location of the audit event file. 3 Select the audit event file to be opened. 4 Click Open. The selected file is opened in the Auditor Viewer. Polycom, Inc.
Page 177: Audit Events
IP Network Service configuration modified. IP Network Service deleted. Login Logout Management Session Time Out MCU Reset to enable Diagnostics mode. MCU reset. Music file error. New activation key was loaded. New version was installed. NTP synchronization failure. Polycom default User exists. Polycom, Inc.
Page 178: Transactions
The Log file system is disabled. The software contains patch(es). USB key used to change system configuration. User closed the browser User initiated MCU reset. Transactions Transactions recorded by the Auditor Transaction TRANS_CFG:SET_CFG TRANS_IP_SERVICE:DEL_IP_SERVICE TRANS_IP_SERVICE:NEW_IP_SERVICE TRANS_IP_SERVICE:SET_DEFAULT_H323_SERVICE TRANS_IP_SERVICE:SET_DEFAULT_SIP_SERVICE TRANS_IP_SERVICE:UPDATE_IP_SERVICE TRANS_IP_SERVICE:UPDATE_MANAGEMENT_NETWORK TRANS_ISDN_PHONE:ADD_ISDN_PHONE TRANS_ISDN_PHONE:DEL_ISDN_PHONE TRANS_ISDN_PHONE:UPDATE_ISDN_PHONE Polycom, Inc.
Page 179: Activex Bypass
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. Polycom, Inc.
Page 180: Installing Activex
Installing ActiveX To install ActiveX components on all workstations in the network: 1 Download the MSI file EMA.ClassLoaderInstaller.msi from the Polycom Resource Center. 2 The MSI file contains installation scripts for both .NET Framework and .NET Security Settings. 3 Create a text file to be used during the installation, containing the IP addresses of all the Collaboration Servers (both control unit and Shelf Management IP addresses) that each workstation in the network should connect.
Page 181: Reset The Collaboration Servers 2000/4000/1800
● VMWare - See VMWare documentation on Resetting Virtual Machines. ● Hyper-V - See Hyper-V documentation on Resetting Virtual Machines. Please note that, the System Reset option doesn’t actually reboot the Virtual Machine, it only restarts the MCU service. Polycom, Inc.
Page 182: Entry Queues, Ad Hoc Conferences And Sip Factories
SIP Factories Note: Virtual Platform Guideline When using Polycom® RealPresence® Platform, virtual Entry Queues and ad-hoc conferences should be defined in the RealPresence Resource Manager and virtual Meeting Rooms in the RealPresence DMA system. They should not be defined directly in the RealPresence Collaboration Server.
Page 183 The Entry Queue can also be used as part of the Gateway to DMA solution for connecting Audio only ISDN-voice, ISDN-video, SIP and H.323 endpoints to DMA system. For more information, see Gateway to Polycom® RealPresence Distributed Media Application™ (DMA™) System. Default Entry Queue properties The system is shipped with a default Entry Queue whose properties are shown in the following table.
Page 184 (Unicode and ASCII). Maximum field length in ASCII is 80 characters. If the same name is already used by another conference, Meeting Room or Entry Queue, the Collaboration Server displays an error message requesting you to enter a different name. Polycom, Inc.
Page 185 Control Channel Framework-Interactive Voice Response) package. When selected, the connection process of the participant to the conference via the Virtual Entry Queue is controlled and managed by an external IVR service of an application server (for example, DMA). Polycom, Inc.
Page 186: Entry Queue List
Dial-in Number (2) By default, the second dial-in number is not defined. To define a second-dial-in number, enter a required number from the dial-in number range defined for the selected Network Service. Entry Queue List The list of Entry Queues: Polycom, Inc.
Page 187: Transit Entry Queue
IVR services. Call Flow The SIP participant dials the DMA Virtual Entry Queue number, for example 1000@dma.polycom.com. The DMA forwards the SIP call to the Collaboration Server, to a special Entry Queue that is configured as IVR Only Service Provider.
Page 188: Using External Ivr Services Via The Mccf-Ivr
Polycom RealPresence Virtualization Manager (DMA) as the application server. When the application server is deployed in the enterprise environment and the Polycom RealPresence Collaboration Server (MCU) is deployed as a media server, the external IVR service can be used to play audio messages, display slides, and collect DTMF input from the participant.
Page 189: Call Flow For Standalone Tip Endpoints
Call Flow for TIP Endpoints from a Polycom ITP System The following describes how a TIP call from Cisco TPS endpoints or TIP calls from a Polycom ITP system working as a TIP call is placed into the IVR-controlled Entry Queue and is then connected to a conference: 1 A TIP call is routed through the application server to the IVR-controlled Entry Queue.
Page 190: Guidelines For Using External Ivr Services Via The Mccf-Ivr Package
To change this flag value from YES to NO, you must first add it to the System Configuration. 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. Polycom, Inc.
Page 191 (Unicode and ASCII). Maximum field length in ASCII is 80 characters. If the same name is already used by another conference, Meeting Room or Entry Queue, the Collaboration Server displays an error message requesting you to enter a different name. Polycom, Inc.
Page 192: Sip Registration & Presence For Entry Queues And Sip Factories With Sip Servers
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. Polycom, Inc.
Page 193: Guidelines For Registering Entry Queues And Sip Factories With Sip Servers
ID is already running on the MCU. If not, the system automatically creates a new ongoing conference with that ID. The conference parameters are based on the Profile linked to the Entry Queue. As opposed to Meeting Rooms, that are predefined conferences saved on the MCU, Ad Hoc conferences are not stored Polycom, Inc.
Page 194: Gateway To Polycom® Realpresence Distributed Media Application™ (Dma™) System
Gateway to DMA 7000 enables audio only ISDN-voice, ISDN-video (video endpoints using only their audio channels), SIP and H.323 calls to connect to the Polycom DMA 7000 via gateway sessions running on the Collaboration Server. Each Collaboration Server conference acting as a gateway session includes one connection to the endpoint and another connection to the DMA.
Page 195: System Flags
2 In the MCMS_PARAMETERS_USER select the flag to be modified and click Edit Flag. tab, 3 Enter the value in the New Value field and click OK. 4 Repeat steps 2 and 3 to modify any additional flags. 5 Click Close. Polycom, Inc.
Page 196: Delete A System Flag
42 Kbps, when the Lync server is configured to allow 33 Kbps audio rate. Siren 7 audio codec is preferred for SIP/Lync calls, depending on the value of this flag. Default value: NO Possible values: YES/NO Polycom, Inc.
Page 197 HW/VE _LYNC over the video channel. Also includes those with the Polycom CCS plug-in installed, even when the Send Content to Legacy Endpoints is enabled. Other non-Lync legacy endpoints will not be affected by this flag and will receive content according to the Send Content to Legacy Endpoints settings in the conference profile.
Page 198 HW/VE to NO will prevent BIOS upgrade. Default value: YES Possible values: YES/NO CAC_ENABLE When set to YES, enables Call Admission Control HW/VE implementation in the RealPresence Collaboration Server. Default value: NO (CAC is disabled) Possible values: YES/NO Polycom, Inc.
Page 199 Ad-hoc Entry Queue and enters a conference ID that is not being used by any other conferencing entity. It is based on the Conference Profile assigned to the EQ.<does ad-hoc conference need to be defined> Polycom, Inc.
Page 200 Default value: YES Possible values: YES/NO CPU_BONDING_LINK_MONITORI Used when using the MII Monitor for troubleshooting HW/VE NG_FREQUENCY networks. This flag sets the MII Polling Interval in milliseconds. A value of zero disables the MII monitoring. Default value: 100 Polycom, Inc.
Page 201 Indicates the interval in seconds between the HW/VE ONDS KeepAlive requests. Default value: 75 seconds Range: 10-720 seconds DELAY_BETWEEN_H320_DIAL_O The delay in milliseconds that the MCU waits when UT_PARTY connecting dial out ISDN-video and voice participants. Default vlaue: 1000 Polycom, Inc.
Page 202 Control (AGC) for the participant audio. This mechanism regulates noise and audio volume by keeping the received audio signals of all participants balanced. Default value: NO Possible values: YES/NO Note: Enabling AGC might result in amplification of background noise. Polycom, Inc.
Page 203 Microsoft Skype for Business or Lync user on the video layout of a Video Teleconference user participating in a Polycom RealConnect conference, when that Skype for Business or Lync user disables its video output. If the Skype for Business or Lync...
Page 204 IVR, when the MCU collects the Conference ID in the local entry queue or the password while routed to the conference. Polycom, Inc.
Page 205 System Flags General System Flags Flag Name Description Platform Add? ENABLE_EPC When set to YES, enables the Polycom proprietary HW/VE People+Content. When set to NO, disables this feature for all conferences and participants. Default value: YES Possible values: YES/NO ENABLE_EXTERNAL_DB_ACCES...
Page 206 When enabled, a Part Index is added to the CDR List. It displays the CDR file sequence in the CDR file set. The files included in a set have the same unique Display Name. Default value: NO (disabled) Possible values: YES/NO Polycom, Inc.
Page 207 RealPresence Collaboration Server and that they will be connected as audio only. Default value: YES Possible values: YES/NO ENABLE_POLYCOM_EPS_IN_LYN Enables all Polycom endpoints connected to the HW/VE C_ROSTER RealPresence platform in Lync roster. Default value: DISABLED Possible values: DISABLED,...
Page 208 Default value: YES Possible values: YES/NO ® ™ ENABLE_SIRENLPR Enables or disables the Polycom Siren Lost HW/VE Packet Recovery Audio Algorithm for use in IP (H.323, SIP) calls in both CP and VSW conferences.
Page 209 HW/VE the RealPresence Collaboration Server to send and receive XML requests/responses. Default value: 80 EXTERNAL_CONTENT_USER The login name defined for the RealPresence HW/VE Collaboration Server in the RealPresence Resource Manager server defined in the format: domain name/user name Polycom, Inc.
Page 210 Server 2000 or 4000 only. EXTERNAL_DB_LOGIN The login name defined for the RealPresence HW/VE Collaboration Server in the external database server. Default value: POLYCOM Note: Applicable to RealPresence Collaboration Server 2000 or 4000 only. EXTERNAL_DB_PASSWORD The password associated with the user name...
Page 211 Enter the product type to which the CIF resource should be allocated. Possible values are VSX nnnn - where nnnn represents the model number. For example, VSX 8000. FORCE_G711A Forces the use of the G.711A audio codec. HW/VE Default value: NO Possible values: YES/NO Polycom, Inc.
Page 212 When set to YES, the level of broadcasting volume HW/VE OLUME of the connected participant is value taken from the system flag SYSTEM_BROADCAST_VOLUME. If set to NO (default), the broadcasting volume level is 5. Default value: NO Possible values: YES/NO Polycom, Inc.
Page 213 Content protocols: Up to H.264 or H.263. When set to YES, the RealPresence Collaboration Server checks the frame rate, resolution, and all other parameters of the Content mode as declared by an endpoint before receiving or transmitting Content. Default value: NO Possible value: YES/NO Polycom, Inc.
Page 214 NO. If set to YES, the RealPresence Collaboration Server will release video resources for Audio Only calls. Default value: YES Possible value: YES/NO Polycom, Inc.
Page 215 Mixed mode conferences, since in this case AVC-only and SVC-only are the only conference modes supported. This flag can be enabled to achieve a higher capacity for a given hardware and virtual machine configuration. Default value: NO Possible values: YES/NO Polycom, Inc.
Page 216 When set to NO (default) this flag prevents potential HW/VE scheduling conflicts from occurring as a result of system calls from external scheduling applications such as Polycom ReadiManager ® , and others through the API. Set to YES to schedule conference reservations using an external scheduling application.
Page 217 When set to NO (default), this flag disables the HW/VE telepresence features in the Conference Profile. Set the flag to YES to enable the telepresence features in the Conference Profile (provided that the appropriate license is installed). Default value: NO Possible values: YES/NO Polycom, Inc.
Page 218 Note: System reset is not required for flag changes to take effect. IVR_ROLL_CALL_SUPPRESS_OP When set to YES, the MCU suppresses the HW/VE ERATOR entry/exit tone when the operator participant joins or leaves the conference. Default value: NO Possible values: YES/NO Polycom, Inc.
Page 219 • System reset is not required for flag changes to take effect. LEGACY_EP_CONTENT_DEFAULT Defines the video layout to be displayed on the HW/VE _LAYOUT screen of the legacy endpoints when switching to Content mode. Default value: CP_LAYOUT_1P7 (1+7). Polycom, Inc.
Page 220 At times, further reduction is required to preserve the bandwidth, which is regulated by this system flag. When set to YES, enables H.323 endpoints to reduce their content rate or Polycom Lost Packet Recovery (LPR) strength as follows: • For single MCU conferences: ...
Page 221 Implements any Frame Rate based on Lync RTV Client capabilities. Range: 0-30 fps MAX_COUNT_LYNC_PARTIES Allows to get the count of Skype for Business and HW/VE nonSkype Business audio/video participants connected to cascaded conference through AVMCU. Flag values are as follows: Default value: 20 Range: 0-99 Polycom, Inc.
Page 222 MCU_DISPLAY_NAME The MCU name that is displayed on the endpoint’s HW/VE screen when connecting to the conference. Default value: Polycom RealPresence Collaboration Server 1800, 2000, or 4000 (the last depends on the product type). MEDIA_NIC_MTU_SIZE The maximum data payload size (bytes) transmitted...
Page 223 MS_CAC_VIDEO_MIN_BR, the call is not connected as a video call. Default value: 40 Range: 0 - 384 MS_ENVIRONMENT When set to YES, the RealPresence Collaboration HW/VE Server SIP environment integrates with Microsoft OCS solution. Default value: NO Possible values: YES/NO Polycom, Inc.
Page 224 (SBC) with a 3-second interval between messages. Default value: 3 Range: 1 -10 NUMBER_OF_REDIAL Enter the number redialing attempts required. HW/VE Dialing might continue until the conference is terminated. Default value: 3 Polycom, Inc.
Page 225 (*86) or themselves (*6). Default value: NO Possible Values: YES/NO If the chairperson dials *5 and any endpoint dials the configured override mute all DTMF, the override DTMF continues to function without the need of this flag. Polycom, Inc.
Page 226 Message Overlay functionality to the participants directly connected to the MCU in a Polycom RealConnect conference, to indicate certain restrictions pertaining to the presentation and viewing of content. Default value: No Possible values: YES/NO Polycom, Inc.
Page 227 MLA. PSTN_RINGING_DURATION_SEC If there is a slow response from the ISDN-video ONDS switch, ISDN-voice dial-out ringing duration (in seconds) is used by the RealPresence Collaboration Server to disconnect the call. Default value: 45 Polycom, Inc.
Page 228 Default value: NO Possible Value: YES/NO Note: Requires MCU reset. REDIAL_INTERVAL_IN_SECONDS Enter the number of seconds that the RealPresence HW/VE Collaboration Server should wait before successive redialing attempts. Default value:10 Range: 0-30 Polycom, Inc.
Page 229 0 – 19 (seconds): The feature is disabled. • 20 – 300 (seconds): The feature is enabled. REMOVE_H323_EPC_CAP_TO_N Used to disable EPC protocol. Use of Polycom’s HW/VE ON_POLYCOM_VENDOR proprietary protocol, High Profile, EPC, might result in interoperability issues when used with other vendors’...
Page 230 RRQ - registration request sent to the gatekeeper. Default: NO Possible values: YES/NO RTCP_FIR_ENABLE When set to YES, the Full Intra Request (FIR) is sent HW/VE as INFO (and not RTCP). Default = YES Possible values: YES/NO Polycom, Inc.
Page 231 Port Usage threshold. When set to NO, the system does limit the SIP audio endpoint connections to a certain capacity and will not send a busy notification when the resource capacity threshold is exceeded. Default value: NO Possible value: YES/NO Polycom, Inc.
Page 232 We recommend this setting for Maximum Security Environments. •  When any conferences on the RealPresence Collaboration Server will have both Microsoft Lync clients and Polycom endpoints participating.  Some third-party endpoints might be unsuccessful in participating in conferences with this setting.
Page 233 (4 kHz) audio algorithms: • G.729a • G.711 Note: This flag sets the initial value for Polycom Audio Clarity during First-time Power-up. Thereafter, control the feature through the Profile Properties > Audio Settings dialog box. Default value: OFF Possible Values: ON/OFF...
Page 234 Entering john.smith will generate a SIP URI = john.smith@maincorp.com SIP_ENABLE_FECC By default, enable FECC support for SIP endpoints HW/VE at the MCU level. You can disable it by manually adding this flag and setting it to NO. Possible values: YES/NO. Polycom, Inc.
Page 235 The call becomes an audio only call and video resources are not guaranteed to participants if they want to add video again. Default value in Microsoft environment: NO Possible values: YES/NO Polycom, Inc.
Page 236 Default value: YES Possible value: YES/NO SUPPORT_HIGH_PROFILE_WITH Enables or disables the support of High Profile video _ISDN protocol for ISDN-video participants in CP Only conferences. Default value: NO Possible value: YES/NO SUPPORT_MULTIPLE_ICE_USER Enables the configuration of multiple Lync registrations. Polycom, Inc.
Page 237 The number of seconds the server will wait for a HW/VE TCP client to answer a call before closing the connection. Default value:5 seconds TERMINATE_CONF_AFTER_CHAI Indicates that the chairperson has left the R_DROPPED conference. Note: Enable the flag to play this message. Polycom, Inc.
Page 238 This flag contains a new parameter OUT_REQ IsLyncVideoMuted and can take the following values: • 0 - To not display any doughboy image for the Microsoft Lync participants. • 1 - To display doughboy image for the Microsoft Lync participants. Polycom, Inc.
Page 239 CRL. • DISABLED - Does not check the CRL and does not fail the connection request based on the CRL content. Default value: DISABLED Possible values: ENABLED, OPTIONAL, DISABLED Polycom, Inc.
Page 240 Controls the time that the RealPresence Collaboration Server waits for endpoints to respond to its SDP Re-invite that is determined by a timer. Default value: 10 seconds Range: 1-60 seconds (values outside this range are rejected and an error message is displayed). Polycom, Inc.
Page 241 H.323 protocol. Default value: 0 Possible values: • 0 (Default) - Sets the H.323 index timer to Polycom proprietary. • 1 - Sets the H.323 index timer based on the H.323 Standard recommendation. Note: For homologation and certification testing, this flag must be set to 1.
Page 242 Note: For homologation and certification testing, this flag must be set to 1. SIP_TO_TAG_CONFLICT For use in Microsoft environments. In case of forking, a tag conflict will be resolved when Status 200 OK is received from an answering UA.<require more clarity> Default value: YES Possible: YES/NO Polycom, Inc.
Page 243 RMX Web Client or RMX Manager are hidden when viewing the properties of the conference. • Automatic generation of passwords (both conference and chairperson passwords) is disabled, regardless of the settings of the flags:  NUMERIC_CONF_PASS_DEFAULT_LEN  NUMERIC_CHAIR_PASS_ DEFAULT_LEN Default value: NO Automatic Password Generation Flags Polycom, Inc.
Page 244 The minimum number of special characters (asterisks, brackets, periods, etc.) required in a login password in Ultra Secure Mode. Default value: 0 NUM_OF_UPPER_CASE_ALPHABETIC The minimum number of uppercase alphabetic characters required in a login password in Ultra Secure Mode. Default value: 0 Polycom, Inc.
Page 245 The maximum number of digits that the user can enter when manually assigning a password to the chairperson. Default value: 16 Range: 0 – 16 NUMERIC_CHAIR_PASS_MIN_LEN Defines the minimum length required for the chairperson password. Default: 0 - This rule is not enforced. Range: 0-16 Polycom, Inc.
Page 246 Determines the display of a warning to the user of the number of days until password expiration. Value: between 0 and 14 days. 0 - password expiry warnings are not displayed. In Ultra Secure Mode, the earliest display - 14 days, the latest 7 days (default). Polycom, Inc.
Page 247 Enables the administrator to control the ICMP Destination UNREACHABLE Unreachable messages (ICMP message type #3). Default value: • Ultra Secure Mode: NO - Destination Unreachable Message is never sent. • Default Security Mode: YES - Destination Unreachable Message is sent when needed. Possible values: YES/NO Polycom, Inc.
Page 248 Controls the Minimum Threshold Line Rate for HD720p50 and HD720p60 resolutions for High Profile-enabled VSW conferences. Default value: 832 Kbps VSW_SD_HP_THRESHOLD_BITRATE Controls the Minimum Threshold Line Rate for SD resolution for High Profile-enabled VSW conferences. Default value: 128 Kbps Polycom, Inc.
Page 249 When set to YES, this flag disables the encryption of the recording link, regardless of the encryption settings of the ® ® conference and the Polycom RealPresence Media Suite recorder. Default value: NO Possible value: YES/NO Polycom, Inc.
Page 250 Possible values: AUTO, QCIF, CIF, VGA, or HD720 MINIMUM_FRAME_RATE_THRESHOLD_FOR_ Prevents low quality and 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. Default value: 15 Range: 0 -30 Polycom, Inc.
Page 251 Collaboration Server to send and receive XML requests/responses. For secure communications set the value to 443. Default value: 5005 RMX_MANAGEMENT_SECURITY_PROTOC Enter the protocol to be used for secure communication. Default value: TLSV1_SSLV3 (both) Default value for U.S. Federal licenses: TLSV1 Polycom, Inc.
Page 252 Default value: TOP_RIGHT Possible values: • BOTTOM_LEFT • BOTTOM_RIGHT • TOP_LEFT • TOP_RIGHT DISABLE_CELLS_NETWORK_IND This flag disables the display of network quality indicators displayed in the cells of the conference video layout. Default value: YES Possible values: YES/NO Polycom, Inc.
Page 253 Default value: BOTTOM_RIGHT Possible values: • TOP_ LEFT • • TOP_RIGHT • BOTTOM_ LEFT • BOTTOM • BOTTOM_RIGHT NOTE: The Network Quality check box in the Layout Indications tab of the New Profile/Profile Properties dialog replaces this flag’s function. Polycom, Inc.
Page 254 PCM_FECC System Flag Flag Name Description PCM_FECC Determines whether the DTMF Code, ##, the Arrow Keys (FECC), or both will activate the PCM interface. In addition, use this flag to disable the PCM. Default value: YES Possible Values: YES/NO Polycom, Inc.
Page 255 Enter the interval in seconds between the Intra requests sent from RealPresence Collaboration Server 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 value: 5 Polycom, Inc.
Page 256 System Configuration to view or modify its value. Default value: 20 Range: 16-300 (4-second units). Values indivisible by 4 will be rounded upward. Flag values between 0 and 15 disable the flag functionality. Polycom, Inc.
Page 257 User Management Flags Flag Name Description DEFAULT_USER_ALERT This flag alerts the administrator that the default user (Polycom) exists. Default value: NO Default value (Ultra Secure Mode): YES Possible values: YES/NO DISABLE_INACTIVE_USER The system automatically disables the users when not logged on to the RealPresence Collaboration Server application for a predefined period.
Page 258 Enables the video preview feature. Default value: YES Network Security System Flags Flag Name Description ICMP_ECHO SEPARATE_MANAGEMENT_NETWORK Enables or disables Network Separation. Can only be disabled in the Ultra Secure Mode. (ULTRA_SECURE_MODE=YES). Default value: NO Possible values: YES/NO Polycom, Inc.
Page 259 Default: 0 (This value should never be used as the connection time is unlimited.) (If the SESSION_TIMEOUT_IN_MINUTES System Flag if configured, RMX Manager will disconnect after the specified period if there is no keyboard or mouse activity.) Polycom, Inc.
Page 260 Range: 0 - 480 USER_LOCKOUT_WINDOW_IN_MINU Defines the time period during which the three consecutive login failures occur. 0 means that three consecutive Login failures in any time period will result in User Lockout. Default value: 60 Range: 0 - 45000 Polycom, Inc.
Page 261 Manager global Address Book. When empty, the integration of RealPresence Resource Manager address book with RealPresence Collaboration Server is disabled. EXTERNAL_CONTENT_PAS The password associated with the user HW/VE SWORD name defined for RealPresence Collaboration Server in RealPresence Resource Manager server. Polycom, Inc.
Page 262 Default value: /PlcmWebServices Auto Layout – Default Layouts in CP Conferences Flags No. of Video Participants Auto Layout Flag Auto Layout Default Default Value PREDEFINED_AUTO_LAYOUT_0 CP_LAYOUT_1X1 PREDEFINED_AUTO_LAYOUT_1 PREDEFINED_AUTO_LAYOUT_2 PREDEFINED_AUTO_LAYOUT_3 CP_LAYOUT_1x2VER PREDEFINED_AUTO_LAYOUT_4 CP_LAYOUT_2X2 PREDEFINED_AUTO_LAYOUT_5 PREDEFINED_AUTO_LAYOUT_6 CP_LAYOUT_1P5 PREDEFINED_AUTO_LAYOUT_7 PREDEFINED_AUTO_LAYOUT_8 CP_LAYOUT_1P7 PREDEFINED_AUTO_LAYOUT_9 Polycom, Inc.
Page 263 Participants Auto Layout Flag Auto Layout Default Default Value PREDEFINED_AUTO_LAYOUT_10 CP_LAYOUT_2P8 PREDEFINED_AUTO_LAYOUT_11 PREDEFINED_AUTO_LAYOUT_12 CP_LAYOUT_1P12 PREDEFINED_AUTO_LAYOUT_13 PREDEFINED_AUTO_LAYOUT_14 PREDEFINED_AUTO_LAYOUT_15 PREDEFINED_AUTO_LAYOUT_16 PREDEFINED_AUTO_LAYOUT_17 PREDEFINED_AUTO_LAYOUT_18 PREDEFINED_AUTO_LAYOUT_19 PREDEFINED_AUTO_LAYOUT_20 Available Layout Flags No. of Cells Layout Flag Value Layout CP_LAYOUT_1X1 CP_LAYOUT_1X2 CP_LAYOUT_1X2HOR CP_LAYOUT_1x2VER CP_LAYOUT_2X1 CP_LAYOUT_1X2_FLEX Polycom, Inc.
Page 264 System Flags Available Layout Flags No. of Cells Layout Flag Value Layout CP_LAYOUT_1P2HOR CP_LAYOUT_1P2HOR_UP CP_LAYOUT_1P2VER CP_LAYOUT_1P2HOR_RIGHT_FLEX CP_LAYOUT_1P2HOR_LEFT_FLEX CP_LAYOUT_1P2HOR_UP_RIGHT_FLEX CP_LAYOUT_1P2HOR_UP_LEFT_FLEX CP_LAYOUT_2X2 CP_LAYOUT_1P3HOR CP_LAYOUT_1P3HOR_UP CP_LAYOUT_1P3VER CP_LAYOUT_2X2_UP_RIGHT_FLEX CP_LAYOUT_2X2_UP_LEFT_FLEX CP_LAYOUT_2X2_DOWN_RIGHT_FLEX CP_LAYOUT_2X2_DOWN_LEFT_FLEX CP_LAYOUT_2X2_RIGHT_FLEX CP_LAYOUT_2X2_LEFT_FLEX CP_LAYOUT_1P4HOR_UP CP_LAYOUT_1P4HOR CP_LAYOUT_1P4VER Polycom, Inc.
Page 265 System Flags Available Layout Flags No. of Cells Layout Flag Value Layout CP_LAYOUT_1P5 CP_LAYOUT_1P7 CP_LAYOUT_1P8UP CP_LAYOUT_1P8CENT CP_LAYOUT_1P8HOR_UP CP_LAYOUT_3X3 CP_LAYOUT_1TOP_LEFT_P8 CP_LAYOUT_2P8 CP_LAYOUT_2TOP_P8 CP_LAYOUT_1P12 CP_LAYOUT_4X4 CP_LAYOUT_4X5 Overlay Layouts CP_LAYOUT_OVERLAY_1P1 CP_LAYOUT_OVERLAY_1P2 CP_LAYOUT_OVERLAY_ITP CP_LAYOUT_OVERLAY_1P3 Polycom, Inc.
Page 266: Call Detail Records
Call Detail Records The Polycom® RealPresence® Collaboration Server (RMX) creates Call Detail Records (CDRs) for every conference started on it. This section discusses the CDR options that you can configure and the CDR tasks you may want to perform. CDR Options ●...
Page 267: View The Mcu Cdr List
Businesses that must generate video conferencing billing information or resource usage reports should retrieve and archive MCU CDRs on a periodic basis. You can retrieve and archive all available CDRs, which can then be used to generate billing information, resource usage reports and more by any third party applications. Polycom, Inc.
Page 268: Cdr Fields In Unformatted Files
This allows users with lower versions to retrieve CDR files that were created in higher versions. The Conference Summary Record The conference summary record (the first record in the unformatted CDR file) contains the following fields. Polycom, Inc.
Page 269 Indicates whether the GMT Offset is positive or negative. The possible values are: 0 - Offset is negative. GMT Offset will be subtracted from the GMT Time. 1 - Offset is positive. GMT Offset will be added to the GMT Time. Polycom, Inc.
Page 270 ● The event time. ● The structure length. This field is required for compatibility purposes, and always contains the value 0. For information of codes used for the various disconnection causes in event descriptions, see Disconnection Cause Values. Polycom, Inc.
Page 271 For more information about the fields, see Event Fields for Events 10, 101, 105 - DEFINED PARTICIPANT, USER ADD PARTICIPANT, USER UPDATE PARTICIPANT. Note: There is one event for each participant defined before the conference started. Polycom, Inc.
Page 272 CDR file each time the endpoint changes its connection bit rate. RATE For more information about the fields, see Event fields for Event 31 - PARTICIPANT CONNECTION RATE. EVENT NEW Information about the IPv6 address of the participant’s endpoint. UNDEFINED PARTY CONTINUE IPV6 ADDRESS Polycom, Inc.
Page 273 105 - DEFINED PARTICIPANT, USER ADD PARTICIPANT, USER UPDATE PARTICIPANT. USER SET END A user modified the conference end time. TIME For more information about the fields, see Event Fields for Event 106 - USER SET END TIME. Polycom, Inc.
Page 274 Additional information about a DEFINED PARTICIPANT event that includes PARTICIPANT the IPv6 addressing of the defined participant. CONTINUE PV6 For more details, see Event Fields for Events 2010, 2011, 2015 - DEFINED ADDRESS PARTICIPANT CONTINUE 1,USER ADD PARTICIPANT CONTINUE 1, USER UPDATE PARTICIPANT CONTINUE Polycom, Inc.
Page 275 CDR each time the value of one of the following conference fields is modified: • Conference Password • Chairperson Password • Info1, Info2 or Info3 • Billing Info These additional events only contain the value of the modified field. Polycom, Inc.
Page 276 23 - 512 kbps 24 - 768 kbps 26 - 1152 kbps 29 - 1472 kbps 32 - 96 kbps Line Rate (cont.) 33 - 1024 kbps 34 - 4096 kbps Restrict Mode Not supported. Always contains the value 0. Polycom, Inc.
Page 277 5 - The conference never started. 6 - The conference could not start due to a problem. 8 - An unknown error occurred. 9 - The conference was terminated by a participant using DTMF codes. Polycom, Inc.
Page 278 For more details refer to the Q.931 standard. Calling Participant The type of calling number, as follows: Number Type 0 - Unknown, default 1 - International 2 - National 3 - Network specific 4 - Subscriber 6 - Abbreviated Polycom, Inc.
Page 279 The telephone number used for dial-out. Phone Number Event fields for Event 4 - ISDN/PSTN CHANNEL DISCONNECTED Field Description Participant Name The participant name. Participant ID The identification number assigned to the participant by the MCU. Channel ID The channel identifier. Polycom, Inc.
Page 280 11 - Redialing Remote Note: This field is only relevant to ISDN-video participants. Capabilities The remote capabilities in H.221 format. Remote Note: This field is only relevant to ISDN-video participants. Communication The remote communication mode in H.221 format. Mode Polycom, Inc.
Page 281 Call Disconnection The disconnection cause. For more information about possible values, see Disconnection Cause Cause Values. Q931 Disconnect If the disconnection cause is “No Network Connection” or “Participant Hang Up”, then this Cause field indicates the Q931 disconnect cause. Polycom, Inc.
Page 282 255 - Taken from Network Service, default Notes: • For dial-in participants, the only possible value is 255 - Taken from Network Service • This field is only relevant to ISDN (audio/video) participants. Net Sub-Service Not supported. Name This field remains empty. Polycom, Inc.
Page 283 The data in this field should be ignored. For accurate rate information, see CDR event 31. Max Rate The maximum line rate achieved by the participant. The data in this field should be ignored. For accurate rate information, see CDR event 31. Polycom, Inc.
Page 284 7 - Deleted by a user 8 - Secondary. The participant could not connect the video channels and is connected via audio only 10 - Connected with problem 11 - Redialing Capabilities Not supported. Always contains the value 0. Polycom, Inc.
Page 285 Not supported. Always contains the value 0. Number of The number of channels being connected for this participant. Channels Note: This field is only relevant to ISDN (audio/video) participants. Net Channel Width Not supported. Always contains the value 0. Polycom, Inc.
Page 286 The meet-me per method, as follows: 3 - Meet-me per participant Network Type The type of network between the participant and the MCU, as follows: 0 - ISDN (audio/video) 2 - H.323 5 - SIP H.243 Password Not supported. This field remains empty. Polycom, Inc.
Page 287 For H.323 participants, the alias type, as follows: Participant Address 7 - E164 Type 8 - H.323 ID 13 - Email ID 14 - Participant number For SIP participants, the address type, as follows: 1 - SIP URI 2 - Tel URL Polycom, Inc.
Page 288 The type of DTMF failure, as follows: 2 - The participant did not enter the correct conference password. 6 - The participant did not enter the correct chairperson password. 12 - The participant did not enter the correct Conference ID. Polycom, Inc.
Page 289 The identity of the user sending a SIP message as it was verified by authentication. Charging Vector A collection of charging information. Preferred Identity The identity the user sending the SIP message wishes to be used for the P-Asserted-Header field that the trusted element will insert. Polycom, Inc.
Page 290 Event fields for Event 34 - PARTICIPANT MAXIMUM USAGE INFORMATION Field Description Participant Name The name of the participant. Participant ID The identification number assigned to the participant by the MCU. Maximum Bit Rate The maximum bit rate used by the participant during the call. Polycom, Inc.
Page 291 Negotiated reception line rate Transmit line rate Negotiated transmission line rate Uplink Video • Number of uplink streams Capabilities • Video stream (multiple streams):  Resolution width  resolution height  max frame rate  max line rate Polycom, Inc.
Page 292 The identification number of the participant who was moved, as assigned by the MCU. Destination Conf The name of the conference to which the participant was moved. Name Destination Conf ID The identification number of the conference to which the participant was moved. Polycom, Inc.
Page 293 255 - Unknown or not relevant Voice Mode Indicates whether or not the participant is an Audio Only participant, as follows: 0 - The participant is not an Audio Only participant 1 - The participant is an Audio Only participant 255 - Unknown Polycom, Inc.
Page 294 Note: This field is only relevant to dial-in participants. Meet Method The meet-me per method, as follows: 1 - Meet-me per MCU-Conference 3 - Meet-me per participant 4 - Meet-me per channel Note: This field is only relevant to dial-in participants. Polycom, Inc.
Page 295 In all other cases the address overrides the gatekeeper. Call Signaling Port Note: This field is only relevant to IP participants. The signaling port used for participant connection. A value of 65535 is ignored by MCU. Polycom, Inc.
Page 296 0 - The participant is not encrypted. 1 - The participant is encrypted. 2 - Auto. The conference encryption setting is applied to the participant. Participant Name The name of the participant. Participant ID The identification number assigned to the participant by the MCU. Polycom, Inc.
Page 297 Currently the only value is 0. Allow Undefined Indicates whether or not undefined dial-in participants can connect to the conference. Participants Currently the only value is: 1 - Undefined participants can connect to the conference Polycom, Inc.
Page 298 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. Polycom, Inc.
Page 299 Mux Unit ID Not supported. Always contains the value 0. Audio Codec Board Not supported. Always contains the value 0. Audio Codec Unit Not supported. Always contains the value 0. Audio Bridge Board Not supported. Always contains the value 0. Polycom, Inc.
Page 300 H.243 Password Not supported. This field remains empty. Chair Not supported. Always contains the value 0. Video Protocol The video protocol used by the participant, as follows: 1 - H.261 2 - H.263 4 - H.264 255 - Auto Polycom, Inc.
Page 301 H.323 Participant Note: This field is only relevant to IP participants. Alias Name/SIP For H.323 participants: Participant Address The participant alias. May contain up to 512 characters. For SIP participants: The participant address. May contain up to 80 characters. Polycom, Inc.
Page 302 Conference Password The conference password. An empty field “” means that no conference password was assigned to the conference. Chairperson Password The chairperson password. An empty field “” means that no chairperson password was assigned to the conference. Polycom, Inc.
Page 303 Indicates the conference encryption setting, as follows: 0 - The conference is not encrypted. 1 - The conference is encrypted. Event Fields for Event 11001 - CONFERENCE START CONTINUE 10 Field Description Display Name The Display Name of the conference. Polycom, Inc.
Page 304 If the ENABLE_CYCLIC_FILE_SYSTEM_ALARMS is set to YES (default setting when ULTRA_SECURE_MODE System Flag is set to YES) and a Cyclic File reaches a file retention time or file storage capacity limit, the user is alerted that log files need to be backed up. Polycom, Inc.
Page 305 Note: Applicable to Collaboration Servers 2000/4000 Central signaling component failure Possible explanations: • Central signaling component failure; unit type: [NonComponent\CSMngnt\CSH323\ Polycom® ContentConnect™IP] • Central signaling component failure; unit type: (invalid: [NonComponent\CSMngnt\CSH323\ ContentConnect IP]) • Central signaling component failure - Invalid failure type. Unit id: [id],...
Page 306 DNS not configured in IP Network Configure the DNS in the IP Network Services. Service Encryption Server Error. Failed to FIPS 140 test failed while generating the new encryption key. generate the encryption key Error in external database certificate Polycom, Inc.
Page 307 Failed to establish connection to server, url = [url]. Failed to connect to recording device The MCU could not connect to the defined recording device due to configuration error or network error. Failed to connect to SIP registrar Cannot establish connection with SIP registrar. Polycom, Inc.
Page 308 Out of file system space in [file system path]; Free space: [free space percentage]% ([free space] Blocks) - Minimum free space required: [minimum free space percentage]% ([minimum free space] Blocks). FIPS 140 failure FIPS 140 test result not received Polycom, Inc.
Page 309 Hard disk error Hard disk not responding. Hot Backup: Master-Slave Possible reasons: configuration conflict. • When both the MCUs are configured as Master or as Slave • The slave Collaboration Server is defined with the same IP as the Master. Polycom, Inc.
Page 310 Management Network not configured Configure the Management Network. Missing Central Signaling configuration Configure the central signaling. Missing Central Signaling IP configuration MPL startup failure. Authentication not Authentication was not received from Switch. Check the switch card. received. Polycom, Inc.
Page 311 No License for ISDN/PSTN. Please Configure the ISDN (audio/video) Network Service. activate the RTM ISDN card through Note: Applicable to Collaboration Servers 2000/4000/1800 Polycom website No response from Central Signaling No connection with central signaling. No response from RTM ISDN card Note: Applicable to Collaboration Servers 2000/4000/1800 No RTM-LAN or RTM-ISDN installed.
Page 312 Reset is completed Collaboration Server fails to connect to Active Directory server. Collaboration Server is uploading the version file. To cancel the upload and the upgrade, reset the Collaboration Server Collaboration Server user/password list will be reset Polycom, Inc.
Page 313 • Wrong certificate file type. Only files of the following types can be loaded to the system: rootCA.pem, pkey.pem and cert.pem and certPassword.txt • The contents of the certificate file does not match the system parameters Polycom, Inc.
Page 314 Temperature Level - Critical Temperature has reached a critical level. Temperature Level - Major Temperature has reached a problematic level and requires attention. The Log file system is disabled because of high system CPU usage The MCCF channel is not connected Polycom, Inc.
Page 315 Voltage problem Possible reasons for the problem: • Card voltage problem. • Shelf voltage problem. • Voltage problem Warning: Upgrade started and SAFE Upgrade protection is turned OFF Yellow Alarm Problem sending/receiving data from/to network. Check the cables. Polycom, Inc.
Page 316 The required control ports exceed the number of ports allocated to control data in fixed ports. H323 call close. No port left for videocont The required video content ports exceed the number of ports allocated to video content in fixed ports. Polycom, Inc.
Page 317 H323 call closed. Audio channels didn't The endpoint did not open the audio channel. open before timeout H323 call closed. Remote sent bad There was a problem in the capabilities sent by the endpoint. capability Polycom, Inc.
Page 318 The request could not be completed due to a conflict with the current state of the resource. SIP client error 411 The endpoint sent a SIP Client Error 411 (Length Required) response. The server refuses to accept the request without a defined Content Length. Polycom, Inc.
Page 319 The requested resource is no longer available at the Server and no forwarding address is known. SIP moved permanently The endpoint moved permanently. The user can no longer be found at the address in the Request-URI. SIP moved temporarily The remote endpoint moved temporarily. Polycom, Inc.
Page 320 SIP server error 504 The SIP server sent a SIP Server Error 504 (Server Time-out) response. The server did not receive a timely response from an external server it accessed in attempting to process the request. Polycom, Inc.
Page 321 Misdialed trunk prefix A trunk prefix has erroneously been included in the called user number. (national use) Channel Unacceptable The sending entity in the call does not accept the channel most recently identified. Polycom, Inc.
Page 322 No B-Channels are available for the call. Available Network Out-of-Order Network is out-of-order because due to a major malfunction. Permanent Frame Mode A permanent frame mode connection is out-of-service. This cause is Connection Out-of-Service part of a STATUS message. Polycom, Inc.
Page 323 The service or option is unavailable. No other disconnection cause Available, Unspecified applies. Bearer Capability Not The requested bearer capability is not supported. Implemented Channel Type Not The requested channel type is not supported. Implemented Requested Facility Not The requested supplementary service is not supported. Implemented Polycom, Inc.
Page 324 Implemented Message is Not Compatible An unexpected message or unrecognized message incompatible with with the Call State, or the the call state has been received Message Type is Non-Existent or Not Implemented Polycom, Inc.
Page 325 H323 call close. No port left for FECC H323 call close. No control port left H323 call close. No port left for video content A common key exchange algorithm could not be established between the MCU and the remote device Polycom, Inc.
Page 326 H323 call close. Capabilities not accepted by remote H323 failure H323 call close. Remote stop responding H323 call close. Master slave problem SIP timer popped out SIP card rejected channels SIP capabilities don’t match SIP remote closed call Polycom, Inc.
Page 327 SIP client error 406 SIP client error 407 SIP request timeout SIP client error 409 SIP gone SIP client error 411 SIP client error 413 SIP client error 414 SIP unsupported media type SIP client error 420 SIP temporarily not available Polycom, Inc.
Page 328 SIP server error 500 SIP server error 501 SIP server error 502 SIP server error 503 SIP server error 504 SIP server error 505 SIP busy everywhere SIP global failure 603 SIP global failure 604 SIP global failure 606 Polycom, Inc.
Page 329 Hardware Monitoring For the Appliance Edition of the Polycom® RealPresence® Collaboration Server (RMX) 1800/2000/4000, use the Hardware Monitor to monitor the status and properties of MCU hardware components. Viewing the Status of the Hardware Components For RealPresence Collaboration Server 2000/4000 models (also called MCUs), the Hardware Monitor...
Page 330 4 Select the Event Log tab (if available) to view a log of events recorded by the MCU on the card. 5 Select the Active Alarms tab (if available) to view alarms related to the card, i.e. temperatures and main power sensors. 6 Click Close to return to the Hardware Monitor. Polycom, Inc.
Page 331 1 In the RMX Management section, click Hardware Monitor 2 In the Hardware Monitor, select the MCU or video card of interest. 3 Right-click and select Properties. 4 Click Event Log to view a log of events that were recorded by the MCU. Polycom, Inc.
Page 332 2 In the Hardware Monitor, select the MCU of interest (for example, Slot 0 RMX 4000). 3 Right-click and select Properties. 4 Select the Active Alarms tab to view alarms for the MCU, such as temperatures and main power sensors. Polycom, Inc.
Page 333 Mode. Entering this mode causes the MCU to terminate all active conferences and prohibits conferences from being started. To access an MCU in Diagnostic Mode, the administrator must use the MCU Shelf Management IP address. To run diagnostics on a card: 1 In the RMX Management section, click Hardware Monitor Polycom, Inc.
Page 334 9 To exit Diagnostic Mode and reset the MCU, in the Hardware Monitor, click ISDN Diagnostic on RMX 1800 RMX1800 MCUs support the following diagnostic items: ● RTM DSP Memory-Data Bus ● RTM DSP Memory-Address Bus ● RTM DSP Memory-Energy ● RTM DSP Memory-Integrity ● RTM DSP Core clock Polycom, Inc.
Page 335 If you perform diagnostics on an RMX1800 MCU that has ISDN cards through the USB utility, the diagnostic program will check all items including DSP, system memory, and ISDN cards. The program will take about 1 hour to complete all tests. Polycom, Inc.
Page 336 Restore RealPresence Collaboration Server Defaults Administrators can erase the current Polycom® RealPresence® Collaboration Server configurations and restore default system settings. Two options are available: ● Standard restore Delete customer conferencing entities and keep only system default conferencing entities. However, the management network service and license info are not deleted.
Page 337 ● Using the RMX Web Client (Recommended). ● Using the USB key. Use the USB key for system restore only when you cannot do it from the system Web Client. For example, when the Web Client is inaccessible. Polycom, Inc.
Page 338 Backup. The system initiates the backup of the Collaboration Server configuration files. When the backup completes, a confirmation dialog box is displayed. To cancel the backup, click Close. 5 Click Yes to restore the Collaboration Server. Polycom, Inc.
Page 339 ISDN (audio/video) Network Services Overview To perform a comprehensive restore using the USB key (1800): 1 Insert the USB key that is included with the system into your workstation:  In Windows XP: The Polycom Documentation option is automatically selected. Click OK. Polycom, Inc.
Page 340 2 Double-click the index.hta file. 3 In the Language Menu window, click the hyperlink for the required documentation language. 4 In the Polycom End User Licenses Agreement window, read the agreement and click the Accept Agreement button. In the Product Type Selection window, click RealPresence Collaboration Server 1800.
Page 341 Step 1. 14 Restart the Collaboration Server. (If the Collaboration Server is unresponsive after these procedures a further restart may be necessary.) 15 Enable Secured Communication and re-apply the Certification procedures. For more information see Certificate Management. Polycom, Inc.
Page 342 Appendix - Polycom Lab Features Polycom enables examining experimental features of Polycom RealPresence Collaboration Server. These features may be later incorporated as constant features, but at this point are neither tested nor supported. Only an Administrator may access the experimental features, provided the Collaboration Server is in experimental mode.
Page 343  Feature Unit Tested  Feature Unit and Product Regression Tested  Full Feature Unit, Product Regression, and Solution Tested To find out more about this Polycom Lab feature or provide feedback on this feature, contact Polycom Support. Description of Feature The term Discussion Mode refers to the Collaboration Server ability to identify conferencing scenarios, in which either one or two participants are the main/only speaker(s).
Page 344 Appendix - Polycom Lab Features Layouts Used in Discussion Mode Number of Active Speakers Layout Name Layout Discussion Mode is triggered once the number of participants reaches a minimum, and one of the participants becomes the active speaker by speaking over a time interval (see System Flags below).
Page 345 Appendix - Polycom Lab Features System Flags System Flags for Discussion Mode Activation Flag Name Flag Description DISCUSSION_DISPLAYED_PA The minimal visual participants required to trigger Discussion Mode. RTICIPNATS_TO_START Visual participants are video participants with an active video, or one of the two static video participants included in the conference layout.
Page 346 We encourage you to try them out, but because they are not fully tested or supported, please don't deploy them in production environments. Polycom Lab features are experimental and may or may not become official features in a future release. This brief specification documents the following Polycom Lab Feature.
Page 347 Telepresence room. ● A participant forced in the layout is always displayed, even if its video is inactive. Enable and Disable this Polycom Lab Feature To enable/disable excluding inactive-video participants from layout: 1 Right-click on a CP Only or Mixed CP and AVC conferencing profile, and select Profile Properties.
Page 348 We encourage you to try them out, but because they are not fully tested or supported, please don't deploy them in production environments. Polycom Lab features are experimental and may or may not become official features in a future release. This brief specification documents the following Polycom Lab Feature.
Page 349 Appendix - Polycom Lab Features General Guidelines ● The site name display utilizes the message overlay mechanism, thus both are enabled/disabled simultaneously, and conform to identical settings, such as color, font size, and horizontal location. ● Message overlay is replaced by site name upon participant joining/leaving for the specified duration, after which the message overlay display is renewed for static message overlay.
Page 350 We encourage you to try them out, but because they are not fully tested or supported, please don't deploy them in production environments. Polycom Lab features are experimental and may or may not become official features in a future release. This brief specification documents the following Polycom Lab Feature.
Page 351  Feature Unit Tested  Feature Unit and Product Regression Tested  Full Feature Unit, Product Regression, and Solution Tested To find out more about this Polycom Lab feature or provide feedback on this feature, contact Polycom Support. Description of Feature When connecting a conference running on Polycom RealPresence Collaboration Server via an Entry Queue, a still slide is used, which up until version 8.7 could be replaced by a different still slide.
Page 352 Range: YES (default), NO Note: Set this flag to NO if you experience difficulties in viewing motion slides in TIP endpoints connected to your Collaboration Server. To Enable and Disable this Polycom Lab Feature See the last prerequisite below. Prerequisites ●...
Page 353 Appendix - Polycom Lab Features Polycom Labs - general check-box Feature check-box Procedures To select a video clip to be used for an IVR service: 1 Select IVR Service Properties > Video Services. Polycom, Inc.
Page 354 Appendix - Polycom Lab Features 2 From the Video Welcome Slide list, select the video clip to be used for the IVR service. Polycom, Inc.
Page 355 Appendix - Secure Communication Mode Polycom® RealPresence Collaboration Server can be configured to work in Secure Mode or Ultra Secure Mode. For more information see Ultra Secure Mode Flags Specific to Maximum Security Environments - Ultra Secure Mode. In Secured mode the Collaboration Server and the RMX Web Client are configured to work with SSL/TLS.
Page 356 Adding Certificates to the Certificate Repository. Note: Certificate Vulnerability due to Restoring Factory Defaults Certificates are deleted when an administrator performs a Restore Factory Defaults with the Comprehensive Restore option selected. For details see Appendix - Restore Defaults from USB. Polycom, Inc.
Page 357 Communication check box. This box is selected by default when the MCU is in Ultra Secure Mode. 4 Select the Certificate Validation mode by checking or clearing the Skip certificate validation for user logging session field as set out in the following table: Polycom, Inc.
Page 358 Management Network is accessible only via the dedicated LAN 3 port. For more information see Connect the Alternate Management Network (2000/4000). Note: Connection of Alternate Management Network Connection to the Alternate Management Network bypasses LAN and Firewall security. Strict control of access to LAN 3 port is recommended. Polycom, Inc.
Page 359 Note: Feature Applicability External Database Authentication is not supported in Collaboration Server 1800. Polycom® RealPresence® Collaboration Servers 1800/2000/4000/Virtual Edition 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 360 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. Polycom, Inc.
Page 361 (corresponding to the User Defined 1 field in the Profile properties) and user’s PIN code. The same user definitions can be used for conference access authentication, that is, to determine who can join the conference as a participant and who as a chairperson. Polycom, Inc.
Page 362 (according to the conference ID), his/her parameters (as defined in the database) can be sent to the MCU in the same response granting the participant the right to start a new ongoing conference. These parameters are: Polycom, Inc.
Page 363 ● An external database application with a database containing Conference IDs associated with participants and their relevant properties. ● Define the flags required to access the external database in System Configuration. For more information, see MCU Configuration to Communicate with an External Database Application Polycom, Inc.
Page 364 (Always) Once the conference is created either via an Ad Hoc Entry Queue, or a standard ongoing conference, the right to join the conference is authenticated with the external database application for all participants connecting to the conference. Polycom, Inc.
Page 365  If the correct chairperson password is entered, the participant is connected to the conference as its chairperson.  If the wrong password is entered, he/she is disconnected from the conference. To enable conference access validation for all participants the following conferencing components are required: Polycom, Inc.
Page 366 ● If the chairperson identifier is entered, the participant is prompted to enter the chairperson password. ● When the participant enters the chairperson password or his/her personal password, it is sent to the external database application for validation.  If the password is incorrect the participant is disconnected from the MCU. Polycom, Inc.
Page 367 Set the Entry Queue IVR Service to send authentication requests to the external database application to verify the participant’s right to start a new conference according to the Conference ID entered by the participant. For details, see Enabling External Database Validation for Starting New Ongoing Conferences Polycom, Inc.
Page 368  Participant Information, such as the participant E-mail. These fields correspond to Info 1, 2, 3 and 4 fields in the Participant Properties - Information dialog box. 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. Polycom, Inc.
Page 369 EXTERNAL_DB_PASSWORD The password associated with the user name defined for the MCU in the external database application. EXTERNAL_DB_DIRECTORY The URL of the external database application. 3 Click OK. 4 Reset the MCU for flag changes to take effect. Polycom, Inc.
Page 370 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. » Set the External Server Authentication field to Numeric ID. Polycom, Inc.
Page 371 ● Set the External Server Authentication field to:  Always - To validate the participant’s right to join an ongoing conference for all participants ▪ Upon Request - To validate the participant’s right to join an ongoing conference as chairperson Polycom, Inc.
Page 372 Appendix - Media Traffic Shaping Polycom integrated traffic shaping capabilities into the RealPresence Collaboration Server to enable deploying Collaboration Server systems in networks limiting packet bursts within 100ms time intervals (or more). Setting router policies to limiting of bandwidth within a time interval, causes the router to drop packets exceeding the allowed bandwidth within this interval.
Page 373 HD1080p Audio Only * Assuming conference bit rate ≤ 1024 Kbps System Limitation Currently, Traffic shaping is limited to conferences using a minimum of 384 bit rate. Under this bit rate, the user might experience bursts of data. Polycom, Inc.
Page 374 ● A Main MCU - May be either Collaboration Server Virtual Edition, or one of the Hardware MCUs, i.e. Collaboration Servers 1800/2000/4000. ● Soft Blades - Polycom Soft Blade proprietary software installed on a virtual machine (currently only VMWare machines). Each Soft Blade is assigned to a Main MCU.
Page 375 ● Deployment of Soft Blades in a Modular MCU ● Monitoring Modular MCU Components ● RDP Content ● Modular MCU Resource Consumption and Management ● Modular MCU Security Aspects ● Modular MCU Logger ● Modular MCU Upgrade Process Polycom, Inc.
Page 376 Main MCU. 4 Via putty, log into the intended Soft Blade machine via the console wizard, with polycom as both username and password, to display the Minion Setup menu.
Page 377 In the System Monitor at the Main MCU, the Soft Blade Status changes to Installing. At this point its deployment begins, and assuming a smooth process through Installing and Initializing, the Soft Blade Status at the System Monitor becomes Ready, which indicates the Soft Blade is now operational. Polycom, Inc.
Page 378 Supported on the Skype for Business Front End server. 15 Change cascade link from Attendees to Presenters in Skype for Business. For more information, Change a Cascade Link (Polycom Participants) from an Attendee to a Presenter in Skype for Business.
Page 379 ● When the Main MCU cannot communicate with the Soft Blade application, though it does manage to ping it - Soft Blade <name> status has changed to Faulty. ● When the Main MCU cannot communicate with the Soft Blade application, nor ping it - Soft Blade <name> status has changed to Disconnected. Polycom, Inc.
Page 380 Soft Blade erased ** Operational Phase Installing The Soft Blade Installation is successfully completed. Initializing installation is Installation fails. Faulty launched Initializing Initializing the Soft Initialization is successfully completed. Ready Blade Initialization fails. Faulty (ping) Disconnected (no ping) Polycom, Inc.
Page 381 Initiating a Restore to Factory Defaults operation on a Soft Blade, results in the Soft Blade requiring re-authentication before resuming its normal operation (see the Pend Authentication state in the State Machine above). Using Backup of an operational MMCU, to Restore on a different machine, requires re-authentication of the assigned Soft Blades. Polycom, Inc.
Page 382 RDP and hence it uses the H.239 (for H.323 endpoints) or BFCP (for SIP endpoints). In order to enable content sharing between Skype for Business clients and standard room endpoints, RealPresence Collaboration Server can be used (when configured to work in Modular MCU mode). Polycom, Inc.
Page 383 (VMR) and the Microsoft Application Sharing MCU (ASMCU). This resource resides on a soft blade MMCU. For Polycom RealConnect calls to work, set ‘AllowMultiView’ to TRUE on the Skype for Business Front End Server. This allows participants to connect and receive multiple video streams.
Page 384 Enabling RDP content needs configurations on DMA and IP Network Service. Polycom MCU Video Quality Dialog on DMA Select Enable MS RDP content on DMA through Polycom MCU Video Quality > Content Video Definition. Note: Enable MS RDP on DMA Before enabling MS RDP on DMA, make sue no ContentConnect server is configured in DMA.
Page 385 SIP Password Optional. DMA server password. Change a Cascade Link (Polycom Participants) from an Attendee to a Presenter in Skype for Business Content can only be shared by the cascade link who are presenters and not attendees in the Skype for Business.
Page 386 Two separate resource reports are available, as before, only now they are separated into a report on the Main MCU, and a report on the Soft Blades assigned to that Main MCU. These reports are: ● The bar-graph representation: Polycom, Inc.
Page 387 Soft Blades in the MMCU, to yield the general Soft Blades resource pool usage information. The TC also keeps track of the resource pool on the Main MCU, to be able to pass on this information to external entities. Polycom, Inc.
Page 388 Translator Machines. It also allows the Main MCU to gather the Translators/Soft Blades logs from a centralized gathering point. Logger Guidelines ● The Main MCU writes logs into the regular Main MCU log file, including API messages sent to the Soft Blades. Polycom, Inc.
Page 389 Logging volume varies according to the logging level. However, it is designed so that, assuming a total of 15GB storage, approximately one month worth of logs can be stored. To determine the configuration settings for the Soft Blades: 1 In the Collaboration Server main menu, select Administration > Tools > Logger Configuration. Polycom, Inc.
Page 390 3 Click OK to save and return to the Logger Configuration dialog, and then OK to exit. Logs at the Soft Blades The Soft Blade log files are located under /opt/polycom/Translator/Logs. Note: Salt Logs Location Salt logs are stored in a dedicated folder under that location.
Page 391 You can upgrade modular MCU in the same way of upgrading non-modular MCU, the only difference is that upgrading modular-MCU may take extra 1 or 2 minutes. and you can monitor the soft blades upgrade status on the MMCU System Monitor pane. Polycom, Inc.
Page 392  You can manually install the new version software on soft blades, which failed to be upgraded. For information of installing soft blades, see Deployment of Soft Blades in a Modular MCU.  Only the soft blades are upgraded successfully will work actively with the modular MCU. Polycom, Inc.
Page 393 (delay) in connections and low video quality resulting from the reformatting of video and audio content. Polycom’s solution is to allow Polycom® RealPresence® Collaboration Server to natively inter-operate with Cisco TelePresence Systems, ensuring optimum quality multi-screen, multipoint calls between: ●...
Page 394  Model 1: Mixed Polycom and Cisco infrastructure at one of the companies, Cisco only infrastructure at the other.  Model 2: Polycom only infrastructure at one of the companies, Cisco only infrastructure at the other. Single Company Model - Polycom and Cisco...
Page 395 Appendix - Polycom Open Collaboration Network (POCN) Single company with Polycom and Cisco Infrastructure - Polycom endpoints using SIP Polycom endpoints can also connect to Entry Queues, Meeting Rooms and conferences using all protocols, including TIP and SIP. The following table lists components and versions of the Collaboration Server and Cisco Telepresence Systems (CTS) Integration Solution Architecture.
Page 396 Appendix - Polycom Open Collaboration Network (POCN) Solution Architecture Components Component Version Description Cisco Unified 8.5, 8.6 Network-based Presence and Instant Messaging. Presence Cisco Unified 8.0, 8.5 Call distributor (ACD), interactive voice Contact Center response (IVR) and computer telephony integration (CTI).
Page 397 Telephony, desktop and room systems. • H.323 endpoints must register to the IOS gatekeeper. • Polycom SIP endpoints must register to DMA as SIP Proxy when DMA is used. • H.323 endpoints must register to the IOS gatekeeper. Call Flow - Multipoint Call with DMA In this example: ●...
Page 398 Appendix - Polycom Open Collaboration Network (POCN) Call Flow - Multipoint Call without DMA In this example: ● Collaboration Server prefix in the gatekeeper: 72 ● CUCM: According to its Dial Plan forwards calls with prefix 72 to the Collaboration Server...
Page 399 ● Model 1:  Company A has a Polycom only environment.  Company B has a Cisco only Environment. ● Model 2:  Company A has a mixed Polycom and Cisco environment.  Company B has a Cisco only Environment. Polycom, Inc.
Page 400 ● Collaboration Server ● MLA ● Resource Manager Gatekeeper (for Collaboration Server Virtual Edition) ● Polycom telephony and desktop endpoints. The roles of the Polycom components are described in the Polycom Equipment section of the Solution Architecture Components table. Company B - has deployed a Cisco solution including: ●...
Page 401 Appendix - Polycom Open Collaboration Network (POCN) Company to Company via Service Provider - Model 1 Call Flows - Multipoint Call via Service Provider Model 1 In this example: ● Collaboration Server prefix in the gatekeeper: 72 ● Virtual Meeting Room in DMA: 725123 ●...
Page 402 Appendix - Polycom Open Collaboration Network (POCN) Call Flow - Multipoint Call via Service Provider Model 2 The deployment architecture in Deployment Architecture Composition shows two companies: Company A and Company B. Company A - has the same deployment architecture as shown in...
Page 403 Appendix - Polycom Open Collaboration Network (POCN) Deployment Architecture Composition Company A For a full description of Company A’s deployment, see Single Company Model - Polycom and Cisco Infrastructure. Differing or additional configuration requirements for each element of this deployment model are listed below: Polycom, Inc.
Page 404 Appendix - Polycom Open Collaboration Network (POCN) Company A Solution Architecture Components Component Version Description CISCO Equipment CUCM Cisco Unified Communication Manager: CUCM must be configured with a SIP trunk to the Service Provider’s SBC. Polycom Equipment Collaboration Server 7.6.x and up...
Page 405 Standalone Polycom Resource Manager/DMA System as a Gatekeeper The Polycom Resource Manager/DMA system can be used as the only gatekeeper for the network. Bandwidth and call admission control of endpoints registered with the DMA/Resource Manager system is split between the DMA/Resource Manager system and the CUCM.
Page 406 Neighbored Cisco IOS and Polycom Resource Manager Gatekeepers. The Polycom DMA system can be configured as a SIP proxy and registrar for the environment. When used as a SIP peer, the DMA system can host video calls between Cisco endpoints that are registered with the CUCM and Polycom SIP endpoints that are registered with the DMA system.
Page 407 Environments, Configure the Cisco IOS Gatekeeper for use with a Resource Manager System. Polycom Equipment The following table lists the Polycom products supported within the various Deployment Architecture. Only Collaboration Server configurations are described in detail in this document. Configuration procedures for all other solution components are described in the Polycom Unified Communications Deployment Guide for Cisco Environments.
Page 408 Server. 1 Configuring DMA to route SIP calls to CUCM 2 Configuring a Virtual Meeting Room (VMR) The procedures for configuring DMA are described in detail in Polycom Unified Communications Deployment Guide for Cisco Environments. Configuring the Resource Manager 1 Configuring Resource Manager to route H.323 calls to Collaboration Server...
Page 409 Configuring TIP endpoints to register to: c DMA d CUCM The procedures for configuring TIP- enabled endpoints are described in detail in Polycom Unified Communications Deployment Guide for Cisco Environments. Configuring Entry Queues and IVR Services Conference IVR and Entry Queue/Virtual Entry Queues are supported with AVC TIP protocol in conferences that include both TIP-enabled and non-TIP-enabled endpoints.
Page 410 The configuration process is the same for TIP and non-TIP enabled Conferences and Entry Queues. Content Polycom and Cisco endpoints can share Content within a Cisco TelePresence environment. The content sharing experience depends on whether the endpoints are registered with the DMA or CUCM.
Page 411 Appendix - Polycom Open Collaboration Network (POCN)  Supported on HDX, Polycom ITP and Cisco CTS systems. ● The following content compatibility options are available:  None (TIP not enabled) – TIP endpoints cannot join the conference.  Prefer TIP - Both TIP and non-TIP endpoints can share content via H.264, base profile, using resolution and rate as described above.
Page 412 Appendix - Polycom Open Collaboration Network (POCN) b The Port field must be set to it’s default value: 5060. DMA and CUCM use this port number by default. 7 In the Outbound Proxy Servers table: a Enter the IP address in the Server IP Address or Name field (the same value in Step 6a).
Page 413 Appendix - Polycom Open Collaboration Network (POCN) Procedure 4: Configure a TIP Enabled Profile on the Collaboration Server TIP enabled profiles must be used for the Entry Queues and Meeting Rooms defined on the Collaboration Server. (Different Profiles can be assigned to Entry Queues and Meeting Rooms, however they must be TIP enabled.) When TIP is enabled in the Profile, Gathering Settings and Message Overlay options are disabled.
Page 414 Appendix - Polycom Open Collaboration Network (POCN) 3 Open the Advanced tab. Polycom, Inc.
Page 415 Appendix - Polycom Open Collaboration Network (POCN) 4 Select Prefer TIP as the TIP Compatibility mode. To view its behavior, see the Content Sharing Behavior table at the end of this procedure. 5 Open the Video Quality tab. Polycom, Inc.
Page 416 Appendix - Polycom Open Collaboration Network (POCN) Content Settings is disabled if TIP Compatibility is set to Prefer TIP in the Advanced tab. For more information on content in TIP environments, see Content Sharing Behavior. 6 Open the Video Settings tab.
Page 417 Appendix - Polycom Open Collaboration Network (POCN) 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. Procedure 5: Configuring an Ad Hoc Entry Queue on the...
Page 418 Appendix - Polycom Open Collaboration Network (POCN) 3 Ensure that the Entry Queue is designated as the Transit Entry Queue as described in Transit Entry Queue. Procedure 6: Configuring a Meeting Room on the Collaboration Server The Profile for the Meeting Room must be TIP enabled as described in Procedure 4.
Page 419  Video Protocol is set to Auto or at least H.264. Collaboration with Microsoft and Cisco This solution enables Polycom, Microsoft and Cisco users, each within their own environment, to participate in the same conference running on an Collaboration Server.
Page 420 Single company with Polycom and Cisco Infrastructure - Polycom endpoints using SIP shows a company that has a mixture of Polycom, Cisco and Microsoft endpoints, room systems and telephony equipment that needs to enable multipoint calls between all its video and audio endpoints using the Collaboration Server as the conference bridge.
Page 421 Appendix - Polycom Open Collaboration Network (POCN) POCN Polycom, Microsoft and Cisco Infrastructure. Solution Architecture POCN Polycom, Microsoft and Cisco Infrastructure. Solution Architecture components Component Version Polycom 3.0.5 Polycom® RealPresence® Media Suite Resource Manager 5.2.3, 6.0.1 ITP (OTX, RPX, ATX, TPX) 3.0.5...
Page 422 Appendix - Polycom Open Collaboration Network (POCN) POCN Polycom, Microsoft and Cisco Infrastructure. Solution Architecture components Component Version Outlook 2010 14.0.6112.5000 Cisco CUCM 8.5, 8.6.2 Cisco Unified Personal communicator 8.5(2),8.5(5) Cisco Unified IP Phones 7960, 7961, 7962, 7965, 7975 CUCM 8.5 / CUCM 8.6(2) Compatible 1.7.4, 1.8.1...
Page 423 When used as a SIP peer, the DMA system can host video calls between Cisco endpoints that are registered with the CUCM, Lync Clients that are registered with the Lync Server and Polycom endpoints that are registered with the DMA system.
Page 424 Microsoft Lync Server Microsoft Lync Server manages Presence for each registered Polycom endpoint and enables video calls between Lync Clients and Polycom endpoints allowing Lync contacts to be called without needing to know their addresses. RTV video, MS-ICE and Lync-hosted conferencing are supported when Polycom endpoints are registered to Lync Server.
Page 425 TIP Layout Support & Resource Usage Cisco Telepresence endpoints using TIP protocol support only one (CTS 1000) or three (CTS 3000) display screens. Therefore, Polycom Telepresence endpoints will adjust their display to use one or three screens as follows: ● OTX system - Works with three screens, therefore no adjustment is required and it should be set to work in room switch Telepresence Layout Mode (while avoiding zooming in/out) ●...
Page 426 Carry out the following steps to configure the various system components to enable TIP. To configure the Microsoft, Cisco and Polycom components: 1 Configure a SIP Trunk connection between the Polycom DMA system and the Cisco Unified Communications Manager (CUCM).
Page 427  Deployment into Lync Environments.  Polycom Unified Communications Deployment Guide for Microsoft Environments, Configuring Your Collaboration Server System for use with the Lync Server. 3 Register the Collaboration Server with the Lync Server. a In the IP Network Services Properties dialog, select the SIP Servers tab.
Page 428 FORCE_2048_FOR_PLCM_TIP - Forces a line rate of 2048kbps for all Polycom TIP-enabled endpoints connecting to the TIP-enabled Telepresence conference. NO_FORCE - No forcing is applied, and Polycom TIP-enabled endpoints can connect to the TIP-enabled Telepresence conference at any line rate or resolution.
Page 429 For more information see the Polycom® DMA™ 7000 System Operations Guide. 15 Open MLA to configure ITP Layouts 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 430 Appendix - Polycom Open Collaboration Network (POCN) c Select the Advanced tab. d Select Prefer TIP as TIP Compatibility mode. To view its behavior, see the Content Sharing Behavior table listed below. Note: Feature Applicability in TIP Enabled Conferencing When Prefer TIP is selected, Video Switching, Gathering Settings, Skins, Message Overlay, Site Names and Network Indications are disabled.
Page 431 Appendix - Polycom Open Collaboration Network (POCN) Content Sharing Behavior The following tables 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 ...
Page 432 Appendix - Polycom Open Collaboration Network (POCN) TIP Compatibility - Prefer TIP Content Receiver Prefer TIP HDX / ITP Content HDX / ITP Media: H.264 Sender Flow Control: H.323 via H.239 SIP via BFCP CTS* TIP via Auto Collaboration * CTS Version 1.9.1 and higher support H.264 Content.
Page 433 Appendix - Polycom Open Collaboration Network (POCN)  Cisco CUCM Version 9.0  Cisco TPC Version 2.3  Cisco endpoints running Version 1.9.1  C20, C40, C60, and C90 running TC5  CTS500  CTS1310  CTS3010 To enable DTLS negotiation for content encryption: 1 In a new or existing Profile, open the Advanced tab.
Page 434 Appendix - Polycom Open Collaboration Network (POCN) Content Settings is disabled if TIP Compatibility is set to Prefer TIP in the Advanced tab. b Open the Video Settings tab. Polycom, Inc.
Page 435 Creating a New Meeting Room. 5 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. Resolution Configuration The resolution configuration dialog is not applicable to TIP-enabled conferences as it uses fixed settings.
Page 436 To register the various types endpoints: 1 Configure HDX endpoints to register to Lync Server. The procedures for configuring HDX endpoints are described in detail in the Polycom Unified Communications Deployment Guide for Microsoft Environments. 2 Configure H.323 endpoints to register to DMA as SIP Proxy The procedures for configuring SIP endpoints are described in detail in the Polycom Unified Communications Deployment Guide for Cisco Environments.
Page 437 Appendix - Polycom Open Collaboration Network (POCN) Video and Content Endpoint Registration Lync CUCM ITP /HDX ITP /HDX ITP /HDX RTV Key is required for TIP Key is required for TIP Key is required for Dialing Method HDX and ITP HDX to Collaboration •...
Page 438 Appendix - 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.
Page 439 Appendix - Polycom Open Collaboration Network (POCN) Lync Participants (RTV) 1 In the Participant List pane double-click the participant entry. Alternatively, right-click a participant and select Participant Properties. The Participant Properties - General dialog opens. 2 Open the SDP tab.
Page 440 Appendix - Polycom Open Collaboration Network (POCN) Known Limitations The following may occur in the collaborative environment: ● 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.
Page 441 Appendix - Polycom Open Collaboration Network (POCN) ● Lync Clients always connect encrypted to non-encrypted conferences. ● Auto Layout sometimes ignored for CTS and Lync Clients calling through DMA. Frequency: Rarely. ● Content sent from HDX endpoint is received by all endpoints for 1 second before stopping.
Page 442 RealPresence Collaboration Server To establish a direct connection to the RealPresence Collaboration Server you must: ● Configure the Connecting Workstation ● Cable the Workstation Connection to the RealPresence Collaboration Server ● Connect to the MCU with the RMX Web Client Polycom, Inc.
Page 443 1 Using a LAN cable, connect the workstation:  To the LAN 1 Port on the RealPresence Collaboration Server (RMX) 1800 back panel.  To the LAN 2 Port on the RealPresence Collaboration Server (RMX) 2000/4000 back panel. Polycom, Inc.
Page 444 Use the RMX Web Client to directly access to a single RealPresence Collaboration Server, Appliance Edition. To connect to the MCU with the RMX Web Client: 1 Open a Microsoft Internet Explorer browser window, enter the factory setting Management IP address in the browser’s address line and press Enter. Polycom, Inc.
Page 445 Appendix - Direct Connection to the RealPresence Collaboration Server 2 In the RMX Web Client Login screen, enter the default Username (POLYCOM) and Password (POLYCOM) and click Login. The Fast Configuration Wizard launches. For more information on First-time Power-up and the Fast Configuration Wizard see Polycom RealPresence Collaboration Server Getting Started Guide.
Page 446 3 Create a dial-up connection – Using Windows New Connection Wizard. 4 Connect to the Collaboration Server – Via the RMX Manager. Configure the Modem Configure the modem with the following settings. ● IP address – near 169.254.192.nn Polycom, Inc.
Page 447 10 The Connection applet is displayed with the field values filled in as specified by the New Connection Wizard. 11 Click Dial 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 448 This section describes how the RealPresence Collaboration Server meets homologation requirements for import into 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 RealPresence Collaboration Server, allowing the user to define and select either standard or proprietary H.323 and SIP protocol settings.
Page 449 Section CS_MODULE_PARAMETERS Possible values: 0 - Sets the H.323 index timer to Polycom proprietary (flag default setting) 1 - Sets the H.323 index timer based on the H.323 Standard recommendation. For homologation and certification testing, this flag must be set to 1.

This manual is also suitable for:

Realpresence 2000 Realpresence 4000