Project

General

Profile

Actions

Feature #2488

closed

separate libosmo-mgcp-client from mgcp server code

Added by neels over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
09/03/2017
Due date:
% Done:

100%

Spec Reference:

Description

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.)

Actions #1

Updated by neels over 6 years ago

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

Updated by neels over 6 years ago

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

Updated by neels over 6 years 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.

Actions #4

Updated by neels over 6 years ago

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

patches merged, debian packaging fault fixed

Actions #5

Updated by laforge over 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)