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]

Can you change the security mode of one of your WPA2 APs and verify that this 
is 
related to the security mode?

Original comment by pmerl...@googlemail.com on 24 Jun 2009 at 7:38

[GoogleCodeExporter]

Have almost the same problem Sipdroid 0.9.8 on htc magic with android 1.5
I always getting Registration failed (timeout). I was never able to sign in 
even on
gizmo, pbxes.org

PS. i have tried many networks open and wpa , wpa 2 

Original comment by sree4s...@gmail.com on 24 Jun 2009 at 7:52

[GoogleCodeExporter]

I stepped down the security on one of the access points first to WPA then to no 
security and the client still failed to register so my original thoughts on 
WPA2 are 
not withstanding. 

I have connected successfully to two more public hotspots and used sipdroid 
without 
problem. so it's either my router or ISP. Do you have any ideas on what I can 
check? 

Original comment by karih...@hotmail.com on 25 Jun 2009 at 12:18

[GoogleCodeExporter]

You could try alternate ports.

Original comment by pmerl...@googlemail.com on 25 Jun 2009 at 7:33

[GoogleCodeExporter]

Issue 24 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 25 Jun 2009 at 11:29

[GoogleCodeExporter]

hello i have the same problem.
i have realize a  lot of test with crypt of key (wpa2 wpa open) the problem is 
the
same. and i cannot succeed find the mistake because i cannot see the packet of 
the
answer of voip server with wireshark.

Original comment by romain.h...@gmail.com on 5 Jul 2009 at 12:36

[GoogleCodeExporter]

Searching around the internet I found a few postings that the newer Linksys 
router 
firmware may be part of the issue. one posting suggested from packed traces 
that the 
SIP ACK packed was never relayed back to the local network and hence the 
timeout on 
registration.

In the same thread one person changed the linksys firmware to a version 
supported by 
DD-WRT and the problems went away somewhat supporting the thought that newer 
Linksys 
firmwares may be part of the problem.

Original comment by karih...@hotmail.com on 6 Jul 2009 at 4:06

[GoogleCodeExporter]

I can confirm I have the same problem with a Linksys WRT54GL running Tomato 
(WPA,
WPA2). I have other devices (nokia phone, SIP box) that can connect fine to the 
SIP
server.

Original comment by sirtaj.k...@gmail.com on 6 Jul 2009 at 4:32

[GoogleCodeExporter]

I have the problem with siproid 1.0.1 no matter if trying to connect over 3g or 
over
different wifi-access-points. I always run into a 404 not foudn error.

Original comment by joachim....@gmail.com on 14 Jul 2009 at 11:52

[GoogleCodeExporter]

A recent firmware upgrade for the wrt610n router I have at home added a 
configuration 
switch to enable or disable SIP ALG on the router. With this disabled the 
Sipdroid 
client registers where as before it would timeout.

I still experience the timeout problem on some networks - if SIP ALG is the 
cause of 
this, for consistent operation Sipdroid might need to find a way to deal with 
it on the 
client side as the router appeared to default to SIP ALG being enabled.

Original comment by karih...@hotmail.com on 6 Aug 2009 at 2:19

[GoogleCodeExporter]

Using alternate ports (as suggested above) would also bypass SIP ALG.

SIP ALG is causing problems because it often contains implementation bugs and 
is not 
necessary for PBXes.

Original comment by pmerl...@googlemail.com on 6 Aug 2009 at 3:00

[GoogleCodeExporter]

i have the same problem at HTC Hero i can coonect fine trough a apple airport 
express but not trough linksys wrgt54 even with an open linksys

Original comment by mric...@gmail.com on 12 Aug 2009 at 3:54

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I have the same issue.  Installed SIPdroid, set up a Gizmo5 account, turned on 
Google Voice integration, but the 
SIPdroid cannot register at proxy1.sipphone.com.  Is that the correct address?

Does not work over wifi OR edge (no 3g in this area)

Original comment by kstr...@gmail.com on 23 Aug 2009 at 5:32

[GoogleCodeExporter]

It's not proxy1.sipphone.com it's proxy01.sipphone.com... so that's maybe 
you're problem.

