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
I am using stream-webrtc-android version 1.2.2 in my android project and trying to connect an audio call using my turn server. The connection is initially successful, I get COMPLETED state and audio is being transferred but after 40 seconds, the connection state changes to DISCONNECTED->FAILED. A packet capture of my TURN server showed that after 40 seconds the client sends a binding request and server responds with a binding success response, which I assume is the consent request involved in the Ice connection process. In this case the connection should stay alive because server replied with binding success response but it goes to FAILED state.
I have a separate web application as well, which uses the official webRTC library, and I can see that after every 40 second it goes to COMPLETED state after the successful consent requests so this doesn't seem to be a server specific issue.
I request you to kindly help me with this problem.
The text was updated successfully, but these errors were encountered:
Hi @sourish115, the new release, version 1.3.0, is now available and includes the m125 patches. Could you check if this issue still occurs with the updated release?
I am using stream-webrtc-android version 1.2.2 in my android project and trying to connect an audio call using my turn server. The connection is initially successful, I get COMPLETED state and audio is being transferred but after 40 seconds, the connection state changes to DISCONNECTED->FAILED. A packet capture of my TURN server showed that after 40 seconds the client sends a binding request and server responds with a binding success response, which I assume is the consent request involved in the Ice connection process. In this case the connection should stay alive because server replied with binding success response but it goes to FAILED state.
I have a separate web application as well, which uses the official webRTC library, and I can see that after every 40 second it goes to COMPLETED state after the successful consent requests so this doesn't seem to be a server specific issue.
I request you to kindly help me with this problem.
The text was updated successfully, but these errors were encountered: