Cannot start or accept audio calls

[damianoazzolini]

When i try to start an audio call, nothing happens: the small spinner spins for one second and then nothing happens. Similarly, when someone sends me an audio call request, when i click on join nothing happens.
I use vscode on wsl and this is the configuration

Version: 1.46.0 (user setup)
Commit: a5d1cc28bb5da32ec67e86cc50f84c67cc690321
Date: 2020-06-10T09:03:20.462Z
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

I've tried to export the log but Live share: Export logs creates an empty file.

In the previous case, both computers run vscode on wsl. However, when i try to reproduce it using a virtual machine running debian and the last version of vscode, if vscode on debian starts the call, the caller pops up in the list but not the receiver. If vscode on windows (wsl) calls first, nothing happens as above.

[mill1000]

Having a similar issue on Windows 10 with WSL.

Here's the some log output that might be useful.

[LiveShareAudio I] Trace log: /tmp/VSFeedbackVSRTCLogs/20200624_204812_15930316928780_VSLSAudio.log
[ExternalAppCallingService I] Calling stack will be lazy loaded
[LiveShareAudio V] Current state: Initializing, Action: InitializeDone
[LiveShareAudio I] Can Collect PII: false
[LiveShareAudio I] LiveShare session changed:
[LiveShareAudio V] Current state: NoLiveShare, Action: LiveShareSessionStarted
[LiveShareAudio V] Current state: LiveShareWithoutAudio, Action: AttemptConnectAudio
[ExternalAppCallingService E] [JsonRPC] Dispose start
[ExternalAppCallingService E] [JsonRPC] Dispose end
[ExternalAppCallingService I] Getting SkypeToken
[LiveShareAudio V] Current state: AudioConnecting, Action: AudioDisconnected
[ExternalAppCallingService E] Electron closed unexpectedly: code:127 signal:null
[ExternalAppCallingService I] Initializing SlimCore
[ExternalAppCallingService E] Failed to initialize electron app: Call initialization failed Error: Call initialization failed
at ExternalAppCallingService. (/home/tk891973/.vscode-server/extensions/ms-vsliveshare.vsliveshare-audio-0.1.85/out/calling/externalAppCallingService.js:218:27)
at Generator.next ()
at fulfilled (/home/tk891973/.vscode-server/extensions/ms-vsliveshare.vsliveshare-audio-0.1.85/out/calling/externalAppCallingService.js:4:58)
at processTicksAndRejections (internal/process/task_queues.js:89:5)
[LiveShareAudio W] startOrJoinAudio: cancellation on connect to audio: Call initialization failed
[LiveShareAudio V] Current state: LiveShareWithoutAudio, Action: AudioConnectionFailed
[LiveShareAudio W] No transition exists for action: AudioConnectionFailed

[mill1000]

This looks similarly related to issue #3028. Following steps from there I determined that I could not run the packaged electron in my WSL environment.

I had to install the additional dependencies like so:

 sudo apt-get install libnss3 libgtk-3-0 libxss1 libasound2

at which point I was able to run electron and begin a audio call!

EDIT. I was able to begin a call but there's no recognized sound devices. Will have to investigate further if WSL can access sound devices or not.

[mill1000]

Looks like there's not native sound support on WSL. There is a work around though.

Enable audio in WSL
This trick uses a PulseAudio client on the WSL side, and a PulseAudio server on the Windows side to route audio via TCP.
Quick how-to here: https://wiki.ubuntu.com/WSL#Enabling_Sound
Details are here: microsoft/WSL#486

Verify Audio Devices
I also installed pavucontrol and alsa-utils. With pavucontrol I was able to confirm that PA saw my Windows sound devices. I then used aplay and arecord to verify that ALSA saw the PA record and playback devices.

After rebooting my WSL instance I was able to see audio devices in LiveShare and successfully do an audio call (to myself).

[lostintangent]

Closing this as a duplicate of #3359.