Previous Android releases

Bria for Android 6.20.1 (May 22, 2025)

Resolved issues

This version contains improvements to the overall stability and performance of Bria and miscellaneous bug fixes.

Bria for Android 6.19.4 (April 24, 2025)

Resolved issues

  • Fixed issues with dark mode on Samsung S25 devices running Android 15.

Bria for Android 6.19.3 (March 13, 2025)

Resolved issues

  • Fixed an issue where the app was still using the Bluetooth device for audio even after the Bluetooth permission was declined by the user.

Bria for Android 6.19.1 (February 13, 2025)

Resolved issues

  • Fixed a Bluetooth issue where no audio came through Bluetooth headsets if a smart watch was connected to the Android phone.

  • Fixed a Bluetooth issue with Samsung devices running Android 14 or newer where users could not hear audio through Bluetooth headsets after switching headsets during an active call.

  • Fixed an issue with Android 15 devices where a contact avatar cannot be set due to the placement of the buttons on the screen.

Bria for Android 6.18.3 (January 16, 2025)

Starting this app version, a new permission needs to be added during the app review with Google Play. It's FOREGROUND_SERVICE_TYPE_CAMERA. See Branding Portal Guide for details.

Resolved issues

  • Fixed the issue with the Missed Call toast which now displays the caller's name.

Bria for Android 6.18.2 (November 21, 2024)

Resolved issues

  • Corrected the Do Not Disturb warning message; now it states you won't receive calls and messages.

  • Added improvements on message sync handling upon network changes.

Bria for Android 6.18.1 (October 24, 2024)

Android 15 support

Bria version 6.18.1 includes Android 15 support.

Resolved issues

  • Includes a fix for the issue where Bria receives incoming calls even after completely logging out of Bria. Please contact us if you continue experiencing this issue.

  • Adjusted the size of the visual feedback which is a colored circle appearing for a second after a number on dialpad is tapped.

Bria for Android 6.17.3 (September 26, 2024)

Call recording improvements

Multiple improvements have been made for call recording.

  • Deleting a call history entry. Previously, when you deleted an entry from Call History, the associated recording file was also deleted from your device. Starting this version, it is your choice. The app displays two options: Delete and Delete with recording. The recording can be accessed using the Recordings page within the Bria app, or connecting an USB cable to the device.

    "Delete" is on the long-press menu.

  • The recording file name includes a time stamp of when the recording was started as well as the remote party name.

  • Recording notifications. By default, the app plays a tone to the remote party when recording starts and resumes. You can change it to play an Announcement from Settings > Preferences > Call Recording > Call Recording Notification. When the announcement is chosen, the remote party hears "This call is being recorded".

  • Preferences for auto delete recordings. You can set rules for the app to automatically delete the recordings on your device:

    • Short recordings. You can specify how many seconds.

    • Old recordings. You can specify how many days old.

Resolved issues

This version contains improvements to the overall stability and performance of Bria and miscellaneous bug fixes.

Bria for Android 6.17.1 (August 15, 2024)

Busy tone support

When a call is dialed and the number is busy, Android users hear a busy tone along with a pop-up displaying 486 busy here.

Google Play Service detection

For better troubleshooting, Bria now checks if Google Play Services is enabled and up-to-date on an Android device.

Resolved issues

This version contains improvements to the overall stability and performance of Bria and miscellaneous bug fixes.

Bria for Android 6.16.4 (July 18, 2024)

Native Integration preference on new install

We have changed the default value for the Native Integration preference. Previously off by default, but with version 6.16.4, it's on by default for new and clean install. Upgrading to this app version does not change the existing end user's preference.

Resolved issues

  • Fixed an issue with Android 15 devices where received messages were invisible in the dark mode due to conflicting color combinations.

Bria for Android 6.16.2 (June 20, 2024)

Call forwarding party

If your SIP server supports and sends a call forwarding party ID to the app, the app now shows the forwarding party in the incoming call screen, the active call screen and the call historythe incoming call screen and the active call screen. For example, the following incoming call screen displays the Via line indicating who is transferring the call.

Resolved issues

  • Fixed an issue where a user could not log in to the app because the phone permission was not granted. The app now explicitly asks for the permission where needed.

  • Fixed an issue with an attended call transfer where the call screen did not update to show the original caller to the person receiving the transferred call. For example, A called B. B called C, then transferred the call with A to C. With this fix, C now sees the call is established with A.

Bria for Android 6.16.1 (May 23, 2024)

Resolved issues

  • Fixed an issue on a device with the Auto start on boot setting enabled. After the app restarts, tapping the "starting" notification opens the app and brings it to the foreground.

Bria for Android 6.15.3 (April 18, 2024)

Microphone issue resolved

The known issue since Bria 6.14 has been resolved with Version 6.15.3. This issue was reported on Android 14 where the microphone was not released for Bria's incoming calls when other apps were already using it. Let us know if you still experience this issue after upgrading to Version 6.15.3.

Resolved issues

  • Includes the localization of the permissions prompts at startup.

  • Resolved an issue with xiaomi devices where a user was stuck on the battery permission page after upgrading from 6.14 to 6.15.

Bria for Android 6.15.2 (March 14, 2024)

App permissions at installation

The app permission requests during installation have been streamlined. During install, Bria asks for a permission that's critical. Other non-critical permissions will be requested later as needed.

Resolved issues

  • Adjusted the font color of messages and hyper links in dark mode.

Known issues since version 6.14

Multiple users on Android 14 have reported that the microphone is not released for Bria's incoming calls when other apps are already using it. If you are in this situation, toggle the Speaker icon on Bria's in-call screen to enable and disable the audio. We are working on finding a better way to handle the foreground services permission.

Bria for Android 6.15.1 (February 15, 2024)

Resolved issues

This version contains improvements to the overall stability and performance of Bria and miscellaneous bug fixes.

Known issues in version 6.14

Multiple users on Android 14 have reported that the microphone is not released for Bria's incoming calls when other apps are already using it. If you are in this situation, toggle the Speaker icon on Bria's in-call screen to enable and disable the audio. We are working on finding a better way to handle the foreground services permission.

Bria for Android 6.14.3 (January 18, 2024)

Resolved issues

  • Fixed an issue with clearing call notifications. Users now can answer an incoming call in the background after a call was answered elsewhere.

  • Added missing French translations.

Known issues in version 6.14.1 and 6.14.2

Multiple users have reported that the microphone is not released for Bria's incoming calls when other apps are already using it. If you are in this situation, toggle the Speaker icon on Bria's in-call screen to enable and disable the audio. We are working on finding a better way to handle the foreground services permission.

Bria for Android 6.14.2 (December 7, 2023)

Dropping Android 9 support

Bria version 6.14.2 drops Android 9 support. Any devices using Android 9 or older will not be able to upgrade to this version.

Resolved issues

  • Fixed an issue where onscreen keyboard covered the fields when the user was trying to edit the End User Portal web page within the app.

Bria for Android 6.14.1 (November 9, 2023)

Android 14 support

Bria version 6.14.1 includes Android 14 support. However, we are aware of an issue on Android 14 where some icons in notifications bar are not displayed correctly; for example, the call-in-progress icon appears to notify a missed call. We are working on fixing this issue in the next version.

Contact images on notifications

The notification for an ongoing call and a missed call now displays a contact image instead of the default avatar image.

Resolved issues

This version contains improvements to the overall stability and performance of Bria and miscellaneous bug fixes.

Bria for Android 6.13.4 (October 12, 2023)

Resolved issues

  • Fixed an issue on Android 14 Beta where placing the second outgoing call failed.

  • Fixed an issue where a non-numeric SIP URI wasn't placed properly.

Bria for Android 6.13.3 (September 14, 2023)

Resolved issues

This version contains improvements to the overall stability and performance of Bria and miscellaneous bug fixes.

Bria for Android 6.13.2 (August 17, 2023)

Resolved issues

  • The dialer view and quick start view have been adjusted to fit large fonts.

  • The app now has the cancel button for sending troubleshooting logs.

