QBCore Frameworkqbcore.netCommunity docs
On this page

6 min read

QBCore Voice Chat Not Working

Test proximity voice, radio and phone calls separately. An animated mouth, a microphone icon or a connected radio display does not prove that another player receives audio. Start with two real clients and a repeatable test rather than replacing several voice resources at once.

This guide references pma-voice 6c9d96ed and qb-radio e8caccf3. The configuration examples are source-reviewed; they are not a claim of successful audio tests on your server. Third-party phones and voice replacements require their own integration contracts.

Evidence to collect

Record the exact pma-voice/qb-radio/phone commits, active voice-related convars, first client/server error, recent changes and which of the three audio paths fails. Note whether the issue affects one client, one network or all players. Keep private Mumble endpoints, player identifiers and voice recordings out of public support logs.

Safe diagnostic

Establish a two-player baseline

Use two clients, preferably on different connections. Put both characters in the same normal game context, close enough for the chosen proximity mode. Verify the intended input/output devices, in-game voice setting, push-to-talk binding, volume and local mute state on both clients.

Have A speak while B listens, then reverse roles. Test a known working microphone outside the game only to rule out the device; that does not prove the FiveM voice transport. Move apart and repeat to distinguish proximity behavior from total audio failure. Record actual audible results, not just HUD indicators.

ResultNext investigation
One client cannot be heard in any modeIts microphone/input/keybind and game connection
Nobody hears proximity voiceCompeting voice resources, audio convars and voice transport
Proximity works, radio failsItem, channel membership, restrictions, radio binding and volume
Proximity/radio work, phone failsPhone's pma call-channel integration and enabled call module
Only a subset of networks failsNetwork path, configured endpoint and relevant client logs
Began after replacing a HUD/phoneNew scripts overriding voice natives or using old integration names

Run only one voice owner

The pma-voice README explicitly warns against running it alongside other voice systems, including vMenu's voice feature. Inspect your active resources and disable the competing voice component on staging, not unrelated vMenu features blindly.

Search custom resources for overrides of NetworkSetTalkerProximity, MumbleSetTalkerProximity, MumbleSetAudioInputDistance, MumbleSetAudioOutputDistance and NetworkSetVoiceActive. A HUD that appears unrelated can still alter voice state. Test removal of one conflicting integration at a time.

Fix

Check convar names, types and audio mode

The following is an explicit native-audio example, not a requirement to overwrite an already working configuration:

setr voice_useNativeAudio true
setr voice_use2dAudio false
setr voice_use3dAudio false
setr voice_useSendingRangeOnly true
setr voice_enableRadios 1
setr voice_enableCalls 1
setr voice_enableSubmix 1

ensure pma-voice
ensure qb-radio

Keep the rest of the recipe's dependencies, including qb-core, in their proper order. Audio-mode options are booleans; the radio/call switches shown here are integer convars. Choose one audio mode rather than enabling native, 2D and 3D simultaneously. The referenced README requires native audio for submix effects.

Set startup convars before starting the relevant resources and perform a coordinated staging reconnect/restart when testing initialization changes. Do not assume changing a default rewrites every connected client's saved settings.

The pinned README calls out these renamed options:

Older nameReferenced current name
voice_defaultPhoneVolumevoice_defaultCallVolume
voice_enablePhonesvoice_enableCalls

Check a phone's actual code for the documented setCallChannel/call integration and cleanup on hangup. The presence of the new convar alone does not migrate a vendor phone's callbacks or state handling.

Radio: check the item and channel contract

In the referenced qb-radio configuration, Config.RadioItem is radio, Config.MaxFrequency is 500, and channels 1–10 are restricted to configured jobs. Confirm both clients have the required item, have joined the same permitted frequency and have sufficient radio volume.

The current restriction shape is a table of job/gang arrays. For example, inside Config.RestrictedChannels:

[1] = {
    jobs = { 'police', 'ambulance' }
},

The configuration describes job access as requiring duty and allows gang-based alternatives through gangs. Compare the server implementation and your deployed config together before changing restrictions. Test an unrestricted frequency permitted by your server first, then test an allowed and a denied restricted-channel user. Never solve a radio problem by granting everyone access to protected channels.

Use qb-radio configuration for the resource reference. IsRadioOn() reports local radio state; it is not proof that packets reach another client.

Keybindings and state inspection

Changing voice_defaultRadio or a proximity-cycle default does not necessarily change a returning player's saved FiveM binding. Inspect the client's Key Bindings → FiveM entries and use the keybinding guide.

For a temporary client-side staging diagnostic, add this to a client script:

RegisterCommand('docs_voice_state', function()
    local state = LocalPlayer.state
    print(('radioChannel=%s callChannel=%s disableRadio=%s'):format(
        tostring(state.radioChannel),
        tostring(state.callChannel),
        tostring(state.disableRadio)
    ))
end, false)

Run docs_voice_state in F8 on each client. The referenced pma state getters use 0 for no radio/call channel. disableRadio is an integer bitmask, not a boolean; Lua treats 0 as truthy. Do not write if state.disableRadio then to infer that radio is disabled. Inspect the exact flags owned by the relevant resource without forcibly clearing them.

Remove the diagnostic after the test. Do not use state values from a HUD as authorization for restricted channels or other server actions.

Network and external Mumble configuration

First determine whether you intentionally use an external voice endpoint. The pma README documents voice_externalAddress and voice_externalPort; stale values can direct clients away from the intended voice server. Do not add an external endpoint as a generic “fix”.

Compare connectivity and logs from affected and unaffected clients against the actual hosting setup. No single extra port rule can be prescribed without that topology. Do not disable the firewall or expose all ports. For focused logging, the referenced voice_debugMode supports basic logging at 1 and more verbose output at 4; enable it briefly on staging, keep logs private and restore it to 0 afterward.

Manual acceptance checks

TestRequired result
Proximity A → B and B → AAudible voice at the intended range; sensible behavior outside it
Radio on a permitted channelBoth directions work, with expected binding and volume
Restricted channelAuthorized user succeeds; unauthorized user remains denied
Item removal/job or duty changeChannel access follows your resource's policy
Phone call and hangupCorrect call participants hear each other; channel membership clears on hangup
Reconnect and resource restartNo lingering channel, muted state or competing voice owner
Returning playerSaved bindings/volume are checked rather than assumed reset

A Cfx.re report from September 2024 describes indicators and mouth movement without reliable received audio. It demonstrates why these audible two-client tests matter; forum suggestions about its cause should not be treated as a universal fix.

Rollback

Restore the previous tested voice/phone/radio commits and convars as one compatible set. Reconnect the two test clients and repeat proximity, radio and call checks. A voice configuration rollback does not require deleting characters or player inventories. Retain any intentional channel permissions and reverse only the diagnosed change.

Sources

Found an issue in this guide?

Send the page URL, the affected example, and a source or reproduction to the site maintainer. For a server or resource problem, use the support guide.

On this page