One time incomming call based on accepted push

[PolyakovPavel]

Hello.
We need to accept incoming calls based on data received in push messages. For example, in a push notification, we receive data about the server, the user, their login, and the password for connecting to the SIP. We then pass this data to the AccountModel in the SDK. The SDK makes a Register request to the SIP server and waits for the specified time INVITE from server. The subsequent behavior is similar to accepting an incoming call.

Based on your example, we were unable to connect to the SIP server when receiving a push notification.

If such a scenario is possible, could you provide an example?

[siprix]

.. in a push notification, we receive data about the server,

It appears like you want to implement user's credentials provisioning based on the push notification.
But it looks strange as typically app will be able to receive push notification only after it sent REGISTER request with push token, which requires to have some initial server credentials.

Also question - are you asking about iOS or Android?

Technically, it's possible.
In case of Android you'll get _firebaseMessagingBackgroundHandler(RemoteMessage message) - see main.dart:84
App can extract data from the received message and (re-)initialize SDKs instance.

In case of iOS, SDK will trigger onPushIncoming(pushPayload) - see calls_model_app.dart:41, where argument contains all received data.

[PolyakovPavel]

Hello
Thank you for your reply.

I was able to use _firebaseMessagingBackgroundHandler for our use case.
The push notification arrives, the app wakes up, and the account is registered on the SIP server.

However, on Android, if a call doesn't arrive within 3 seconds of receiving the push notification, the app goes into idle mode and doesn't respond to the incoming call.

As far as I understand, this is related to power saving. After going into idle mode, the system blocks any network requests.

If i disable the recommended power saving profile for the app, the SDK starts sending requests to the keepalive, and everything works correctly.

When using the recommended power saving profile, only the following scenario is currently possible:

1. Send a push notification to register on the server.
2. Once the account is registered, initiate the call.
3. Send immediately another push notification to wake the application from idle mode and enable network calls.

We see the following use case:

1. Send a push notification with SIP connection details.
2. Upon receiving the push notification, registration occurs on the server.
3. The call acceptance timeout is 10-15 seconds. This is the time the application can accept the call.
4. After the timeout expires or the call ends, we unregistr account on the server and delete.

Can you suggest a way to implement this use case? Or are we misunderstanding it?

[siprix]

Root cause of issue is delay between receiving push and SIP INVITE.
During that delay system may disallow app to access network and it can't receive anything.

You can't cover this issue by sending push with some specific details as app doesn't control how long system allows it to access network.
Possible fixes:

• send second push after delay, which potentially should allow app to work longer;
• start SDKs service in foreground mode when push received;
  await SiprixVoipSdk().setForegroundMode(true);
  In this mode system should allow network access, but it also requires additional permissions.