We should add properties for relay-traversal to the mediasignalling interface. 1. Proxy type ("socks5" or "http-connect") 2. IP address 3. port 4. username 5. password and I guess in the new caps-o-tron world, you also want the matching capabilities.
Could this be done by extending RelayInfo, or is it conceptually separate?
I think that they are conceptually separate. A relay is normally somewhere on the public internet provided by your provider. While a proxy is between the local network and the internet (you would normally go through the proxy to get to the relay). And you normally have a single proxy I guess? I would just add 5 properties (proxy- type, ip, port, username, password), and just copy them as-is (with ip addresses resolved) from the connection manager startup properties.
Is this fixed in Call? If so, WONTFIX; if not, please tag appropriately.
Call doesn't do this, but I think the general consensus is that the client should find its own proxy using GLib's new GProxyResolver. I'll add GProxyResolver support somewhere below.. Either tp-fs or directly inside libnice ?
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.