MCU GMT Time

Table 2-2: MCU GMT Time Options Field MCU GMT Offset Description Displays the currently defined time zone difference. To manually modify the GMT Offset, click on the scroll arrows to change the value, or enter the new value. Note: GMT offset can be set in minutes, for example: 5 hours and 45 minutes. Click this button to automatically update the MCU's Date, Time and time zone to match the MGC Managers date, time and time zone settings. Click this button to automatically update the MCU's Time and Date to match the MGC Managers time and date settings (without GMT offset). This field is only applicable to XPEK systems. Select this check box to synchronize the time with an NTP server. Enter the IP address of the required NTP server. Displays the local date and time as set in the MGC Manager (this time is taken from the Windows operating system). The time zone difference as set in the MGC Manager (this time is taken from the Windows operating system).
Get Oper Time&GMT Get Oper Time

Use NTP Server

Operator Local Time and Date Operator GMT Offset
To set the time on the MCU using an NTP Server: 1. In the MCU GMT Offset box, enter the time difference between the MCU Local Time and MCU GMT Time. 2. 3. Select the Use NTP Server check box, and enter the IP address of the NTP server. Click OK. NTP Server synchronization may take up to an hour. All time-related settings, such as the scheduled Starting Time of Reservations, are adjusted.
To set the time on the MCU automatically, using the MGC Manager time settings: 1. Click the Get Oper Time&GMT button or Get Oper Time button. 2. Click OK.
To set the time on the MCU Manually: 1. In the MCU GMT Time box, enter the appropriate MCU GMT time by either clicking on the scroll arrows to change the value, or retyping the new value. 2. 3. Set the MCU GMT Offset (hours), by clicking the scroll arrows to change the value, or retyping the new value. Click OK.
Modifying the MCU Local Time for Daylight Savings
To modify the MCU Local Time for daylight savings: 1. In the MCU Time dialog box, change the MCU GMT Offset. The MCU local time will be changed accordingly. For example, if the Local MCU Time shows 11:00 and the MCU GMT Offset is set to 2, changing the MCU GMT Offset to 1 will change the MCU Local Time to 10:00. The MCU GMT Time will remain unchanged. 2. Click OK.

MGC Unit Software Installation
When upgrading the software from a previous version, you need to download the new MCU version to the MCU unit. This process may also be required when replacing or upgrading the control unit of the MCU. A pre-download check is performed to ensure a successful software installation.
Before you upgrade the MGC unit software, it is important to backup all reservations in the MCU. This is to safeguard against reservations being lost. For more details, see Chapter 5, Backing up Reservations on page 5-112.
To install the MCU software: 1. Select the MCU to which you want to download software. 2. On the File menu, click Download MCU Software.
Alternatively, right-click the MCU icon, click MCU Utils, and then click Download MCU Software.
A message is displayed reminding you that you must have a valid dongle attached to the MCU. 3. Click OK. The Logon dialog box opens.
The Login Name and Password of the current logged in operator are entered by default. If required, enter another login name and password. 4. Click OK to login or Cancel to continue without logging in. If you have selected Cancel, a message is displayed indicating that connection will be established without login. Click YES to continue. The Software Installation dialog box opens, with the selected MCU displayed in the MCU List box.
Select the Install Default Services check box to download the default IVR Service and Entry Queue Service. The default IVR Service is in English and is named IVR90. The default Entry Queue Service is in English and is named EQ90. You can manually install the default English IVR Service and Entry Queue Service or the English and Spanish IVR and Entry Queue Services. For more information, see Manual Installation of the Default Message Services on page 2-30.
You can download software to all MCUs listed in the MCU List in one operation. Make sure that all MCUs to update appear in the MCU List. To add an MCU to the list: a. Click the Add MCU button. The Add MCU dialog box opens.

b. c. d. e.

In the MCU Name box, type the name of the MCU. In the MCU IP box type the IP address of the MCU. The Login and Password fields are filled with the login name and password of the logged in operator. Click OK. The Add MCU dialog box closes and the name of the MCU is added to the MCU list.

DiffServ and Precedence

Select Precedence when the network router uses Precedence for priority encoding, or when you are not sure which method is used by the router. Note: If you are not sure which QoS policy your router supports, select Precedence combined with None in the TOS field. Precedence is the default mode as it is capable of providing priority services to all types of routers, as well as being currently the most common mechanism.
Table 3-17: QoS of Ethernet Service Dialog Box Options (Continued) Field Audio and Video Description You can prioritize audio and video IP packets to ensure that all participants in the conference hear and see each other clearly. Select the desired priority. The scale is from 0 to 5, where 0 is the lowest priority and 5 is the highest. The recommended priority for both audio and video is 4 to ensure that the delay for both packets is the same and audio and the video packets are synchronized and to avoid lip sync. Type of Service (TOS) defines optimization tagging for routing the conferences audio and video packets. Routers that support the Precedence mechanism can implement classification by TOS optimization tags when transferring IP packets. Delay The recommended default for video conferencing; prioritized audio and video packets tagged with this definition are delivered with minimal delay (the throughput of IP packets minimizes the queue sequence and the delay between packets). None No optimization definition is applied. This is a compatibility mode in which routing is based on Precedence priority settings only. Select None if you do not know which standard your router supports.
Click OK to apply your settings and return to the Settings dialog box.
Click Next. The DNS Settings dialog box opens.
This dialog box is used to define the DNS Server IP address and the local domain name. For H.323 conferencing, DNS is used if gatekeeper discovery using the gatekeeper host name and NAT auto-discovery are applied. Using NAT Traversal, the DNS is queried for the NAT server IP address used for allocating the public (external) IP addresses to the cards for the conferencing session. For SIP conferencing, domain names are required and therefore it is recommended to enter the details of the DNS server and the local domain name. The DNS is also used if SIP Server discovery is applied. The system decides whether to use the DHCP or the DNS server for autodiscovery with preference to the DNS server.
Table 3-18: DNS Settings Dialog Box Options Field Use DNS Servers Description
Off DNS servers are not used in the network. Specify Select this option to enter the IP address of the DNS servers. Auto Select this option to automatically detect the primary DNS address, provided the DNS Server is defined in the DHCP and if the DHCP obtain IP Address Automatically check box was selected in the Settings tab.

Signaling [TCP]

Control [TCP]
Table 3-27: Fixed Ports & NAT Dialog Box Options (Continued) Field Audio [UDP], Video [UDP] Description Define the ports used for audio and video channels. After you enter the beginning of the range, the system automatically fills in the end of the assigned range. If the first audio port is 49182, and the number of audio ports per call is two, the total number of required ports for six simultaneous calls is 12. Therefore, the last port number in the range is 49193. Define the ports used for transferring data packets: file transfer, whiteboard, and application sharing. The recommended port range is 49152 to 65535. After you enter the beginning of the range, the system automatically fills in the end of the assigned range. Define the ports used for FECC. After you enter the beginning of the range, the system automatically fills in the end of the assigned range.

Data [TCP]

FECC [UDP]
When fixed ports are exhausted Allocation ports dynamically Select this option to allocate any of the available ports in the firewall to calls that exceed the number of predicted simultaneous calls. These ports may not be secured. Set the system to reject any request to open additional ports and the call will be rejected. If the volume of simultaneous calls exceeds the specified number of calls and there are no available ports in the firewall to handle the call, it is rejected by the network server.

Reject

Table 3-27: Fixed Ports & NAT Dialog Box Options (Continued) Field NAT Traversal Use Span External Address Define the method in which the public IP address is mapped to the IP cards internal address: Off No external IP address will be used. Select this option for local calls, there is no need to use the public IP address to identify the source and destination for the messaging. Specify Select this option to manually define the IP cards public IP address. Auto The IP cards public IP address is automatically retrieved from the HTML Answer of the external server. http://videovideo.polycom.austin.com. The automatically retrieved IP address appears in the IP Card Settings-IP-Network Parameters tab. If you selected Specify, enter the IP cards public IP address. Description

