Is the Cloudflare STUN server free to use, similar to Google's STUN server?
Is
stun.cloudflare.com:3478 a free server to use, like stun.l.google.com:19302?19 Replies
since its linked on https://developers.cloudflare.com/calls/turn/ id think its covered under this sentence
Using Cloudflare Calls TURN service is available free of charge when used together with the Calls SFU. Otherwise, it costs $0.05/real-time GB outbound from Cloudflare to the TURN client.but not completely sure
Yes, I read that, but I am not using it with Cloudflare calls. I just use it to get the optimal route and then establish a peer-to-peer connection. Once the peer-to-peer connection is established, I no longer need a STUN server.
it sounds like even if they do decide to charge for that, it would be extremely cheap for your usage.
im not super familiar with stun/turn but is the stun server authenticated? if its not then id assume itd have to be free
nope i still connect with
stun.cloudflare.com:3478 without the need of username and password
but i am worried about if they get me rate limitedhmm 🤔 yeah it would be good for them to be clear about this
ya
I'll ask someone at cloudflare and see if they can ask the team to clarify
thx
@James the Calls team confirmed that STUN is free to use, unlimited and unauthenticated, only TURN is not. They'll update the documentation soonish
Thx that’s great
@James , what is your use case?
I am using it as fallback if stun is not able to make a connection I use tun server then
Is it webRTC?
Yup
I'm guessing something broke for you sometime yesterday or the day before?
Yup because I only give stun server when I give both the issue is fixed
I am tracking down a similar issue with webRTC openai realtime api.
I think you only provide stun in ice config
I still haven't fully tracked down my issue. I was working on my project and it just stopped working. I checked other projects and they stopped as well. I have narrowed down to possibly needing a STUN or openai has enforced the ephemeral token rather than the direct token. Still tracking down rn.
I should note that a stripped down version works fine locally
@James Are you using the realtime api?