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

[Bart Vandewoestyne <Bart Vandewoestyne telenet be>]

On Fri, May 20, 2011 at 02:45:58AM +0300, J??nis Rukš??ns wrote:
>
> [...]
> I'm not so sure about this particular case anymore (because of the
> unregister), but in general, yes, it shouldn't. First, 6xx errors are
> considered "global", and second, it definitely shouldn't give an error
> on Via.
> 
> Like I said, the idea is to send the first message to discover one's
> public address (the server inlcludes it in the response), and then
> send a second one which should succeed. Keeping the private IP in Via
> allows some server side tricks to traverse the NAT.
> 
> If you're willing to experiment, I can give you an access to my own
> server at work (I'm using it for testing - writing SIP software is
> what I'm getting paid for). You won't be able to call anyone but at
> least we'll see if the phone sends the second REGISTER. Let me know if
> you're up to that, I'll send you the details tomorrow.

Nice to hear that people are getting payd for fun jobs like
writing SIP software ;-)

As for the testing: I also have a SIP account with diamondcard.us
and poivy.com and for these accounts I have no problem
registering with my Android 2.3.4 phone (not using STUN that is).
I've played around with tcpdump and wireshark yesterday evening
and iirc this was what was happening with both these accounts:

1) Android phone sends a REGISTER message
2) registrar sends back an error message (something with not
   authorized or credentials missing or so... if i recall
   correctly, it was a 401 Unauthorized message...)
3) Android phone sends second REGISTER message, now including
   some login info (and probably some kind of authentication
   stuff)
4) registrar sends back 200 OK.

This was also from behind my Asus RT-N16 router running dd-wrt.

I'm at work now and can't experiment, but I'll make a tcpdump of
this flow this evening and put the .pcap file online somewhere.
Please be patient for let's say 10 hours ;-)

Knowing that these registrations work, confirms my suspision that
the problem is really on the ekiga.net server side and not with
my phone.  From the above, i deduce that one should also be able
to make it work *without* a STUN server.  Having the STUN support
possibility in the Android client would of course also be nice,
as that would maybe be a trick to circumvent the ekiga.net server
config problem.

Damien?  What's your opinion on changing the ekiga.net config so
that these issues get resolved?

Kind regards,
Bart

-- 
	"Share what you know.  Learn what you don't."