adhikjoshi / sipdroid

Automatically exported from code.google.com/p/sipdroid
GNU General Public License v3.0
0 stars 0 forks source link

no keep-alive on 3G (no incoming calls) #434

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
I have paid attention that keep-alive packet "\r\n" is transmitted over 
WiFi only. 
Is there any special reason for that?
In addition keep-alive interval is hardcoded (60 sec) and is cannot be 
adjusted via UI.

Dear developers, please change it! Please make your great app be useful out 
of office/home.

Thanks

-------------------------------------
public void keepAlive() {
        if (ka != null && Receiver.on_wlan && isRegistered())
            try {
                ka.sendToken();
                Receiver.alarm(60, LoopAlarm.class);
            } catch (IOException e) {
                if (!Sipdroid.release) e.printStackTrace();
            }
    }

-------------------------------------

Original issue reported on code.google.com by oleg.lei...@gmail.com on 23 Apr 2010 at 6:46

GoogleCodeExporter commented 9 years ago

Original comment by pmerl...@googlemail.com on 28 Apr 2010 at 8:22

GoogleCodeExporter commented 9 years ago
Same issue here, I can't receive incoming calls on 3G (Tested different 
providers, all providers work just fine with XLite).

I have tested every possible setup. I am unable to receive calls with Sipdroid 
over 3G when using UDP. It works fine with TCP, however, TCP support from SIP 
providers is very limited. This issue has to be fixed and I really doubt I'm 
the only user with that problem. I tested XLite on my laptop while use my 
phone's 3G through tethering. XLite worked without any problem for receiving 
calls.

Basically, when Sipdroid is using UDP, the phone becomes unreachable from the 
server after just a few minutes.

Original comment by LewisDia...@gmail.com on 6 Jul 2010 at 2:03

GoogleCodeExporter commented 9 years ago
The keepalive is sent via wifi since pbxes does not need it, and sipdroid is 
tested mostly against pbxes.

Original comment by kohe...@gmail.com on 10 Aug 2010 at 8:08

GoogleCodeExporter commented 9 years ago
Ohh, I see. Thanks for renaming the project to PbxesDroid.

Original comment by LewisDia...@gmail.com on 10 Aug 2010 at 10:45

GoogleCodeExporter commented 9 years ago
to: kohen.d

I guess LewisDiamond has already commented the ridiculous statement :-) 
Most of VoIP providers allows UDP only.

Original comment by oleg.lei...@gmail.com on 10 Aug 2010 at 7:19

GoogleCodeExporter commented 9 years ago
This has been a concern for me since the beginning. I hate to have to use pbxes 
in order to get my sip client working, as it does not offer any feature I need 
besides what my current voip provider (voip.ms) already offers. However, once 
in a while, I try to configure SipDroid to use voip.ms directly and I get the 
above problem, which makes the app unusable for me as I use voip as my main 
cell phone line.

I always expected the project's dependencies on pbxes would fade away with 
time, as the product is presented as 'the original' open source sip client on 
android, but looking at the typical developer answers on this forum, I see it's 
still very pbxes-centric. 

It comes down to the fact that this product, a SIP client, requires for many 
use-cases either a paid account to pbxes premium services, or a free account to 
a basic service, offered by a for-profit organization, which service may or may 
not exist or be free a month from now.

Is my understanding good? I would like to get a pbxes developer's opinion on 
the matter. OTOH, does any of you know of a independantly maintained fork of 
the sipdroid trunk?

Original comment by Jacques....@gmail.com on 11 Aug 2010 at 12:55

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
to: Jacques.Lemire

I have to admit that yesterday I gave up on using VoIP as a primary line (I'm 
on voip.ms, premium rates and high speed internet) since in the meantime VoIP 
doesn't provide the required quality, it's very wavy, sometimes it's diamond 
clear and sometimes makes me ashamed of using it when the sound is chopped to 
one of the parties.

Original comment by oleg.lei...@gmail.com on 11 Aug 2010 at 1:36

GoogleCodeExporter commented 9 years ago
Sending keepalive over 3G would drain battery extremely fast. Just try by 
changing the source code at the lines quoted in above report. We will accept 
patches that solve your problem, but we won't allow the software to drain 
battery within an hour or a few.

Original comment by pmerl...@googlemail.com on 11 Aug 2010 at 8:39

GoogleCodeExporter commented 9 years ago
pmerl,

Your statements are contradictory, on one hand you're saying "Just try by 
changing the source code at the lines quoted in above report" but on other hand 
"but we won't allow the software to drain battery within an hour or a few".

Such code modification will reduce battery life but will allow to receive 
incoming calls seamlessly so how should I interpret the said above?
Another required modification is a configurable keep-alive interval through 
"Advanced settings" or similar.

Thanks  

Original comment by oleg.lei...@gmail.com on 11 Aug 2010 at 8:45

GoogleCodeExporter commented 9 years ago
Quick question... I'm having a similar problem (no incoming calls on 3G), but 
with PBXes and TCP on a G1. Sipdroid is registered without problems (green dot) 
and the same setup works fine on my Desire... any ideas?

Original comment by simonbro...@gmail.com on 14 Nov 2010 at 2:01

GoogleCodeExporter commented 9 years ago
After a bit of additional testing, I'm dismayed to report that the problem is 
present on my Desire too - I just hadn't noticed it.

Depending on how long ago Sipdroid re-registered, it takes ages to start 
ringing, even though the other end has been ringing for quite a while. Also, 
hanging up on the calling end before Sipdroid shows the incoming call popup 
causes Sipdroid to continue ringing.

