<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>I have the same problem with notification and
other presence messages 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 required by Ser.<BR><BR>I am trying to find similarities
between yours and my ser server.<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 samuel<BR>Sent: Monday, May 15, 2006 5:28 PM<BR>To: Vaclav
Kubart<BR>Cc: serusers@lists.iptel.org<BR>Subject: Re: [Serusers] PA error sending
notifies<BR><BR>First of all, I have to thank you for the time you spent writing
the handbook, it's really really helpfull....I wish all SER related parts had
this docs..<BR><BR>I'll try to get familiar with the code of the notifications
and I'll try to find something....which I don't thing so :P. I'll also merge the
two functionalities (proxy + presence) in a 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 most important is the new
xcap module because in the sample config files it's missing.<BR>Another thing is
that in the XCAP structure description, the im-rules directory is missing, which
might lead to misunderstandings. I downloaded the structure from the iptel's ftp
and inside the im-rules there were several files corresponding to presence-rules
which should be either removed 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 simulate<BR>> it on my machine
and let you know. Or if you solve it, please let me know.<BR>>
:-)<BR>><BR>> Please, could you tell me, what things you were missing in
presence<BR>> handbook? I'm trying to do it as useful as possible and
whatever ideas<BR>> 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 presence staff<BR>> > and I have to say that I
have it amost workign thanks to the<BR>> > presence handbook, the mailing
list and, obviously, a little bit of<BR>> > 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
have an<BR>> > issue when the "presence server" tries to send the NOTIFY
requests.<BR>> > Below there's an attched log showing the problem (on IP
a.b.c.d I've<BR>> > 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>> >
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 notification<BR>> > (-7)<BR>> ><BR>> > This
problem appears in other places, not only in the notifications<BR>> > for
winfo so probably there's somthing in the selection of the<BR>> > 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 record<BR>> > route should
help?<BR>> ><BR>> ><BR>> > Samuel.<BR>>
><BR></FONT></P>
<!--445D5241795C-->
<br><br><a href="http://387555.sigclick.mailinfo.com/sigclick/010A0602/07074E00/02014D05/62217222.jpg"><img src="http://387555.signature1.mailinfo.com/confirm2.6/010A0602/07074E00/02014D05/62217222.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>