Search the Community

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 Features We are launching a refreshed login page – complete with social media buttons you can configure in our Branding app! Our Branding app has been redesigned to make it easier to brand your customer’s experience – including previews of the branding. The Voicemail Manager app has been updated to have a more intuitive experience. The Fax Manager app has s sleek new interface to enhance the usability. All email notification templates that are using the system-wide standard will be updated to a new, friendlier, nicer looking format. System admins can now “impersonate” any user on the system they have access to, so that debugging is easier, from Monster UI. Multiple Call Center improvements, including: 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 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 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: Filter optional AMQP headers prior to exposing externally (#4625) Ensure UI applications that use websocket channel create/answer/destroy events show the current call state properly (primarily Operator Console) 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 Fixed incorrect failure code for inbound faxes HELP-34413: Inbound faxes show wrong failure code (TX not RX) if there is a failure Improved parking stops efficiency at the account level HELP-34315: Parking Stops working in accounts after repeat create/delete of parking documents 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 Corrected time of day HELP-34176: Time of Day not working on Mondays in some cases (also fixed in 4.1) Improved Webhook data and compatibility HELP-32874: Webhook data not backward compatible with old CDR format (fixed) Removed duplicate call recording events HELP-33420: Fixed inbound call recording duplicate events Enhanced caller ID settings in Smart PBX HELP-33189: Allow setting Caller ID in SmartPBX for a number in porting state Enhanced VM recording media HELP-34868: Enforce media_source for cf_voicemail when recording voicemail greetings Porting updates HELP-34892: Phone numbers in port_in state are not set to in_service after successful inbound calls Fixed Voicemail-to-email errors HELP-34519: Voicemail-to-Email Notification is disabled: a new voicemail message might be still marked "saved" or "deleted". BLF improvements for *98 Support for BLF on mailbox via *98 + mailbox number Resolved Provisioner Crashes KAZOO-5837: provisioner_v5 crashes when trying to get the label for presence combo key Updated device ring groups KAZOO-5575: Ring group does not check if device is deleted Revised Doodle requirements KAZOO-5636: Doodle should not be a required app, currently kazoo crashes when doodle is not installed Improved email notifications KAZOO-5718: Comments entered in the GUI by the user for a port do not cause an email notification Enhanced ledger query functionality KAZOO-5657: Queries for large number of ledgers can crash kazoo applications Improvements to Call Recording storage Ensure storing call recordings to an HTTP URL works as expected (Google Drive / AWS) 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 Improved default port templates KAZOO-5717: Default port email templates don't include port messages Refined voicemail retention capabilities KAZOO-5736: As a user I want kazoo voicemail to not count messages older than retention duration 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

On a new cluster, latest kazoo v4.2.3, Monster-UI v4.2.10, Accounts App v4.2.0, functionally fine other than this small issue: The latest version of the Accounts app when adding a new account, unsuccessfully makes a call to a service_planner endpoint resulting in an error and ultimately an unusable Accounts app. Other apps seem fine. I search the kazoo repo and was only able to find a few references to this searching for "service_planner", mainly in the service_planner.md and cb_service_planner.erl files, none of these are able to be found other than in this commit and referenced pull request. service planner available fields to customize API (#4104) https://github.com/2600hz/kazoo/commit/5ee55d9b9c97f05b78369682c2ad0ae2f6610ac7 KAZOO-5618: Service plans planner API https://github.com/2600hz/kazoo/pull/4087 OK, looks like a new API but there wasn't a branch (including master) or RPM (Tried them all) that I could find the code in, namely cb_service_planner.erl So, looks like I can't fix this by rebuilding kazoo (even checking out master), so I should have to downgrade MonsterUI to a version that doesn't attempt to use this new API. At appearance, it would seem the problem lies in the Accounts MonsterUI app, but I was able to trace it down to a MonsterUI core template: servicePlanDetails.js The commit in the MonsterUI repo where the change appears to be introduced: UI-2390: service plan overrides with new ledgers item: https://github.com/2600hz/monster-ui/commit/3a20cad6938acd46efce554d4f7be3203c499f1d#diff-34258a55b944d8971d79d24e1871ba54R782 It appears after this change, it was also ported back to earlier 4.2.x RPM's because this string appears when grepped for on all 4.2.x RPM's. At this point I realize the solution either involves surgery or rolling back to 4.1.x so I do that and call it a day to get things working. This is sad because I would really like to use a more recent version of Kazoo and MonsterUI. I see it is effectively working on the Kazoo Sandbox (MonsterUI v4.2.10 according to the version string). On there it appears the service_planner endpoint is working correctly too. Is there a way I can check this out on open-source? If not, any idea when it might be released in the future? Also, would copy/pasting the source from github for cb_service_planner.erl work or just asking for trouble? I'm not asking for support on an undocumented feature, I'm just looking to have Kazoo & MonsterUI 4.2.x able to create a new user through the UI, and to tip you guys off on a possible bug if it ends up being one. Thanks!