freebusy configuration, what is needed in kontact

[Richard Bos]

Hi,

a question about what needs to be configured in kontact to get freebusy working.  

I was investigation today how the kolab's freebusy functionality works in combination
with kontact / korganizer.  In short without additional configuration kolab is not queried
for FreeBusy (FB) information, when a meeting is scheduled with participants.
I'm wondering as this works as expected / designed?  I would expect that _no_ additional
configuration is needed in kontact to obtain FB information, if kontact has been
configured with kolabwizard....

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?


-- 
Richard Bos
Without a home the journey is endless