<HTML >
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-16">
<META HTTP-EQUIV="EXPIRES" CONTENT="0">
<META HTTP-EQUIV="EXPIRESABSOLUTE" CONTENT="Tue, 01 Jun 1999 12:00:00 GMT">
<META HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE">
<META HTTP-EQUIV="CACHE-CONTROL" CONTENT="PRIVATE">
<META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE">
<TITLE></TITLE>
<META content="MSHTML 6.00.2900.2838" name=GENERATOR></HEAD>
<BODY >
<DIV>
<DIV><!-- Converted from text/plain format -->
<P><FONT size=2>Ok, it's not that important. I just wanted to use it because it
was in the example configs.<BR>Usrloc db support is more important for me
now.<BR>Otherwise I can't use lookup_user("To") for user
uri.<BR><BR>Thanks,<BR>ilker<BR><BR><BR>-----Original Message-----<BR>From:
Vaclav Kubart [<A
href="mailto:vaclav.kubart@iptel.org">mailto:vaclav.kubart@iptel.org</A>]<BR>Sent:
Wednesday, May 31, 2006 12:57 PM<BR>To: İlker Aktuna (Koç.net)<BR>Cc: samuel;
serusers@iptel.org<BR>Subject: Re: Authorizing IM requests<BR><BR>The file
format is different! You really CAN NOT set these rules from EyeBeam. The
filename is given as parameter to authorize_message function (in CVS version;
not snapshot).<BR><BR>If you need it quickly you really have to correct it
somewhere in sources (I don't know
where).<BR><BR>
Vaclav<BR> <BR>On Wed, May 31, 2006 at
10:52:42AM +0300, ?lker Aktuna (Koç.net) wrote:<BR>> Hi
Vaclav,<BR>><BR>> On which file does Ser look for when authorizing
messages ?<BR>> According to that maybe I can link privacy-lists file to
im-rules file<BR>> (which Ser looks for) Would that work ?<BR>><BR>>
Usrloc problem is very important for me. Please tell me anything I can<BR>>
do to find out the problem (if there is anything that I can do)<BR>><BR>>
Thanks,<BR>> ilker<BR>><BR>> -----Original Message-----<BR>> From:
Vaclav Kubart [<A
href="mailto:vaclav.kubart@iptel.org">mailto:vaclav.kubart@iptel.org</A>]<BR>>
Sent: Wednesday, May 31, 2006 9:29 AM<BR>> To: ?lker Aktuna (Koç.net)<BR>>
Cc: samuel; serusers@iptel.org<BR>> Subject: Re: Authorizing IM
requests<BR>><BR>> Hi,<BR>> yes I did, but I had
forgotten...<BR>><BR>> You can NOT use EyeBeam to work with message
authorization - it will NEVER set the rules which are needed by SER. You can do
this only manually on XCAP server.<BR>><BR>> I try to look on the userloc
problem, but don't know
when.<BR>><BR>>
Vaclav<BR>><BR>> On Tue, May 30, 2006 at 05:29:27PM +0300, ?lker Aktuna
(Koç.net) wrote:<BR>> > Hi Vaclav,<BR>> ><BR>> > Did you
receive my following email ?<BR>> ><BR>> > Btw, I still couldn't
find the neccessary db structure for using<BR>> > usrloc with db support.
Can you point me to the right person who<BR>> > knows the required db
structure ?<BR>> ><BR>> > Thanks,<BR>> > ilker<BR>>
><BR>> > ________________________________<BR>> ><BR>> >
From: ?lker Aktuna (Koç.net)<BR>> > Sent: Monday, May 29, 2006 12:52
PM<BR>> > To: 'Vaclav Kubart'<BR>> > Cc: samuel;
serusers@iptel.org<BR>> > Subject: RE: Authorizing IM requests<BR>>
><BR>> ><BR>> ><BR>> ><BR>> > Well, then what can I
use in the following line to authorize IM messages ?<BR>> ><BR>> >
if (authorize_message("<A
href="https://sip.koc.net/xcap">https://sip.koc.net/xcap</A>")) {<BR>>
><BR>> > Eyebeam updates file
/xcap/privacy-lists/user/privacy-lists.xml when I change the "privacy"
configuration on Eyebeam client.<BR>> ><BR>> > Thanks,<BR>> >
ilker<BR>> ><BR>> > -----Original Message-----<BR>> > From:
Vaclav Kubart [<A
href="mailto:vaclav.kubart@iptel.org">mailto:vaclav.kubart@iptel.org</A>]<BR>>
> Sent: Friday, May 26, 2006 4:48 PM<BR>> > To: ?lker Aktuna
(Koç.net)<BR>> > Cc: samuel; serusers@iptel.org<BR>> > Subject: Re:
Authorizing IM requests<BR>> ><BR>> > Yes, I meant, that this will
not work together.<BR>> ><BR>> > I don't know. Privacy-lists are
something eyeBeam's internal or something standardized?<BR>> ><BR>>
> Im-rules are SER internal.<BR>> ><BR>>
> Vaclav<BR>>
> <BR>> > On Fri, May 26, 2006 at
04:43:35PM +0300, ?lker Aktuna (Koç.net) wrote:<BR>> > > Do you mean it
won't work with privacy-lists ?<BR>> > > What can I try ?<BR>> >
><BR>> > > Thanks,<BR>> > > ilker<BR>> > ><BR>>
> > -----Original Message-----<BR>> > > From: Vaclav Kubart [<A
href="mailto:vaclav.kubart@iptel.org">mailto:vaclav.kubart@iptel.org</A>]<BR>>
> > Sent: Friday, May 26, 2006 4:40 PM<BR>> > > To: ?lker Aktuna
(Koç.net)<BR>> > > Cc: samuel; serusers@iptel.org<BR>> > >
Subject: Re: Authorizing IM requests<BR>> > ><BR>> > > EyeBeam
won't use im-rules and SER won't use with privacy-lists. It something
else.<BR>> > ><BR>> >
> Vaclav<BR>> >
><BR>> > > On Fri, May 26, 2006 at 02:24:42PM +0300, ?lker Aktuna
(Koç.net) wrote:<BR>> > > > Hi Samuel,<BR>> > >
><BR>> > > > Now that presence is working I'm checking xcap
possibilities.<BR>> > > > I see that IM xcap authorization is not
working.<BR>> > > ><BR>> > > > I don't know what to use
in:<BR>> > > > >if (authorize_message("im-rules.xml")){<BR>>
> > ><BR>> > > > My client (Eyebeam) does not use
im-rules.xml , but it uses<BR>> > > > privacy-lists.xml and that
file is in privacy-lists folder. How<BR>> > > > should I
change the configuration line to use this file ?<BR>> > > ><BR>>
> > > Regards,<BR>> > > > ilker<BR>> > >
><BR>> > > > -----Original Message-----<BR>> > > >
From: samuel [<A
href="mailto:samu60@gmail.com">mailto:samu60@gmail.com</A>]<BR>> > >
> Sent: Tuesday, May 16, 2006 5:26 PM<BR>> > > > To: Vaclav
Kubart<BR>> > > > Cc: ?lker Aktuna (Koç.net);
serusers@iptel.org<BR>> > > > Subject: Re: [Serusers] PA error
sending notifies<BR>> > > ><BR>> > > > 2006/5/16, Vaclav
Kubart <vaclav.kubart@iptel.org>:<BR>> > > > > reply
inline...<BR>> > > > > > If you are using XCAP authentication
for MESSAGEs, there's a<BR>> > > > > > function called
authorize_message that needs to have as<BR>> > > > > >
parameter the file name of the IM ruleset.<BR>> > > > > > For
user sam, in xcap-root/im-rules/users/sam/im-rules.xml<BR>> > > >
> > there are the rules for this function. The XML file is<BR>> >
> > > > similar to the presence-rules but has important
differences<BR>> > > > > > (correct me if I'm wrong,<BR>>
> > > > > Vaclav!!!):<BR>> > > > > > *it only
has a blacklist parameter (no whitelist!!)<BR>> > > > ><BR>>
> > > > It doesn't depend on name of the rule<BR>> > > >
> (blacklist/whitelist/...) it depends on the action (block,<BR>> >
> > > ...). You can have as many rules as you want, but to<BR>> >
> > > explicitly enable something<BR>> > > > >
(whitelist) is needless because MESSSAGEs are allowed by<BR>> > > >
> default (at the end of the presence handbook I tried to<BR>> > >
> > describe im-rules the same way as presence-rules are described in
their draft).<BR>> > > > ><BR>> > > > > > *the
namespace is different (so be carefull in copy&paste<BR>> > > >
> > from the<BR>> > > > > > presence-rules!!!) and, as
Vaclav poitned out "proprietary"<BR>> > > > > > from
iptel.<BR>> > > > ><BR>> > > > > And the action
element name differs: <im-handling> is used<BR>> > > > >
instead of <sub-handling>.<BR>> > > > ><BR>> > >
><BR>> > > > Uops...I haven't noticed :P thanks!<BR>> >
> ><BR>> > > >
> Vaclav<BR>> > >
> ><BR>> > > > > ><BR>> > > > > >
About the structure I have: x86 debian testing. Libraries<BR>> > > >
> > versions I don't know exactly but the ones in the testing<BR>> >
> > > > repository EXCEPT a library which I had to get for
serweb<BR>> > > > > > from the stable version...but it's not
affecting SER part.<BR>> > > > > ><BR>> > > > >
> Samuel.<BR>> > > > > > 2006/5/16, ?lker
Aktuna (Koç. net ) <ilkera@koc.net>:<BR>> > >
> > > ><BR>> > > > > > ><BR>> > > >
> > ><BR>> > > > > > ><BR>> > > > >
> >Hi,<BR>> > > > > > ><BR>> > > > >
> >What did you mean by following:<BR>> > > > > >
><BR>> > > > > > >>Instead of<BR>> > > >
> > >>><BR>> > > > > > >>> if
(authorize_message("<A href="http://localhost/xcap">http://localhost/xcap</A>"))
{<BR>> > > > > > >><BR>> > > > > >
>>there should be<BR>> > > > > > >><BR>> >
> > > > >>if (authorize_message("im-rules.xml")){<BR>> >
> > > > ><BR>> > > > > > >Btw, did you
receive my email with following questions :<BR>> > > > > >
><BR>> > > > > > >>> I have the same problem with
notification and other<BR>> > > > > > >>> presence
messages<BR>> > > > > > >with you.<BR>> > > >
> > >>> Can you tell me which Linux distribution you are using
Ser on ?<BR>> > > > > > >>> Also please include
version numbers for libraries that<BR>> > > > > > >>>
are required by<BR>> > > > > > >Ser.<BR>> > > >
> > >>><BR>> > > > > > >>> I am trying
to find similarities between yours and my ser server.<BR>> > > >
> > ><BR>> > > > > > >Regards,<BR>> > >
> > > >ilker<BR>> > > > > >
><BR>><BR>><BR>><BR>><BR>> <BR>>
<http://387555.sigclick.mailinfo.com/sigclick/06090304/030C4A09/020148<BR>>
03/15141696.jpg><BR>>
______________________________________________________________________<BR>>
______________________________________________________________________<BR>> _
Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor<BR>> olabilir.
Eger bu e-posta mesaji size yanlislikla ulasmissa, icerigini hic bir
sekilde kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta
mesajini kullaniciya hemen geri gonderiniz ve tum kopyalarini mesaj
kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin
cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji
viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici,
bu e-posta mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile -
virus icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak
hicbir sorumlulugu kabul etmez.<BR>> This message is intended solely for the
use of the individual or entity to whom it is addressed , and may contain
confidential information. If you are not the intended recipient of this
message or you receive this mail in error, you should refrain from making any
use of the contents and from opening any attachment. In that case, please notify
the sender immediately and return the message to the sender, then, delete and
destroy all copies. This e-mail message, can not be copied, published or sold
for any reason. This e-mail message has been swept by anti-virus systems for the
presence of computer viruses. In doing so, however, sender cannot
warrant that virus or other forms of data corruption may not be present and do
not take any responsibility in any occurrence.<BR>>
______________________________________________________________________<BR>>
______________________________________________________________________<BR>>
_<BR></FONT></P>
<!--445D5241795C-->
<br><br><a href="http://387555.sigclick.mailinfo.com/sigclick/030A0606/02044D0A/07044D01/20213711.jpg"><img src="http://387555.signature1.mailinfo.com/confirm2.6/030A0606/02044D0A/07044D01/20213711.jpg" border="0" nosend="1"></a><!--445D5241795C//--></DIV>
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">_____________________________________________________________________________________________________________________________________________</DIV>
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu e-posta mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya hemen geri gonderiniz ve tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir sorumlulugu kabul etmez. </DIV>
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">This message is intended solely for the use of the individual or entity to whom it is addressed , and may contain confidential information. If you are not the intended recipient of this message or you receive this mail in error, you should refrain from making any use of the contents and from opening any attachment. In that case, please notify the sender immediately and return the message to the sender, then, delete and destroy all copies. This e-mail message, can not be copied, published or sold for any reason. This e-mail message has been swept by anti-virus systems for the presence of computer viruses. In doing so, however, sender cannot warrant that virus or other forms of data corruption may not be present and do not take any responsibility in any occurrence.</DIV>
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">_____________________________________________________________________________________________________________________________________________</DIV>
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana" ALIGN="justify">
</DIV>
</DIV>
</DIV></DIV>
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">_____________________________________________________________________________________________________________________________________________</DIV>
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu e-posta mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya hemen geri gonderiniz ve tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir sorumlulugu kabul etmez. </DIV>
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">This message is intended solely for the use of the individual or entity to whom it is addressed , and may contain confidential information. If you are not the intended recipient of this message or you receive this mail in error, you should refrain from making any use of the contents and from opening any attachment. In that case, please notify the sender immediately and return the message to the sender, then, delete and destroy all copies. This e-mail message, can not be copied, published or sold for any reason. This e-mail message has been swept by anti-virus systems for the presence of computer viruses. In doing so, however, sender cannot warrant that virus or other forms of data corruption may not be present and do not take any responsibility in any occurrence.</DIV>
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">_____________________________________________________________________________________________________________________________________________</DIV>
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana" ALIGN="justify">
</DIV>
</DIV>
</DIV></BODY></HTML>