VideoRoom Room Cascading with Turn

We have an architecture where we have edge devices on prem and a k8s cluster in the cloud. The k8s cluster has Janus and STUNner and the edge device has a janus instance as well. In certain cases we want to publish edge publishers to the cloud instance and vice versa. This prevents the need from outside entities needing access to an edge system that is behind a strict firewall. Does the ip in the add_remote_publisher response take into account a turn setup? Or does Janus have to be directly exposed?

{
        "videoroom" : "success",
        "room" : <same as request>,
        "id" : <unique ID associated to the new remote publisher>,
        "ip" : "<host address to use to send RTP associated to this remote publisher>",
        "port" : <port to use to send RTP associated to this remote publisher>,
        "rtcp_port" : <port to latch to in order to receive RTCP feedback from this remote publisher>
}

Thanks,

Rick

After digging into this more I realized the cascading process is an rtp_forwarder and not webrtc based which turn isn’t used. So a better question, any plans to be able to do cascading via a webrtc connection in the future?