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 (
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(a)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
-----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(a)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(a)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(a)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
> > >
<http://387555.sigclick.mailinfo.com/sigclick/07090307/00054905/04084800/14142505.jpg>
_____________________________________________________________________________________________________________________________________________
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.
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.
_____________________________________________________________________________________________________________________________________________