Bria for Android 6.13.1 (July 20, 2023)

Quick access buttons and conversation history

On the Contacts tab, the contact detail page now has quick access buttons as well as conversation history.

  • Quick access buttons include placing a call, messaging, and viewing a call history with this specific contact.

  • The conversation history shows a call history with this specific contact. This section is view only.

Labels for the navigation tabs

Another improvement you will see is labels being added to the navigation tabs at the bottom of the screen.

Resolved issues

This version contains improvements to the overall stability and performance of Bria and miscellaneous bug fixes.

Bria for Android 6.12.2 (June 21, 2023)

Resolved issues

  • Fixed an issue where a badge disappeared after a file or image was received via messaging.

Bria for Android 6.12.1 (May 26, 2023)

OpenSSL 3.0 Support

The Bria app uses OpenSSL 3.0. Ensure your service provider supports secure renegotiation as per RFC 5746. Support for RFC 5746 secure renegotiation is now required by default for SSL or TLS connections to succeed.

Resolved issues

  • Fixed an issue where a Message Waiting Indicator was not counted for the Launcher icon badge.

  • Fixed an issue where call forwarding was not working if a call came in when Bria was in the background.

Bria for Android 6.11.4 (April 27, 2023)

Resolved issues

Bria for Android 6.11.2 (March 30, 2023)

Resolved issues

  • Fixed an issue where the ringtone for an incoming call could not be muted by pressing the device button.

  • Fixed an issue where the user was unable to send a file using Android 13.

Bria for Android 6.11.1 (February 16, 2023)

Dropping Android 8 Support

This app version drops Android 8 support; it does not install on Android 8 devices.

New Contacts and Call History buttons during a call

When you are in a call and want to place a second call or transfer the current call, it is now easier to access your Contacts and Call History. Note the new icons added to the bottom of the pop-up.

Change in handling concurrent calls

We made a small change with how Bria handles multiple calls so that Bria behaves in the same way as Native Dialer.

Previously when Bria has two ongoing calls and one of the calls ended, the remaining call automatically becomes unheld (or active in other words) so that the user starts hearing the call as soon as another call ended. Now, the remaining call stays on hold until the end user explicitly takes the call off hold.

Resolved known issue in Bria Android 6.10.2

Some users have reported that when a Galaxy watch is paired with a Samsung device running Android 13, they experience choppy audio with Bria. The solution to this issue is to apply an OS update on the Android 13 device.

Resolved issues

  • Corrected a VoiceOver prompt for the Select Outgoing Account button.

Bria for Android 6.10.3 (January 19, 2023)

Resolved issues

  • Fixed an issue where Bria on Samsung Galaxy Tab A8 stopped working.

  • Other stability improvements and fixes.

Known issue in Bria Android 6.10.2

Some users have reported that when a Galaxy watch is paired with a Samsung device running Android 13, they experience choppy audio with Bria. The solution to this issue is to apply an OS update on the Android 13 device.

Bria for Android 6.10.2 (December 1, 2022)

Resolved issues

  • Fixed an issue on the in-call screen where the Contacts button beside the caller's display name did not appear even though the contact was saved in the local / native contacts list. This issue was observed for outgoing calls. Now the Contacts button appears on both incoming and outgoing calls as long as the contact exists in the native contacts list with the matching softphone number.

  • Fixed an issue where long-tapping on history record stopped Bria from working.

  • Fixed an issue on UI where the account status message did not appear when network was disabled on the device.

  • Multiple stability fixes.

Bria for Android 6.10.1 (November 4, 2022)

Android 13 Support

Bria app version 6.10.1 includes Android 13 support.

Updates: Picture-in-picture on Android 13

With this app version, picture-in-picture is enabled again on Android 13 devices. Bria now shows the correct image when the device is in the portrait mode; however, you will not see picture-in-picture in landscape after navigating away from the call screen. Use a call head instead to go back to the Bria call screen.

Resolved issues

This version contains improvements to the overall stability and performance of Bria and miscellaneous bug fixes.

Bria for Android 6.9.3 (September 29, 2022)

New Recordings page via the History tab

Bria now has a new page listing all the call recording files stored on your device. Previously in order to listen to a recording, you needed to scroll down the call history to find the entry. Some users found it hard or impossible to locate one if the call history has many entries. To open the Recordings page, go to the History tab, tap More Options > Recordings, then you will see a list of recordings.

Resolved issues

  • Fixed an issue on tablet where it was unable to enter a room name when creating a new chatroom.

Bria for Android 6.9.2 (August 25, 2022)

Resolved issues

  • Fixed an issue where the Share Anonymous Usage Data option chosen by the user on fresh install was not honored.

  • Fixed an issue where an incoming call via Bria Push was terminated after ringing.

  • Fixed an issue with SIP registration errors reported by our beta user on the beta version of Bria 6.9.2.

Bria for Android 6.9.1 (July 27, 2022)

Resolved issues

  • Fixed an issue where users could not type a message after opening the message tab from a locked screen. The compose field showed a message "Keyguard is enabled, no typing allowed".

Bria for Android 6.8.3 (June 23, 2022)

