Re: [Ekiga-devel-list] Problem with presence

[Eugen Dedu <Eugen Dedu pu-pm univ-fcomte fr>]

Damien Sandras wrote:
> Le vendredi 16 janvier 2009 à 12:01 +0100, Eugen Dedu a écrit :
> > Hi,
> >
> > I have my own name in roster, but I am not seen as available (but as un 
> > unknown contact, a "bonhomme") after connecting to ekiga.net.  Looking 
> > at the output, it seems I receive indeed the event.
>
> Hi,
>
>
> I see no incoming NOTIFY => you publish your state, but you do not
> receive the notification.

Some things intrigues me:

1. When I start ekiga the first time today, presence does not work
2. When I close it and restart, presence works
2'. I close and restart, presence works
3. One minute later, presence does not work again (even restarting)

I saved the -d 4 output.  Doing a grep STUN, it shows that the external 
port changes (5060 and 1024), and that the NAT type is recognized 
differently (Port Restricted and Cone):

for 1.
2009/01/16 11:49:46.717	  0:05.768	StunDetector:0x41a43950	OPAL	STUN 
server "stun.ekiga.net" replies Port Restricted NAT, external IP 
82.238.108.175
2009/01/16 11:49:47.607	  0:06.658	                       	MonSock 
Created bundled UDP socket via STUN, internal=192.168.0.1:5060, 
external=82.238.108.175:5060

for 2.
2009/01/17 10:22:31.164	  0:05.629	StunDetector:0x402bc950	OPAL	STUN 
server "stun.ekiga.net" replies Port Restricted NAT, external IP 
82.238.108.175
2009/01/17 10:22:31.505	  0:05.970	                       	MonSock 
Created bundled UDP socket via STUN, internal=192.168.0.1:5060, 
external=82.238.108.175:1024

for 3.
2009/01/17 10:29:05.647	  0:00.774	StunDetector:0x41506950	OPAL	STUN 
server "stun.ekiga.net" replies Cone NAT, external IP 82.238.108.175
2009/01/17 10:29:06.499	  0:01.626	                       	MonSock 
Created bundled UDP socket via STUN, internal=192.168.0.1:5060, 
external=82.238.108.175:5060

--
Eugen