Howto:Bria 3.x - Counterpath - SIP Testreport

FIXME: has to be finished

Summary

The presence features of the Bria soft-phone can be used only with limitations.

Certification Status

This product is being tested right now. The test is not yet completed.

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
Device supports SIPS (SIP over TLS)
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
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
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
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
call using wideband codecs
MWI from voicemail displayed correctly
Device can create audio conferences
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.
inno1 calls inno2. inno1 transfers to testphone.
inno1 calls testphone. inno1 transfers to inno2.
inno1 calls testphone. testphone transfers to inno2.
testphone calls inno1. inno1 transfers to inno2.
testphone calls inno1. testphone transfers to inno2.

Transfer with consultation (alerting only)

Tested feature	Voice Ok?	MoH Ok?
inno1 calls inno2. inno2 transfers to testphone.
inno1 calls inno2. inno1 transfers to testphone.
inno1 calls testphone. inno1 transfers to inno2.
inno1 calls testphone. testphone transfers to inno2.
testphone calls inno1. inno1 transfers to inno2.
testphone calls inno1. testphone transfers to inno2.

Blind Transfer

Tested feature	Voice Ok?
inno1 calls inno2. inno2 transfers to testphone.
inno1 calls inno2. inno1 transfers to testphone.
inno1 calls testphone. inno1 transfers to inno2.
inno1 calls testphone. testphone transfers to inno2.
testphone calls inno1. inno1 transfers to inno2.
testphone calls inno1. testphone transfers to inno2.

Blind Transfer (alerting only)

Tested feature	Voice Ok?
inno1 calls inno2. inno2 transfers to testphone.
inno1 calls testphone. testphone transfers to inno2.
testphone calls inno1. inno1 transfers to inno2.

Broadcast Group & Waiting Queue

Tested feature	Result
testphone makes call to a Broadcast Group. inno1 picks up.
inno1 makes call to a Broadcast Group. testphone picks up.
testphone makes call to a Waiting Queue. inno1 picks up before announcement is played.
testphone makes call to a Waiting Queue. inno1 picks up after announcement is played.
inno1 makes call to a Waiting Queue. testphone picks up.

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.
Bria Device makes call forward to own extension (other registration is ringing).
Bria Device has a active call (is busy) - signalling of an additional call is sent only to the Bria Device

Other Features

Directory

Tested feature	Result
Device built-in directory
Exists
Can be dialled from
Does CLI resolution

Hands free

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

Keys

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

Configuration

innovaphone configuration

Add a new PBX object of type "user"

3rd party product configuration

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

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.

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

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.

Related Articles

• Bria 3.x administrator guide

• What USB devices are supported by Bria 3.x ?