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
When my Customer Premise Equipment (CPE) obtains its external IP and port through the STUN server(x.x.x.x:3478), it sends this information to my Auto-Configuration Server (ACS).
When my ACS wants to initiate communication with the CPE, it sends a UDP Connection Request (UDP-CR) to the STUN server. The STUN server(x.x.x.x:3478) then forwards this UDP-CR to my CPE.
Upon receiving the UDP-CR, the CPE initiates a TCP connection with my ACS.
Now, I'm wondering if coturn has any features or methods to help forward this UDP-CR for me.
The text was updated successfully, but these errors were encountered:
Hi @gzm2015
I'm not sure I fully understand your setup of what you are trying to achieve but it looks like coturn does not support what you want.
However, you could probably build that yourself by watching created allocations in redis or from logs and then forward them yourself.
When my Customer Premise Equipment (CPE) obtains its external IP and port through the STUN server(x.x.x.x:3478), it sends this information to my Auto-Configuration Server (ACS).
When my ACS wants to initiate communication with the CPE, it sends a UDP Connection Request (UDP-CR) to the STUN server. The STUN server(x.x.x.x:3478) then forwards this UDP-CR to my CPE.
Upon receiving the UDP-CR, the CPE initiates a TCP connection with my ACS.
Now, I'm wondering if coturn has any features or methods to help forward this UDP-CR for me.
The text was updated successfully, but these errors were encountered: