Released Date: August 7, 2019


System Stability
  • Fixed the system issue: Neither internal calls nor external calls could be established when multiple Linkus Push channels were not released.
  • Fixed the system issue: The system would crash after receiving an abnormal ACK packet (Non-existed extension number in the From header and no tag in To header).
  • Fixed the system issue: The PBX might crash for high CPU usage when the Call Pickup feature was used.
  • Speed up the hard disk formatting.
  • Optimized the system stability: If all extensions were selected on a configuration page (e.g. Outbound Route page), the Extension List page would get stuck.
  • Fixed the Presence issue: DND status could not be changed on web.
  • Fixed the issue of Extension Monitor: The extension with 1-digit number could not be monitored.
  • Fixed the issue of Call Forwarding: If the Call Forwarding destination was set to a mobile number, the mobile number Prefix could not be deleted.
  • Fixed the issue of Extension List: The Extension List page could not display if the database has an error of the extension User Password.

  • Optimized All Busy Mode for SIP Forking: PBX would send “486 Busy” message to the caller when the callee is busy.

    In the earlier version, PBX would sent “603 Decline” to the caller.

  • Added support for processing P-Preferred-Identity (PPI) header in the request message.

    Added the P-Preferred-Identity (PPI) option to Outbound Parameters and Transfer Parameters(Settings > PBX > VoIP Trunk > Advanced).

  • Optimized the Register Trunk settings: Special characters ; & " ' \ < > ` | are allowed in the Password field.
  • Fixed the issue of Peer Trunk: Fail to register a peer-trunk by using Chinese characters in Username field.
SIP Settings
  • Added support for getting DID and Caller ID from P-Preferred-Identity (PPI) header.
    • Added P-Preferred-Identity option to Get DID From and Get Caller ID From (Settings > PBX > VoIP Trunk > Advanced > Inbound Parameters).
    • Added P-Preferred-Identity option to Get DID From and Get Caller ID From (Settings > PBX > General > SIP > Advanced).
  • Added the iLBC Mode: You can go to Settings > PBX > General Settings > SIP > Codec > iLBC Settings, select the iLBC mode: 20ms (default) or 30ms.
Outbound Routes
  • Fixed the issue of Outbound Routes: If 100 trunks were selected for an outbound route, the users could not make outbound calls through this route.
  • Optimized the Callback feature: If the Peer-Trunk is used for Callback, the From header in INVITE request would use its DOD number in priority.
    • If the peer trunk has no DOD number, PBX will use "callback+original caller ID" in From header, which would cause a callback failure.
    • If the Register-Trunk is used for Callback, make sure the From User is configured, or callback would fail.
Call Queue
  • Fixed the issue of Call Queue: The CPU usage was too high when transferring an external call to a queue by dialing *75.
  • Fixed the issue of Queue custom configuration: The custom configuration in which defined the incoming calls transferred to the failover destination when the queue members were busy or ringing didn't take effect.
  • Fixed the issue of Call Queue: The Queue would work abnormally after you transferred an external call to a queue by dialing *75.
CDR and Recording
  • Fixed the issue of Call Recording: If call was parked, the conversation resumed on another phone would not be recorded.
  • Fixed the issue of CDR and Recording: The PBX did not generate a CDR and Recording file when an external call was transferred to call queue.
  • Optimized Recordings Auto Cleanup: The recordings can be cleaned up automatically even if the home partition is not created when installing PBX system.
Hot Standby
  • Fixed the issue of Hot Standby: The File Share function could not work after the Hot Standby was enabled.
  • Fixed the issue of Hot Standby: The data was not synchronized between the primary server and the secondary server if the secondary server took over as an active server.
  • Fixed the Firewall issue: If the default firewall rules were deleted, the rules would be automatically restored after the PBX was rebooted.
User Permission
  • Fixed the issue of User Permission: Up to 1000 extensions were displayed and available to be selected when granting permissions.
Me Page
  • Fixed the issue of Me page: The Voicemail Access PIN could not be edited.
  • Added support for Cross-Origin Resource Sharing (CORS),which allows JavaScript clients from a different origin to access PBX APIs.
  • Fixed the issue of Call Transfer API: The API program would be restarted if Call Transfer API was used.
  • Fixed the Extension Status report: PBX didn't send API report when the extension status was changed.
  • Fixed the Apply issue: If the third-party server frequently sends API application requests, the PBX might fail to establish internal calls and external calls.
  • Fixed the issue of DTMF report: The infos parameters were not sent to the 3rd-party server because that the URL was incorrect.
  • Fixed the issue of DTMF report: No infos parameters in the DMTF report when you dialed an external number through IVR and the callee pressed keys following by the IVR prompt.
The Linkus version will be updated to 2.2.21 automatically after you upgrade the PBX. Check the updates of the new Linkus App in the followings.
  • Added support for Linkus Cloud Service.
  • Fixed the issue of Linkus Call: The Linkus user in the ring group could not answer the call, which is transferred from another ring group after timeout.
  • Fixed the issue of Linkus Email: The login QR code could not be displayed if the email was sent to Gmail, Whitebox, and Outlook.
  • Fixed the issue of Linkus Call: If All Busy Mode for SIP Forking was enabled, the Linkus client, which was a Ring Group member could not receive calls.
Auto Provisioning
  • Fixed the issue of Auto Provision Template: The special characters %cn in the custom template could not be identified correctly and would be deleted.
  • Fixed the issue of Auto Provisioning Device List: The Auto Provisioning Device List could not display if the assigned extension name contains a line break.