Re: [Opensync-users] Problems adding new contacts (SE 608i, irmc<->file)

[Armin B. <arm...@de...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Jason,

sorry for the very late reply. I was snowboarding and we didnt have
internet connection where we stayed. But ill try to answer your
questions as best as possible now.

Jason Grant wrote:

> Given the unfortunate lack of support for opensync, I've found the
> best source of information on this is in the IrMC spec.
>
> So it seems like the correct way to add a contact is to perform an
> OBEX put with filename telecom/pb/luid/.vcd, and it is the
> responsibility of the phone to allocate a unique ID. Unfortunately,
> the irmc-sync plugin doesn't comply with this; if I create a new
> contact without a LUID, the irmc plugin uses the filename in the
> OBEX put instead of ".vcd". Also, when the phone allocates the
> LUID following the put, I can see no mechanism in the irmc plugin
> for the local copy of the contact to be brought up to date with the
> allocated LUID, and filename that includes this ID.

> So I guess the irmc plugin is only half-built? Is it undergoing
> active development? A short synopsis of gaps would be really
> helpful for folk like me who are spending hours troubleshooting
> this stuff, when the status must be obvious to the developers.
>
Yes, the status of the irmc plugin is know to the developers. The main
problem is that the irmc plugin is a port of the plugin from multisync
(thats also the reason for some of the strange options in the config).
So all these things are bugs that existed in multisync.

I cannot promise when we will fix those issues, but your findings from
above (with the .vcd) will definitely speed this up since we dont have
to investigate this ourselves then. so thanks for your help!

Best Regards,
Armin Bauer

> Thanks,
>
> Jason.
>
>
> On Wed, 2005-12-21 at 22:52 +1100, Jason Grant wrote:
>
>> For the benefit of others, I've made a little progress here. I
>> can now add contacts that I create on my local filesystem ...
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDvmKzq9z7v9k9UakRAu6jAKCPz7w+/0R33ZmKz4odhBN00dMMJwCgiFlw
T4/MypwhBso5ck2KYvLmFEw=
=Yfb8
-----END PGP SIGNATURE-----