[PATCH] fix build without mISDN

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Harald Welte laforge at gnumonks.org
Thu Mar 1 12:40:26 UTC 2012


Hi Nik,

On Thu, Mar 01, 2012 at 11:05:45AM +0000, Nik Pakar wrote:

> 1. Use OpenBSC Nitb as its on LCR and implement a gsm channel driver for
> yate.  

Well, you are asking the lcr author to implement something for yate.  I
think it may be a bit of a strange question ;)

> 2. Use extensive SCCP, MAP implementation already on yate and implement
> full A interface integration towards yate.

I would be honestly surprised if yate implemented connection-oriented
SCCP procedures.  This is only used on the GSM A interface and not to be
mistaken with the datagram-oriented SCCP (UDT only) used by TCAP/MAP.

In fact, it might make more sense to use the existing libosmo-sccp and
	either
1) add SCCP-lite (IPA multiplex) support to yate
	or
2) implement M3UA as a transport for osmo-bsc's existing libosmo-sccp
   and use that to connect to yate.

But then, I am not aware of any commercial OpenBSC user who has any
interest in OpenBSC with classic A interface.  Everybody wants to move
away from TDM and to an all-IP RAN.

Furthermore, at least as far as I know, yate may not support AMR/EFR
codecs, which makes it somewhat limited in the context of GSM.  I may be
wrong here, though.

Regards,
	Harald
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)




More information about the OpenBSC mailing list