For Workes & Pages, what is the name of the domain?
``
What is the issue or error you’re encountering
Support Alternative Ports in TURN API for ICE URLs
What are the steps to reproduce the issue?
The TURN API currently returns ICE URLs with only the primary port. I need a way to provide both primary and alternative ports to WebRTC peer connections.
Problem: The TURN API response only includes the primary port, which limits the flexibility of WebRTC peer connections. Providing only the primary port may lead to connectivity issues in certain network conditions where an alternative port could be used as a fallback.
Request: Add an option in the TURN API to include both primary and alternative ports in the response.
Workaround Consideration: Alternatively, should the client handle this by modifying the ICE URLs manually (e.g., through string replacement)? This would involve processing the URL as a string and replacing the primary port with an alternative. While this approach could work, it adds complexity to the client code and increases the risk of maintenance challenges or errors. It is presented as a workaround rather than the preferred solution because direct support from the API would provide a more reliable and consistent approach.
Having a direct way to retrieve both ports from the API would reduce manual client-side modifications, improve code maintainability, and ensure consistent configuration.