ProCall 8 - Release Notes 8.9.4
| Release date |
|
| Type | Quality Update |
| Version | 8.9.4.11605 |
| Security advice | - |
You don't have the latest version of ProCall 8 yet?
Version info
Update dated 23 April 2026: Version 8.9.4 is no longer available for download, as the following issues may occur:
- When connecting an OpenScape 4000 to an ECSTA configuration with ACD agents, the UCServer crashes on start-up.
- When configuring ECSTA line groups, a tab is missing that is required for assigning the location and specifying the behaviour for activating the lines.
We are currently working on a solution and will let you know as soon as a new version is available for download.
If you are experiencing any of the issues mentioned above, we recommend temporarily downgrading to ProCall 8.9.3.
When performing a UCServer update within a product version, please follow the instructions.
Bug fixes/improvements
ProCall Desktop for Windows
- Improvement regarding an incoming call with no caller ID on a TAPI and a SIP line with the same extension: With the Mitel MiVoice 400, for example, only one call window is now displayed and the log entry is created correctly.
- Subscribing to and unsubscribing from agent groups can be automated via an action registered in ProCall Desktop for Windows.
(Prerequisite: Update for UCServer and ProCall Desktop for Windows) - A problem has been resolved whereby new installations via the UCServer Update Service would not work if only the "Advanced Remote TAPI Driver" had been installed previously.
- In ProCall Desktop for Windows, the resolution of contact details in Remote Desktop mode has been improved. In scenarios where remote control was operated using a ProCall client with a Microsoft Outlook data source and a ProCall client without Microsoft Outlook, incomplete contact details (e.g. only phone numbers) could be displayed in the call window. This affected both caller and call forwarding information and has been resolved.
In ProCall Desktop for Windows, the "Execute remote control" setting for Remote Desktop Mode has been enhanced so that the client automatically switches to remote control mode as soon as a user’s client logs in that allows remote control.
This means that the user can leave their workstation running in the office with the "Enable remote control" setting selected whilst they switch to working from home, where another PC is located. If they start up their PC, on which a ProCall instance is running with the "Allow remote control" setting, and open a Remote Desktop session from there to work with the usual applications on the office computer, they can also make softphone calls on the office computer whilst using their headset in their home office. In this case, the headset connected to the office computer is automatically deactivated.
If the client is running in a virtualised environment with the "Execute remote control" setting (e.g. on a terminal server without audio devices), the client behaves as normal.- A crash in the Microsoft Teams interface has been fixed.
- The "Remember last position" setting for the "information window" is working again.