Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Voice chat #1439

Open
0-x-2-2 opened this issue Feb 23, 2023 · 3 comments
Open

Voice chat #1439

0-x-2-2 opened this issue Feb 23, 2023 · 3 comments
Assignees
Labels
enhancement New feature or request no-issue-activity

Comments

@0-x-2-2
Copy link
Contributor

0-x-2-2 commented Feb 23, 2023

You can get Vivox to attempt to connect with this snippet on the server.

      server.sendData(client, "Voice.Login", {
        clientName: '[issuer or Vivox admin username]', // fload02985-Fu36-dev-Admin
        sessionId: '[password or jwt]', // [vivox admin password works here]
        url: 'https://mt1s.www.vivox.com',
        characterName: '.[issuer].[username].' // fload02985-fu36-dev
      });

The issue is that this will call vx_req_account_login_create with the Vivox API but if voice still works on Z1 BR, slightly newer versions of the Vivox libraries are still ABI compatible and can be replaced then we just need packet decrypted dumps of Voice.Login and Voice.JoinChannel but the best option would most likely be hooking and redirecting the vx_req_account_login_create to the modern JWT login flow unless we can find documentation for the vx_req_account_login_create login flow but it is very hard to get it working as it seems to throw an internal error when using it with my account type.

I heard that some people got voice working on the 2015 build but I don't see code related to it anywhere.

Here are some tools useful for the JWT token generation flow:
https://github.com/LeafChage/vivox-token
https://cdn.discordapp.com/attachments/1069493856724320336/1071461084092964894/vivox_admin.py

@0-x-2-2 0-x-2-2 added the enhancement New feature or request label Feb 23, 2023
@Z1Meme Z1Meme added this to the v0.30.0 milestone Nov 2, 2023
@Z1Meme
Copy link
Collaborator

Z1Meme commented Nov 2, 2023

Should be added in v0.30.0 using a separate voice system than vivox

@Z1Meme Z1Meme self-assigned this Nov 2, 2023
@QuentinGruber QuentinGruber removed this from the v0.30.0 milestone Jan 8, 2024
Copy link

github-actions bot commented Mar 9, 2024

Stale issue message

Copy link

github-actions bot commented May 9, 2024

Stale issue message

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request no-issue-activity
Projects
None yet
Development

No branches or pull requests

3 participants