Prevent your computer from going to sleep
- Mac Keep Alive App Download
- Mac Keep Alive App Free
- Mac Keep Alive App Windows 10
- Mac Keep Alive App Offline
If you have problems with your PC locking or going to sleep, caffeine will keep it awake. It works by simulating a keypress once every 59 seconds, so your machine thinks you're still working at the keyboard, so won't lock the screen or activate the screensaver.
Welcome to Amphetamine, the most awesome keep-awake app ever created for macOS. Amphetamine can keep your Mac, and optionally its display (s), awake through a super simple on/off switch, or automatically through easy-to-configure Triggers. Amphetamine is extremely powerful and includes advanced features for those who need them, yet remains intuitive and easy-to-use for those who don't need all of the bells and whistles. I recommend grabbing a copy of iTerm. It's free and has tabbed shells so you can have a ton of sessions open in one window. There are settings in the app to send keep-alive signals as well which would fix your problem. If you do something wrong, the general result will be that the app is not only kept alive, but in fact keeps launching every 10 seconds or so (launchd's throttle time-out), so that it keeps grabbing screen focus, which is very annoying. If that happens, just unload the plist, make sure it is correctly written and the app is quit, then load it.
The icon is shown above - it's the leftmost one in the task tray, and this is all you see. Double-clicking the icon empties the coffee pot (that's what the icon is) and temporarily disables the program. Double-clicking it again refills the pot, and will keep your machine awake.
By default the app starts enabled, and works every 59 seconds. There are some command line switches you can use to alter this behaviour:
xx
- where xx is a number which sets the number of seconds between simulated keypresses. This must be the first text on the commandline-startoff
- application starts disabled.-exitafter:xx
- application will terminate after xx minutes-activefor:xx
- application will become inactive after xx minutes-inactivefor:xx
- application will become active after xx minutes-appexit
- terminates current running instance of application-appon
- makes the current running instance of the application active-appoff
- makes the current running instance of the application inactive-apptoggle
- toggles the running state of the current running instance of the application-apptoggleshowdlg
- toggles the running state, and shows dialog-replace
- closes the current running instance, replacing it-noicon
- does not show a task tray icon-useshift
- simulate the shift key instead of F15-showdlg
- shows a dialog indicating whether caffeine is active-ontaskbar
- show a task bar button (use with -showdlg)-allowss
- prevent sleep, but allow the screensaver to start-key:xx
- simulate using virtual key code xx
Note: the codes on the linked page are in Hex, convert them to decimal for use with this parameter-keypress
- simulate a full key press, not just a key up event-oldicons
- use more colourful tray icons-darkicons
- use icons which work better for dark-on-light colour schemes-watchwindow:xx
- active only when a window with xx in the title is found-activehours:....xxxxxxxx....
- put 24 . or x characters - which indicate from hour 0 to hour 23 of the day. Caffeine will be active only in hours with an x
Compatibility
The keepalive concept is very simple: when you set up a TCP connection, you associate a set of timers. Some of these timers deal with the keepalive procedure. When the keepalive timer reaches zero, you send your peer a keepalive probe packet with no data in it and the ACK flag turned on. You can do this because of the TCP/IP specifications, as a sort of duplicate ACK, and the remote endpoint will have no arguments, as TCP is a stream-oriented protocol. This fun brain training app follows the journey of two animated characters who travel through a field of grass. Personal Zen is a nice app meant for reducing anxiety and trains the brain to focus on the positive aspects. The developer’s advice is to use the app for 10 minutes a day to see the best results.
Caffeine works by simulating an F15 key up event every 59 seconds. Of all the key presses available, F15 is probably the least intrusive, and least likely to interfere with your work.
However, Caffeine might interfere with some apps:
- PowerPoint uses the F15 keypress to pause video in a slide
- Google Docs/Sheets
- Smartsheet
- Terminal emulation, e.g. Putty
If you think any of these might cause you a problem, set the
-useshift
command line parameter.Video
Caffeine user humancar2n has put together a short YouTube video showing how the app works.
Mac version
Do you need this functionality on your Mac? Lighthead Software have written a separate app, also named Caffeine, which can help you out.
Versions
v1.90 - October 2020
-darkicons
command line option added-activehours
command line option addedTooltip replaced with a new one which works more reliably
Menu appearance updated
v1.81 - May 2020
Bug with the
-watchwindow
command line fixedv1.80 - January 2020
v1.64 - September 2017
Option for old icons added, 'cos not everyone likes the new ones
v1.63 - February 2017
Icons updated slightly to show up better on a white background.
v1.62 - April 2016
New icons, designed by Rubén Gómez Radioboy
v1.61 - October 2015
Fixed bug with app not going active/inactive correctly when a timed period elapsedv1.60 - July 2013
New command line options:
-allowss
-ontaskbar
-apptoggleshowdlg
-key:xx
-keypress
Added menu items to go Active/Inactive
Type in About box corrected
-apptoggle
will re-show the dialog if it was originally shownMac app store gnuplot. v1.50 - November 2010
New command line options:
-inactivefor
-showdlg
-apptoggle
Simulated keypress changed from right context menu key to F15 as this is likely to be even less intrusive.
v1.40 - July 2009
New command line options:
-replace
-noicon
-useshift
Hovering over the tray icon now shows the status of the app
v1.35 - May 2009
Simulated keypress changed from shift to the right context menu key (at the suggestion of Kevin Kleinfelter) as this is likely to be less intrusive.
v1.30 - February 2009
Command line switches added to terminate the app after x minutes, disable the app after x minutes, and enable or disable the currently running instance of the app
v1.20 - March 2008
Command line switches added to set the interval and to start disabled
Download Caffeine (x86 and x64)
Issues related to incoming calls are a common problem with voice over IP.
This article aims to outline the most common problems for the different operating systems as well as possible solutions and best practices for the most reliable incoming calls.
Most computers and phones do not use a fixed IP or are behind a NAT network.
VOIP servers use REGISTRATIONS to keep track of the current location of a user, this also servers as way to keep NAT bindings open on your home or office router.
iOS, Android and Windows Phone:
Make sure that Zoiper is allowed to run in the in the background
Android:
Open Zoiper -> go to settings -> Connectivity
Enable Keep Alive WiFi (unless you want to switch to 3g/4g when the wireless turns off).
Stay awake is on
Run in background is on
Then go to Android Settings -> Apps -> Zoiper -> Data Usage
Enable background data
Enable Unrestricted data usage
On Android 6.0 and above, please make sure Zoiper is on the whitelist for battery optimization. Zoiper should popup to allow it to add itself to the whitelist, but this will not work on some devices (Huawei, Xaomi,.) that come with their own battery optimization settings. Please manually add Zoiper to the battery optimization whitelist on such devices.
For Huawei devices, please see here.
iOS:
First make sure that Zoiper is allowed to use the cellular network.
To do so, to to the ios settings -> Cellular
Scroll down to the 'Use Cellular Data For' and make sure the option is enabled for Zoiper.
Then try to use TCP or TLS for your SIP account. (This does not work for IAX)
Note, when using TCP if the server sends too much wake-up packets (more than 15 for 300 seconds), iOS will kill the application.
(When 'Qualify' is enabled in Asterisk servers, the default timeout will be 2 seconds)
You can do so in Zoiper -> Settings -> Accounts -> (Your account) -> Network Settings
Change the transport to be TCP or TLS.Try if you can still register. If you cannot, your provider does not support TCP or TLS and this setting will not work.
Keep in mind that due to iOS limitations, it is possible for incoming calls not to work when your internet connectivity stops (out of reach for WiFi and cellular at the same time) and this continues for over 30 seconds.
(This will cause the TCP voip socket to get closed and iOS will force Zoiper to hibernate).
Zoiper will keep retrying approximately every 10 minutes and if there is network it will re-register.
The default registration expiry values are:
- UDP: 60s;
- TCP/TLS: 600s.
If you cannot use TCP or TLS because your provider or PBX does not support it, you can still try use UDP although it often causes side effects such as increased battery usage and sometimes problems with audio on other applications.
To enable it, go to Zoiper -> Settings -> Incoming calls
How to Uninstall Apps on the Mac - Lifewire. Enable Wi-Fi Keep alive
Enable Force background
Windows Phone:
As Microsoft does not allow applications to run in background, Zoiper will not be able to run in background, only under the lock screen.
This means if you started any application after opening zoiper, then the incoming calls will no longer work.
The only thing to be done is to implement Push on your/VoIP provider's server.
This means if you started any application after opening zoiper, then the incoming calls will no longer work.
The only thing to be done is to implement Push on your/VoIP provider's server.
The NAT network is causing issues
You can verifiy if this is the case if Zoiper receives incoming calls immediately after a registration to the server, but after a few minutes incoming calls stop working.
The most likely culprit here is the short NAT port mapping on your home or office router.
When using UDP, most routers will drop the port mapping after a few minutes. This means zoiper would have to re-register every minute to keep the mapping alive.
When using TCP most routers will keep the connection for many hours (unless they run out of memory and start recycling port mappings).
Try switching to TCP or TLS instead of UDP (if your provider or PBX supports it).
If your voip provider or PBX does not support TCP, try lowering the re-registration time in zoiper to 30 or 1 minute. (Keep in mind that this will have a significant impact on battery life when using cellular 3g/4g, the impact on WiFi is not as signficant).
Keep in mind that an excessive reason of re-registrations might lead to temporary blocking by your voip provider, in this case you can try using the sip keep alive option in Zoiper instead.
Windows:
go to settings -> accounts -> your account -> advanced -> Network related.
Change transport to TCP or TLS.
If that does not work and you can only use UDP, please ensure sip keep alive is enabled and is set to 30s.
Mac:
Mac Keep Alive App Download
on mac: go to settings -> accounts -> your account -> advanced -> Network related.
Change transport to TCP or TLS.
If that does not work and you can only use UDP, please ensure sip keep alive is enabled and is set to 30s.
Lastpass apple app for mac will not open. Linux:
go to settings -> accounts -> your SIP account -> advanced -> Network related.
Change transport to TCP or TLS.
If that does not work and you can only use UDP, please ensure sip keep alive is enabled and is set to 30s.
Android:
go to settings -> accounts -> your SIP account -> network -> Network
Change transport to TCP or TLS.
If that does not work and you can only use UDP, please ensure sip keep alive is enabled and is set to 30s.
iOS:
go to settings -> accounts -> your SIP account -> advanced -> Network related.
Change transport to TCP or TLS.
If that does not work and you can only use UDP, please ensure sip keep alive is enabled and is set to 30s.
Please note that if your public ip address changes but you are using an internal ip address behind a NAT, then zoiper will not be notified about a network change and will not re-register automatically. This situation will correct itself when the re-registration time is due. If you are experiencing this, please reduce the re-registration time (registration expiry) to a lower value to minimize the time you could be without incoming calls when such an event happens.
Incoming calls never work
Mac Keep Alive App Free
SIP ALG
STUN
rPORT for signalling
Zoiper will send a register to the server to let the server know w
- A firewall is blocking the incoming connections
-> faster re-registration
Mac Keep Alive App Windows 10
Make sure you do not use keep alive on the server or zoiper could get killed. Other than that it should work reliably. It could fail for maximum 10 minutes if there was no network for a while.
In such case, zoiper would lose the TCP connection, have limited time to try to reconnect before being forced to sleep by ios and since there is no active TCP socket, not be notified about a new network change.
Your ip address on the router changed but the pc still has the same ip.
Mac Keep Alive App Offline
add here the stuff from the error 408 about the data in the background and on cellular for ios and android.