Incoming calls are not received while phone is suspended/sleeping

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Set up, place and receive calls successfully
2.place phone on charger and wait until it has suspended (more than 5 min)
3.place call from a second phone to sipdroid phone.

What is the expected output? What do you see instead?
expected: phone to ring as when not suspended.
instead:
no reaction at phone, phone call goes to voice mail

What version of the product are you using? On what device/operating system?
latest from market sipdroid on:
cyanogen5.07 on G1
  and
droid w/2.1 update

Which SIP server are you using? What happens with PBXes?
Cisco Callmanager--not exposed to internet!

Which type of network are you using?
internal (802.11g) wifi is all that is available to device. 3g is disabled for 
this test. intent is to use phone with no voice/data plan.

Please provide any additional information below.
have disabled any wifi powermanagement, switched from UDP to TCP--waiting 
further suggestions!

Original issue reported on code.google.com by llath...@gmail.com on 11 Jun 2010 at 9:39

[GoogleCodeExporter]

this is a VERY irritating issue. The product is unusable under wifi

Original comment by skrypko....@gmail.com on 27 Jun 2010 at 4:35

[GoogleCodeExporter]

I found a solution in another bug. go into the phone settings, select wireless, 
then Wifi settings. press the menu key, chose advanced, and change the wifi 
sleep policy to "Never". After that I can leave the phone at my desk for a 
weekend, come back to my desk and call it's extension and it will generally 
ring. 

Maybe someone should mark this in a faq somewhere, since it seems to get lots 
of questions. I searched everywhere I could think of before posting a bug. I 
only thought of looking in closed bugs later. I received the impression from 
the docs that the option in sipdroid "Control Wi-Fo Power" did this!

Original comment by llath...@gmail.com on 27 Jun 2010 at 3:12

[GoogleCodeExporter]

I am also having this issue, but only with wifi.  If I use 3G/TCP, I can 
receive calls when the phone is asleep.  I am on Fido, in Canada.

However, when I use wifi, I never receive calls when the phone is asleep.  I 
have tried the following configurations:  control wifi power on, wifi sleep 
policy never, and both TCP/UDP.  I have also tried with control wifi power off, 
wifi sleep policy never, and TCP/UDP.  I am using PBXes.

The steps I follow are this:
1.  set up sipdroid with PBXes.
2.  sleep the phone
3.  call from another phone -- rings busy after about a 10 second pause
4.  sipdroid does not wake up or indicate an incoming call
5.  manually wake the phone, and after a few seconds it will ring with the 
incoming call, which was already ended

I am using sipdroid 1.5.2 beta on Nexus One Android 2.2.

My workaround, for now, is to just turn off wifi if I don't need it, or when I 
am expecting a call.  The 3G connection works just fine for receiving calls.

I have also tried unchecking "Use WLAN" in sipdroid preferences.  This doesn't 
seem to make any difference.  I was hoping that this would cause sipdroid to 
use the 3G data connection while the rest of the system continued to use wifi.

Original comment by kevin.ch...@gmail.com on 1 Jul 2010 at 5:09

[GoogleCodeExporter]

Issue 536 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 7 Jul 2010 at 8:51

[GoogleCodeExporter]

Hello, I am also on Nexus One 2.2 with sipdroid 1.5.4 and my phone when 
sleeping is not ringing on 3G. I have not tested with wifi.  I'm using Sipgate 
and Sipsorcery instead of PBXes. Also I am using 3G/UDP. I tried using TCP but 
the notification gives me the "yellow" circle instead of "Green". I am able to 
make calls fine on my 3G connection. Anyone have any suggestions?

Original comment by thienpha...@gmail.com on 14 Jul 2010 at 11:07

[GoogleCodeExporter]

Issue 562 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 18 Jul 2010 at 7:25

[GoogleCodeExporter]

