Audio Not Starting after switching from main subsession to subsession

Description
The behaviour is such that, when a user joins the meeting, the audio starts normally and works fine. But when the user joins the subsession, the audio does not start, instead it keeps returning a ‘REQUEST TIMEOUT’ error on the console.

The same happens when the user returns from the subsession to join the main session, the audio would not just start and returns a ‘REQUEST TIMEOUT’ error.

Please is there any reason for this unending loading/request timeout error? And why it works when the user joins the meeting, but when switching to/from the subsessions, it just doesn’t work?

Browser Console Error
REQUEST TIMEOUT

Which Web Video SDK version?
I recently upgraded to the latest SDK version 1.9.5.

Video SDK Code Snippets

const onMicrophoneClick = useCallback(async (action: string) => {
        if (isStartedAudio) {
            if (action === 'unmute' && isMuted) {
                await mediaStream?.unmuteAudio();
                setIsMuted(false);
            } else if(action === 'mute' && !isMuted) {
                await mediaStream?.muteAudio();
                setIsMuted(true);
            }
        } else {
            await mediaStream?.startAudio();
            setIsStartedAudio(true);
            await mediaStream?.muteAudio();
            setIsMuted(true);
        }
    }, [
        isMuted,  
        isStartedAudio, 
        mediaStream, 
        zmClient
    ]);

To Reproduce(If applicable)
Steps to reproduce the behavior:

  1. Start the meeting
  2. Create and open subsessions
  3. Join subsession as participant (not as host)
  4. See error

Device (please complete the following information):

  • Browser: Chrome

Hey @godwin.owonam

Thanks for your feedback.

Sorry for the inconvenience caused. We have identified the root cause of the issue and are working on resolving it promptly.

Thanks
Vic

Hey @godwin.owonam

We have rolled out the Video SDK Web 1.9.8, the issue is fixed in this version.

Thanks
Vic

Thanks @vic.yang
I will upgrade and let you know.

Thanks @vic.yang. This issue was fixed after the upgrade.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.