You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In an incoming call scenario, when the iOS app in background or in locked screen mode, we are getting the initial PushKit notification ( the ghost call) and in between getting the real call, the Sofia stack is creating multiple sockets which are left dangling and we have 200% CPU usage and then crash which seem to user like call has terminated.
In a very simplified form this is what is happening
PushKit comes.
Stack tries to make socket to the non-existent call
Application via stack tells server “I’m here send me SDP”
Stack makes new socket every 500ms until SDP comes from server - this could be 5 seconds (or more) so we have ten sockets open
We get the SDP and make a proper socket connection. We now have one socket that is doing a call and the rest are still there doing their socket things chewing up CPU.
Appreciate how we can handle this when we get incoming call on IOS via PushKit?
The text was updated successfully, but these errors were encountered:
In an incoming call scenario, when the iOS app in background or in locked screen mode, we are getting the initial PushKit notification ( the ghost call) and in between getting the real call, the Sofia stack is creating multiple sockets which are left dangling and we have 200% CPU usage and then crash which seem to user like call has terminated.
In a very simplified form this is what is happening
Appreciate how we can handle this when we get incoming call on IOS via PushKit?
The text was updated successfully, but these errors were encountered: