freebusy configuration, what is needed in kontact

[Richard Bos]

Hi,

Gunnar thanks for your support!

Op Thursday 20 March 2008 16:37:32 schreef u:
> > What I did:
> > - With a small script I verified that the freebusy functionality on kolab
> > worked.  I did that by basically running the following commands:
> >  curl -k https://${_LOGIN_USER}${_PASSWORD}@$SERVER/freebusy/FB
> >
> > where FB has the following values:
> > $FB_USER.ifb
> > $FB_USER.xfb
> > trigger/$FB_USER/Calendar.pfb
> > $FB_USER/Calendar.pfb
> > trigger/$FB_USER/Calendar.xpfb
> > $FB_USER/Calendar.xpfb
> >
> > In all cases kolab provides output, that looks valid.
> >
> > - Configure kontact for another user with kolabwizard.  No errors, all
> > look fine. - Start kontact
> > - Contact the (imap) server
> > - Groupware folders are created
> > - Schedule a meeting, and invite the person that has freebusy information
> >   on kolab (the one checked with the commands listed above).
> > - Go to the free busy tab in the event scheduler / window of korganizer
> > (kontact) Korganizer does not contact the kolab server.  Click on reload
> > nothing happens.  Why not???
> > - Double click the participant, a small window pops up, that can be used
> >   to configure FB information for that participant.
> > - If I fill that window (actually 2 windows), kolab is queried for FB
> > information. The url that I used there is:
> >   https://${_LOGIN_USER}${_PASSWORD}@$SERVER/freebusy/$FB_USER.ifb
> >
> > Is this the way it has been designed?  If not, why does korganizer
> > (kontact) not contact the kolab server automatically (AFAICS korganizer
> > has all the information available to know where the FB data is located).
> >
> > This is with kontact from openSUSE version 1.2.4 (enterprise
> > 20070904.708012) and kolab from cvs, running natively on openSUSE.
> >
> > What behaviour should I expect from kontact / korganizer?
>
> YOu should see the request from kontact in you apache server logs.

I see those request, but not always...
See above when I run my FB test script (please find it attached)), it shows 
the freebusy output and I have the request logged in the apache log.
(Would it be usefull to add it to the kolab-freebusy cvs module?), that 

> I think there are also some good hints on debugging the free/busy system
> in the wiki. Did you check these?

I did not use them, I checked them now.  It seems I have did those checks by 
myself ;)  Anyway, after reading this wiki page:
http://wiki.kolab.org/index.php/Kolab2_Server_Troubleshooting_-_Free/Busy
I still encounter the problem.  It seems I'm at this point:
http://wiki.kolab.org/index.php/Kolab2_Server_Troubleshooting_-_Free/Busy#Kontact
So it looks like a kontact (korganizer) configuration issue:

Just to be sure: Is it sufficient to run kolabwizard for the freebusy 
configuration?  (I assume that it is sufficient to run kolabwizard to fully 
configure kontact and that no more configuration is needed by the user, is 
that correct?)

-- 
Richard Bos
Without a home the journey is endless
-------------- next part --------------
A non-text attachment was scrubbed...
Name: freebusy-test
Type: application/x-shellscript
Size: 1172 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/users/attachments/20080322/832e67b8/attachment.bin>