Documentation

​
​

Development

User Acquisition

Monetization

Industry

Vivox Core SDK

Vivox Core SDK

Vivox
​
​
Vivox Core SDK
  • Overview
  • Before you begin
  • Get started
    • Integration guide
      • Phase 1: Planning and organization
      • Phase 2: Implementation
      • Phase 3: Testing
        • Smoke test
        • Feature checkpoints
    • Quick start guide
  • Release notes
  • Developer Guide
  • Reference
  • Privacy overview
  1. Vivox Core SDK documentation

Smoke test

What to look for when smoke testing Vivox.
Read time 1 minute
Last updated 8 months ago

When a user has voice enabled, UI elements indicate channel join state and what options (for example, mute, push-to-talk) are active and usable. Otherwise, UI elements aren't active or indicate that a user isn't in a channel.
  • UI elements
    • User is connected to a Vivox voice network but is not in a channel or call.
    • User is in a channel or call, and they see a personal speaking indication or for another person.
    • Microphone is active or inactive (muted).
    • Push-to-talk is active or inactive.
  • UI function controls
    • Selecting a channel to enter gets the user to the expected channel.
    • If mute for me is implemented, check for persistence by restarting the game.
    • Entering or leaving a channel works.
    • Choosing a different capture (microphone) or render (loudspeaker) device correctly updates the UI.
  • Logging checkpoints
    • Vivox voice network connection, login, and session creation.
    • Channel activity: for example, speaking indications.
    • Capture device or render device changes: for example, volume or changing devices.
    • Vivox connectivity is monitored. For example, an error is thrown when voice unexpectedly disconnects or logouts.

Copyright © 2026 Unity Technologies
LegalPrivacy PolicyCookiesDocumentation Terms of UseDo Not Sell or Share My Personal InformationYour Privacy Choices (Cookie Settings)

"Unity", Unity logos, and other Unity trademarks are trademarks or registered trademarks of Unity Technologies or its affiliates in the U.S and elsewhere (more info here). Other names or brands are trademarks of their respective owners.

Some pages are machine-translated for convenience, and may contain inaccuracies. In the event of conflicting information, the English version is authoritative.


    Report a problem with this page