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

[Peter Robinson <pbrobinson gmail com>]

>>>> The problem is that your router replaces the public IP address Ekiga
>>>> puts in by a private one due to a bug in the router itself, you can see
>>>> the Ekiga PDUs in the log, they are correct.
>>>> If you disable STUN, perhaps your router will put the public IP address
>>>> in the packets.
>>>>
>>>> What happens is that some dummy routers replace public ip's by private
>>>> ones. That's your case.
>>>
>>> Don't think that's true. As I said, using twinkle behind the NAT with the
>>> same router works perfectly with that provider. So the router couldn't be
>>> the problem here  and it seems that it's indeed a software issue.
>>
>> Please show me a trace of Ekiga with stun disabled and a trace of
>> twinkle so that we can compare both.
>>
>> Btw, I don't understand your reasoning which consists to say that Ekiga
>> puts deliberately private IP addresses in PDUs when the log says no.
>
> 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.

This issue sounds quite familiar to a couple of bugs I've had reported
on F-11 where they are unable to connect to a SIP server where with
previous versions of ekiga they were (in some cases they even went as
far as recompiling ekiga 2 themselves.

Peter