BRIA 3 as Endpoint reviews

[cavagnaro]

Hi guys,
I'm doing a small lab with BRIA as endpoints for SIP Server and so far have encountered a couple of issues:

1. When A is doing a conference call with B, A doesn't autoanswer this call (even when autoanswer is setted up and in Options the Autoanswer timer = 0). Whant happens is that the second line rings and the agent has to answer this one before the B extension actually starts ringing. Is this ok? Do you consider it as normal? How to over-ride this and make it autoanswer as well?

2. When doing the conference we lost the audio between the 3 participants we lose the audio. Still checking the SM but funny thing is that if we do this without GAD it works fine...

Any ideas and experiences?

[cavagnaro]

If you could also share the Annex tab config you use, that would be great.
Thanks

[aakarach]

best thing to do, do not use GAD with bria use IWS (if you really need to and have no other options), it much better and more fully integrated for 3pcc

[cavagnaro]

Do you have some tests done? Autoanswer for example?

[Adam_W]

I'd really recommend against using the Bria standalone client.

When using it with GAD I've experienced the following issues, amongst others that I've probably forgotten:

1.  Audio randomly dropping out for a few seconds mid-call;
2.  Delays in connecting the two parties at the start of a call;
3.  Garbled audio when retrieving a call from hold using the GAD (pressing hold then retrieve in Bria resolves this);
4.  Bria volume control randomly muting itself;
5.  Bria application crashes;
6.  Bria loses connection with SIP Server but GAD stays in Ready status, leading to dropped calls;
7.  RTP inactivity timer does not work correctly (If an agent puts a customer on hold and initiates a call to a 3rd party with the customer still on hold, after 30 secs the call is cut off.  The timer was not even set to 30 secs!  Deactivating the timer resolves this)

To make things worse, each new release of the software introduced a new issue.

Deployment of the application is also a particular challenge with more than just a few users because there's no mass deployment solution and all the settings are held within the user profile.

The main issues seem to be caused by the poor interaction between GAD and Bria.  Although the Interaction Workspace SIP Endpoint uses Bria's technology, it sounds like it's much more tightly integrated.  I've just begun looking at this so will update here if any problems!

[cavagnaro]

Hi,

7.  RTP inactivity timer does not work correctly (If an agent puts a customer on hold and initiates a call to a 3rd party with the customer still on hold, after 30 secs the call is cut off.  The timer was not even set to 30 secs!  Deactivating the timer resolves this)

About this issue:

I have been testing the same and I had to do 2 changes on Bria:
Disable it: because by some reason RTP is not send to Stream Manager...the issue is the RTP Stream...not the timer.
On the SIP account settings: Enable SIP register sessions (UAS) with 60 seconds.