I'm using the right name and I have a timeout issue :(

Original comment by gavin...@gmail.com on 25 Aug 2009 at 10:06

[GoogleCodeExporter]

I had the same issue.
In my case, i modified code. It's just temporary workaround.

in /SipUA/src/org/sipdroid/sipua/SipdroidEngine.java
87   SipStack.transaction_timeout = 300000;// modified 30000 to 300000(enough 
number 
than 30000)

30000 just 30 sec, so i modified it and it's working!!!!

Original comment by overjoo...@gmail.com on 25 Aug 2009 at 11:16

[GoogleCodeExporter]

Using Sipdroid 1.0.5 on CM 4.2 connecting to gizmo5's network, the above fix 
still
does not work.  Now it takes 5 mins to time out, but still times out.  Using the
gizmo5 client on Ubuntu on the same wireless network I have no problems.

Original comment by mber...@gmail.com on 26 Aug 2009 at 7:26

[GoogleCodeExporter]

Update and above:
sipdroid with gizmo5 works fine over 2G (though not usable) and over my home 
wifi. 
Possible issue with how android handles WPA2-EAP since that is what is run at 
school.
(Standard WPA2 at home.)  Should not be a firewall issue since Gizmo client 
runs fine
off my laptop at school.

Original comment by mber...@gmail.com on 27 Aug 2009 at 2:28

[GoogleCodeExporter]

I was able to use sipdroid briefly in conjunction with Gizmo5 and Google Voice 
when I
first installed the software on my G1.  However, I was disconnected while 
trying to
record a new Google Voice voicemail greeting and have not been able to reconnect
since.  My router is a Linksys WRT54G2 Version 1.0 running Linksys firmware 
1.0.04
with WPA2 Personal security set up.  I tried turning off the wireless security 
on the
router and that did not solve my inability to connect (Registration failed:  
Timeout).

Original comment by andrew.r...@gmail.com on 21 Sep 2009 at 4:04

[GoogleCodeExporter]

I installed sipdroid today and set it up with pbxes.org connected to my gizmo 
account. it worked on a couple of test calls with a friend, both for outgoing 
and 
incoming. However, he noticed that my caller id said '00', so i set that in 
sipdroid 
and it failed to connect after that with the timeout error. Removed the caller 
id and 
still no go. Restarted the phone and my WiFi AP, but still no luck. I can 
telnet to 
pbxes.org port 5060 from my computer, so it's not the network at fault. Either 
the 
server is timing out on registration or something broke in the client.

My WiFi AP uses WPA2, but I haven't touched it's config through the entire 
process. 
Going to reinstall sipdroid now -- maybe resetting its settings via that 
process will 
help.

Original comment by jackerhack on 13 Oct 2009 at 7:24

[GoogleCodeExporter]

Just tested: reinstalling (preserving user data) did not help, but uninstalling 
and installing did. I am now 
able to sign on and make SIP calls again.

Original comment by jackerhack on 13 Oct 2009 at 11:00

[GoogleCodeExporter]

I can confirm on the WRT610n router that disabling SIP ALG on the 
Administration page
resolves this issue. ( There may be a similar setting on other LinkSYS routers. 
)

I am using WPA2 and it works fine!

Original comment by lordst...@gmail.com on 14 Oct 2009 at 9:56

[GoogleCodeExporter]

Issue 137 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 3 Nov 2009 at 9:00

[GoogleCodeExporter]

Similar problem here, with a TrendNET TEW-631BRP router. Sometimes it registers,
sometimes it says that it timed out. Most of the time it can't register. Same 
problem
happens with both UDP and TCP, and with punching a hole on my firewall or not.

Original comment by eugeni...@gmail.com on 3 Nov 2009 at 10:47

[GoogleCodeExporter]

I'm also getting timeouts with an AVM FRITZ!Box 7270, firmware 54.04.76, using 
WPA2
and an HTC Hero. Other SIP phones connect fine, including my Gigaset SL75 WLAN.

Original comment by sschuberth on 18 Nov 2009 at 8:36

[GoogleCodeExporter]

