Hello Harald,
Thanks for the reply and sorry if i was blunt to ask the question as im new to openbsc. I was just trying to find a good sip interoperability for opensbc while keeping ss7 in handy.
How would you think best way to integrate it with yate as we already have some services with yate and would like to integrate opensbc with that. All we need is basically,
1. Have multiple opensbc (probably NITB but with unbundled HLR features) connecting many nano.BTSs
2. Connect them back to yate in some way
3. let the call handling to take care of yate
i.e. any MO call to routed to yate and yate will consult the HLR database and decide which BSC it should send it back to.
WHat would be the best way to achieve this ?
BTW, yate does support both AMR and GSM codes.
Thanks again Harald for your valuable result and openbsc is a great software im just new to it, but i find it extremely useful and just trying to make it use in a commercial environment.
Thanks again
Nik.
On Thu, Mar 1, 2012 at 12:40 PM, Harald Welte
<laforge@gnumonks.org> wrote:
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@gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)