Status page

[GoogleCodeExporter]

When calling numbers using Sipdroid v. 2.2 on Garmin nüvi A50 connected to 
WiFi, the called person can hear me but I cannot hear the other station. That 
also happens when wifi does not have any firewall enabled.

Unfortunately Sipdroid does not seem to have a status screen where one could 
see what happened, e.g. if the stunning did work and what external ip sipdroid 
found through stunning. Such a status screen is available on all my routers and 
voip boxes from linksys and also in sip clients for windows.

I suggest coders include such a page so that knowledgeable users are enabled to 
communicate more detailed error reports and am prepared to promptly deliver 
more detailed information and testing results.

@pmerle: I suggest to close very old "Issue 2: Can't hear other person"
which started in 2009 and make a newer entry for the new versions of sipdroid.

Original issue reported on code.google.com by tuxoho...@hotmail.de on 17 Jun 2011 at 1:51

[GoogleCodeExporter]

Original comment by pmerl...@googlemail.com on 18 Jun 2011 at 7:30

• Changed title: Status page
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I have the same experience when trying Sipdroid v. 2.2 on my Garmin nüvifone 
A50. 
I can make a call, the phone I call rings, and my voice comes through. But I 
hear nothing incoming at all, not even the ring tone.
It's both when using wifi and 3G, which I guess should rule out router port 
forwarding problems?

I'm no Android nerd(actually just got my phone a couple of days ago), so I 
still have a lot to learn.

Original comment by jensgade...@gmail.com on 20 Jun 2011 at 2:30

[GoogleCodeExporter]

@Jens: you can try to add the nüvifone MAC to your WLAN router's DMZ 
(demilitarized zone) and connect the router to your modem directly. You will 
have no route/port blocking in the DMZ, but the nüvifone user still won't hear 
the person calling while the other person has not problem whatsoever.

So it's complicated, maybe related to not properly working STUN protocol. But 
without a status screen a tester can't give more precise bug reports on what 
goes wrong. Without s status screen testers would have to sniff the 
conversation using wireshark, then filter the data packages, analyze them.

Original comment by tuxoho...@hotmail.de on 28 Jun 2011 at 1:23

[GoogleCodeExporter]

Well, I tried it over 3G, where there shouldn't be a NAT problem, and it was 
the same.

I also tried other SIP VOIP apps, where most of them act the same. But 3CX 
seems to work sound-wise, but then has other problems.

Anyway, I guess I should post this in the old #2 issue, instead of here.

Jens

Original comment by jensgade...@gmail.com on 29 Jun 2011 at 8:02