csip loses registration and and does not re-register

[GoogleCodeExporter]

This is really a 

1. Haven't found the exact cause yet but csipsimple loses registration from 
time to time. I noticed that after downloading something from the market or 
going on youtube the app loses registration.

2. Does not re-register after losing registration. When I check the settings. 
It says timeout error. Only way to re-register is to go into settings and 
change something then save again. Could the app not check if it's registered 
and then try to reset the parameters and re-register?

3. Sometimes when on wifi the DSL connection goes down but wifi is still up. In 
this case csip loses the registration but can't re-register on wifi because DSL 
is down. Why not switch to 3g at this point. I.e. have a failsafe registration 
mode. If app can't register or re-register on wifi, try 3g (if allowed) and 
vice versa.

Original issue reported on code.google.com by dcitele...@gmail.com on 7 Sep 2010 at 1:59

[GoogleCodeExporter]

Ooops. Telus HTC with RomVillain 12 (android 2.1) and 12-28 dev version.

Original comment by dcitele...@gmail.com on 7 Sep 2010 at 2:00

[GoogleCodeExporter]

For point 1 : is lock wifi enabled on csipsimple settings?
For point 2 : re-registration is done once directly after the registration loss 
and then each 5 minutes if you are in 'Always available mode' (of course). 
(P.S. : did you try just to deactivate/reactivate account, that's easier than 
going in settings and pressing back (and that only does an unregister while 
settings and back restart all the sip stack).

For point 3: unfortunately, on android, we don't choose which connection type 
we use. And we can't stop wifi. We can know what connection we are currently 
using but that's android os that choose the data connection. (And besides, when 
you are using wifi, 3G is automatically cut => 3G and WIFI can't live at the 
same time). As consequence there is nothing I can do for your issue. But all 
android apps are affected the same way than me : you'll not receive mail, 
you'll not be able to use gtalk...

For point 1 & 2, if you can produce some logs could be interesting for me to 
see exactly what is happening (there is a wiki page about how to produce logs).

Original comment by r3gis...@gmail.com on 7 Sep 2010 at 2:26

[GoogleCodeExporter]

1. Yes. Lock wifi is enabled. 
2. I'll see what I can do about the logs. Enable always on mobile data seems to 
reduce the registration loss. Maybe the re-registration has to be done 
different to overcome the timeout error. 
3. Why can't you stop wifi? There are many apps that do just that. So if you 
are on wifi and the registration fails just switch it off and the phone will 
re-register on 3g. Just a thought.

Original comment by dcitele...@gmail.com on 7 Sep 2010 at 2:54

[GoogleCodeExporter]

3. You're right... But for most users I'm not sure it would be good idea : 
there is users that are not allowed to use 3G for Voip, the problem can come 
from the sip server, if there is another app that is downloading using wifi 
you'll break the download...
So as a default implementation I don't think cutting wifi is a good idea. 
However, it can be envisaged as an option for users (like you) that have an 
unstable wifi connection. But for now I'm more interested in doing it stable at 
least when condition are favorable (and as you noticed that's not always the 
case... the app is still in alpha developement ;) ). Once things will be fine 
when connections are stable, we will be able to build on the top of solid 
foundations.

Original comment by r3gis...@gmail.com on 7 Sep 2010 at 3:28

[GoogleCodeExporter]

I think cutting off wifi on one app's whim is unacceptable.
(But, for those who really need this functionality, they could develop a 
separate application that would periodically check Internet connectivity and 
turn wifi off or on according to some policy.)

Original comment by egcros...@gmail.com on 9 Sep 2010 at 8:00

[GoogleCodeExporter]

If csipsimple is configured to allow incoming calls it has to maintain 
registration 24/7 which means its the primary app on the phone for 
connectivity. If csipsimple is connected via wifi and notices that something is 
wrong with the wifi connection, i.e. the DSL modem has lost DSL and sip loses 
registration then the wifi connection is obviously down and it makes no sense 
to maintain it at that point. You switch to 3g to re-register and check wifi 
every 15 minutes or so if the connection is back up. I don't is this can be 
coded but it's what I do manually when wifi Internet is down. An easy way to 
turn off wifi is the app Quick Settings.

