Polycom PVX Release Note page 34

Release Notes
Polycom PVX Version 8.0.2
34
Product
Polycom Global
Management System
Polycom iPower
Polycom MGC
Issue
Global Management System managers may notice incorrect
caller ID listed under the Call Status tab in the Global
Management System Manager. This occurs when a Polycom
PVX is in a video call with a ViewStation FX.
The current version of Global Management System does not
display alert messages from PVX systems.
T.120 does not work with an iPower if the iPower is configured
for encryption required.
iPower systems do not accept transferred calls from Polycom
PVX at this time.
When sharing data from PVX to an iPower system, you must
wait until the readiness tone is heard before sending data.
Sending data before the receiving end is ready to accept it,
may result in having to disconnect and redial the call.
During audio-only calls to an iPower system, the data-sharing
buttons on the PVX system may appear to be active and
functional when they are not.
Polycom PVX does not support sending snapshots when in a
conference call with an MGC-100 using H.261 protocols. To
correct this, reestablish the call using H.263 protocols.
Users may experience ghosting and freezing image video
when in a video call with an MGC-100 bridge running software
version 5.0. MGC version 5.1 addresses this issue.
PVX far end camera control (FECC) is not operable on SIP
calls through a Polycom MGC conferencing bridge.
When deactivating a T.120 data-share through a bridged MGC
call, the data-share option buttons may continue to appear
active and functional in the PVX application when they are
not.
PVX SIP calls through an MGC bridge to a VSX system
running version 7.5.2 may result in no audio being heard from
the VSX system.
In a 384 kbps transcoded conference with dynamic bandwidth
allocation, encryption, and People+Content on the MGC, the
PVX system reports packet loss. To avoid this problem,
disable dynamic bandwidth allocation for calls using the MGC.
Calls using a 128 kbps continuous presence SIP conference
room on the MGC+H29 connect as secondary mode. To avoid
this problem, set the MGC's video algorithm to H.263 and set
the video format to a format other than Auto (for example, CIF
or QCIF).In a 384 kbps call that uses a continuous presence
meeting room on the MGC, the transmit rate does not go
above 70 kbps. In a 384 kbps transcoding multipoint call that
uses People+Content on the MGC, the people transmit rate
drops when the system receives content.
3725-22754-006/A