OpenBSC and Asterisk with NanoBTS and no ISDN

historical

Have you been following this?
http://openbsc.osmocom.org/trac/wiki/OpenBSC_LCR

I recently configured a very similar setup with the latest git of OpenBSC,
libosmocore, mISDN,mISDNuser, and LCR. I used Asterisk 1.8, in which case
you'll need to checkout the asterisk_1_8 branch of LCR.

I know it seems a little counter-intuitive in an ethernet-only
environment, but you need to build the mISDN kernel modules so you can
create the loopback ISDN interfaces. These are needed for communication
between OpenBSC and LCR.

I configured LCR to pass all calls to Asterisk. If you need help with the
LCR/Asterisk configuration let me know. I found the following site helpful
for setting up my asterisk diaplans:
http://astbook.asteriskdocs.org/en/2nd_Edition/asterisk-book-html-chunk/asterisk-CHP-5.html

c

> I am trying to get OpenBSC working with Asterisk for a class project.  I
> have a NanoBTS DCS1800.  I was hoping to get this to work entirely over
> Ethernet, as the server is running on a controlled VM cluster with no way
> of
> getting an add-on ISDN card in.
>
> I have attempted to follow the OpenBSC+LCR+Asterisks route.  But as
> expected, LCR gives me issues when it does not find an ISDN card.  I am
> not
> familiar with LCR to tweak it.  Can I use LCR without an ISDN card?  What
> should I look into to get this done?
>
> I have also attempted to modify the asterisk chan_openbsc code to comply
> with the libosmo break off earlier this year.  With a few Makefile
> adjustments, include a few more header files, and strip out some debuging
> code, everything will compile.  However, asterisk seg faults when the
> module
> loads.  The gdb output is:
> Program received signal SIGSEGV, Segmentation fault.
> 0xb72fcd1d in cmd_execute_command_strict (vline=0x83d4c88, vty=0x83c2450,
> cmd=0x0) at command.c:2000
> 2000            cmd_vector = vector_copy(cmd_node_vector(cmdvec,
> vty->node));
>
> I am not familar with this code, so all I can do is comment out things in
> an
> attempt to debug.  Eventually I keep it from crashing, and the nanoBTS
> will
> make contact with the driver.  However, since the code that gets commented
> out also involves loading the cfg, the BTS does not get bootstraped. This
> is
> all running on Gentoo, though I have also tried on Debian and Ubunto.
>
> Any help would be appreciated.
>