-
Notifications
You must be signed in to change notification settings - Fork 33
Freeswitch connects to local IP address #106
Comments
I read #28 that this is due to the usage of Apache reverse proxy. And there is a way to fix it with correct directive. Currently, I am using exactly the same directive as in the tutorial. Is there anything I need to update to that? Thank you ! |
I've tried to fix the issue with no luck. My machine is setup like this: On my router, I opened port 443,3008,5060,5066,8888,16384-32768 (a lot are not necessary, just open them while I am debugging this issue) On my Ubuntu machine, ufw is disabled On my Apache web server, I used the configuration in the tutorial
I am still seeing ICE 1007 Error and my Freeswitch webrtc is trying to connect to 10.0.0.2 |
It's seems to be a conflict beetwen apache proxy and bbb-docker_https_proxy_1. With apache running I have this error in the scripts/compose logs -f
with apache stopped,
and there is no ICE 1007 Error using my client but original websites from host are unreacheable. I will try to use bbb-docker_https_proxy_1 to distribute original websites As I can use WebRTC fron WAN to Server 192.168.1.20, viewing local IP address was not the problem for me. |
My server's local IP address is 10.0.0.2
When I am connecting to my server using home wifi, everything works because 10.0.0.2 can be accessed.
When I am connecting from outside network, part of the webrtc connection is still doing it at 10.0.0.2 and I now have the ICE1007 Error.
Does anyone have any insight on what might be going womrong on my configurations?
The text was updated successfully, but these errors were encountered: