New Update: VitalPBX 2.3.8

We are so pleased to announce that today we are releasing our new update VitalPBX 2.3.8. This version includes all of the changes announced on VitalPBX 2.3.7 (RC), and some other improvements and bug fixes.

Thanks to all of our users, beta testers, and all of the VitalPBX community for reporting issues, suggest improvements, features, and contribute to the project on all levels to make VitalPBX better and better.

Next, we will list all of the changes included in this version.

Improvements

  • Queues CallBack:
    • Dial Agents First: A checkbox labeled “Dial Agents First” has been added to the Queues Callback dialogue. If it is set to yes, the scheduled callbacks will be sent first to the agents and then to the customer.
    • Daemon: Now it is possible to define from the “System General” module how frequently the Queues Callback service will search for scheduled callbacks.
  • Geo Firewall: 
    • Select / Deselect Countries: We’ve added a couple of buttons at bottom of the Geo Firewall add-on to select/deselect all the countries at once.
    • Countries Menu: We’ve added the possibility to search countries through the Geo firewall menu for selecting or deselecting, when clicking the desired country on the menu.
  • Extensions: now the extensions menu is sorted ascending by the extension number.
  • I18n: Now VitalPBX is almost fully translated to the Italian language.

Fixes

  • Trunks: The calls got into an infinite loop when the defined dialing manipulation rules were ambiguous.
  • Queues: The ringback tone played on queues when MoH was set to “None”, didn’t correspond with the indication tone (zone tone) defined on “SIP Settings”.
  • Inbound Routes: Enabling call recording on inbound routes did not guarantee that the calls were fully recorded, especially the transferred calls.
  • DialPlan: When trying to transfer an outgoing call from one internal extension to another, it was not possible, due that asterisk was trying to use the trunk channel instead of using the caller (extension) context.

If you want to know what other features, improvements, and fixes include this version, please visit the following link: VitalPBX 2.3.7 (RC).

Release 2

Improvements 

  • Backup and Restore: OpenVPN certificates and the HTTP certificates, are now added as part of VitalPBX’s backups. 
  • CID Modifier & CID Lookup: Now it is possible to define a custom timeout for HTTP/HTTPS requests. This may avoid for calls to get stuck for a long time when requesting some URL configured on these modules. 
  • I18n: Update Spanish and Russian translations. 
  • VitalPBX CLI: Now it is possible to restore a backup using VitalPBX’s command tool (vitalpbx –restore-backup {BACKUP_PATH}). 

Fixes 

  • Extensions: Due to the introduction of the DID range feature on Inbound Routes, the extensions module collapsed because this method was not filtered fully. 
  • Multi-Tenant: The direct pickup feature was getting mixed between tenants, allowing that calls get picked up from extensions outside of the tenant. 
  • Backup and Restore: On previous versions of VitalPBX it was not possible to restore the voicemail audios. 

Security 

  • Firewall: Now VitalPBX’s firewall block by default the most common SIP scanners: “friendly-scanner”, “sip-scan”, “sipcli”, “sipvicious”, etc. on future versions of VitalPBX it will be possible to define this kind of blocking directly from the GUI. 

Release 3

We’ve released VitalPBX 2.3.8-3, due that one of our partners has reported that on the previous version it was not possible to perform a full restore. So, we made the appropriate testing, and effectively the issue was present. With this in mind, this version only includes the fix for restoring the backups from the GUI and from the Linux console.

Important Note: We fully recommend to update your add-ons after updating VitalPBX. This is to keep compatibility, and always have the newest features and fixes.

Get to know about VitalPBX, our services and how we can help you achieve your goals in our official website.

0
October 7, 2019

Leave a Reply

Your email address will not be published. Required fields are marked *