Hi,
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 ?
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 ?)
Thanks,
ilker
-----Original
Message-----
From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org]
Sent:
Tuesday, May 02, 2006 1:34 PM
To: İlker Aktuna (Koç.net)
Cc:
serusers@lists.iptel.org
Subject: Re: [Serusers] IM and presence problems
I
take a look into the log and it seems, that NOTIFY requests try to be sent to
192.168.2.17.
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?
If yes, it means, that there is a
bug in PA module.
Be sure to catch messages on machine with presence
server.
Vaclav
On Tue,
May 02, 2006 at 01:14:37PM +0300, ?lker Aktuna (Koç.net) wrote:
>
Hi,
>
> I've captured debug logs by suggestion of Mr. Michal
Matyska.
> Attached I'm sending them to you. I hope it reaches
you.
> Please look for the "no socket found" and "Can't send watcherinfo
notification " lines in the log as it's too long.
>
>
Thanks,
> ilker
>
> -----Original Message-----
> From:
Vaclav Kubart [mailto:vaclav.kubart@iptel.org]
>
Sent: Tuesday, May 02, 2006 12:28 PM
> To: ?lker Aktuna (Koç.net)
>
Cc: serusers@lists.iptel.org
> Subject: Re: [Serusers] IM and presence
problems
>
> You don't need anything else. Are you sure that changed
config is used by ser (you can try to add a mistake there, if SER will complain
in startup or not)?
>
Vaclav
>
> On Tue, May 02, 2006 at 12:24:59PM +0300, ?lker Aktuna
(Koç.net) wrote:
> > Hi,
> >
> > I changed it to
"debug=4" and restarted ser but nothing changed.
> > Is there anything
missing in my configuration ? Do I need a seperate module for debug messages
?
> >
> > Thanks,
> > ilker
> >
> >
-----Original Message-----
> > From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org]
>
> Sent: Tuesday, May 02, 2006 12:15 PM
> > To: ?lker Aktuna
(Koç.net)
> > Cc: serusers@lists.iptel.org
> > Subject: Re:
[Serusers] IM and presence problems
> >
> > Hi,
> >
debug=4 should be enough. And if you restart ser with this debug level, there
should be really lots of messages in the log.
> >
> > If you
have another proxy doing NAT it is probably not needed to do it on presence
server (and if oter messages work like MESSAGE).
>
> Vaclav
> >
>
> On Tue, May 02, 2006 at 11:39:01AM +0300, ?lker Aktuna (Koç.net)
wrote:
> > > Hi,
> > >
> > > Which level of
debug should I use ?
> > > debug= ? (I tried debug=7 but
nothing changed)
> > >
> > > Btw, my clients are behind
NAT. But I already forward them to an RTP+SIP proxy for voice communication. And
there is no rpoblem with voice.
> > > Should I use any nathelper
configuration for presence messages ?
> > >
> > >
Thanks,
> > > ilker
> > >
> > >
-----Original Message-----
> > > From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org]
>
> > Sent: Tuesday, May 02, 2006 11:23 AM
> > > To: ?lker
Aktuna (Koç.net)
> > > Cc: serusers@lists.iptel.org
> > >
Subject: Re: [Serusers] IM and presence problems
> > >
> >
> I think, that this problem is not caused by absence of unixsock or
unconfigured fifo module.
> > >
> > > Have you restarted
ser after changing debug level (debug=xxx in cfg)?
> > > There
should be lots of messages.
> > >
> >
> Vaclav
> >
>
> > > On Tue, May 02, 2006 at 10:49:22AM +0300, ?lker Aktuna
(Koç.net) wrote:
> > > > Hi,
> > > >
> >
> > Do you think that I need unixsock module ?
> > >
> Also, do I need any configuration for fifo module ?
> > >
>
> > > > I'm now using the CVS version and with full
configuration in the presence handbook.
> > > > Everything seems
to work except presence messages.
> > > >
> > > >
After increasing the loglevel to 7 there is no more information in the
log.
> > > > Only these lines:
> > > >
>
> > > May 2 10:56:49 sesapp /root/ser/sbin/ser[18655]: t_uac:
no
> > > > socket found May 2 10:56:49 sesapp
/root/ser/sbin/ser[18655]: ERROR:
> > > > notify.c:398: Can't
send watcherinfo notification (-7) May 2
> > > > 10:56:49
sesapp /root/ser/sbin/ser[18655]: send_winfo_notify
> > > >
returned -7 May 2
> > > > 10:56:49 sesapp
/root/ser/sbin/ser[18649]: t_uac: no socket
> > > > found
May
> > > > 2 10:56:49 sesapp /root/ser/sbin/ser[18655]: t_uac:
no socket
> > > > found
> > > >
> > >
> If it would help , I can send you my full configuration.
> > >
> I need help desperately.
> > > >
> > > >
Regards,
> > > > ilker
> > >
>
