Backgrounding Siphon

[GoogleCodeExporter]

There exists a backgrounding app for the iphone. Would it be possible to
add support for this? Especialy, that something pops up when a call comes
in. Backgrounding seams to work with the current version of siphone.

Original issue reported on code.google.com by matthias...@gmail.com on 4 Jan 2009 at 6:20

• Merged into: #410

[GoogleCodeExporter]

Note: This application is called 'Backgrounder'.

However, would adding the Siphone bundle name to the Background settings file 
not
solve the issue?  I'm sure native support would be great, but that should do the
trick.  There's info about it on their Google Code wiki.

Original comment by patrickp...@gtempaccount.com on 4 Jan 2009 at 7:07

[GoogleCodeExporter]

Issue 93 has been merged into this issue.

Original comment by samuelv0...@gmail.com on 4 Jan 2009 at 2:27

[GoogleCodeExporter]

Original comment by samuelv0...@gmail.com on 4 Jan 2009 at 2:27

• Changed title: Backgrounding Siphon
• Changed state: Accepted

[GoogleCodeExporter]

I'm using Backgrounder, which works pretty good, except I think that Siphon 
stops 
working without any warning due to memory limitations on the iPhone.  Once a 
native 
background mode is built for Siphon, I would suggest that the application pops 
up 
with the accept and decline buttons upon receiving a new call.  Currently it 
rings, 
but you have to find the application icons, start it, then answer it.  This of 
course takes time and while you are doing this, you could miss the call.

Original comment by quinlanr...@gmail.com on 5 Jan 2009 at 12:58

[GoogleCodeExporter]

I don't know how Backgrounder works, but I know when Siphon quits it stops  all
connection. 

Original comment by samuelv0...@gmail.com on 5 Jan 2009 at 8:24

[GoogleCodeExporter]

Just tried it with backgrounder, works pretty good, except the program doesn't 
pop up. Beggars can't be 
choosers I guess :p 
http://gizmodo.com/5058234/iphone+backgrounder-hack-brings-true-background-
multitasking-to-iphone-apps

Original comment by harry...@gmail.com on 5 Jan 2009 at 8:08

[GoogleCodeExporter]

From Dustodub:
Just tested the new version in Cydia and everything is working great. Thank you 
very
much for your effort, it is great to finally have a solid working and free SIP 
app on
my iphone 3g. Also, I know you were testing a daemon for siphon, this requires a
constant data connection to the sip server. How does this effect battery life? 
Is it
possible to have an idle connection to the server with periodic connection 
updates to
save battery life? Thanks. Dustin

Original comment by samuelv0...@gmail.com on 12 Jan 2009 at 7:57

[GoogleCodeExporter]

What is the URL to the google code wiki for Backgrounder?

Original comment by RiceInte...@gmail.com on 17 Jan 2009 at 6:29

[GoogleCodeExporter]

Issue 124 has been merged into this issue.

Original comment by samuelv0...@gmail.com on 21 Jan 2009 at 12:27

[GoogleCodeExporter]

I'm using backgrounder to background the siphon. I'm connecting it to my own 
asterisk
server. Seems like the siphon is constantly sending UDP messages every few 
seconds.
This kills the battery life of the iphone. Is there anyway to customize this UDP
interval ?

Thanks
Mudit

Original comment by mwa...@gmail.com on 21 Jan 2009 at 11:54

[GoogleCodeExporter]

Issue 160 has been merged into this issue.

Original comment by samuelv0...@gmail.com on 16 Feb 2009 at 7:01

[GoogleCodeExporter]

When it's accepted it meant you will work on it?

Original comment by infinite...@yahoo.com on 17 Feb 2009 at 10:17

[GoogleCodeExporter]

Backgrounder works, even if it says disconnected, you could use it to make a 
call,
although I'm using a MagicJack account so YMMV. Also, I use Insomnia to be able 
to
shut the display off, essentially turning my touch into an iPhone without the 
built
in earpiece/mic.

As for the UDP pings, I wonder if that has to do with the keep alive interval?

