provd: fix wrong port in http_port for phone templates
Description
Impacts
On majority of desktop phone (without using wazo DHCP), the provisioning process is completely broken due to wrong port
After an upgrade (or new install), only new desktop phone are impacted (or doing hard reset)
Quick solution
revert the work related to proxy through nginx
Good solution
create another task to reintroduce proxy with all constraints (not well know when ticket was done)
Tech info
The port used for the provisioning HTTP server is also the port that is given to phone templates. Given that we changed this port to be an internal one and that provisioning is exposed via port 8667 through nginx, http_port should still be 8667. A new configuration option is thus necessary for the real listening port of wazo-provd and the port that should be exposed to the phone templates to remain http_port.
Impacts
On majority of desktop phone (without using wazo DHCP), the provisioning process is completely broken due to wrong port
After an upgrade (or new install), only new desktop phone are impacted (or doing hard reset)
Quick solution
revert the work related to proxy through nginx
Good solution
create another task to reintroduce proxy with all constraints (not well know when ticket was done)
Tech info
The port used for the provisioning HTTP server is also the port that is given to phone templates. Given that we changed this port to be an internal one and that provisioning is exposed via port 8667 through nginx, http_port should still be 8667. A new configuration option is thus necessary for the real listening port of wazo-provd and the port that should be exposed to the phone templates to remain http_port.