Cellular Network Infrastructure

From https://jenkins.osmocom.org/jenkins/job/Osmocom-repo-install-debian9/feed=nightly,label=repo-install-test/403/consoleFull:

Feb 25 10:45:21 57c7d4458dc5 osmo-msc[16190]: <0024> mgcp_client.c:792 MGW(mgw) MGCP client: using endpoint domain '@mgw'
Feb 25 10:45:21 57c7d4458dc5 osmo-msc[16190]: <0014> socket.c:419 unable to bind socket: (null):2728: Address already in use
Feb 25 10:45:21 57c7d4458dc5 osmo-msc[16190]: <0014> socket.c:431 no suitable local addr found for: (null):2728
Feb 25 10:45:21 57c7d4458dc5 osmo-msc[16190]: <0024> mgcp_client.c:912 MGW(mgw) Failed to initialize socket (any):2728 -> (null):2427 for MGW: Address already in use
Feb 25 10:45:21 57c7d4458dc5 osmo-msc[16190]: MGCPGW connect failed
Feb 25 10:45:21 57c7d4458dc5 systemd[1]: osmo-msc.service: Main process exited, code=exited, status=7/NOTRUNNING
Feb 25 10:45:21 57c7d4458dc5 systemd[1]: osmo-msc.service: Unit entered failed state.
Feb 25 10:45:21 57c7d4458dc5 systemd[1]: osmo-msc.service: Failed with result 'exit-code'.

This job starts all systemd services of Osmocom programs with default configurations, and checks whether they start up.

I guess the failure relates to osmo-hnbgw now also using the mgcp client, and both using the default address.

dexter: could you change the address in the default config of osmo-hnbgw?