Missing configuration when using docker

[ghjansen]

Upgrading Restcomm in a environment that uses docker, it was noticed that the configuration set through docker was not correctly applied to the new container.

This way, the configuration files restcomm.conf and advanced.conf remained with default values (mostly empty) for the all parameters, and even after manually configuring those files, the container still with unstable behaviour. Some of the issues faced as consequence:

• sip container failed to start due to bad password for JKS certificate;
• 2 new sip connectors failed to start due to port number already taken by other connector;
• wrong port configuration for HTTP/HTTPS;
• container shutting down itself after jboss completes bootstrap and is already running normally (an exception from jboss-cli was noticed for this case, failing to connect to the default ethernet interface address using port 9999);
• RMS is started even when the configuration assumes an external media server (XMS).

The configuration files and logs contain sensitive information and will be not posted here.

This issue is related to #1945 .

[ghjansen]

Main cause identified was missing prefixes for the variables inside the configuration file of the environment, like RCBCONF_, RCADVCONF_, EXTCONF_, LBCONF_ and RMSCONF_.

Also, the bug https://issues.jboss.org/browse/WFLY-1664 was fixed with the provided workaround.