Dubber V1.8 Release Notes

Effective: 6th November, 2014

• The concept of Teams has been introduced within an account. Basically, the Account Administrator now has ability to set up a more granular permission structure around recordings.
  • Can create/update/delete teams.
  • Can (un)associate User “dub.points” to a team.
  • Set permissions on the User “dub.points” within a team to Manager, Contribute or Listener. In turn, dictates what a User can do with recordings associated with those “dub.points”. That is; can view, can search, can tag, etc…
  • Special option has been provided for a Standard User to restrict all others on the account listening to their recordings, even the Account Administrator. Use wisely and within your company’s guidelines.
  • Note 1: The team permission structure setup for the portal, also applies for recordings management via the Dubber API.
  • Note 2: By default all existing “dub.points” will be associated with the “All Team”, so no restrictions will be applied. Up to you to set up teams accordingly.
• Making a call from the browser once logged into the Dubber portal gets a new ‘flavor’. A separate window now appears when you want to make a call, by direct entry or via the new dial pad. Once on a call the main window shows you the duration of the call until you hang up. Yes, you can now navigate around the main Dubber portal while on a call. This much-improved feature needs to be turned on for you, please contact Dubber Support.
• We all know that if a call comes through on our phones and we see ‘blocked’ or ‘No Caller Id’, most times we won’t answer the call these days. SO, when making a call from the browser, we now allow you to use a Dubber phone number you’ve associated with any of your Inbound services on the Account. More sales? Maybe, that’ll be up to you. But, you’ll get more pickups based on anecdotal evidence we’re hearing back, hence the feature now exists.
• Improvements around filtering and searching recordings. Especially, the ability to ‘(un)star’ favorite or important recordings. Like most email applications, so you should be familiar with the functionality.
• The Dubber Call Flow has been enhanced to allow you to set up some ‘rules’ around how you might treat some inbound calls. E.g. a known number can be directly routed to a particular End Point, say an Account Manager. What a great way to improve customer service.
• With the introduction of teams, we saw an opportunity to take that concept further and introduce it into the powerful and flexible Dubber Call Flow. The Account Administrator can setup a call flow that now has a “Team End Point”. What this means is that a call will randomly be allocated to any user on the account that has indicated they’re available to take a call for that team (new presence management feature on portal header). Oh yeah, they can take the call on any phone number (mobile or fixed) they provide and it will be recorded by Dubber. This is a pretty powerful feature that will only get better in the future when a user can also choose to take a call via their browser.
• All email correspondence now contains a “PO Box” for Dubber.
• Corrected the “dub.point” (label) association for an Inbound Number with IVR options that share the same End Point (number).
• An Account User can now see on their profile page all the “dub.points”.
• Developers can now try out via IODocs on Dubber Developer Website the oAuth 2.0 Spec Authorization Code option, before implementing it in their own code/solution.
• All the improvements as part of this release will be in place in the Developer Sandbox as well. Just remember, it is a sandbox and the data will be cleared out regularly.
• Various bugs fixed “behind the scenes” to further stabilize the product.
• Other background activities to make Dubber a better product and to ensure you the User are getting a quality service;
  • Improved environment and application monitoring, to allow us to be proactive around possible issues.
  • Improved the resilience and capability of our search engine.
  • Auditing of all background events on environments to further improve security.
  • Speed up deployment process, as part of ensuring future capability for no outages at all for customers/users.
  • Important Security Patches done as hotfixes – Bash Shell & SSL vulnerabilities that were affecting majority of users/applications connected to the Internet.
  • Automated processes to rollout and maintain Dubber environments, as we expand into other geographical regions around the globe.
  • Some building blocks put in place to support Inbound Phone calls being taken in the browser, for a future release.
  • Improvements to the core platform to allow Dubber to better integrate with some established Telco solutions, as they need a recording capability.