According to the docs, announcedIp (or announced_ip in Rust) in TransportListenInfo can be a IPv4 or a IPv6. However, it should be possible that it's also a hostname since that's a very common use case in WebRTC app deployments.
Funny thing is that it works perfect in Node if we pass announcedIp: "some-domain.org" (since nothing in Node or C++ validates whether it's a IP or not). However:
Docs in the website are wrong (they state that it must be a IPv4 or IPv6).
Rust is not ready for this since the type of announced_ip has type Option<IpAddr>.
@nazar-pc can we just make it a string? The worker and Rust side doesn't need to do absolutely anything with this value other than honoring it in transport.ice_candidates.
According to the docs,
announcedIp(orannounced_ipin Rust) inTransportListenInfocan be a IPv4 or a IPv6. However, it should be possible that it's also a hostname since that's a very common use case in WebRTC app deployments.Funny thing is that it works perfect in Node if we pass
announcedIp: "some-domain.org"(since nothing in Node or C++ validates whether it's a IP or not). However:announced_iphas typeOption<IpAddr>.transport.ice_candidates.