Re: Addressbook sync with nextcloud
Rainer Dorsch via Linphone-users <[email protected]> Mon, 21 Jul 2025 20:02:15 +0200
| Newsgroups | gmane.comp.voip.linphone.user |
|---|---|
| Organization | @home |
| Message-ID | <8556345.T7Z3S40VBb@h370> |
Hi Greg, many thanks for following up. Am Samstag, 19. Juli 2025, 19:20:29 Mitteleuropäische Sommerzeit schrieb Greg Troxel: > Rainer Dorsch via Linphone-users <[email protected]> writes: > > I use davx5 to access CardDAV on my nextcloud server. > > I didn't reply to your first message becauae you didn't mention what you > are actually doing in enough detail. I apologize for not providing many details, I thought the questions is trivial and I am just missing a minor detail, which is obvious for other linphone users. > Now we have a clue that you are using Android. No, I just mentioned davx5 to show that on the nextcloud side the CardDAV interface is configured and operational. Also kaddressbook (out of KDE Gear) on the same Linux desktop which runs linphone works flawless with my nextcloud instance. > > If I enter this address in linphone, I get a synchronization error from > > linphone. If I start linphone with --verbose, I get on the commandline > > But it seems that maybe you are not. I am on Debian Linux Trixie (upcoming 13.0 release). > > <d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns"> > > > > <s:exception>Sabre\DAV\Exception\NotAuthenticated</s:exception> > > <s:message>No public access to this resource., AppAPIAuth has not > > passed, No> > > 'Authorization: Basic' header found. Either the client didn't send one, or > > the server is misconfigured, No 'Authorization: Bearer' header found. > > Either the client didn't send one, or the server is mis-configured, No > > 'Authorization: Basic' header found. Either the client didn't send one, > > or the server is misconfigured</s:message> > > </d:error> > > To debug this, you should begin by understanding how this is supposed to > work: > > nextcloud provides a carddav server, accessed with authentication to > the nextcloud user > > davx5 on android gets conencted to the carddav server > > davx5 provides a contacts database view to the OS > > programs that can display and use contacts access the contacts api and > see contacts from the union of the provided views > > > Step 0 is log into nextcloud as admin and click around to get it to do > the system selftest and eval. Or have your admin check that. > > Step 1 is log into nextcloud, click settings and look at contacts > URLS, and click contacts app and make sure all is ok. > > Step 2 is configure DAVx5 to login. > > Step 3 is use the contacts app and see if that is ok. > > Only when all of that works should you move on to linphone. As mentioned above, that works flawless and not only with davx5 & contacts app. > > On the server side, I see that the URL is accessed, but I don't see any > > error indication. > > > > There is an authentification area field in the linphone DAV settings, I > > leave that empty, since I have no idea what that is supposed to be. > > linphone implementing carddav is an alternate path to linphone using the > android system contacts interface, with that being populated by DAVx5. I am using linphone on a Linux desktop: Linphone-6.0.0-CallEdition-x86_64.AppImage > (As alawys, follow up on list, not to me directly. It would be rude of > me to quote private mail on the list, and I don't want to provide > offlist help as that doesn't help the next person.) Sure. Please let me know, if I missed to share some information this time. Thanks Rainer -- Rainer Dorsch http://bokomoko.de/ _______________________________________________ Linphone-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/linphone-users
signature.asc
(application/pgp-signature, 659 B)
-----BEGIN PGP SIGNATURE----- iQGzBAABCgAdFiEEvxDOxJgXzxfm1YjWzE1Dd9lwMVMFAmh+gKcACgkQzE1Dd9lw MVMDUQv8DmWqo+TEiFDdAZK5XvEltQsxGy5NNaxCBds4xWcOEWIT4LWJb2sA/peC 6uiuYSfUfhhq3T693ij/5fo8E4xPRWuT9rjXJzroa96UIBQfM+ScRXgeay8oD8Fp N1rpr5VDksrofs34XeVBK/x9rsW59ocqWgvXZGmXpvYNq3uiFHpCHCAg76evqFGJ lWoiSs1KRCVWAonJZDU6golH4v85WOqfvhrvIsil7ZUm32ZV37iFBkD+XjhcbQFb ZCD70AmRt0Jkemz4J+P3vGz3N2lw+ynRC0QfwKBSkSq+CHkV7bRYIVfFdwLOKQQx uIqKQhtGgc7r5i4vs8lUBiedycSficvL7jCbp8Ka2XZBZpyaYR2wyaLCZa5xyWzf 8cJbLbrqdzdX60Yneq0L0WG/fUv20Zdpu4uGO4AUj8Tm9egpHx5BpaV//rawFo8H y1TOiLJJrzCOzugK33SIHudWyTV6DSX0dFWjulffh1sUBLwHBT30qCWBG0yyV4s2 xJ/4Yf5B =P4HZ -----END PGP SIGNATURE-----