ProCall Infinity - Release Notes 2610.0 Feature Update
| Release date |
|
|---|---|
| Type | Feature Update ProCall Infinity (DataCenter) |
| Version | 2610.0 (8.9.3.12754) |
| 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.
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?
ProCall Infinity (DataCenter) 2610.0 (Build 8.9.3.12754)
New features
UCServer
- The Node.js component of the UCConnect services has been updated to the latest version (CVE-2026-111497, CVE-2026-105482, CVE-2026-105483, CVE-2026-106069, CVE-2026-106072, CVE-2026-105481).
- The status monitor has been updated. It now also displays the allocated and currently occupied conference channels, as well as the peak utilisation over the last 7 days.
- Windows Performance Monitor displays the current number of conference channels in use for the UCServer currently being monitored.
- When connected to the MX-One PBX, a fixed listening port on the UCServer can now be specified in the UCServer for SIP connections.
- When using a SIP softphone connection with TLS, the telephone system’s certificates are checked. If they are identified as insecure, the line status indicator in the UCServer management interface turns yellow, and the tooltip lists the errors detected. You should therefore check that the telephone system’s certificates are valid before carrying out an installation or an update.
Chat in ProCall
If a user has no SIP/TAPI line assigned, the corresponding telephony icons are hidden in the user interface.
In the Chat app in ProCall Desktop for Windows, calls can now also be started from the contact details in the contact widget by clicking a phone number - the same as in the ProCall Web interface.
- The context menu item for deleting a chat message is highlighted in red, consistent with other delete actions.
Bug fixes/Improvements
SecurityAdvisory – Fixing a security vulnerability
Node.js in ProCall Web has been updated to the latest version (CVE-2026-111497, CVE-2026-105482, CVE-2026-105483, CVE-2026-106069, CVE-2026-106072, CVE-2026-105481).
UCServer
- In the UCServer management interface, a warning is displayed if the SIP failover delay is shorter than the re-registration interval. You can still save the settings.
- A UCServer conference is now only available on the line to which a conference server is assigned.
- A bug has been fixed which could cause the UCServer to crash if the Performance Monitor was open whilst an update was in progress.
- A bug has been fixed which meant that the ‘Forwarded by’ field was missing from emails regarding missed calls.
- A bug has been fixed whereby favourites buttons were missing or displayed incorrectly after a user was moved to a different server.
ProCall Desktop for Windows
A bug has been fixed whereby ProCall Desktop for Windows was unable to locate the correct server in a multi-server environment connected to an Active Directory.
Chat in ProCall
- If the ‘Start chat’ permission is disabled, users can no longer create new chats; however, they can still receive messages and reply to existing conversations.
- If file sending is disabled, file attachments in a group chat can no longer be forwarded.
- Changes to user data on the UCServer are now displayed correctly again in the chat (e.g. contact widget).
- When creating a group chat, the selection tick boxes now reliably indicate the selected status again.
- Clicking on the desktop notification for an incoming chat message now reliably opens the corresponding chat in ProCall Desktop for Windows.
- Pinned group chats are now correctly restored when new messages arrive simultaneously – there is no need to reload the app.
- New messages from a contact now reappear correctly in the chat list after the chat history has been deleted.
- The confirmation message when leaving or deleting group chats now displays group names and quotation marks correctly.
- Muting and pinning now work again via the context menu in the chat search results.
ProCall Web (Preview)
Known problems and limitations
We publish known problems and limitations on the following pages.