Resolved issues

  • Fixed an issue with devices on ColorOS/OxygenOS, such as OnePlus and OPPO Find X3 Pro, where screen flickers during a call. (Ticket # 61715/63187/63554/65280/65891/66819)

Bria for Android 6.8.2 (May 26, 2022)

Resolved issues

  • Fixed an issue with installation where a Bluetooth permission dialog appeared and prevented a user from moving to the next screen.
  • Fixed an issue where Bria had a problem with accepting an encrypted incoming call.

Bria for Android 6.8.1 (April 28, 2022)

Resolved issues

  • Fixed an issue with a ring group "Call Completed Elsewhere" feature where Bria displayed a call as a missed call even though the call was completed elsewhere.

Bria for Android 6.7.3 (March 25, 2022)

Battery optimization improvement on Android 12

A customer reported high battery consumption even with Bria Push enabled. This version includes changes aiming to solve this issue on Android 12. Contact Customer Support if you still experience an issue.

UI changes

This version includes minor UI changes to align with Desktop and iOS apps.

  • The menu to start Collaboration calls has been changed from Conference Call to Meeting. The functionality stays the same.

  • The Android app now presents the call forwarding indicator in the same way as the iOS app.

Resolved issues

  • Fixed an issue where a password was visible in ADB logcat.

Bria for Android 6.7.2 (February 25, 2022)

Auto Answer Timer

You can configure Bria to wait before automatically answering incoming calls. Go to Preferences > Auto Answer After. By default, auto answer is disabled and the timer is set to 3 seconds.

Resolved issues

This version contains improvements to the overall stability and performance of Bria and miscellaneous bug fixes.

Bria for Android 6.7.1 (January 27, 2022)

Changes in system requirements

Dropped Android 6 and 7 support. This version of Bria runs on Android 8+ devices.

Dark mode support for Android 10+

Bria supports dark mode on Android 10+ devices. Open Bria and go to Preferences, scroll down to the bottom, and use Display Theme to change between light, dark, and System default.

Resolved issues

  • The SIP Proxy setting for Bria Push is visible again under the SIP account section.

Bria for Android 6.6.3 (December 16, 2021)

Improvements and changes

  • Improved permission handling on Android 11+. The app now asks for the microphone permission when needed even after a user taps Deny more than once. This improvement helps users who accidentally denied the microphone permission without realizing it is required for a phone call.

  • The Collaboration Management User Portal page now appears right under the Menu icon instead of under the Settings page for quicker access.

Resolved issues

This version contains improvements to the overall stability and performance of Bria and miscellaneous bug fixes.

Bria for Android 6.6.2 (November 18, 2021)

New features

  • Android 12 support

Resolved issues

  • Fixed an issue where a login password was logged as plain text in one of the log files. Now the login password is masked with * (an asterisk).

Bria for Android 6.6.1 (October 14, 2021)

New menu for Settings and Logging out

This version introduces the new Menu at the top left corner, so the user's Presence, Settings, Log Out, and Exit options can be accessed from anywhere in the app.

Resolved issues

  • Fixed an issue where a chromebook user could not place a call.

Bria for Android 6.5.4 (August 26, 2021)

Resolved issues

  • Dialing someone from Favorites now uses a dial plan if dial plan is configured.

  • Resolved an issue where Bria failed to show a notification for a message which arrived while the recipient was offline.

  • Resolved an issue where the preference Default Account for History was not honored.

Bria for Android 6.5.3 (July 29, 2021)

Resolved issues

  • Microphone does work now even when the Bria app is in the background.

  • The notification for an incoming call is now accessible even when the device is locked.

  • Calls can now be made using Bria on Chromebooks with Chrome OS that emulates Android OS 10 or higher.

Bria for Android 6.5.2 (June 29, 2021)

Changes in Telecom Framework Integration

In Preferences, the Use Native Dialer option has been removed under Telecom Framework native integration. SIP calls will be made using Bria rather than native dialer.

Resolved issues

  • A fix for an issue where contact suggestions are not visible on the dialpad while typing. This issue is observed when moving back to the dialer tab from other tabs on Bria version 6.5.1.

  • A fix for a broken link in file transfer.

  • A fix for the voicemail count icon disappearing after declining an incoming call.

  • Adjusted the size of the green Call button on dialpad.

Bria for Android 6.5.1 (June 1, 2021)

Improvements

  • Favorite sorting: Favorites are sorted alphabetically instead of by date added.

  • Chat Room improvement: The chat room threads are now automatically refreshed when opened so that users do not need to manually refresh it. With this change, notifications for unread messages are synced among devices. If you have multiple devices and read a message in a Chat Room on one device, notifications on the rest of your devices will be removed.

  • On the Login screen, the Keep Password option has been changed to Remember Login which now controls both login username and password. This change aligns the behavior between desktop and mobile clients.

Resolved issues

  • Voicemail: voicemail notifications will now update after the first login.

  • Permissions: the app no longer asks for the External Storage permission when accessing the Photo Gallery, sending files, and taking an avatar photo.

  • File Transfer: PDF and MP4 files will now open when sent via File Transfer.

  • Collaboration meeting: When a user joins a meeting on Chromebooks, their avatar will now appear in the participant list.

  • UI: Increased font size for the banner "Your video is not sent".

Bria for Android 6.4.3 (April 26, 2021)

New features and Changes

  • Permissions: Changes required by Google for storage access permissions on Android 11.

  • New preference - Show account name on heads-up notification

    This helps you identify which SIP account is receiving the incoming call.

    • Ability for the Host to change conference resolution during session.

    • Ability to detect the user's app language and play the audio greetings in the same language.

Resolved issues

This version contains improvements to the overall stability and performance of Bria and miscellaneous bug fixes.

Bria for Android 6.4.2 (March 15, 2021)

New features

Added a new option to Android phones to join a conference with your Speaker muted. To enable this option, go to Bria > Settings > Conferences and enable Mute Speaker When Joining.

Resolved issues

There have been improvements to the overall stability and performance of Bria, such as:

  • a change for the font color of links in the Instant Messages, to be more visible against the background color.
  • a fix for the Collaboration feature where multiple websocket connections were observed when the device had no internet connection.

If you continue to encounter a resolved issue, or if you have a new issue, please report it to the CounterPath Support Center.

Bria for Android 6.4.1 (February 8, 2021)

  • A bigger text area for writing a message. Note the expand icon to make it even bigger.

  • Typing indicator when someone is typing into a chat room or 1:1 message thread.

  • Easier navigation for unread messages: when a user taps the Messaging panel, Bria displays the tab with the unread messages.

  • The Buddies list on the Contacts tab now is called Roster.

When starting this version of Bria, it asks for anonymous usage data collection. Bria collects usage data in order to improve the quality and performance of CounterPath products. None of the information being collected is personally identifiable. To opt-out, you can select Decline at the startup, or go to Settings > Advanced Settings, and turn off Share Anonymous Usage Data.

Added a new option to join a conference with your microphone muted. To enable this option, go to Bria > Settings > Conferences and enable Mute Mic When Joining.

Added a new option for 480P, which uses 848 x 480 pixels.

  • A new preference for incoming call notifications: you can display the phone number / SIP username along with the display name. Off by default. Enable the Show Number in Notification setting under Preferences to show the number.

  • Added a pop-up for a microphone permission to remind end users that Bria needs to access their microphone for making and receiving calls. This aims to solve the issue where end users deny the permission by selecting Deny and don't ask again.

  • Diagnostics logs size has been increased.

This version contains improvements to the overall stability and performance of Bria and miscellaneous bug fixes.

Please report any issues to the CounterPath Support Center.

If you see a dialog asking to give Bria permission to record a call, answer Yes even if you do not intend to record calls. This dialog is actually asking for permission to access your microphone for making calls, not necessarily for recording. Calls will be recorded if you manually start recording during a call, or if you enable Settings > Preferences > Auto Record Calls.

There are known issues in Android OS regarding Bluetooth audio support for third party applications such as Client. The list of open issues is available at Open Source Project - Issue Tracker.

Users of Xiaomi and Huawei devices with EMUI or MIUI firmware are unable to answer incoming calls using heads-up notifications. Heads-up notifications are disabled for all Xiaomi and Huawei devices with EMUI and MIUI stock ROM.

When using a Samsung EDGE device with the Edge Lighting feature enabled, notifications do not show the Answer and Decline buttons – users have to open the notification to answer the call. Disable Preferences > Use heads-up notification for incoming calls.

On some Android phones, the remote party on a Bria call experiences a decrease in audio volume when there is an incoming native Android call. This is caused by the Android OS reducing outgoing call volume.

If the remote party tries to add video to an audio call on your Team Voice account, the call is dropped. If the caller tries to add video to an audio call, the call remains as an audio call. In order to use video, place the call as a video call.

On devices running Android 8 Oreo and above, there is a known Android issue where users can only select a text tone and not a ring tone for incoming calls using notification channels. To provide support for users without the ability to assign a ring tone, Bria uses a custom ringtone for incoming calls. For users that do have access to ring tones in notification channels, you can still change the ringtone for incoming Bria calls.

This is a known issue for some devices running Android 6 (Marshmallow) or lower where the screen remains off when receiving a call. Double tap the screen to wake the phone and answer the call.

Some users on Android 7.0 may encounter difficulty opening Bria from the tray notification. In this case, please use the launcher icon to access the app.

Bria for Android 6.3.4 (November 20, 2020)

  • A new setting has been added to disable the shush gesture. Flip to silence ringer can be found under Preferences > Incoming Call.

  • Mute when face down improvements - two scenarios are supported: 1) a native incoming call answered via heads-up notification, 2) a call merged into a local conference.
  • Removed the CIF option (352x288) from Video resolution preferences. With this change, the lowest option available is VGA.
  • On the Messaging tab, the People section has been changed back to the IM section.

There have been improvements to the overall stability and performance of Bria, such as:

  • a fix for a call-in-progress notification that persists even after the call ended

  • a fix for an error in Traditional Chinese localization.

If you continue to encounter a resolved issue, or if you have a new issue, please report it to the CounterPath Support Center.

If you see a dialog asking to give Bria permission to record a call, answer Yes even if you do not intend to record calls. This dialog is actually asking for permission to access your microphone for making calls, not necessarily for recording. Calls will be recorded if you manually start recording during a call, or if you enable Settings > Preferences > Auto Record Calls.

There are known issues in Android OS regarding Bluetooth audio support for third party applications such as Client. The list of open issues is available at Open Source Project - Issue Tracker.

Users of Xiaomi and Huawei devices with EMUI or MIUI firmware are unable to answer incoming calls using heads-up notifications. Heads-up notifications are disabled for all Xiaomi and Huawei devices with EMUI and MIUI stock ROM.

