edgegap-eos-voice

Topics in the source

• EOS Voice on Edgegap dedicated servers (Unreal Engine)
• How it works (explain this to the developer in two sentences, not more)
• How to work
• Phase 0: Preconditions
• Phase 1: EOS Developer Portal (the developer does this)
• Phase 2: Drop in the code
• Phase 3: Configure
• Phase 4: Local test, two clients on one PC

Goal: players in a match talk to each other through EOS Voice, in rooms the game server decides (whole match, or per matchmaker team), and a player who leaves the server leaves voice. The job is done when two clients on an Edgegap deployment hear each other, proved by logs, not when it compiles. Verified on UE 5.5.4 from source (EOS SDK 1.16 bundled) with the Edgegap Unreal sample: two Windows clients matched by the Edgegap matchmaker onto one Linux deployment, in the same team room, hearing each other, and the leaving player removed from the room. 1. The client logs into EOS Connect with a device ID (no Epic account) on the EOSVoiceChat plugin's own EOS platform, then sends the server its Product User ID (PUID) and an ID token through a replicated UEdgegapVoiceComponent. 2. The server verifies the ID token (RS256, Epic's JWKS), picks the room from the player's IP and the matchmaker's MMTICKET variables, calls POST https://api.epicgames.dev/rtc/v1/{deployment}/room/{room} with the player's IP, and sends the token to that player only. 3. The client joins with IVoiceChat::JoinChannel. On logout the server calls DELETE …/participants/{puid}, which also revokes the token. The server us

This is an excerpt. Refer to the complete source and its current requirements.