Platform Specifics

Behaviour of the mobile app for incoming calls when the app is turned off.

• iOS: As soon as a call starts ringing, the mobile app starts running in the background (i.e. after 1 to 2 seconds).

• Android: App starts running only when a user accept a call from an incoming call alert. On older devices, the app may take a few seconds to launch, i.e., the call rings but the app is not yet running.

• Once the application starts (regardless of the platform), the Daktela device is automatically logged in and registered.

What should I do if I receive the standard notification instead of the expected blue screen notification?

Open the Daktela app in your phone settings and allow the notification permission."

On Xiaomi Phones:

1. Open the Daktela app in your phone settings and allow the notification permision.

2. Open Other permissions.

3. Allow the Show on Lock screen and Open new windows while running in the background.

Connection Behaviour on Your Mobile Device

Huawei, Honor, and Xiaomi phones are known for their strong battery optimization policy which may cause background apps to be killed by the operating system. This can cause problems with incoming calls and chats. To prevent this, please turn off battery optimizations for the Daktela app. You can do this in the app settings.

• When you are on a call using the App and you receive a GSM call, your mobile internet turns off, meaning your call in the App will disconnect. If you end your GSM call within 10 seconds, the original call will reconnect.

• When you have a mobile device, calls to the mobile app ring from the caller’s point of view even if you don't have an internet connection on your device. You can set up a GSM Redirect as a backup.

• If you experience calls breaking up, the most common reason is data connectivity. If you are sure your connectivity speed is sufficient and experience breaking up calls repeatedly, please get in touch.

• The behaviour above is consistent with other VoIP phone applications such as WhatsApp.

List of Supported Devices

• Currently we support following models:

  • Apple

  • Samsung

  • Google

  • Motorola

Other phones may work but you may experience some errors.

Huawei, Honor, and Xiaomi phones are known for their strong battery optimization policy which may cause background apps to be killed by the operating system. This can cause problems with incoming calls and chats. To prevent this, please turn off battery optimizations for the Daktela app. You can do this in the app settings.

The Pull Data and WhoIm processes

Pull Data

This feature uses a method called long polling to check for new events. The first time you make a request, you'll leave the hash attribute empty.The server will respond right away with all available data and a hash value. This hash identifies your current state. For long polling to work, include the hash from the previous response in every new request you make.If something happens (like an incoming call or a notification), the server will send back the new data along with an updated hash. If nothing happens within 15 seconds, the server will still respond but only with the hash. Use this hash for your next request. Pull Data process is essential for real-time applications. It helps detect various activities and events such as:

• Incoming calls

• Device state changes

• Start and end of pauses

• Queue logins and logouts

• Notifications

By following this process, you can ensure that your application remains responsive and up-to-date with all the latest events.

The Pull Data process only run under the following conditions:

• Phone is Unlocked: The phone must be unlocked for the Pull Data to function.

• App is Foregrounded: The mobile application must be open and active in the foreground. If the application is backgrounded or the phone is locked, the process will not run.

  Scenario Example:

• A user logs into the mobile app.

• They then switch to another app or lock their phone.

• Since the Pull Data stops running when the app is not in the foreground, the user's session is considered inactive.

• If the app remains inactive (backgrounded or phone locked), the user will be automatically logged out according to the auto logout policy.

WhoIm

This feature enables you to get information about the user who is currently logged in, based on the access token provided. By using the HTTP GET method, WhoIm returns static data about the user. If the access token is invalid, it will not provide user information but will instead return details about the current version of the Daktela V6 system. Essentially, it helps you quickly check the logged-in user's details, as long as the access token is valid.

The WhoIm process only run under the following conditions:

• Phone is Unlocked: The phone must be unlocked for the WhoIm to function.

• App is Foregrounded: The mobile application must be open and active in the foreground. If the application is backgrounded or the phone is locked, the process will not run.

  Scenario Example:

• A user logs into the mobile app.

• They then switch to another app or lock their phone.

• Since the WhoIm stops running when the app is not in the foreground, the user's session is considered inactive.

• If the app remains inactive (backgrounded or phone locked), the user will be automatically logged out according to the auto logout policy.