In the General tab you also want to provide user account information: I haven’t found a more viable workaround at this time. De-selecting the IM/Presence option will “hide” the DnD presence option. During my testing, I found that the “Do Not Disturb” feature in the Bria client doesn’t work with CUCM and results in a fast busy. You may want to de-select the IM/Presence option. For CUCM integration, you will want to enable this account to use the “Call” option. The name is locally significant and can be anything you want. Under the “Account” section you must give the account a name. When you add a new SIP account, a multi-page configuration dialog is presented. You will have the option to add a SIP account or a XMPP account. Under the account list you will see a plus “+” sign. You will see “Mac Address Book” account listed (we will discuss this later). When the Preferences panel loads, click on the Accounts tab. In the application menu choose Bria 3>Preferences. Enter the license key as provided and you should be good to go.Īfter launching Bria, you will need to provision an account for use with CUCM. The license key is provided by CounterPath when you purchase the software. The first time you launch Bria, you will be prompted to enter a valid license key. The first step is to download and install the CounterPath Bria client. This is necessary to support the video capabilities in Bria. The primary difference between the X-Lite procedures and those I used for Bria is that I added a 3rd Party Advanced SIP Device to CUCM instead of a Basic SIP Device. See the blog on CounterPath X-Lite version 3.0 for more information. For sake of brevity, I won’t repeat all of the procedures here. The procedures for configuring CUCM are pretty much the same as I used for X-Lite 3.0. So, I expect what I am provided herein applies to 6x, 7x, and 8x appliance models. The procedures I used are similar to those used for other 3rd party SIP applications I have tested on CUCM 8x and 7x platforms. At the time of this writing, Cisco isn’t offering a “voice-only” softphone like Cisco IP Communication (CIPC) for the Mac OS X platform. However, Jabber for Mac requires a Unified Presence Server or WebEx Connect account to load. Some additional background here, Cisco has a Jabber client for Mac OS X and that client can intercommunicate with CUCM. I also wanted to test out various end user features and functionality with Bria to determine how viable it was as a soft client for OS X users. So, I decided to drop the $49 bones for CounterPath Bria to see what’s what. I also kinda wanted to get rid of that annoying banner ad that X-Lite 4 has. The X-Lite client only supports H.263 for video media and the Cisco 9900 only supports H.264. A quick check and it was easily determined that this does not work. I have used X-Lite for video communications with the Cisco Video Communications Server (VCS) but I had not tested with the Cisco 9900 series phones. Specifically, they wanted to know if X-Lite supported video communications with the Cisco 9900 series IP phones. One of the readers of my blog asked me about video and X-Lite.