Previous Desktop releases

Bria for Windows and Mac 6.7.3 (January 9, 2025)

Updating to Bria 6.7.3 on Windows

Before you update Bria to version 6.7.3, make sure to close the Messages window. If the Messages window is open during the update, you will see a crash report dialog. If this happens to you, ignore the crash and continue updating to 6.7.3. Bria 6.7.3 will install successfully.

Support for macOS 15 and Windows 11 2H2024

This app version officially supports macOS 15 and Windows 11 version 24H2. With this change, macOS 12 (Monterey) is no longer officially supported.

XMPP Messaging Improvements

  • Read Receipt: In instant messages, the check mark appears when the other person received your message. Hover over the check mark to see the time the message was received.

  • New Emoticon Library: You can search by a keyword, and choose a skin tone to personalize emoticons. New emoticons are available in both instant messages and chatrooms.

Call recording improvements

Multiple improvements have been made for call recording.

  • Auto Record Calls. A new preference has been added to record all calls automatically and have the audio file saved on your computer. Go to Preferences > Advanced to see the settings.

  • Call Recording Warning pop-up. The app displays a pop-up reminding you to follow the laws in your jurisdiction for recording calls. It appears right after login. Your accounts will not register until you click Yes.

  • 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 or Delete All Recording.

  • 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. You can change it to play an Announcement from Softphone > Preferences > Advanced > 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.

USB headsets integration improvement

We've redone how the app integrates with Leitner, Logitech, and other USB headsets that use Generic Human Interface Devices (HID) interface. This improvement aims to provide more reliable and real-time integration between Bria and USB headsets. The same headsets are officially supported with this improvement which mitigates existing issues where USB headsets get unresponsive or out of sync.

Reverting to the older app version after the 6.7.3 update

Because of the XMPP messaging improvements in the version 6.7.3, an extra step of renaming a hidden folder is required if you need to revert the Bria desktop app to the older version, for example from 6.7.3 to 6.7.2.

  1. Uninstall Bria 6.7.3.

    1. Open the file explorer and click More > Options.

    2. Go to the View tab.

    3. Under Hidden files and folders, select Show hidden files, folders, and drives.

    4. Click Apply and close the dialog.

  3. On Mac, open Finder. While holding down the Option key, click Go at the top menu. Click Library.

  4. Rename the following folder to any name of your choice, for example Not Used Bria.

    On Windows:

    C:\Users\<<Windows-Username>>\AppData\Roaming\CounterPath Corporation\Bria

    On Mac:

    /Users/<<macOS-username>>/library/Application Support/CounterPath Corporation/Bria

    The following image shows an example of the Bria folder on Windows.

  5. Install and start Bria 6.7.2.

Resolved issues

  • Fixed an issue where an incoming call could not be answered using the Poly Voyager Focus UC headsets.

  • Fixed an issue where Bria did not update the display name after the call was transferred to another party.

Bria for Windows and Mac 6.7.2 (June 26, 2024)

Headsets integration improvements for EPOS and Leitner

This version contains many improvements to make EPOS and Leitner headsets work better with Bria.

  • Leitner: New support for Leitner LH470, LH570, LH670. Button controls on the headset work with Bria for volume control, mute, start call, end call, and hold functions.

  • EPOS: Starting this version, users no longer need to install software from EPOS on their desktop computer. For a list of supported headsets, visit our Support Center.

Simultaneous ringing on both headset and speaker

If you want to hear an incoming call ringtone on headset and speaker at the same time, go to Preferences > Devices > Other Devices, and under Ring on: choose Headset and Speaker.

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 and the active call screen. For example, the following incoming call screen displays the Via line indicating who is transferring the call.

Outlook contact improvements

Previously when Outlook contacts were added to Bria using Accounts Settings, Outlook contacts in subfolders did not sync with Bria. With this version, Outlook contacts in subfolders are added to Bria as a flat list, without the subfolders.

Resolved issues

  • Fixed an issue on Windows where placing a call using drag and drop onto the dialer did not start the call right away.