External IP address

Notes: For a complete port configuration you define both the fixed ports (signaling, media, etc.) and the relevant reserved ports. Make sure that the following IANA registered ports reserved for system services have been opened as part of your firewalls definitions: Port # 1720 H.323 standard signaling port
Port # 1719 H.323 gatekeeper port Port # 1503 T.120 port for incoming connections

Answer Mode Clear Mode

Table 3-31: MPI Settings Dialog Box Options Field CTS Delay Description The CTS (Clear To Send) delay indicates when to start synchronizing with the clock signals sent from the DCE. Some DCEs send a CTS signal before the channels are BONDED. In these cases, a delay should be entered. Delay between DTR (Data Terminal Ready) active and RTS (Request to Send) active. Usually, it will be set to 0 (zero), but some DCE equipment may require a delay between the activation of these signals. Select this check box when an encryption device is used. Select this check box when the DCE does not return the Clear to Send signal as expected. When this option is checked, the MCU sends the data to the DCE without waiting for the CTS signal from the DCE. When On, the signal is sent continuously. Select this check box when the endpoint does not return the Request to Send signal as expected. In such a case, the DCE will get the RTS signal and will return the clock and required signals from the endpoint. When On, the signal is sent continuously. Select this check box when the endpoint does not return the Data Terminal Ready signal as expected. In such a case, the DCE will receive the DTS signal and will return the clock and required signals from the endpoint. When On, the signal is sent continuously.

RTS Delay

KG Mode CTS On

RTS On

DTR On

Click Next to continue.

The Span dialog box opens.
The Span dialog box displays the list of spans currently defined in the system. This dialog box is used to assign circuit identification numbers and the phone numbers to be used in dial-in conferences. Circuit orders are automatically assigned to spans. If all the DCE ports are connected using the same protocol and characteristics, one network service may be defined. In such a case, a separate circuit Id and phone number must be defined for each port. These numbers will be used to identify the participant and display the participant phone number in the Status and Monitor pane during an On Going Conference.
The phone number has no influence on receiving or rejecting calls. It is used only to attach a participant to a specific port.

10. Click the Plus

button to define a new span.
The New MPI Span dialog box appears.
11. Define the following parameters:
Table 3-32: New MPI Span Dialog Box Options Field Circuit ID Description The Circuit Identification is a logical number used to identify the span to the MGC Manager. This number is later used to assign the span to the network interface card. Type an integer from 0 to 65535, to be used as the circuit identification number in the MGC Manager. If you enter any other number, the system will reject it and you will be prompted to re-assign the circuit identification number. Note: If other services are already defined, make sure to use numbers other than those already assigned to the existing services.

Make sure that the ATM Network Interface module is installed in the MCU. If not, install it first. Obtain the UNI address of the V-Gate. Make sure that the MCU power is on.
To define a new ATM Network Service: 1. Connect the MGC Manager to the MCU. For more information, see the MGC Manager User's Guide, Volume 1, Chapter 3, Connecting to an MCU. 2. In the Browser pane, double-click the MCU icon, or click the plus [+] icon next to the MCU icon. A list of options is displayed below the MCU icon. 3. In the MCU options list, double-click the MCU Configuration icon, or click the plus [+] icon next to the MCU Configuration icon.
A list of configuration options is displayed below the MCU Configuration icon. 4. Double-click the Network Services icon, or click the plus [+] icon next to the Network Services icon. A list of Network Service types is displayed below the Network Services icon.
Right-click the ATM icon, and then click New ATM Service.
This dialog box is used to define the properties of the ATM network, and UNI address of the V-Gate. These properties should be obtained from your service provider. 6. Click the Plus button in the V-Gate UNI Address pane. The UNI Address dialog box opens.
Enter the V-Gates UNI Address. Usually, the first number and the last six numbers in the UNI address are modified. The V-Gate UNI Address is defined by the operator. It stores the address book of the endpoints UNI Addresses.
Click OK. The UNI address is added to the V-Gate UNI Number list Up to six V-Gates may be defined in the system. The order in which the V-Gates are defined determines the order in which they will be addressed by the MGC unit when searching for the UNI Address of endpoints. To define additional V-Gates, repeat steps 7 and 8. To delete a UNI Number from the UNI number list, select the desired number, and then click the Minus pane. button in the V-Gate UNI Address
A confirmation dialog box is displayed. Select Yes to confirm or No to cancel.
Table 3-34: ATM Settings Dialog Box Options Field ATM Service Name Service Type Description Enter the Network Service name using up to 20 characters. The ATM Service Name identifies the service to the system. Select the network transfer rate from the drop-down list according to the ATM Network Interface module installed in your system. There are two network transfer rates currently available for ATM networks: ATM-25 (which is the default) for a transfer rate of 25 Mbps, and ATM-155 for a transfer rate of 155 Mbps. An internal parameter used by the VC-NIC. By default, the MVIP Interrupt Rate is set to 4 milliseconds. This value can be modified to 8 milliseconds, but should only be changed with the authority of a support engineer. CBR Constant Bit Rate. Used for real time applications like voice and audio. VBR-RT Variable Bit Rate Real Time. Similar to CBR. This service allows statistical multiplexing and consistent service quality to applications such as compressed voice and audio. VBR-NRT Variable Bit Rate Non-Real Time. This service is defined for non-real time applications whose data transfer is performed in random bursts. The maximum cell rate at which a source may send its cells during the connection lifetime. There are two types of switches that can be used depending on the default Quality of Service settings. Others Set this switch type when the default Quality of Service settings is VBR-RT. FORE Switches Set this switch type when working with FORE Swithes and the default Quality of Service settings is VBR-NRT.

Performs video processing and Transcoding. Performs video processing and Transcoding. Multiplexes and demultiplexes audio, data, video, and control information; performs channel aggregation (inverse multiplexing). Multiplexes and demultiplexes audio, data, video, and control information; performs channel aggregation, enables Encryption. Multiplexes and demultiplexes audio, data, video, and control information; performs channel aggregation, enables Encryption.

Video+ MUX Module

MUX+10

18 channels at 128Kbps

MUX+20

channels at 128Kbps

Table 4-1: Functional Modules (Continued) Functional Module MUX+40 Function Multiplexes and demultiplexes audio, data, video, and control information; performs channel aggregation, enables Encryption. Performs data routing and conference control. Port capacity 72 channels at 128Kbps

Data Module

T.120 standard card 12 ports T.120-24 card - 24 ports
The different types of functional modules are used to produce a variety of configurations. In the MGC-50 up to eight individual Functional Modules can be used to build the desired configuration. In the MGC-100, 16 modules can be used. The configuration of each functional module can be checked and for specific modules, and if required, modified. Any operator can view the Functional Module configuration settings. Only an operator defined as Superuser can modify the configuration settings of a functional module.
Listing the Installed Modules
You can check which functional modules are installed in a particular MCU by listing them. To list an MCUs functional modules: 1. Connect to the MCU whose modules you want to list. 2. 3. 4. Expand the MCU tree to list its options. Expand the MCU Configuration tree to list the configuration options. Expand the Cards tree. All the MCU slots are listed (16 slots for the MGC-100, 8 slots for the MGC-50). Empty slots are indicated by a white card icon. Occupied slots are indicated by a green card icon. The name of the functional module occupying the slot appears next to the slot number.

