Re: [Ekiga-devel-list] alien registrar problem

[Christian Schäfer <schaefec googlemail com>]

Michael Rickmann wrote:
> > Again, to clearify my reasoning, these are the relevant observations:
> >
> > Firstly:
> > Relevant -d 4 output of ekiga says the following when trying to 
> > connect to bluesip.net:
> >
> > rem=udp$217.74.179.29:5060,local=udp$96.232.27.238:5060,if=192.168.1.36%wlan0 
> >
> > SIP/2.0 479 Please don't use private IP addresses
> >
> > This suggests that there's a problem with the private IP address 
> > (192.168.1.36). Whether this is sip conform or not I dodn't know. 
> > Concerning to some people in some voip forums, it isn't.
> >
> > Secondly:
> > This behavior is independent of using a STUN server or not and only 
> > appears when I am behind a NAT router.
> >
> > And thirdly:
> > The fact that twinkle is able to connect to bluesip successfully from 
> > behind this specific router, suggests that this is no router-issue.
> >
> > Detailed traces of both ekiga and twinkle will follow.
> >
> > Chris
> Hi, I think a -d 4 trace and something from twinkle might really help 
> Ekiga. When I tried from a machine with official internet access the 
> line containing your rem=.. contained 
> rem=udp$212.227.15.231:5060,local=udp$134.76.145.30:5060,if=134.76.145.30%eth0 
>
> but a few lines up:
> Contact: <sip:495512963297 134 76 145 30>;q=1, 
> <sip:495512963297 192 168 21 30>;q=0.500 because the machine had a 
> second interface to a local network.
> result from sip.1und1.de: SIP/2.0 403 Keine RFC1918-IPs erlaubt

OK, here are the logs, one with STUN acivated and one without:
http://home.in.tum.de/~schaefer/ekiga/
Hope that helps and clarifies things.

Don't know however how to produce a twinkle trace. Something from 
tcpdump or wireshark? Let me know.

Chris