When using a Samsung EDGE device with the Edge Lighting feature enabled, notifications do not show the Answer and Decline buttons – users have to open the notification to answer the call. Disable Preferences > Use heads-up notification for incoming calls.

On some Android phones, the remote party on a Bria call experiences a decrease in audio volume when there is an incoming native Android call. This is caused by the Android OS reducing outgoing call volume.

If the remote party tries to add video to an audio call on your Team Voice account, the call is dropped. If the caller tries to add video to an audio call, the call remains as an audio call. In order to use video, place the call as a video call.

On devices running Android 8 Oreo and above, there is a known Android issue where users can only select a text tone and not a ring tone for incoming calls using notification channels. To provide support for users without the ability to assign a ring tone, Bria uses a custom ringtone for incoming calls. For users that do have access to ring tones in notification channels, you can still change the ringtone for incoming Bria calls.

This is a known issue for some devices running Android 6 (Marshmallow) or lower where the screen remains off when receiving a call. Double tap the screen to wake the phone and answer the call.

Some users on Android 7.0 may encounter difficulty opening Bria from the tray notification. In this case, please use the launcher icon to access the app.

Bria for Android 6.3.2 (October 8, 2020)

  • PiP (Picture in picture) support on Android 11
  • Mute when face down improvements - playing audio announcement when the device is placed face down.
  • When creating a contact from Call Log, the phone number type is now set to Main (instead of Softphone). This change aligns the behavior of Bria iOS and Android.
  • Bria Push Improvements in handling push subscriptions between Bria and the Bria Push server when the app is in the Continuous mode.

There have been improvements to the overall stability and performance of Bria, such as:

  • a fix for an issue where sending log fails for a new domain

  • a fix for file transfer file picker not showing the full storage on the device.

If you continue to encounter a resolved issue, or if you have a new issue, please report it to the CounterPath Support Center.

If you see a dialog asking to give Bria permission to record a call, answer Yes even if you do not intend to record calls. This dialog is actually asking for permission to access your microphone for making calls, not necessarily for recording. Calls will be recorded if you manually start recording during a call, or if you enable Settings > Preferences > Auto Record Calls.

There are known issues in Android OS regarding Bluetooth audio support for third party applications such as Client. The list of open issues is available at Open Source Project - Issue Tracker.

Users of Xiaomi and Huawei devices with EMUI or MIUI firmware are unable to answer incoming calls using heads-up notifications. Heads-up notifications are disabled for all Xiaomi and Huawei devices with EMUI and MIUI stock ROM.

When using a Samsung EDGE device with the Edge Lighting feature enabled, notifications do not show the Answer and Decline buttons – users have to open the notification to answer the call. Disable Preferences > Use heads-up notification for incoming calls.

On some Android phones, the remote party on a Bria call experiences a decrease in audio volume when there is an incoming native Android call. This is caused by the Android OS reducing outgoing call volume.

If the remote party tries to add video to an audio call on your Team Voice account, the call is dropped. If the caller tries to add video to an audio call, the call remains as an audio call. In order to use video, place the call as a video call.

On devices running Android 8 Oreo and above, there is a known Android issue where users can only select a text tone and not a ring tone for incoming calls using notification channels. To provide support for users without the ability to assign a ring tone, Bria uses a custom ringtone for incoming calls. For users that do have access to ring tones in notification channels, you can still change the ringtone for incoming Bria calls.

This is a known issue for some devices running Android 6 (Marshmallow) or lower where the screen remains off when receiving a call. Double tap the screen to wake the phone and answer the call.

Some users on Android 7.0 may encounter difficulty opening Bria from the tray notification. In this case, please use the launcher icon to access the app.

Bria for Android 6.3.1 (September 8, 2020)

New languages have been added: Traditional Chinese and Polish.

Bria now has the ability to change your ringtone for incoming calls. Go to Preferences > Incoming Call > Ringtone.

A new setting to use the native dialer UI for dialing out SIP calls. Under Preferences > Telecom Framework > Use Native Dialer. A reminder that native integration requires Android 8.0+, and not supported on Chromebooks.

The + symbol is now allowed in the Softphone field in contacts, which aligns with the behavior of Bria on Desktop.

  • When a user makes a call from the History tab, Bria previously used either the SIP account that received the call as a dial out account, or the default account if the preference Default Account for History was enabled. What is new here is that if the SIP account that received the call has been deleted by the time a user decided to call back from the history, Bria uses the default account regardless of Default Account for History. This was introduced to due a customer report.

  • Settings have been reorganized and aligned between Bria iOS and Android clients. Under Preferences, and Advanced Settings.

This version contains improvements to the overall stability and performance of Bria and miscellaneous bug fixes.

Please report any issues to the CounterPath Support Center.

If you see a dialog asking to give Bria permission to record a call, answer Yes even if you do not intend to record calls. This dialog is actually asking for permission to access your microphone for making calls, not necessarily for recording. Calls will be recorded if you manually start recording during a call, or if you enable Settings > Preferences > Auto Record Calls.

There are known issues in Android OS regarding Bluetooth audio support for third party applications such as Client. The list of open issues is available at Open Source Project - Issue Tracker.

Users of Xiaomi and Huawei devices with EMUI or MIUI firmware are unable to answer incoming calls using heads-up notifications. Heads-up notifications are disabled for all Xiaomi and Huawei devices with EMUI and MIUI stock ROM.

When using a Samsung EDGE device with the Edge Lighting feature enabled, notifications do not show the Answer and Decline buttons – users have to open the notification to answer the call. Disable Preferences > Use heads-up notification for incoming calls.

On some Android phones, the remote party on a Bria call experiences a decrease in audio volume when there is an incoming native Android call. This is caused by the Android OS reducing outgoing call volume.

If the remote party tries to add video to an audio call on your Team Voice account, the call is dropped. If the caller tries to add video to an audio call, the call remains as an audio call. In order to use video, place the call as a video call.

On devices running Android 8 Oreo and above, there is a known Android issue where users can only select a text tone and not a ring tone for incoming calls using notification channels. To provide support for users without the ability to assign a ring tone, Bria uses a custom ringtone for incoming calls. For users that do have access to ring tones in notification channels, you can still change the ringtone for incoming Bria calls.

This is a known issue for some devices running Android 6 (Marshmallow) or lower where the screen remains off when receiving a call. Double tap the screen to wake the phone and answer the call.

Some users on Android 7.0 may encounter difficulty opening Bria from the tray notification. In this case, please use the launcher icon to access the app.

Bria for Android 6.2.3 (July 22, 2020)

Contact search

Previously Bria found contact names by searching only the first word in the First Name and Last Name fields. Now Bria searches all the words in these fields, which should bring up more contacts that weren't found in the previous versions.

There have been improvements to the overall stability and performance of Bria, such as:

  • A fix for a call history issue

  • A fix for a 1:1 messages synchronization issue

If you continue to encounter a resolved issue, or if you have a new issue, please report it to the CounterPath Support Center.

If you see a dialog asking to give Bria permission to record a call, answer Yes even if you do not intend to record calls. This dialog is actually asking for permission to access your microphone for making calls, not necessarily for recording. Calls will be recorded if you manually start recording during a call, or if you enable Settings > Preferences > Auto Record Calls.

There are known issues in Android OS regarding Bluetooth audio support for third party applications such as Client. The list of open issues is available at Open Source Project - Issue Tracker.

Users of Xiaomi and Huawei devices with EMUI or MIUI firmware are unable to answer incoming calls using heads-up notifications. Heads-up notifications are disabled for all Xiaomi and Huawei devices with EMUI and MIUI stock ROM.

When using a Samsung EDGE device with the Edge Lighting feature enabled, notifications do not show the Answer and Decline buttons – users have to open the notification to answer the call. Disable Preferences > Use heads-up notification for incoming calls.

On some Android phones, the remote party on a Bria call experiences a decrease in audio volume when there is an incoming native Android call. This is caused by the Android OS reducing outgoing call volume.

