ProCall Infinity - Release Notes 2603.2 Quality Update
| Release date | |
| Type | Quality Update ProCall Infinity (DataCenter) |
| Version | 2603.2 - 8.9.3.12258 |
| Security advice | - |
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.2 (Build 8.9.3.12258)
New features
- Large conferences now location-based – ideal for multi-site operation
Conference servers can now be set up on a location-by-location basis : Instead of a single global conference server, multiple conference servers with their own locations and lines can be configured. When a moderator starts a conference, the UCServer automatically selects the appropriate conference server based on the location of their line. Each conference server can be activated individually and has its own setting to determine whether the conference ends automatically when the moderator leaves. Administration is carried out conveniently via a new wizard in the UCServer administration interface. Existing configurations are automatically carried over.
Current Redis version 8 and TLS
Following load tests carried out with Redis version 8 (8.4), we no longer recommend Stunnel for TLS, but rather Redis with native TLS.
Accordingly, we have updated the system requirements and installation instructions for ProCall Infinity (DataCenter).
Microsoft’s discontinuation of the EWS (Exchange Web Services) API
Microsoft has announced to gradually phase out the Exchange Web Services (EWS) API in Exchange Online from October 2026 and is expected to be completely deactivated April 2027To ensure that ProCall Infinity (DataCenter) can continue to retrieve information (e.g. appointments, contacts, mailbox items) from Microsoft cloud services via this API from October 2026 onwards, the ‘access to Exchange Web Services’ which will have been blocked by then must be re-enabled (EWSEnabled=true) in time before October.
Further information on the discontinuation and the procedure to follow can be found here: Retirement of EWS API by Microsoft - what does that mean for connecting estos applications to Microsoft online services?
Improvements
- UCServer
Performance and stability when monitoring and updating presence status have been improved. The UCServer now requires less CPU power when subscribing to presence information and releases occupied memory more reliably – for example, when contacts are deleted or deactivated, or when connections are lost.
- The processing of Redis heartbeats in UCServer has been further optimised. As a result, server status information in multi-server environments (e.g. availability and licence usage) is updated more reliably under heavy load.
Bug fixes
UCServer
- The UCServer has been optimised to ensure that it remains stable and reliable even when handling a high number of simultaneous search requests.
UCWeb log files now contain significantly fewer entries: repeated connection checks at debug level are no longer logged there.
- In the event of WebSocket protocol errors, the connection is now correctly terminated with close code 1002. Previously, invalid data could lead to unstable behaviour or crashes. The connection to the UCWeb service is now detected more reliably in the event of outages and is automatically restored.
- The UCServer now behaves more reliably when automatically reconnecting to Redis Sentinel, particularly following changes to the Redis configuration.
- Changing the management server for SIP lines – particularly when doing so for several lines at once – has been made more stable. Previously, in rare cases, this process could cause the server to stop responding correctly and lines to no longer be displayed. This issue has been resolved.
- When Redis Sentinel has TLS encryption enabled, the UC Server now also connects to the Sentinel instances using an encrypted connection. In multi-server environments, the configured Sentinel master name is retained after a UCServer restart, ensuring that the Sentinel connection can be reliably re-established.
- The shutdown process for the UCServer has been made more stable. Previously, in rare cases, the server could shut down unexpectedly whilst Active Directory changes were being processed. This issue has been resolved.
ProCall Desktop for Windows
- When ‘Appear as offline’ and "StrictIncognitoMode" are enabled, presence and call activity are now correctly hidden in the search function of ProCall client – as is already the case in the Favourites view.
Known problems and limitations
We publish known problems and limitations on the following pages.