why is the priority of this bug set to medium?  It would seem to me that if an 
app
with a dependency on the network doesn't support cisco equipment then it would 
be
pretty imporant :$

Original comment by thehyper...@gmail.com on 19 Nov 2009 at 5:09

[GoogleCodeExporter]

I just fixed this issue for myself. Using a trendnet tew-631brp. Tried setting 
wifi
to open, wep and wpa, and the issue still occurred. Fixed by disabling the sip 
ALG
setting on the firewall itself. Seems weird as my softphone on my laptop worked 
fine
before i changed that, and after i changed it, it still works. so at least i 
have
sipdroid working at home as well!

Original comment by spen...@koshsolutions.com on 2 Dec 2009 at 7:02

[GoogleCodeExporter]

Ok, so this narrows it down. I hope the developer of SIPdroid finds out why this
happens and fixes it. I have the same router btw, so I could test it too.

Original comment by eugeni...@gmail.com on 2 Dec 2009 at 7:06

[GoogleCodeExporter]

Hi, can confirm that with my Linksys WRT610n and an HTC Hero (Android 1.5), I 
had to disable the SIP ALG in 
the Linksys web Administrative interface to make SipDroid work. After doing 
that it worked like a charm. I do use 
WPA2, and didn't have to change that at all.

Original comment by pablo.gu...@gmail.com on 2 Dec 2009 at 10:45

[GoogleCodeExporter]

hello, I have the same problem as many people here. trying to connect from HTC
Dream(1.5) through a Mikrotik (where IP/Firewall/service ports/SIP --> is 
disabled).
Get the "Timeout" error 

Original comment by axelt...@gmail.com on 3 Dec 2009 at 10:53

[GoogleCodeExporter]

Hello,
I have the same problems with the Linksys54G with WPA2 private and TKIP/AES. I 
am
running on Android 1.6 and Sipdroid 2.2beta. I can register fine, and it works 
on 3G
networks. 
ALso I tried it on a different wireless, and that worked as well. That's why I 
found
this posting...Just wanted you guys to know that the problem seems to still be 
there.
I am gonna try OpenWRT or sth like that now

Original comment by philipp....@gmail.com on 18 Dec 2009 at 9:10

[GoogleCodeExporter]

ups, I also made a typo on the sipdroid version there, obviosly I meant 1.2.2! 
I forget to mention that I can succesfully register (only after the update to 
1.2.2),
but I cannot receive calls and or phone out. then the yellow button appears, and
afterwards I get the same "registration failure(timeout)" message as the other 
did ... 

I am sorry for the double post!

Original comment by philipp....@gmail.com on 18 Dec 2009 at 9:19

[GoogleCodeExporter]

works seamless with openWrt! This thread helped a lot in finding the problem,
although my "solution" isn't perfect, but works for me! 

Shiny :) Thanks a lot and keep up the good work!

Original comment by philipp....@gmail.com on 18 Dec 2009 at 11:05

[GoogleCodeExporter]

Hmm, this issue disappeared for me with version 1.2.2, or maybe switching my AP 
from
a hidden SSID to broadcasting the SSID also helped. Anyway, works now for me on 
my
HTC Hero with a FritzBox.

Original comment by sschuberth on 18 Dec 2009 at 11:17

[GoogleCodeExporter]

i have the same problem with the latest sipdroid app with htc hero. Failed to
registered time out error. after reading thru this thread, I decided to change 
the
protocol from UDP to TCP. I am not sure what happen but it worked. it registered
fine. I then changed the port numbers from 5060 to something else to make sure 
tha
tmy router has no conflict and compatibility problem with it and all is good. 
now i
can make calls from wifi or 3g. thanks everyone for your contributions to this 
thread.

Original comment by tksentro...@gmail.com on 19 Dec 2009 at 8:13

[GoogleCodeExporter]

is everyone totally sure that the problem here is the type of router you're 
trying 
to connect to?  I have a suspicion that the reason that sipdroid times out is 
because pbxes.org's security certificate is not known as a trusted certificate 
by 
the android web browser.  Think about it:  sipdroid contacts pbxes.org and what 
you 
dont see is the popup asking if you should 'continue to the site anyway'.  
Eventually it times out because it got no additional input.

