sean t
will be in next update 
yes on .net bindings - I haven't changed any other code - just having these ffmpeg dlls loaded in the same app domain causes it - it's like webrtc is...
yeah i know that, it's what i'm doing and it's been working fine for well over a year, it's just the new build of ffmpeg is built with pthread support...
i setup a coturn instance on my network, added no-udp to the config file and forced TCP with the ice server configuration and set iceTransportPolicy to relay and i've been...
Thanks for responding. Wireshark is detecting this as CLASSIC-STUN. I'm wondering if pion supports that or not? When i try the ubuntu stun test client on googles stun servers it...
OK it looks like i've run into Compatability notes [RFC 5389](https://tools.ietf.org/html/rfc5389) obsoletes [RFC 3489](https://tools.ietf.org/html/rfc3489), so implementation was ignored by purpose, however, [RFC 3489](https://tools.ietf.org/html/rfc3489) can be easily implemented as separate package....
erghhh looks like we needed to update the models for their api - have pushed an update
i think probably you downloaded the older version might need to wait a bit for the cache to update 
If it was using the new code you'd be getting an object reference error or an error deserializing the response not a definition error. You'd only get that same error...
closing this as haven't heard back..