ghjansen
commented
7 years ago Hi @atsakiridis Here is new data about the tests from tadhack environment. olympus-99.zip
Open ghjansen opened 7 years ago
ghjansen
commented
7 years ago Hi @atsakiridis Here is new data about the tests from tadhack environment. olympus-99.zip
ghjansen
commented
7 years ago Everything runs normally when using Firefox, but when using Chrome the issue still the same.
ghjansen
commented
6 years ago 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.
ghjansen
commented
6 years ago 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
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 https://github.com/RestComm/restcomm-android-sdk/issues/536#issuecomment-285644668 .
Here is the console log from chrome: 54.90.157.242-1489412808634.txt