Age | Commit message (Collapse) | Author | Files | Lines |
|
Those static libraries were not used or maintained a long time ago.
We have a much more complete implementation of SCCP and xUA in
libosmo-sigtran. That has been the basis of osmo-stp, as well as in
osmo-sgsn.git, osmo-bsc.git, osmo-msc.git.
The only user of the old static libraries was osmo-bsc-sccplite from
openbsc.git, which is unsupported for many years.
Change-Id: I299a32a2f8f61477cf49c8126567fef2092d5407
|
|
Change-Id: Ie85c5f4806adbb1e5e5c26e90a8ecc73529caea9
|
|
Change-Id: I6e39dcb594ffe918ba117fce08cae7b5a6fd2dcc
|
|
Change-Id: I4fe457dc0ee1e904e05423557cfba2505b315a75
|
|
Change-Id: I9efb883d2a56723300a66b7e13c7aa079f2e4600
|
|
Change-Id: I563bba2eaca7f569a5216fb8268122c0f55ef48b
|
|
This allows having a clearer picture of the several entities involved,
as well as simplifying the files.
In the future, we can do the same for AS, route, etc. and leave osmo_ss7
for the "instance" object.
Change-Id: I3d43268459d61b0b9f9bec34bf31dc0851fa5e48
|
|
Change-Id: I431dc58d5c4adfcb2c4ff19a95b31853618034b5
|
|
Change-Id: Ibe4efb64b8de506a007559e2fcf13cc9dc0d9d60
|
|
Change-Id: I963499ba9f78924660127312f4469b0781fed805
|
|
default hosts
Allow user apps to relay the decision of proper default local/remote
hosts values to the library. Proper configuration of these addresses can
be quite cumbersome to get correctly, or confusing at least. That's due
to the multi-homing feature of SCTP where both IPv4 and IPv6 are
involved.
We were already doing this kind of automatic setup in
osmo_ss7_vty_go_parent(), where we do validations and assign addresses
based on IPv6 availability.
On the other hand, apps using osmo_sccp_simple_client_on_ss7_id() API
usually pass "localhost" as default address. In Linux, when IPv6 is enabled
localhost is resolved as "::1", and "127.0.0.1" when IPv6 is disabled.
Let's instead allow apps to relay the setup to the lib, so same addresses
can be applied both during VTY command as well as if there was no VTY
setup at all.
Related: OS#5186
Change-Id: I82e203612571b7651d758d8148661f706a1642ba
|
|
Change-Id: I017147905ffb69829d010f3e8416c8c5d80e7040
|
|
* add N-PCSTATE.ind and N-STATE.ind definitions to SCCP user SAP
* add minimal SCMG (SCCP Management) and LBCS (Local Broadcast)
* generate MTP-PAUSE.ind/MTP-RESUME.ind based on received xUA DUNA/DAVA
* generate N-PCSTATE.ind towards the local SCCP users
Change-Id: Idb799f7d7ab329ad12f07b7cbe6336da0891ae92
Related: OS#2623, OS#3403, OS#4701
|
|
M3UA and SUA have one sub-protocol called [S]SNM, through which the
SG informs the ASP about certain destinations (point codes) becoming
available (DAVA) or unavailable (DUNA) in the SS7 network.
This patch adds support for
* generating DAVA/DUAN on a SGP when the AS FSM changes to/from AS-ACTIVE
* receiving DAVA/DUNA on an ASP and informing other "SG role" AS/ASP
* processing DAUD from ASP received by SG, generating relate DAVA/DUNA
responses
Related: OS#2623
Change-Id: Id92be4691b0fd77598a6edb642c028bbd8c5b623
|
|
This way the function can be re-used by SUA.
Change-Id: I0dfc5a7a24dd068002e837dc47eb0778c503cac5
|
|
Change-Id: Ibf3ee4be88a4ca633a01fad08d4c714bfa9008bc
|
|
Change-Id: Ibab643b971f80e3774c393ff3988a765dc081196
|
|
Change-Id: I3fe741cb70fa75fb911d40dc8f9eb50e1a85238b
|
|
Change-Id: I9b9d9331bdd1d9cdebdef5c3e0c49a1b18972abd
|
|
Change-Id: Ia087b9f03a73a08f0eaa461f61c6244aaf13e3d4
|
|
Change-Id: Ie3d11408f35509138475e7edde285e1bf5bef8e0
|
|
libosmo-sigtran is using symbols from libosmo-vty, so make sure that
we explicitly link against libosmo-vty to ensure the dependency shows
up in `ldd` of the library.
Change-Id: I4d96612a0df5a1232ed8fe280c5d592f462ef7b1
|
|
Add missing libosmogsm dependency.
Change-Id: I6e5cf393ffe81c582966ca0e9479e6deeffa9280
Fixes: OS#2182
|
|
This tries as good as possible to fit the IPA/SCCPlite stacking into the
existing SIGTRAN/SS7 code architecture/model. To the user, the IPA
protocol looks like yet another protocol on the same level as the choice
between SUA and M3AU. On the inside, things are obviously quite
different.
We need to handle TCP with IPA framing instead of SCTP for both server
and client. We also implement an alternative "ASP FSM" for IPA, which
takes care of the CCM handshake (ID_REQ/ID_RESP/ID_ACK/ID_ACK2) for both
client and server mode.
In server mode, we use the 'unit name' as identifier to look up the AS,
similar to how we use a routing context to look up the AS in the xUA
case.
We also have to bypass activating the default layer manager in the
simple client to make sure we don't run into even more complexity.
What's missing right now is some way to manually override/set the point
codes. As IPA/SCCPlite is missing any routing label, we currently
simply generate one with SPC=0/DPC=0, which will obviously not work in
most configurations.
Change-Id: I9098574cddeba10fcf8f1b6c196a7069a6805c56
|
|
Change-Id: I100daaa947dbab6a4528c4e9fbd0d30790288f63
|
|
Now that the VTY has no static dependencies like a global ss7_instance
anymore, we can move it back to libosmo-sigtran and make use of it in
other programs outside osmo-stp.
This requires Change-Id I184a7e3187b48c15c71bf773f86e188fe1daad15 in
libosmocore
Change-Id: I2e549f1eadbfb28dde79f620b130cbf022312c42
|
|
This "default layer manager" can optionally be used by a xUA ASP. It
will handle the xUA Layer Manager (xlm) primitives and use them to
behave as follows:
* bring the ASP into state "INACTIVE"
* see if the SG can match our connection (based on IP address + port
information) to a statically configured ASP configuration with
associated AS(s). If yes, it will send us a NOTIFY message with
AS-INACTIVE.
* if the above doesn't work, try to dynamically register a routing key
using RKM for the point code that was locally confiured on the
ASP/client. If that works, the SG will now have created ASP and AS
objects as well as a routing key and be able to serve us, sending the
NOTIFY with the AS-INACTIVE state.
* After either of the two above, we will attempt to transition into
ASP-ACTIVE. The SG should send us an AS-ACTIVE notification in return
* if anything fails, abort and disconnect the SCTP connection, restart
related FSMs and start from scratch
Change-Id: I78d4623dd213b5c59007a026a6cc3cfe5c04af50
|
|
Change-Id: I9b1cf438a42519c0fe2f555c1672fafa499122a1
|
|
This is an implementation of SCCP as specified in ITO-T Q.71x,
particularly the SCRC (routing), SCLC (Connectionless) and SCOC
(Connection Oriented) portions. the elaborate state machines of
SCOC are implemented using osmo_fsm, with one state machine for each
connection.
Interfaces to the top (user application) are the SCCP-USER-SAP and on
the bottom (network) side the MTP-USER-SAP as provided by osmo_ss7.
Contrary to a straight-forward implementation, the code internally
always uses a SUA representation of all messages (in struct xua_msg).
This enables us to have one common implementation of all related state
machines and use them for both SUA and SCCP. If used with real SCCP
wire format, all messages are translated from SCCP to SUA on ingress and
translated from SUA to SCCP on egress. As SUA is a super-set of SCCP,
this can be done "lossless".
Change-Id: I916e895d9a4914b05483fe12ab5251f206d10dee
|
|
Change-Id: I8151a9b08a0b0ca97b9c73105ad4548512ce3be8
|
|
Change-Id: I7067a85dcc5dda66f4b17b0fe08da8cb3efe79ef
|
|
This is what aims to be a rather complete/proper implementation of the
SIGTRAN + SS7 protocol suite. It has proper abstraction between the
layers with primitives, finite state machines for things like the AS and
ASP state machines, support for point code routing, etc.
What's not implemented at this point:
* re-integration of pre-existing SUA (pending)
* actual MTP2 and physical E1/T1 link support
* different trafic modes like broadcast/fail-over/load-balance
Change-Id: I375eb80f01acc013094851d91d1d3333ebc12bc7
|
|
Move here unchanged first, so we're able to see the modifications in diffs.
Pending changes will follow in subsequent patches.
Moved from osmo-iuh 3da8608b6ad014fc74536dbb49019704fd425b8c, which was before
the rename of osmo_sua_link and osmo_sua_user to osmo_sccp_link and
osmo_sccp_user, so this will not compile.
Change-Id: Iae0c58c5f1eb00a685de70add0d5257e4316c6d5
|
|
|
|
... this code originates from the osmo-iuh repository, but is now part
of a new shared libosmo-sigtran.so library generated in this repository.
|
|
Generalize, this requires various API modifications
but that is the most sane path forward.
|
|
Since automake 1.13 INCLUDES is depricates and causes a warning
|
|
|
|
|
|
SCCP can be wrapped inside the MTP Level3, and one can
use it for link testing as well. This repository should
be renamed to libosmo-itu or libosmo-ss7 and be a host
to SS7 related encapsulation...
The code is coming from the cellmgr-ng code.
|
|
|
|
|