Release highlights

We are changing the way we manage traffic coming into Mindful for callback requests via SIP.

Starting with this release, the new Access Control List page will allow you to specify individual IP addresses or CIDR blocks of addresses that will be allowed for unlimited inbound SIP traffic. Starting in a future release, all inbound SIP traffic will be denied by default, unless the source IP address is configured on the Access Control List page.

For more information, see Access Control List after release.

Disabling multi-factor authentication (MFA) on a user account now requires a one-time MFA passcode to be entered on the Account page.

Previously, after successfully logging in with a username, password, and one-time passcode, users could disable MFA for their accounts without further authentication. The new requirement of an additional code strengthens the security of MFA-enabled accounts.

The Callback Opportunities column has been removed from the Call Target Info table on the Callback Usage dashboard.

All other metrics will remain in place on the Callback Usage dashboard.

An alternative method of authentication is now available for the Invoke a Call Answer API endpoint.

For clients who are unable to use the OAuth 2.0 authentication flow required by the POST method of the endpoint, a new GET method is available. The GET method replaces OAuth authentication with a required query string parameter containing an API Key (see below).

When creating an Application Client, an API Key will now be displayed on the page, in addition to the Client ID and Client Secret.

The API Key will be a required query string parameter for the new GET method of the Invoke a Call Answer API endpoint (see above).

Verizon CSP clients can now use an alternative to the Mindful routing token to identify your organization to the Mindful SIP router.

Rather than sending your organization's Mindful routing token via the X-Mindful-Routing-Token SIP header, you can now send the X-VZ-CSP-Customer-Identifier header instead.

Amazon Connect clients can now use an alternative to the Mindful routing token to identify your organization to the Mindful SIP router.

Rather than sending your organization's Mindful routing token via the X-Mindful-Routing-Token SIP header, you can now send the X-VoiceConnector-ID header instead. It is possible for the Mindful SIP router to map many voice connector IDs to a single Mindful organization.

Accessibility enhancements

We have made several updates to enhance compatibility with assistive technologies like screen readers, including:

• The HTML elements containing descriptive headings in Scheduler widgets have been changed to the appropriate elements for screen readers.

• Accessible Rich Internet Applications (ARIA) attributes have been applied to buttons and fields in Scheduler widgets to indicate their functions (roles) and states.

• The Phone Number field in Scheduler widgets is now appropriately labeled as a required field.

• The color contrast has been updated for radio buttons.

We continue to make updates to ensure maximum compliance with Web Content Accessibility Guidelines (WCAG).

Fixed issues

(MENG-1604) Exported Call Detail reports will now take the Type filter into account appropriately.

Previously, any selections in the Type filter (ASAP and/or Scheduled) were not taken into account in CSV exports of the Call Detail page. Now, all filters on the page will be applied to exports.

(MENG-1550) The Messaging tab of the Global Settings page is no longer visible to users with the Callback - Manager role.

This tab was not intended to be available to the Callback - Manager role, but only to client Administrators, since it determines organization-wide defaults.

(MENG-1514) An issue causing more alerts to be visible than intended for certain users has been resolved.

When a user with a Manager or Viewer role was assigned to a business unit, they could still see alerts related to Call Targets not included in their assigned business unit. Now, only alerts related to Call Targets in the business unit will be visible to these users.

(MENG-1488) We have updated an error message in Scheduler widgets to accurately describe when an invalid callback phone number has been entered.

Previously, when a customer entered an invalid phone number (with invalid formatting, unacceptable characters, etc.), an error message stating "We are currently unable to accept callback requests" would be displayed. Now, "Please enter a valid phone number" will be displayed, instead.

(MENG-1471) An issue preventing the ECBT from being updated in Datastore records has been resolved.

Previously, when the Enable Mindful Datastore Integration checkbox was selected on the Call Target page, the ECBT value was not updated for callbacks created on the associated Call Target. With this release, the ECBT will be updated for newly registered callbacks as expected.

(MENG-1010) Callbacks will no longer be dialed while the Max Requested Callbacks threshold is exceeded.

New callbacks were still being dialed after the number of current callbacks exceeded the value of Max Requested Callbacks. Now, callbacks will not be dialed in this scenario until the number drops below the threshold. The default value is 0 (unlimited), so this only affected Call Targets with an updated value.

(MENG-283) An incorrect error response from Datastore's Get Data API endpoint has been updated.

Previously, when submitting a request to the Get Data endpoint of the Datastore API without a valid contact number, a 401 Unauthorized error was returned, which did not accurately describe the issue. Now, a more appropriate 404 Not Found error will be returned, instead.