Vivox: What causes VxAccessTokenInvalidSignature (20122) errors?

When you see a VxAccessTokenInvalidSignature (20122) error, check for the following scenarios:

• Token generation: If you are generating your own tokens, ensure that your token generation follows the directions from the Access Token Developer Guide in the Vivox Developer Documentation. Refer to the section that details how to generate a token on a secure server.
• Credentials: Ensure that your issuer, key, and domain are correct. If you have both sandbox and production keys, ensure that you are using production credentials for the production environment and are using sandbox credentials for the sandbox environment. If you mix credentials, you will receive errors.
• Channel names and usernames: Ensure that channel names and usernames follow the guidelines specified in the Access Token Developer Guide in the Vivox Developer Documentation. Refer to the section that details access token identifiers, which covers usernames, channel names, issuers, and token keys.

If you have checked all of the above and are still experiencing the issue, report this through the forums, or if you have a paid support plan, by using a support ticket.