Previous the osmo-hlr always sent a wildcard APN as the only APN
which violates the spec. Further wildcard APNs aren't support
by the current Open5gs.
Since I540132ee5dcfd09f4816e02e702927e1074ca50f the osmo-hlr
supports multiple APN in the subscriber data.
The checkout directory should only contains source and no erlang bytecode.
Otherwise it might not compile when creating the build_dep.tar.gz on a machine
with newer erlang and try to build the package on a system with older erlang.
This commit improves handling of the resynchronization information in
a DIAMETER request from a UE that has a sync failure. It factors
parsing of the resync info into a helper function with a defined spec,
and handles the resynchronization info as a binary rather than a
To build on OBS the source package must include all dependencies.
Downloading dependencies isn't allowed. generate_build_dep.sh will
download all dependencies.
The jenkins job to update OBS should do this before calling
`dpkg-buildpackage -S` to build a source package.
- use the rebar3' debian/rules as template
- use override targets instead of the exact targets
- only install the escriptize osmo_dia2gsup file
The rebar.lock contains the last known working state
of all dependencies with exact version numbers.
rebar.config only holds the minimal dependencies (package x version >=2.0.0)
The IP 127.0.0.4 is already used by the open5gs smf. Since the mme by default
tries to connect to the hss at 127.0.0.8 let's change the default here
to something that works ootb.
Add initial debian packaging and a systemd service that starts
osmo_dia2gsup. Given that dependencies listed in rebar.lock are not
packaged in debian 11, this just uses rebar3 to download and compile
the dependencies during the build.
Resulting erlang files are installed to the following path, where they
become available in the erlang shell (erl):
The travelping diameter files appear to define a number of AVPs
originating in 29.229 in the 29.329 .dia file, let's try to
resolve this and avoid diameteerc complaining about AVPs being
defined in two locations.