Project

General

Profile

Feature #3399

mobile: refactor / finish external MNCC handler implementation

Added by fixeria 3 months ago. Updated 15 days ago.

Status:
Stalled
Priority:
High
Assignee:
Category:
OsmocomBB mobile (host)
Start date:
07/17/2018
Due date:
% Done:

40%

Resolution:
Spec Reference:

Description

In general, it is possible to connect mobile application to an external MNCC-handler, such as LCR and osmo-sip-conector.
In case of the second one, mobile can be even connected to a PBX, e.g. FreeSWITH or Asterisk:

The current implementation has the following problems:

  • impossible to configure MNCC-socket path per MS instance,
  • TCH FR codec only,
  • no RTP support.

History

#1 Updated by fixeria 15 days ago

  • Checklist item Ability to configure MNCC-socket path per MS instance added
  • Checklist item Drop TCH/F codec limitations added
  • Checklist item Implement RTP support added
  • Checklist item OsmocomBB - MNCC codec negotiation added
  • Checklist item OsmocomBB - MNCC transcoding added

#2 Updated by fixeria 15 days ago

  • Checklist item Ability to configure MNCC-socket path per MS instance set to Done
  • Checklist item Drop TCH/F codec limitations set to Done
  • Status changed from New to Stalled
  • Priority changed from Normal to High
  • % Done changed from 0 to 40

Some work has already been done, and the code can be found in the following branches:

https://git.osmocom.org/osmocom-bb/log/?h=fixeria/audio
https://git.osmocom.org/osmocom-bb/log/?h=fixeria/mncc

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)