I agree that if getting the ports working is too difficult then using a seperate asterisk instance seems like the straight forward solution. Having an image would be nice but I agree with pergola that the best option would be to either use the existing addon or create another with the right settings as this will work for everyone. But I guess these are still in docker and therefore have the same port issue?
Maybe a workaround for the ports issue, is to change the network setting? So the docker gets the IP from the router? And not some ip from the host? So everythng is exposed directly on the local LAN?
Maybe we will issues too when we register other SIP clients in future, thisā¦ Running it directly on the network will eliminate that issue too
But even if the add-on works, I still think a integration is a good idea. With that people can also use their own Asterisk server. And I can make a device with all the entities in there.
But if I can get the add-on working, I will first focus on that of course.
I tested with the card and a test page (also in the HA-SIP repo). And it did work with my FreePBX server.
Pushed a test to the repo. It launches Asterisk in console mode so it doesnāt make entities for this test. And there is a weird thing were you get a lot of whitespace in the consoleā¦
Couldnāt get ssh working in docker. HA does something with it, since it does work in my test VM.
Just updated , not debugged yet, but my CPU load was continue 99% ?? Had to shutdown the dockerā¦
I also noticed no new DHCP IP lease on local network? It it still getting an IP address from hassio 172.x?