Project

General

Profile

Feature #2551

generalization of OSMUX support in osmo-mgw

Added by laforge 2 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Start date:
10/06/2017
Due date:
% Done:

0%


Description

The goal here is that OSMUX endpoints are just another endpoint type, and that it should be easy for any program at any level of the network (whether BSC, BSC-NAT, MSC, ...) to simply use OSMUX instead of RTP for media transport. Scenarios to keep in mind are:

  • between OsmoBSC and OsmoMSC
  • between OsmoBSC and OsmoBSCNAT
  • future: between OsmoMSCs or even towards external MNCC handlers

OsmoMGW should be able to support conversion between regular RTP and osmux (and vice-versa). We need to find out how exactly we will map this to MGCP endpoint + connection semantics.


Related issues

Related to OsmoBSC - Feature #2552: Support configuring voice via osmo-mgw as OSMUX instead of RTP New 10/06/2017
Related to OsmoBSCNAT - Feature #2553: Support configuring voice via osmo-mgw as OSMUX instead of RTP New 10/06/2017
Related to Cellular Infrastructure - Feature #2554: Reference/Demo setup + documentation for use of OsmoBSC+OsmoBSCNAT with OSMUX New 10/06/2017

History

#1 Updated by laforge 2 months ago

  • Related to Feature #2552: Support configuring voice via osmo-mgw as OSMUX instead of RTP added

#2 Updated by laforge 2 months ago

  • Related to Feature #2553: Support configuring voice via osmo-mgw as OSMUX instead of RTP added

#3 Updated by laforge 2 months ago

  • Related to Feature #2554: Reference/Demo setup + documentation for use of OsmoBSC+OsmoBSCNAT with OSMUX added

#4 Updated by laforge about 2 months ago

  • Target version set to OSMUX Generalization

Also available in: Atom PDF