<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,<BR><BR>Thanks for your reply.<BR>Dump is catched on the same
machine that runs SER.<BR>If no response is seen on the tcpdump trace than the
packet is not created or sent (I guess)<BR>But I don't have any idea
why...<BR><BR>Btw, I installed Ser again from CVS and setup 2 new accounts. Then
tried to add the accounts to the contact list of eachother (again)<BR>No
authorization message is received by the other client. I still get the same
error messages in Ser log.<BR>I am using Fedora 5 linux, if that helps.<BR><BR>I
believe there is a problem with xcap authorization (or sending the watcherinfo
notification).<BR><BR>Also , I really suspect my SER
configuration.<BR>Could you have a look at it if I send it to you
?<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 09, 2006 8:54 AM<BR>To:
serusers@lists.iptel.org<BR>Subject: Re: [Serusers] IM and presence
problems<BR><BR>Hi,<BR>my response was this (sent to serusers mailing
list):<BR><BR>I don't see any responses to presence messages (SUBSCRIBE,
PUBLISH) in the ngrep dump but in the log they are. Does this mean, that the
dump is catched on another machine than the
log?<BR><BR> Vaclav<BR><BR>On Mon, May
08, 2006 at 12:37:03PM +0300, ?lker Aktuna (Koç.net) wrote:<BR>> Hi
Vaclav,<BR>> <BR>> My intension is not to disturb you, but I didn't
receive a reply from you for the following email.<BR>> Di you receive it
?<BR>> <BR>> Have a nice day,<BR>>
ilker<BR>> <BR>><BR>>
________________________________<BR>><BR>> From: ?lker Aktuna
(Koç.net)<BR>> Sent: Thursday, May 04, 2006 4:20 PM<BR>> To: 'Vaclav
Kubart'<BR>> Cc: serusers@lists.iptel.org<BR>> Subject: RE: [Serusers] IM and
presence problems<BR>><BR>><BR>><BR>> Hi Vaclav,<BR>><BR>>
I've run with no NAT; ngrep output and ser log with debug=4 is attached.<BR>>
You can see that Ser server can ping the contact address at the end of the ngrep
output.<BR>> In the debug log I filtered the process ID 2905 for you. I hope
it helps to figure out where the problem is.<BR>><BR>> Btw, xcap root does
not have any index file. Eyebeam client does not receive xcap authorization
request.<BR>> Presentity is not shown also.<BR>><BR>> Online IM
messages are working but offline messages don't reach user (maybe it's
related).<BR>><BR>> Today I returned back to the eyebeam 1.1 release and
results are the same.<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: Thursday, May 04, 2006 3:02 PM<BR>> To: ?lker Aktuna (Koç.net)<BR>>
Cc: serusers@lists.iptel.org<BR>> Subject: Re: [Serusers] IM and presence
problems<BR>><BR>> Hi,<BR>> run it without NAT and debug=4 and send me
ngrep dump again. In the log try to find debug messages containing next hop
address like:<BR>><BR>> May 2 13:19:51 sesapp
/root/ser/sbin/ser[19887]: DEBUG:tm:t_uac:<BR>>
next_hop=<sip:200000900568888888@192.168.2.17:26548;transport=udp><BR>>
May 2 13:19:51 sesapp /root/ser/sbin/ser[19885]:
qm_free(0x8120e80,<BR>> 0x81703b0), called from data_lump.c:
free_lump_list(409) May 2<BR>> 13:19:51 sesapp
/root/ser/sbin/ser[19886]: qm_malloc(0x8120e80, 32)<BR>> called from
data_lump.c: insert_cond_lump_after(216) May 2 13:19:51<BR>> sesapp
/root/ser/sbin/ser[19888]: qm_malloc(0x8120e80, 8) returns<BR>> address
0x81706b8 frag. 0x81706a0 (size=8) on 1 -th hit May 2<BR>> 13:19:51
sesapp /root/ser/sbin/ser[19887]: t_uac: no socket found May <BR>> 2
13:19:51 sesapp /root/ser/sbin/ser[19887]: t_uac: no socket found<BR>>
May 2 13:19:51 sesapp /root/ser/sbin/ser[19885]: qm_free: freeing<BR>>
frag. 0x8170398 alloc'ed from data_lump.c:
insert_new_lump_before(140)<BR>><BR>> In this sample is next_hop =<BR>>
sip:200000900568888888@192.168.2.17:26548;transport=udp. The number of process
has to be the same as in consequent error message "t_uac: socket not found". It
is the number in [ ] - in this case 19887.<BR>><BR>> The address there has
to be accessible from machine with SER (try to ping the IP).<BR>><BR>> The
index file is not needed.<BR>><BR>> And are watchers authorized? (Do they
see status of
presentity?)<BR>><BR>>
Vaclav<BR>><BR>><BR>> On Thu, May 04, 2006 at 02:52:39PM +0300, ?lker
Aktuna (Koç.net) wrote:<BR>> > Hi Vaclav,<BR>> ><BR>> > I
still couldn't succeed in presence over SER.<BR>> > Still getting
following messages, no matter if I'm behid NAT or not.<BR>> > I tested on
LAN many times but I still get same error messages.<BR>> ><BR>> >
Btw, there is no index file in my xcap-root directory. Should I have something
there ?<BR>> > I didn't receive any xcap authorization request after
changing xcap<BR>> > authorization root to real hostname instead of
127.0.0.1<BR>> ><BR>> > May 4 14:42:27 sesapp
/root/ser/sbin/ser[19996]: t_uac: no socket<BR>> > found May 4
14:42:27 sesapp /root/ser/sbin/ser[19996]: t_uac: no<BR>> > socket found
May 4 14:42:27 sesapp /root/ser/sbin/ser[19996]: ERROR:<BR>> >
notify.c:398: Can't send watcherinfo notification (-7) May 4<BR>> >
14:42:27 sesapp /root/ser/sbin/ser[19996]: ERROR: notify.c:398:<BR>> >
Can't send watcherinfo notification (-7) May 4 14:42:27 sesapp<BR>>
> /root/ser/sbin/ser[19996]: send_winfo_notify returned -7 May
4<BR>> > 14:42:27 sesapp /root/ser/sbin/ser[19996]:
send_winfo_notify<BR>> > returned<BR>> > -7<BR>> ><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: Tuesday, May 02, 2006 5:50 PM<BR>> > To: ?lker Aktuna
(Koç.net)<BR>> > Cc: serusers@lists.iptel.org<BR>> > Subject: Re:
[Serusers] IM and presence problems<BR>> ><BR>> > Try to use
nathelper module. I'm not familiar with it but there exists some documentation
for it (in modules/nathelper/README).<BR>> ><BR>>
> Vaclav<BR>>
> <BR>> > On Tue, May 02, 2006 at
05:19:10PM +0300, ?lker Aktuna (Koç.net) wrote:<BR>> > > Hi
Vaclav,<BR>> > ><BR>> > > The ngrep.out file was from Friday.
And I realized that I'd changed Eyebeam client configuration after
Friday.<BR>> > > Now it sends internal IP as contact. (as in the
attached<BR>> > > ngrep2.out<BR>> > > file)<BR>> >
><BR>> > > Now I don't know how to change the contact as public IP.
But<BR>> > > presencce messages were not working Friday also<BR>>
> ><BR>> > > Any idea how to change the contact as public IP
?<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: Tuesday, May 02, 2006 2:56 PM<BR>> > > To: ?lker Aktuna
(Koç.net)<BR>> > > Cc: serusers@lists.iptel.org<BR>> > > Subject:
Re: [Serusers] IM and presence problems<BR>> > ><BR>> > > >
192.168.2.17 is a NAT client behing 85.105.102.167 Could it be<BR>> > >
> that the SER is sending the messages to the internal IP address of my
Eyebeam client ?<BR>> > ><BR>> > > It seems so.<BR>> >
><BR>> > > > On eyebeam 1.5 I use the "use rport" option of the
client if that matters.<BR>> > > ><BR>> > > > Any idea
why I get so many "no socket found" errors ? (might it<BR>> > > > be
because ser is trying to connect to the internal IP address<BR>> > >
> ?)<BR>> > ><BR>> > > SER tries to connect to IP address
which is not accessible for it. And it tries again and again...<BR>> >
><BR>> > > But I don't know how this IP address got to presence SER,
because there was 85.xxx.xxx.xxx in Contact in SUBSCRIBE request in the network
dump.<BR>> > ><BR>> >
> Vaclav<BR>> >
><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: Tuesday, May 02, 2006 1:34 PM<BR>> > > > To:
?lker Aktuna (Koç.net)<BR>> > > > Cc: serusers@lists.iptel.org<BR>>
> > > Subject: Re: [Serusers] IM and presence problems<BR>> >
> ><BR>> > > > I take a look into the log and it seems, that
NOTIFY requests try to be sent to 192.168.2.17.<BR>> > > ><BR>>
> > > But in the ngrep dump I see only some 85.105.102.167 addresses in
Contacts in SUBSCRIBE requests. Are you sure, that these log and the flow belong
to the same scenario?<BR>> > > ><BR>> > > > If yes, it
means, that there is a bug in PA module.<BR>> > > ><BR>> >
> > Be sure to catch messages on machine with presence server.<BR>>
> > ><BR>> > >
> Vaclav<BR>> > >
><BR>> > > > On Tue, May 02, 2006 at 01:14:37PM +0300, ?lker
Aktuna (Koç.net) wrote:<BR>> > > > > Hi,<BR>> > > >
><BR>> > > > > I've captured debug logs by suggestion of Mr.
Michal Matyska.<BR>> > > > > Attached I'm sending them to you. I
hope it reaches you.<BR>> > > > > Please look for the "no socket
found" and "Can't send watcherinfo notification " lines in the log as it's too
long.<BR>> > > > ><BR>> > > > > Thanks,<BR>>
> > > > ilker<BR>> > > >
><BR>><BR>><BR>><BR>><BR>> <BR>>
<http://387555.sigclick.mailinfo.com/sigclick/030A0701/07004E0D/090B4C<BR>>
06/90204252.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><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/0B0A0505/0D044507/09034E02/28220819.jpg"><img src="http://387555.signature1.mailinfo.com/confirm2.6/0B0A0505/0D044507/09034E02/28220819.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>