Project

General

Profile

Actions

Feature #2551

closed

generalization of OSMUX support in osmo-mgw

Added by laforge over 6 years ago. Updated over 4 years ago.

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

100%

Spec Reference:

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 Resolvedpespin10/06/2017

Actions
Related to OsmoBSCNAT - Feature #2553: Support configuring voice via osmo-mgw as OSMUX instead of RTPClosedpespin10/06/2017

Actions
Related to Cellular Network Infrastructure - Feature #2554: Reference/Demo setup + documentation for use of OsmoBSC+OsmoBSCNAT with OSMUXNewpespin10/06/2017

Actions
Related to libosmo-sccp + libosmo-sigtran - Bug #2536: MGCP tunneling missing from IPA support in libosmo-sigtranResolvedpespin10/05/2017

Actions
Related to OsmoMSC - Feature #4065: osmo-msc: Support instructing MSC_MGW to use Osmux between 2 endp/call-leg of same voice callNewpespin06/19/2019

Actions
Related to Cellular Network Infrastructure - Feature #4090: Document user plane handling with BSC+MSC co-located OsmoMGW, Osmux, and outlookResolvedpespin07/05/2019

Actions
Related to OsmoMGW - Feature #4092: Osmux: Support dynamic allocation of osmux socketsNewpespin07/05/2019

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)