Bria for Windows and Mac 6.7.1 (January 25, 2024)

Changes to system requirements

  • Windows 11, version 23H2 support added. This version of Bria complies with Windows 11 Smart App Control.

  • macOS 14 support added. macOS 11 is no longer supported.

Improvements for Jabra headsets integration

This version contains several changes to make Jabra headsets work better with Bria.

Resolved issues

  • Fixed an issue where the Windows shortcut keys for answering and ending a call could not be customized.

  • Fixed an issue where test music for speakers kept playing after the user closed the page without explicitly clicking the Stop button.

  • Added some changes to solve issues with the Google Contact sync. Contact us if you encounter issues.

  • Contains library updates, including OpenSSL version 3.1.

Bria 6.6.3.1 (October 27, 2023)

  • Renewed client certificate for Desktop API. All customers leveraging the desktop API should update to this latest version as soon as possible due to an expired client certificate error.

  • macOS 14 (Sonoma) video support. The official macOS 14 support is coming soon.

  • DNS failover improvements

Bria 6.6.3 (August 24, 2023)

Yealink headsets support

As part of this release, we have tested and certified the latest Yealink headset devices. End users need to allow Yealink USB Connect to access Bria. For the instructions and the detailed list of Yealink headset compatibility, please refer to the Yealink website here.

Resolved issues

  • Fixed an issue with creating a contact using the right-click menu on the History tab. The contact name the user entered is now displayed properly.

  • Fixed an issue with contact search when the device's language is set to Russian. The search is now performed case-insensitive.

Bria for Windows and Mac 6.6.2 (May 29, 2023)

System requirements

This version includes macOS 13 (Ventura) support.

Resolved issues

  • Fixed a few issues with macOS 13 (Ventura).

  • Fixed an issue on Mac where previous messages did not appear in the right pane.

Bria for Windows and Mac 6.5.5.2 (November 10, 2022)

Resolved issues

  • Fixed a crash which affected many Windows users. If you are experiencing a crash, upgrade to Bria 6.5.5.2 to see if it solves the issue.

    This crash was observed on the following OS with the recent Windows Update.

    • Windows 10 (version 22H2) with KB5018410

    • Windows 11 with KB5017271

    Windows 10 version 21H2 does not experience this issue.

  • Fixed an issue with Jabra headsets where headsets kept ringing after a call was answered.

Bria for Windows and Mac 6.5.5 (September 22, 2022)

New features and improvements

  • Jabra headsets integration: Jabra device handling in Bria has been completely reworked to ensure Bria works properly with most Jabra headsets.

  • Click-to-dial with an extension: Use the tel protocol to set up a hyperlink for click-to-dial with an extension. For example, the code <a href="tel:+16045553727;ext=1">dial +1-604-555-3727 Extension 1</a> instructs Bria to call the number, pause, then call the extension.

  • This version also includes updates to various third party libraries.

Resolved issues

  • Fixed an issue where Jabra Evolve 30 headset sends a hangup message to Briawithout the user pressing the button. (Ticket # 56599)

  • Fixed an issue where the Call History list on Bria does not roll over to a new calendar day if left running overnight. (Ticket # 67095)

  • Fixed an issue on Windows where the Stretto login server recognizes as a separate device when a Windows 10 computer connects with and without docking station. (Ticket # 67212)

Bria for Windows and Mac 6.5.4 (June 24, 2022)

Improvements

  • Language selection at start up - Previously Bria required an exact match of "language+locale", but it now uses the closet one if no exact match is found. For example, if the OS language is German - Switzerland (de-ch), Bria now chooses German where the older version of Bria chooses English.

  • [Windows] New preference for camera rotation - This setting controls the rotation of a camera for your video feed. Under BriaPreferences > Devices > Other Devices, look for Camera Rotation, and select Normal, Flipped or None, and close and reopen the Video window to see the change.

  • Bria Desktop API certificate now includes the full chain of certificates. (Ticket # 63400)

Resolved issues

  • Fixed a login issue where Bria Windows clients did not respond after the user tried logging in.

  • Fixed an issue with camera access where Bria Windows clients did not release camera after an attempted video call. (Ticket # 66363)

  • Fixed an issue where Bria Windows clients reported an incorrect OS version to the servers.

Bria for Windows and Mac 6.5.3 (March 21, 2022)

This version includes changes to the Diagnostic log server. We recommend you upgrade to this version because the older clients require end users to manually send the Bria log to Customer Support.

Resolved issues

  • Fixed an issue on Windows with custom web panels where a second web panel did not appear by default if the second panel was added after initial login.

  • Fixed an issue on Mac where the date format for the Messages panel reverted to default after receiving or sending messages.

  • Fixed an issue on Mac with disconnecting a camera then ending a Collaboration meeting.

Bria for Windows and Mac 6.5.2 (December 21, 2021)

Improvements

  • The default value for upstream video resolution is now 480p. Users who previously selected another resolution under Preferences > Devices > Other Devices > Max Resolution will see no change until they uninstall and install the app again.

  • [Mac] Improved notification handling for the missing Microphone or Camera permission.
  • [Windows] Outlook contacts now remain displayed when internet connection is unavailable on the device.

  • Updates to the latest Jabra SDK.

Resolved issues

  • Fixed an issue on Windows where an embedded browser displays a blank page until the page is resized; pages now appear properly.

  • Fixed a screen sharing issue on Windows after a participant became a presenter to share their screen.

Known issue found in Version 6.5.2

Version 6.5.2 had the following issue which has been fixed in 6.5.3.

On Windows, there is an issue with custom web panels where a second web panel does not appear as a tab by default if it is added after provisioning the first web panel. Users can go to the Bria menu > View then click to show the second web panel manually.

Bria for Windows and Mac 6.5.1 (October 29, 2021)

Changes to system requirements

  • Added Windows 11 support.

  • Added support for macOS 12 (Monterey), and dropped support for macOS 10.14 (Mojave) and 10.15 (Catalina).

  • Microsoft .NET Framework 4.8 is now required (previously 4.6.2).

Resolved issues

  • Reduced webcam usage during video calls, so that webcam gets activated when the user chooses to send their video or enable local preview of their video.

  • [Mac] Fixed an issue with a Collaboration meeting where the user starts the screen share of an application while using an external monitor, other participants just see a blank screen. The resolved scenario is when the application being shared is maximized in full screen in the external monitor. If you encounter a similar issue, please report it to Support with a log.

  • [Windows] Fixed an issue where Bria stops working when a G-Suite account is configured in Bria.

Bria for Windows and Mac 6.4.2 (August 3, 2021)

Resolved issues

  • Previously a built-in microphone on some Windows laptop appeared in Bria's drop down list, but did not recognize sound. This issue has been resolved for several users. Affected computers include: HP EliteBook 840 G6, Lenovo Thinkpad X1 Yoga, Lenovo X1 Carbon, Lenovo ThinkPad X1 Carbon Gen8.

Bria for Windows and Mac 6.4.1 (June 7, 2021)

Change in system requirements

MacOS 10.13 (High Sierra) is no longer supported.

Resolved issues

  • Conference Video Resolution Fix: resolved an issue where the client does not always update to show the current Conference video resolution during the Conference.

  • Screen Share Fix: resolved an issue where Screen Share may disconnect due to significant packet loss or a poor network condition.

Bria for Windows and Mac 6.4.0 (May 3, 2021)

New features

  • Contacts: Ability to add a new phone number to an existing contact from History. Previously from the History panel, you only were able to create a new contact. Now you can add a new number to an exiting contact by right-clicking the number, then choose Update Existing.

  • Auto echo cancellation for headsets: See Preferences > Devices > Enable echo cancellation. This new setting controls both speakers and headsets. With this change, the Reduce echoes from speakers (AEC) setting has been removed from the Speakerphone Mode on the Devices panel.

  • DTMF: Ability to send A-D DTMF tones during a call. Now users can enter A/B/C/D DTMF tones during a call using keyboard. Must be upper case. There are no additional buttons on dialpad on Bria.

  • Screenshare improvements

    • Static screen share link: End users can use the link for recurring sessions.

    • Share application: Ability to share an application instead of an entire screen or monitor. Supported on both Windows and Mac. Make sure the application you want to share is NOT minimized to the task bar, NOT in the full screen mode, or NOT in Mission Control space (F3) on Mac.

  • Collaboration improvements

    • Resolution. Added the ability for the host to change the conference downstream resolution during a conference.

    • Screenshare. Added the ability to share an application instead of an entire screen or monitor.

    • Quality. The call quality indicator and call encryption icon now appear on the Conference window.

    • Participants. The participants list now shows yourself.

    • Language. Added the ability to detect the user's app language and set the audio greetings to the same language.

  • Desktop API improvements

    Refer to Bria Desktop API Guide for details.

    • Added API calls for signing in and out the end user as well as exiting Bria

    • Added the accountId parameter to GET /status "callHistory" and GET /status "callHistoryItem". This change makes it easier for the API users to redial based on a history item.

    • The GET /startScreenShare API call prompts for the end user to choose a window or monitor to share.

  • More improvements

    • Added logging for the Contact Import feature to capture failure information.

    • Updated Jabra SDK to 1.8.7.15

Resolved issues

  • fix for no audio during a call through AirPods (1st Generation). This issue was reported on Windows, but no issue on Mac.
  • fix for hyperlink preview which does not render pages in Simplified Chinese.

Bria for Windows and Mac 6.3.0 (December 9, 2020)

New features

  • Support for macOS 11.0 (Big Sur)

  • Video resolution changes. Added a new option for 480P, and removed the CIF option. With these changes, the lowest video resolution available is VGA. Video resolution can be changed under Softphone > Preferences > Devices > Other Devices > Max resolution.

  • Added Camera Test to the Troubleshooting menu

  • Added a preference to turn on/off device integration (such as headsets and speakers). See Preferences > Devices.

  • Previously a pop-up appeared for sending or receiving files via file transfer. Now these messages appear in the Messages window for better user experience.

  • Added additional filters for call history such as Incoming calls and Answered elsewhere. The ability to filter missed calls with a specific SIP account has been removed.

  • Desktop API - Added an API call for conference calling (locally merged)

    • The red mute pop-up appears on the Collaboration screen to indicate your microphone or speaker is muted. Click X to dismiss the pop-up.

      The mute pop-up appears below the tool bar on top of either video feed or screenshare.

    • Join options for muting speaker and/or microphone have been added in Settings > Preferences.

  • Added TLS 1.3 support and removed TLS 1.1.

  • Jabra SDK in Bria has been updated to version 1.8.7.12.

Resolved issues

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

Bria for Windows and Mac 6.2.1/6.2.2 (September 28, 2020)

HD Video screenshare

Starting this version, Bria uses HD screenshare which is video stream based.

Related changes include:

  • Screenshare links are dynamic and created at the time the end user starts the screenshare. This is for improved security and better operation. If the end user has recurring screenshare sessions, they need to invite people or send the new link each time.

  • The screen being shared displays a red bounding box around it, instead of yellow.
  • When screensharing is paused or stopped, there is no page displayed to the viewers; the last video frame is shown instead, as HD screenshare uses a video feed.
  • HD Screen share supports up to 4K video resolution. Video frame rate depends on overall bandwidth limits but can go up to 30 fps for 1080p video.

Resolved issues

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

Bria for Windows and Mac6.2.0 (September 2, 2020)

  • This version of Bria for Mac restores the support for virtual cameras such as ManyCam and ChromaCam. Changes by Apple had prevented apps from using Virtual Cameras and this issue is now resolved.

  • On Mac computers, a re-login was previously required in order to sync Bria with Mac Address Book contacts. This version requires no re-login; it syncs simultaneously in the background.
  • Jabra SDK in Bria has been updated to version 1.8.3.
  • Performance improvement for handling a large number of message threads (200 threads that contain 500 messages in each thread).
  • Improved look and feel of contacts and contact group headers.
  • A customer has noticed that after end users restarted Bria, they needed to log in again for the Web Panel page. It has been changed to maintain login in such situations.
  • Desktop API via Pipe has been deprecated for a while. This version removes it from Bria.

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

  • A fix for a call transfer issue using Jabra headsets
  • A fix for an issue with connecting Bria with Leitner headsets
  • A fix for an issue with downloading call statistics of a user with + in their email address/username.
  • A fix for an issue where SIP presence is not automatically populated when contacts are imported from LDAP directory to Bria
  • A fix for retained logins of the Web Panel page between different users on the same machine.

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

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.

Bria for Mac 6.1.2 (July 24, 2020)

TLS versions for Desktop API

Desktop API supports TLS 1.1 and 1.2 for secure web socket connections to Bria 6.1.2.

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 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 click on an IM notification, the Messages window appears. You should be able to start typing right away. If you receive multiple IMs at once, you cannot start typing until all of the IM notifications disappear. No issue has been found when receiving only one IM. This is because IM toasts take the focus away from the Messages window.

Workaround: Explicitly click the text area in the Messages window where you want to type.

Bria for Mac 6.1.1 (June 4, 2020)

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

  • Bria for Mac stopped working during a Collaboration session when a window was moved to a second monitor. This issue has been resolved.
  • On Bria for Mac, a diagnostic log was not sent when the log level was set to Debug. This issue 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 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 click on an IM notification, the Messages window appears. You should be able to start typing right away. If you receive multiple IMs at once, you cannot start typing until all of the IM notifications disappear. No issue has been found when receiving only one IM. This is because IM toasts take the focus away from the Messages window.

Workaround: Explicitly click the text area in the Messages window where you want to type.

Bria for Windows and Mac 6.1.0 (March 4, 2020)

  • To use Jabra headsets, Bria no longer requires users to download the Jabra Direct software and allow API access for Jabra Direct.
  • XMPP Messaging - now a plus character (+) can be used in an XMPP username or contact field address.

  • On Windows, the shortcut key for bringing focus to Bria has been changed from CTRL+ALT+SHIFT+F to CTRL+ALT+SHIFT+B. To use shortcut keys in Bria, go to Bria > Preferences and enable them first.

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

  • Some of the fields in a Google contact (such as home or mobile number) were not mapped correctly in Bria contacts. This issue has been resolved.
  • Broadsoft XSI directory search failed due to a connection problem in the previous version of Bria. This issue has been resolved.

  • On Mac, some users reported that they could not install an update via auto-upgrade notification. This version includes a fix for this issue.

    Note that users will still encounter this issue when upgrading from 6.0 to 6.1. Download the 6.1.0 client manually then this issue will not occur for the next upgrade to 6.1.x.

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

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 click on an IM notification, the Messages window appears. You should be able to start typing right away. If you receive multiple IMs at once, you cannot start typing until all of the IM notifications disappear. No issue has been found when receiving only one IM. This is because IM toasts take the focus away from the Messages window.

Workaround: Explicitly click the text area in the Messages window where you want to type.

Bria for Windows and Mac 6.0.3 (January 27, 2020)

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

  • For the call history sync feature, Bria was not using the consistent account names between login and sync. This issue 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 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 click on an IM notification, the Messages window appears. You should be able to start typing right away. If you receive multiple IMs at once, you cannot start typing until all of the IM notifications disappear. No issue has been found when receiving only one IM. This is because IM toasts take the focus away from the Messages window.

Workaround: Explicitly click the text area in the Messages window where you want to type.

When using a Jabra headset, Jabra users are required to install Jabra direct software in order to use core functionality. You may not be notified to run Jabra Direct when you connect your Jabra device. In order to use your Jabra headset with Bria, download Jabra Direct and allow Jabra Direct API access.

Bria for Windows and Mac 6.0.1 (November 15, 2019)

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

  • Crash on startup/login related to HTTP/Open SSL.

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

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 click on an IM notification, the Messages window appears. You should be able to start typing right away. If you receive multiple IMs at once, you cannot start typing until all of the IM notifications disappear. No issue has been found when receiving only one IM. This is because IM toasts take the focus away from the Messages window.

Workaround: Explicitly click the text area in the Messages window where you want to type.

When using a Jabra headset, Jabra users are required to install Jabra direct software in order to use core functionality. You may not be notified to run Jabra Direct when you connect your Jabra device. In order to use your Jabra headset with Bria, download Jabra Direct and allow Jabra Direct API access.

Bria for Windows and Mac 6.0.0 (November 8, 2019)

Bria are no longer tested or supported on:

  • Windows 7 SP1
  • Windows 8.1
  • macOS 10.12 (Sierra)

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.

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.

Bria now allows you to generate a packet capture and send it to CounterPath Support. Go to Help > Troubleshooting.

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.

When using a Jabra headset, Jabra users are required to install Jabra direct software in order to use core functionality. You may not be notified to run Jabra Direct when you connect your Jabra device. In order to use your Jabra headset with Bria, download Jabra Direct and allow Jabra Direct API access.

When you click on an IM notification, the Messages window appears. You should be able to start typing right away. If you receive multiple IMs at once, you cannot start typing until all of the IM notifications disappear. No issue has been found when receiving only one IM. This is because IM toasts take the focus away from the Messages window.

Workaround: Explicitly click the text area in the Messages window where you want to type.

Bria for Windows and Mac 5.7.1 (Sept 25, 2019)

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

Call controls for a number of Logitech and Sennheiser headsets connected via USB were not working in version 5.7.0. This has been fixed in version 5.7.1.

Version 5.7.1 includes a fix for the setting Pause iTunes when making or receiving calls on macOS 10.15.

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

For some users, Bria freezes after upgrading to Bria 5.7 on a Mac running macOS 10.13 (High Sierra). To resolve this issue, either:

  • Stop or restart iTunes if it is running.
  • Click Bria - Preferences in the menu bar and clear Pause iTunes when making or receiving calls in the Application panel.

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 click on an IM notification, the Messages window appears. You should be able to start typing right away. If you receive multiple IMs at once, you cannot start typing until all of the IM notifications disappear. No issue has been found when receiving only one IM. This is because IM toasts take the focus away from the Messages window.

Workaround: Explicitly click the text area in the Messages window where you want to type.

When using a Jabra headset, Jabra users are required to install Jabra direct software in order to use core functionality. You may not be notified to run Jabra Direct when you connect your Jabra device. In order to use your Jabra headset with Bria, download Jabra Direct and allow Jabra Direct API access.

Bria for Windows and Mac 5.7.0 (Sept 9, 2019)

The separate sections for Rooms and People have been removed from the Messages window. Now, the conversation list shows all IMs and chat rooms, and can be filtered to show either Rooms or People.

IMs and chat rooms appear in the conversation list with the "All" filter selected.

Create a new IM conversation or join and create rooms in one place by clicking New Conversation. You can also add people to a chat room from the new conversation window.

Type the name of a contact in "Type to add people to a conversation".

When you export Bria's call history to a .csv file, the format of the call duration field has been updated to the standard Excel time format hh:mm:ss.

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 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 click on an IM notification, the Messages window appears. You should be able to start typing right away. If you receive multiple IMs at once, you cannot start typing until all of the IM notifications disappear. No issue has been found when receiving only one IM. This is because IM toasts take the focus away from the Messages window.

Workaround: Explicitly click the text area in the Messages window where you want to type.

When using a Jabra headset, Jabra users are required to install Jabra direct software in order to use core functionality. You may not be notified to run Jabra Direct when you connect your Jabra device. In order to use your Jabra headset with Bria, download Jabra Direct and allow Jabra Direct API access.

Bria for Windows and Mac 5.6.2 (June 4, 2019)

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

Some users continued to experience call failures when using click-to-dial outside of Bria (i.e. clicking a link on a web page). Further fixes have been made 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 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.

When you click on an IM notification, the Messages window appears. You should be able to start typing right away. If you receive multiple IMs at once, you cannot start typing until all of the IM notifications disappear. No issue has been found when receiving only one IM. This is because IM toasts take the focus away from the Messages window.

Workaround: Explicitly click the text area in the Messages window where you want to type.

When using a Jabra headset, Jabra users are required to install Jabra direct software in order to use core functionality. You may not be notified to run Jabra Direct when you connect your Jabra device. In order to use your Jabra headset with Bria, download Jabra Direct and allow Jabra Direct API access.

Bria for Windows and Mac 5.6.1 (May 21, 2019)

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

When using screen share during a Collaboration meeting, Windows users may have experienced high memory usage. This has been fixed in this version.

The desktop API call GET /call returned a 400 Bad Request if no accountType was specified. This has been fixed and the accountType is now optional in the API call.

Some users experienced a crash on startup if they had a touch device – such as a touch pen – connected to their computer. This has been fixed in this version.

Some users may have experienced call failures when using click-to-dial outside of Bria (i.e. clicking a link on a web page). 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 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.

When you click on an IM notification, the Messages window appears. You should be able to start typing right away. If you receive multiple IMs at once, you cannot start typing until all of the IM notifications disappear. No issue has been found when receiving only one IM. This is because IM toasts take the focus away from the Messages window.

Workaround: Explicitly click the text area in the Messages window where you want to type.

When using a Jabra headset, Jabra users are required to install Jabra direct software in order to use core functionality. You may not be notified to run Jabra Direct when you connect your Jabra device. In order to use your Jabra headset with Bria, download Jabra Direct and allow Jabra Direct API access.

Bria for Windows and Mac 5.6.0 (May 9, 2019)

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.

A new settings has been added in Preferences > Application. If you enable Change status to away on computer lock, your presence is automatically updated to Away when you lock your computer.

New keyboard accelerators have been introduced that can be used when Bria is in focus

  • CTRL+V: Pause or resume sending video (Mac only)
  • CTRL+W: Change presence from current status to Do not disturb and from Do not disturb to the default status (Mac only)
  • CTRL + SHIFT + C: Bring the active Collaboration window into focus.
    Your administrator must subscribe to Collaboration.

The Prioritize Bria Contacts setting was added to Preferences > Calls. 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 you would prefer to see the SIP information on the caller ID, clear this setting.

A list of Allowed Applications and a list of Declined Applications is shown on the Security tab of Preferences > Applications. See which external applications have been granted API access and which have been declined. Move the applications between columns to control API access.

If you turn on Disable Call Waiting, Turn Letters to Numbers, and Hide my number, these settings now remain on after logging out or restarting Bria.

A new field – accountId – has been added to the Bria API.

A new API call has been added to request a list of accounts. The response contains the value for the new field accountId, as well as the values for accountName, type, enabled, and registered. The accountType can be sip or xmpp (case sensitive) – only the accounts of the specified account type are returned. If no accountType is specified or an incorrect accountType is specified, 400 Bad Request is returned.

Sample request
GET /status
User-Agent: MyApplication
Transaction-ID: GF8002137
Content-Type: application/xml
Content-Length: 135
<?xml version="1.0" encoding="utf-8" ?>
<status>
<type>account</type>
<accountType>xmpp</accountType>
</status>
Sample response
HTTP/1.1 200 OK
Transaction-ID: GF8002137
Content-Type: application/xml
Content-Length: 231
<?xml version="1.0" encoding="utf-8" ?>
<status type="account">
<account>
<accountName>VCCS XMPP</accountName>
<accountId>512</accountId>
<type>xmpp</type>
<enabled>true</enabled>
<registered>true</registered>
</account>
</status>

To select the account used to place a call, use the new field accountId. This field is optional in the GET/call request. If auto-select is enabled, the call uses the account specified in accountId. If the user selects a specific account for the outgoing call, the specified account takes priority.

Sample request
GET/call
User-Agent: MyApplication
Transaction-ID: GF8002137
Content-Type: application/xml
Content-Length: 135
<?xml version="1.0" encoding="utf-8" ?>
<dial type="audio">
<number>1440@zippy-voip.com</number>
<displayName>Joseph Santos</displayName>
<suppressMainWindow>true</suppressMainWindow>
<accountId>512</accountId>
</dial>

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 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.

When you click on an IM notification, the Messages window appears. You should be able to start typing right away. If you receive multiple IMs at once, you cannot start typing until all of the IM notifications disappear. No issue has been found when receiving only one IM. This is because IM toasts take the focus away from the Messages window.

Workaround: Explicitly click the text area in the Messages window where you want to type.

When using a Jabra headset, Jabra users are required to install Jabra direct software in order to use core functionality. You may not be notified to run Jabra Direct when you connect your Jabra device. In order to use your Jabra headset with Bria, download Jabra Direct and allow Jabra Direct API access.

Bria for Windows and Mac 5.5.1 (March 25, 2019)

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

When entering a team member's name into one of the search boxes, only the Team Voice account appeared in the auto-complete list. Now, all numbers associated with team members appear in the auto-complete list.

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

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.

When you click on an IM notification, the Messages window appears. You should be able to start typing right away. If you receive multiple IMs at once, you cannot start typing until all of the IM notifications disappear. No issue has been found when receiving only one IM. This is because IM toasts take the focus away from the Messages window.

Workaround: Explicitly click the text area in the Messages window where you want to type.

Bria for Windows and Mac 5.5.0 (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.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.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 on iOS and Android and version 5.5.0 or higher on Windows and Mac.

See Working with messages for information on exporting messages.

Users with more than one SIP account can select one of the accounts in the Outgoing Account field. In previous versions, this field reverted back to Auto Select when you restarted Bria. Now, the Outgoing Account preference is retained even after shutting down.

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

In the previous version of Bria, files opened in Messages instead of being sent to the remote party when drag and drop was used. This has been resolved in this version.

When a contact or favorite was added to the alert list using Bria for Mac, the display name changed. The display name now appears properly when the contact or favorite is aded.

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

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.

When you click on an IM notification, the Messages window appears. You should be able to start typing right away. If you receive multiple IMs at once, you cannot start typing until all of the IM notifications disappear. No issue has been found when receiving only one IM. This is because IM toasts take the focus away from the Messages window.

Workaround: Explicitly click the text area in the Messages window where you want to type.

Bria for Windows and Mac 5.4.1 (December 10, 2018)

Add your G-Suite account to Bria to integrate your G-Suite contacts. Your G-Suite contacts are read-only in Bria. To add your G-Suite account, go to Account Settings, click Add and select Google Account. When your default browser opens, sign in to your G-Suite account and click Allow.

G-Suite is part of the BriaInsider Program. Your administrator must enable it in the Bria Portal.

Skype for Business was added to Bria as a brandable option. See the Skype for Business User Guide for more information on this feature.

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.

When using the drag and drop method to send a file transfer, the file is opened in the Messages window instead of being sent to the remote party. This only occurs on Windows version 10 version 1809. If you are using this version of Windows, use the shortcut menu in Contacts or Favorites instead.

"Send Files" is in the "Contacts" short-cut menu.

When you add a Contact or Favorite to the alert list using Bria for Mac, the display name changes. The display name appears properly the next time you log into Bria. However, if you log out, the alert is removed from the Contact or Favorite.

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.

When you click on an IM notification, the Messages window appears. You should be able to start typing right away. If you receive multiple IMs at once, you cannot start typing until all of the IM notifications disappear. No issue has been found when receiving only one IM. This is because IM toasts take the focus away from the Messages window.

Workaround: Explicitly click the text area in the Messages window where you want to type.

Bria for Windows and Mac 5.4.0 (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.

Bria supports macOS 10.14 (Mojave).

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.

When you click on an IM notification, the Messages window appears. You should be able to start typing right away. If you receive multiple IMs at once, you cannot start typing until all of the IM notifications disappear. No issue has been found when receiving only one IM. This is because IM toasts take the focus away from the Messages window.

Workaround: Explicitly click the text area in the Messages window where you want to type.