H.323 related reboot issue and local/web interface unresponsiveness fix.

Resolved Issue(s)

✔ ️ RealPresence Group Series reboots occasionally when the system loses its H.323 registration.

✔ ️ RealPresence Group Series is unresponsive locally and in the system web interface. The logs show large gaps in time between activity, and the system must be rebooted to restore functionality.

Known Issue(s)

? API - When you connect an EagleEye Cube camera to a RealPresence Group Series system, the camera near move right API command fails to return the exact camera position after executing the 'camera near setposition 0 0 0' API command.

? Audio - When you enable M-Mode, RealPresence Group Series systems can't receive audio from a Polycom QDX 6000 system

? Calendaring - The system's local interface and the RealPresence Touch device sometimes display only nine participants, even though the Calendar invitation includes more attendees.

? Call Management - When initiating a multipoint call, you might not be able to include audio endpoints and video endpoints in the same call.

? Call Management - In an AVMCU call, the system doesn't capture the packet loss information in the Call Detail Report.

? Call Management - When a RealPresence Touch device is in Skype for Business mode, adding a participant to the meeting fails from RealPresence Touch.

? Call Management - In an AVMCU call, don't place the call on HOLD while the system receives content.

? Call Management - In a point-to-point call, while trying to add an invalid participant and escalate to AVMCU server, RealPresence Group Series systems fail to send the failure message.

? Call Management - Occasionally, pressing and holding the star (*) key doesn't activate the pinned speaker feature in the internal MCU SIP calls.

? Calling - When you connect a SoundStation IP 7000 phone to a RealPresence Group Series system, blast dialing endpoints might fail.

? Calling - During a large AVMCU conference call, the performance of the RealPresence Group Series system degrades when the system receives many messages from the AVMCU server.

? Configuration - If you enable Dual Stack (IPv4 and IPv6), RealPresence Group Series systems fail to navigate from an IPv4 address to an IPv6 address.

? Configuration - If the SIP registrar password includes a backslash character, RealPresence Group Series systems fail to register with the SIP server.

? Configuration - The Picture-In-Picture configuration is only applicable when Tracking mode is set to Frame Speaker, but the is available for all Tracking modes.

? Configuration - The value of Transfer Frequency under Log Management changes to Manual from Auto at Threshold when you export and reimport the system profile to a RealPresence Group Series system.

? Configuration - Due to Lighttpd limitations of uploading huge files, the file upload fails occasionally while doing manual software updates.

? Configuration - The RealPresence Touch device gets unpaired from the RealPresence Group Series system while transferring the update package to perform a manual upgrade

? Configuration - When the SIP server is down, and the SIP failover server is configured with another domain, RealPresence Group Series systems fail to register the Skype for Business client to the failover server.

? Configuration - When you configure the PAC URL through DHCP 252 in an Infoblox DHCP server, a null character is appended.

? Configuration - Calls drop during a TIP call when you set the RealPresence Group Series system encryption to Required for Video Calls Only.

? Configuration - RealPresence Group Series systems show the wrong error message when the SCEP renewal fails.

? Configuration - RealPresence Group Series systems fail to re-register with Skype for Business Online when the IP address is changed.

? Configuration - RealPresence Group Series systems fail to restore the configuration details of the RealPresence Touch home screen button when you restore the system configuration from the system profile.

? Content - When RealPresence Group Series systems share content in a long multipoint call, the content may be sent over to the people channel instead of the video channel.

? Content - In H.323 calls above 1472 Kbps the RealPresence Group Series system might receive black video when sharing content in a RealPresence collaboration Server (RMX) call.

? Content - The Polycom Touch Control device might not be able to send content from a USB-connected local computer running Windows 10.

? Content - In some scenarios, it may take up to 15 seconds to receive Skype for Business desktop and window sharing.

? Content - In a RealPresence Group Series conference call, if you share content using Polycom Panoyou stop RealPresence Touch device content and start content using Pano, the RealPresence Group Series system local interface displays a black screen.

? Content - In a conference call, when a computer is sharing content to RealPresence Group Series using Polycom People+Content IP (PPCIP) and another computer tries to share content by entering an incorrect password, the content sharing from the first computer disconnects.

? Content - In Skype mode, there's no Visual Board support on the RealPresence Touch system when content is shared via VisualBoard from RealPresence Group Series system web interface.

? Content - When you change the RealPresence Group Series system Microsoft desktop sharing mode from Disable to VBSS or vice versa, the video output port changes to the RealPresence Group Series system due to hardware limitations.

? Content - In a Skype for Business Online environment, RealPresence Group Series systems occasionally delay displaying Remote Desktop Protocol (RDP) content.

? Content - RealPresence Group Series systems display the received content slowly when the content is above 2K resolution.

? Content - H.329 content sharing may fail intermittently between RealPresence Group Series systems and WebEx conference calls due to the system receiving a TokenRelease message from the WebEx end.

? Directories/Address Books - In the RealPresence Group Series system CDR, a RealPresence Touch device is listed as ptc in the View Name column.

? Directories/Address Books - On the Contacts tab of the RealPresence Group Series system web interface home page, the Global Entry displays based upon client policy. The displays when a user has a client policy with address book availability configured to WebSearchAndFileDownload. The option doesn't display when a user's client policy with address book availability is changed to WebSearchOnly.

? Directories/Address Books - While adding and removing speed dial contacts from the Microsoft directory server contacts in the RealPresence Group Series system web interface, the Edit Speed Dial contacts page doesn't respond and loading overrides to other system web interface areas.

❗ Hardware - When you change the RealPresence Group Series system mode from Disable to VBSS or vice versa, the video output port changes from RealPresence Group Series system due to hardware limitations.

