Skip to main content
Español 日本語 한국어 简体中文
Search our knowledge base

Vivox: Channel join consistently goes to "Disconnected" rather than "Connected"

Dylan Douglas
  • Updated

Scenario

When joining channel using a Vivox Access Token on Unity, the channel status goes from "Connecting" to "Disconnecting" to "Disconnected" without ever entering the "Connected" state.  No error message is logged indicating the cause.

Resolution

This issue is typically caused by incorrect claims of the Vivox Access Token, but no error message was displayed indicating that cause in certain versions of the Vivox SDK.

Update the Vivox SDK

The "Access Token Claims Mismatch,20123" error message is now displayed starting with the following Vivox SDK versions:

  • Unity 15.1.230000-pre.1
  • Unity 16.2.0

Please make sure you are on these or later versions of the Vivox SDK before continuing.

Check Vivox Access Token Claims

Ensure your token follows the following formula:

sip:confctl-d-{issuer}.{channelName}{3dChannelProperties}@{domain}

Example: 

sip:confctl-d-myissuer.lobby!p-32-1-1.000-1@mtu1xp.vivox.com

In most cases, the issue occurs when the 3D channel properties is missing from the Vivox Access Token, but can occur from any channel mismatch.

Related articles