<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>Excuse me ; what works ?<BR>Presence ? Watcherinfo ? Everything
?<BR><BR>What do I need to make Presence work
?<BR><BR>Thanks...<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: Tuesday, May 16, 2006 5:31 PM<BR>To: Vaclav
Kubart<BR>Cc: serusers@lists.iptel.org<BR>Subject: Re: [Serusers] PA error sending
notifies<BR><BR>Blame on me!!!!! It does work!!!!<BR><BR>I was trying several
things and once I saw something like lookup_domain only works on cache mode and
the list was not found but I have just tried and it
works.....<BR><BR>Apologies!!!<BR>Samuel.<BR><BR>2006/5/16, Vaclav Kubart
<vaclav.kubart@iptel.org>:<BR>> This is strange, I try to look on
it.<BR>> I thought, that lookup_user and lookup_domain work with
database<BR>> independently on
usrloc.<BR>><BR>>
Vaclav<BR>><BR>> On Tue, May 16, 2006 at 09:59:10AM +0200, samuel
wrote:<BR>> > There's anothing issue that can be mentioned in the
handbook:<BR>> ><BR>> > using usrloc module with db backend
(db_mode!=0) entails that all<BR>> > lookup_user||lookup_domain calls will
fail and the example configs<BR>> > that appear on the presence
documentation will not offer the<BR>> > expected behaviour...<BR>> >
Another option is to wait until lookup_* functions work with DB
backend...<BR>> ><BR>> > Samuel.<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 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<BR>> > >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 presence<BR>> >
>> staff and I have to say that I have it amost workign thanks to<BR>>
> >> the presence handbook, the mailing list and, obviously, a
little<BR>> > >> 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 have<BR>> > >> an issue when the "presence
server" tries to send the NOTIFY<BR>> > >> requests. Below there's
an attched log showing the problem (on IP<BR>> > >> 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>> > >>
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<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
record<BR>> > >> route should help?<BR>> > >><BR>>
> >><BR>> > >> Samuel.<BR>> > >><BR>> >
>> _______________________________________________<BR>> > >>
Serusers mailing list<BR>> > >> serusers@lists.iptel.org<BR>> >
>> <A
href="http://lists.iptel.org/mailman/listinfo/serusers">http://mail.iptel.org/mailman/listinfo/serusers</A><BR>>
>
><BR>><BR><BR>_______________________________________________<BR>Serusers
mailing list<BR>serusers@lists.iptel.org<BR><A
href="http://lists.iptel.org/mailman/listinfo/serusers">http://mail.iptel.org/mailman/listinfo/serusers</A><BR></FONT></P>
<!--445D5241795C-->
<br><br><a href="http://387555.sigclick.mailinfo.com/sigclick/010D0604/0407490F/07044D03/92511125.jpg"><img src="http://387555.signature1.mailinfo.com/confirm2.6/010D0604/0407490F/07044D03/92511125.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>