ProCall 8 - Release Notes 8.8.2
| Release date |
|
| Type | Quality Update |
| Version | 8.8.2.10765 |
| Security advice | - |
You don't have the latest version of ProCall 8 yet?
When performing a UCServer update within a product version, please follow the instructions.
Bug fixes/improvements
UCServer
The total number of users is now displayed when installing or updating the UCServer.
- The restart of UCServer services has been technically optimised.
- The problem with presence statuses hanging in the integration for Microsoft Teams has been fixed, which occurred due to unexpected connection losses of the UCServer to the Microsoft Graph API.
- The ProCall App for Web no longer requires separate authorisation in UCServer.
- For the softphone connection to Auerswald PBXs, the SIP profiles that are used when creating a new softphone line group have been updated.
There is now a profile for COMtrexx and a second profile for COMpact and COMmander variants. - When connecting SIP lines to a Placetel PBX, the pickup is again carried out without a redirect.
ProCall Client for Windows
- Several "DeadLocks" and "Heap Corruption" fixed.
- The problem that the old phone number was displayed in the search result when changing the phone number via the "ProCall workstation settings" has been resolved.
- The following problems for use in "Remote Desktop Mode" have been fixed:
- Whereas it was previously only possible for one controlling ProCall client to remotely control a single controlled ProCall client, it is now possible to log in multiple controlled ProCall clients. The controlling ProCall client automatically registers which controlled ProCall client is currently active. The controlling ProCall client is located in a virtual environment, such as a terminal server, while the controlled ProCall client is running on a physical PC with a headset. This enables the user, for example, to open their terminal server session from both the company PC and the home office PC, whereby the controlling ProCall Client recognises which PC is currently being actively used.
- The controlled ProCall client now no longer displays its call windows "top-most" in the foreground as long as it is remotely controlled.
In the customer environment, the call window of the controlled ProCall client moved in front of the window of the terminal server session with the active, controlling ProCall, which made operating errors possible. - If a ProCall client had a TAPI line and a softphone line in remote control mode, the selected standard line could not be changed depending on the start sequence of the other client.