Adds Support For 25 Speed Dials And Brings Several Quality Fixes
Improvements
Support Up to 25 Speed Dials
You can now choose how many (5, 10, or 25) speed dials to enable in Admin Settings > General Settings > Home Screen Settings > Speed Dial > Number of Speed Dials. Edit the speed dial shortcuts on the Home Screen from Manage Favorites > Edit Speed Dial.
Bug fixes
· API - Group Series intermittently fail to start an SSH session.
· Audio - The monitor audio resumes upon reboot after you set the Video at to DVI to block it on a Group 550 system
· Calendaring - The calendaring service fails to register to Poly One Touch Dialvia web proxy.
· Call Management - Group Series system doesn't connect to the alternate gatekeeper proposed in the reject message from the primary gatekeeper.
· Calling - Group Series system ignores calls with large messages.
· Conference - In a call routed by a gatekeeper, the internal MCU doesn't show the proper video when some participants leave the conference
· General - Group Series system crashes during content sharing.
· Interoperability - When a RealPresence Group Series system is registered to Skype for Business, the system fails to connect to a third-party endpoint if it's already connected to a Cisco endpoint.
· Network - When the hostname of the proxy server contains uppercase "Y" or "Z", Group Series can't join external Skype meeting
· Peripherals - Camera tracking doesn't work after the EagleEye Producerupgrades to 6.2.2.7
· Software Updates - Can't upgrade from Polycom Software Server.
· Software Updates - Poly Trio VisualPro doesn't upgrade within the configured maintenance window.
· Video - If you dial into a Group Series MCU using IP with extension, you may see frozen video on your Group Series endpoint.
Open 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 near setposition 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 GroupSeries 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 DetailReport (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.
· 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 option 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 SIP failover 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 fail over 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 - In a RealPresence Immersive Studio Flex Virtual Meeting Room call, the primary codec is encrypted while the secondary codecs are not
· 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 (Workaround: Manually reconfigure the home screen of the RealPresence Touch device in theRealPresence GroupSeries system web interface).
· 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 15seconds 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 Token Release 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 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 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 flash drive. Instead, perform a downgrade usingRealPresence ResourceManager 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 preferencetoSIP. In Office 365environments, disableH.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 FIPSmode (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 to256 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 CMS (Cisco Meeting Server) - (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
· Network - During a failover, Group Series may take up to thirty minutes to register to the alternate GK.
· 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 aRealPresence Touch device when theCamera 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 aRealPresence Group Series system when TLS1.0 and 1.1 are disabled (Workaround: In the system web interface, go to AdminSettings > 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 s the Check for Software Update button and switches between the tabs in the system web interface (Workaround: 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, 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 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 log-on screen displays.
· User Interface - System information and user settings aren't available when a RealPresence Touch device isn't paired (Workaround: Pair a RealPresenceTouch device to the RealPresence GroupSeries system to view the information or use the RealPresence Touchsystem web interface to view the information (the IP address is available on the unpaired screen)).
· User Interface - The log stamp feature might not display in the Polycom labs feature list in the system web interface (Workaround: Clear theEnable 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 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 toFar, thenContent, thenNear, set monitor 2 toFar then Near, and thendisable Automatic Self View and Self View,three identical layout choices may display onthe RealPresence Group Series local interfaceand 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 participant
· 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 Group Series 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 Group Series system).
· User Interface - In a call, the TV user interface displays the RealPresence Group Series system name instead of the SIP user name for the far-ends ystem.
· 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 VBSS content, if the call is changed from audio to video through RealPresence Touch, 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 Group Series system monitor (Workaround: Use the Desktop option and specify the monitor to share content).
· Video -The RealPresence Immersive Studio may transmit a green or pink video image to the far side of a call (Workaround: On the RealPresence Touch interface, verify the green or pink video by selecting Self View On. Correct the symptom by restarting the system).