Mandatory Message Confirmation For Outbound Calls And ZRC Update

Improvements

Add a Mandatory Message Confirmation for OutboundCalls
Configure Poly Trio systems to lock and display a configurable message when the phone boots up after losing power. Until a user acknowledges the message, the phone limits outgoing calling only to certain defined contacts. You can enable the phone to accept incoming calls while locked.
This can be helpful by reminding users that they must update their registered emergency location when they've physically moved their phones.
To add a mandatory message confirmation for outbound calls:
1. Open the configuration file.
2. Enable the phone lock feature.
phoneLock.enabled="1"
3. Set the phone unlock method to require message acknowledgment from the user.
phoneLock.mode="messageConfirmation"
Note: Set this parameter to"userPasswordAndMessageConfirmation"if you want users to enter their password in addition to the acknowledgement message.
4. (Optional) Change the message that the phone displays while the message displays. The custom
message can be up to 255 characters.
The default message is:
This phone rebooted and may have been relocated. Before confirming, please ensure this phone's
registered emergency location is correct. To do this, you may require access to an online service
portal. Contact your phone service provider for details.
phoneLock.confirmationMessage=""
5. (Optional) Require users to acknowledge the messageevery time the phone reboots, regardless of
why the phone rebooted. By default, the message only displays after the phone loses power.
phoneLock.confirmationMessage.onlyOnPowerLoss="0"
6. (Optional) Enable the phone to permit incoming calls while the message displays.
phoneLock.Allow.AnswerOnLock="1"
7. (Optional) Define a contact the phone can call while the message displays. Repeat for each contact, with a maximum of five permitted contacts. For the variablex, set a number from 1 to 5.
phoneLock.authorized.x.description=""
phoneLock.authorized.x.value=""

Zoom Rooms Controller Update
Trio 8500 and 8800 systems, when optimized for Zoom Rooms, act as a controller for Zoom Rooms via the system's touch user interface and provide audio for Zoom Room meetings through the built-in speakers and microphones.
This software release runs Zoom Rooms Controller software5.9.3 (1069)as embedded software. For more information on this Zoom release, see the Zoom Help Center.
For the latest setup instructions, see theIntegratingPoly Trio Systems with Zoom Rooms Solution Guide
atPolySupport.

Bug fixes

API -Changes to the Logging configuration from the Teams Admin Center do not update the setting on the Trio phone

Calendar - Cancelled meetings continue to display from the meetings list on Triophones.

Calendar - Daisy-chained Trio phones can't connect to the Exchange server, even if the primary phone connects without issue.

Network -If you configure a phone on a DHCP-enabled network and the DHCPconversation includes 43, and then you move the phone to a DHCP-enabled VLAN with DHCP VLAN discovery enabled, the phone doesn't use the DHCP options on the second DHCP conversation.

Security - The system web interface may be vulnerable to a TLS client renegotiationDoS attack.

Security - Certificates cross-signed with DST and ISRG certificates fail verification because of an expired DST certificate.

User Interface -When Trio is in Microsoft USB Optimized base profile, the menu permitting change of Trio's role between HUB or Device mode has obscured text informing you that Trio will reboot on applying this change.

User Interface -Trio phones woken from power-saving mode by the proximity sensors display the incorrect time

Open issues

Content -If you share content using Video-based Screen Share (VbSS) and switch directly to Remote Desktop Protocol (RDP), the content sharing fails (Workaround: Restart the failed RDP content sharing to restore it. To prevent the content sharing from failing, manually stop the VbSS before starting RDP content sharing).

Device Management -The system web interface doesn't show the correct time if you change
the device time zone (Workaround: Log out and log in to the system web interface two times.

Directories -Pause characters programmed into saved contact information don't display in Recent Calls, preventing users from calling the contacts back from the Recent Calls list (Workaround: Manually dial the contact number, including the pause characters).

Interoperability -Mute controls must be managed from the Trio when running Zoom RoomConnector and ed over USB toMAC OS systems. If Trio is muted before joining a meeting, the ZRC application will not update its icon to show as muted even though the Trio will actually be muted, and all mute LEDs show red (Workaround: Use the Trio's physical mute button to unmute the Trio and resume mute state Sync).

Interoperability -The speaker test is distorted when the Trio system is connected to a Windows 11 computer using the Virtual USB app. The speaker test performs as expected if the system is connected using a physical USB cable, and other audio and call audio functions are unaffected.

Logs -Occasionally, the phone logs scheduled informational messages at higher than intended log levels. For example, default or minorError messages log at event and debug levels. This error may interfere with the boot logs

Network -While using Wi-Fi, the phone uses an IP address obtained from the DHCP server, even if a preferred static IPaddress was already configured (Workaround: Configure a static IP address using an Ethernet connection).

User Interface -Users can't delete or enter a new name for a paired device on the Trio8300 for 40 seconds because the Bluetooth pop up blocks.