on Acrobits Softphone & Groundwire
Up until now, we have always left configuration of incoming calls up to the user, so they would be aware of what they are actually doing and not have any surprises. But many users think this has made Acrobits Softphone and Groundwire more complicated to configure than need be. Starting with the latest update to Groundwire and Acrobits Softphone), we've changed the way we handle incoming calls slightly, making it easier to configure for new users, but advanced users will still be able to tweak their settings when they need to.
New users (and existing users after the update) will get a new screen when they first open the client. It will contain a disclaimer and inquire whether the user wants to enable Push Notifications. If you accept, all SIP Accounts added will automatically have push notifications enabled. If you don't accept, we will set incoming calls to Foreground Only, but you can always change this.
Now, when you tap on settings from the keypad, you will see a new 'global' incoming calls settings. This enables you to set default preferences for incoming calls for all accounts. No matter what you select here, you can always go to the advanced settings of the SIP Account and change what method the account uses manually. Here is the definition of each of the options.
Push Notifications - This is our recommended setting for receiving calls when the client is not in the foreground. All accounts added will be registered for Push Notification automatically when this is selected
Backgrounding or Push - Depending on what transport protocol you are using for the provider, we will set Push Notifications or Backgrounding for that account. Accounts that use udp (this will be by far the vast majority, very few providers support tcp) will be set to push notifications. Accounts that use tcp will be set to Backgrounding.
Backgrounding Always - We will always set incoming calls to Backgrounding. If you have selected tcp as the transport protocol, it will work directly. If you have udp as the transport protocol, we will use our proxy to translate the protocol.
Keep Device Awake - Keeps the application fully active while in the background. Works with virtually any providers, but puts the most drain on battery.
Foreground Only - This was previously the default for all accounts when they are added. All accounts added will register and receive calls automatically, but only when in the foreground (unless you use multitasking, see more below).
Off - Do Not Register - This is exactly what it says, we will not register your account and you will not receive calls. But be aware many providers do not support this. If using this causes issues making calls, change to one of the other methods.
Off with Registration - The app will register, but incoming calls from the provider will be rejected.
As mentioned earlier, no matter what you have listed here, you can always change the methods individually in the advanced settings for each SIP Account.
Notes: If you have not read our other articles on Push Notifications and multitasking, you may be confused. This article is only to explain how to set which method is used. You should read these articles for descriptions of how each method works.
Important Note: The iOS feature necessary for backgrounding to work has been deprecated in iOS10. Due to this we will, unfortunately, be removing this feature shortly.