SNMP (Simple Network Management Protocol)
SNMP is a standard protocol for managing all types of network equipment. Adding SNMP functionality to the MCU enables monitoring of the MCU status by external managing systems, such as HP OpenView. A network management system consists of two primary elements: a Manager and Agents. The Manager is the terminal through which the network administrator performs network management functions. Agents are entities that interface to the actual device being managed. Bridges, Hubs, Routers and MCUs are examples of managed devices that contain managed objects. These managed objects may be hardware, configuration parameters, performance statistics, and so on, that directly relate to the current operation of the device being monitored. These objects are arranged as a virtual information database, known as Management Information Base (MIB). SNMP allows managers and agents to communicate for the purpose of accessing these objects. MIBs are a collection of definitions, which define the properties of the managed object within the device to be managed. Every managed device keeps a database of values for each of the definitions written in the MIB. The H.341 standard defines the MIBs that H.320 and H.323 MCUs must comply with. In addition, other MIBs should also be supported, such as MIBII and the ENTITY MIB, which are common to all network entities.
MIB (Management Information Base) Files
This section describes the MIBs that are included with the MGC Manager. These MIBs define the various parameters that can be monitored, and their acceptable values. The MIBS are contained in files in the SNMP Mibs subdirectory of the MGC Manager root directory. The files should be loaded to the SNMP external system and compiled within that application. Only then can the SNMP external application perform the required monitoring tasks.
The MULTI-MEDIA_MIB_TC must be compiled before compiling the other MIBs.

Standard MIBS

MULTI-MEDIA-MIB-TC (MULTIMTC.MIB) defines a set of textual conventions used within the set of MultiMedia MIB modules. H.320ENTITY-MIB (H320-ENT.MIB) is a collection of common objects, which can be used in an H.320 terminal, an H.320 MCU and an H.320/H.323 gateway. These objects are arranged in three groups: Capability, Call Status, and H.221 Statistics. H.320MCU-MIB (H320-MCU.MIB) is used to identify managed objects for an H.320 MCU. It consists of four groups: System, Conference, Terminal, and Controls. The Conference group consists of the active conferences. The Terminal group is used to describe terminals in active MCU conferences. The Controls group enables remote management of the MCU. H323MC-MIB (H323-MC.MIB) is used to identify objects defined for an H.323 Multipoint Controller. It consists of six groups: System, Configuration, Conference, Statistics, Controls and Notifications. The Conference group is used to identify the active conferences in the MCU. The Notifications group allows an MCU, if enabled, to inform a remote management client of its operational status. MP-MIB (H323-MP.MIB) is used to identify objects defined for an H.323 Multipoint Processor, and consists of two groups: Configuration and Conference. The Configuration group is used to identify audio/video mix configuration counts. The Conference group describes the audio and video multi-processing operation. MIB-II/RFC1213-MIB (RFC1213.MIB) holds basic network information and statistics about the following protocols: TCP, UDP, IP, ICMP and SNMP. In addition, it holds a table of interfaces that the Agent has. MIB-II also contains basic identification information for the system, such as, Product Name, Description, Location and Contact Person. For details of the MIB-II sections supported by the MGC Manager for PSOS and XP see Support for MIB-II Sections on page 5-43. ENTITY-MIB (ENTITY.MIB) describes the unit physically: Number of slots, type of board in each slot, and number of ports in each slot.

Confer.cfg Flags Section AUTO_REDIAL NUM_REDIAL_TIMES = 3 The number of times the system redials when a participant is disconnected.
REDIAL_INTERVAL_IN_SECS = 30 The interval between system redial attempts when a participant is disconnected.
Section AUTO_EXTENSION The end time of a conference can be automatically extended without operator intervention. The following parameters are defined at the MCU level and they apply to all the conferences that will be run on this MCU. Whether the automatic extension of conference duration will apply to a specific conference is determined by enabling the End Time Alert Tone, in the Conference Properties Settings dialog box.
ENABLE_AUTO_EXTENSION Defines whether the automatic extension is enabled and if it can be applied to conferences. Select YES to enable the auto extension mode for conferences, or NO to disable it. MAX_EXTENSION_TIME The maximum accumulative number of minutes to be added to the predefined conference duration. For example, if the conference duration is set to 3 hours and this flag is set to 45 minutes, the total number of minutes that can be added to a conference (in multiples defined in the Extension Time Interval field) is 45 minutes, totaling a conference duration of 3 hours and 45 minutes.
EXTENSION_TIME_INTERVAL The number of minutes that the conference will be extended by each time the system checks and identifies that at least one participant is still connected to the conference.
Section SPEAKER_CHANGE SPEAKER_CHANGE_TIME_INTERVAL = 0 The amount of time a speaker is displayed before the system starts checking if there is a new speaker. The minimum time that a speaker has
to speak to become the main speaker is set per conference in the Talk Hold Time field, in the Conference Properties Settings dialog box. Sections AUTO_LAYOUT and AUTO_LAYOUT_QUAD Layout selection for each number of video participants is defined in the confer.cfg file. These values can be modified. The flags are divided into two sections:
AUTO_LAYOUT contains the layout definitions for Continuous Presence Classic
AUTO_LAYOUT_QUAD contains the layout definitions for Continuous Presence Quad Views.
To modify these values, enter the appropriate name of the layout. Table 5-14details the names of Continuous Presence Classic layouts that can be entered in the confer.cfg to modify the automatic layout selection.
Table 5-14: Continuous Presence Classic Layout Names Layout # 1 Layout Name in confer.cfg CP_LAYOUT_1X1 Layout

Destination Endpoint Type
H.320 Endpoint Parameters
H.323 Endpoint Parameters
Table 7-7: Address Book - Endpoint Definition Options (Continued) Field Endpoint Characteristics Description Describes the endpoint capabilities. This is especially important when importing the endpoint information from the database. These four fields appear in the Gateway Profile, the system will conduct the session according to the highest possible common denominator between the endpoint and the profile. Line Rate - Select the multimedia (audio, video or data) transfer rate in Kbps for the gateway session. Maximum line rate currently supported is E1 (1920 Kbps). For example, if the endpoint maximum Line rate is set to 384, while the Gateway Profile is set to 128 Kbps, the session will use 128 Kbps as the session Line rate. Audio Only - Select this check box if the gateway session should be run using audio only (without Video). When cleared, video can be used during the conference. Restrict Only - Select this check box if one of the participants is using restricted endpoint. The line rate for each channel of restricted lines is 56 Kbps instead of 64 Kbps. Encryption - Select this check box if encryption is to be used.
Defining H.320 Routing Services
The H.320 Routing Services define how the call originating from an H.320 endpoint will be transferred to an H.323 endpoint. There are different methods on how to transfer the call depending on the system configuration. Calls can be routed using H.323 Destinations, Address Book, Forwarding Services or using a Double Gateway Link. To define a new Routing Service, you start by selecting the dial in number range that will be allocated that Routing Service. Refer to Spans and Phones Dialog Box on page 3-14 for configuration of Dial-in number ranges. When you have completed configuration of Dial-in ranges then you define the properties of that Routing Service. To define an H.320 Routing Service: 1. In the Gateway Configuration tree, double-click the H.320 Routing Services icon.
The From H.320 Routing Services dialog box opens.
The list of dialin numbers configured for the different Routing Methods
The list of dialin numbers allocated to the gateway sessions in all the ISDN Network Services defined in the system
The Dial in Gateway Range Numbers are based on entries in the Network Services. 2. To define a new Routing Service, in the Dial in Gateway Range Numbers, double-click the dial-in range from which to allocate numbers to a Routing Service. Alternatively, in the Dial in Gateway Range Numbers, click the Dial-in range from which to allocate the number to the Routing Service and then click the Configure button. The H.320 Routing Services Definition dialog box opens.

Level major major

Description An attempt was made to enable a specific audio algorithm not supported by the card. Similar to red alarm, but resulting in transmission failure between the local span and the PBX. Check the connection between the net spans, the transmission equipment and the PBX. For development use only. May occur if the simulation check box was checked during card installation.
CARD_IS_IN_SIMULATOR_ MODE
Table A-4: Card Fault Descriptions (Continued) Code
CARD_SOFTWARE_FILE_ NOT_EXIST

Level major