Original comment by dcitele...@gmail.com on 9 Sep 2010 at 10:05

[GoogleCodeExporter]

Actually for point 2 : re-registration is done once directly after the 
registration loss and then each 5 minutes if you are in 'Always available mode'

I believe it would make sense to wait 30 seconds before attempting 
re-registration since I tried manually to deactivate/reactivate account and it 
does not work unless I wait about 30 seconds in between registration attempts.

Original comment by dcitele...@gmail.com on 12 Sep 2010 at 3:24

[GoogleCodeExporter]

i'm experiencing registration loss almost every day, and it's mostly annoying 
bug.
i've csipsimple configured to use wifi on incoming calls.
and sometimes (few times during a working day) it loses the registration, and 
keeps saying, that no network available.
meanwhile, wifi is up, and all other application use it without any visible 
problem.

the matter, is that i haven't found any way to make it connect from the 
csipsimple app.
including reconfiguring network settings, account, kill/restart app and even 
account delete/recreate.

the only way to get it to work - disable wifi (yes, system wide), and turn it 
on again.

i can provide any additional information needed.

this bug is on any version is i can remember and till the nightlies, which i 
now use.
h/w is an HTC Desire, stock ROM, as well as a cyanogen 6, and cm7 dev.

Original comment by mrozents...@gmail.com on 25 Jan 2011 at 2:39

[GoogleCodeExporter]

@mrozents : You should try latest dev version. Things should be really better 
right now. http://nightlies.csipsimple.com/trunk/

Besides if you really want to be always available, in addition to CSipSimple 
settings to have "Lock wifi" (if you have 3g deactivated, it's automatically 
done if you choose "Always Available"); so in addition to that, you should 
change your device wifi sleep policy.
To do so; in *android* settings, in wifi settings, press menu and advanced 
setting. In sleep policy choose "Never".
As consequence even if wifi goes down (and if so CSipSimple release the wifi 
lock to avoid battery drain), the android system will continue to scan and 
retry to connect wifi even if screen is off.

Original comment by r3gis...@gmail.com on 25 Jan 2011 at 5:07

• Changed state: NextRelease

[GoogleCodeExporter]

yes, I use nightly builds and update every day.
also "never" sleep  policy is always set up.

I'm still not sure, what the " lock wifi" option is, so I've just set "always 
available" and will look forward. 

Original comment by mrozents...@gmail.com on 25 Jan 2011 at 5:44

[GoogleCodeExporter]

got twice for these 2 days, and last time on latest #595 build just now.
as always - keep saying no networks available, and only switching wifi "off" 
and "on" on device helps to get it working :(

settings:"always available", not allowed to use mobile.
wifi sleep policy: never.

Original comment by mrozents...@gmail.com on 28 Jan 2011 at 1:22

[GoogleCodeExporter]

well, this problem is due at least not only csipsimple, but also kernel, as it 
seems now.
when i have "network is unavailable" in csipsimple, i also can't make any 
download through a browser.
the downloads app is just stuck, and does nothing in that case.
But just with two exceptions, all other app, sync, browsers, resolve, 
ping/telnet in terminal etc. have an internet access and continue to work just 
fine.

Can I suppose, that csipsimple and downloads app use some api, not as common, 
unlike others do? And which got stuck from time to time in kernel for unknown 
reason.

Original comment by mrozents...@gmail.com on 2 Feb 2011 at 1:32

[GoogleCodeExporter]

below is how it looks in logs:

I/ActivityManager(  165): Starting: Intent { 
act=com.csipsimple.phone.action.DIALER flg=0x10000000 
cmp=com.csipsimple/.ui.SipHomebnds=[0,593][480,689] } from pid -1
I/ActivityManager(  165): No longer want com.tmobile.thememanager (pid 14322): 
hidden #16
E/SIP SRV ( 9989): Not able to start sip stack
I/ActivityManager(  165): Displayed com.csipsimple/.ui.SipHome: +568ms

now things in cm7 nightlies has really changed: it continues to work, and even 
allows you to disable account and reenable it again/ but keeps popping up with 
"no network available"

Original comment by mrozents...@gmail.com on 3 Feb 2011 at 3:24