Release Notes

Bandwidth has released an Answering Machine Detection feature for our V2 Voice Platform. You can now see if a call is answered by a person or was sent to Voicemail.

This enhancement to your Voice API experience will allow for better use of automated call routing. It will also be helpful as your teams design workflows and processes that are directly impacted by who’s answering the phone.

Please contact your sales account manager to contract for Answering Machine Detection.

What’s happening? The Full Phone Number Details report now includes the associated Campaign ID. Customers can use this information to validate that their 10DLC numbers are properly associated with their registered campaigns.

What do I need to do? You don’t need to take any action. The report is available for use.

Short Code (SC) SMS messages destined to US Cellular are now split out into multiple single-segment messages.

Multi-segmented SC SMS messages to US Cellular are now being split up into multiple single-segment messages, resulting in customers receiving multiple Delivery Receipts (DLR).

Prior to this fix, multi-segment messages to US Cellular were failing due to a limitation in their handling User Data Headers (UDH). This fix means that multiple single-segment messages will have their own DLR.

Customers will receive multiple DLRs unless suppression is implemented.

We are here to help! Drop us a line on our support site.

Voice API customers now the ability to use SIP clients directly with our Voice API platform. Customers can provision domains and user credentials to be used with their SIP clients so they can be called using a SIP URI like [email protected]. Customers can now have 10 active registrations for a specific user that can make or receive calls. Contact your sales account manager if you are interested in learning more about this feature.

Bandwidth has released the ability for V2 MMS customers to specify a “filename” when sending script file media. The “filename” can be specified in the standard Content-Disposition header of a V2 MMS message.

• E.164 Formatted TN
• Formatted TN
• Country
• Line Type (e.g. wireless vs. wireline)
• Line Provider (e.g. AT&T)
• Mobile Country Code (if applicable)
• Mobile Network Code (if applicable)

We are excited to be launching v3 of our WebRTC platform. This update includes:

• Upgrades to our media server infrastructure which will provide improved video and audio quality
• Improved scaling performance
• Transition to the WebRTC Unified Plan SDP format which will provide better support for Firefox and avoid the impact of Chrome’s removal of support for the deprecated Plan B format.

We’ve made it very easy to bring your WebRTC browser side application up to date: all you need to do is update your browser side SDK to the latest version (0.9.x) by August 1st, 2021.

This SDK maintains compatibility with the recent versions of the browser SDK, so none of your JavaScript code needs to be changed. We will be following up with a more detailed email notice to contracted customers.

• A slight change to the way that you log into the Bandwidth App. First you will enter your username, then another field will appear to enter your password.
• API user credentials will no longer be able to access the Bandwidth App via a web browser and will only be able to authenticate via the API. Read our support article.

We’ve added new fields to our Message Search feature! You can now find ‘Message-Size’, ‘Attachment-Count’, ‘Recipient-Count’ and ‘Message-Length’ in your Message Search API.

Message Expiration is also live! This API parameter gives you the ability to specify the date  after which a message shouldn’t be sent, thus improving the time-relevance for sent messages.

• Speedier delivery of your most important messages
• More control of the order of messages in your queue
• The ability to categorize messages based on priority

We’ve simplified an existing endpoint, and reduced the elements of the VoiceHostGroup from 5 to 1. This brings the API in line with what the UI supports. Check out the API docs for more info, specifically the /accounts /{accountId} /sites /{siteId} /sippeers section, for more information.

Our information security engineers are focused on keeping your account safe and secure. We’ve updated our password management policies to include the following security enhancements:

• Admins can unlock user accounts for those who have been locked out
• The password reset link will now expire after 24 hours from when it was sent
• The new user email confirmation will expire after 24 hours from when it was sent
• We’ve increased the complexity of the password from minimum of 8 to minimum of 12 characters
• The password expiration time was reduced to 90 days (this does not impact API users)

With this enhancement you can now manage your Emergency Services Notifications using the 911 Access Dashboard APIs.

To use this feature you’ll need to be contracted/enabled for the Notification service. If you’d like to use this feature and are not contracted for it please reach out to your Account Manager.

We’ve updated our user management emails to provide you with a fully self-service experience to create and manage user credentials. These emails will clearly guide you through the proper actions to take in order to log into the Bandwidth App & reset your password as-needed.

You can now make voice calls to endpoints by specifying a SIP URI address.

For example you can now make calls to endpoints as follows: The destination to call (must be an E.164 formatted number (e.g. +15555551212) or a SIP URI (e.g. sip:[email protected]).

To use this feature you’ll need to be contracted/enabled for the CALL-TO-SIPURI SKU. If you’d like to use this feature and are not contracted for it please reach out to your Account Manager.

• Asynchronous execution
• Detailed GET order status and information
• Detailed GET order history

We’ve updated the Applications page to now support the ability to send messaging events to separate endpoints. One for inbound messages and another for status (outbound) messages.

With this update you can:

• Configure separate callback URLs for inbound messages and status (outbound) callback events
• Set status (outbound) callback as optional
• Select which status (outbound) callback events you receive

Existing applications will continue to work as they currently do. If you’d like to take advantage of these Messaging Callback configuration options, visit the Applications page in the Bandwidth App to update.