Avaya Client SDK

< Back to Package Overview

iOS application behaviour during background state

The iOS application during background state gets suspended by the operating system. Any incoming network notification is available to the user only after the application comes back to foreground state. This issue is seen when the iOS application use the Client SDK library which is built using the iOS SDK 10 or higher.

Once your application has been invoked by the user, the application is in foreground state. Either by user action or system action, your application can go to background state. The operating system controls the system resource usage of the application during the background state.

You will see your application is suspended by the Apple's iOS operating system, when it is moved to background state. Hence all the incoming notification from the servers such as incoming call or incoming messages are not handed over to Client SDK for processing. Under this background state your application is idle and no notifications are sent to user.

The communication with the call server is restored when user brings back your application to screen (foreground state).

Use case Sample App behaviour
Making outgoing P2P call in foreground state The outgoing P2P call succeed. Outgoing P2P call can be made only when the application in the foreground state.
Making outgoing conference call in foreground state The outgoing conference call succeed. Outgoing conference call can be made only when the application in the foreground state.
Receiving incoming P2P call in foreground state Incoming call alert notification sent to user.
Receiving incoming P2P call in background state Incoming call alert notification is not sent to user.
Receiving incoming text message in foreground state Incoming message alert notification sent to user.
Receiving incoming text message in background state Incoming message alert notification is not sent to user.
Contact addition in the foreground state Contact addition succeed and the contact list gets updated immediately.
Contact addition by admin in background state Contact addition succeed but the contact list gets updated only after the application comes back to foreground state.
Placing the application in background state while call is ongoing. Audio/Video data is not sent from the CSDK. Media gets restored after the application comes back to foreground state. Registration error seen at first and cleared in retry.