>> I would still want the application to fall back to using a proxy if >> all hole-punching attempts failed. And what sadly is not obvious to >> the implementers: I would want the applications to DETECT that it >> failed, i.e. when there's no rtp packet for a second you send out some >> standard SIP event: INFO fuck-why-can't-you-say-something and then >> retry with proper rtp. > > Except from the lousy port-guessing-algorithm, this should work here > already[2].
Sure, most DHT implementations work perfectly for signalling, as long as there are enough people without NAT helping out. But I don't see anything about the actual rtp stream there. Does it get sent over DHT, too? I see that the DHT is slowed down deliberately. That together with uncontrollable commonly bad-quality home internet connections is making me fear bad latencies and packet drop just as with tor.
