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

Draft: Calling support #327

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from
Draft

Draft: Calling support #327

wants to merge 4 commits into from

Conversation

rubdos
Copy link
Member

@rubdos rubdos commented Sep 30, 2024

This PR aims to add all the stuff™ necessary to make calls. Could be a lot, could be nothing at all.

@rubdos
Copy link
Member Author

rubdos commented Oct 19, 2024

Rebased up to right before reqwest.

@rubdos
Copy link
Member Author

rubdos commented Oct 22, 2024

Already outdated. signalapp/Signal-Server@cacd4af

@rubdos
Copy link
Member Author

rubdos commented Oct 26, 2024

Already outdated. signalapp/Signal-Server@cacd4af

Now we're ahead of Signal Android and Signal iOS 😅

@rubdos
Copy link
Member Author

rubdos commented Nov 16, 2024

Tested, both end points work.

v1:

TurnServerInfo {
  username: "XXX",
  password: "YYY",
  hostname: Some("turn3.voip.signal.org"),
  urls: ["turn:turn3.voip.signal.org"],
  urls_with_ips: ["turn:34.1.15.80", "turn:34.1.15.80:80?transport=tcp", "turns:34.1.15.80:443?transport=tcp", "turn:35.214.194.0", "turn:35.214.194.0:80?transport=tcp", "turns:35.214.194.0:443?transport=tcp", "turn:[2600:1901:8120:e0:0:1d:0:0]", "turn:[2600:1901:8120:e0:0:1d:0:0]:80?transport=tcp", "turns:[2600:1901:8120:e0:0:1d:0:0]:443?transport=tcp", "turn:[2600:1900:4060:4603:0:24:0:0]", "turn:[2600:1900:4060:4603:0:24:0:0]:80?transport=tcp", "turns:[2600:1900:4060:4603:0:24:0:0]:443?transport=tcp"] }

v2:

[
  TurnServerInfo {
    username: "AAAA",
    password: "BBBB",
    hostname: Some("turn3.voip.signal.org"),
    urls: ["turn:turn3.voip.signal.org"],
    urls_with_ips: ["turn:34.1.15.80", "turn:34.1.15.80:80?transport=tcp", "turns:34.1.15.80:443?transport=tcp", "turn:35.214.194.0", "turn:35.214.194.0:80?transport=tcp", "turns:35.214.194.0:443?transport=tcp", "turn:[2600:1901:8120:e0:0:1c:0:0]", "turn:[2600:1901:8120:e0:0:1c:0:0]:80?transport=tcp", "turns:[2600:1901:8120:e0:0:1c:0:0]:443?transport=tcp", "turn:[2600:1900:4060:4603:0:24:0:0]", "turn:[2600:1900:4060:4603:0:24:0:0]:80?transport=tcp", "turns:[2600:1900:4060:4603:0:24:0:0]:443?transport=tcp"]
  }
]

Things to note: username and password seem to follow a pattern. Both were distinct, so I suppose they're generated on the fly. Username seems like a versioned unix timestamp with some other number behind it (unixts:other-number:#01), and the password looks like a base64 encoded string. These things can probably be inferred from the server source code. :-)

The IP addresses mentioned in the answers are what you get by resolving the turn3.voip.signal.org DNS name.

Android moved away, so we can safely assume the new endpoint is the intended new version.
@rubdos
Copy link
Member Author

rubdos commented Nov 16, 2024

Already outdated. signalapp/Signal-Server@cacd4af

Android moved on: signalapp/Signal-Android@47300bbd563

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant