Registration failed (timeout) - only on some wifi networks

[GoogleCodeExporter]

Sipdroid is configured for gizmo. It appears that on unsecure wifi networks 
it registers OK but on networks with security enabled (WPA2) the client fails 
to register with a timeout error.

What steps will reproduce the problem?
1. Sipdroid 0.9.8 on htc magic with android 1.5
2. Wifi network on linksys wrt610n with WPA2 security
3. Wifi network on Cisco Aironet 1200 with WPA2 securty
4. Sipdroid does not register
5. On android phone change wifi network to open wifi G network (unknown AP 
but displaying SSID of linksys)and sipdroid registers - calls can be made.
6. Gizmo windows client works on laptop on all wifi networks tested

What is the expected output? What do you see instead?
Expect sipdroid to register on wifi network with WPA2 security, networks 
tested so far does not allow this to happen.

What version of the product are you using? On what operating system?
0.9.8 from android market place (also tried full version from sipdroid.org 
with same results)

Please provide any additional information below.
Data services on android phone appear to work as expected on all tested 
wifi networks; only failed application is sipdroid. Client also times out 
when attempting to connect to pbxes.org

Original issue reported on code.google.com by karih...@hotmail.com on 24 Jun 2009 at 2:53

[GoogleCodeExporter]

Different port seems to have helped here. Let's see how it holds up :)

I have a router with an integrated SIP client, so that might be the reason...

Original comment by simonbro...@gmail.com on 14 Sep 2010 at 2:21

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I keep getting "Registration failed (440 not found), I tried switching to UDP 
from TCP, I've tried different ports... no go :( I'm using Droid X (Verizon). I 
was able to connect to my home VOIP service no problem, but not to pbxes.org

Original comment by ale...@gmail.com on 10 Nov 2010 at 8:52

[GoogleCodeExporter]

RCA wifi router sorry didnt get the model put in by brighthouse networks causes 
timeout error. asked to get the netgear wireless router no issue.  today got 
the motorola sbg6580 now have timeout issue.  so this issue is router specific. 
 I disabled all security and turned off firewall.  

Original comment by michaelj...@gmail.com on 19 Nov 2010 at 3:48

[GoogleCodeExporter]

I am having similar problems. I've tried disabling the sip alg, putting the 
phone's ip in the DMZ, removing security from the network, changing ports, tcp, 
udp, different usernames, all to no avail. I can connect on edge, and 3g, but 
not my wifi. 

Original comment by nbouras...@gmail.com on 8 Jan 2011 at 1:22

[GoogleCodeExporter]

This seems to happen to me when the wifi network just hasn't fully connected 
(sipdroid tries to auth too quickly when wifi gets connected).  Manually 
opening sipdroid to initiate another registration with pbxes.org allows it to 
connect.  This is kind of annoying though...as I have to watch my sipdroid 
connection.  A notification when sipdroid fails to connect would be really 
handy.

Original comment by lucky2...@gmail.com on 24 Jan 2011 at 2:10

[GoogleCodeExporter]

I've figured out why Sipdroid wouldn't register for me. If I have any other
phones than Google talk selected inside of Google Voice, sipdroid wouldn't
register on my Desire. So, to use my Google Voice account as a trunk, only
Google Talk may be selected as an active phone. Any ideas on a way around
this?

- Noah

Comment #56 on issue 60 by lucky2...@gmail.com: Registration failed
(timeout) - only on some wifi networks
http://code.google.com/p/sipdroid/issues/detail?id=60

This seems to happen to me when the wifi network just hasn't fully connected
(sipdroid tries to auth too quickly when wifi gets connected).  Manually
opening sipdroid to initiate another registration with pbxes.org allows it
to connect.  This is kind of annoying though...as I have to watch my
sipdroid connection.  A notification when sipdroid fails to connect would be
really handy.

Original comment by nbouras...@gmail.com on 24 Jan 2011 at 11:03

[GoogleCodeExporter]

I am having this same problem on my Comet. At home (WEP and WPA) I can make 
calls just fine. At work, using several different routers (WPA and WPA2) it 
times out. There has to be a work around for this somewhere.  

Original comment by drcame...@gmail.com on 29 Jan 2011 at 12:55

[GoogleCodeExporter]

I just changed the port to 36999 and instantly it connected. Why I don't know, 
but it's connected now.

Original comment by primer...@gmail.com on 1 Feb 2011 at 8:20

[GoogleCodeExporter]

Update to earlier post. I've been using sipdriod 2.0.1 beta Tmobile Comet with 
Froyo. Now my home no longer works. Changing the port to 4500 allowed me to 
connect again at home. Tried it on another public open wifi access point and 
received the same timeout error. Switching ports did not help. I am able to 
connect to wifi at every location I've mentioned in both posts using other 
apps. This is very disappointing. 

Original comment by drcame...@gmail.com on 1 Feb 2011 at 4:26

[GoogleCodeExporter]

Another update. I see this problem only on networks with the login welcome 
screens. My work and the one public wifi I was using had these. For a browser, 
I would open up my home page, see the welcome screen and either login in with 
my credentials or click a terms acceptance button to gain network access. Even 
after this I could not get sipdroid to connect. So far I've been able to 
connect to every other network I've tried that does not have this type of 
welcome screen. Anyone else see this connection? Any thoughts on a workaround. 

Original comment by drcame...@gmail.com on 2 Feb 2011 at 10:53

[GoogleCodeExporter]

Another edit...on some login screen type wifi access points I am able to 
register correctly. I think something may be up with specific router types. 

Original comment by drcame...@gmail.com on 14 Feb 2011 at 11:04

[GoogleCodeExporter]

none of the sip apps including sipdroid seem to work for me on my froyo. 
Connection to my gizmo account through any sip  app gives me timeout error. I 
am trying to connect to proxy01.sipphone.com over secure wifi.  

Original comment by kankeimu...@gmail.com on 21 Feb 2011 at 4:57

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

having the same issue - works on WEP, doesn't work on my work's WPA2 - 802.1x 
EAP 

Original comment by gtitiev...@gmail.com on 7 Mar 2011 at 5:36

[GoogleCodeExporter]

Issue 962 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 9 Sep 2011 at 8:36

[GoogleCodeExporter]

I guess I am having this same issue? Except my wifi router is a 2wire, not a 
linksys or cisco. This is very annoying.

Original comment by Upth...@gmail.com on 24 Dec 2011 at 11:21

[GoogleCodeExporter]

I was getting the same timeout error on my linksys ddwrt610n (WPA 2 Personal).  
I was under the impression that the caller ID field could be changed if desired 
from the default username.  I found that when I changed the "Username or caller 
ID" field, I got the error, when I left it blank to just use the default, my 
phone would connect just fine.

Original comment by iamt...@gmail.com on 1 Jun 2012 at 1:48

[GoogleCodeExporter]

Please forgive me for the sin of necromancy, but I had to thank the last user 
for his suggestion - leave the "username or caller ID" field blank and it 
suddenly works.  In doing so, perhaps another google-er will come across this 
helpful tip.  

Original comment by helpdesk...@gmail.com on 6 Jul 2013 at 4:36