krunal09 / csipsimple

Automatically exported from code.google.com/p/csipsimple
0 stars 0 forks source link

Stays registered, but misses incoming calls #999

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
I use ViaTalk as my provider, and it will stay registered indefinitely and 
outgoing calls work great, but after about 10 minutes of initial SIP register I 
don't receive incoming calls. 

I thought PBXES would be a fine work around, but for some reason incoming 
callers cannot hear me... what a pickle!

Any help would be greatly appreciated as I love this app, and really want to 
figure out a way to use it permanently. Thanks a million.

-Pete

Original issue reported on code.google.com by numberst...@gmail.com on 28 May 2011 at 2:40

GoogleCodeExporter commented 9 years ago
What device are you using and what version of android it is running?
(Some device has some wifi "PSP" mode which may be the root of this kind of 
problem).

Original comment by r3gis...@gmail.com on 28 May 2011 at 10:38

GoogleCodeExporter commented 9 years ago
Hi,
Thanks for the prompt reply. I am using an HTC Desire running stock froyo. I've 
got it on wifi lock through the app and "never sleep" through froyo.  

Original comment by numberst...@gmail.com on 29 May 2011 at 12:31

GoogleCodeExporter commented 9 years ago
Actually PSP mode is a little bit different of sleep policy mode. That's 
something linked to the driver itself. 
http://code.google.com/p/android/issues/detail?id=9781 .

Normally if you select wifi lock on the app, it's not needed to activate "never 
sleep" (both have the same effect) about the sleep policy. 
Normally lock wifi in csipsimple should be already selected if you have the 
"Always available" option choose and "allowed over 3G" deactivated in "easy 
settings" (the setting panel that also open at very first run). So I guess all 
of that is already fine.
The PSP mode is something else. In fact when the wifi card enter this mode 
packets are received less frequently from the access point. As pointed out by 
the android bug, some driver are buggy and it's not "less frequently" but "not 
at all".

Unfortunately the workaround for that may drain battery faster. I'll introduce 
an option shortly so that you can test and we can determine if it's the cause 
of the problem.

Original comment by r3gis...@gmail.com on 29 May 2011 at 10:54

GoogleCodeExporter commented 9 years ago
Sounds great man, you've done a brilliant job with this app... you continue
to hone it down and refine it. Thanks again.

Original comment by numberst...@gmail.com on 29 May 2011 at 10:28

GoogleCodeExporter commented 9 years ago

Original comment by r3gis...@gmail.com on 21 Jul 2011 at 10:32