9 May
2006
9 May
'06
9:20 a.m.
Hi,
Thanks for your reply.
Dump is catched on the same machine that runs SER.
If no response is seen on the tcpdump trace than the packet is not created or sent (I
guess)
But I don't have any idea why...
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)
No authorization message is received by the other client. I still get the same error
messages in Ser log.
I am using Fedora 5 linux, if that helps.
I believe there is a problem with xcap authorization (or sending the watcherinfo
notification).
Also , I really suspect my SER configuration.
Could you have a look at it if I send it to you ?
Thanks,
ilker
-----Original Message-----
From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of
Vaclav Kubart
Sent: Tuesday, May 09, 2006 8:54 AM
To: serusers(a)lists.iptel.org
Subject: Re: [Serusers] IM and presence problems
Hi,
my response was this (sent to serusers mailing list):
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?
Vaclav
On Mon, May 08, 2006 at 12:37:03PM +0300, ?lker Aktuna (Koç.net) wrote:
Hi Vaclav,
My intension is not to disturb you, but I didn't receive a reply from you for the
following email.
Di you receive it ?
Have a nice day,
ilker
________________________________
From: ?lker Aktuna (Koç.net)
Sent: Thursday, May 04, 2006 4:20 PM
To: 'Vaclav Kubart'
Cc: serusers(a)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(a)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:
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
<http://387555.sigclick.mailinfo.com/sigclick/0B0A0505/0D044507/09034E02/28220819.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.
_____________________________________________________________________________________________________________________________________________
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(a)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(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
> > >
<http://387555.sigclick.mailinfo.com/sigclick/030A0701/07004E0D/090B4C
06/90204252.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.
______________________________________________________________________
______________________________________________________________________
_ 
9 May
9 May
3:32 p.m.
New subject: [Serusers] IM and presence problems
Hi,
main problem is probably sending watchrinfo notification - I think that
eyebeam has its "authorization messages" based on watcherinfo
notifications.
I will take a look into it.
Vaclav
On Tue, May 09, 2006 at 09:20:13AM +0300, ?lker Aktuna (Koç.net) wrote:
Hi,
Thanks for your reply.
Dump is catched on the same machine that runs SER.
If no response is seen on the tcpdump trace than the packet is not created or sent (I
guess)
But I don't have any idea why...
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)
No authorization message is received by the other client. I still get the same error
messages in Ser log.
I am using Fedora 5 linux, if that helps.
I believe there is a problem with xcap authorization (or sending the watcherinfo
notification).
Also , I really suspect my SER configuration.
Could you have a look at it if I send it to you ?
Thanks,
ilker
-----Original Message-----
From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of
Vaclav Kubart
Sent: Tuesday, May 09, 2006 8:54 AM
To: serusers(a)lists.iptel.org
Subject: Re: [Serusers] IM and presence problems
Hi,
my response was this (sent to serusers mailing list):
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?
Vaclav
On Mon, May 08, 2006 at 12:37:03PM +0300, ?lker Aktuna (Koç.net) wrote:
Hi Vaclav,
My intension is not to disturb you, but I didn't receive a reply from you for the
following email.
Di you receive it ?
Have a nice day,
ilker
________________________________
From: ?lker Aktuna (Koç.net)
Sent: Thursday, May 04, 2006 4:20 PM
To: 'Vaclav Kubart'
Cc: serusers(a)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(a)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:
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
<http://387555.sigclick.mailinfo.com/sigclick/0B0A0505/0D044507/09034E02/28220819.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.
_____________________________________________________________________________________________________________________________________________
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(a)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(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
> > >
<http://387555.sigclick.mailinfo.com/sigclick/030A0701/07004E0D/090B4C
06/90204252.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.
______________________________________________________________________
______________________________________________________________________
_
4:02 p.m.
New subject: [Serusers] IM and presence problems
In the config I don't see any problems on the first look; only the port
number in listen addresses - this really works?
Vaclav
On Tue, May 09, 2006 at 02:32:34PM +0200, Vaclav Kubart wrote:
Hi,
main problem is probably sending watchrinfo notification - I think that
eyebeam has its "authorization messages" based on watcherinfo
notifications.
I will take a look into it.
Vaclav
On Tue, May 09, 2006 at 09:20:13AM +0300, ?lker Aktuna (Koç.net) wrote:
Hi,
Thanks for your reply.
Dump is catched on the same machine that runs SER.
If no response is seen on the tcpdump trace than the packet is not created or sent (I
guess)
But I don't have any idea why...
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)
No authorization message is received by the other client. I still get the same error
messages in Ser log.
I am using Fedora 5 linux, if that helps.
I believe there is a problem with xcap authorization (or sending the watcherinfo
notification).
Also , I really suspect my SER configuration.
Could you have a look at it if I send it to you ?
Thanks,
ilker
-----Original Message-----
From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of
Vaclav Kubart
Sent: Tuesday, May 09, 2006 8:54 AM
To: serusers(a)lists.iptel.org
Subject: Re: [Serusers] IM and presence problems
Hi,
my response was this (sent to serusers mailing list):
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?
Vaclav
On Mon, May 08, 2006 at 12:37:03PM +0300, ?lker Aktuna (Koç.net) wrote:
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers Hi Vaclav,
My intension is not to disturb you, but I didn't receive a reply from you for the
following email.
Di you receive it ?
Have a nice day,
ilker
________________________________
From: ?lker Aktuna (Koç.net)
Sent: Thursday, May 04, 2006 4:20 PM
To: 'Vaclav Kubart'
Cc: serusers(a)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(a)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:
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
<http://387555.sigclick.mailinfo.com/sigclick/0B0A0505/0D044507/09034E02/28220819.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.
_____________________________________________________________________________________________________________________________________________
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(a)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(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
> > >
<http://387555.sigclick.mailinfo.com/sigclick/030A0701/07004E0D/090B4C
06/90204252.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.
______________________________________________________________________
______________________________________________________________________
_
6772
days inactive
6772
days old
2 comments
2 participants
participants (2)
-
İlker Aktuna (Koç.net) -
Vaclav Kubart