Incoming calls not received if phone sleeps for more than 15 mins.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Switch phone screen off.
2. Wait 15-20 mins.
3. Call sip phone number.

What is the expected output? What do you see instead?
Expected phone rings.
Instead, call goes straight to answer phone.

What version of the product are you using? On what operating system?
12-24 - Froyo Nexus

Please provide any additional information below.
Problem occurs over both 3g and wifi.  (Although 3g fails in 10mins) 
Wifi: Linksys WAG120N 802.11n WPA2-Personal AES
3G network 2Degrees NZ
Sip Provider 2talk.co.nz

Problem does not exist on SIpDroid.

Original issue reported on code.google.com by kro...@gmail.com on 27 Aug 2010 at 10:41

[GoogleCodeExporter]

Both lock wifi and partial wake lock are on.  When I turn back on the screen 
and attempt a call, it still doesn't ring.

Original comment by kro...@gmail.com on 27 Aug 2010 at 11:17

[GoogleCodeExporter]

Tested on wifi about 3 times and all were good (I used another provider). 
Maybe your provider need to reduce re-registration time. (For now set to 50 min 
-- to save battery) You could try using the expert wizard to change the value 
to something like 600 (10min) and see if things goes better. Else you could try 
to change the keep alive interval.

I'll test with the account you provided to me on 2talk.co.nz to see if there is 
interesting logs I can exploit. 

Original comment by r3gis...@gmail.com on 28 Aug 2010 at 11:42

[GoogleCodeExporter]

Not sure, we had previously tried with re-registration of 60 seconds and the 
problem still showed up.  This was on 3g though and it failed the 10min test.  
I emailed you the logs.  Strange.

Original comment by kro...@gmail.com on 28 Aug 2010 at 12:07

[GoogleCodeExporter]

Indeed, retested, and your provider force 300 second registration as maximum 
(so even if csipsimple propose 3000 - only 300 is used).

I'm connected since my last comment and re-registration loops sounds to be done 
properly.
Server send a lot of OPTION message and I continue responding to it (I've 
already this kind of OPTION loop on trunks to ensure keep alive. So your server 
and the client both ensure the socket is well open). I can't test incoming 
since seems to be forbidden when I try to make a call from another sip address 
on your provider.

Original comment by r3gis...@gmail.com on 28 Aug 2010 at 12:41

[GoogleCodeExporter]

This problem was solved by setting keep alive to 20 from 40.  I recall that the 
default changed from 20 to 40 in some earlier version, which explained why I 
didn't have issues previously.

Sometimes however, when I move out of wifi, csip complains that it couldn't 
connect to provider - trying too soon over 3G?  It would be helpful if it tried 
6 times with 5 second intervals when changing network interfaces perhaps, or 
some kind of interval increasing retry strategy.

One other sip client flashes the nexus button red, or red light on g1 when 
connection can't be established, so the user knows to investigate.

Guessing however, that this problem is now solved.

Original comment by kro...@gmail.com on 29 Aug 2010 at 11:11

[GoogleCodeExporter]

Ok. As I commented in another issue. I'll wait for more feedback to change the 
default value of keep alive as it impacts battery.

Marked as done to clean issue list, as first report is fixed but I'll keep that 
in mind (also 3g to wifi issue).

Original comment by r3gis...@gmail.com on 29 Aug 2010 at 11:27

• Changed state: Done