-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SIP not working when running homeassistant without host networking #10
Comments
I just tried binding to |
I've added the bind to |
Hi, I'm having this same issue (posted on Discord and was pointed here). I (kinda) understand the docker networking, but I'm confused as to why the container can't bind to 192.168.1.10 - in my case, I can ping the calling IP, and even TCP connect to it - so this just routes though docker out to the LAN (outbound ports don't need to be mapped like inbound). I'm going to try to change the .py file as per above and see if that works. |
So, I get a call connecting now, but no voice data coming though so I guess that's the port not getting though. |
I think this is happening because the address (
call_info.server_ip
) is taken from the INVITE, which looks like this:Without host networking, the homeassistant container has an IP like 172.26.0.20 and cannot bind to 192.168.1.10.
To fix this, maybe we could bind to
INADDR_ANY
instead of trusting the IP from the INVITE which will not be correct in a lot of networking scenarios?Something like:
voip-utils/voip_utils/voip.py
Line 53 in e9e58f3
The text was updated successfully, but these errors were encountered: