Jan wrote on the devel-ml :
Since some users reported buggy behaviour, I tested some 5 minutes:

- EVO: Add contact, enter Video URL: Nothing shows up in Ekiga
- EVO: Add contact, enter Businessphone Number: Shows up in Ekiga (as Phone)
- Ekiga: Edit existing empty contact, add Video URI, Shows up as Businessphone number in EVO (???)
-- Re-Edit that contact in evo (add something so you can save it), the VoIP URI info for ekiga is gone, shows up as Businessphone 




I (Snark) tried to reproduce with evolution, contacts and ekiga. I don't have "Video URL" in evolution, and not in contacts -- and if I add it through ekiga, it appears as something entirely different in contacts and evolutions -- and consequently gets re-written as something else when edited.

I had a look at the codes of those applications : they don't use exactly the same api of evolution-data-server -- which means that e-d-s doesn't have the same behaviour seen from those different apis.

I would say using the VIDEO_URL in ekiga in 2.0.x was a mistake : obviously that was added to e-d-s as a second thought and isn't supported correctly by  either other clients or e-d-s itself. Using it in ekiga for 3.0.0 was needed to have compatibility between the versions (it *does* work, doesn't it!?)...

I don't know what to do, and I'm not sure there's something to do...

Confirmed. With ekiga 2 I added a few sip contacts, which landed in Evo in the "Video-Chat" field. Now, after upgrading to ekiga 3 the SIP addresses are gone, and ekiga asks me to "fill in those fields".

If that field was a mistake, then new contacts can certainly be stored in different fields, but the value of Video-Chat should always be the fallback (you can check if it starts with "sip:"), to not break existing configuration for users.

Thanks!

*** Bug 564790 has been marked as a duplicate of this bug. ***

*** Bug 564834 has been marked as a duplicate of this bug. ***

*** Bug 578814 has been marked as a duplicate of this bug. ***

What migration do you propose? If we detect a video url, do we move it to something else? If so, what?

If roster is empty (we consider this as a transition from v2 to v3), copy all contacts visible in ekiga 2 into ekiga 3 roster.  Is that good?

That bug isn't about the roster, but about the evolution book as visible in the addressbook window...

Really sorry, I have misunderstood this bug.

No problem ; in fact I'm wondering if we shouldn't push it to evolution-data-server... after all, it provides several apis, and those give inconsistent results :-/

*** Bug 580975 has been marked as a duplicate of this bug. ***

Hmm. This bug is sitting here since a year. Any workaround? (Should Ekiga audio magically start to work in Fedora 10/11...)

Julien, any news about this bug?

No news ; I have disabled e-d-s in my personal builds since long.

So, since you are not working on this bug anymore and it is an old issue, we close it as WONTFIX?