Don't get me started on Counterpath...

There are new tracker items on the JIRA.


http://track.sipfoundry.org/browse/XX-8542
Seems a simple fix to me, generate a blank file to the phone doesn't
timeout trying to subscribe to an empty list.

http://track.sipfoundry.org/browse/XX-8558
Webdav/presence:storage issue

http://track.sipfoundry.org/browse/XX-8528
Firewall setting not correct for 3.x provisioning

http://track.sipfoundry.org/browse/XX-8634
Bria 3.1 : Call to User added under Instant Messaging enabled user Group fails

http://track.sipfoundry.org/browse/XX-8632
Bria 3.1: "See this person's Jabber online presence" should be enabled.

http://track.sipfoundry.org/browse/XX-8633
Bria 3.1: "See this person's Jabber online presence" parameter gets
disabled on every login.

http://track.sipfoundry.org/browse/XTRN-1065
Duplicate IM contacts in Bria 3.1 Client

For me this last one is the worst, because it uncovers the "1980's"
way CounterPath went about implementing XMPP. It has to do with the
fact they they DO NO use SRV for XMPP at all, instead, they want
u...@hostname, even for contacts, so it will CONTINUE to play a role
in the cascading failures with subsequent versions. THIS is the issue
they have flatly denied to address at all. They use SRV for SIP, but
not on XMPP, on the same client application! How broken is that?
VERY!!! I suspect this will continue to be a problem IF thy dont fix
it, otherwise there will be LOTS of special code in various places in
sipx to address it, which will probably have to shift every time CP
makes a new release...

Enough ranting. If you have comments on the trackers, it would be
great if you could provide any relevant information.



On Fri, Aug 27, 2010 at 7:39 AM, Paul Scheepens <[email protected]> wrote:
>
> Just saw this thread, was on a very nice holiday, which resulted in a "small" 
> backlog of SipX mails.
> I can confirm that 3.1.2 (I now have build 58754) is still not good.
> I don't have the "4 XMPP contacts" problem however.
>
> At the moment there are umptie ways to get contacts and presence into Bria.
> So to keep posts understandable I think it is necessary to find a good way of 
> describing how you get them in
> and also the best way to get them in.
>
> OK this is going to be a long mail, but I want to get this a bit clearer (and 
> I hope this helps..................)
> AFAIK at least the following methods exist to get contacts in Bria:
> Disclaimer: this is to my best knowledge, if somebody thinks I am wrong 
> please let me know what I've got wrong.
>
> 1) On Phone level, configured under Phone in Sipx and under Preferences in 
> Bria
>    Phone and User are normally  mapped one to one in Bria because the 
> Phone-id is
>    the user-id.
> 2) On User level, configured on the Line in SipX and under Account Settings 
> in Bria
> 3) UserGroup IM, configured on User Groups in SipX, not configurable in Bria
> 4) WorkGroups, not really presence, but still a bit ........
>    configured under User, Speeddials in SipX, not configurable in Bria
>
> 1) Under Preferences we have Local, webdav and xcap
> 1.1) Local, is useful, but completely user-managed and not suitable for 
> hotelling setup
> 1.2) Webdav, read below for my 2 cents:
>    If under Phone settings in System you select "webdav" as "Resource list 
> method" you get ALL users
>    defined in SipX as contacts in Bria under the Group "Work".
>    AFAIK there is no way to control what gets distributed. ---I think this is 
> what you use Tony, or not?-----

Correct. Additionally, once you do invites using webdav as storage, it
works properly and the contact list is in the proper location in
sipx/webdav. HOWEVER, upon a restart of the BRIA the data (contact
list) disappears and the only way to use it again is to reinvite...
Counterpath says its sipx...
>
> =The XMPP case
>    If Bria is using XMPP for presence (and thus not SIP, you enable XMPP by 
> enabling Instant Messaging
>    for the user) then you won't see any presence because the checkbox
>     "See this person's Jabber online presence" is not ticked. Tick it and 
> presence is working.
>    (I think Openfire takes care of the autorization). ---Are you also using 
> XMPP Tony?--

Yes, but not with presence agent, because that does not work.
>
>    Restart/Logout/reboot and the tick is gone again because Bria is not 
> allowed (I am guessing here, but almost sure)
>    to WRITE to the XMPP contacts list on the Sipx-Openfire-XMPP server.
>    If your user community isn't changing a lot you can get all your contacts 
> into Bria this way, then disable
>    WebDav in SipX for that Phone, then place the ticks. Now they are 
> persistent because they are stored either locally or
>    on a different WebDav (see 2.2 below, this allows hotelling as well).
>
> = The SIP-presence case
>    Is similar to the XMPP case, set tick to see presence, reboot/logout and 
> it's gone again.
>    Again Bria can't write the new presence config back to SipX.
> 1.3) Xcap, nothing to report from this side
>
Yes, it has to do with the list being removed and not "saved" or
reinserted after a logout/reboot.
>
> 2) Under Account we have the same options......
> 2.1) Local, useful again but again no bonusses.
> 2.2) Webdav, not configurable in SipX without modification, with my mod it is.
>    When using your own webdav you can write to it, thus ensuring that the 
> presence tick is kept.
>   Good solution for Hotelling. Very usefull in combination with 1.2
> 2.3) Xcap, again no experience.
>
> 3) UserGroup IM
>    I really like this feature, it gives you some control on what gets 
> distributed to the users and you can Group users.
>    Also presence seems to work out of the box for Groups, so no fiddling 
> needed. There is of course a drawback.....
>   Currently Bria does not check for duplicates, so after a 
> reboot/restart/logout your contacts are in the list twice.
>   One more restart and you have triplets, etc.
>   Otherwise this would be a perfect alternative for option 1.2 since it gives 
> you the option to distribute all..but a few..users.
>   There is for example no need to distribute superadmin IMHO.
>   Nice thing is that if you create multiple Usergroups in SipX then in Bria 
> you see the same groups
>   (like "Engineering" and "Not Engineering"). If you are not part of a 
> Usergroup you don't see the Group in Bria.
>   This is both nice and not nice of course. It would be nice if on UserGroup 
> (or User) level you could configure which
>   other UserGroups should be distributed to this UserGroup (User) as well.
>   To bybass Bria's unability to keep the list unique you could load the 
> UserGroups, then disable the IM for the Usergroup
>   so that the client is not updated anymore. All clients do have to authorize 
> each other then (apparently
>   authorization to see each others presence is removed from openfire when you 
> remove IM from the group).
>
> 4) Workgroups
>    By configuring speeddials for a user and enabling presence for them you 
> create a workgroup with  presence status.
>    This allows for call pickups as well.
>   Again, this is not really presence, but it's a way of automatically 
> distributing contacts.
>
> Best regards / Mit freundlichen Grüßen / Sincères salutations
>
> Paul Scheepens
>
> P.S. Sorry for the long mail :o)
> P.P.S. Thanks to Paul Herron for the nomination as a proxy, just before I 
> read your mail I send this to Counterpath Support,
> which Support "passed on to Engineering", lets see whether we will hear more:
> =Hi,
> =
> =I would like to let you know that we have a growing need for a decent 
> softphone.

Agreed. Bria works as a phone, but the rest of the application leaves
a lot to be desired. I have NEVER had a bria working properly without
having to modify sipx provisioning or the bria client itself YET.
Their XMPP implementation leaves a lot to be desired, and I did ask
pointed questions of them, to which they replied "we have no plans to
fix that"... so I say, gotta find another softphone, perhaps one that
has dialogue events AND lets you use a different IM client
(spark/pidgin), because integration makes NO SENSE if you have to wait
another two or 3 years to get it right with what you have now.
>
> =I would also like to let you know that at the moment Bria is not performing 
> in an acceptable way.
> =
> =How can it be that you announce 3.1 mid july and say "The retail version of 
> Bria 3.1 will be available mid-July"?
> =The product is still not available! Fortunately I got my hands on 3.1 build 
> 58754, but this does not seem to solve
> =my main problems.
> =
> =Please pay more attention to the product. It would be a great pity if we 
> have to abandon this product.
> =

