PortSIP PBX v22.5: Key Enhancements and Performance Optimizations

PortSIP Meeting

Release Date: March 27, 2026

PortSIP PBX v22.5 is a maintenance release focused on bug fixes, stability improvements, performance optimization, and interoperability enhancements.

This release addresses issues identified in production deployments and further improves platform reliability for service providers delivering UCaaS, CCaaS, and Cloud PBX services at scale.

 

New Features & Enhancements

 

  • Added support for accessing an extension’s voicemail through DISA.
  • Updated outbound rule behavior for system extensions. When an outbound rule includes a user group condition, calls made by system extensions such as Call Queues or Virtual Receptionists now ignore that condition, since system extensions are not associated with user groups.
  • Added support for AI transcription with Deepgram when recording files are stored in public AWS S3, Azure, or private S3 storage.
  • Increased auto-provisioning support to up to 200 BLF keys for IP phones.
  • REST API enhancement: Queue agent status responses now include both the current status and the associated reason.
  • Optimized performance when querying Queue Summary Analytics.
  • CRM integration enhancement: caller and callee names are now included when logging calls to the CRM.
  • Updated CRM call logging so that the callee number reflects the final called number.
  • Updated CRM logging to use the PBX administrator-defined brand name instead of the default “PortSIP” name.
  • For performance reasons, CDR queries are now limited to a maximum of 5 years.
  • Improved outbound rule matching for transfer scenarios. For example, if extension 1001 calls extension 1002 and extension 1002 transfers the call to a trunk, the PBX now matches the outbound rule based on extension 1002.
  • Added support for using Custom Options to replace the destination URL for outbound SMS and WhatsApp messages.
  • Improved speaker recognition accuracy for AI transcription.
  • Optimized port usage under high-volume webhook traffic.
  • Updated night mode behavior for IVR and Call Queue. When night mode is active, incoming calls are now forwarded directly to the configured night mode destination without playing the prompt.
  • Allow alphanumeric sender ID for inbound SMS and WhatsApp messages.

  • Enhanced Microsoft 365 Integration:

    • Added support for controlling synchronization for specified departments, improving control over permissions, and enhancing enterprise security.
    • Added support for more granular Microsoft 365 API permissions, ensuring that only the necessary permissions are requested, enhancing security and reducing access requirements.

 

Bug Fixes

 

  • Fixed an issue where inbound SMS or WhatsApp messages sent to a Ring Group were always assigned to the first group member, even if that member was offline.
  • Fixed an issue with incorrect Average Wrap-Up calculation for Call Queue wallboards.
  • Fixed an issue where AI transcription failure could cause CRM call logging to fail.
  • Fixed an issue where CRM logging used the wrong timezone. The system now uses the tenant’s timezone.
  • Fixed an issue where, for outbound calls, the outbound caller ID configured on the calling extension or system extension did not take priority over the caller ID configured in the outbound rule.
  • Fixed an issue where, if a call arrived at an IVR, Ring Group, or Call Queue and was routed to an extension or Ring Group because night mode was active, the destination number’s forwarding rules were incorrectly ignored.
  • Fixed an issue where an agent remained in Not Ready status after declining a queue callback call, then making and completing another call.
  • Fixed an issue where, when calling a WebRTC app, the destination field in target_answer WSI and webhook events contained an incorrect username.
  • Fixed an issue in certain rare scenarios where the IP whitelist or blacklist could become ineffective.
  • Fixed an issue where, if an app meeting already had a host, participants joining the meeting could receive a message indicating that the host was empty.

 

SBC Updates

 

The PortSIP SBC has been updated to v11.2.5, including:

  • Updated the PortSIP ONE for WebRTC to v10.8.10 with the latest enhancements.

 

App Updates

 

The PortSIP ONE  for Windows, iOS, Android, and macOS has been updated to v10.8.10, including the latest enhancements.

 

Upgrade Instructions

 

To upgrade to v22.5 from a previous v22.x version, please follow the official upgrade guide:

Upgrade to the Latest Version Within v22.x

For more information or to download the latest release, please visit www.portsip.com or contact the PortSIP support team.

 

Share the Post:

Related Posts