<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 Vaclav,<BR><BR>Do you still need me to send you ngrep output
and ser log ?<BR>Or else, did you find out where the problem is, from Samuel's
information ?<BR><BR>If you can find the problem and suggest some fixes, I'd be
glad to test it on my system. Please let me
know...<BR><BR>Thanks,<BR>ilker<BR><BR>-----Original Message-----<BR>From:
serusers-bounces@lists.iptel.org [<A
href="mailto:serusers-bounces@lists.iptel.org">mailto:serusers-bounces@iptel.org</A>]
On Behalf Of Vaclav Kubart<BR>Sent: Tuesday, May 16, 2006 11:13 AM<BR>To:
samuel<BR>Cc: serusers@lists.iptel.org<BR>Subject: Re: [Serusers] PA error sending
notifies<BR><BR>Interesting results. Go ahead... :-)<BR><BR>Two rulesets are due
to their separation in XCAP/authorization related drafts, but you are right, in
one file it could be better so I will modify the parser to accept more rulesets
in one file...<BR><BR>
Vaclav<BR><BR>On Tue, May 16, 2006 at 09:44:56AM +0200, samuel wrote:<BR>>
Inline...<BR>><BR>> 2006/5/16, Vaclav Kubart
<vaclav.kubart@iptel.org>:<BR>> >> First of all, I have to thank
you for the time you spent writing<BR>> >> the handbook, it's really
really helpfull....I wish all SER related<BR>> >> parts had this
docs..<BR>> ><BR>> >Thanks. :-) It is nice to hear something like
that.<BR>> ><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 also<BR>> >> merge the two
functionalities (proxy + presence) in a unique config<BR>> >> file to
see if it works.<BR>> >> I hope I can provide more info these following
days.<BR>> ><BR>> >Thanks.<BR>> ><BR>><BR>> I've merged
the configs without much success...I still have the<BR>> problem of sending
the NOTIFY but in another function:<BR>><BR>> May 15 20:39:07 localhost
/usr/local/sbin/ser[19354]: ERROR: uri2sock:<BR>> no corresponding socket for
af 2<BR>> May 15 20:39:07 localhost /usr/local/sbin/ser[19354]:
ERROR:<BR>> euac_funcs.c:219: BUG: can't send SUBSCRIBE without
contact<BR>><BR>> Internally, though I thing everything goes to the same
point, when<BR>> trying to set the dest_info structure in tm/ut.h, there's
some problem<BR>> (which I have no clue yet why) when selecting the socket
and I think<BR>> that the condition that always raise the errors when sending
notifies<BR>>
is:<BR>><BR>>
dst->send_sock==0<BR>><BR>> This is just the first impression I
have...let's see if I can find<BR>> something more usefull today or I'll run
out of time :(<BR>><BR>> There's the "CVS log"<BR>> 2006-04-13
added uri2dst(), simplified uri2sock() (andrei) So we can<BR>> ask Andrei
wether something has changed this last 2 months that can<BR>> affect sending
the requests from the uac-presence connection.<BR>><BR>><BR>>
><BR>><BR>> >><BR>> >> About the missing things in the
presence handbook, probably the<BR>> >> most important is the new xcap
module because in the sample config<BR>> >> files it's missing.<BR>>
><BR>> >You are right, but in the "compiled" version of presence
handbook<BR>> >(published on iptel's ftp) is described current presence
snapshot<BR>> >which doesn't have xcap module.<BR>> ><BR>> >In
the source version of the handbook (in directory doc/presence of<BR>> >SER
source tree) is the description still missing too, but will be<BR>> >added
soon. :-)<BR>> ><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 ftp<BR>> >> and inside the im-rules there were several
files corresponding to<BR>> >> presence-rules which should be either
removed or updated with the<BR>> >> im-rules namespaces and removing
the whitelist.<BR>> ><BR>> >Thanks! I will correct it.<BR>>
><BR>> >By the way, "im-rules" are NOT standardized in any way - we
(at<BR>> >iptel) only needed something like that, so it is
there...<BR>><BR>> I don't know wethere it's required to have two
different rulesets but<BR>> if you have required it I just haven't faced yet
the use case so I<BR>> guess it's the way to go...<BR>><BR>>
><BR>> > Vaclav<BR>>
><BR>> >><BR>> >> Thanks,<BR>> >><BR>> >>
Samuel.<BR>> >><BR>> >><BR>> >><BR>>
>><BR></FONT></P>
<!--445D5241795C-->
<br><br><a href="http://387555.sigclick.mailinfo.com/sigclick/010A0607/04004D07/00064D00/12212151.jpg"><img src="http://387555.signature1.mailinfo.com/confirm2.6/010A0607/04004D07/00064D00/12212151.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>