I am doing some experimenting with openbsc with software emulation of ipaccess. At this early stage, I am communicating with openbsc with hard coded messages. Here is what getting as response from openbsc:
./bsc_hack --debug=DNM:DRSL DB: Database initialized. DB: Database prepared. <0005> bsc_init.c:626 bootstrapping OML for BTS 0 <0005> abis_nm.c:583 OC=BASEBAND TRANSCEIVER(04) INST=(00,ff,ff) SW Activate Request: ACKing and Activating <0005> abis_nm.c:934 Found SW config: 42 12 00 05 01 02 03 04 05 13 00 05 05 04 03 02 01 <0005> abis_nm.c:1482 state 4, NM MT 0x0e <0005> abis_nm.c:1581 Activate Software DONE! <0005> abis_nm.c:583 OC=BASEBAND TRANSCEIVER(04) INST=(00,ff,ff) Software Activated Report <0005> abis_nm.c:583 OC=BTS(01) INST=(00,ff,ff) IPACCESS(0xe1): RSL CONNECT ACK PORT=3003
Openbsc responding properly on PING from softBTS in both links for OML and RSL. Looks like OML and RSL connection are established, but, here is problem. To get RSL CONNECT ACK PORT=3003, I send OML message NM_MT_IPACC_RSL_CONNECT_ACK before recieving request NM_MT_IPACC_RSL_CONNECT from openbsc. My question is, how to get in stage when openbsc is ready to send NM_MT_IPACC_RSL_CONNECT. What expecting openbsc to get from ipaccess before sending NM_MT_IPACC_RSL_CONNECT?
Thank you
Fadil Berisha
On Monday 05 April 2010 16:37:31 Fadil Berisha wrote:
To get RSL CONNECT ACK PORT=3003, I send OML message NM_MT_IPACC_RSL_CONNECT_ACK before recieving request NM_MT_IPACC_RSL_CONNECT from openbsc. My question is, how to get in stage when openbsc is ready to send NM_MT_IPACC_RSL_CONNECT. What expecting openbsc to get from ipaccess before sending NM_MT_IPACC_RSL_CONNECT?
I think you want to look into src/bsc_init.c for our init sequence and on which states we trigger the RSL connect message.
Hi Fadil,
On Mon, Apr 05, 2010 at 10:37:31AM -0400, Fadil Berisha wrote:
I am doing some experimenting with openbsc with software emulation of ipaccess.
This is great news! Are you going to release this as Free / Open Source Software ?
I think even in an early stage, it might be very interesting to have a look at it. If you'd like, I can set up a git repository for you.
I once started with creating an Abis/IP BTS-side implementation for OpenBTS, but never had the time to continue it.
There might be quite some code sharing possibilities.
I'll try to port my OpenBTS Abis/IP code against current OpenBTS and release it soon.
Regarding your actual technical problem: Holger has already responded to it, so I won't add anything else...
Cheers, Harald
Hi Harald
This is great news! Are you going to release this as Free / Open Source
Software ?
This project is based on openBSC and would be Free/Open Source. Let me comment a few points for this project:
1. Abis side Create software for BTS which will use same Abis/IP software what is already developed to communicate with ipaccess. OpenBSC will operate this BTS as ipaccess, using same cfg files etc.
2. Um side Use or adapt as much as we can software already developed in current project OsmocomBB (LAPDm, etc).
3. Core New module. Following programing techniques and approach as in openBSC will allow more people to be involved.
4. Hardware Hardware independent. Kernel driver for each hardware solution.
There might be quite some code sharing possibilities.
I'll try to port my OpenBTS Abis/IP code against current OpenBTS and release it soon.
That would be great. Would be good to have more hardware options for openBSC also will help to prepare better some initial code for repository.
Fadil
-
Fadil Berisha -
Harald Welte -
Holger Freyther