Description The software file of the required version does not exist. You must reinstall this file. If this does not solve the problem, consult your service engineer. This fault is related to the function: OnUnexpectedStartupIndication that is called only when receiving: NEW_CARD_INDICATION
CARD_STARTUP_NOT_IN_ TIME
CARD_TYPE_NOT_EXIST_ IN_CONFIG
STARTUP_COMPLETION_INDICATION
START_POLLING_INDICATION when the card is in normal state.
The entry is missing in version.txt on the Main Controls local disk. Consult your service engineer. There was a fatal error in the CCOM card. This will cause the reset of the CCOM card. When the reset is complete, the system should continue to function normally. This may interfere with On Going Conferences. It is recommended to reset the MCU when idle (when there are no On Going Conferences). The span failed to establish a D-Channel. Check the physical connection and the network configuration settings. Occurs after VideoPlus/H.323 card selfrecovery. No LAN link to IP card. The card could not find the DHCP Server. Autodiscovery failed.

CCOM_FATAL_ERROR

D_CHANNEL_IS_NOT_ ESTABLISHED
FAULTY_UNIT_ RECOVERED H323_LAN_LINK_STATUS_ DOWN IP_CARD_STATUS_DHCP_ SERVER_TIMEOUT IP_CARD_STATUS_NAT_A UTODISCOVERY_FAIL

minor major major minor

IP_CARD_STATUS_DNS_ SERVER_TIMEOUT IP_CARD_STATUS_DNS_ SERVER_IP_NOT_ PROVIDED IP_CARD_STATUS_SIP_ PROXY_IP_NOT_ PROVIDED IP_CARD_STATUS_NOT_ PROVIDED IP_CARD_STATUS_ ADDRESS_CHANGED LARGE_CONF_NOT_ SUPPORTED_BY_CARD
Description The DNS Server did not respond. The DHCP Server did not return the DNS Server IP address. The DHCP Server did not return the SIP Proxy IP address. The DHCP Server did not return the Gatekeeper IP address. The DHCP Server sent a new address for the IP card. Applicable only to a legacy Audio card where conferences with more than 16 participants are not supported by the current software version of the card. There is a problem downloading a message to the audio card. There is a problem transmitting a message to the audio card. Problems occurring during PRI card startup. May be caused when assigning a network service to a span and then deleting the network service. The MCU failed to communicate with the card. The card may have been removed, or is not firmly in place. This may also be caused by a faulty card.

A list of slots appears.

Click the slot containing the Net-T1/Net-E1 Network Interface module (PRI48) to configure, or click the plus [+] icon next to the card icon, to list its spans. Right-click the unit whose ISDN line quality you want to check, and then select: Monitor 15 min to retrieve statistical data on the line quality in the last 15 minutes. Monitor 24 hours to retrieve statistical data on the line quality in the last 24 hours (in 15 minute intervals).
The Performance Monitoring dialog box opens.
The dialog box heading indicates the span being monitored and the monitoring time interval. Table C-1, "Performance Monitoring Options." describes the monitored parameters.
Table C-1: Performance Monitoring Options Error Condition Seconds In Current Interval Valid Intervals Description Indicates the number of actual seconds within the 15 minute interval. Possible values are from 0 to 900 seconds. Indicates the number of valid 15 minute intervals in the last 24 hour period. Possible values are from 0 to 96 minutes. This field only applies when you are monitoring the performance over a 24 hour period. Indicates the current status. Refers to errors on a T1 line, specifically when the frame structure cannot be found.

Current Status ESF

Table C-1: Performance Monitoring Options (Continued) Error Condition Error Seconds (ES) Description ES is a second with one or more Path Code Violations (PCV), or one or more Out Of Frame (OOF) defects, or one or more Controlled Slip (CS) events, or where AIS defects have occurred. SES is a second with 320 or more Path Code Violation (PCV) error events, or one or more Out Of Frame (OOF) defects, or where AIS defects have occurred. SEFS is a second with one or more Out Of Frame (OOF) defects, or where AIS defects have occurred. Unavailable Seconds are calculated by counting the number of one-second intervals during which the ISDN line is unavailable as a result of 10 contiguous SES errors, or when there are yellow and red alarms, CRC errors or synchronization problems. Controlled Slip Seconds are calculated by counting the number of one-second intervals during which one or more Controlled Slip events occurred. A frame synchronization bit error. See detailed explanation above. A second in which one or more Line Code Violation error events were detected. A second in which fewer than 320 and more than one Path Code Violation error events were detected. A condition when one or more of the established performance parameters fall outside predetermined limits and results in a lower quality of service.

Insert LAN cable to I/O port
Slot A Main Control Module Cover

IO Card

Main Switch

AC Inlet

RJ45 Connector
To connect the LAN cable to an MGC-100 unit: 1. Ensure that the Control LAN cable is connected to the RJ 45 Connector port.
Connect a LAN cable to the I/O port on the back of any IP+ card to be tested.
Slot A RS232 Connectors Network Connectors Main Control Module Cover

LINE IN

10/100 Mbits
Main Switch and Circuit Breaker AC Inlet Dry Contacts RJ45 Connector
Running the Tests at the MCU Level To run the diagnostic tests:
The LAN test and the ISDN Loop test are automatically run at the MCU level testing, so connect the ISDN Loopback and LAN cables to the MCU before running the tests. For more details, see Connecting the LAN and ISDN Loopback cables on page D-15.
Connect to all the MCUs that must be tested. In the Test Options box, select the test mode. For a detailed description of the three modes, see Test Options Box on page D-11. For a description of how to connect the LAN or ISDN Loopback cables, see Connecting the LAN and ISDN Loopback cables on page D-15. At the MCU level, the LAN test is automatically run and therefore, the IP Test fields must be filled in. For a detailed description of the IP Test fields, see IP Test Box on page D-11.
Select a test mode in the Test Options box. For a description of the test selection options, see Test Selection on page D-11.
Click the Run button. The test results appear in the Test Results pane as the tests occur. For a detailed description of the Test Results pane, see Test Results Pane on page D-12.
Running Tests at the Card Level Once you are connected to an MCU, you can expand the MCU tree to display its cards. This enables you to run the diagnostic tests on individual cards without having to run the test series on all the cards that are installed. You can set multiple tests to run at once, but they will run serially rather than simultaneously. To run diagnostic tests on cards: When you run the diagnostic tests on a specific card, all available tests are performed on that card. If you run a LAN test on an IP+ or IPN card, or an ISDN Loop test on an IPN card, you must connect the ISDN Loopback or LAN cables to the MCU before you run the diagnostic tests. For a description of how to connect the LAN or ISDN Loopback cables, see Connecting the LAN and ISDN Loopback cables on page D-15. 1. 2. 3. 4. In the Browser pane, expand the selected MCU tree. Select the cards to test. In the Test Options box, select the test mode. For a detailed description of the three modes, see Test Selection on page D-11. If you have an IP or IPN card installed on your MCU, one of the tests that is run is the LAN test. To complete the LAN test, you must fill in the IP Test fields. For a description of completing the IP Test fields, see IP Test Box on page D-11. Click the Run button The test results appear in the Test Results pane. For a detailed description of the Test Summary pane, see Test Results Pane on page D-12.

Release Notes

Polycom HDX Systems, Version 3.0.0.2
This document provides the latest information about the Polycom HDX systems and Polycom Touch Control. Polycom is pleased to announce the latest release of Polycom Touch Control software, version 1.0.3 of the Polycom Touch Control Panel Software and version 1.0.3 of the Polycom Touch Control Operating System. These updates are the minimum versions required for Hardware Version 5 of the Polycom Touch Control. However, these software updates are also recommended for previous hardware versions because the pairing functionality has been improved. For more information about using the features described in this document, refer to the product documentation available at www.polycom.com/videodocumentation.
When making a connection from a web browser to configure the Polycom HDX system, always enter the address of the Polycom HDX system in one of the following formats: https://hostname or https://10.11.12.13. If Security Mode is enabled on your system, you must use secure HTTPS access (for example, https://10.11.12.13). Click Yes in the security dialog boxes that appear. Using the HTTPS protocol ensures that the configuration of all login credentials (such as user names and passwords) are transmitted using an encrypted channel, including those user names and passwords used to communicate with third-party systems on your network. Using the HTTPS protocol severely limits the ability of anyone on the network to discover these credentials.
March 2011 3725-23984-039/A
Release Notes Polycom HDX Systems, Version 3.0.0.2

Software Version History

Polycom HDX System Software
Software Version 3.0.0.2 3.0.0.1 3.0 Description Maintenance release that includes updates from software testing with Microsoft Lync Server 2010 Correction for an issue involving pairing an HDX system with a Polycom Touch Control Support for Polycom HDX systems and the Polycom Touch Control
Polycom Touch Control Software
Software Version Panel Software version 1.0.0 Operating System version 1.0.0 Panel Software version 1.0.1 Panel Software version 1.0.3 Operating System version 1.0.3 Corrections for pairing issues Support for Hardware Version 5 of the Polycom Touch Control and corrections for pairing issues Description Initial release

Polycom, Inc.

Installing Version 3.0.0.2

Before You Install

Points to note about Software Update: Because of changes in software functionality and the user interface, some settings might be lost when you upgrade to the current version or reinstall an older version after upgrading. Polycom recommends that you store your system settings using profiles and download your system directory before updating your system software to the current version. Do not manually edit locally saved profile and directory files. Refer to the Administrators Guide for Polycom HDX Systems for more information. Systems perform an internal restart before running Software Update. If you are updating a Polycom HDX system using a web browser, the internal restart is not visible from the web interface. This process improves the reliability of the update process by freeing up memory before performing the update. If you install the software using a management server, such as Polycom Converged Management Application (CMA), Polycom Global Management System, or Polycom ReadiManager SE200, note that some limitations are associated with this update method. Refer to Installing By Using a Management Server in Traditional Management Mode on page 4 for more information.

Running Software Update

To update your system software, use the Software Update feature in the Polycom HDX web interface. Customers upgrading Polycom HDX systems from version 2.6.1.3 or earlier to version 3.0.0.2 must have an upgrade key. To access Software Update: 3 Go to http://support.polycom.com and navigate to your product page. Download the Polycom software update package for your system. In the browser address line of Internet Explorer 6.x, 7.x, or 8.x, enter the systems IP address, for example, https://10.11.12.13, to access its web interface. Enter the Admin ID as the user name (default is admin), and enter the Admin remote access password, if one is set. Go to Admin Settings > General Settings > Software Update and follow the instructions on the screen.
Installing on a Polycom HDX System Under Warranty or a Service Plan
If you are installing software on a Polycom HDX system that is under warranty or a service plan, you need an upgrade key to activate the software. You can get that key by logging in to support.polycom.com and requesting the upgrade key. You need the Polycom HDX systems serial number to get the key. If the Polycom HDX system is not under warranty or a service plan, you need to get a license and then activate the license on support.polycom.com to obtain an upgrade key. For more detailed information about installing Polycom software, refer to Installing Polycom HDX Software and Options on the web page where you download the software.
Installing By Using a Management Server in Traditional Management Mode
To install the current version on a Polycom HDX system that is in traditional management mode, you must use a management system that supports the new Software Update method that involves an internal restart on the system. The following management systems support the new Software Update method: Polycom CMA version 4.1.4 or later Polycom Global Management System version 7.1.10 or later. Polycom ReadiManager SE200 version 3.0.7 or later.
Installing an Older Version after Upgrading to Version 3.0.0.2
If you reinstall an older version of software after upgrading to the latest version, which is also known as downgrading, Polycom recommends performing a Custom installation and selecting Erase System Flash Memory. This setting is available when you use Software Update. To downgrade from version 2.6.1 or later software to 2.6 or earlier software, first downgrade to version 2.6.0.2, then to the desired software release.
Whats New in Version 3.0.0.2
This version is a maintenance release that includes updates from software testing with Microsoft Lync Server 2010.
Whats New in Version 3.0.0.1
Polycom HDX systems running version 3.0 software that were paired with a Polycom Touch Control running version 1.0 of Polycom Touch Control Panel Software and version 1.0 of Polycom Touch Control Operating System would occasionally appear to not be paired. In addition, the pairing connection could become unstable. If you use an HDX system with a Polycom Touch Control, Polycom recommends running HDX software version 3.0.0.1 software with version 1.0.1 of the Polycom Touch Control Panel Software and version 1.0 of the Polycom Touch Control Operating System.

Camera Firmware Update for HDX 4000 Systems
Version 3.0 includes a camera firmware update for HDX 4000 series systems. This update improves image quality issues with sharpness and backlit exposure situations.
Default Setting for Outgoing Call Speed
The default preferred speed for placing calls is 512 kbps, which applies to IP call types only (ISDN remains at 128 kbps). This change means that when you upgrade to version 2.6.1 or later, the Select the preferred speeds for placing calls setting reflects the default of 512.
Polycom HDX System State Changes Through XML API
Polycom CMA system version 5.4 processes some of the Polycom HDX system events and status changes that are sent via the HDX system XML API. This allows the CMA system to report status and events for HDX systems that are outside a firewall such as the Polycom Video Border Proxy (VBP).
Certificates and Revocation
If your organization requires a secure environment, Polycom recommends that you have a strong understanding of certificate management before you implement these features. Polycom HDX systems can generate and use certificates to authenticate network connections to and from the Polycom HDX system. The system uses configuration and management techniques typical of public-key infrastructure (PKI) to manage certificates, certificate signing requests (CSRs, sometimes also called unsigned certificates), and revocation lists. ANSI X.509 standards regulate the characteristics of certificates and revocation. The certificate authority (CA) is the trusted entity that issues, or signs, digital certificates for others, as well as the certificates associated with the CA itself. You can manage certificates and revocation only through the Polycom HDX web interface. When certificate validation is enabled, the HDX system tries to validate the peer certificate chain on secure connection attempts for the applicable network services. Validation may fail for several reasons, such as certificate expiration or revocation. The HDX system can check revocation status by using certificate revocation lists (CRLs) or the online certificate status protocol (OCSP). Polycom encourages you to check your system logs daily to ensure that your installed certificates are current. Finally, in some cases, expired certificates or CRLs might prevent you from accessing the web interface. Polycom allows you to reset your system without certificates, on the local interface, so you can get back into your web interface.

Whitelist

When a whitelist is enabled, the Polycom HDX system allows access to its web interface only by those systems with an IP address that matches the set defined on the HDX system. You can use this feature only through the web interface.

Sessions List

You can use the sessions list to see information about everyone logged in to an HDX system including: Type of connection: Web, when users are logged in through the web interface Serial, when users are logged in through the RS-232 port Local, when users are logged in to the local interface User ID Remote IP address (that is, the computer addresses logged in to the HDX system) Session duration in hours, minutes, and seconds for each user currently logged into the HDX system How long the system has been idle, in seconds

Description The Polycom Touch Control would indicate it was paired with the HDX system when in fact it had lost the pairing connection. Version 1.0.3 of the Polycom Touch Control Panel Software and version 1.0.3 of the Polycom Touch Control Operating System resolve this issue. SIP calls across firewalls sometimes failed to connect fully. This issue has been corrected. Polycom HDX 9002 failed to detect input on input 1. This issue has been corrected.

SIP Software Update

VIDEO-71148 VIDEO-88909
Corrected Issues in 3.0.0.1
The following table lists issues corrected in version 3.0.0.1.
Issue Polycom Touch Control Device Jira ID VIDEO-88393 Description On occasion, HDX systems running 3.0 software paired with Polycom Touch Control running version 1.0 of Polycom Touch Control Panel Software and version 1.0 of Polycom Touch Control Operating System would get out of sync on the status of pairing between them. In addition, the pairing connection could become unstable. HDX version 3.0.0.1 software, together with version 1.0.1 of the Polycom Touch Control Panel Software and version 1.0 of the Polycom Touch Control Operating System, resolves this issue.

Corrected Issues in 3.0

