Skip to content

Conversation

@stefankiesz
Copy link
Contributor

@stefankiesz stefankiesz commented Nov 3, 2025

Description of changes:

  • Added a switch to the UI to control whether to use dual-stack KVS endpoints.
  • Improved the spacing of existing UI elements.
  • Tested (ran the other peer on the JS Test Page) :
    • e2e WebRTC connection using a pre-prod dual-stack control plane endpoint with the JS Test Page as the other peer.
    • e2e WebRTC connection with the switch set to "Legacy", checking for regressions when connecting to the legacy endpoint.
    • e2e WebRTC connection with the switch set to "Dual-stack", using the prod dual-stack endpoint, which currently returns legacy signaling endpoints.
image

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@stefankiesz stefankiesz requested review from YPandas, Copilot, sirknightj and unicornss and removed request for Copilot November 3, 2025 20:15
Copy link
Contributor

@sirknightj sirknightj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wondering if we can move the endpoint setting to maybe an "Advanced" tab


let kvsStunUrlStrings: [String]
if self.useDualStackKvsEndpoint {
kvsStunUrlStrings = ["stun:stun.kinesisvideo." + self.regionName.text! + ".api.aws:443"]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's also CN variant as well

@stefankiesz stefankiesz changed the title Prepare for Dual-Stack Support - Control Plane Endpoint Dual-Stack Endpoint Support Dec 5, 2025
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.

3 participants