- Shipped
- April 26, 2026 at 5:28 PM UTC
- Author
- Kamo
- Commit
- b882928
The previous approach (http_custom.conf with [general] override) didn't actually take effect because Asterisk's INI parser doesn't honor multiple [general] sections across includes the way the docs imply: enabled=no in http_additional.conf was winning over enabled=yes in http_custom.conf. The reliable solution is to write http.conf directly with [general] inline, then re-include http_additional.conf and http_custom.conf afterwards (FreePBX still maintains those, but the keys we care about land in our [general] first). Verified: HTTP server now binds 0.0.0.0:8089, /ws upgrade returns 101. Also: empty pjsip.transports_custom.conf because FreePBX's auto-generated pjsip.transports.conf now contains [0.0.0.0-ws] (driven by the ws bind we turn on in kvstore_Sipsettings during startup), and a duplicate [0.0.0.0-ws] section in the custom file caused Asterisk to drop ALL transports.