These are very basic issues that need to be sorted out if Sipdroid is to become 
a usable tool instead of just a toy. :(

Original comment by simonbro...@gmail.com on 14 Nov 2010 at 2:45

GoogleCodeExporter commented 9 years ago
After a bit of additional testing, I'm dismayed to report that the problem is 
present on my Desire too - I just hadn't noticed it.

Depending on how long ago Sipdroid re-registered, it takes ages to start 
ringing, even though the other end has been ringing for quite a while. Also, 
hanging up on the calling end before Sipdroid shows the incoming call popup 
causes Sipdroid to continue ringing.

These are very basic issues that need to be sorted out if Sipdroid is to become 
a usable tool instead of just a toy. :(

Original comment by simonbro...@gmail.com on 14 Nov 2010 at 2:45

GoogleCodeExporter commented 9 years ago
You may be able to change the registration interval through your SIP provider.

Original comment by kowalews...@gmail.com on 11 Aug 2011 at 3:50

GoogleCodeExporter commented 9 years ago
Let's face it, this bug is by design. No incomming over 3g (or 4g) so they can 
sell their service.

Original comment by doodtra...@gmail.com on 8 Oct 2011 at 8:34

GoogleCodeExporter commented 9 years ago
I use PBXes and TCP, on an Exhibit II.  Sipdroid appears to receive incoming 
calls over wifi, but NOT over the 3G / 4G data network.  My dot will be green 
and I am able to successfully place outgoing calls, but people trying to call 
me get rung through to voicemail, meanwhile I get no rings and no record of the 
missed call, just a new voicemail in my GV account.  Doodtrader's comment is 
really disheartening if it's true - I initially paid to download the grooVeIP 
app and could never get the call quality where I wanted it. Sipdroid has nice 
call quality but if I can't receive any calls when I'm not on the wifi in my 
house (where I have a landline phone, anyway -_-) this app is pointless.

Original comment by amalia.t...@gmail.com on 13 Jul 2012 at 5:17

GoogleCodeExporter commented 9 years ago
I solved this problem by switching to a different VoIP client on my Android 
phone. That VoIP client is part of Cronos, a Cyanogenmod-based ROM for my HTC 
Magic phone: http://forum.xda-developers.com/showthread.php?p=11333792

I am now able to receive incoming calls from my voip.ms account when I am on 
3G. My keepalive is set to 15, and "Send-keepalive" is set to "Always" instead 
of "Automatic". I am happily closing my pbxes.org account now...

Original comment by val.kul...@gmail.com on 11 Apr 2013 at 5:59

GoogleCodeExporter commented 9 years ago
My solution is an unlimited voice plan :-)

Original comment by o...@mobbie.net on 11 Apr 2013 at 6:14

GoogleCodeExporter commented 9 years ago
and that plan includes unlimited long distance and international calls, correct?

Original comment by val.kul...@gmail.com on 11 Apr 2013 at 6:20

GoogleCodeExporter commented 9 years ago
No, it's Canada-wide and 5c/min to US.
Anyway, I use DISA if I really need to call internationally when I'm not at 
home/office and in general I'm trying to use wireless technologies as less as 
possible - I've replaced all my home/business phones to WIRED ones.

Original comment by o...@mobbie.net on 11 Apr 2013 at 6:39

GoogleCodeExporter commented 9 years ago
Unfortunately mobile internet is not reliable enough for phone-like call 
quality.

Original comment by o...@mobbie.net on 11 Apr 2013 at 6:40

GoogleCodeExporter commented 9 years ago
And the integrated Android 4 SIP client is good enough though not that 
configurable compared to SIPDroid.

Original comment by o...@mobbie.net on 11 Apr 2013 at 6:44

GoogleCodeExporter commented 9 years ago
I am effectively avoiding roaming and long-distance charges by forwarding 
incoming calls to my voip.ms number. Then I receive calls on the same phone but 
these are VoIP calls, not cellular network calls - therefore, no roaming or 
long-distance charges.

I have SIM cards in those countries that I visit most often; with an unlocked 
phone, all I need is simply put the appropriate SIM card in the phone upon 
arrival to that country. With this, I have managed to avoid the [hideous] 
international roaming charges while using my phone a lot.

I agree that wireless is not as reliable as wired, however when you are on the 
road the wired option is not really an option.

Original comment by val.kul...@gmail.com on 11 Apr 2013 at 7:01

GoogleCodeExporter commented 9 years ago
Actually I'm doing the same but for different reasons - simply no need to 
update everyone if I change cell operator.

I believe one day mobile internet will be reliable enough for managing smooth 
conversation but for now it's not there yet and I cannot afford to myself 
torturing people with cutting off calls.

Original comment by o...@mobbie.net on 11 Apr 2013 at 7:09

GoogleCodeExporter commented 9 years ago
Not Receiving Most Incoming Calls While On 3G... PLS HELP ME....

Original comment by manoj4...@gmail.com on 7 Aug 2013 at 9:18

GoogleCodeExporter commented 9 years ago
Did anyone tested this code
public void keepAlive() {
        if (ka != null && Receiver.on_wlan && isRegistered())
            try {
                ka.sendToken();
                Receiver.alarm(60, LoopAlarm.class);
            } catch (IOException e) {
                if (!Sipdroid.release) e.printStackTrace();
            }
    }
thanks for sharing voip client, can i use it with www.vitelglobal.com

Original comment by azhar4...@gmail.com on 31 Oct 2013 at 4:58