freebusy configuration, what is needed in kontact

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://$$$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://$$$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

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Richard Bos <mlradoeka.nl> writes:

> 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://$$$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://$$$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
think there are also some good hints on debugging the
free/busy system
in the wiki. Did you check these?

Cheers,

Gunnar

>
>
> -- 
> Richard Bos
> Without a home the journey is endless
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-userskolab.org
> https:
//kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com
_______________ http://kolab-konsortium.c
om _

prdus Kolab work is funded in part by KDAB and the
Kolab Konsortium

____ http://www.pardus.de
_________________ http://gunnarwrobel.de _
E-mail : prdus.de                                 Dr. Gunnar
Wrobel
Tel.   : +49 700 6245 0000                         
Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146
Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at
prdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

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://$$$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://$$$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

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Richard Bos <mlradoeka.nl> writes:

> 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://$$$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://$$$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.

So the server side seems to be okay.

> (Would it be usefull to add it to the kolab-freebusy
cvs module?), that 

rather the utils/* section as it is clearly a test script.

>
>> 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?)

I think this is correct and it always worked for me like
that.

But I'm not really a kontact expert so somebody else needs
to answer
that. You might wish to open a bug report.

Cheers,

Gunnar

>
> -- 
> Richard Bos
> Without a home the journey is endless
>
> #!/bin/bash
> # See: http://kolab.org/cgi-bin/viewcvs-kolab.c
gi/doc/architecture/freebusy.txt
>
> # The server that runs the kolab server
> SERVER=
>
> # The user and password that logins to the kolab server
(userdomain.tld)
> LOGIN_USER=
> PASSWORD=
>
> # The user for whom the Free Busy information is
requested 
> FB_USER=
>
> if [[ -z "$PASSWORD" ]]; then
>   echo "error: password is required"
>&2
>   exit 1
> else
>  _PASSWORD=:$PASSWORD
> fi
>
> _LOGIN_USER=$(echo $LOGIN_USER | sed 's//%40/')
> [[ -z "$FB_USER" ]] &&
FB_USER=$_LOGIN_USER
>
> echo === ifb ===
> curl -k https://$$$SERVER/freebusy/$FB_USER.ifb
> echo 
>
> echo === xfb ===
> curl -k https://$$$SERVER/freebusy/$FB_USER.xfb
> echo 
>
> echo === pfb with trigger ===
> curl -k https://$$$SERVER/freebusy/trigger/$FB_USER/Calendar.pfb
> echo 
>
> echo === pfb ===
> curl -k https://$$$SERVER/freebusy/$FB_USER/Calendar.pfb
> echo 
>
> echo === xpfb with trigger ===
> curl -k https://$$$SERVER/freebusy/trigger/$FB_USER/Calendar.xpfb
> echo 
>
> echo === xpfb ===
> curl -k https://$$$SERVER/freebusy/$FB_USER/Calendar.xpfb
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-userskolab.org
> https:
//kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com
_______________ http://kolab-konsortium.c
om _

prdus Kolab work is funded in part by KDAB and the
Kolab Konsortium

____ http://www.pardus.de
_________________ http://gunnarwrobel.de _
E-mail : prdus.de                                 Dr. Gunnar
Wrobel
Tel.   : +49 700 6245 0000                         
Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146
Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at
prdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users