Run away!!
>
> =But at the moment it is not really better or more stable then say 1 1/2 year 
> ago and some functionality seems to be worse.
> =

Well, if I logged all the hours that I have spent doing
troubleshooting and talking to their technicians, or trying to anyway,
I don;t think I should have to actually pay for the phone. They say it
has "this" functionality, which I get, is their problem and doesn't
work. They should offer bounties to find bugs before releasing, at
least that way they have a monetary way of tracking what needs to be
fixed.
>
> =Please pay attention to the following problems, still existing in build 
> 58754, in order of priority:
> =
> =- Echo Cancellation, fix it, how else can I convince people that Bria is a 
> decent mature product when even for example Google Talk gives them better 
> voice quality?
> =I now have to use Solicall next to Bria, that is a stupid way of doing 
> things.
> =- XMPP, fix it or don't support it, stick to standards.

Agreed.
>
> =IM groups work in 3.1 (not in 3.0, an improvement) but each time you restart 
> the contacts are reloaded and not checked for duplicates, so after 5 restarts 
> each contact is in the list 6 times.
> =- Responsiveness of the application is not OK.

That's sad, but I have the download to 3.0 if you need it, but you
have to uninstall first.
>
> =In the past switching between headset mode and speakermode was 
> instantanious, now there is a 5 second freeze of the video.
> =I am using a Polycom CX300 with Bria, if I press a key on the Polycom it 
> takes too long before it appears in Bria.
> =- HID settings are now stored on a per user basis, this is annoying if you 
> have to map say 15 buttons for each user.
> =It should not be so difficult to load a user file if it exists, and if that 
> does not exist to load a general file.
> =Other option would be a checkbox in the configuration window to say "use for 
> all accounts"
> =- Video with Vico systems. When we set up a vico with a Tandberg in HD 
> widescreen mode we still see black bars on the Tandberg on each side of the 
> picture.
> =The image is a 16:9 image displayed as 4:3, so people seem to have small 
> faces.
> =According to the Tandberg it receives VGA resolution. This does not seem to 
> be OK.
> =
> =I hope you don't consider this as ranting, I like the functionality of the 
> product, but please make it a bit more userfriendly.
> =Please give me a few dates when I can expect solutions to my problem.
> =I will have to convince my management to continue with Bria.
> =
> =Best regards / Mit freundlichen Grüßen / Sincères salutations
> =
> =Paul Scheepens
> =
> [email protected] wrote on 20-08-2010 21:29:49:
>
> > From:
> >
> > Tony Graziano <[email protected]>
> >
> > To:
> >
> > Kyle Haefner <[email protected]>
> >
> > Cc:
> >
> > sipx-users <[email protected]>
> >
> > Date:
> >
> > 20-08-2010 21:29
> >
> > Subject:
> >
> > Re: [sipx-users] Bria 3.0 --> 3.1
> >
> > Sent by:
> >
> > [email protected]
> >
> > I had someone tell me today it loads 4 users on new installs.
> >
> > I had removed the profiles for another user, logged out/exited, and
> > logged back in to pickup new configs, still 4 of everyone. In 90
> > minutes those peope are getting paychecks for 25% of what they are
> > used to! har har har.
> >
> > If someone needs 3.0 (win.mac) message me offlist.
>
> > On Fri, Aug 20, 2010 at 3:19 PM, Kyle Haefner <[email protected]
> > > wrote:
> > Tony,
> >
> > No just one, but this is a fresh install of 3.1.2.  I wonder if there
> > is a setting in the User/AppData folders that is causing this, doesn't
> > help your upgraded users though.
> >
> > Kyle
> >
> > On Fri, Aug 20, 2010 at 1:13 PM, Tony Graziano
> > <[email protected]> wrote:
> > > argh says charlie brown... are you also getting 4 of every IM
> > contact though?
> > >
> > > On Fri, Aug 20, 2010 at 3:05 PM, Kyle Haefner <[email protected]
> > <mailto:[email protected]>> wrote:
> > > I thought setting:
> > > system:contact_list_storage:resource_list_method="local"  re-enabled
> > > presence.  I still see presence using 3.1.2 on windows and OSX, I've
> > > never seen it on the linux version, but that has so many problems it
> > > should still be beta.
> > >
> > > Kyle
> > >
> > > On Tue, Aug 17, 2010 at 12:15 PM, Tony Graziano
> > > <[email protected]<mailto:[email protected]>> wrote:
> > >> I had counterpath issues today... like that is any surprise. They
> > started notifying users of an update. 3.0 users who are entitled now
> > get a 3.1 version installed. Presence is now broken (again). Does
> > anyone "know" if this works?  Now contacts are showing up 4 times,
> > and presence is not working.
> > >>
> > >> I think a JIRA to block or specify codeservers for Counterpath
> > phones should be in order. That way an admin can at least figure out
> > a way to "control" the upgrade process instead of being chaotically
> > introduced to bugs...
> > >>
> > >> --
> > >> ======================
> > >> Tony Graziano, Manager
> > >> Telephone: 434.984.8430
> > >> sip: [email protected]<mailto:
> > [email protected]><mailto:[email protected]
> > <mailto:[email protected]>>
> > >> Fax: 434.984.8431
> > >>
> > >> Email: [email protected]<mailto:[email protected]
> > ><mailto:[email protected]<mailto:[email protected]>>
> > >>
> > >> LAN/Telephony/Security and Control Systems Helpdesk:
> > >> Telephone: 434.984.8426
> > >> sip: [email protected]<mailto:
> > [email protected]><mailto:[email protected]
> > <mailto:[email protected]>>
> > >> Fax: 434.984.8427
> > >>
> > >> Helpdesk Contract Customers:
> > >> http://www.myitdepartment.net/gethelp/
> > >>
> > >> Why do mathematicians always confuse Halloween and Christmas?
> > >> Because 31 Oct = 25 Dec.
> > >>
> > >>
> > >
> > >
> > >
> > > --
> > > ======================
> > > Tony Graziano, Manager
> > > Telephone: 434.984.8430
> > > sip: [email protected]<mailto:
> > [email protected]>
> > > Fax: 434.984.8431
> > >
> > > Email: [email protected]<mailto:[email protected]>
> > >
> > > LAN/Telephony/Security and Control Systems Helpdesk:
> > > Telephone: 434.984.8426
> > > sip: [email protected]<mailto:
> > [email protected]>
> > > Fax: 434.984.8427
> > >
> > > Helpdesk Contract Customers:
> > > http://www.myitdepartment.net/gethelp/
> > >
> > > Why do mathematicians always confuse Halloween and Christmas?
> > > Because 31 Oct = 25 Dec.
> > >
> > >
> >
> >
> >
> > --
> > ======================
> > Tony Graziano, Manager
> > Telephone: 434.984.8430
> > sip: [email protected]
> > Fax: 434.984.8431
> >
> > Email: [email protected]
> >
> > LAN/Telephony/Security and Control Systems Helpdesk:
> > Telephone: 434.984.8426
> > sip: [email protected]
> > Fax: 434.984.8427
> >
> > Helpdesk Contract Customers:
> > http://www.myitdepartment.net/gethelp/
> >
> > Why do mathematicians always confuse Halloween and Christmas?
> > Because 31 Oct = 25 Dec.
> > _______________________________________________
> > sipx-users mailing list
> > [email protected]
> > List Archive:
> http://list.sipfoundry.org/archive/sipx-users/


--
======================
Tony Graziano, Manager
Telephone: 434.984.8430
sip: [email protected]
Fax: 434.984.8431

Email: [email protected]

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected]
Fax: 434.984.8427

Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/

Why do mathematicians always confuse Halloween and Christmas?
Because 31 Oct = 25 Dec.
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to