Seitenhistorie

STARFACE UCC Client for Windows, Version 6.7.0.176

The technical change history contains a more detailed view of the changes in the new version. The installers (as MSI and EXE files) can be found on the STARFACE Downloads page.

The STARFACE UCC Client for Windows requires Windows 7 or higher

Version 6.7.0.176:

Improvements

• Added the ability to assign two default status texts: auto-away, logged off
• Added the option to deactivate navigation in the UCC Client's internal browser, as this feature could have negative effects on the UCC Client's memory footprint [Call#6926009]
• Function keys which are not supported in the UCC Client are now hidden

• Address book contacts now no longer attempt to display a presence status on mouse-over, as they do not have one

• Microphone gain level can now be set automatically (setting can be activated via the expert mode)
• Improved phone number detection in the Outlook Connector [Call#6910907]
• The client now dials phone numbers correctly that begin with +49 0 [Call#6923359]
• "Send Email" is now available via the search function in the Quick Access Bar and the Call Manager) [Call#6916577]
• The names of telephone conference participants are now also able to be resolved from the Outlook address book
• Security: OpenSSL library updated to version 1.1.0j
• Separate ringtones for internal and external calls can now be set in the expert configuration
• The installer now prompts the user to restart their computer if the .Net Framwork 4.7.2 needed to be installed

Bugfixes

• The chat status text was retained when the UCC Client was first set to "Away" due to the user having logged off and then set to "Available" again. [Call#6931462]
• In some cases, a chat message that was written into the Interaction field of a call was not sent.
• Network connectivity issues caused persistent problems with phone calls
• Users had access to redirections, regardless of the permission setting
• The function key "activate modules" was available regardless of the permission setting
• Links in chat messages were displayed incorrectly if they contained numbers
• Received files could not be opened if the file name contained Umlauts (ä/ö/ü)
• The presence status text remained in place after the user logged out [Call#6927802]
• The OK button to create a Support Package was not displayed at high DPI scaling factors
• Fixed miscellaneous typos in the settings window
• The doorline feed was not automatically scaled to the size of the embedded panel [Call#6914650]
• No error message was displayed when attempting to save an iFMC number that is already assigned [Call#6921452]
• No error message was not displayed when saving a planned conference failed [Call#6922699]
• It was possible to create a duplicate iFMC device by adding an iFMC device with a canonical phone number
• It was possible for the client to remain unregistered after the network connection was lost and restored
• Long caller names were shortened and covered the call duration indicator
• Names and email-addresses of planned conference participants are now read-only [Call#6922699]
• Quickdial function keys incorrectly had a context menu symbol
• It was possible for the entire window to be pushed to the foreground instead of just the call manager panel on a ringing call [Call#6905727]
• It was possible for the search function in the Outlook Add-In to return no results [Call#6916578]
• Address book contacts could not be created via the WCF API
• REST services such as conferences and function key creation could not be used when the user did not have the permission "Address book"
• The Outlook Connector and Fax Printer did not work properly if HyperV was installed locally
• The Outlook Connector's contact search-bar did not work after a Windows system update