Fixes Calling, Configuration , Networking, And Provisioning Issues

Improvements

WHAT'S NEW

This release includes all the features and important fixes from earlier 7.3.x releases as well as:

• Microsoft Teams version rollback to 2022 update 1C

Bug fixes

• Calling - On CCX 500 phones with the Microsoft Teams base profile, the first outgoing call after the phone reboots doesn't play a ringback tone or illuminate the set and handsfree icons until after the call connects. All subsequent calls work as expected.

• Configuration - Auto off hook number doesn't take effect unless manually rebooted.

• Configuration - Poly CCX phones configured with an unreachable provisioning server address may enter a reboot loop if the phone crashes due to repeated attempts to upload a core file.

• Networking - Failure to parse SCEP requests that use indefinite-length BER encoding in their PKCS#7 payloads.

• Provisioning - The phone failed to establish a HTTPS connection with the ZTP server at startup.

Open issues

• User Interface - CCX phones using the Genband GlobalAddress Book (GAB) clip the display of the Submit and View softkeys.

• Interoperability - Poly Lens dashboards show the private IP of a CCX phone as "unknown".

• User Interface - When putting a call on hold, a small icon at the top of the CCX active call screen may be delayed in updating from the active call icon to the hold icon.

• Audio - When using a Bluetooth connected Poly Voyager Focus set (B825), the first call after a reboot may experience a brief audio disruption.

• Provisioning - Poly CCX phones configured with an unreachable provisioning server address may enter a reboot loop if the phone crashes due to repeated attempts to upload a core file (Workaround: Use the Web Configuration interface or the phone menu to correct or delete the provisioning server address).

• Hardware - Specific user events are not extending the phone lock feature's user input expiry timer triggering the phone to lock while a user is navigating a menu (Unlock the phone as normal and continue using the menu).

• Diagnostics - The trace route diagnostic tool accessed from the Settings > Diagnostics > Network menu , does not return any results.

• Networks - The Poly web proxy code is unable to process PAC files using FQDNs containing the characters Y or Z, resulting in failed authentication with Teams.