Summary of Changes
Please follow the guide to upgrading your PBX to the latest version.
Changes for Release v16.4.4
Date: Nov 25, 2024
Fixed an issue where the call direction was incorrect when calls were initiated via the REST API.
Resolved a bug where blacklisted numbers set to "permanent" were not properly affected.
Addressed an issue causing no voice when a call launched via the REST API failed on the first trunk route but succeeded on the second.
Fixed a bug where outbound caller IDs outside the trunk DID pool were still used during calls.
Resolved an issue where outbound caller IDs were not recorded in CDRs for calls initiated via the REST API to trunks.
Removed trunk information from CDRs for calls between internal extensions.
Fixed a queue bug where the last agent did not receive calls in queue "ring simultaneously" mode when all agents were available.
Resolved an issue in version 16.4.3 where the PBX used an incorrect IP address in the call SDP when making calls to trunks over the internet in a High Availability (HA) setup.
Changes for Release v16.4.3
Date: Sep 10, 2024
Users can now efficiently locate IVRs within the IVR list page by utilizing the search functionality.
Fixed a crash issue that occurred when using a domain for the trace server host.
Fixed a bug affecting calls using the G.723.1 codec.
Changes for Release v16.4.2
Date: Jul 24, 2024
Fixed a crash bug in the IVR Server.
Fixed a bug where video might lag behind audio in a video call recording file.
Fixed a crash bug that occurred when the RTP port was already in use by another application.
Fixed a bug that could cause calls to hang up automatically.
Fixed a bug where system notification emails were incorrectly using the tenant’s template.
Fixed an issue where the MOH music file might be incorrectly used by another tenant.
Fixed a bug where making a large number of calls could result in a new call having only one voice channel.
Fixed a bug where deploying the queue server as a cluster might cause the REST API
/api/call_queues/{id}/waiting
to return empty callers.Fixed a bug where incorrect codec usage in SNOM M400 and M900 could result in no voice.
Changes for Release v16.4.1
Date: Jun 12, 2024
The following changes are included in this release:
Support the Microsoft Teams direct routing refer request.
Upgraded the DB to PostgreSQL 14.12.
Fix an issue when provisioning the ALE H2P phone via RPS.
Fix a bug that if an extension registers to PBX from IPv4 and IPv6 devices simultaneously.
Allow set the Queue and ring group number for the BLF key.
Changes for Release v16.4.0
Date: May 23, 2024
The following changes are included in this release:
Now the PortSIP SBC supports transcoding.
Google will stop supporting the legacy FCM APIs for push notifications in June 2024, all PortSIP PBX v16.x installations need to be upgraded to v16.4.0 to make the push notifications work correctly, please reference the article: Migrate from legacy FCM APIs to HTTP v1 for Android Push Notifications.
From v16.4, when a trunk is added, the outbound call over this trunk will apply the outbound caller ID to the FROM header by default, no longer needing to make the changes for the outbound parameters manually.
Limited the file name size to a maximum of 128 characters when uploading the voice prompt files.
Support French and Russian languages.
REST API Changes
Updated
/api/mobile_push
series API, removedandroid_server_key
,android_sender_id
, addedandroid_service_account
to specify the the contents of Firebase Cloud Messaging service account JSON file.
Changes for Release v16.3.0
Date: Mar 11, 2024
The following changes are included in this release:
We’ve moved the Microsoft 365 settings from the global scope to the tenant level. Now, each tenant administrator can configure Microsoft 365 integration independently, without requiring assistance from the System Administrator.
We’ve redesigned the login page for the PBX Web Portal, Windows app, and WebRTC app.
New outbound rules will now use their own office hours by default, instead of using the tenant’s office hours.
We’ve made changes to the username format limitations.
System Administrators and Dealers are now allowed to change their usernames.
We’ve updated the SMTP username format validation to be compatible with AWS SES.
We’ve fixed a bug where, if a call was answered on the IP Phone or Desktop app, the mobile app would continue ringing for a while.
Tenant administrators can now subscribe to the CDR event for the entire tenant scope.
We’ve added an option for the trunk to remove the SRTP line, resolving compatibility issues with some trunks.
We’ve introduced a new permission to control access to company contacts.
Tenant administrators can now clear device registration and app push information on the Web Portal for an extension.
We’ve added a new feature that allows re-provisioning of all phones for a tenant.
Fix a bug count the concurrent calls are incorrect on a trunk for some special scenarios.
Support the English UK language.
REST API Changes
Remove
GET /api/token
.Remove
POST /api/token/refresh
.Remove
POST /api/token/destroy
.Add POST
/api/login/by_microsoft
for Microsoft 365 integrated login.Add GET
/api/login
for users to get their current login status.Modify
GET /api/info
to accept an optional query parameterdomain
. When thedomain
parameter is specified in the request, the server will additionally return the public propertiesname
,domain
,website
,avatar_url
,enable_ms365_integration
,ms365_authorization_endpoint
of the corresponding tenant.Add GET
/api/users/:id/status/:instance_id/destroy_status
to clear the login information of a specified user.Rename
POST /api/phones/{mac}/reprovsion
toPOST /api/phones/{mac}/reprovision
.Add
POST /phones/reprovision
to reconfigure all phones.Add a configurable property
remove_srtp_info
for the Trunk.Modify the username format validation rules to allow a sequence of 1-64 characters that can include uppercase and lowercase letters, numbers, underscores, hyphens, periods, and single quotes. However, periods are not allowed at the beginning or end.
Add
POST /api/admin/username
for users to change the system administrator's username.Add
POST /api/dealer/username
to change the dealer's username.Add
GET /api/user/call_queues
to get the list of call queues that the currently logged-in user belongs to.Add
GET /api/user/call_queues/:id/agent
to get the agent status of the specified call queue that the currently logged-in user belongs to.Add
POST /api/user/call_queues/:id/agent
to set the agent status of the specified call queue that the currently logged-in user belongs to.Add
GET /api/users/:id/call_queues
to get the list of call queues that a specified user belongs to.Add
GET /api/users/:id/call_queues/:queue_id/agent
to get the agent status of the specified call queue that a specified user belongs to.Add
POST /api/users/:id/call_queues/:queue_id/agent
to configure the agent status of the specified call queue that a specified user belongs to.
Changes for Release v16.2.0
Date: Jan 18, 2024
The following changes are included in this release:
Supports SNOM M series and Yealink W series DECT phones.
Adds support auto provisioning for Fanvil i504(W), i505(W), i506W, and i507W devices.
Changes the SNOM phone configuration file to HTM format.
Enables playing of call recording voice prompts for inbound calls.
Allows setting of office hours and holidays for each IVR DTMF input.
If an extension is registered to PBX from multiple devices, once one of the devices rejects the incoming call by 486, the PBX will also hang up the call on other ringing devices.
Adds an option for the trunk to allow or disallow the PBX to adjust the SDP direction when holding the call.
Supports auto-provisioning of emergency numbers to the IP phones, allowing the IP phone to dial the emergency number even when the phone keys are locked.
No longer displays the offline agent in the Contact Center Wallboard.
Removes the Offline status in the BLF settings.
Supports creating the transport on the port which is less than 1024 (limited permissions by some Linux).
Displays the Feature Access Code in the WebRTC and Windows Client.
Updates the apps (iOS, Android, Windows, WebRTC) to synchronize the status between the apps and IP Phones. The statuses include:
Online
Ringing
On call
Away
Do Not Disturb
Business Trip
Supports synchronization of the Do Not Disturb (DND) status by pressing the DND button on the IP phone.
Adjust the REST API rate limit to 5,000 per minute.
Changed the WSI (Web Socket Interface) events so subscribers more easily watch the extension status.
Resolved an issue that was preventing new voicemail alerts on SNOM phones.
Fixed a bug that could prevent the Queue prompt voice from playing to the caller when the Queue servers are configured as a cluster.
Changes for Release v16.1.0
Date: Nov 2, 2023
The following changes are included in this release:
Improved security; now each extension's IP Phone configuration file is stored in a separate directory with a random name to prevent guessing even if the phone MAC address is leaked
Integrated Microsoft 365 and enabled Single Sign-On (SSO)
Implemented Contact Center Wallboards
Introduced skill-based routing for ring groups
Introduced skill-based routing for queues
Added support for Last Called Agent Routing for the queue
Supported setting agent status to Not Ready after the agent completes a Non-ACD call
Introduced Queue Manager Role
Changed the CTI menu name to Contact Center
Implemented custom headers at tenant level, allowing the adding of custom SIP headers for a call and relaying of specified custom headers for a call
Optimized High Availability (HA) for On-Premise and AWS deployments
Enabled scaling of the Media server, Queue server, Virtual Receptionist Server, and Meeting server as a cluster
Implemented Direct Inward System Access (DISA)
Added support for meeting invitations and joining meetings via link
Added support for Hotdesking
Introduced the FAC
*70
and*71
for HotdeskingAdded theme support, allowing customers to adjust the themes of the WebRTC Client, PBX Web Portal, and SBC Web portal to fit their business style
Added support for Italian and Spanish languages and voice prompts
Added support for Speed Dial 8 and Speed Dial 100
Added functionality to resend welcome emails to extensions
Enabled voicemail PIN authorization by default
Allowed contact's phone number to be empty
Refactored the WSI (WebSocket Subscribe Interface)
Enabled changing the user's presence status via BLF key
Fixed a bug preventing SNOM phones from picking up calls via BLF key
Introduced Advanced Routing for inbound rule that allows routing of inbound calls based on years, months, days, weekdays, and any time shifts
Added a notification template for meeting invitations
Implemented max concurrent call limits for trunks at both global and tenant levels
Added functionality to send notification emails when max concurrent calls on a trunk are reached
Introduced user personal contacts feature
Implemented the User-Agent blacklist
Added support for associating IP addresses with CIDR format for a trunk
Optimized performance for WebRTC, outbound calls, and video meetings
Introduced Recipients for Shared Voicemail that sends email notifications to them
Allowed specifying outbound caller ID for the outbound rule
Supported random routes for an outbound rule
With the PortSIP PBX setup wizard, the web domain field is now mandatory to enter
Adjusted the REST API rate to 1,000 requests per minute per IP address
Added Virtual Group Park in the BLF keys, supporting Fanvil, Yealink, and Dinstar phones
Added support for more new models of Fanvil IP Phones and intercom devices
Added support for more new models of Yealink IP Phones
Added support for more new models of SNOM IP Phones
Allowed recharging with a negative amount to reduce the balance
Made some other minor changes and improvements
Fixed some minor bugs
Changes for Release v16.0.4
Date: August 8, 2023
Fixed a security issue.
Fixed a bug that can't hear early media when launching the call by REST API.
Changes for Release v16.0.3
Date: July 17 2023
The following changes are included in this release:
Fixed a bug that caused SNOM phones to fail to download configuration files when auto-provisioned using a custom template. The issue was due to the configuration file name being in lowercase instead of the phone’s MAC address. For more details, please read the article on Custom IP Phone Templates.
Fixed a bug that caused mobile app push notifications to expire after 1.5 days. The expiration time has been changed to 60 days.
Improved compatibility with 2N devices. 2N devices appended a non-standard server port to the TO and FROM headers in REGISTER and INVITE messages, causing calls to ring groups to return a 480 error.
Fixed a bug that the video meeting recorded is not working.
Fixed a bug that caused the media server to hang when video call recording was enabled in the PBX.
Fixed a bug that screen sharing did not work during meetings when the PBX was running on a Linux server.
Automatically determine if the server’s IPv6 is disabled, and if so, do not attempt to bind the service to the IPv6 interface.
Added support for configuring the first BLF as a speed dial for Fanvil i series intercom devices via auto-provisioning.
Changes for Release v16.0.2
Date: June 1, 2023
The following changes are included in this release:
Updated the certificates for Apple push notifications. Users must upgrade the PBX to make the PortSIP app work with push notifications.
Changed the default retain days for recording files, log files, temporary files, and call report files.
Changed Max-Forwards from 20 to 70.
Added support for visual park feature with Fanvil IP Phones.
Improved voice mix in meetings.
Fixed a bug that did not use new brand name for creating custom phone templates.
Fixed bug that displayed incorrect presence status.
Fixed bug that sent NOTIFY for new voicemails.
Fixed billing bug that added one more billing round if billing time was multiple of 60 seconds.
Fixed push status display incorrectly on the user list page.
Changes for Release v16.0.1
Date: March 30, 2023
The following changes are included in this release:
If the "Set agent to Ready automatically" option of the queue is disabled, an agent’s status will be restored to their previous status instead of "Wrap up" after they complete a non-queue call.
The license key will only display the last part and mask other parts with *.
A new REST API
GET /api/sessions/directly
has been added which allows launching calls by URL.The REST API
POST /api/users/{id}/call
has been removed.When a caller presses a DTMF that is not predefined, a prompt will play.
The MOH file of the queue is no longer mandatory. The queue will use the default MOH file if the user has not uploaded a MOH file for a queue.
If the user is offline and push notifications are enabled, their status will be displayed as "PushOnline" in the Web portal.
The Web portal will display the language as the browser language.
The WebRTC client URL port has been changed to 10443. Don’t forget to create the firewall rule for port 10443 on TCP.
Passwords will be auto-generated when creating a user.
Custom menus can be used to link to external websites.
The IP Address will be displayed when viewing the details of an online user.
If a user signs in to the Web portal with an incorrect password or if the user does not exist, just return the message "Authentication Error" and no longer return the detailed reason.
The issue where auto-provisioning for GrandStream IP Phones the URL is wrong has been fixed.
The issue where emails failed to send with some SMTP servers has been fixed.
The issue where there may be no voice after completing an attended transfer has been fixed.
The issue where extension call forwarding is not affected if the call comes from Virtual Receptionist or Queue has been fixed.
The issue where the outbound caller ID is set as starting with + and it won’t set to the INVITE message when making a call to the trunk has been fixed.
The issue where if a user registers to PBX from multiple devices and launches a call from REST API with that user and the call actually answered but the CDR will display as not answered has been fixed.
The issue where if you launch a call by REST API, one party may have no voice has been fixed.
In the Webhook and WSI messages, the ID has been changed from in64_t to string in order to be compatible with JS.
The billing issue is that if the call duration is multiples of the billing circle, don’t plus more 1 billing round; in the previous version, if the duration is 10 seconds and the billing circle is 5 seconds, we will charge 3 rounds, now just charge 2 rounds.
Changes for Release v16.0.0
Date: January 16, 2023
The following changes are included in this release.
New Admin web portal
New rebranding engine
Rewritten all REST APIs
Introduced dealer system, support distributor, sub-distributor, reseller
Support call park and group call park
Support group pickup
Support shared voicemail
Support automatic callback
Support queue callback
Support rich call reports
Notifications, ability to configure the types of email notifications that the system sends to users
Custom notifications template
Custom IP Phone template
Roles Based Permissions
Custom Role
Feature Access Codes (Dial Codes)
Password policy
Integrated SBC
Support Microsoft Teams Direct Routing
Billing on tenant
Billing on user
Online charging
Offline charging
Multiple office hours per day
Route calls based on the DID number range
Visual IVR Editor
Voice Announcement
Audit log viewer
Trunk-Based Outbound Caller ID
Outbound caller ID for tenant
User Profile Picture
RFC3323 Privacy Mechanism
Priority for outbound rules
Last updated