Original comment by Rams...@gmail.com on 23 Feb 2009 at 2:07

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

We came across another issue with Backgrounder and Siphon. When in the office, 
firewalls block connections, 
when we leave connections don't restart. In fact the last test we did took a 
full day to get Siphon working 
properly again. This is reproducible for us.

Original comment by jasonbe...@mac.com on 27 Aug 2009 at 8:17

[GoogleCodeExporter]

Look issue 312

Original comment by samuelv0...@gmail.com on 11 Oct 2009 at 9:22

[GoogleCodeExporter]

I am running siphon in background connected to my home asterisk as well. 
I would say that for now, a button to "hibernate" the app (leaving only the sip 
messages alive) and some GRIP support could make it a GREAT app to integrate 
SIP and 
GSM on the iphone.
http://code.google.com/p/networkpx/wiki/GriP

Original comment by pedro.pr...@gmail.com on 16 Oct 2009 at 7:45

[GoogleCodeExporter]

Here are three ways you can do this.
You can make a mobile substrate add on that will use NSConnection to control 
Siphon. That will allow 
you to popup when other apps are on, you can make it tell backgrounder to put 
the current application in 
the background and popup you, or you can tell the iPhone os to popup a 
notification asking if you want to 
answer the phone. 

Original comment by GRMrGe...@gmail.com on 2 Nov 2009 at 5:05

[GoogleCodeExporter]

http://stackoverflow.com/questions/1413154/how-to-implement-daemon-process-for-b
ackground-task-in-iphone-sdk-3-0

Block thread at applicationWillTerminate: won't get killed in a short time, but 
WILL
be rejected by App Store. For non-AppStore or personal applications, here is 
code:

@interface MyApplication : UIApplication
{
    BOOL _isApplicationSupposedToTerminate;
}
@property (assign) BOOL isApplicationSupposedToTerminate;
- (void)_terminateWithStatus:(int)status;
@end

@implementation MyApplication
@synthesize isApplicationSupposedToTerminate = 
_isApplicationSupposedToTerminate;
- (void)_terminateWithStatus:(int)status
{
    if (self.isApplicationSupposedToTerminate) {
        [super _terminateWithStatus:status];
    }
    else {
        return;
    }
}
@end

In main.m

    int retVal = UIApplicationMain(argc, argv, @"MyApplication", nil);

Delegate:

- (void)applicationWillTerminate:(UIApplication *)application
{
    [(MyApplication*)application setIsApplicationSupposedToTerminate:!kIsTransferDone];
}

Block thread at applicationWillTerminate: won't get killed in a short time, but 
WILL
be rejected by App Store. For non-AppStore or personal applications, here is 
code:

@interface MyApplication : UIApplication
{
    BOOL _isApplicationSupposedToTerminate;
}
@property (assign) BOOL isApplicationSupposedToTerminate;
- (void)_terminateWithStatus:(int)status;
@end

@implementation MyApplication
@synthesize isApplicationSupposedToTerminate = 
_isApplicationSupposedToTerminate;
- (void)_terminateWithStatus:(int)status
{
    if (self.isApplicationSupposedToTerminate) {
        [super _terminateWithStatus:status];
    }
    else {
        return;
    }
}
@end

In main.m

    int retVal = UIApplicationMain(argc, argv, @"MyApplication", nil);

Delegate:

- (void)applicationWillTerminate:(UIApplication *)application
{
    [(MyApplication*)application setIsApplicationSupposedToTerminate:!kIsTransferDone];
}

This will stop application from terminating unless your transfer is done. Setup 
a
timer for check timeout is important. And in 
applicationDidReceiveMemoryWarning:,
quit your app by:

- (void)applicationDidReceiveMemoryWarning:(UIApplication *)application {
[(MyApplication*)application setIsApplicationSupposedToTerminate:YES]; 
[application
terminateWithSuccess]; }

Original comment by samuelv0...@gmail.com on 16 Nov 2009 at 11:17

[GoogleCodeExporter]

Original comment by samuelv0...@gmail.com on 30 Jun 2010 at 1:16

• Changed state: Duplicate