PortSIP PBX v22.2.15 and v16.4.5 Released

PortSIP CPaaS Solution

July 1, 2025 — PortSIP Announces PortSIP PBX Updates: v22.2.15 and v16.4.5

PortSIP is pleased to announce the release of PortSIP PBX v22.2.15 and v16.4.5, delivering key stability improvements and bug fixes across our robust and flexible Unified Communications platform. These updates are part of our continued commitment to performance, reliability, and service excellence for our customers and partners.

PortSIP PBX v22.2.15 — Focused on Stability

This minor release addresses several issues identified in production environments to ensure optimal performance and reliability in real-world deployments.

Bug Fixes

  • Resolved an issue where, in rare edge cases, queue agents or ring group members could remain in an “ON CALL” status even after no active call was present.

  • Fixed a potential memory leak in the queue server under specific conditions.

  • Addressed a problem that prevented successful integration with Google Workspace.

 

PortSIP PBX v16.4.5 — Maintenance Update

PortSIP PBX v16.4.5 has now officially entered maintenance mode. While no new features will be added, this release includes important optimizations and bug fixes to support long-term stability.

Enhancements

  • Webhook engine reimplemented for significantly improved performance.

  • System file cleanup routines have been optimized. Administrators can now configure the cleanup schedule (e.g., set it to 2:00 AM) via the system.ini file. See the guide Configure File Vacuum Time.

Bug Fixes

  • Fixed an issue where calls from a SIP trunk, auto-answered by a queue, could fail to route to agents if the trunk delayed sending an ACK response.

  • Resolved an issue where, in rare edge cases, queue agents or ring group members could remain in an “ON CALL” status even after no active call was present.

  • Resolved a CDR issue where calls routed to the Virtual Receptionist displayed the DID number as the callee instead of correctly showing the IVR label.

  • Fixed a bug where, if a trunk’s IP address changed during re-registration, the PBX would still use the old IP.

  • Corrected CDR direction reporting for trunk-to-trunk calls, ensuring they are properly labeled as INBOUND_OUTBOUND_CALL.

  • Fixed an issue where only the last “Advanced Routing Rule” in an inbound rule would take effect if multiple rules were configured.

  • Addressed a problem where calls initiated via REST API could result in incorrect or incomplete recording files if the call was never answered and timed out.

  • Fixed a crash scenario when “Enable Call Recovery” was activated and a call was initiated via REST API.

  • Resolved an issue in Ring Groups where, if the group was configured to repeat on “no answer” and the last member declined the call, the PBX would incorrectly hang up the call.

These updates reinforce our ongoing effort to deliver a high-performance, carrier-grade PBX platform designed for service providers, enterprises, and developers building UCaaS, CCaaS, and CPaaS solutions.

Upgrade Instructions:

  1. To upgrade to v22.2.15 from a previous v22.x version, please follow the official guide:
    Upgrade to the latest v22.x on Linux

  2. For the v16.x upgrading, please don’t upgrade the SBC! Just upgrade the PBX only. To upgrade to v16.4.5 from a previous v16.x version, refer to the following guide:
    Upgrade PortSIP PBX to v16.x

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

Share the Post:

Related Posts