Feature #2488

separate libosmo-mgcp-client from mgcp server code

Added by neels 3 months ago. Updated about 1 month ago.

Target version:
Start date:
Due date:
% Done:



The mgcp code can be built with --enable-mgcp-transcoding, which adds a dependency to libgsm.
However, osmo-msc and osmo-bsc only need the mgcp client code, and including the entire libosmo-legacy-mgcp pulls in a useless requirement of libgsm.

Hence the mgcp client code that does not relate to transcoding should live in a separate library, libosmo-mgcp-client.

(osmo-bsc_nat does use the remaining bits of libosmo-legacy-mgcp, so the osmo-bsc.git in general will need to manage libgsm dependency for osmo-bsc_nat, but the osmo-bsc binary will need only the mgcp client code.)


#1 Updated by neels 3 months ago

  • Subject changed from separate mgcp_client as separate library to separate libosmo-mgcp-client from mgcp server code

#2 Updated by neels 3 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 90

#3 Updated by neels 2 months ago

The patches are merged, but there is still an issue with debian packaging.
A final patch to resolve this is in the queue... not on gerrit yet, waiting for some of pmaier's changes first to avoid rebase hell.

#4 Updated by neels about 2 months ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

patches merged, debian packaging fault fixed

#5 Updated by laforge about 1 month ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF