For Administrators - Polycom RPX HD 400 Series Release Notes

For Administrators

The following table lists the known issues relevant to RPX HD administrators.
Feature Description
Audio/Video When the primary codec answers an incoming video call, any HDX codecs that are not being
Calls used will automatically accept any other incoming video calls if the following conditions exist:
To prevent unused codecs from accepting any incoming calls, use the Do Not Disturb timer.
To change the amount of time before Do Not Disturb is activated, access the
DoNotDisturbTimer field in the System_Config.ini file. In this field, you can enter a value
between 10 and 300, or leave the value at 0 if you want to keep the feature disabled:
For example, DoNotDisturbTimer=120 sets the parameter to 120 seconds.
If you use the web UI to place a call that is not at the default call speed, the codecs will not
automatically adjust to the same call speed. The Primary codec will connect at the call speed
specified in the HDX web UI Call Quality field, but the remaining codecs will connect at the
default call speed.
To avoid this issue when placing a call using the web UI, connect to each codec individually
at the desired call speed (if the desired call speed is different from the default).
Avoid using the suffixes '1', '2', '3', and '4' for your audio speed dial name entries. Using
these suffixes may cause the system to incorrectly interpret them as an ITP suite, instead of
distinct audio speed dial entries.
Avoid creating directory entries that have an "&" symbol in the name. If you do so, the entry
will appear on the site list with the word "amp" in the name rather than the "&" symbol.
When the RPX is in a call, sending Telnet commands to change the video format may not
work properly.
To avoid this issue, do not use Telnet commands to change the video format when the RPX
is in a call.
If you use the web UI to place a call that is not at the default call speed, the codecs will not
automatically adjust to the same call speed. The Primary codec will connect at the call speed
specified in the HDX web UI Call Quality field, but the remaining codecs will connect at the
default call speed.
To avoid this issue when placing a call using the web UI, connect to each codec individually
at the desired call speed (if the desired call speed is different from the default).
When an RPX calls another RPX in a point-to-point call, the codecs begin to connect one at a
time. If network resources become limited, not all of the codecs may connect, which may
make it appear that one of the projectors is not working properly. If a projector does not work
correctly in a call, you should check if the codec connected. If it did not connect, reducing the
call bandwidth may solve the issue.
If your ITP environment is configured to use both the LDAP directory and H.323 Gatekeeper
functions, and your speed dial entries are not IP addresses, video calls may take longer to
connect due to the additional communication involved between the various components in
the solution.
1. The RPX 200 Series or RPX 400 Series is in a single endpoint video call with a
VSX or HDX video conferencing system (video ad-hoc dialing).
2. The RPX 400 is in a video call with an RPX 200 Series, a TPX™ 306M, or a TPX
204M.
DoNotDisturbTimer=x where x is the value (in seconds) of the desired timeout
period.
9