Jump to content

KAZOO 4.2 Upgrade Highlights

Recommended Posts

  • 2600Hz Employees

Hey Everyone,

 We’re excited to announce the Kazoo 4.2 release is primed and stable for launch!

To ensure a smooth transition and address any real-time issues that may occur, we’ve segmented the upgrade into phases that we'll roll out based on your platform.

Hosted Platform Clients: We’ll be kicking off the upgrade with Hosted Platform clients this weekend - The update will begin on Sunday, March 25th, 2018 at 10pm PST. No disruption to service is expected.

Private Cloud & Global Infrastructure: If all goes well, Kazoo 4.2 will be available to private cloud and global infrastructure clients for upgrade via Cluster Manager next week (remember to let us know before you schedule an upgrade with your clients!). Look for more communications around this soon!

Open Source: Over the next week we’ll be promoting 4.2 as stable for all open-source users. Feel free to connect with us in the community if you have any questions. 

You can find highlights of what’s in 4.2 below:  (*Please note that some bugs were also released as part of 4.1 so may already be in your environment if they were deemed urgent.)

Feel free to comment or reply to this post with any questions and our team will do our best to get back to you ASAP. 


What to Expect from the 4.2 Upgrade: Feature Updates, Bug Fixes & More


  1. We are launching a refreshed login page – complete with social media buttons you can configure in our Branding app!
  2. Our Branding app has been redesigned to make it easier to brand your customer’s experience – including previews of the branding.
  3. The Voicemail Manager app has been updated to have a more intuitive experience.
  4. The Fax Manager app has s sleek new interface to enhance the usability.
  5. All email notification templates that are using the system-wide standard will be updated to a new, friendlier, nicer looking format.
  6. System admins can now “impersonate” any user on the system they have access to, so that debugging is easier, from Monster UI.
  7. Multiple Call Center improvements, including:
    1. New Features
      • A new reporting API
      • Added CSV support to reporting API
      • Improved event sending to reduce erroneous warning messages
      • Shortened callid's for recipient dialouts
      • Added ability to load all queues and recipients with single API call
      • Switch from using "Action" field to "Event-Name" to be consistent with other Kazoo applications
      • Added support for tracking non-Qubicle calls
      • Added CCV's with information about queue actions to inbound calls
      • Improved hold-treatment handling
      • Added "Event-Timestamp" to enable events to display correct timers regardless of client time correctness
      • Agent/manager role enforcement in the UI
      • Timers sync’d across different clients/browsers/time zones
      • Visually improve app loading
      • Show problem queues in real time without reloading the app
    2. Greater Stability:
      • Improved routing strategies and routing metrics
      • Improved logging for all entities
      • Improved call offer process
      • Simplified session management
      • Improved session join process to prevent timeouts due to network latency
      • Added active session check to prevent "ghost" sessions
      • Improved failure handling during outbound dialing to agents
      • Improved system startup across multiple zones
      • Improved process management across nodes
      • Added sensu checks for Qubicle to monitor telemetry

Vulnerability Fixes

  1. KAZOO-5848: A sophisticated hacker who gained access to a Kazoo server’s internal RabbitMQ management port, when deployed in a multi-zone configuration, and where RabbitMQ was configured to require a password, could manipulate the WebSockets application to emit the password for RabbitMQ access. This is due to the user/pass being part of the AMQP broker URL itself. These changes were implemented to protect against this:
    1. Filter optional AMQP headers prior to exposing externally (#4625)
    2. Ensure UI applications that use websocket channel create/answer/destroy events show the current call state properly (primarily Operator Console)
  2. The Kamailio team has notified the public of a security vulnerability where a malformed packet can be used to overrun memory space, causing Kamailio to crash. A sophisticated hacker may be able to manipulate memory space for other purposes as well. This is fixed in Kamailio 5.0.4j and higher.


Bug Fixes

  1. Fixed incorrect failure code for inbound faxes
    • HELP-34413: Inbound faxes show wrong failure code (TX not RX) if there is a failure
  2. Improved parking stops efficiency at the account level
    • HELP-34315: Parking Stops working in accounts after repeat create/delete of parking documents
  3. Improved VM security
    • HELP-34437: Improve security of voicemail for customers who do not follow our GUI setup process and misconfigure fields, to avoid hacking of insecure voicemail boxes
  4. Corrected time of day
    • HELP-34176: Time of Day not working on Mondays in some cases (also fixed in 4.1)
  5. Improved Webhook data and compatibility
    • HELP-32874: Webhook data not backward compatible with old CDR format (fixed)
  6. Removed duplicate call  recording events
    • HELP-33420: Fixed inbound call recording duplicate events
  7. Enhanced caller ID settings in Smart PBX
    • HELP-33189: Allow setting Caller ID in SmartPBX for a number in porting state
  8. Enhanced VM recording media
    • HELP-34868: Enforce media_source for cf_voicemail when recording voicemail greetings
  9. Porting updates
    • HELP-34892: Phone numbers in port_in state are not set to in_service after successful inbound calls
  10. Fixed Voicemail-to-email errors
    • HELP-34519: Voicemail-to-Email Notification is disabled: a new voicemail message might be still marked "saved" or "deleted".
  11. BLF improvements for *98
    • Support for BLF on mailbox via *98 + mailbox number
  12. Resolved Provisioner Crashes
    • KAZOO-5837: provisioner_v5 crashes when trying to get the label for presence combo key
  13. Updated device ring groups
    • KAZOO-5575: Ring group does not check if device is deleted
  14. Revised Doodle requirements
    • KAZOO-5636: Doodle should not be a required app, currently kazoo crashes when doodle is not installed
  15. Improved email notifications
    • KAZOO-5718: Comments entered in the GUI by the user for a port do not cause an email notification
  16. Enhanced ledger query functionality
    • KAZOO-5657: Queries for large number of ledgers can crash kazoo applications
  17. Improvements to Call Recording storage
    • Ensure storing call recordings to an HTTP URL works as expected (Google Drive / AWS)
  18. Fixed whitelabel upload errors
    • KAZOO-5794: After uploading a new whitelabel logo with Monster UI on sandbox, 404 on the following request to GET the /logo
  19. Improved default port templates
    • KAZOO-5717: Default port email templates don't include port messages
  20. Refined voicemail retention capabilities
    • KAZOO-5736: As a user I want kazoo voicemail to not count messages older than retention duration
  21. Qubicle Fixes
    • Cancel offer timeout when offer is rejected
    • Remove bindings for outbound recipient calls after use
    • Removed "primary_node" field from queue configurations
    • Filter invalid endpoint types before attempting outbound recipient calls
    • Fixed overflow timeout bug
    • Correctly return error codes for failures during outbound dialing to agents
    • Check to prevent duplicate sessions



Link to comment
Share on other sites

Looks great guys! I also understand there are some performance enhancements in 4.2, so don't forget to showcase them!

As part of the qubicle updates, will there be an event emitted when an agent gets on and off a non-queue call since qubicle is now aware of non-queue calls?

"Added ability to load all queues and recipients with single API call" - What is this new API call?

Any update on wiretap with the queues?

As part of the call recording storage updates: 
"Improvements to Call Recording storage - Ensure storing call recordings to an HTTP URL works as expected (Google Drive / AWS)"
Does that indicate that these storage options are supported in 4.2?

Link to comment
Share on other sites

  • 1 year later...
  • Emily R unfeatured this topic
  • Create New...