Howto:Bria 2.x - Counterpath - SIP Testreport

From innovaphone-wiki

Jump to: navigation, search

Contents

Summary

The Bria 2.x softphone supports all required innovaphone features and is therefore qualified as recommended product.

The video functionality as well as the usage of wideband codecs of the softphone were also tested successfully. However when using the v7 firmware, only video calls to SIP phones registered on the same PBX will work. In v8 this limitation does not apply.

The integration of the innovaphone voicemail in the softclient is possible. The message waiting indication will work only when using v7 firmware, all other voicemail features are working with v6 firmware too.

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 22th, 2008.

Version

Firmware Version:

Bria release 2.3 stamp 49440

innovaphone Firmware:

SR2 HF7

Test Setup

Image:Bria_-_Counterpath_-_SIP_Testreport_5.PNG

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 No
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 No
Reverse Media Negotiaton No
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 (only with v7 PBX firmware)
call using wideband codecs Yes (only with v7 PBX firmware)
MWI from voicemail displayed correctly Yes(only with v7 PBX firmware)
Device can create audio conferences Yes. Maximal 6 parties
Device can create video conferences Yes. Maximum number not tested.
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. N/A
testphone calls inno1. inno1 transfers to inno2. Yes
testphone calls inno1. testphone transfers to inno2. N/A

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 No
Can be dialled from No
Does CLI resolution No

Hands free

Tested feature Result
Loudspeaker operation works fine Yes
Hands free works fine Yes
Volume adjustable during call Yes

Keys

Tested feature Result
Device has speed dial keys No
Device has programmable function keys No

Configuration

innovaphone configuration

Add a new PBX object of type "user":
Image:Bria - Counterpath - SIP Testreport_1.PNG

3rd party product configuration

Bria Account Configuration

On the Bria softphone go to "SIP Account Settings ...".
Open "Properties" of a new account and fill like this:
Image:Howto-Bria_-_Counterpath_-_SIP_Testreport_1bria.png

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

Bria Voicemail Configuration

To make Bria interrogate for current voicemail status, enable "Check for voice mail" and enter the voice mail number of the Bria user:
Image:Bria - Counterpath - SIP Testreport_3.PNG
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 ("4" + "217").

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.

Presence

In V8 innovaphone implemented the presence functionality in its PBX. The BRIA soft-phone can however interact only partially with this feature. 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).

Bria Advanced Options

Open the advanced option collection by dialing ***7469 on your Bria softphone.

Symmetric Audio Coder

Deactivate asymetric codec support on the Bria softphone, otherwise you will have one-way-audio problems.

In order to find the option "system:network:honor_first_codec" apply "honor" as filter.
Make sure the value of "system:network:honor_first_coder" is "1" (not "0") as shown here:
Image:Howto-Bria - Counterpath - SIP Testreport 2bria.png
Restart Bria to apply changes!

RTCP Timeout

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 30 seconds.
In order to keep Bria from terminating the hold call, you must set the following advanced option:

rtp:inactivity:must_have_rtcp = 0

Restart Bria to apply changes!


in release 2.5.4 build 53958 set the following advanced option:
rtp:inactivity:timer_enabled = 0

Restart Bria to apply changes!

Related Articles

Personal tools