LOG(L_ERR, "send_presence_notify(): Error while adding headers\n");
str_free_content(&doc);
str_free_content(&content_type);
}
From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of İlker Aktuna (Koç.net)
Sent: Monday, May 08, 2006 12:37 PM
To: Vaclav Kubart
Cc: serusers@lists.iptel.org
Subject: RE: [Serusers] IM and presence problems
From: İlker Aktuna (Koç.net)
Sent: Thursday, May 04, 2006 4:20 PM
To: 'Vaclav Kubart'
Cc: serusers@lists.iptel.org
Subject: RE: [Serusers] IM and presence problems
Hi Vaclav,
I've run with no NAT; ngrep output and ser log
with debug=4 is attached.
You can see that Ser server can ping the contact
address at the end of the ngrep output.
In the debug log I filtered the
process ID 2905 for you. I hope it helps to figure out where the problem
is.
Btw, xcap root does not have any index file. Eyebeam client does not
receive xcap authorization request.
Presentity is not shown
also.
Online IM messages are working but offline messages don't reach
user (maybe it's related).
Today I returned back to the eyebeam 1.1
release and results are the
same.
Thanks,
ilker
-----Original Message-----
From:
Vaclav Kubart [mailto:vaclav.kubart@iptel.org]
Sent:
Thursday, May 04, 2006 3:02 PM
To: İlker Aktuna (Koç.net)
Cc:
serusers@lists.iptel.org
Subject: Re: [Serusers] IM and presence
problems
Hi,
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:
May 2 13:19:51 sesapp /root/ser/sbin/ser[19887]:
DEBUG:tm:t_uac:
next_hop=<sip:200000900568888888@192.168.2.17:26548;transport=udp>
May
2 13:19:51 sesapp /root/ser/sbin/ser[19885]: qm_free(0x8120e80, 0x81703b0),
called from data_lump.c: free_lump_list(409) May 2 13:19:51 sesapp
/root/ser/sbin/ser[19886]: qm_malloc(0x8120e80, 32) called from data_lump.c:
insert_cond_lump_after(216) May 2 13:19:51 sesapp
/root/ser/sbin/ser[19888]: qm_malloc(0x8120e80, 8) returns address 0x81706b8
frag. 0x81706a0 (size=8) on 1 -th hit May 2 13:19:51 sesapp
/root/ser/sbin/ser[19887]: t_uac: no socket found May 2 13:19:51 sesapp
/root/ser/sbin/ser[19887]: t_uac: no socket found May 2 13:19:51 sesapp
/root/ser/sbin/ser[19885]: qm_free: freeing frag. 0x8170398 alloc'ed from
data_lump.c: insert_new_lump_before(140)
In this sample is next_hop
=
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.
The address there
has to be accessible from machine with SER (try to ping the IP).
The
index file is not needed.
And are watchers authorized? (Do they see
status of presentity?)
Vaclav
On Thu, May 04, 2006 at 02:52:39PM +0300, ?lker Aktuna
(Koç.net) wrote:
> Hi Vaclav,
>
> I still couldn't succeed in
presence over SER.
> Still getting following messages, no matter if I'm
behid NAT or not.
> I tested on LAN many times but I still get same error
messages.
>
> Btw, there is no index file in my xcap-root directory.
Should I have something there ?
> I didn't receive any xcap authorization
request after changing xcap
> authorization root to real hostname instead
of 127.0.0.1
>
> May 4 14:42:27 sesapp
/root/ser/sbin/ser[19996]: t_uac: no socket
> found May 4 14:42:27
sesapp /root/ser/sbin/ser[19996]: t_uac: no
> socket found May 4
14:42:27 sesapp /root/ser/sbin/ser[19996]: ERROR:
> notify.c:398: Can't
send watcherinfo notification (-7) May 4 14:42:27
> sesapp
/root/ser/sbin/ser[19996]: ERROR: notify.c:398: Can't send
> watcherinfo
notification (-7) May 4 14:42:27 sesapp
> /root/ser/sbin/ser[19996]:
send_winfo_notify returned -7 May 4
> 14:42:27 sesapp
/root/ser/sbin/ser[19996]: send_winfo_notify returned
>
-7
>
>
> Thanks,
> ilker
>
>
>
-----Original Message-----
> From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org]
>
Sent: Tuesday, May 02, 2006 5:50 PM
> To: ?lker Aktuna (Koç.net)
>
Cc: serusers@lists.iptel.org
> Subject: Re: [Serusers] IM and presence
problems
>
> Try to use nathelper module. I'm not familiar with it
but there exists some documentation for it (in
modules/nathelper/README).
>
>
Vaclav
>
> On Tue, May 02,
2006 at 05:19:10PM +0300, ?lker Aktuna (Koç.net) wrote:
> > Hi
Vaclav,
> >
> > The ngrep.out file was from Friday. And I
realized that I'd changed Eyebeam client configuration after Friday.
>
> Now it sends internal IP as contact. (as in the attached ngrep2.out
>
> file)
> >
> > Now I don't know how to change the contact
as public IP. But
> > presencce messages were not working Friday
also
> >
> > Any idea how to change the contact as public IP
?
> >
> > Thanks,
> > ilker
> >
>
>
> > -----Original Message-----
> > From: Vaclav Kubart
[mailto:vaclav.kubart@iptel.org]
>
> Sent: Tuesday, May 02, 2006 2:56 PM
> > To: ?lker Aktuna
(Koç.net)
> > Cc: serusers@lists.iptel.org
> > Subject: Re:
[Serusers] IM and presence problems
> >
> > > 192.168.2.17
is a NAT client behing 85.105.102.167 Could it be
> > > that the SER
is sending the messages to the internal IP address of my Eyebeam client
?
> >
> > It seems so.
> >
> > > On
eyebeam 1.5 I use the "use rport" option of the client if that matters.
>
> >
> > > Any idea why I get so many "no socket found" errors
? (might it be
> > > because ser is trying to connect to the
internal IP address ?)
> >
> > SER tries to connect to IP
address which is not accessible for it. And it tries again and again...
>
>
> > 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.
> >
> >
Vaclav
> >
> > >
> > > Thanks,
> >
> ilker
> > >
> >
>
