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

[Eugen Dedu <Eugen Dedu pu-pm univ-fcomte fr>]

On 19/05/11 22:48, Bart Vandewoestyne wrote:
> On Thu, May 19, 2011 at 09:50:08AM +0200, Bart Vandewoestyne wrote:
> > OK, so if I get things right, there are two possible reasons for
> > me not being able to register with ekiga.net with the native
> > Android 2.3.4 SIP client, namely:
> >
> > 1) it is because the native Android 2.3.4 SIP client does not
> > support a STUN server yet.
> >
> > 2) it is a problem with the ekiga.net server configuration.
> >
> > I would be glad to help out here, but I'm not really sure how I
> > can help.  My educated guess is that I should somehow be able to
> > grab the SIP messages from and to my Android phone, but I have no
> > idea how I can do this.  I have some basic familiarity with
> > wireshark on Linux, but I have never done packet sniffing on an
> > Android phone.
> >
> > If somebody knows, please let me know how I can get to the real
> > SIP-traffic, so we can diagnose this problem more in depth.
>
> OK.  I've played a bit around with tcpdump on my dd-wrt Asus
> RT-N16 router and this is what I did:
>
> * turned off my Android phone
> * issued the following command:
>      root@asus:~# tcpdump -i eth1 host 192.168.1.138 -w sip_capture.pcap
> * turned on my Android phone and played a bit around
> * turned off my android phone
> * CTRL+C the tcpdump command
>
> The output (to be visualised with e.g. wireshark) is here:
>
> http://www.kuleuven-kortrijk.be/~bartv/sip_capture.pcap
>
> All I can see is that the following is happening:
>
> 1) an UDP packet is being sent to ekiga.net
> 2) ekiga.net replies with a SIP message 606 Not Acceptable

There is a problem with your output.  Captured packet is truncated to 62 
bytes, so the full SIP packet is not shown.

Could you retry tcpdump to have full packets in the file?

--
Eugen