? Installation - Downgrading platform software using a USB flash drive might cause a RealPresence Touch device to stop the downgrade process and restart.

? Inoperability - If you dial multiple Skype for Business clients at the same time, the call connects as audio-only.

? Inoperability - RealPresence Group Series systems connected to a Polycom ISDN Gateway with stereo enabled can't connect to an audio-only call.

? Inoperability - After a DNS failure during a call between a Poly Trio conference phone and a RealPresence Group Series system, the Poly Trio conference phone doesn't automatically disconnect from the call.

? Inoperability - While in Skype for Business mode, you might not be able to place a video call from the RealPresence Group Series system to voice mail.

? Inoperability - In Unify server environments, you might not be able to resume held calls after the call was transferred on a RealPresence Group Series system.

? Inoperability - When a SIP call is using a Microsoft remote desktop registered to a RealPresence DMA system, RealPresence Group Series systems registered to Lync disconnect after you press Hold on RealPresence Group Series systems.

? Inoperability - Office 365 environments don't support FIPS mode.

? Inoperability - When a RealPresence Group Series system places a 128-bit encrypted call to Avaya XT7000 or XT5000, there's no audio or video.

? Inoperability - RealPresence Group Series systems using a RealPresence Touch device registered in an Avaya environment restart when a video call with an Avaya 9641GS IP desk phone fails.

? Inoperability - RealPresence Group Series systems reboot when connected to a conference call hosted by Cisco CMS (Cisco Meeting Server).

❗ Network - Due to a network issue on AVMCU servers, RealPresence Group Series systems suddenly reboot and display a black screen.

❗ Peripherals - After an EagleEye Director II system wakes from sleep, the EagleEye IV camera might not automatically move to the preset position.

❗ Peripherals - The USB 3.0 ports on the back panel of RealPresence Group 700 systems don't support USB sets.

? Peripherals -Camera 3 doesn't appear as content on a RealPresence Touch device when the Camera 3 HDMI is connected using DVI.

? Peripherals - The blue LED on the EagleEye IV camera remains on when you shut down the RealPresence Group 310systembefore the camera has fully powered on or awakened.

? Peripherals - ThePPCIP application doesn't launch properly from a Mac device running the Catalina OSthat'sconnected to RealPresence Touch with a USB connection.

? Software - When you connect an EagleEye Director IIcameratoa RealPresence Group Series system that's being updated, the process takes approximately90 minutes to complete. Don't interfere with the update process during this time.

? Software - Manual software upgrades for RealPresenceGroup Series systems fail when upgrading from different web browsers at a time.

? Software - RealPresence Touch devices crash and reboot automatically when the admin s the Check for Software Update button and switches between the tabs in the system web interface.

? User Interface - On some touch monitors, the virtual keyboard might not display during a call on RealPresenceGroup 500 and 700 systems.

? User Interface - If you enter an incorrect system password, then change the Lock Port After Failed Login setting in the system web interface, the system is locked out after the third password attempt, regardless of the setting value.

? User Interface - On RealPresence Touch devices, the HelpDesk number might display as a regular PSTN call on the participant list.

? User Interface - After completing the setup wizard, you might see the Hello screen flash and hear a welcome sound before the log on screen displays.

? User Interface - System information and user settings aren't available when a RealPresence Touch device isn't paired.

? User Interface - The log stamp feature might not display in the Polycom labs feature list in the system web interface.

? User Interface - When you enable the Restrict to HTTPS setting on a RealPresence Group Series system, the paired RealPresence Touch device might not download the device's application software.

? User Interface - If you set monitor 1 to Far, then Content, then Near and set monitor 2 to Far, then Near and with Automatic Self View Control enabled, the far-end video displays full screen on monitor 2 and monitor 1 displays the background image in full screen (if configured)or black video (if not configured) with its local video in PIP.

? User Interface - If you set monitor 1 to Far, then Content, then Near, set monitor 2 toFar thenNear, and then disable Automatic Self View and Self View, three identical layout choices may display on the RealPresence Group Series local interface and on the RealPresence Touch device.

? User Interface - If you're logged out of the RealPresence Touch system web interface, the device screen might not refresh automatically and might continue to display the same screen and the login dialog.

? User Interface - Far-end site camera presets aren't available on RealPresence Touch devices.

? User Interface - When a RealPresence Group Series system joins a CCCP conference as an audio-only PSTN endpoint, the system may connect the call as audio/video. As a result, the PSTN party displays black video to the other participants.

? User Interface - When you end a call, RealPresence Touch devices are intermittently slow to respond.

? User Interface - In Skype for Business calls when all the attendees are muted, RealPresence GroupSeries systems don't show an attendee's video even after the organizer blocks and unblocks the attendee's video.

? User Interface - In a call, the TV user interface displays the RealPresence Group Series system name instead of the SIP username for the far-end system.

? User Interface - The RealPresence Group Series system fails to register with a Skype for Business client if the Skype for Business password contains double quotation marks.

? User Interface - When RealPresence Group Series systems are in an audio AVMCU call and sharing VBSScontent, if the call is changed from audio to video through RealPresenceTouch, the RealPresence Group Series system fails to transmit the video.

? User Interface - When a RealPresence Touch device is paired with a RealPresence Group Series system, the system information page displays a Poly Trio system even though there isn't one connected.

? User Interface - When a SoundStation IP 7000 system that's connected to a RealPresence Group Series system makes a video call, the RealPresenceGroup Series system CDR displays "-" in the call details in the View Name column.

? Video - The SmartPairing feature is not supported on RealPresence Group Series systems.

? Video - When a Skype for Business client shares a window using a dual monitor with an extended display, the content received is displayed on half of the screen of the RealPresence GroupSeries system monitor.

? Video - The RealPresence Immersive Studio may transmit a green or pink video image to the farside of a call.