Bria 3.3 UPDATE

[Derek Jacobs]

For call quality issues, please be sure that "preserve bandwidth during silent periods" is not enabled in your media quality settings.
For call delay issues please be sure that your topology options are set correctly.
In some cases you may need to select use local IP or specify a STUN server where previously you had left the setting on auto.

[hlogmans]

Setting the topology to STUN (stun.counterpath.com) seems to have fixed the delay. The audio quality may have been another issue, because that was no problem anymore before I changed this.

[rickygomez]

I had nothing but problems since getting the last pushed update on Thursday, March 1.

I would answer a call and the call would be dropped immediately. When I would place a call, it would take 5-8 seconds before I would get a dial tone and the number would be dialed. Some numbers would not dial. I would get a "number cannot be dialed" message even though I tried calling my cell phone or house phone and those lines were available. If I could make a call, the call would be dropped exactly 1 minute 5 seconds into the call. Every time! I scoured these forums and tried every suggestion, but was still having problems. I had to use my cell phone to make business sales calls.

Today, I gave up. I uninstalled Bria 3.3 and reinstalled Bria 3.2 build 61762 and now everything works like it did before the last update. I won't be updating anytime soon.

[Derek Jacobs]

Did you even try the suggestions I have outlined?

For call quality issues, please be sure that "preserve bandwidth during silent periods" is not enabled in your media quality settings.
For call delay issues please be sure that your topology options are set correctly.
In some cases you may need to select use local IP or specify a STUN server where previously you had left the setting on auto.

[rickygomez]

Of course I did. I even stated so in my post. Did you read my comment?

But why should Bria users have to tweak settings when we get an update? If it is working, why issue an update that breaks the software? Some of us really rely on your software and when we can't use it properly, we come across as unprofessional to our clients and potential clients. And sure, there are other softphones out there, but none that do its job as well as the Bria. Just don't hamstring us with bad updates that require us to troubleshoot the software to get it to work like it was before the update.

[Derek Jacobs]

Hi Ricky

I've e-mailed you directly.

[ntitan]

I'm also having trouble since the 3.3.2 (65843) update. Call quality doesn't appear to be too affected but incoming calls drop in the first 10 seconds 20% of the time. Or have no audio.

Also out going calls take an extra 5 seconds to place.

I've tried changing the topology to STUN, and preserve bandwidth during silent periods is not selected.

I don't see where I can download an earlier version.

Thanks for your help.

[FrameworkTraining]

Just registered to post that we've had significant problems with Bria 3 since the update we installed at the end of February.

Sounds like we've been experiencing similar issues to others; incoming calls being dropped on pick-up, incoming calls continuing to receive dialling tone when we have 'answered'. Slow outgoing connections are also an issue. The only work-around for incoming calls was to pick up after the second ring - this seem to connect both sides simultaneously and not cause any disconnects. This period was a substantial wait for the incoming caller though.

We've rolled back to 3.2.1 and things are working OK.

I might reinstall 3.2.2 on a spare box and have a play with the suggested fixes.

To be frank, however, a commercial product that facilitates such a vital aspect of a company's access to it s customers should work fresh from an update.
If an updates breaks the product (even for a minority of users) the update should be quickly patched or recalled and shouldn't really require proactive searching and troubleshooting by the customer.

Regards
Ian

[FrameworkTraining]

Just wanted to post a quick update - I tried the Topology settings change and it's not improved the incoming call issues.

We'll be sticking with 3.2.1 for sure. Real shame though.

[Derek Jacobs]

Please email support directly if you would like assistance.
This is a user to user support forum.

thank you

(I have posted the resolutions in numerous other posts)

[FrameworkTraining]

Are these resolutions in addition to changing the topology settings and "preserve bandwidth during silent periods" not being selected?
I've tried both of those.