Automatic reconnect on Request Timeout

[GoogleCodeExporter]

Samuel,

Can you please give some description of the Request Timeout message and 
the Reg. Timeout setting defaulted to 1800?

I always have Siphon running and on average I see Request Timeout message 
2-3 times a day. What I usually do is simply restart Siphon and it 
connects again. I guess it's caused by temporary lost of replies from the 
server. And since all it takes to restore the connection is to restart 
Siphon, is it possible to add a feature to attempt automatic reconnect 
when connection is lost instead of displaying the Request Timeout message?

Thanks,
Aleks

Original issue reported on code.google.com by aleksand...@gmail.com on 19 Mar 2010 at 3:24

[GoogleCodeExporter]

Normally, when the network wake up, Siphon tries to reconnect to the server.

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:57

[GoogleCodeExporter]

I installed the new version and tested it for a few days. Unfortunatelly the 
status 
still changes to Request Timeout once or twice a day even when the keep awake 
option 
is on.

I also noticed that it drains battery much faster.

Samuel, can you please answer these questions?
1) What exactly keep awake option does? Is it similar to Insomnia?
2) What causes Siphon to change to the Request Timeout status?
3) What is Reg. Timeout setting?

Thanks!

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

[GoogleCodeExporter]

By the way, if the connection with the server for some reason is lost, it would 
be 
nice if Siphon displays Reconnecting in the status. And after certain number of 
attempts or time trying it would switch to Request Timeout to prevent draining 
the 
battery. Maybe it's already doing something like this.

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

[GoogleCodeExporter]

1/ yes like Insomnia, KeepAwake plugin for SB... So it's logic it drains the 
battery,
because this option stops/forbids sleep mode.
2/ Maybe network
3/ This settings allows to Siphon to reconnect to the SIP server. The value 
depends
of Server configuration.

Logically, when the network (re)starts Siphon tries to connect. But I don't 
know if
it works when Siphon runs in background. I believe the 3G doesn't notify when 
is restart.

I didn't define a strategy to try to reconnect when the connection is lost 
because of
server and not network.

Original comment by samuelv0...@gmail.com on 3 Apr 2010 at 8:13

[GoogleCodeExporter]

I see. So if Siphon can detect that it's disconnected (when it displays Request 
Timeout) can you try to reconnect automatically?

Original comment by aleksand...@gmail.com on 3 Apr 2010 at 4:12

[GoogleCodeExporter]

While using Siphon on 3G/Edge, this is rather a boring problem. Since, GSM 
operators 
(at least in my country), does not keep the connection idle, they just shut it 
down.

3g/edge connection also dies and comes back when you're on the move, since 
sometimes 
you hit a place where there is no 3g base stations, or a place where your phone 
is 
messed up 'cause some BSSs are offering Edge, some are offering 3G.

Original comment by muratilk...@gmail.com on 10 Apr 2010 at 6:58

[GoogleCodeExporter]

I understand that connection may be lost, but it would be nice if siphon try to
recover from any case of lost connectivity. As a user I have to check my running
Siphon every other hour to make sure that it's in Connected status and not in 
Request
Timeout. And if I find it in Request Timeout status, all I have to do is to 
restart
it as I mentioned earlier.

It should be possible to automate this process, so that I don't need to check it
manually. If Siphon is running and there is no major problem with the no signal 
from
the carrier or the SIP server being down, I will know that it's Connected.

Original comment by aleksand...@gmail.com on 10 May 2010 at 6:10

[GoogleCodeExporter]

Original comment by samuelv0...@gmail.com on 10 May 2010 at 6:34

• Changed state: Accepted