The following table lists issues corrected in version 3.0.
Issue Audio Jira ID VIDEO-84517 Description If more than three endpoints are connected to a Polycom HDX system hosting a multipoint call, and one of the endpoints plays audio content, and that endpoint is not the last endpoint connected to the call, audio is no longer garbled. Polycom HDX 9001 systems no longer experience distorted audio when the following sequence of events occurs: 1. The Polycom HDX 9001 system places a POTS call. 2. The Polycom HDX 9001 system places a video call to an endpoint that supports stereo. 3. The Polycom HDX 9001 system places a video call to an endpoint that does not support stereo. Automatic Provisioning VIDEO-70052 VIDEO-70539 Configuring automatic provisioning information in the out-of-box setup wizard (or configuring the system to not use provisioning) and later moving back to the provisioning page to change this information caused an issue that has been corrected. Video is no longer delayed on a Polycom HDX 9001 system when in a multipoint call with a Polycom HDX 8000 system with Hardware Version B that is hosting the multipoint call and sending content. When a leading zero was used in the IP address, the ifconfig command treated the value incorrectly. This issue has been corrected. With Allow Directory Changes provisioned to disabled, you could add Contacts but not delete them. This issue has been corrected. Polycom HDX systems can now send content when in a call with a Polycom RMX system when content resolution is configured for 800x600. On occasion the far endpoint stopped receiving content if the presenter changed screen resolution from 12x7 to 10x7. This issue has been corrected. When registering an HDX system running version 2.6.1 to Avaya Aura 6.0, the registration for the HDX system is no longer rejected with a message of Missing/Invalid Header.

VIDEO-84718

VIDEO-83607

VIDEO-76321

Contacts

VIDEO-70531

Content

VIDEO-85286

VIDEO-72048

Interoperability Avaya

VIDEO-86608
Issue Interoperability Microsoft

Jira ID VIDEO-84367

Description When a Polycom HDX system hosting a multipoint call is in a Office Communications Server SIP call with three Office Communicator clients, connecting to another Polycom HDX system via SIP no longer results in degraded video on the Polycom HDX system that joined the call. When a Microsoft Office Communicator client is in an audio-only call with a Polycom HDX system that is already in a point-to-point call with another Polycom HDX system, the Office Communicator client can now connect to the Polycom HDX system by video. Polycom HDX systems in high-speed, video-switched conferences with Polycom Pro-Motion on Polycom MGC sometimes experienced video artifacts when sending content. Polycom MGC 8.0.0.26 resolved this issue. Polycom HDX systems running 2.5.0.5 or earlier could sometimes crash with RMX 4.0 in 4 Mbps 1080p calls. This issue has been corrected. Polycom HDX systems no longer restart after approximately 90 minutes when all of the following conditions are true: the Polycom HDX system is in an H.323 call the H.323 call is routed through a Polycom VBP system the Polycom HDX system has SIP enabled, and the SIP proxy server specified is incorrect
Interoperability Microsoft

VIDEO-83905

Interoperability Polycom MGC

VIDEO-51962

Interoperability Polycom RMX System Interoperability Polycom Video Border Proxy (VBP)

VIDEO-74566

VIDEO-84719
Interoperability Polycom VSX Systems

VIDEO-82744

When a Polycom HDX 8006 system is in a mixed call with a Polycom VSX system connected over H.323 and a Polycom HDX 9001 system connected over ISDN, the Polycom HDX 9001 system no longer shows video latency in the PIP window when content is stopped and started among the different endpoints. When a Polycom VSX system running version 9.0.5 made a SIP connection to an existing point-to-point H.323 call between two Polycom HDX endpoints, the Polycom HDX system hosting the multipoint call appeared unresponsive and the call statistics indicated no transmit or receive video on any of the endpoints. Upgrading the VSX system to version 9.0.5.1 resolves the issue. VSX version 8.5.1 did not activate PVEC (Polycom Video Error Concealment) in a call with a Polycom HDX system that experienced network errors. VSX version 8.5.2 addresses this issue. Calls from a VSX system version 8.7 did not connect when using the UDP transport protocol. VSX version 8.7.1 resolves this issue.

VIDEO-84272

VIDEO-84274

Certificates

VIDEO-86209
Restart your HDX system after you manually change the date or time.

Chair Control

VIDEO-80896

Category Chair Control

Issue ID VIDEO-80895

Found in Release 2.6

Description When a system acting as chair control selects an endpoint and selects the View Site icon, the endpoint's video will be shown. When the system with chair control selects the Stop Viewing Site icon, the web interface provides a status of denied but the endpoints video is no longer displayed. When a system acting as chair control selects the Disconnect Site icon to disconnect an endpoint from a conference, the web interface returns a status of denied, even though the endpoint was disconnected from the conference. When selecting a system to have chair control, the endpoint does not stay highlighted as being the chair control. To release chair control, highlight all the participants in the Meeting Participants window and select Release Chair. Chair control is not supported when a SIP endpoint is in the call. When providing closed captions over a serial connection, you must manually go to near video before entering text. Closed captioning (sent via either the serial port or the web interface) is limited to 31 characters per line.

VIDEO-80897

VIDEO-74353

VIDEO-83802

Connect all endpoints via H.323 or H.320. None

Closed Captions

VIDEO-59615

VIDEO-60912

Category Contacts

Issue ID VIDEO-70317

Description Polycom HDX systems can share presence information with up to 200 Contacts. If a remote site attempts to invite the Polycom HDX system as a Contact after it has reached its limit of 200 Contacts, the Polycom HDX system rejects the invitation but does not display a warning message to the local user. You cannot delete Contacts using the web interface. Instead, delete them in the systems local interface. You cannot add Contacts that support presence using the web interface. Instead, add them in the systems local interface. A laptop connected to a Polycom HDX 9000 system as a content source might not be able to display content when the laptop resolution is configured for 1280x720. Some DVI video sources (such as certain laptops) do not correctly support the hot plug detect pin (HPD). This can result in the source sending video in the wrong format for Polycom HDX video input ports 4 and 5. Please consult your equipment manuals to find out the behavior of the HPD pin. Presets support switching from one People source to another. Presets do not support switching from a People source to a Content source or from one Content source to another. Content at a resolution of 1280 x 1024 is scaled and sent to the far site in 1024 x 768 format unless the far site can display it at 1280 x 1024.

AVA-1064

Aura 6.0, 1-XC 6.0

AVA-1063

Contact your Avaya Authorized service provider.

AVA-1062

VIDEO-25523

VIDEO-25521

Issue ID VIDEO-25520
Description While connected to the Avaya Communication Manager, telephony features are not supported to systems behind a neighboring gatekeeper. The Avaya Communication Manager version 4 supports wideband audio over trunk calls. However, Avaya Communication Manager version 4 will not support wideband audio over a trunk to Polycom PathNavigator. Cisco PIX does not pass through Annex H, which is required by the Avaya Communication Manager. Polycom HDX systems will not connect calls across a firewall that does not pass Annex H. Avaya's IP Softphone (IPSP) with video set to manual will not negotiate video with endpoints registered to a neighboring gatekeeper. In calls placed from a Polycom HDX system, the far-site system name may show a neighboring gatekeeper, such as PathNavigator, instead of the actual system name. G728 k and G722.1-16 k audio codecs are not available when registered to the Avaya Communication Manager. Internal MCU calls from a Polycom iPower system to an Avaya IP Softphone (IPSP) or Polycom HDX system do not connect.

VIDEO-25517 VIDEO-25526

VIDEO-25516

VIDEO-25522

VIDEO-25519

VIDEO-25515

IP338 VS2277
Issue ID VIDEO-25478 VIDEO-48111
Description Avaya Communication Manager Telephony features and IPSP video mute are not supported with Polycom HDX, V500, Polycom VSX, iPower, or Polycom ViewStation FX systems behind PathNavigator. iPower IMCU calls to Polycom HDX systems using Avaya do not connect.
The Avaya Communication Manager does not support Polycom Siren 22 audio or Siren 22 stereo. 2.0.2 If you set the Gatekeeper field to Specify with PIN, you will see an additional field Outbound Call Route. Ignore this field. When configuring the Polycom HDX system gatekeeper setting to Specify with PIN, you may see an extraneous field called PathNavigator for Multipoint Calls. Ignore this field. HDX systems registered to Avaya Communication Manager might occasionally fail to place or receive calls. When registered to Avaya Aura 6.0, the HDX system does not transmit DTMF in SIP calls. When a Polycom HDX system running software version 2.6.1 sends content over SIP, the Avaya 1000 Series video endpoints display the content on the primary video channel. The Avaya 1000 Series video endpoints do not support the Binary Floor Control Protocol (BFCP) SIP content.

Workaround Place the call as a SIP call.

VIDEO-86789

VIDEO-88116
Configure HDX for Basic mode. Note: Basic Mode severely limits the features available in a call. Among other things, Basic Mode disables content, far end camera control, and encryption. In Internet Explorer, go to Tools > Internet Options and click the Advanced tab. Under the Security section, make sure that Use SSL 3.0 is the only SSL choice selected. Place the call again.
Users might have trouble using Internet Explorer to access the web interface.

VIDEO-80679

When a Polycom HDX system is configured for integration with Microsoft Office Communications Server and is in a point-to -point 2M SIP call, the call disconnects after approximately 10 hours. When People Video Adjustment is set to Stretch on a Polycom HDX 8000 HD system in a call with Microsoft Office Communicator, Office Communicator displays black video.

VIDEO-61286

Category Interoperability Microsoft

Issue ID VIDEO-81020

Description The Office Communications Server should be configured to allow no more than 200 contacts (this is the default setting). If the Office Communications Server allows more than 200 contacts and more than 200 contacts are in the directory, the Polycom HDX system may show up to 200 contacts, or none. If there is a meeting password configured for a multipoint meeting hosted on a Polycom HDX system, Microsoft Office Communicator clients cannot join the meeting. Occasionally, if three Office Communicator clients simultaneously call a Polycom HDX system hosting a multipoint call, the Polycom HDX system restarts. The user interface of a Polycom HDX system hosting a multipoint call may experience reduced response when in a high-bandwidth, 5-way federated Interactive Connectivity Establishment (ICE) call. Polycom HDX systems do not support presence in federated ICE calls. During a federated Interactive Connectivity Establishment (ICE) call between an Office Communicator client and a Polycom HDX system, the Office Communicator client disconnects from the Polycom HDX system after approximately three hours.

VIDEO-53388

VIDEO-58840

VIDEO-60343

To address this issue, enable H.239 on the Polycom HDX system.

VIDEO-88849

This issue corrects itself automatically.
Interoperability Polycom PVX

VIDEO-51274

Enable H.239.
Interoperability Polycom RMX System

VIDEO-71383

Category Interoperability Polycom RMX System

Issue ID VIDEO-74330

Description Content is sent as H.263 content when in an H.320/ISDN call with the Polycom RMX system (which is configured for H.264 content). Occasionally, when a Polycom HDX system is in a bridge call with a 5.0.1 Polycom RMX system and a large amount of packet loss occurs, video artifacts will be displayed. When a Polycom HDX system is in a call with a Polycom RMX 1000, the Polycom HDX video freezes momentarily and returns to live video only when the RMX conference video layout configuration is changed. Calls hosted on an RMX 7.0.x system might occasionally experience distorted video. A Polycom HDX system cannot dial into a password-protected call on an RMX system using a dial string in the format <conference ID>##<password> (for example, 1111##2222). A Polycom HDX system might receive Siren 14 audio rather than Siren 22 Stereo audio when it is in a 6 Mbps H.323 call on a Polycom RMX system. Polycom RSS 2000 supports a maximum call speed of 1024 kbps. To record a conference in HD using Polycom RSS 2000, make sure that the Polycom HDX system is configured for sharpness. Polycom HDX systems display blocky, gray video for a few seconds after leaving the Polycom RSS 2000 menu.

VIDEO-82335

Disconnect the call and place it again.

VIDEO-82746

2.5.0.2
Interoperability Polycom RMX System Interoperability Polycom RMX System

VIDEO-86864

Disconnect the call and place it again. Dial into the conference and then provide the password using DTMF tones when prompted.

VIDEO-88649

VIDEO-88800
Configure the HDX system's preferred call rate as 4096 kbps.
Interoperability Polycom RSS 2000

VIDEO-49888

VIDEO-51952
Category Interoperability Polycom RSS 2000 Interoperability Polycom Touch Control

Issue ID VIDEO-57005

Description In calls using a Polycom RSS 2000, audio is transmitted using G.722.1 Annex C. People+Content IP occasionally does not launch when you connect a PC to a Polycom Touch Control device via a USB cable. Do not touch or hold the Polycom Touch Control device by the black border outside the visible screen. Doing so may interfere with the Polycom Touch Control devices ability to detect touches. If you navigate into an Administration screen on the Polycom Touch Control device while in a call and the call ends, the device returns to its Home screen rather than staying on the Administration screen. When an HDX system is paired with a Polycom Touch Control device and using a Global Directory Server (GDS), the HDX system downloads directory information only from the server configured in first entry in the directory configuration page. If you place a call from the HDX systems web interface and subsequently attempt to dial that site from the Polycom Touch Control device's recent calls list, the call will not connect and will remain in the calling state indefinitely. Do not use an external control panel (such as Crestron or AMX) with an HDX system that is paired with a Polycom Touch Control.

Description If a Polycom HDX system is configured for provisioning from the Polycom CMA server, you will be unable to log in if Secure Mode in the Polycom CMA site provisioning profile is enabled. When the Polycom CMA provisions the Polycom HDX system with a scheduled provisioned profile that includes the password for a Global Directory (GDS), the Polycom HDX system is updated with the password. However, the user interface screen will show that the password has been provisioned, but the web interface will not. The ISDN Gateway check box is not enabled or disabled on the Polycom HDX system when the Polycom CMA Administrator has pushed a scheduled provisioning profile that includes provisioning values on pages of the Polycom CMA scheduled provisioning pages other than the Video Network > IP Network > H.323 Settings page. If a Polycom HDX system is configured for provisioning from the Polycom CMA server, you will be unable to log into the system if the following conditions are met: Secure Mode in the Polycom CMA site provisioning profile is enabled the DoD DSN Security Profile is configured
Workaround Disable Secure Mode in the Polycom CMA site provisioning profile. Reconfigure the Polycom HDX system with the new profile settings. None

VIDEO-80710

VIDEO-80707
Provision the Polycom HDX system with values only on the Video Network > IP Network > H.323 Settings page or manually update the Polycom HDX system via the local system interface or web interface.

VIDEO-75459

To work around this issue, delete the system settings by pressing and holding the restore button on the Polycom HDX system for 15 seconds while the Polycom HDX system powers on. Disable Secure Mode in the Polycom CMA site provisioning profile.

Issue ID VIDEO-86491

Description In some environments, the Recent Calls button might disappear from the HDX systems Home screen after CMA v5 configures a system using scheduled provisioning. When the Display button is held down, the Polycom HDX remote control displays some video output formats that are not available for Polycom HDX 4000 and Polycom 8000 HDX systems. A document will occasionally fail to print when an ISDN call is made and either endpoint performs an action with the remote control. This print failure will occur when two Polycom HDX systems have the following settings: PC and printer attached serial port mode set to pass through baud rate set to 115200 flow control to None
Workaround Use automatic provisioning and then configure the Home screen using the HDX system's web interface. None

VIDEO-56317

VIDEO-82739
Set the baud rate to 57600.

Sample Sites