I can confirm that from the US the steel and dolphin browsers get cranky when 
you 
try to reach pbxes.org, or www4.pbxes.com, because the certificate is not 
signed by 
a trusted source. I cant figure out how to add this site to my trusted zones 
like 
you can with windows.  I dont know if that's an option on android web settings. 

Original comment by thehyper...@gmail.com on 15 Jan 2010 at 6:13

[GoogleCodeExporter]

>the problem here is the type of router you're trying to connect to?

Yes, it has nothing to do with pbexes, since I don't use pbexes, I'm trying to
connect to gizmo.

Original comment by eugeni...@gmail.com on 15 Jan 2010 at 7:15

[GoogleCodeExporter]

I have a linksys wrt610n also but I don't see anywhere in the settings to 
disable the 
sip alg???? I've searched over the setting a 100 times and can't find it???

Original comment by jackson...@gmail.com on 18 Jan 2010 at 8:39

[GoogleCodeExporter]

Sorry never mind the above post... I updated my firmware and found it.... and 
that was definitely the problem.  Now by disabling the sip alg it works 
flawless now, thanks all 
who discovered that.

Original comment by jackson...@gmail.com on 18 Jan 2010 at 9:25

[GoogleCodeExporter]

Try to setup the Sipdroid device IP into the DMZ setting (expose the device to 
Internet) on your router.

I did not have problem with login timeout but I had a problem with "dialing" -> 
"in 
call" status change. Even if I already heard some voice from the other site, 
the 
call was still in the "dialing" status. It happened only on my home wifi 
connection. 
I have discovered it in the Security log of the router where was the following 
message:

SIP PKT: Failed parsing. Error code: -1019

I have fixed it by exposing the Sipdroid device to the Internet by passing its 
IP 
into the DMZ.

I still don't know if it is my router misconfiguration or if Sipdroid is 
sending 
some wrong packets, but it is working now with the DMZ trick.

Original comment by jiri....@gmail.com on 7 Mar 2010 at 7:42

[GoogleCodeExporter]

Hi, Am using a Netgear DG834G. does anyone know if these suffer the same 
problems? I'm 
also getting the timeout error.

Original comment by gprigg...@gmail.com on 30 Mar 2010 at 11:16

[GoogleCodeExporter]

Issue 450 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 6 May 2010 at 3:40

[GoogleCodeExporter]

Hi

couldn't get this to work in my NAT - using sipagent now which works with my 
sip provider without problems, no STUN, no special routing.

Cheers
Nils

Original comment by nils.me...@gmail.com on 13 Jun 2010 at 1:25

[GoogleCodeExporter]

I had the same problem, worked on one firmware and not on another one.

I found that using the IP address of the SIP server worked on the firmware 
which would not register but gave the OP's error message. Perhaps its a more 
fundamental issue with DNS, or just a coincidence..?

Original comment by andydi...@gmail.com on 13 Jun 2010 at 7:57

[GoogleCodeExporter]

I was having the same problem and I think it's a DNS issue too. If I change the 
server to the IP address and set the domain to the server hostname, it works 
instantly. However, I can ping the host normally via the ping application. Hope 
this helps someone!

Original comment by tim.st...@gmail.com on 25 Jun 2010 at 5:43

[GoogleCodeExporter]

I have the same issue. I cant seem to register my EVO on sipdroid. It says 
times out. I have been trying to set up my sipgate and sipsorcery along with 
sip droid, but the sipdroid fails to confirm my account...

Original comment by mishmiami on 22 Jul 2010 at 12:46

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Ya i have the same problem. Mine doesnt work on 3g nor wifi. I have tried using 
gizmo5 ip address. Tried using my phone number as my username. Tried different 
port. Tried tcp. Fails everytime

Original comment by thegreys...@gmail.com on 5 Aug 2010 at 4:02

[GoogleCodeExporter]

So i finally got it to work, but I have to switch been tcp and udp. Any one 
else have that issue?

Original comment by thegreys...@gmail.com on 7 Aug 2010 at 2:00

[GoogleCodeExporter]

[deleted comment]