VitalPBX 3 – RC 2

We are glad to announce the second release candidate for VitalPBX 3, this update brings fixes to the issues reported by our beta testers to whom we want to express our gratitude for helping us to debug VitalPBX 3 to make it more stable and even better.

Also, this new release candidate introduces some improvements to different Add-Ons, especially in the branding add-on, which now include some outstanding customization for the login page. Next, we will list all the changes included in this version.

Improvements on VitalPBX 3 – RC 2

  • Extensions: Now, it is possible to scan the devices QR codes from GUI, and also be able to send them by email on demand.
  • Add-ons Menu: Now, the add-ons menu on the login page only shows the add-ons that are already installed (Sonata add-ons or Vitxi)
  • Phonebooks: It is now possible to generate QR codes for VitalPBX’s phonebooks and send them by email. This has been implemented especially for the VitXi mobile app.
  • Time Conditions: Now, it is possible to assign a specific time zone for matching the time groups associated with time conditions. This is an extended feature, so, it will be available only for those who have any kind of license (Add-ons or Subscription) applied to the PBX.
  • Branding: Now, it is possible to fully customize colors for the login page using the branding add-on. These new settings will be applied only if the add-on has been licensed previously.
  • Tenants:
    • Now, it is possible to define a default timezone per tenant, this timezone will be used for showing date/time info across the GUI, also, for matching time conditions (Unless the time condition has a timezone different than “System”). However, users will be able to select their own timezone, in such cases, the date/time data will be shown using the user’s timezone.
    • Also, with this update, it is also possible to select what external add-ons (Sonata, or VitXi) the tenant will have access to.
  • Custom Applications: Now, it is possible to edit the extension code for existing custom applications.
  • Modules: Now, some modules’ menus come sorted according to its content. Those which use extensions come sorted by extension and those who only have descriptions comes sorted alphabetically. For now, we have sorted the menu for the following modules:
    • Inbound Routes
    • Custom Applications
    • Queues
    • Ring Groups
    • Conferences
    • Class of Services
    • Trunks

Addressed Issues on VitalPBX 3 – RC 2

  • Branding: The logo customization and others were not applied to the login page
  • System General: The add-ons menu didn’t get hidden according to the settings on the System General module
  • Endpoint Manager: It was not possible to use the current provisioning system on VitalPBX 3
  • System Misc: Time zones changes were not applied to the Asterisk Dialplan nor PHP configurations. This was producing that the script that updates BLF Hint for Time Conditions, and returning the time conditions to its default state, was providing wrong information.
  • GUI: It was not possible to update VitalPBX from the GUI. From this version onward, it will be possible to perform updates from the GUI. But for now, if you want to update to the latest RC version, you must do it from the Linux console, using the command “yum update -y“. This command will update all the packages, including Linux packages, so, we recommend you to reboot the server after updating.

Conclusion

With this new release we are getting very close to the official release of VitalPBX Version 3.0. But remember that even Release Candidate versions are still preliminary versions. So please test everything before implementing on a production environment. We appreciate all the feedback you give us, so, if you find any bugs or issues during your testing don’t doubt to let us know through our community forum. Also, if you want to know what the previous releases of Version 3.0 has had to offer you can check this article, here.

0

Comments

  1. papin0

    Bulk Extensions still doesn’t show on all the tenants

    0
  2. Mario Gutierrez

    The QR code is only available for PJSIP extensions, how ever, de 90% of the people it’s going to use SIP.

    0
  3. Mario Gutierrez

    The TLS/SRTP on the inbound is not working.

    I have a provider that work with TLS/SRTP the outbound and the inbound, so I create a sip profile with TLS/SRTP, have de certificates, the outbound is good, but in the inbound i get this error

    == Using SIP VIDEO TOS bits 136
    == Using SIP VIDEO CoS mark 4
    == Using SIP RTP TOS bits 184
    == Using SIP RTP CoS mark 5
    [2020-08-12 12:36:18] WARNING[15171][C-00000006]: chan_sip.c:10943 process_sdp: Matched device setup to use SRTP, but request was not!
    == Using SIP VIDEO TOS bits 136
    == Using SIP VIDEO CoS mark 4
    == Using SIP RTP TOS bits 184
    == Using SIP RTP CoS mark 5
    [2020-08-12 12:36:19] WARNING[15171][C-00000007]: chan_sip.c:10943 process_sdp: Matched device setup to use SRTP, but request was not!

    And this is part of my sip trunk:

    host=*********************
    user=67834957
    username=67834957
    authname=67834957
    secret=********************
    insecure=port,invite
    transport=tls
    encryption=yes
    type=friend
    qualify=yes
    disallow=all
    allow=g729
    allow=g722
    allow=opus
    allow=gsm
    allow=ulaw
    allow=alaw
    allow=h264
    allow=h263p
    allow=h263
    allow=vp8

    tls://67834957:******************@**************/67834957

    This bug is also on VitalPBX V2

    0
  4. TheG-Man

    How do I upgrade from 2.4.x?

    0

Leave a Reply

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