Siphon does not receive incoming calls after a few minutes of sleep on 3G

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run Siphon. Enable backgrounder (not necessarily)
2. Press the power button or leave the iphone to auto lock itself
3. Place one incoming call 3 minutes later and another call 10-15 minutes 
later.

What is the expected output? What do you see instead?
Siphon should ring for both calls. Instead, it rings on the first call, 
but after a longer period it doesn’t show the incoming call. If you turn 
on the screen, Siphon is in the Connected status. Moreover, if you place a 
call, it connects well, and after that we can again place an incoming call 
and Siphon will ring. However, if we again wait for 10-15 minutes, the 
incoming calls won’t go through again and Siphon won’t ring.

What version of the product are you using? On what operating system?
Siphon 2.1.0, OS 3.0

Please provide any additional information below.
I’m using Google Voice and Gizmo. Gizmo calls history show missed calls, 
so GV connects Gizmo. Also, it can stay for many hours and then ring on an 
incoming call on Wifi with Insomnia running. So, it’s not a Gizmo problem. 
Plus other applications like Skype and Fring stay connected on 3G and ring 
on incoming calls after much longer periods than 15 minutes.

My guess is that iphone goes to sleep and Siphon disconnects. However, why 
does it still show Connected and why it doesn’t go to sleep right after 30 
seconds (according to the specification), but rather after couple of 
minutes?

Original issue reported on code.google.com by aleksand...@gmail.com on 17 Nov 2009 at 7:33

[GoogleCodeExporter]

Effectively, it's weird :-(
Could you enable log file and post or send me the log file ?

Original comment by samuelv0...@gmail.com on 4 Jan 2010 at 7:43

[GoogleCodeExporter]

Samuel,

Thanks for replying. I tested it today with Google Voice + Gizmo having Siphon 
running and placing a call from another phone to my google number. I saw 
various 
behavior. One time out of 6 tests the call went through even after 10 mins. A 
couple 
of times I saw strange situation where running Siphon starts ringing only after 
I 
unlock the iphone even if the incoming call was over several minutes ago (Maybe 
GV 
or Gizmo kept trying to connect it) and a couple of times a call didn't go 
through 
at all.

Here is the detailed description of the tests with the log files attached:

0.txt - Successful call that went through after 10 mins of idle time.

1.txt - Made a call after about 10 mins. Siphon didn't ring. Waited till the 
voicemail greeting started and hung up on the initiating phone. Unlocked the 
iphone 
and Siphon started ringin immediatelly. Tapped the answer button - Siphon was 
hanging on the same screen with buttons for a few seconds. Tapped the cancel 
button -
 the screen switched back to dialpad.

2.txt - Made a call after about 10 mins. Siphon didn't ring. Waited till the 
voicemail greeting started and hung up on the initiating phone. Waited for a 
minute. 
Unlocked the iphone and Siphon started ringin immediatelly. Tapped the cancel 
button - the screen switched back to dialpad.

3.txt - Made a call after a minute. Waited for 3 rings on the initiating phone 
- 
Siphon did not ring. Unlocked the iphone - Sipon did not ring and displayed 
Connected. Hung up on the initiating phone.

4.txt - Made a call after about 3 mins. Siphon didn't ring. Waited till the 
voicemail greeting started and hung up on the initiating phone. Waited for 
about 3 
mins. Unlocked the iphone and Siphon started ringing immediatelly. Tapped the 
cancel 
button - the screen switched back to dialpad.

5.txt - Made a call after 2 mins. Siphon didn't ring. Waited till the voicemail 
greeting started and hung up on the initiating phone. Waited for about 10 mins. 
Unlocked the iphone - Siphon displayed Connected.

Original comment by aleksand...@gmail.com on 5 Jan 2010 at 1:28

Attachments:

• 0.txt
• 1.txt
• 2.txt
• 3.txt
• 4.txt
• 5.txt

[GoogleCodeExporter]

Hi, 
I have exactly the same problem. I am using sipgate.at.
Sometimes happen after 10 min, sometimes after 1 hour. But sure it happen. 

Original comment by helmut.f...@gmail.com on 5 Jan 2010 at 12:30

[GoogleCodeExporter]

I just tried Sipgate and had the same problem too. It was similar to the test 2 
described above. Siphon started ringing right after I unlocked it.

Original comment by aleksand...@gmail.com on 5 Jan 2010 at 2:23

[GoogleCodeExporter]

I tried together with Insomnia and it works well also on 3G. Also after some 
hours.
I think insomnia keep siphone full runing and so there isnt this problem.
But unfortunaly it need a lot of battery. Without insomnia looks like siphone 
also 
still runing after go to sleep mode, but only for around 10-30 min. Maybe after 
Expire Time to SIP Provider is finish it does not work longer.

Original comment by helmut.f...@gmail.com on 6 Jan 2010 at 4:09

[GoogleCodeExporter]

backgrounder and insomnia enable  continue running siphon in the sleep mode. 
but wifi 
will be disabled by OS in 30 minutes, so siphon is not able to receive the 
incomming 
calls anyway :-). the workaround is set the value of 
<key>DisassociationInterval</key> 
in com.apple.wifi.plist from <real>1800</real> (this means 1800 seconds, or 30 
minutes) 
to some bigger value. I am not sure, if apple don't follow  the same way for 3G 
disabling ....somebody knows?

Original comment by ivo.vacek on 8 Jan 2010 at 12:36

[GoogleCodeExporter]

I tested it for a couple of days with Insomnia. With Sipgate it was giving me 
Request Timeout after a few minutes all day. With Gizmo it was working 
perfectly all 
day. However, today I decided to test again and I'm having the same problem 
even 
with Gizmo when Insomina is running. Incoming call doesn't ring.

Ivo,
Are you saying that even with insomnia wifi will be turned off after 30 mins?

Original comment by aleksand...@gmail.com on 9 Jan 2010 at 1:27

[GoogleCodeExporter]

I've been testing this issue since my last post and I tend to blame VOIP 
servers 
and/or cellular 3G network, not Siphon. This issue is totally unstable. Some 
days it 
stays Connected all day and all calls go through. Other days it disconnects 
several 
times a day either displaying Request Timeout or not ringing on incoming call.

This will need to be evaluated with a very reliable provider. Maybe after 
Google 
officially release something around Gizmo hopefully delivering better quality 
than 
Google Voice is now.

Original comment by aleksand...@gmail.com on 19 Mar 2010 at 1:40

[GoogleCodeExporter]

I uploaded a new version of Siphon 
(http://code.google.com/p/siphon/downloads/list ).
This issue should be fixed, could you confirm this ?

I added a new switch in network settings to enable Keep Awake option.
By default this switch is disabled. When the keep awake feature is enabled, a 
phone
is displayed in status bar

New features and bugs fixed are described here :
http://code.google.com/p/siphon/wiki/Feedback

Original comment by samuelv0...@gmail.com on 27 Mar 2010 at 4:54

• Changed state: Fixed

[GoogleCodeExporter]

I posted about testing in the somewhat related Issue 380. I didn't see calls 
not 
going through when it's Connected. However, I hadn't experienced this issue for 
a 
while already. That's why I posted here earlier that I blame the network and 
infrastructure, not Siphon.

We can probably close this issue.

Original comment by aleksand...@gmail.com on 2 Apr 2010 at 10:45