Bria 3.0 Issues

[amehmood]

1. "The user experience with multiple accounts has been simplified: For phone calls, if you have multiple accounts, you must setup dial plans to select the desired accounts; you cannot select the account when placing the call."

This process not simplified our experience, just putted us in deep trouble. We are providing VOIP services/ support and working with multiple clients. We use 10 different lines at one time and frequently change these accounts according to requirements. It’s very difficult to create separate dial plan for each user instead of simply selecting desired line.
Must needed function, so its batter to restore this feature in next release.

2. Bria is dropping calls, especially when we call Bria 3.0 to Bria 3.0 over VPN (sometime without VPN) it drops call after 7 sec. but if we use Bria 2.5 to 3.0 or reverse its working properly.

3. Bria 3.0 response time is very slow compare to 2.5

4. Bria stops responding if we use/modify DNS entries for domain. Working properly if use IP address.

[Kamen]

Being able to choose the account from which to dial out using a combo box on the UI was a nice feature in version 2.5, I miss it.
Kamen

[Derek Jacobs]

Noted.
It is on my list to report to engineering.

[brianbuckman]

I would just like to reitterate that the inability to select which account to use when making a call is a major issue issue for me as well. Without this feature for me Bria is unusable. Also missing, as it is probably related, is the ability to effectively set a default account. The reason for originally switching to Bria was its ability to handle multiple accounts simply, without that you might as well stay with X-Lite.

[Kamen]

In case your need to select an account can be tied algorithmically to contacts, then you could use dialing plans (although that is not so easy to configure). However, if you need to make the decision about which account to use each time you dial (depending on other factors), Bria 3.0 just isn't able to do it and that is a problem.
A much smaller issue is the lost ability in version 3.0 to select which account is used for presence for each contact like version 2.5 could do. For instance, I have contacts on different networks that use different approaches for presence (e.g., some use peer-to-peer, some use presence agent) and using their own account that supports the appropriate technology ensures presence works in both ways. With Bria 3.0 that is not possible any longer. I suspect that there is some technical difficulty (probably standards-based) that has caused this regression in functionality, but if that is not the case, it would be highly appreciated to restore this functionality in the new version.

Kamen

[Derek Jacobs]

Hi Kamen

The first issue has been noted.
Regarding presence. We now only support presence via a single means or account.
Presence across multiple netowrks is problematic, and for 99% of users is not needed.

[brianbuckman]

Is there a comprehensive explanation of how Bria's Dialling Plans work. I tried to follow the description on the FAQ but I got lost.

Thank you.

Brian

[Derek Jacobs]

Appendix C of the user guide should have the proper information.
http://www.counterpath.com/assets/files ... nts_R1.pdf

[lucspe]

Dear Derek,

For me, not being able to select which account to use when dialing out, is a major issue. In practice, I cannot use Bria without that as I have multiple SIP accounts and depending on which number I need to call, I need to be able to select a different account.

Is there any (planned) solution to this issue?

Also, in the meantime, is there a way for me to revert back to v2.5? (the email which I received announcing the upgrade, stated that:
"Please note that once you have upgraded your license to Bria 3.0, your existing license(s) will become invalid and you will not be able to revert back to your previous softphone version.")

Thanks a lot,
Luca Speranza

[Kamen]

Dear Derek,

[...] I have multiple SIP accounts and depending on which number I need to call, I need to be able to select a different account.[...]

I believe this is the exact case (i.e., tying a contact to a VoIP account) that dialing plans are designed for. It is when you need to decide based on other criteria that it becomes a problem. You should read the manual that Derek referenced above and give it a try.
Kamen

[cello]

I was looking for a solution to this and could only find a workaround. It's not optimal, but if you prefix the phone number with #n (n being the account number in your preferences) you will dial out with the desired line.
For example: #1+4170000000 will use account 1, while #2+4170000000 will use account 2.

However, this is only practical when manually typing the phone number.

[Derek Jacobs]

Cello... et al.

I made this my #1 request to engineering for consideration.

[jh72]

Dear Derek,

[...] I have multiple SIP accounts and depending on which number I need to call, I need to be able to select a different account.[...]

I believe this is the exact case (i.e., tying a contact to a VoIP account) that dialing plans are designed for. It is when you need to decide based on other criteria that it becomes a problem. You should read the manual that Derek referenced above and give it a try.
Kamen

Imagine the most common case of "multiple accounts": one for private, one for business. And now imagine the most common call case: just dial a number. One that is not in your contacts list and will not get there. Because you just call it once. So how do you chose if to call out via your business or private account (=phone number)? Set up a dial plan for each number to call once? Nope.

Same for presence: Some people (my friends) should be able to see when I'm ready for _private_ communication. But "business partners" should only see "presence info for the business account". And maybe some stalker shouldn't even see that. Why should this be a problem?

Another issue: I've set up 2 accounts at 1und1.de and 1 at sip.gmx.net (same provider). First time all 3 worked well, but after a reboot only the first one (the one with presence info) gets registered. (And another account at 12voip.) The 2nd 1und1-account as well as the sip.gmx.net account constantly gets registration errors.

Edit: Now all 3 1&1/GMX accounts fail to register.

[Derek Jacobs]

There are no issues with registering to multiple proxies.
I'm currently registered to 6

[Kamen]

JH, those are separate issues. If you are having registration problems, that has nothing to do with presence and you should troubleshoot this the normal way (i.e., see if the provider is online, if your account configuration might have changed, etc.)
Kamen