Vadim Yanitskiy
4b7dcfe66d
Below is an example of a decoded Requested-EUTRAN-Authentication-Info: [{ 'Requested-EUTRAN-Authentication-Info', [1], %% Number-Of-Requested-Vectors [1], %% Immediate-Response-Preferred [[ %% Re-Synchronization-Info 154,153,78,226,63,248,178,208,169,186,215,18,159,150,252, 103,249,220,169,90,223,249,219,26,172,118,171,193,216,221 ]], [] %% AVP }] As can be seen, the value of Re-Synchronization-Info is not a binary, but a list, so indeed is_binary(ReSyncInfo) would yeild false. Use is_list() instead and convert to binary using list_to_binary(). Change-Id: Ie5eded2f5fb2de01f69d2a9c0e5d70283bf5cbf5 Related: OS#5646 |
||
---|---|---|
contrib | ||
debian | ||
dia | ||
src | ||
.gitignore | ||
.gitreview | ||
README.md | ||
rebar.config | ||
rebar.lock |
README.md
= Osmocom DIAMETER -> GSUP translator =
This project implements a proxy translating Diameter into GSUP, hence allowing Diameter clients connecting to GSUP server. This allows, for instance, using OsmoHLR as an HSS used by 4G/5G nodes.
== Building ==
Install erlang and rebar3 packages (not "rebar", that's version 2! You may need to compile it from source in some distros).
$ rebar3 compile $ rebar3 escriptize
== Testing ==
Unit tests can be run this way: $ rebar3 eunit
== Running ==
Once osmo_dia2gsup is built, you can start it this way:
$ rebar3 shell
In the erlang shell: 1> osmo_dia2gsup:start().