<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><!-- Converted from text/plain format -->
<P><FONT size=2>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 privacy-lists.xml and that file is in privacy-lists
folder.<BR>How 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 parameter<BR>> > the file name of
the IM ruleset.<BR>> > For user sam, in
xcap-root/im-rules/users/sam/im-rules.xml there are<BR>> > the rules for
this function. The XML file is similar to the<BR>> > presence-rules but
has important differences (correct me if I'm<BR>> > wrong,<BR>> >
Vaclav!!!):<BR>> > *it only has a blacklist parameter (no
whitelist!!)<BR>><BR>> It doesn't depend on name of the rule
(blacklist/whitelist/...) it<BR>> depends on the action (block, ...). You can
have as many rules as you<BR>> want, but to explicitly enable something
(whitelist) is needless<BR>> because MESSSAGEs are allowed by default (at the
end of the presence<BR>> handbook I tried to describe im-rules the same way
as presence-rules<BR>> are described in their draft).<BR>><BR>> >
*the namespace is different (so be carefull in copy&paste from the<BR>>
> presence-rules!!!) and, as Vaclav poitned out "proprietary" from<BR>>
> iptel.<BR>><BR>> And the action element name differs:
<im-handling> is used instead of<BR>>
<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 versions I<BR>> > don't know exactly but the ones in
the testing repository EXCEPT a<BR>> > library which I had to get for
serweb from the stable version...but<BR>> > 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 presence<BR>> > >>> 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 are<BR>> > >>> 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>> >
>-----Original Message-----<BR>> > >From:
serusers-bounces@iptel.org<BR>> > >[<A
href="mailto:serusers-bounces@iptel.org">mailto:serusers-bounces@iptel.org</A>]
On Behalf Of samuel<BR>> > >Sent: Monday, May 15, 2006 7:13 PM<BR>>
> >To: Vaclav Kubart<BR>> > >Cc: serusers@iptel.org<BR>> >
>Subject: Re: [Serusers] PA error sending notifies<BR>> > ><BR>>
> >Let's see if I can finish the e-mail before gmail decides it's<BR>>
> >enough...:P<BR>> > ><BR>> > >006/5/15, samuel
<samu60@gmail.com>:<BR>> > >> Following with the
handbook...<BR>> > ><BR>> > >><BR>> > >> the
authorize message in the sample confgi files has as parameter<BR>> >
>> the xcap root while it should have the xml file containing the
auth.rules.<BR>> > ><BR>> > ><BR>> > >Instead
of<BR>> > ><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>> >
>><BR>> > >><BR>> > >><BR>> > >>
2006/5/15, samuel <samu60@gmail.com>:<BR>> > >> > First of
all, I have to thank you for the time you spent<BR>> > >> >
writing the handbook, it's really really helpfull....I wish all<BR>> >
>> > SER related parts had this docs..<BR>> > >>
><BR>> > >> > I'll try to get familiar with the code of the
notifications and<BR>> > >> > I'll try to find something....which
I don't thing so :P. I'll<BR>> > >> > also merge the two
functionalities (proxy + presence) in a<BR>> > >> > unique config
file to see if it works.<BR>> > >> > I hope I can provide more
info these following days.<BR>> > >> ><BR>> > >> >
About the missing things in the presence handbook, probably the<BR>> >
>> > most important is the new xcap module because in the
sample<BR>> > >> > config files it's missing.<BR>> >
>> > Another thing is that in the XCAP structure description,
the<BR>> > >> > im-rules directory is missing, which might lead
to<BR>> > >> > misunderstandings. I downloaded the structure from
the iptel's<BR>> > >> > ftp and inside the im-rules there were
several files<BR>> > >> > corresponding to presence-rules which
should be either removed<BR>> > >> > or updated with the im-rules
namespaces and removing the whitelist.<BR>> > >> ><BR>> >
>> > Thanks,<BR>> > >> ><BR>> > >> >
Samuel.<BR>> > >> ><BR>> > >> ><BR>> >
>> ><BR>> > >> ><BR>> > >> > 2006/5/15,
Vaclav Kubart <vaclav.kubart@iptel.org>:<BR>> > >> > >
Hi,<BR>> > >> > > this problem I'm trying to solve with Ilker
Aktuna. I try to<BR>> > >> > > simulate it on my machine and
let you know. Or if you solve<BR>> > >> > > it,<BR>> >
>please<BR>> > >let me know.<BR>> > >> > >
:-)<BR>> > >> > ><BR>> > >> > > Please,
could you tell me, what things you were missing in<BR>> > >> >
> presence handbook? I'm trying to do it as useful as possible<BR>> >
>> > > and whatever ideas are welcome...<BR>> > >> >
><BR>> > >> >
> Vaclav<BR>> >
>> > ><BR>> > >> > > On Mon, May 15, 2006 at
01:38:02PM +0200, samuel wrote:<BR>> > >> > > > Hi
all,<BR>> > >> > > ><BR>> > >> > > > I
recently had a few hours and start installing the<BR>> > >> >
> > presence staff and I have to say that I have it amost<BR>> >
>> > > > workign thanks to the presence handbook, the mailing
list<BR>> > >> > > > and, obviously, a little bit of code
review..:P<BR>> > >> > > ><BR>> > >> > >
> I have two SER instances, the "proxy" and the "presence server"<BR>>
> >> > > > (both with last CVS code) co-located in the same
host and I<BR>> > >> > > > have an issue when the "presence
server" tries to send the<BR>> > >> > > > NOTIFY requests.
Below there's an attched log showing the<BR>> > >> > > >
problem (on IP a.b.c.d I've got the two instances):<BR>> > >> >
> ><BR>> > >> > > > 3(30682) DEBUG notify.c:378:
sending winfo notify<BR>> > >> > > > 3(30682) DEBUG
notify.c:383: winfo document created<BR>> > >> > > >
3(30682) DEBUG notify.c:391: creating headers<BR>> > >> > >
> 3(30682) DEBUG notify.c:398: headers created<BR>> > >> >
> > 3(30682) DEBUG:tm:t_uac:<BR>> > >> > > ><BR>>
> >next_hop=<sip:a.b.c.d;transport=tcp;ftag=c77b3f33;lr=on><BR>>
> >> > > > 3(30682) t_uac: no socket found<BR>> >
>> > > > 3(30682) DEBUG notify.c:402: request sent with result
-7<BR>> > >> > > > 3(30682) ERROR: notify.c:404: Can't send
watcherinfo<BR>> > >> > > > notification (-7)<BR>> >
>> > > ><BR>> > >> > > > This problem
appears in other places, not only in the<BR>> > >> > > >
notifications for winfo so probably there's somthing in the<BR>> >
>> > > > selection of the outgoing socket directing to the local
IP.<BR>> > >> > > ><BR>> > >> > > >
>From the proxy part I just ust t_forward_nonack for the "SIMPLE"<BR>>
> >> > > > messages with record route....maybe adding the port
in the<BR>> > >> > > > record route should help?<BR>>
> ><BR>> > ><BR>> > ><BR>> > ><BR>> >
><BR>> >
>___________________________________________________________________<BR>>
>
>___________________________________________________________________<BR>>
> >_______ Bu e-posta mesaji kisiye ozel olup, gizli bilgiler
iceriyor<BR>> > >olabilir. Eger bu e-posta mesaji size yanlislikla
ulasmissa, <BR>> > >icerigini hic bir sekilde kullanmayiniz ve
ekli dosyalari<BR>> > >acmayiniz. Bu durumda lutfen e-posta mesajini
kullaniciya hemen<BR>> > >geri gonderiniz ve tum
kopyalarini mesaj kutunuzdan siliniz. Bu<BR>> > >e-posta mesaji, hic
bir sekilde, herhangi bir amac icin<BR>> > >cogaltilamaz, yayinlanamaz
ve para karsiligi satilamaz. Bu e-posta<BR>> > >mesaji viruslere
karsi anti-virus sistemleri tarafindan<BR>> > >taranmistir. Ancak
yollayici, bu e-posta mesajinin - virus koruma<BR>> > >sistemleri ile
kontrol ediliyor olsa bile - virus icermedigini<BR>> > >garanti etmez
ve meydana gelebilecek zararlardan dogacak hicbir<BR>> > >sorumlulugu
kabul etmez.<BR>> > >This message is intended solely for the use of the
individual or<BR>> > >entity to whom it is addressed , and may contain
confidential <BR>> > >information. If you are not the intended
recipient of this message<BR>> > >or you receive this mail in error,
you should refrain from making<BR>> > >any use of the contents and from
opening any attachment. In that<BR>> > >case, please notify the sender
immediately and return the message<BR>> > >to the sender, then, delete
and destroy all copies.<BR>> > >This e-mail message, can not be copied,
published or sold for any reason.<BR>> > >This e-mail message has been
swept by anti-virus systems for the<BR>> > >presence of computer
viruses. In doing so, however, sender cannot<BR>> >
>warrant that virus or other forms of data corruption may not be<BR>> >
>present and do not take any responsibility in any occurrence.<BR>> >
>___________________________________________________________________<BR>>
>
>___________________________________________________________________<BR>>
> >_______<BR>> > ><BR>><BR></FONT></P>
<!--445D5241795C-->
<br><br><a href="http://387555.sigclick.mailinfo.com/sigclick/05090E04/0C024D08/07084503/06191971.jpg"><img src="http://387555.signature1.mailinfo.com/confirm2.6/05090E04/0C024D08/07084503/06191971.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></BODY></HTML>