osmo-mgw/src
Neels Hofmeyr 72bc8da537 mgcp_client: drop a bunch of dead code
Remove public API that makes no sense anymore and is dead code.

I see the dropped API as a dead-end initial misconception of the early mgcp
client, and it doesn't really make sense to drag this stuff along. It has not
been used by osmo-msc,-bsc for a long time now, and just confuses the reader.

It is public API, yes, and older versions of osmo-msc / osmo-bsc will not be
able to compile against this, but even if it did, the resulting MGCP client
would not work with the current osmo-mgw: this API is still based on the
premise that the MGCP client dictates the MGW endpoint numbers, a concept that
cannot be used with the current osmo-mgw. Instead, osmo-mgw expects a
wildcarded endpoint upon CRCX and assigns its own endpoint names.

Also, the bts-base configuration is unused and a legacy of when osmo-bsc_mgcp
had explicit BTS and CN sides.

Change-Id: I98a9f1f17a1c4ab20cea3b08c7d21663592134d6
2018-12-19 22:22:34 +00:00
..
libosmo-mgcp osmo-mgw: err-log: include expected domain name 2018-12-19 17:58:42 +01:00
libosmo-mgcp-client mgcp_client: drop a bunch of dead code 2018-12-19 22:22:34 +00:00
osmo-mgw fix osmo-mgw -s; fixes osmo-mgw.service using -s 2018-11-25 22:43:16 +01:00
Makefile.am Remove libosmo-legacy-mgcp and osmo-bsc-mgcp 2018-09-06 20:39:53 +00:00