SIGTRAN/SS7 stack in libosmo-sigtran merged to master

As I blogged in ,
some of which already are the squashed results of many more incremental
development steps.

The result is as follows:

• General SS7 core functions maintaining links, linksets and routes




• xUA functionality for the various User Adaptations (currently supported)

  
  
  
  

  • MTP User SAP according to )

  
  

  • support for dynamic registration via RKM (routing key management)

  
  

  • osmo-stp binary that can be used as Signal Transfer Point, with
    the usual "Cisco-style" command-line interface that all Osmocom
    telecom software has.

  
  
  
  



• SCCP implementation, with strong focus on Connection Oriented SCCP (as
  that's what the A interface uses).

  
  
  
  

  • osmo_fsm based state machine for SCCP connection, both incoming and
    outgoing

  
  

  • SCCP User SAP according to and OsmoHNB-GW over to libosmo-sigtran.
    They're now all just M3UA clients (ASPs) which connect to osmo-stp
    to exchange SCCP messages back and for the between them.

    
    

    What's next on the agenda is to

    
    
    
    

    • finish my incomplete hacks to introduce IPA/SCCPlite as an alternative
      to SUA and M3UA (for backwards compatibility)

    
    

    • port over OsmoBSC to the SCCP User SAP of libosmo-sigtran

      
      
      
      

      • validate with SSCPlite lower layer against existing SCCPlite MSCs

      
      
      
      
    
    

    • implement BSSAP / A-interface procedures in OsmoMSC, on top of the
      SCCP-User SAP.

    
    
    
    

    If those steps are complete, we will have a single OsmoMSC that can talk
    both IuCS to the HNB-GW (or RNCs) for 3G/3.5G as well as AoIP towards
    OsmoBSC. We will then have fully SIGTRAN-enabled the full Osmocom
    stack, and are all on track to bury the OsmoNITB that was devoid of such
    interfaces.

    
    

    If any reader is interested in interoperability testing with other
    implementations, either on M3UA or on SCCP or even on A or Iu interface
    level, please contact me by e-mail.

    Vollständiger Original-Artikel

    Den kompletten Beitrag mit allen Details direkt auf laforge.gnumonks.org lesen.

    ↗ Original-Artikel auf laforge.gnumonks.org lesen