Call button Dissappears if logged in trough Bitlbee

[vaskozl]

If an xmpp account is logged in trough Bitlbee and Jitsi at the same time, friends are not able to perform a call as the call button is greyed out. Both local and friend client are running version 2.8 on GNU/Linux.

[bgrozev]

I suspect that this may be have been caused by 478a8ec or 4e5c881

[bgrozev]

If someone could confirm that reverting one (or both) of these fixes the problem, I'd push a revert to master (and figure out how to fix it later).

[459below]

I just tried all combinations. Both commits separately and together. But reverting those changes did not seem to fix the issue. On two separate contacts running jitsi-android and chatsecure it didn't show the buttons reliably. Though it seems to help, if jitsi is using a higher priority, since that contact does at least initially show the buttons.

[459below]

I've just tested jitsi-2.1.4590.10823 from back in 2013-04-30 and it behaves exactly the same. Meaning only the capabilities of the last signed in client on the side of the contact are being considered. Right now I'm currently looking into OperationSetContactCapabilitiesJabberImpl. If I understand correctly, there should be code checking every single resource that contact has registered and use the capabilities of the resource supporting the most capabilities. However I did not find code similar to the one in MetaUIContact yet. Unfortunately contact.getResources() seems to be empty at this point.

[459below]

So I took the list of resources straight from EntityCapsManager, since it seems way more reliable than contact.getResources(). This does actually work out pretty smoothly. I will test this a while and I will reference the commit, after I'm certain that it doesn't brake something.

[459below]

459below@9dcb88b

I've been using this fix for some days. This shows the buttons appropriately and I haven't noticed any regressions. I have noticed a different issue mentioned in the commit message. But this seems to be a different pre-existing issue.

I suppose I should create a proper pull request in order to assess these changes, shouldn't I?