You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Some users will have problems installing and configuring an ICE Server or probably can't pay for that.
Describe the solution you'd like
Embedding the requirements for Audio and Video Calls can be a plus to this application.
Describe alternatives you've considered
Another option we can consider is create a separated project under tinode that cover the ICE requirement, with easy integration.
Additional context
Audio and Videocalls will be a killer feature, we can work creating a better experience deploying the solution.
The text was updated successfully, but these errors were encountered:
Would be nice to have some prepared stun / turn for Tinode. I added config with a free stun server that works for me.
Instead of integrate / embedding stun / turn I think it would be better to have an example how to run own stun / turn servers as docker containers in a stack with tinode?
But I'll take a look into coturn or something else in the future with a little bit more time. Any suggestion about a good / simple self hosted stun / coturn service?
If you are not requesting a feature, please post to https://groups.google.com/d/forum/tinode instead.
Is your feature request related to a problem? Please describe.
Some users will have problems installing and configuring an ICE Server or probably can't pay for that.
Describe the solution you'd like
Embedding the requirements for Audio and Video Calls can be a plus to this application.
Describe alternatives you've considered
Another option we can consider is create a separated project under tinode that cover the ICE requirement, with easy integration.
Additional context
Audio and Videocalls will be a killer feature, we can work creating a better experience deploying the solution.
The text was updated successfully, but these errors were encountered: