Re: [Ekiga-list] [ekiga 3.2.5 on Ubuntu Karmic] "Could not register: sip:foo ekiga net"

[Michael Rickmann <mrickma gwdg de>]

I may be wrong, but when looking at the summary log of Eugene I find two 
different external IPs. 24.151.75.88.in-addr.arpa name = 
dslb-088-075-151-024.pools.arcor-ip.net. and 214.42.223.94.in-addr.arpa 
name = dslb-094-223-042-214.pools.arcor-ip.net. Here in Germany Arcor 
usually sells DSL plus Phone flatrates and has been swallowed by 
Vodafone lately. Could it be that the router is a SIP client itself? If 
so I would move Ekiga to different ports and use port forwarding on the 
router. Eg. in gconf-editor 
>apps>Ekiga>protocols>udp_port_range:5070-5079 and 
...>sip>listen_port:5070. Then set port forwarding on the router for 
these UDP ports to your computer using the same ports for internal and 
external.
Regards
Michael

Eugen Dedu schrieb:
> Damien Sandras wrote:
> > Le lundi 05 octobre 2009 à 13:54 +0200, Eugen Dedu a écrit :
> > > Detlef Lechner wrote:
> > > > Eugen Dedu wrote:
> > > >
> > > > > But I do not understand why you receive this error.  Try restarting
> > > > > ekiga.  
> > > > I did. Always the same result.
> > > >
> > > > > Also, restart ekiga with only ekiga.net account activated, or
> > > > > put it in the second place (after the other account in Account list).
> > > > I did. See the result: http://pastebin.ca/1594263. It's the same as before.
> > > > What should I test next?
> > > I honestly do not know what could be the problem (you receive 606 error
> > > code).  Maybe someone other knows...
> > Probably the NAT router rewrites the packet in a way the SIP proxy does
> > not understand it.
>
> It should be very useful to create a small program, to be put on
> ekiga.net machine when tackling such a problem, which gets just the
> packets with a specified IP as src or dest.  We could very easily see
> where the problem is and we have also a proof about who is responsible.
>
> The program could be very simple, such as tshark (tcpdump) with a filter
> on IP address.