Hi Neels,
On Mon, Jan 15, 2018 at 09:23:40PM +0100, Neels Hofmeyr wrote:
> So since we merged that patch, osmo-bsc_nat is no longer part of the osmo-bsc
> build. That's certainly not intended, is it?
It is intended, or at least expected. osmo-bsc_nat is heavily tied to SCCPlite.
We have freed osmo-bsc from those ties and it implements "generic SCCP" on top
of
the SCCP User SAP of libosmosigtran.
Until somebody will do the same amount of porting in osmo-bsc_nat, I think it
is best
that the two programs dealing natively with SCCPlite are in openbsc.git.
> Confirm and please fix that. thx!
If there's an easy fix, it might be worth looking into it. However, I think
with
all the rework on the SCCP and MGCP side, it makes sense to leave it disabled
until we have a clear plan how a new AoIP-enabled osmo-bsc_nat might look like.
Regards,
Harald
--
- Harald Welte <[email protected]> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
