Closed rijnhard closed 6 years ago
Hey Rijnhard, what's your docker run command (or otherwise way of instantiating the containers), I'm wondering if maybe it is something with network permissions -- maybe either firewall (like iptables maybe), or otherwise. One thought is to try it with host networking, e.g. docker run --net host [other options] dougbtv/asterisk
I going to close this, for brevity I was being a tool. I was running a soft phone locally for testing, obviously it was trying to bind 5060 and a bunch of other ports and so was the asterisk container. I fixed this by REMOVING the net=host
and doing a docker inspect to get the container IP and registering the soft phone to that (only because I couldn't be bothered to get consul and registrator running locally). The caveat is each time I restart the containers I need to redo that process.
So it looks like it's slightly affecting the running operation, registrations can sometimes fail repeatedly until like attempt 19 then it works. I get this error when I have multiple asterisk containers in a bridge network (docker-compose).
According to Asterisk Forums it's permissions or networking, I doubt bridge is doing anything funny, and it looks like you have all the ports open, although I'll get one of our techs to review the file again. Makes me think its permissions, which is of course always fun with docker.
Any idea?