If the remote party tries to add video to an audio call on your Team Voice account, the call is dropped. If the caller tries to add video to an audio call, the call remains as an audio call. In order to use video, place the call as a video call.

On devices running Android 8 Oreo and above, there is a known Android issue where users can only select a text tone and not a ring tone for incoming calls using notification channels. To provide support for users without the ability to assign a ring tone, Bria uses a custom ringtone for incoming calls. For users that do have access to ring tones in notification channels, you can still change the ringtone for incoming Bria calls.

This is a known issue for some devices running Android 6 (Marshmallow) or lower where the screen remains off when receiving a call. Double tap the screen to wake the phone and answer the call.

Some users on Android 7.0 may encounter difficulty opening Bria from the tray notification. In this case, please use the launcher icon to access the app.

Bria for Android 6.2.2 (June 30, 2020)

A new preference has been added to automatically mute your voice when the device is placed face down during a call (audio, video, and Collaboration meeting). Go to Bria's Settings > Preferences > Mute when face down.

This version includes various improvements on Telecom Framework integration. Please upgrade to this version if you are using this feature, and give us feedback. As a reminder:

  • This feature is not supported in Chromebooks, and requires Android 8.0+.
  • This feature is off by default. To turn this on, go to Settings > Preferences > Native Integration.

There have been improvements to the overall stability and performance of Bria, such as:

  • A fix for the audio routing issue where Bria only uses speaker and not the internal microphone after a Bluetooth headset is disconnected.

  • A fix for a call termination when R Instance is enabled
  • A fix for push registration handling for the Single Device Emulation mode

If you continue to encounter a resolved issue, or if you have a new issue, please report it to the CounterPath Support Center.

If you see a dialog asking to give Bria permission to record a call, answer Yes even if you do not intend to record calls. This dialog is actually asking for permission to access your microphone for making calls, not necessarily for recording. Calls will be recorded if you manually start recording during a call, or if you enable Settings > Preferences > Auto Record Calls.

There are known issues in Android OS regarding Bluetooth audio support for third party applications such as Client. The list of open issues is available at Open Source Project - Issue Tracker.

Users of Xiaomi and Huawei devices with EMUI or MIUI firmware are unable to answer incoming calls using heads-up notifications. Heads-up notifications are disabled for all Xiaomi and Huawei devices with EMUI and MIUI stock ROM.

When using a Samsung EDGE device with the Edge Lighting feature enabled, notifications do not show the Answer and Decline buttons – users have to open the notification to answer the call. Disable Preferences > Use heads-up notification for incoming calls.

On some Android phones, the remote party on a Bria call experiences a decrease in audio volume when there is an incoming native Android call. This is caused by the Android OS reducing outgoing call volume.

If the remote party tries to add video to an audio call on your Team Voice account, the call is dropped. If the caller tries to add video to an audio call, the call remains as an audio call. In order to use video, place the call as a video call.

On devices running Android 8 Oreo and above, there is a known Android issue where users can only select a text tone and not a ring tone for incoming calls using notification channels. To provide support for users without the ability to assign a ring tone, Bria uses a custom ringtone for incoming calls. For users that do have access to ring tones in notification channels, you can still change the ringtone for incoming Bria calls.

This is a known issue for some devices running Android 6 (Marshmallow) or lower where the screen remains off when receiving a call. Double tap the screen to wake the phone and answer the call.

Some users on Android 7.0 may encounter difficulty opening Bria from the tray notification. In this case, please use the launcher icon to access the app.

Bria for Android 6.2.1 (May 28, 2020)

  • Dropped support for Android Lollipop (5.x). Bria now requires Android 6.0+.

Bria now supports Telecom Framework Integration which allows you to:

  • Answer or decline an incoming call by pressing the button on a Bluetooth device, or by talking (if supported by Bluetooth devices).

  • End a call by pressing the button on a Bluetooth device.

    Note that if you mute using a Bluetooth device, the call gets muted but the Bria screen shows unmute. This is a limitation by Android OS.

  • Receive and answer a Bria incoming call while you already have a native call.

    When Native Integration is disabled, an incoming call to Bria receives a busy tone because you already have an ongoing native call.

This feature is not supported in Chromebooks, and requires Android 8.0+.

This feature is off by default. To turn this on, go to Settings > Preferences > Native Integration.

You can now configure call forwarding per SIP account as well as globally on all SIP accounts on Bria. When both are enabled, the global call forwarding takes effect.

  • The per-account settings are under Settings > Account (SIP) > Call Forwarding.
  • The global settings are under Settings > Preferences.

Bria has a new preference for dialing from History if multiple SIP accounts are configured. You can use either the default (primary) account or the account that received the call.

Change the preference from Settings > Preferences > Default Account for History.

There have been improvements to the overall stability and performance of Bria, such as:

  • The Enable PRACK setting now can be applied via provisioning refresh. Previously changing this setting required to restart the client in order to take effect.
  • Previously dial plans were applied only to the calls made using the dialpads. This version includes a fix so it also applies to the numbers saved in your Contacts or Call Logs.

If you continue to encounter a resolved issue, or if you have a new issue, please report it to the CounterPath Support Center.

If you see a dialog asking to give Bria permission to record a call, answer Yes even if you do not intend to record calls. This dialog is actually asking for permission to access your microphone for making calls, not necessarily for recording. Calls will be recorded if you manually start recording during a call, or if you enable Settings > Preferences > Auto Record Calls.

There are known issues in Android OS regarding Bluetooth audio support for third party applications such as Client. The list of open issues is available at Open Source Project - Issue Tracker.

Users of Xiaomi and Huawei devices with EMUI or MIUI firmware are unable to answer incoming calls using heads-up notifications. Heads-up notifications are disabled for all Xiaomi and Huawei devices with EMUI and MIUI stock ROM.

When using a Samsung EDGE device with the Edge Lighting feature enabled, notifications do not show the Answer and Decline buttons – users have to open the notification to answer the call. Disable Preferences > Use heads-up notification for incoming calls.

On some Android phones, the remote party on a Bria call experiences a decrease in audio volume when there is an incoming native Android call. This is caused by the Android OS reducing outgoing call volume.

If the remote party tries to add video to an audio call on your Team Voice account, the call is dropped. If the caller tries to add video to an audio call, the call remains as an audio call. In order to use video, place the call as a video call.

On devices running Android 8 Oreo and above, there is a known Android issue where users can only select a text tone and not a ring tone for incoming calls using notification channels. To provide support for users without the ability to assign a ring tone, Bria uses a custom ringtone for incoming calls. For users that do have access to ring tones in notification channels, you can still change the ringtone for incoming Bria calls.

This is a known issue for some devices running Android 6 (Marshmallow) or lower where the screen remains off when receiving a call. Double tap the screen to wake the phone and answer the call.

Some users on Android 7.0 may encounter difficulty opening Bria from the tray notification. In this case, please use the launcher icon to access the app.

Bria for Android 6.1.1 (February 3, 2020)

The display name field now allows the plus (+) character.

There have been improvements to the overall stability and performance of Bria, such as:

  • The LDAP query search pattern has been aligned with the Desktop clients.
  • An error occurred while joining a collab session. This has been resolved.

If you continue to encounter a resolved issue, or if you have a new issue, please report it to the CounterPath Support Center.

If you see a dialog asking to give Bria permission to record a call, answer Yes even if you do not intend to record calls. This dialog is actually asking for permission to access your microphone for making calls, not necessarily for recording. Calls will be recorded if you manually start recording during a call, or if you enable Settings > Preferences > Auto Record Calls.

There are known issues in Android OS regarding Bluetooth audio support for third party applications such as Client. The list of open issues is available at Open Source Project - Issue Tracker.

Users of Xiaomi and Huawei devices with EMUI or MIUI firmware are unable to answer incoming calls using heads-up notifications. Heads-up notifications are disabled for all Xiaomi and Huawei devices with EMUI and MIUI stock ROM.

When using a Samsung EDGE device with the Edge Lighting feature enabled, notifications do not show the Answer and Decline buttons – users have to open the notification to answer the call. Disable Preferences > Use heads-up notification for incoming calls.

On some Android phones, the remote party on a Bria call experiences a decrease in audio volume when there is an incoming native Android call. This is caused by the Android OS reducing outgoing call volume.

If the remote party tries to add video to an audio call on your Team Voice account, the call is dropped. If the caller tries to add video to an audio call, the call remains as an audio call. In order to use video, place the call as a video call.

On devices running Android 8 Oreo and above, there is a known Android issue where users can only select a text tone and not a ring tone for incoming calls using notification channels. To provide support for users without the ability to assign a ring tone, Bria uses a custom ringtone for incoming calls. For users that do have access to ring tones in notification channels, you can still change the ringtone for incoming Bria calls.

This is a known issue for some devices running Android 6 (Marshmallow) or lower where the screen remains off when receiving a call. Double tap the screen to wake the phone and answer the call.

Some users on Android 7.0 may encounter difficulty opening Bria from the tray notification. In this case, please use the launcher icon to access the app.

Bria for Android 6.0.2 (November 9, 2019)

With Call History Sync, when a user enables their SIP account on multiple devices, the user sees a consistent call log history on all of their devices. For example, a user answers a call on a Windows computer, then sees on an iPhone that the call was answered on another device.

For more information, see Call History Sync.

With this feature, Bria blocks incoming calls with:

  • No number,
  • Anonymous Caller ID, and/or
  • Any number or SIP address you added to the block list.

You can block up to 10 phone numbers/SIP addresses in Bria. This block list is stored locally on your device; if you have Bria installed on multiple devices, you need to set this feature manually on each device.

For more information, see Enabling Call Blocking.

With this feature, Bria automatically answers an incoming call as soon as the call comes in.

Client-side auto answer can be enabled from Preferences > Auto Answer Calls.

Bria now allows you to add a description of an issue when you send a log to CounterPath Support.

  • Push improvements
  • Improvements in handling of device ID for Android 10

This version contains improvements to the overall stability and performance of Bria and miscellaneous bug fixes.

Please report any issues to the CounterPath Support Center.

If you see a dialog asking to give Bria permission to record a call, answer Yes even if you do not intend to record calls. This dialog is actually asking for permission to access your microphone for making calls, not necessarily for recording. Calls will be recorded if you manually start recording during a call, or if you enable Settings > Preferences > Auto Record Calls.

There are known issues in Android OS regarding Bluetooth audio support for third party applications such as Client. The list of open issues is available at Open Source Project - Issue Tracker.

Users of Xiaomi and Huawei devices with EMUI or MIUI firmware are unable to answer incoming calls using heads-up notifications. Heads-up notifications are disabled for all Xiaomi and Huawei devices with EMUI and MIUI stock ROM.

When using a Samsung EDGE device with the Edge Lighting feature enabled, notifications do not show the Answer and Decline buttons – users have to open the notification to answer the call. Disable Preferences > Use heads-up notification for incoming calls.

On some Android phones, the remote party on a Bria call experiences a decrease in audio volume when there is an incoming native Android call. This is caused by the Android OS reducing outgoing call volume.

If the remote party tries to add video to an audio call on your Team Voice account, the call is dropped. If the caller tries to add video to an audio call, the call remains as an audio call. In order to use video, place the call as a video call.

On devices running Android 8 Oreo and above, there is a known Android issue where users can only select a text tone and not a ring tone for incoming calls using notification channels. To provide support for users without the ability to assign a ring tone, Bria uses a custom ringtone for incoming calls. For users that do have access to ring tones in notification channels, you can still change the ringtone for incoming Bria calls.

This is a known issue for some devices running Android 6 (Marshmallow) or lower where the screen remains off when receiving a call. Double tap the screen to wake the phone and answer the call.

Some users on Android 7.0 may encounter difficulty opening Bria from the tray notification. In this case, please use the launcher icon to access the app.

Bria for Android 5.7.2 (Sept 18, 2019)

The Low Latency Mode setting has been added to Advanced Settings – Advanced Media Options. The new setting appears when Use AudioTrack is enabled. This setting is enabled by default for devices running Android 8 or lower.

While lower latency is desirable, enabling this setting on newer devices running Android 9 or higher may cause audio to be distorted or missing. On devices running Android 9, this setting is disabled by default.

There have been improvements to the overall stability and performance of Bria, such as:

Some users running Android 10 may have had an issue where there was no incoming call screen when Bria was running in the background. This issue has been fixed in this release.

If the Display over other apps setting is disabled and the device is locked, the user needs to double tap on the incoming call notification to show the incoming call screen.

This release contains improvements to the Bria Push Service.

If you continue to encounter a resolved issue, or if you have a new issue, please report it to the CounterPath Support Center.

If you see a dialog asking to give Bria permission to record a call, answer Yes even if you do not intend to record calls. This dialog is actually asking for permission to access your microphone for making calls, not necessarily for recording. Calls will be recorded if you manually start recording during a call, or if you enable Settings > Preferences > Auto Record Calls.

There are known issues in Android OS regarding Bluetooth audio support for third party applications such as Client. The list of open issues is available at Open Source Project - Issue Tracker.

Users of Xiaomi and Huawei devices with EMUI or MIUI firmware are unable to answer incoming calls using heads-up notifications. Heads-up notifications are disabled for all Xiaomi and Huawei devices with EMUI and MIUI stock ROM.

When using a Samsung EDGE device with the Edge Lighting feature enabled, notifications do not show the Answer and Decline buttons – users have to open the notification to answer the call. Disable Preferences > Use heads-up notification for incoming calls.

On some Android phones, the remote party on a Bria call experiences a decrease in audio volume when there is an incoming native Android call. This is caused by the Android OS reducing outgoing call volume.

If the remote party tries to add video to an audio call on your Team Voice account, the call is dropped. If the caller tries to add video to an audio call, the call remains as an audio call. In order to use video, place the call as a video call.

On devices running Android 8 Oreo and above, there is a known Android issue where users can only select a text tone and not a ring tone for incoming calls using notification channels. To provide support for users without the ability to assign a ring tone, Bria uses a custom ringtone for incoming calls. For users that do have access to ring tones in notification channels, you can still change the ringtone for incoming Bria calls.

This is a known issue for some devices running Android 6 (Marshmallow) or lower where the screen remains off when receiving a call. Double tap the screen to wake the phone and answer the call.

Some users on Android 7.0 may encounter difficulty opening Bria from the tray notification. In this case, please use the launcher icon to access the app.

Bria for Android 5.6.2 (July 18, 2019)

The Match Contacts for Caller-ID setting was added to Preferences – Incoming call.

If you want Bria to try to match incoming calls to your Contacts and use the Display Name for the caller ID, select this setting. If Bria finds a matching contact, the contact's Display Name is used. If there is no match, Bria uses the information in the SIP header.

If you would prefer to see the SIP information on the caller ID, clear this setting.

There have been improvements to the overall stability and performance of Bria, such as:

This version of Bria contains numerous registration improvements.

Improvements have been made for incoming call notifications. Clearing your notification drawer no longer rejects incoming calls. A new setting has been added for incoming call notifications for WearOS users. You can enable WearOS notifications in Preferences – Notifications. With this setting enabled, clearing the notification does reject the call.

Some users experienced one-way audio on some devices running Android 9. This has been fixed in this version.

If you continue to encounter a resolved issue, or if you have a new issue, please report it to the CounterPath Support Center.

If you see a dialog asking to give Bria permission to record a call, answer Yes even if you do not intend to record calls. This dialog is actually asking for permission to access your microphone for making calls, not necessarily for recording. Calls will be recorded if you manually start recording during a call, or if you enable Settings > Preferences > Auto Record Calls.

There are known issues in Android OS regarding Bluetooth audio support for third party applications such as Client. The list of open issues is available at Open Source Project - Issue Tracker.

Users of Xiaomi and Huawei devices with EMUI or MIUI firmware are unable to answer incoming calls using heads-up notifications. Heads-up notifications are disabled for all Xiaomi and Huawei devices with EMUI and MIUI stock ROM.

When using a Samsung EDGE device with the Edge Lighting feature enabled, notifications do not show the Answer and Decline buttons – users have to open the notification to answer the call. Disable Preferences > Use heads-up notification for incoming calls.

On some Android phones, the remote party on a Bria call experiences a decrease in audio volume when there is an incoming native Android call. This is caused by the Android OS reducing outgoing call volume.

If the remote party tries to add video to an audio call on your Team Voice account, the call is dropped. If the caller tries to add video to an audio call, the call remains as an audio call. In order to use video, place the call as a video call.

On devices running Android 8 Oreo and above, there is a known Android issue where users can only select a text tone and not a ring tone for incoming calls using notification channels. To provide support for users without the ability to assign a ring tone, Bria uses a custom ringtone for incoming calls. For users that do have access to ring tones in notification channels, you can still change the ringtone for incoming Bria calls.

This is a known issue for some devices running Android 6 (Marshmallow) or lower where the screen remains off when receiving a call. Double tap the screen to wake the phone and answer the call.

Some users on Android 7.0 may encounter difficulty opening Bria from the tray notification. In this case, please use the launcher icon to access the app.

Bria for Android 5.6.1 (June 4, 2019)

Bria now has 64-bit support which improves performance on 64-bit Android devices.

In the past, if your XMPP account was not registered, you could not see your XMPP Buddy information. Now, roster information is available. You cannot send users an IM and their presence shows as unknown when your XMPP account is not registered, but you can access their contact information, and, if your SIP account is registered, you can attempt to phone your Buddies.

This release contains a number of improvements for chat rooms. Some of these improvements are:

  • Any member of a public chat room can invite new members.
  • The Room Owner of a private chat room can remove participants.
  • Chat rooms can be searched by Description.
  • In the Rooms list, Bria displays the last message viewed instead of the date you joined or created the room.
  • Notifications show the name of the chat room as well as the name of the person who sent the message.

Disable Call Waiting, Turn Letters to Numbers, and Hide My Number have been added. You can enable these features in Settings > Preferences. For more information, see Disabling call waiting, Changing letters to number, and Hiding your identity in the User Guide.

Collaboration is no longer part of the Insider Program and has been added to the Bria Pro subscription. The ability to add your G-Suite account remains part of the Insider Program.

This version contains improvements to the overall stability and performance of Bria and miscellaneous bug fixes.

Please report any issues to the CounterPath Support Center.

If you see a dialog asking to give Bria permission to record a call, answer Yes even if you do not intend to record calls. This dialog is actually asking for permission to access your microphone for making calls, not necessarily for recording. Calls will be recorded if you manually start recording during a call, or if you enable Settings > Preferences > Auto Record Calls.

There are known issues in Android OS regarding Bluetooth audio support for third party applications such as Client. The list of open issues is available at Open Source Project - Issue Tracker.

Users of Xiaomi and Huawei devices with EMUI or MIUI firmware are unable to answer incoming calls using heads-up notifications. Heads-up notifications are disabled for all Xiaomi and Huawei devices with EMUI and MIUI stock ROM.

If the remote party tries to add video to an audio call on your Team Voice account, the call is dropped. If the caller tries to add video to an audio call, the call remains as an audio call. In order to use video, place the call as a video call.

On devices running Android 8 Oreo and above, there is a known Android issue where users can only select a text tone and not a ring tone for incoming calls using notification channels. To provide support for users without the ability to assign a ring tone, Bria uses a custom ringtone for incoming calls. For users that do have access to ring tones in notification channels, you can still change the ringtone for incoming Bria calls.

This is a known issue for some devices running Android 6 (Marshmallow) or lower where the screen remains off when receiving a call. Double tap the screen to wake the phone and answer the call.

Some users on Android 7.0 may encounter difficulty opening Bria from the tray notification. In this case, please use the launcher icon to access the app.

Bria for Android 5.5.4 (April 4, 2019)

When trying to log in to Bria, some Chromebooks did not recognize there was an Internet connection when Ethernet was being used. Bria now detects Ethernet connections on Chromebooks.

This release contains usability improvements for Collaboration. You must have a Bria Pro subscription in order to use Collaboration.

There have been improvements to the overall stability and performance of Bria, such as:

Some users may have experienced one-way audio on Bria calls after upgrading to Android 9 Pie. This issue has been fixed in this release.

If you continue to encounter a resolved issue, or if you have a new issue, please report it to the CounterPath Support Center.

If you see a dialog asking to give Bria permission to record a call, answer Yes even if you do not intend to record calls. This dialog is actually asking for permission to access your microphone for making calls, not necessarily for recording. Calls will be recorded if you manually start recording during a call, or if you enable Settings > Preferences > Auto Record Calls.

There are known issues in Android OS regarding Bluetooth audio support for third party applications such as Client. The list of open issues is available at Open Source Project - Issue Tracker.

Users of Xiaomi and Huawei devices with EMUI or MIUI firmware are unable to answer incoming calls using heads-up notifications. Heads-up notifications are disabled for all Xiaomi and Huawei devices with EMUI and MIUI stock ROM.

If the remote party tries to add video to an audio call on your Team Voice account, the call is dropped. If the caller tries to add video to an audio call, the call remains as an audio call. In order to use video, place the call as a video call.

On devices running Android 8 Oreo and above, there is a known Android issue where users can only select a text tone and not a ring tone for incoming calls using notification channels. To provide support for users without the ability to assign a ring tone, Bria uses a custom ringtone for incoming calls. For users that do have access to ring tones in notification channels, you can still change the ringtone for incoming Bria calls.

This is a known issue for some devices running Android 6 (Marshmallow) or lower where the screen remains off when receiving a call. Double tap the screen to wake the phone and answer the call.

Some users on Android 7.0 may encounter difficulty opening Bria from the tray notification. In this case, please use the launcher icon to access the app.

Bria for Android 5.5.3 (February 21, 2019)

Bria now supports permanent chat rooms. Chat rooms can be private or public. Private rooms can only be joined by invitation. Public rooms can be joined by anyone in your Team Messaging group.

  • All the clients must be running version 5.5.3 or higher on iOS and Android and version 5.5.0 or higher on Windows and Mac.
  • Your Team Messaging account must be registered and enabled.

If some clients are running versions earlier than 5.5.3 on iOS and Android or 5.5.0 on Windows and Mac, the room members list may not accurately show who is in the chat rooms and messages may not be sent to all room members.

Previous group chat sessions are no longer available on version 5.5.3 or higher on iOS and Android and .

See Working with messages for information on copying messages.

History now has filters to sort calls into All and Missed. If you have Collaboration enabled by your team's administrator, you are also able to filter by Conferences.

The filters are displayed in "History".

There have been improvements to the Bria Push Service. In previous versions of Bria, your SIP account remained on the Bria Push server when Use Push Notifications was disabled. Disabling this setting now deletes your SIP account from the Bria Push server.

This version contains improvements to the overall stability and performance of Bria and miscellaneous bug fixes.

Please report any issues to the CounterPath Support Center.

If you see a dialog asking to give Bria permission to record a call, answer Yes even if you do not intend to record calls. This dialog is actually asking for permission to access your microphone for making calls, not necessarily for recording. Calls will be recorded if you manually start recording during a call, or if you enable Settings > Preferences > Auto Record Calls.

There are known issues in Android OS regarding Bluetooth audio support for third party applications such as Client. The list of open issues is available at Open Source Project - Issue Tracker.

Users of Xiaomi and Huawei devices with EMUI or MIUI firmware are unable to answer incoming calls using heads-up notifications. Heads-up notifications are disabled for all Xiaomi and Huawei devices with EMUI and MIUI stock ROM.

If the remote party tries to add video to an audio call on your Team Voice account, the call is dropped. If the caller tries to add video to an audio call, the call remains as an audio call. In order to use video, place the call as a video call.

