Mobile Native demo - Communication initiate takes quite a long time before getting video from another end

[KerwinMa]

I tried both android and iPhone, both are slow for the initiation process. Steps are:

1. start up the node server (start turn/stun server if use local server. I tried both and both have the same issue.)
2. connect to a room name from peer A, the server will say a peer joined
3. connect to the same room from peer B, the sever will say another peer joined the same room
4. click Call from one peer
5. and after about some seconds (more than 10 seconds), both peers have video working

I put this issue here, one reason is that to test with web browsers are working fine. It will be connected the time click Call.

Not sure if this is a known issue. Please advise. Thanks.

[superdump]

On iOS in the NativeDemo app, fixing https://github.com/EricssonResearch/openwebrtc-ios-sdk/issues/2 should help a bit. On both Android and iOS, fixing https://github.com/EricssonResearch/openwebrtc/issues/186 should help. However, it is not uncommon that the time between steps 4 and 5 is something towards 10s. That's not to say there are not things to fix here, there may well be and we will be looking into that more closely.

For example, see the interesting non-standard thing WhatsApp is doing to speed up call startup time: https://webrtchacks.com/whats-up-with-whatsapp-and-webrtc/

[stefanalund]

ICE trickle now supported: https://github.com/EricssonResearch/openwebrtc-ios-sdk/pull/45. Closing.

[xelven]

@stefanalund I think this should not close, even the ICE trickle supported but still depend on 2 things below:

1. all the ICE candidates priorities are same issue. https://github.com/EricssonResearch/openwebrtc/issues/522
2. the logic in sdk, it will waiting the candidates generated then send answer.

lets discuss about this.

[xelven]

ref: https://github.com/EricssonResearch/openwebrtc-ios-sdk/issues/67