ProCall Infinity - Release Notes 2603.0 Feature Update

When performing the update, please follow the Performing a UCServer update within a product version.  

Update notes

• If you are updating from a ProCall Infinity (DataCenter) version <= 2303.x, please note the update instructions for version 2306.0.
• When updating from versions <=2210.5 to a version >= 2403.0, you must update to one of the two versions 2306.0 or 2310.0 as an intermediate step so that the contents of the configuration database are migrated correctly with regard to line management.
• When updating from versions <=2403.x to a version >= 2406.0, all servers of the multi-server network must be terminated and the configuration database must be updated using an individually provided script before the UCServer updates can be continued.

ProCall Infinity (DataCenter) 2603.0 (Build 8.9.3.11808)

New features

• High availability through automatic failover in the UCServer multi-server environment
  Improved high availability in multi-server environments during UCServer node failover.
  In the event of a UCServer failure, users are now automatically and seamlessly redirected to available UCServers, including the consistent transfer of login details, SIP registrations and TAPI connections – ensuring stable and uninterrupted operation:
  ProCall Infinity - Automatische Umverteilung der Benutzer bei Ausfall eines UCServers

Automatic failover

Please note the ProCall Desktop for Windows dependency: The new “automatic failover” feature is available from ProCall Infinity (DataCenter) version 2603.0 onwards.

For this feature to function fully and correctly, both the server and all connected clients (ProCall Desktop for Windows) must be updated to at least version 2603.0.
For clients running versions lower than 2603.0, automatic failover is not available or is only available to a limited extent.

Bug fixes/Improvements

• The estos logos in the ProCall (UCServer and Client) installer and when launching ProCall Desktop for Windows have been updated with a new design.

UCServer

• This update resolves a critical security vulnerability related to the underlying OpenSSL version in the local UCServer web service. Security advisory: OSS vulnerability
• Various crashes and memory leaks have been fixed.
• A deadlock or freeze of the UCServer service caused by a faulty LDAP connection, e.g. to the MetaDirectory, has been resolved.

• The log files for the Microsoft Teams integration  and  ChatGPT integration  are once again written to the directory specified under "Events".

• The display in UCServer for logging into Microsoft Teams using "Service Permissions" has been improved.
• The licence for the UM (User Management) replicator is now displayed correctly in UCServer Management.
• The UCServer’s update server has been optimised, meaning that the UCServer now requires approximately 210 MB less RAM.

• Due to changes in UCServer, downloading the ProCall client via the update service was taking a very long time. The issue has now been resolved.

• An error in the evaluation and processing of rules for sites with SIP lines has been fixed.
• General improvements to performance and stability, in particular the resolution of memory leaks in UCServer
• The stability of the UCServer has been improved, including when accessing the MetaDirectory.
• The issue with the faulty INVITE message during bridged call transfer (e.g. on the OSB trunk) has been resolved.

• Numbers and letters can now be used for SIP registration on all supported PBX systems.

• If the members of a conference group are located in different places, the call is routed to all participants and can be answered. 
  
  

  Whether this call can be transferred to other participants depends on the configuration of the telephone system. 
• When using a UCServer collection group with an agent function, the tooltip for the contact in Favourites now shows which agent groups the user belongs to and whether they are logged in or not. 
• When creating SIP registrations with a "-" in the name, the "-" is no longer automatically interpreted as an instruction to create multiple SIP registrations.
• The UCServer no longer deletes PUSH registrations when it restarts.
• Issues causing the Media Server to crash when using the "Large Conference" feature via ProCall Web have been resolved.
• The line attribute "Generate lines on demand" now works if the location for this line group was set to "Automatic".
  Configuration is carried out in UCServer Management -> Lines -> Properties of a TAPI line group 
• A problem has been fixed whereby, in certain scenarios, user presences were not displayed after a UCServer restart.
• The automatic user distribution feature in the event of a UCServer failure within the ProCall Infinity multi-server environment can be enabled or disabled via the basic services in the UCServer administration console.
• Various performance improvements have been implemented for component logging. As part of this, memory leaks in the UCServer related to logging have also been fixed.
• Issues with saving the UCServer administrator password have been resolved.
  It is no longer possible to leave the password blank; it must be set via the "UCServer Server Setup".
• Various issues with the UCServer log file settings have been resolved:
  • Once the log level has been changed, these will be saved to the specified directory again and will no longer be stored in the UCServer’s main directory.
  • Specific settings, such as log file size, will be taken into account again.

ProCall Desktop for Windows

• Various crashes have been fixed.

• A problem has been fixed whereby the most recently saved favourites were not loaded when ProCall Desktop for Windows was launched.
• For calls received whilst the ProCall Client is logged out, a contact search is now performed in the locally integrated databases for the log entries.
• The search function in the ProCall Client for "external LDAP data sources" has been corrected. From now on, the search will once again cover the following LDAP attributes: 
• telephoneNumber, otherTelephone, homephone, otherHomePhone, mobile, otherMobilePhone, telephoneAssistant.
• You can change your presence status directly via the ProCall icon in the Windows taskbar.
• If the connection to the UCServer is lost, all presence statuses are set to "grey" (unavailable).
• ProCall Desktop for Windows no longer crashes on launch if the username contains an umlaut.
• On computers managed via Microsoft Intune in "Zero Trust" mode without a domain connection, DNS resolution for the UCServer via the SRV record failed because the required DNS domain was not available.& nbsp;
  A new feature now reads the DNS domain from the "USERDOMAIN" environment variable and uses it to determine the SRV record.
• Call forwarding to "Everyone" can be set again.
• The issue causing ProCall Desktop for Windows to crash when right-clicking on a journal entry has been resolved.
• To address the issue of the volume being too low at the start of a softphone call, the AGC2 stack has been enabled. 
  This is a WebRTC module designed to automatically adjust microphone volume in real time.
• If ProCall Desktop for Windows is launched without the main window and a chat message is received, clicking on the "beep bubble" opens the chat containing the message.
• The presence synchronisation between ProCall Desktop for Windows and Microsoft Outlook is now working again.
• A problem has been fixed whereby some custom actions in ProCall Desktop for Windows occasionally failed to work when specific filters were applied.
• The process of reconnecting the client, for example following a loss of network connection to the UCServer, has been improved.
• A problem has been fixed whereby call forwarding set via a call forwarding profile could not be disabled. 
• Fixed an issue where ProCall Desktop for Windows sometimes failed to use the configured connection details for the UCServer and was therefore unable to connect to the server.
• A problem has been fixed whereby, when switching to debug log level, the server communication log was only available after restarting the client.
• A problem with the offline journal in ProCall Desktop for Windows has been resolved, whereby name resolution was not performed retrospectively for offline entries when the client was launched.

ProCall Web (Preview)

• siehe ProCall App für Web Release Notes

Known problems and limitations

We publish known problems and limitations on the following pages. 

Further information

Technical overview → 

System requirements →

Comparison between ProCall DataCenter/Enterprise →