Ok, I started to use PBXes in the equation and now Sipdroid rings on incoming 
calls. However, it only rings once on my end. Callers say it rings multiple 
times on their end though. 

Original comment by thienpha...@gmail.com on 18 Jul 2010 at 10:11

[GoogleCodeExporter]

thienpham,

This still prevents of making complete technology (in/out calls) usage.

Original comment by oleg.lei...@gmail.com on 18 Jul 2010 at 10:16

[GoogleCodeExporter]

Oleg,

Have you setup PBXes correctly? 

This is the guide I have used. Its a bit long, but since you are not using 
Sipsorcery or Google Voice just skip down to the part where it says "Next we 
move on to PBXes". Just follow the direction for what do to in PBXes. 

In PBXes you need to create an Extension, a Trunk using your VOIP.ms 
information, and an inbound/outbound route using the VOIP.mxsTrunk you created. 
Then on Sipdroid you sign in with your PBXes Extension you created. PBXes 
allows you to use GSM and Speex audio codecs(lower rate for less lag but still 
good sound) in Sipdroid and since it uses TCP it uses less battery.

Original comment by thienpha...@gmail.com on 18 Jul 2010 at 10:38

[GoogleCodeExporter]

...sorry here is the link for the guide:

http://gurnted.wordpress.com/guides/updated-guide-from-xda/

Original comment by thienpha...@gmail.com on 18 Jul 2010 at 10:39

[GoogleCodeExporter]

thienpham,

Once I have tried to use PBXes as a mediator but something didn't work well 
(caller id or something else, I can't remember exactly) and also I don't really 
like the idea of credentials sharing.

Thanks anyway.

Original comment by oleg.lei...@gmail.com on 19 Jul 2010 at 12:07

[GoogleCodeExporter]

I have the same problem! It makes sipdroid unusuable for me...

Original comment by konradwa...@gmail.com on 13 Sep 2010 at 3:08

[GoogleCodeExporter]

Sipdroid answers calls on wifi
-only for 1 hour.  After that, if it has bee
n unused for 1 hour, it wont answer.

Original comment by reach.me...@gmail.com on 20 Sep 2010 at 4:48

[GoogleCodeExporter]

I am using sipdroid with Google Voice, once the phone goes to sleep for about a 
minute I get no reaction to a call, phone call goes to voice mail.  Works fine 
when phone is active.  I have set the wi-fi to "never" sleep, I have tried the 
"Screen on" option with no success.

What version of the product are you using? On what device/operating system?
latest from market sipdroid on:
cyanogen, myTouch w/2.2 OS

Which SIP server are you using? What happens with PBXes?
myipcomms.net phone #, not using PBXes.

Which type of network are you using?
internal (802.11g) wifi is all that is available to device

Original comment by sab...@gmail.com on 1 Oct 2010 at 6:32

[GoogleCodeExporter]

@sabaij

mine did the same.  the fix for me was to disable 'control wifi power (saves 
power)' which apparently overrides the android setting wi-fi to "never" sleep.

altho I have since switched to cSipSimple seems to sound a lot better with 
googvoice.

Original comment by scott.ed...@gmail.com on 1 Oct 2010 at 6:42

[GoogleCodeExporter]

vibrant echo problem was solved. I was quite happy to think that finally I 
could use Sipdroid. But now this problem. I hope it will be solved soon.

Original comment by furkansa...@gmail.com on 18 Oct 2010 at 5:58

[GoogleCodeExporter]

There is a reported workaround.  I am testing it now but please try this.

Do NOT use the Sipdroid setting "Wireless > Control WiFi Power".  Leave that 
unchecked at all times.  It's broke.

Then go into the phone's native settings, Home > Settings > Wireless & Networks 
> Wi-Fi settings > Menu [Button] > Advanced > Wi-Fi sleep policy > Never.  If 
it's already set to Never then change it, save it, come back and put it to 
Never.  That should keep the Wi-Fi turned on all the time and, thus, able to 
receive SIP calls.

