FYI: Last night I
a) merged the SCTP support for libosmo-netif to master
b) moved the sua code from osmo-iuh into the libosmo-sccp repository, where we now build a shared libosmo-sigtran.so, which will be linked by the MSC, SGSN and HNB-GW code for the IuCS/IuPS interface.
Unlike the spec demands, we will not use SCCP in M3UA in SCTP here, but will use SUA in SCTP as a simplification.
Furthermore, the SUA code in libosmo-sigtran does not yet a) fully implement all the correct state machine transitions and inactivity timers (this is to be done) b) implement the ASP management state machines
This is done as a short-cut as we initially only want to communicate between our own network elements. What's important is that we can use wireshark for decoding the protocol stacking that we use, and that the SCCP USER SAP is specified in a way that will enable us to put SCCP+M3UA or other sigtran dialects underneath the RANAP code in the future, as needed.
Regards, Harald
On Wed, Dec 23, 2015 at 12:05:45PM +0100, Harald Welte wrote:
FYI: Last night I
a) merged the SCTP support for libosmo-netif to master
b) moved the sua code from osmo-iuh into the libosmo-sccp repository, where we now build a shared libosmo-sigtran.so, which will be linked by the MSC, SGSN and HNB-GW code for the IuCS/IuPS interface.
Unlike the spec demands, we will not use SCCP in M3UA in SCTP here, but will use SUA in SCTP as a simplification.
Furthermore, the SUA code in libosmo-sigtran does not yet
Just to clarify beyond doubt, "the sua code" == libosmo-sigtran, since recently part of libosmo-sccp.git (which also depends on a recent addition to libosmocore master; and, yesterday, I was using one of Harald's branches of libosmo-sccp, but today master works).
Actually, why is the SUA code called libosmo-sigtran, and not libosmo-sua? Is that just keeping up the ancient tradition of confusing naming? ;)
or other sigtran dialects underneath the RANAP code
Ah, so, SUA and its alternatives (SCCP in M3UA, etc) together are called "sigtran", correct?
~Neels
On 23 Dec 2015, at 15:37, Neels Hofmeyr nhofmeyr@sysmocom.de wrote:
Actually, why is the SUA code called libosmo-sigtran, and not libosmo-sua? Is that just keeping up the ancient tradition of confusing naming? ;)
sure. libosmo-sccp included SCCP codec/connection code, M2UA/M3UA codec code and now SUA code. M2UA/M3UA/SUA is part of "SIGTRAN" and "SCCP" is spoken on top of M2UA/M3UA. So somehow everything in this repo is related to SIGTRAN.
holger
-
Harald Welte -
Holger Freyther -
Neels Hofmeyr