Closed GoogleCodeExporter closed 8 years ago
Issue 131 has been merged into this issue.
Original comment by samuelv0...@gmail.com
on 22 Jan 2009 at 7:44
In all cases, SIP client must keep the open connection between him and server.
Like
that it can receive the call. Otherwise if the connection is down, the server
can't
send INVITE message.
If you want to get Siphon in background, I believe that you want to receive
calls,
isn't it?
Certainly, it's possible to increase the interval. But the WiFi connection stay
open/active, and the battery life will be killing too.
I don't know if there are a good solution for that.
Moreover if Apple refuses the applications in background, it is for that.
Original comment by samuelv0...@gmail.com
on 22 Jan 2009 at 7:50
The problem is whether its foreground or background, siphon still takes too
much CPU
and resources which depletes the battery very fast. Even if I've my phone in
sleep
mode with siphon running in background (wifi disabled, mail disabled, ssh
disabled,
etc etc), I don't get more 3-4 hours of standby time. I think siphon should act
more
like the Phone application which really sips power. Otherwise I may only want
to want
to run siphon to make calls but not receive them.
BTW, thanks a ton for a great app. I was using Truphone with hacks earlier but
that
was horrible .. 80% cpu usage. This is so much better.
Original comment by mwa...@gmail.com
on 22 Jan 2009 at 2:54
It's possible ;-)
struct : pjsua_acc_config
/**
* Set the interval for periodic keep-alive transmission for this account.
* If this value is zero, keep-alive will be disabled for this account.
* The keep-alive transmission will be sent to the registrar's address,
* after successful registration.
*
* Default: 15 (seconds)
*/
unsigned ka_interval;
Original comment by samuelv0...@gmail.com
on 29 Jan 2009 at 11:50
so we will see it in next version :) ???
Original comment by mwa...@gmail.com
on 29 Jan 2009 at 11:58
2.0.3
Original comment by samuelv0...@gmail.com
on 1 Feb 2009 at 5:03
thanks !!!!
Original comment by mwa...@gmail.com
on 1 Feb 2009 at 5:04
Original issue reported on code.google.com by
mwa...@gmail.com
on 22 Jan 2009 at 12:59