We don't support 3 party audio now

Hello,

I am using Zoom.init and Zoom.join etc. to put a participant into the web conference. This has worked well for years. We have always used 3rd party telephone and when the participant joined, they simply saw the shared screen.

However, now on joining the conference, Zoom displays an overlay stating:

We don't support 3 party audio now

Is there any way to stop this (any of the audio options) from displaying? My code is basically:

 ZoomMtg.generateSignature({
    meetingNumber: qs.id,
    apiKey: qs.key,
    apiSecret: qs.sec,
    role: 0,
    success(res) {
        console.log('signature', res.result);
        ZoomMtg.init({
        debug: false,
    showMeetingHeader: false,
    disableInvite: true,
    disableCallOut: true,
    audioPanelAlwaysOpen: false,
    isSupportAV: false,
    disableJoinAudio: true,
        leaveUrl: 'http://www.zoom.us',
            success() {
                ZoomMtg.join(
                    {
                        meetingNumber: qs.id,
                        userName: qs.name,
                        signature: res.result,
                        apiKey: qs.key,
                        userEmail: qs.email,
                        passWord: '',
                        success() {
                            $('#nav-tool').hide();
                            console.log('join meeting success');
                        },
                        error(res) {
                            console.log(res);
                        }
                    }
                );
            },
            error(res) {
                console.log(res);
            }
        });
    }
});

Hey @rayjbell, thanks for posting and using Zoom!

Let me look into this and get back to you. (ZOOM-137285)

Thanks,
Tommy

Thanks Tommy,

For you, and everyone having the same issue, I found that if I added the following CSS to the page, this removes it:

.diaout-layer { height: 0; }

This took a lot of working out, but this does the trick.

Thanks,

Ray

1 Like

Hey @rayjbell,

Thanks for sharing a workaround. :slight_smile:

I will get back to you once we find the root cause.

-Tommy