Howto:Bria 3.x - Counterpath - SIP Testreport
Summary
This testreport is based on the Bria 3.x softphone Windows edition. There is also a Mac and Linux edition but they are not in the scope of this test.
The Bria 3.x is an new version of the already tested and certified Bia 2.x . Bria 3.x comes with new features like SRTP, LDAP, DHCP provisioning, hide own number, HD Video, USB HID support and additional language support.
innovaphone do not recommend connecting the Bria LDAP client to big LDAP databases.
The presence features of the Bria soft-phone can be used only with limitations.
Certification Status
The tests for this product have been completed.
Testing of this product has been finalized August 16th, 2010.
Version
Firmware Version:
Bria release 3.1.1 stamp 58571
innovaphone Firmware:
V8 HF5
Test Setup
Device Setup
Tested feature | Result |
---|---|
Register Device w/o specific configuration (requires DHCP) | No |
DHCP is default | Yes |
DHCP yields timeserver and time displays correctly | Yes |
SNTP config has TZ string for timezone/dst autoconfig | Yes |
DHCP yields correct default gateway | Yes |
Device supports magic registration (e.g. by serial) | No |
Fixed registrations works | Yes |
Device registers w/o Extension (just by name) | Yes |
Device registers by extension | Yes |
Device registers with password | Yes |
Device registers multiple identities | Yes |
Device supports STUN protocol | Yes |
Device sends NAT - keepalive messages | Yes |
Device refreshes the PBX registration | Yes |
Device supports SIP over TCP | Yes |
Device supports SRTP | Yes |
Device supports SIPS (SIP over TLS) | Yes |
Device supports HTTPS | N/A |
Device supports VAD (Voice activity detection) | Yes |
Test Results
Basic Call
Tested feature | Result |
---|---|
call using g711a | Yes |
call using g711u | Yes |
call using g729 | Yes |
Overlapped sending | No |
Early media channel | Yes |
Device shows called id number | Yes |
Device shows called id name | Yes |
Device shows called id display info | Yes |
Fax using T.38 | N/A |
CGPN can be supressed | Yes |
Reverse Media Negotiaton | Yes |
Device shows CDPN/CGPN on incoming call | Yes |
Device shows CDPN/CGPN on outgoing call | Yes |
Device shows connected number | Yes |
Device shows diverting number | No |
Device supports distinctive ringing | No |
Device supports asymetric codec negotiation | Yes |
Device supports codec renegotiation during a conversation | Yes |
Device shows correct display message in case of busy CDPN | Yes |
Device shows correct display message in case of not existing CDPN | Yes |
Device shows correct display message in case that the call is declined | Yes |
Call using video | Yes |
call using wideband codecs | Yes |
MWI from voicemail displayed correctly | Yes |
Device can create audio conferences | Yes , up to 6 possible |
Device can create video conferences | Yes, 3 way conference possible |
Voice Quality OK? | Yes |
DTMF
Tested feature | Result |
---|---|
DTMF tones sent correctly | Yes |
DTMF tones received correctly | Yes |
Hold/Retrieve
Tested feature | Result |
---|---|
Device handles incoming hold (sendonly) correctly | Yes |
Device can put a call on hold using correctly(inactive or sendonly) | Yes |
Transfer with consultation
Tested feature | Voice Ok? | MoH Ok? |
---|---|---|
inno1 calls inno2. inno2 transfers to testphone. | Yes | Yes |
inno1 calls inno2. inno1 transfers to testphone. | Yes | Yes |
inno1 calls testphone. inno1 transfers to inno2. | Yes | Yes |
inno1 calls testphone. testphone transfers to inno2. | Yes | Yes |
testphone calls inno1. inno1 transfers to inno2. | Yes | Yes |
testphone calls inno1. testphone transfers to inno2. | Yes | Yes |
Transfer with consultation (alerting only)
Tested feature | Voice Ok? | MoH Ok? |
---|---|---|
inno1 calls inno2. inno2 transfers to testphone. | Yes | Yes |
inno1 calls inno2. inno1 transfers to testphone. | Yes | Yes |
inno1 calls testphone. inno1 transfers to inno2. | Yes | Yes |
inno1 calls testphone. testphone transfers to inno2. | Yes | Yes |
testphone calls inno1. inno1 transfers to inno2. | Yes | Yes |
testphone calls inno1. testphone transfers to inno2. | Yes | Yes |
Blind Transfer
Tested feature | Voice Ok? |
---|---|
inno1 calls inno2. inno2 transfers to testphone. | Yes |
inno1 calls inno2. inno1 transfers to testphone. | Yes |
inno1 calls testphone. inno1 transfers to inno2. | Yes |
inno1 calls testphone. testphone transfers to inno2. | Yes |
testphone calls inno1. inno1 transfers to inno2. | Yes |
testphone calls inno1. testphone transfers to inno2. | Yes |
Blind Transfer (alerting only)
Tested feature | Voice Ok? |
---|---|
inno1 calls inno2. inno2 transfers to testphone. | Yes |
inno1 calls testphone. testphone transfers to inno2. | Yes |
testphone calls inno1. inno1 transfers to inno2. | Yes |
Broadcast Group & Waiting Queue
Tested feature | Result |
---|---|
testphone makes call to a Broadcast Group. inno1 picks up. | Yes |
inno1 makes call to a Broadcast Group. testphone picks up. | Yes |
testphone makes call to a Waiting Queue. inno1 picks up before announcement is played. | Yes |
testphone makes call to a Waiting Queue. inno1 picks up after announcement is played. | Yes |
inno1 makes call to a Waiting Queue. testphone picks up. | Yes |
Twin Phones
Twin Phone feature is a checkmark in the user object, which means that one user uses different phones. The main difference is, that if one phone is busy and additional call is sent to the busy phone only as call waiting and not to the other phones.
Tested feature | Result |
---|---|
Bria Device pick up call -more phoes are ringing h.323 and sip registration at the same extension. | Yes |
Bria Device makes call forward to own extension (other registration is ringing). | Yes |
Bria Device has a active call (is busy) - signalling of an additional call is sent only to the Bria Device | Yes |
Other Features
Directory
Tested feature | Result |
---|---|
Device built-in directory exists | Yes |
Can be dialled from | Yes |
Does CLI resolution | Yes |
Hands free
Tested feature | Result |
---|---|
Loudspeaker operation works fine | Yes |
Hands free works fine | Yes |
Volume adjustable during call | Yes |
Configuration
innovaphone configuration
Add a new PBX object of type "user"
TLS
When using SIP via TLS you need to configure a self-signed certificate with the IP address as common name at your innovaphone PBX. Also you need to put this certificate to the PC (where the softphone runs) and add it to the trusted certifications. Per default the innovaphone PBX holds a certificate with the mac address as common name. The Bria don´t accept this certificate, it needs the IP address of the PBX as common name.
Bria 3.x configuration
Account Configuration
Open the Bria, go to tab sofphone/account settings and add a new account
You can use the Dialing plan to support international numbers, e.g. +x.T;match=1;prestrip=1;pre=000 will remove the `+´ from an international number and replace it with 000 (assuming this is your international trunk prefix from an internal line).
Voicemail configuration
To make Bria interrogate for current voicemail status, enable Check for voicemail in the Sip account/Voicemail and enter the voice mail number of the Bria user.
Like sip:VMnumber+etension@ipaddress of the PBX
Usually the voice mail number of a PBX user is constructed by appending the phone number of the PBX user to the voice mail prefix (9 + 100)
MOH methode
In order to get the MOH working right you need to set the hold method to M-line and C-line. Go to softphone/account settings/edit account/tab advanced
TLS & SRTP
For using SRTP you need to enable make and accept only encrypted calls, the drawback is that you only can make calls to devices supporting SRTP.
Recording
There are three ways of recording a call
- use the build in recording from Bria, during a call press the record button. After ending the call a screen pops up showing you where the file is stored. You can change the file name in this screen and/or delete the file.
- use a professional third party solution for recording
Presence
In the SIP account change the presence modus from peer-to-peer to presence agent.
Also you need to enable your SIP account for presence.
Presence interaction works only partially with the BRIA soft-phone and innovaphone PBX. By using Bria you can see the presence state of your 'buddy list' contacts. You can also change your own presence state by using a drop-down menu in the soft-phone. The new state is published to the PBX and from there to other users monitoring your state.
The limitation of the BRIA client is that it doesn't allow the PBX to update it's presence state. Its not designed for a user having more then one client (e.g. IP hard phone, mobile phone, DECT handset, etc.). So if you have more then one devices registering to your PBX user, changing the presence state from another device (e.g. mobile phone) is ignored by BRIA. The new state is not displayed in the soft phone menu. Moreover the PBX presence state is overwritten with the state configured at the BRIA client after a defined period (by default 3600 sec).
In conclusion, BRIA can only use innovaphone presence feature if the soft phone is the sole client registered to a PBX user (e.g. no multiple registrations). Also you cannot change the presence state from the PBX (e.g. by DTMF Feature Object, Mobility)
LDAP integration
Bria 3.x supports connecting a LDAP directory or Active directory server. The search entries from the directory will appear at the directory tab.
* Note: innovaphone do not recommend to connect the Bria LDAP client to a LDAP directory that has a big database.
The Bria trys to download the whole subtree and displays then the search entry, but when having many entries the download will stop somewhere and thus not displaying your search entire. We have tested and seen this behaviour with a LDAP database having more then 15.000 entries.
Tests with a LDAP database (innovaphone PBX) having about 200 entries worked fine (but be in mind that every search request will download all LDAP entries). Here it shows how to connect the Bria LDAP client to the innovaphone PBX.
Go to softphone/preferences/Directory
Bria advanced options
RTP inactivity timer
When Bria puts a call on hold RTP is deactivated. Although RTP is inactive Bria expects to receive RTCP report periodically. Otherwise Bria will terminate the held call automatically after 60 seconds. In order to keep Bria from terminating the hold call, you must set the following advanced option:
Go to softphone/preferences/advanced and unchek the chekmark - RTP enable inactivity times.
Codec setting
Deactivate asymetric codec support on the Bria softphone, otherwise you will have one-way-audio problems (at transfer and blid transfer).
Go to softphone/preferences/Audio Codecs and chek the cekmark accept the first codec offerred
Provisioning
With Bria 3.x it is possible to do
- remote login
- remote provisioning
- remote configuration update
- remote software upgrade
You must deploy a web server (serving plane text and xml) to do the remote provisioning, the server is provided via DHCP or manual setting. The exchange is performed via HTTP or HTTPS.
More about provisioning is described in | Provisioning Guide Retail Deployments pdf. The provisioning feature was not tested by innovaphone.