However, there is more to this bug.  According to bug #506 if you change any of 
the Sipdroid network settings (such as "Use Wi-Fi", "Use 3G", or "Control Wi-Fi 
Power") then Sipdroid will annoyingly re-set the Wi-Fi policy back to default, 
meaning, go to sleep (and miss SIP calls).  So, once you set the WiFi sleep 
policy, don't touch the Sipdroid settings.

IMHO, a project admin should merge bugs #354, #506, and #409 into a single 
issue called "Sipdroid Wi-Fi management is broke".  They are all the same basic 
problem, and probably in the same block of code.  Bugs #354 and #506 have both 
been incorrectly marked as "Fixed", and bug #498 has no owner.  This has been 
an open problem since March 2010.

(I'm am going to post this workaround to all three bugs.  I apologize for the 
duplication but I think anyone who Googled and got to any one of those bugs 
would want to have this info.  One commenter wasted a week troubleshooting his 
missed calls due to this issue.)

P.S.> As an aside, I suspect that the 3G network proxies incoming TCP 
connections for the phone.  That's probably why 3G doesn't have this problem.  
And, that's probably why the battery lasts 3x longer with TCP over UDP -- the 
3G network will hold onto an incoming TCP connection on behalf of a phone, wake 
it up from the cell tower, and then forward on the connection.  Wi-Fi routers 
don't do that.

Original comment by dereks...@gmail.com on 20 Dec 2010 at 1:40

[GoogleCodeExporter]

I am using 3G only. Still I am facing the same problem. I am using Mytouch 4g.

It works fine after I configure. After sometime, It stops receiving calls. On 
the top still green light is shown as if it is connected.

I need to manual go to sipdroid and make some changes to make sipdroid receive 
the calls again.

It is very irritating problem.

Original comment by krishnagopal.thogiti on 28 Dec 2010 at 12:19

[GoogleCodeExporter]

I am getting the same problem... trying the work around now... when my phone 
goes to sleep it stops wifi. I can see this because as soon as I wake it up, i 
see the wifi icon re-appear and then i get sipgate's green dot shortly after. 
Sometimes I will have a green dot but calls wont come through at all unless i 
restart sipgate entirely... although this might have to do with something 
completely unrelated...

anyway my setup is GV -> Gizmo -> sipdroid
using TCP, default port, with the workaround fix settings described above.

Original comment by krazyky...@gmail.com on 28 Dec 2010 at 2:42

[GoogleCodeExporter]

Everyone.... Please... Add starmark on the leftside in the issue list.... This 
issue has not been considered seriously as there are no enough stars

Original comment by krishnagopal.thogiti on 28 Dec 2010 at 3:45

[GoogleCodeExporter]

Getting the same problem with Wifi or 3G connection. Tried two different VoIP 
isp; problem still the same. sipdroid 2.0.1 with lg optimus one 2.2 android

Original comment by mauro.to...@gmail.com on 6 Jan 2011 at 1:40

[GoogleCodeExporter]

After cellphone is on standbye on 3G it won't recieve calls from gizmo or any 
SIP service including PBxes. Using Rooted KaosFroyo Droid Eris on Verizon. Wifi 
works fines as long as it is not WPA-EAP.

Original comment by Suvir1...@gmail.com on 8 Feb 2011 at 3:05

[GoogleCodeExporter]

Running Sipdroid 2.1 on HTC Wildfire, Android 2.2.1.  I'm seeing this problem 
too, and the workaround in comment 17 doesn't work for me. Indeed, when I ping 
the phone from my computer, as soon as the screen switches off, pings stop 
being answered, even with WiFi sleep being set to Never.

Original comment by soru...@gmail.com on 5 Mar 2011 at 8:42

[GoogleCodeExporter]

@#23 above:  This is a problem with your phone, and nothing to do with 
Sipdroid.  There were a number of (mostly) HTC phones that did not properly 
honor the WIFI Sleep NEVER setting.  You may be able to get it replaced thru 
HTC.  Friend had similar problem with his Nexus One, but mine worked fine.  
Gingerbread fixed his as well. 

Original comment by scree...@gmail.com on 6 Apr 2011 at 6:02

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

vote for this when you leave a comment so this bug can be fixed

Original comment by chinan...@hotmail.com on 11 May 2011 at 1:42

[GoogleCodeExporter]

Following up my earlier comment (23), with the sleep setting on Never, my 
Wildfire behaves itself after it's seen a power connection since being 
rebooted. It only exhobits the problems I described if I reboot the phone, then 
only until I connect it to the charger.

Original comment by soru...@gmail.com on 11 May 2011 at 2:28

[GoogleCodeExporter]

bump

Original comment by thol...@gmail.com on 9 Jul 2011 at 7:12

[GoogleCodeExporter]

Its not just HTC phones -- same problem with an LG.  

Original comment by mbwdo...@gmail.com on 24 Aug 2011 at 5:02

[GoogleCodeExporter]

Same on the Acer A100 tablet

Original comment by Dan.Qu...@gmail.com on 19 Sep 2011 at 12:01

[GoogleCodeExporter]

Commet #17 solved it for me. This was a huge time waster of a problem until I 
found this solution (the workaround really should be in a prominent place in 
the documentation). This bug is really nasty and should be fixed ASAP. Battery 
life on Android smartphones is only tolerable at the best of times (~24 hours 
for me) and, if using SIP, TCP (that can actually receive calls :-) isn't a 
"nice to have", it is vital. With UDP (and keepalive), my phone wouldn't last 
through a single working day (<14 hours!).

Original comment by o...@ben-kiki.org on 11 Oct 2011 at 7:31

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Just setup SIPdroid and left to do some work after verifying everything worked 
correctly.  Rooted, carrier unlocked SGH-T679 (with no SIM installed) did not 
accept the call when I returned after 2 hours.  I am using PBXes, and WiFi is 
set to never sleep

Original comment by nonoy...@gmail.com on 4 Jan 2012 at 10:53

[GoogleCodeExporter]

That's a hack, but you can install Xabber (for your xampp accounts) and it is 
doing a good job keeping the phone awake making my CSip client work fine :)