On devices running Android 8 Oreo and above, there is a known Android issue where users can only select a text tone and not a ring tone for incoming calls using notification channels. To provide support for users without the ability to assign a ring tone, Bria uses a custom ringtone for incoming calls. For users that do have access to ring tones in notification channels, you can still change the ringtone for incoming Bria calls.

This is a known issue for some devices running Android 6 (Marshmallow) or lower where the screen remains off when receiving a call. Double tap the screen to wake the phone and answer the call.

Some users on Android 7.0 may encounter difficulty opening Bria from the tray notification. In this case, please use the launcher icon to access the app.

Bria for Android 5.5.2 (December 20, 2018)

Bria now has two additional Registration Modes – Continuous and Single Device Takeover. Single Device Takeover is now the default Registration Mode for new SIP accounts.

Continuous: Your VoIP service provider supports multiple registrations. The Bria Push server is always connected to the SIP server. Bria is only connected to the SIP server when Bria is in the foreground. When Bria is in the foreground, Bria ignores push notifications so that you do not receive duplicates.

Single Device Takeover: Your VoIP service provider does not support multiple registrations. This setting allows Bria and the Bria Push server to take over registration from each other without having to unregister first.

Use the Test Push Service button when your additional SIP account is enabled and registered. If the test is successful, your device is able to communicate with the Bria Push server and your device is able to receive push notifications from Google's FCM push notification system.

Bria uses Android notification channels on devices running Android 8 (Oreo) and higher. There is a known issue on some devices where users can only select a text tone and not a ring tone for incoming calls using notification channels. We have implemented a new distinct ringtone for incoming Bria calls that will replace your current sound in this version.

For devices that have the ability to select ringtones, you can still switch to a different ringtone in notification channels if you prefer.

If you switch to a text tone in notification channels on devices that do not support ringtones but want to restore the new distinct Bria ringtone, you need to reinstall the app.

For Xiaomi MIUI 10 devices, you may need to Enable Sound in the native Android OS settings.

For devices running Android 8 (Oreo) or higher, Bria now supports picture-in-picture (PIP). To use PIP on an active video call, put Bria in the background. The video remains in a thumbnail. Reposition the thumbnail by dragging it around on the screen. Close the thumbnail by tapping X.

The video thumbnail displays above the background when using picture-in-picture.

This version on Bria has improvements to the call History logs.

The PROCESS_OUTGOING_CALLS permission has been removed from Bria.

When a user denied the Contacts Permission for Bria and selected Never ask again, users still received a message in the Dialer to access the device contacts. Now when a user selects Never ask again, the dialer no longer displays the Contact Permission message or the Request Permission button. In order to allow Bria to access the device contacts after selecting Never ask again, the user must use Android's app permissions.

This version contains improvements to the overall stability and performance of Bria and miscellaneous bug fixes.

Please report any issues to the CounterPath Support Center.

If you see a dialog asking to give Bria permission to record a call, answer Yes even if you do not intend to record calls. This dialog is actually asking for permission to access your microphone for making calls, not necessarily for recording. Calls will be recorded if you manually start recording during a call, or if you enable Settings > Preferences > Auto Record Calls.

There are known issues in Android OS regarding Bluetooth audio support for third party applications such as Client. The list of open issues is available at Open Source Project - Issue Tracker.

Users of Xiaomi and Huawei devices with EMUI or MIUI firmware are unable to answer incoming calls using heads-up notifications. Heads-up notifications are disabled for all Xiaomi and Huawei devices with EMUI and MIUI stock ROM.

If the remote party tries to add video to an audio call on your Team Voice account, the call is dropped. If the caller tries to add video to an audio call, the call remains as an audio call. In order to use video, place the call as a video call.

On devices running Android 8 Oreo and above, there is a known Android issue where users can only select a text tone and not a ring tone for incoming calls using notification channels. To provide support for users without the ability to assign a ring tone, Bria uses a custom ringtone for incoming calls. For users that do have access to ring tones in notification channels, you can still change the ringtone for incoming Bria calls.

This is a known issue for some devices running Android 6 (Marshmallow) or lower where the screen remains off when receiving a call. Double tap the screen to wake the phone and answer the call.

Some users on Android 7.0 may encounter difficulty opening Bria from the tray notification. In this case, please use the launcher icon to access the app.

Bria for Android 5.4.3 (October 17, 2018)

Some users may have noticed an issue where the name being displayed inside a conversation did not match the name of the person the conversation was with. This has been fixed in this issue.

This version of Bria contains improvements to the Bria Push Service.

There have been improvements to the overall stability and performance of Bria, such as:

This release fixes the unattended or blind transfer issue on Team Voice accounts where the party being transferred remained on hold rather than being transferred to the target.

If you continue to encounter a resolved issue, or if you have a new issue, please report it to the CounterPath Support Center.

If you see a dialog asking to give Bria permission to record a call, answer Yes even if you do not intend to record calls. This dialog is actually asking for permission to access your microphone for making calls, not necessarily for recording. Calls will be recorded if you manually start recording during a call, or if you enable Settings > Preferences > Auto Record Calls.

There are known issues in Android OS regarding Bluetooth audio support for third party applications such as Client. The list of open issues is available at Open Source Project - Issue Tracker.

Users of Xiaomi and Huawei devices with EMUI or MIUI firmware are unable to answer incoming calls using heads-up notifications. Heads-up notifications are disabled for all Xiaomi and Huawei devices with EMUI and MIUI stock ROM.

If the remote party tries to add video to an audio call on your Team Voice account, the call is dropped. If the caller tries to add video to an audio call, the call remains as an audio call. In order to use video, place the call as a video call.

On devices running OS 8 Oreo and above, there is a known issue where users can only select a text tone and not a ring tone for incoming calls using Notification Channels. This is a known issue on Android OS. The list of open issues is available at Android Open Source Project – Issue Tracker.

This is a known issue for some devices running Android 6 (Marshmallow) or lower where the screen remains off when receiving a call. Double tap the screen to wake the phone and answer the call.

Some users on Android 7.0 may encounter difficulty opening Bria from the tray notification. In this case, please use the launcher icon to access the app.

Bria for Android 5.4.1 (September 25, 2018)

Setting up accounts is done via Bria Teams Portal.

Bria Teams includes Team Voice and Team Messaging accounts. With Team Voice, you can make voice and video calls to other members of your team. With Team Messaging, you can share your presence and send IMs to other members of your team. If your administrator has configured an additional SIP account, you can use that account to make voice and video calls outside of your team.

If you see a dialog asking to give Bria permission to record a call, answer Yes even if you do not intend to record calls. This dialog is actually asking for permission to access your microphone for making calls, not necessarily for recording. Calls will be recorded if you manually start recording during a call, or if you enable Settings > Preferences > Auto Record Calls.

There are known issues in Android OS regarding Bluetooth audio support for third party applications such as Client. The list of open issues is available at Open Source Project - Issue Tracker.

Users of Xiaomi and Huawei devices with EMUI or MIUI firmware are unable to answer incoming calls using heads-up notifications. Heads-up notifications are disabled for all Xiaomi and Huawei devices with EMUI and MIUI stock ROM.

If the remote party tries to add video to an audio call on your Team Voice account, the call is dropped. If the caller tries to add video to an audio call, the call remains as an audio call. In order to use video, place the call as a video call.

When you try to make an unattended or blind transfer using your Team Voice account, the call does not come off of hold after the transfer. Instead, use an attended transfer where you call the target before making the transfer.

On devices running OS 8 Oreo and above, there is a known issue where users can only select a text tone and not a ring tone for incoming calls using Notification Channels. This is a known issue on Android OS. The list of open issues is available at Android Open Source Project – Issue Tracker.

This is a known issue for some devices running Android 6 (Marshmallow) or lower where the screen remains off when receiving a call. Double tap the screen to wake the phone and answer the call.

Some users on Android 7.0 may encounter difficulty opening Bria from the tray notification. In this case, please use the launcher icon to access the app.