We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When video calling +1234, the call flow apparently happens normally except for the fact that there is no audio heard on client side.
+1234
Environment: latest Restcomm + latest Olympus 2 + XMS.
It was mentioned the possibility of this issue being related to RestComm/restcomm-android-sdk#536 (comment) .
Here is the console log from chrome: 54.90.157.242-1489412808634.txt
The text was updated successfully, but these errors were encountered:
Hi @atsakiridis Here is new data about the tests from tadhack environment. olympus-99.zip
Sorry, something went wrong.
Everything runs normally when using Firefox, but when using Chrome the issue still the same.
Chrome waits for first video frame before doing any media playback. Seems a mechanism for syncing audio & video streams.
I think until successful decoding of video frame(at least one), chrome won't start audio playback to avoid lip sync issue.
https://groups.google.com/forum/#!searchin/discuss-webrtc/no$20audio$20video%7Csort:relevance/discuss-webrtc/NGxTD3H68o0/N2GbTnyHAgAJ
Discussion related to Chrome sensitiveness for codec names:
Bug: https://bugs.chromium.org/p/webrtc/issues/detail?id=7027
Fix: https://chromium.googlesource.com/external/webrtc.git/+/c964d0b3fa6b3d7a5b51a1d4e8ebfeec56e19dc0
atsakiridis
No branches or pull requests
When video calling
+1234
, the call flow apparently happens normally except for the fact that there is no audio heard on client side.Environment: latest Restcomm + latest Olympus 2 + XMS.
It was mentioned the possibility of this issue being related to RestComm/restcomm-android-sdk#536 (comment) .
Here is the console log from chrome: 54.90.157.242-1489412808634.txt
The text was updated successfully, but these errors were encountered: