Brings Enable/Disable Option For OAuth 2.0 Authentication

Improvements

• OAuth 2.0 Authentication for Calendaring Service
  You can now enable or disable OAuth 2.0 authentication for the Microsoft Exchange Calendar from Admin Settings > Servers > Calendaring Service

Bug fixes

• Application - Far-end camera control (FECC) isn't fully disabled as expected during content sharing.

• Application - The translation Tool fails to connect to Group Series due to inconsistent certificates.

• Audio - When the RealPresence Immersive Studio Flex room wakes up for an incoming audio call, only one microphone is heard at the far end.

• Audio - After a loudspeaker test from the Diagnostics, Group Series calls ignore the DTMF tones.

• Call Management - Group Series may fail to register to Gatekeeper due to DNS failure.

• General - Group Series may automatically reboot during SIP calls when the LAN connection
  is unstable.

• General - Group Series 700 reboots unexpectedly.

• Localization - The Brasilia time on Group Series is 1 hour ahead of the correct time.

• Localization - Non-English system web interfaces don't show the correct text for Admin Settings > Audio > General Audio Settings > Audio mute incoming and outgoing calls.

• Localization - The Japanese system web interface doesn't show the long sentences as appropriate.

• Localization - The GMT +4 time on RealPresence Touch is 1 hour ahead of the correct time.

• Peripherals - Sometimes the far-end camera control button disappears on RealPresence Touch.

•  Security - The TLS/SSL server supports static key ciphers.

• User Interface - RealPresence Touch doesn't show the Media Suite systems in the participants list.

• Video - The Picture-In-Picture video flashes with the cached picture of the previous image if you share content before making a call.

• Video - The previous Picture-in-Picture local image displays for a second despite the self-view is disabled on the Trio system.

• Video - Cameras start tracking when call launches, despite the mic is muted and tracking is disabled.

Known issues

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

• Audio - When you enable M-Mode, RealPresenceGroup Series systems can't receive audio from a Polycom QDX 6000 system (Workaround: Disable M-Mode on the RealPresence Group Series 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 (Workaround: Dial audio endpoints separately from the video calls).

• Call Management - In an AVMCU call, the system doesn't capture the packet loss information in the Call Detail Report (Workaround: To get packet loss information in Skype call, check the QoE report on the AVMCU server).

• Call Management - When a RealPresence Touch device is in Skype for Business mode, adding a participant to the meeting fails from RealPresence Touch (Workaround: Set the dialing preference to SIP instead of H.323).

• 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 AVMCUserver, 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 internal MCU SIP calls (Workaround: Press and hold the star (*) key again).

• Calling - When you connect a SoundStation IP 7000phone to a RealPresence Group Series system, blast dialing endpoints might fail (Workaround: Disconnect the phone from the system before you attempt a blast dial call).

• 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 (Workaround: Disable the System LogSetting; SIP/H.323 Trace, to avoid excessive logging).

• Configuration - If you enable Dual Stack (IPv4 and IPv6), RealPresence Group Series systems fail to navigate from an IPv4 address to an IPv6address (Workaround: When you enable DualStack, enter an IPv6 DNS server address as the first DNS entry).

• Configuration - If the SIP registrar password includes a backslash character, RealPresence GroupSeries systems fail to register with the SIPserver (Workaround: Don't use the "\" character in the SIP registrar password).

• 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 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 SIPfailover server is configured with another domain, RealPresence Group Series systems fail to register the Skype for Business client to the failover server (Workaround: Configure the user name as domain\username to successfully register in the failover environment.).

• 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 system profile.

• Content - When RealPresence Group Series systems share content in a long multipoint call, the content may be sent over the people channel instead of the video channel (Workaround: Hang up the call, redial the call, and restart content).

• Content - In H.323 calls above 1472 Kbps theRealPresence 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 a Poly Clariti meeting, you can't see the shared content if you hold and resume the call when the far-end is sending content.

• 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 (Workaround: Use Polycom Pano to share content again).

• Content - In a conference call, when a computer is sharing content to RealPresence Group Seriesusing 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 (Workaround: Share content from the second computer using the correct password).

• 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 GroupSeries system Microsoft desktop sharing mode from Disable to VBSS or vice versa, the video output port changes to the RealPresenceGroup 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 2 k 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 RealPresenceGroup 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 doesn't display when a user's client policy with address book availability is changedtoWebSearchOnly.

• 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 GroupSeries 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 (Workaround: Don't use a USB flashdrive. Instead, perform a downgrade usingRealPresence Resource
  Manager and an HTTP server).

• Interoperability - If you dial multiple Skype for Business clients at the same time, the call connects as audio-only (Workaround: Set the dialing preference to SIP. In Office 365 environments, disable H.323.).

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

• Interoperability - After a DNS failure during a call between a Poly Trio conference phone and a RealPresenceGroup Series system, the Poly Trio conference phone doesn't automatically disconnect from the call (Workaround: Manually disconnect the Poly Trio conference phone from the call.).

• Interoperability - While in Skype for Business mode, you might not be able to place a video call from the RealPresence Group Series system to voicemail (Workaround: the audio toggle on the RealPresence Touch device to make an audio call to voice mail).

• Interoperability - In Unify server environments, you might not be able to resume held calls after the call was transferred on a RealPresence Group Series system (Workaround: Don't transfer held calls involving a RealPresenceGroup Series system in aUnify environment).

• Interoperability - When in 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.

• Interoperability - Office 365 environments don't support FIPS mode (Workaround: Disable FIPS mode in Office 365 environments.).

• Interoperability - When a RealPresence Group Series system places a 128-bit encrypted call to AvayaXT7000 or XT5000, there's no audio or video (Workaround: Set the encryption key to 256 on all endpoints.

• Interoperability -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.

• Interoperability -RealPresence Group Series systems reboot when connected to a conference call hosted by Cisco Meeting Server (CMS) - (Workaround: Enable Force Connection ReuseSettings on the RealPresence GroupSeries system web interface).

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

• Network - In a registered SIP call, the Group Series system may crash when the network goes down because the BYE transaction is not aborted accordingly.

• Peripherals -After an EagleEye Director II system wakes from sleep, the EagleEye IV camera might not automatically move to the preset position (Workaround: Use the RealPresenceGroup Series local interface or the RealPresence Touch device to the preset to move the camera to the selected 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 310 system before the camera has fully powered on or awakened (Workaround: Allow at least 10 seconds after powering on the RealPresence Group 310or awakening the camera before attempting to shutdown).

• Peripherals - The PPCIP application doesn't launch properly from a Mac device running the Catalina OSthat's connected to RealPresence Touch with a USB connection.

• Peripherals - Polycom Touch Control won't pair with a RealPresence Group Series system when TLS1.0 and 1.1 are disabled (Workaround: In the system web interface, go to Admin
  Settings > Security >Global Security, then clear the check boxes for Disable TLS v1.0 and Disable TLS v1.1).

• Software - When you connect an EagleEye Director II camera to a RealPresence Group Series system that's being updated, the process takes approximately 90 minutes to complete. Don'tinterfere 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 selects the Check for Software Update button and switches between the tabs in the system web interface (Wait until the software list is populated).

• User Interface - On some touch monitors, the virtual keyboard might not display during a call on RealPresenceGroup 500 and 700 systems (Workaround: End and redial the call).

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

• User Interface - On RealPresence Touch devices, the Help Desk 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 logon screen displays.

• User Interface - System information and user settings aren'tavailable when a RealPresence Touch deviceisn't paired (Workaround: Pair a RealPresenceTouch device to theRealPresence GroupSeries system to view theinformation or use the RealPresence Touchsystem web interface toview the information (the IP address is available onthe unpaired screen)).

• User Interface - The log stamp feature might not display in the Polycom labs feature list in the system web interface (Workaround: Clear the Enable Polycom Labs Featurecheck box, then reselect it).

• 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 onmonitor 2 and monitor 1 displays thebackground image in full screen (if configured)or black video (if not configured) with its localvideo in PIP.

• User Interface - If you set monitor 1 to Far, then Content, then Near, set monitor 2 to Far then Near, 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 Touchsystem web interface, the device screen mightnot refresh automatically and might continue todisplay 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 (Workaround: Change the layout on the RealPresence GroupSeries system).

• User Interface - In a call, the TV user interface displays theRealPresence Group Series system name instead of the SIP user name 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 arein an audio AVMCU call and sharing VBSS content, if the call is changed from audio tovideo through RealPresence Touch, theRealPresence Group Series system fails totransmit the video.

• User Interface - When a RealPresence Touch device is paired with a RealPresence Group Series system, the system information page displays a Poly Triosystem 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 awindow using a dual monitor with an extendeddisplay, the content received is displayed onhalf of the screen of the RealPresence GroupSeries system monitor (Workaround: Use the Desktop optionand specify the monitor toshare content.).

• Video - The RealPresence Immersive Studio maytransmit a green or pink video image to the farside of a call (Workaround: On the RealPresenceTouch interface, verify thegreen or pink video by
  selecting Self View On. Correct the symptom by restarting the system).

• Video - If you dial into a Group Series MCU using IP with extension, you may see frozen video on your Group Series endpoint.