Polycom provides sample numbers in the Polycom HDX directory, as well as video test numbers that you can use to test your Polycom HDX system. Please be aware that these numbers may occasionally be unavailable. The Security page in both the local and web interface does not correctly report Telnet, SNMP, or Web connections. Polycom HDX systems do not issue an SNMP alert for failed or successful attempts to log in via Telnet.

VIDEO-81300

Issue ID VIDEO-81297
Description When in a call, pressing the Camera button on the remote control and selecting Camera 1 (assuming it is already selected) changes the view from far video to near video or vice versa. However, the Camera 1 icon displayed will be the default or configured camera icon and not the icon that indicates that the video can be switched between near and far. The statistics for receive content show the maximum that might be received rather than the rate currently being received. When you add Polycom HDX microphones one at a time, the Diagnostics screen may list the version of the first microphone as None. If multiple microphones are connected and you restart the system, they are all correctly displayed. Selecting the space bar in the onscreen keyboard toggles between upper-case and lower-case letters. Polycom HDX 6000, 7000, and 8000 systems do not show the IPv6 addresses on the System Information screen when connected to an IPv6 network. This information is displayed in the web user interface under Diagnostics > System Information. The Polycom HDX system displays an IP address of 0.0.0.0 on the LAN Properties screen when the LAN cable is disconnected, even if a static IP address was configured on the Polycom HDX system.

VIDEO-69792

VIDEO-69620

VIDEO-65940

VIDEO-80600

VIDEO-80412

Category Video

Issue ID VIDEO-80580

Description Occasionally, when a 6M point-to-point SIP call is made between two Polycom HDX systems, the called endpoint displays green video at the bottom of the screen for a couple of seconds when the call initially connects, then displays normal video. Making rapid changes to the selected video source by using API commands might cause the HDX system to display frozen video from one of the sources. To prevent this situation from occurring, allow sufficient time between API commands. You might occasionally notice brief video artifacts when cycling though layouts when using dual monitor emulation. The system will automatically correct these within a couple of seconds. If you use a computer as a People video source, the video on your HDX system might be slightly clipped. If you select a camera that is connected to a video source with an unsupported video format/resolution, the HDX system might display black video. HDX 7000 HD systems using dual monitor emulation and hosting an internal multipoint call might experience frozen video as the content source in the conference changes from site to site.

VIDEO-85838

VIDEO-87018

VIDEO-85839

VIDEO-88110

Select another camera.

VIDEO-88171
Disable dual monitor emulation.

Category Web Interface

Issue ID VIDEO-80675
Description A Polycom HDX system with a BRI card installed and configured for NI-1/NI-2 Switch Protocol does not have the Auto BRI Configuration option in the web interface. The local system interface does have the Auto BRI Configuration option. When a Polycom HDX system is configured to automatically answer point-to-point video calls, the web interface does not display a message for an incoming POTS or ISDN voice call for the user to answer the call. The message asking you to accept the call is displayed on the local system interface. In the web interface, Ctrl+Z does not delete text entered into a text field. Searching the Directory via the web user interface takes up to 45 seconds to retrieve entries if Directory searches are happening on more than 4 simultaneous web interface sessions. Polycom HDX systems generate an SNMP alert for each web interface request. Occasionally, when configuring the Calendaring Service from the web interface, the green registration check mark is not displayed after selecting the Update page. Polycom HDX systems with a V.35 card installed do not issue an SNMP alert when H.320 is enabled or disabled via the web interface.

VIDEO-80674

Set Auto Answer Video calls to No. The pop-up message will then be displayed on the web interface.

VIDEO-80605

Use the Delete key to delete text from a text field. Ensure that only one user at a time performs a directory search.

VIDEO-80603

VIDEO-80106

VIDEO-80092

Refresh the browser page or configure the Calendaring Service from the local system interface.

VIDEO-80074

Issue ID VIDEO-80073
Description Polycom HDX systems with a PRI card installed do not issue an SNMP alert when H.320 is enabled or disabled via the web interface. Directory group names do not display correctly in the web interface when using Internet Explorer 7 with either Simplified Chinese, Traditional Chinese, or Korean languages. After performing a system reset on a Polycom HDX 9004 or Polycom HDX 6000, the Wake System button on the Camera Settings web interface page might be missing when the system goes to sleep for the first time. The Wake System button is displayed on the web interface after the system is awakened by the remote control. The Admin Settings > Network > IP Network > H.323 Settings > Current IP Address field in the web interface appears to be editable, but it is not.

VIDEO-79759

Use Internet Explorer 6 or Internet Explorer 8.

VIDEO-77721

VIDEO-84031
Hardware and Software Requirements
To use the web interface, you need Microsoft Internet Explorer 6.x, 7.x., or 8.x. To integrate a Polycom SoundStation IP 7000 phone with a Polycom HDX system, use the following software versions:
SoundStation IP 7000 phone software version 3.2.1 or 3.2.2 and BootROM 4.2.0 3.2.3 and BootROM 4.2.2 3.3.1 and BootROM 4.3.0 Polycom HDX series system software version 2.5.0.7, 2.5.0.8 2.6.0, 2.6.0.2, 2.6.1, 2.6.1.3 2.6.1.3, 3.0, 3.0.0.1, 3.0.0.2
Interoperability with Avaya Products
For questions and support on the Polycom - Avaya integrated solution, please contact your Avaya Authorized Service Provider.
The following Polycom HDX systems running software version 2.6.1 can call and receive calls with current generally available versions of Avaya one-X Communicator H.323 Video soft clients (R5.2 and R6.0) on Avaya Aura Communication Manager R5.2.1, R6.0, and R. 6.1: Polycom HDX 9004 system Polycom HDX 9002 system Polycom HDX 9001 system Polycom HDX 8000 system with Hardware Version A Polycom HDX 8000 system with Hardware Version B Polycom HDX 7000 system Polycom HDX 6000 system

Interoperability

The following PTZ cameras are supported for use with Polycom HDX systems:
Polycom EagleEye View (requires HDX software 2.6 or later) Polycom EagleEye HD Polycom EagleEye 1080 (requires HDX software 2.5 or later) Polycom EagleEye II (requires HDX software 2.6.1 or later) Polycom PowerCam Plus (SD camera) Polycom PowerCam (SD camera)) Sony EVI-D30/31 (SD camera) Sony EVI-D70 / Vaddio WallVIEW 70 (SD camera) Sony EVI-D100 / Vaddio WallVIEW 100 (SD camera) Sony BRC-300 / Vaddio WallVIEW 300 (SD camera) Elmo PTC-100S/110R/150S/160R (SD camera) Canon VC-C50i/Vaddio WallVIEW 50i (SD camera) Sony BRC-H700 Sony EVI-HD1
Polycom HDX systems are tested extensively with a wide range of products. The following list is not a complete inventory of compatible equipment. It simply indicates the products that have been tested for compatibility with the 3.0 release. Video conferencing systems use a variety of algorithms to compress audio and video. In a call between two systems, each end transmits audio and video using algorithms supported by the other end. In some cases, a system may transmit a different algorithm than it receives. This process occurs because each system independently selects the optimum algorithms for a particular call, and different products may make different selections. This process should not affect the quality of the call.
Type NAT/Firewall/Border Controller Product Linksys WRT54G2 NETGEAR FR114P NETGEAR WGR614v10 Polycom Video Border Proxy (VBP) 5300 E/S Management Systems and Recorders Polycom RSS 4000 Polycom Video Media Center (VMC) 1000 Avaya ACM Cisco Unified Communications Manager Cisco 3745 Codian 4505 OpenSER Polycom CMA 4000, CMA 5000 Polycom Global Management System Version 1.5.00 1.5 Release 14 1.0.2.26_51.0.59NA 9.1.5.3 5.0.0, 6.0.0, 6.4.0 2.0 build 5.3.0.110 R015x.02.0.947.3 6.0, 7.0 (must use Polycom HDX software version 2.5.0.6_00_cisco-3966) 12.4 4.1 (1.51) 1.0.2 4.0.1, 5.0.0, 5.3.0, 5.4.0 7.1.10.1