Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Jānis Rukšāns <thedogfarted gmail com>]

On Wed, May 18, 2011 at 3:46 PM, Bart Vandewoestyne
<Bart Vandewoestyne telenet be> wrote:
> On Wed, May 18, 2011 at 03:35:07PM +0300, J??nis Rukš??ns wrote:
>>
>> Most likely it is neither you nor the Android SIP client. The
>> ekiga.net server has an overly restrictive configuration, which
>> prevents any sufficiently up-to-date SIP client from registering from
>> behind NAT. There have been numerous posts on the list regarding this.
>
> Hmm... having googled around a bit, my guess would rather be that
> i cannot register because the native Android 2.3.4 SIP client
> seems not to support STUN.  Couldn't this be the major problem
> for me not being able to register instead of an 'overly
> restrictive configuration' of the ekiga.net server?
>
> If others agree that this lack of STUN support is most likely the
> reason why my registration fails, then it seems like a good idea
> to vote for

Judging from http://www.onsip.com/blog/leo/2011/01/05/our-evaluation-of-android-gingerbreads-native-sip-calling-with-the-nexus-s
it seems that the Android SIP client is working fine from behind NAT -
the SIP traces show a private IP in Via header, and a public one in
Contact.

Most likely your registration fails because ekiga.net is apparently
configured to require a public IP in both Via and Contact headers. I
cannot be 100% sure without seeing the actual SIP messages, but I
guess a private IP in Via is why your registration fails.

And sending 606 Not Acceptable Anywhere to REGISTER is a violation of
the SIP standard on it's own.

-- 
Ian