Original comment by radek.an...@gmail.com on 5 Jan 2012 at 12:08

[GoogleCodeExporter]

That is certainly one way to go but i would really like to find out why my wifi 
goes to sleep even after specifically telling it not to ever do so. wonder if 
maybe this is an issue with t-mobile's skin

Original comment by nonoy...@gmail.com on 5 Jan 2012 at 12:16

[GoogleCodeExporter]

I just discovered that even though I had originally turned off sipdroid's 
control of wifi it was on again. Iimagine that must have been my mistake 
because now once turned off everthing seems to be working right. It would be 
nice if sipdroid could indeed intelligently control the wifi power like it 
suggests.

Original comment by nonoy...@gmail.com on 5 Jan 2012 at 3:30

[GoogleCodeExporter]

Hi, my phone is a htc desire z also known as T-mobile G2 and I only use 3g with 
TCP and get missed calls because sipdroid never picks up the call and notifies 
me that there is an incoming phone call.  Instead all I get is a missed call 
and voicemail from google voice app.  I don't know how to fix this problem as 
it seems to occur when my phone has been using sipdroid for the entire day or 
has been using it for multiple days and it shows that I am still registered to 
pbxes.org but doesn't pick up the incoming call.  How can i fix this issue?

Original comment by ncassano...@gmail.com on 28 Feb 2012 at 1:12

[GoogleCodeExporter]

I continue to get this error also.

Setup: 
SipDroid 2.7 Release
Android 4.0.4 CM9/AOKP Builds
All are set to Wifi Never Sleep (Post #17 Instructions Executed)
Wifi Power Control in SipDroid Disabled.
GV Settings set to Forward > GTalk ONLY
All are set to IMM79 Build.Prop for integrated SIP also.
Devices are using 5061 for SD and 5060 for ICS Integrated SIP.
PBXes.org Account - 5 Routes
[100, 101, 200, 201, 300]

3 Devices
HTC Incredible - 100 (SD) 101 (ICS Int.)
Samsung Vibrant T959 - 200 (SD) 201 (ICS Int.)
LG G2X P999 - 300 (SD)

I have tried all of these devices with SIM pulled using only WiFi. 
All devices were called while screen was on and wifi active with Success SD.
Internal SIP had mixed results.
All devices were called while screen was off and were slept for approx. 2m 
prior to test call.
All devices failed.

I am using AOKP/JRummy16's TCP Stack Optimization for increased buffer size and 
have suspended Power Collapse behavior on all devices also.

All resultant testing proved to be futile as well; no successful wake-on-call 
was executed. 

As GSM uses a different packet processing stack than SIP achieves over WiFi, is 
this an overall flaw perhaps?

Original comment by jkey...@gmail.com on 4 Aug 2012 at 12:46

[GoogleCodeExporter]

I get this error also.

Setup: Sipdroid 2.7, Android 4.1, Galaxy Nexus GSM, Wifi never sleep, wifi 
Power control disabled, PBXes.org account.

No successful wake up on incoming call either. Outgoing calls fine. Green light 
on.

Why is this still an open issue 2 years after it was first reported here? Just 
wondering.

Thanks,
-Mark

Original comment by intercep...@gmail.com on 13 Aug 2012 at 8:10

[GoogleCodeExporter]

Though the workaround in comment 17 works for me for now, I do believe this 
issue deserves a fix, with so many people spending so much time to look for the 
solution.
Not many know of the Advanced options, and it is not so obvious that you have 
to "change" to Never, even if it is already appearing as set to Never. If I 
hadn't read it here I would have never thought of it, and it this tread does 
not come up so quickly on Google.

Original comment by kli...@gmail.com on 23 Sep 2012 at 11:00

[GoogleCodeExporter]

Agreed! Comment 17 only works some of the time. I still often do not
receive incoming calls when the phone is in sleep mode on wifi.

I've tried setting up two identical sipdroid profiles, except one with udp
for better call quality and one with tcp for longer timeout to receive
incoming calls when the phone is asleep. But that is a hack and probably
uses more battery life.

Please address this issue!

-Mark

Original comment by intercep...@gmail.com on 23 Sep 2012 at 12:57

[GoogleCodeExporter]

Comment 17 does not work for me. Incoming calls are intermittent. Green lights 
all look ok. I'm using a nexus one, with Sipdroid and PBXes.

Still a problem -- let me know if there is a universal fix.

Original comment by sheff...@gmail.com on 16 Oct 2012 at 3:08

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Same issue. Tried all suggestions listed above. NADA! Incoming calls over 3G 
fine.  LG-OV

Original comment by fix4...@gmail.com on 23 Apr 2013 at 12:13

[GoogleCodeExporter]

Well, I've given up on Sipdroid because no one chooses to address issues such 
as this important one which basically makes Sipdroid unusable. I've switched to 
CSipSimple and after some trial and error picking the right codecs and fine 
tuning some of the settings, it works great, over low and high bandwidth 
connections with pbxes.org. CSipSimple answers call over wifi and 3g/4g when 
the phone is in sleep mode, which proves that it is fixable. Until this issue 
is addressed, I'm sticking with CSipSimple.

Original comment by m...@hallidays.me on 23 Apr 2013 at 12:59

[GoogleCodeExporter]

Frankly, Android native integrated sip client is pretty good despite of limited 
configuration ability. 

Original comment by o...@mobbie.net on 23 Apr 2013 at 2:43