Re: [Ekiga-list] Is there any registration delay when creating new ekiga.net accounts?

[Federico Tello Gentile <federicotg gmail com>]

El jue, 01-01-2009 a las 14:17 +0100, yannick escribió:
> My guess is the timeout is due to another reason. To know what this
> reason is, we need a debug output from ekiga when this happen; following
> those instructions:
> http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_debug_output_from_Ekiga
> 


I think I got some helpfull output.

I get lots of "No route to host": MonSock Socket read UDP error (113):
No hay ruta hacia el host


This happens when there's no firewall running (i don't have NAT, i have
a public IP, 190.188.x.x). I even had port 5060 open for incoming
connections when the firewall was running.

I get the same message when trying to register unsuccessfully and when
already registered and calling the echo test. This time the ekiga status
bar tell me there's no route to host, not only the debug output.

It is not permanent, sometimes i can call the echo test and even the
call back test.

Maybe my ISP is eating UDP traffic?

Here's the some part of log output.

2009/01/01 16:18:40.554	 33:20.952	 Housekeeper:0x40377950	SIP	Set state
Terminated_Timeout for transaction 26 REGISTER
2009/01/01 16:18:40.554	 33:20.952	 Housekeeper:0x40377950	SIP	Changing
REGISTER handler from Restoring to Unavailable,
target=sip:federico tello gentile ekiga net,
id=f68fbca4-99d6-dd11-9e32-001fd0909998 phenom
2009/01/01 16:18:40.554	 33:20.952	 Housekeeper:0x40377950	SIP	Retrying
REGISTER in 30 seconds.
2009/01/01 16:18:40.557	 33:20.955	Opal Garbage:0x41414950	SIP
Transaction 26 REGISTER destroyed.
2009/01/01 16:19:05.009	 33:45.407	Opal Liste...0x403b8950	MonSock
Socket read UDP error (113): No hay ruta hacia el host
2009/01/01 16:19:05.010	 33:45.408	Opal Liste...0x403b8950	Listen	UDP
read error.
2009/01/01 16:19:05.510	 33:45.908	Opal Liste...0x403b8950	MonSock
Socket read UDP error (113): No hay ruta hacia el host
2009/01/01 16:19:05.510	 33:45.908	Opal Liste...0x403b8950	Listen	UDP
read error.
2009/01/01 16:19:06.509	 33:46.907	Opal Liste...0x403b8950	MonSock
Socket read UDP error (113): No hay ruta hacia el host
2009/01/01 16:19:06.510	 33:46.908	Opal Liste...0x403b8950	Listen	UDP
read error.
2009/01/01 16:19:08.513	 33:48.911	Opal Liste...0x403b8950	MonSock
Socket read UDP error (113): No hay ruta hacia el host
2009/01/01 16:19:08.514	 33:48.912	Opal Liste...0x403b8950	Listen	UDP
read error.
2009/01/01 16:19:10.558	 33:50.956	 Housekeeper:0x40377950	SIP	Starting
REGISTER for binding refresh
2009/01/01 16:19:10.558	 33:50.956	 Housekeeper:0x40377950	SIP	Changing
REGISTER handler from Unavailable to Restoring,
target=sip:federico tello gentile ekiga net,
id=f68fbca4-99d6-dd11-9e32-001fd0909998 phenom
2009/01/01 16:19:10.558	 33:50.956	 Housekeeper:0x40377950	OpalUDP
Writing to interface 0 - "190.188.119.95%eth0"
2009/01/01 16:19:10.754	 33:51.152	 Housekeeper:0x40377950	SIP
Transaction  created.
2009/01/01 16:19:10.756	 33:51.154	 Housekeeper:0x40377950	SIP	Adding
authentication information
2009/01/01 16:19:10.756	 33:51.154	 Housekeeper:0x40377950	DNS	SRV
Lookup ekiga.net service _sip._udp
2009/01/01 16:19:10.778	 33:51.176	 Housekeeper:0x40377950	SIP
Transaction remote address is udp$ekiga.net:5060
2009/01/01 16:19:10.778	 33:51.176	 Housekeeper:0x40377950	SIP	Sending
PDU (722 bytes) to: rem=udp$86.64.162.35:5060,local=udp
$190.188.119.95:5060,if=190.188.119.95%eth0
REGISTER sip:ekiga.net SIP/2.0
CSeq: 27 REGISTER
Via: SIP/2.0/UDP
190.188.119.95:5060;branch=z9hG4bK2441cd5a-9ed6-dd11-9e32-001fd0909998;rport