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
{{ message }}
This repository has been archived by the owner on Jan 24, 2018. It is now read-only.
The current ostel architecture depends on host nat traversal to properly establish RTP streams between two endpoints. This raises bandwidth requirements on the server side, due to proxying the encrypted bits.
It would be a nice feature to allow RTP streams between two endpoints directly, without server-side proxy.
Coturn is an active project with the primary objective to provide a single server which supports the myriad NAT traversal methods. I installed it on ostel.co and did some tests. Two clients connected properly though they failed to exchange UDP packets with each other, rather falling back to the server-side proxy.
This is using the default configuration. I would like to change the configuration or test on a non-production environment. If successful, this network architecture would be similar to RedPhone's backend.
The text was updated successfully, but these errors were encountered:
The current ostel architecture depends on host nat traversal to properly establish RTP streams between two endpoints. This raises bandwidth requirements on the server side, due to proxying the encrypted bits.
It would be a nice feature to allow RTP streams between two endpoints directly, without server-side proxy.
Coturn is an active project with the primary objective to provide a single server which supports the myriad NAT traversal methods. I installed it on ostel.co and did some tests. Two clients connected properly though they failed to exchange UDP packets with each other, rather falling back to the server-side proxy.
This is using the default configuration. I would like to change the configuration or test on a non-production environment. If successful, this network architecture would be similar to RedPhone's backend.
The text was updated successfully, but these errors were encountered: