Project

General

Profile

Feature #1993

osmo-hnbgw and libiu code of OsmoMSC and OsmoSGSN needs to be ported to libosmo-sigtran

Added by laforge 3 months ago. Updated 3 months ago.

Status:
In Progress
Priority:
High
Assignee:
Target version:
-
Start date:
04/03/2017
Due date:
% Done:

70%

Spec Reference:

Description

The changes required in libosmo-sigtran to support AoIP require other users of libosmo-sigtran to be ported to the new API. Currently, this mans osmo-hnbgw as well as OsmoMSG and OsmoSGSN, who all use the Iu interface (currently over SUA, then over real M3UA).


Related issues

Related to OpenBSC - Feature #1843: osmo-bsc: Add SCCP/M3UA signaling transport as alternative to IPA multiplex In Progress 11/18/2016

History

#1 Updated by laforge 3 months ago

  • Related to Feature #1843: osmo-bsc: Add SCCP/M3UA signaling transport as alternative to IPA multiplex added

#2 Updated by laforge 3 months ago

  • Project changed from OpenBSC to OsmoHNBGW
  • Target version deleted (A-over-IP interface as per 3GPP)

#3 Updated by laforge 3 months ago

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

osmo-hnbgw was really simple, but I think there are some wrong design assumptions in libiu which make porting of the OsmoMSC and OsmoSGSN much harder. Each UE context should not store a reference to the SCCP Link, but to the remote SCCP Address. It doesn't matter from which physical link a message originates; it only matters from which SCCP CalledAddress it comes from. I'll investigate required architectural changes and modify it accordingly.

#4 Updated by laforge 3 months ago

  • % Done changed from 20 to 70

I have a version of osmo-hnbgw and osmo-msc that talk to each other on top of the current laforge/sigtran branch of libosmo-sccp via the new osmo-stp. This needs more testing + clean-up but I think it will be resolved soon.

Also available in: Atom PDF