Version 81.9.0.14

Released Date: August 15, 2019

NEW FEATURE

LDAP Server App
Added support for LDAP Server App.

LDAP Server provides centralized phone book management, which makes phone book management easy, feature rich and even automated. Once LDAP is set up, you can search the LDAP directory and look up contacts on your IP phone.

OPTIMIZATION

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.
Extension
  • 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.

  • Fixed the issue of Extension Registration Status: The registered IP address was not updated when the extension was registered to another IP address.
  • 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.

Trunk
  • The default codecs for a VoIP trunk are changed to G729A, u-law, and a-law.

    Note: Note: iLBC codec is disabled by default.
  • 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 trunk template of VoIP Innovations: A Tech Prefix is assigned to the trunk to help the ITSP to identify this trunk.
  • Refined the Peer Trunk type:
    • Peer Trunk (DID-based): Use the IP address of PBX for authentication. SIP providers route incoming and outgoing calls based on the DID number.
    • Peer Trunk (Port-based): Use the IP address and port of PBX for authentication. SIP providers route incoming and outgoing calls based on the PBX port.
    • Peer Trunk (Domain-based): Use the domain of PBX for authentication. SIP providers route incoming and outgoing calls based on the PBX domain.
    • Peer Trunk (Private Network): PBX is connected directly to SIP provider's dedicated network.
  • 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.
  • Fixed the issue of VoIP Register Trunk: If you registered a VoIP trunk to a private IP address and enabled Outbound Proxy on the trunk, this trunk could not receive incoming calls.
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.
Callback
  • 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.
Me Page
  • Fixed the issue of Me page: The Voicemail Access PIN could not be edited.
  • Fixed the issue of Me page: The administrator could not access the CDR records on Me page.
Ethernet Capture Tool
  • Optimized the Ethernet Capture Tool: Added <pcap></pcap> in the filter.conf file to quickly locate problems.
  • Fixed the issue of Ethernet Capture Tool: The capture process could not be stopped when using the Ethernet Capture Tool to capture Ethernet packet.
API
  • Optimized the Download Recording Files interface: The recording file format is changed from .yswav to .wav.
  • 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.
Linkus
The Linkus version will be updated to 2.2.27 automatically after you upgrade the PBX.
Auto Provisioning
  • Optimized DSSKey/Line Key setting: The Value field is allowed to enter maximum 255 characters.
  • Optimized Account settings for IP phones: The extension Caller ID Name will be automatically filled in the Label field.

    Note: In the earlier version, the extension number will be automatically filled in the Label field.
  • 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 page: The Auto Provisioning Device List could not display if the assigned extension name contained a line break.
  • Fixed the DSSkey issue on Fanvil: The DSSkey setting could not take effect when the DSSkey > Line is set to Auto.

  • Fixed the issue of Auto Provision Template: The setting in Other tab would be cleared if the characters ` was contained in the custom template.

  • Fixed the issue that the auto provisioning would be failed after restoring configurations from a backup file.