October 2012 - OpenBSC - lists.osmocom.org

GPRS - local and foreign TLLIs
by Luca Melette 04 Feb '26

04 Feb '26

Hello everybody, after setting up a nanoBTS with OpenBSC/SGSN/GGSN, I had some troubles trying to connect my smartphone to the GPRS cell. Investigating the BTS-to-SGSN traffic, I saw that the frames sent by the SGSN were all marked with the same N(U) value (at LLC layer), the value was 0. With some debug, I found that the there was a mismatch in the TLLI storage, used to keep the status of attached terminals. The mentioned code is contained in gprs_llc.c, involving LL Entity functions and gprs_llc_tx_ui(). /* look-up or create the LL Entity for this (TLLI, SAPI) tuple */ lle = lle_by_tlli_sapi(msgb_tlli(msg), sapi); if (!lle) { struct gprs_llc_llme *llme; LOGP(DLLC, LOGL_ERROR, "LLC TX: unknown TLLI 0x%08x, " "creating LLME on the fly\n", msgb_tlli(msg)); llme = llme_alloc(msgb_tlli(msg)); lle = &llme->lle[sapi]; } The TX function uses the previously received TLLI to lookup for the LLE. The lle_by_tlli_sapi() performs the search, but preliminary it applies a foreign2local TLLI conversion to ensure to have a local one. Since no valid entry for the searched TLLI is found, a new one is created. And the problem is here. The new entry has the foreign TLLI. Next time the lookup fails again, and a new entry is created. This way, the counter N(U) is always reset, and the mobile do not recognize the message sequence and no attach is possible. My question is about foreign and local TLLIs. I patched the lookup, avoiding the conversion, so that the LLE is found and everything works fine... but... What is the sense of the conversion? Should the TLLI be always stored as a local one? Can this problem be solved with another foreign2local while allocating new entries? Actually, my problem has been solved with that workaround. But I'm curious to know what is the right way. Hope somebody can answer :) Thanks. Cheers, LM

5 6

Re: Help with sccp library
by mosbah abdelkader 07 Jul '25

07 Jul '25

> I don't understand. This callback will be called with data you need to write > to the network. In case of MTP Level3 you will need to wrap that around the > msgb you got. I means: is the interaction with mtp3 layer implemented (is sending sccp data by mtp3 implemented by the library?)? Also, what about the reception of data from mtp3 layer. is that implemented in the sccp lib. I am asking these questions because I see the code of mtp3 in the lib but no significant call is present in the sccp part of the lib. Thank you for your help.

4 3

Re: Any interest for Osmocom meetings in Bavaria ?
by Dieter Spaar 11 Jun '13

11 Jun '13

So far three persons have indicated their interest to join a meeting at my place. Considering the time it takes to drive to my place, it probably makes sense to have the meeting at the weekend (either Saturday or Sunday) so that there is more time for the meeting itself. I can suggest one of the following dates for the first meeting, somewhere between 10:00 to 18:00 on each day: 25.8. (Sa) or 26.8. (Su) 1.9. (Sa) or 2.9. (Su) 8.9. (Sa) or 9.9. (Su) So please let me know when you have time and also make suggestions in which Osmocom topic you are interested in so that we can have some sort of agenda for the meeting to make best use of the time. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

10 40

SimpleHLR: A web interface for OpenBSC
by Peter Caprioli 03 Jun '13

03 Jun '13

Hello everyone, I've just finnished writing together a small web interface for the OpenBSC HLR. It allows you to modify various parameters in the database and also provides a set of functions to modify the HLR or sending SMSes in your own scripts. The project is still very alpha but it seems to work reasonably good. Feel free to give any feedback! Screenshots and source code is available on my website: https://stormhub.org/simplehlr/ -- *Best regards, Peter Caprioli*

3 6

OpenBSC with LCR/SIP
by Kelum Navaratne 26 Jan '13

26 Jan '13

Hello list, First of all congratulation to developers of this project making such wonderful project in an interesting subject. I am new to this project and for past few days i managed to go through the documentation and get most of it tested. Thanks for pretty good documentation in most of the areas as well. I have the osmo-nitb working very fine using a nano bts. How ever when i try to install it with LCR to interconnect with external switch, im facing some problems. Initially i thought i must use LCR+Asterisk. But later i figured out there is a built in SIP interface on LCR which there is no need to asterisk or chan_asterisk. I would prefer to use this LCR SIP interface as i dont want to use asterisk and just want to forward all calls to another SIP switch. Now in this context there seems absolutely no documentation on both openbsc and LCR/mISDN lists. Can some one please shed me some light here on how to build a LCR with SIP to be work with osmo-nitb. All i want to test is GSM phone > Osmo-nitb > LCR with SIP > SIP softswitch Thank you very much for every one's effort in this project and would be glad to see some response for this. Best Regards Nava.

4 10

Several questions
by jason mercury 06 Dec '12

06 Dec '12

I have some questions: 1) When I start bsc_hack bsc_init.c first establishes OML link and initializes the bts then it establishes RSL link and bts starts broadcasting. However, it takes so much time to start the bts. Instead of this I want to do the following: it establishes OML link at the beginning and only once, then when i want to start broadcasting it establishes just the RSL link and bts will start faster since i don't have to wait for OML link. What should be done for this? 2) If i send one or two word messages from telnet interface it is okay. But if i send a longer message the phone could't receive the end of the message correctly(last words may be incomplete). Did any one encounter with this problem? What is wrong with me? 3) Could I send SMS in which extension of the sender is text not integer. For example, i want to send an information SMS that this is a test network. For this purpose i want to send an SMS from 'OpenBSC'. I set the extension of the first subscriber in database as text and tried to send the SMS but SMS wasn't delivered. What should i do? 4) Can i add SMS externally to SMS table of database? Thanks. Jason

4 3

[PATH] Selecting the latest nanoBTS firmware on connect Re: nanoBTS bring up problem
by Alexander Chemeris 03 Dec '12

03 Dec '12

Hi all, Here is a patch which selects the latest nanoBTS firmware when it tries to connect to OpenBSC. This fixed the problem with NACKs for us. Sometimes (like in our case) nanoBTS has two firmwares and could boot any of them. Which one to boot is selected by a BSC during the initial OML setup. Originally OpenBSC selected the first firmware available, which gave us random results - sometimes the older firmware was booted, sometimes the newer firmware was loaded. With this patch OpenBSC always selects the latest firmware to boot (using simple string comparison of firmware version strings). In our case this now gives stable results. PS I don't have time to improve this patch if it's too hackish to be checked in, but I hope it will inspire someone to create a better one. On Tue, Oct 23, 2012 at 4:10 PM, Ivan Kluchnikov <Ivan.Kluchnikov(a)fairwaves.ru> wrote: > Hi! > > We solved this problem, it seems, that ipaccess-config didn't work > correctly for our nanoBTS. > We set primary OML link IP and port using ipaccess-telnet and nanoBTS bring up. > Now we have working osmo-nitb. > > 2012/10/23 Ivan Kluchnikov <Ivan.Kluchnikov(a)fairwaves.ru>: >> Hi all! >> >> We tried to deploy our nanoBTS with osmo-nitb, but unfortunately we >> had no success. >> We have the following logs for ipaccess-find, ipaccess-config, >> osmo-nitb and ipaccess-telnet. >> We would appreciate it, if someone gives us advice. >> What does these logs mean? >> Is it possible, that the problem is in firmware, and we should update it? >> >> ./ipaccess-find >> MAC_Address='00:02:95:00:01:7e' IP_Address='172.44.4.75' >> Unit_ID='1801/0/0' Location_1='' Location_2='BTS_NBT131G' >> Equipment_Version='110_029_13' Software_Version='119a002_v149b18d0' >> Unit_Name='nbts-00-02-95-00-01-7E' Serial_Number='00024616' >> >> ./ipaccess-config -n 0x400/0x400 172.44.4.75 >> <0005> abis_nm.c:419 OC=SITE-MANAGER(00) INST=(ff,ff,ff) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=BTS(01) INST=(00,ff,ff) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) STATE >> CHG: OP_STATE=Disabled AVAIL=Not installed(07) >> OML link established using TRX 0 >> setting NV Flags/Mask to 0x0400/0x0400 >> <0005> abis_nm.c:419 OC=CHANNEL(03) INST=(00,00,00) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=CHANNEL(03) INST=(00,00,01) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=CHANNEL(03) INST=(00,00,02) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=CHANNEL(03) INST=(00,00,03) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=CHANNEL(03) INST=(00,00,04) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=CHANNEL(03) INST=(00,00,05) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=CHANNEL(03) INST=(00,00,06) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=CHANNEL(03) INST=(00,00,07) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=RADIO-CARRIER(02) INST=(00,00,ff) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=GPRS-NSE(f0) INST=(00,ff,ff) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=GPRS-CELL(f1) INST=(00,00,ff) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=GPRS-NSVC(f2) INST=(00,00,ff) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=GPRS-NSVC(f2) INST=(00,01,ff) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) >> IPACCESS(0xf0): SET NVATTR ACK >> Set the NV Attributes. >> >> ./osmo-nitb --debug=DRLL:DCC:DMM:DRR:DRSL:DNM -c openbsc.cfg >> DB: Database initialized. >> DB: Database prepared. >> <0005> abis_nm.c:419 OC=SITE-MANAGER(00) INST=(ff,ff,ff) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=BTS(01) INST=(00,ff,ff) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) STATE >> CHG: OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=CHANNEL(03) INST=(00,00,00) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=CHANNEL(03) INST=(00,00,01) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=CHANNEL(03) INST=(00,00,02) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=CHANNEL(03) INST=(00,00,03) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=CHANNEL(03) INST=(00,00,04) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=CHANNEL(03) INST=(00,00,05) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=CHANNEL(03) INST=(00,00,06) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=CHANNEL(03) INST=(00,00,07) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=RADIO-CARRIER(02) INST=(00,00,ff) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=GPRS-NSE(f0) INST=(00,ff,ff) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=GPRS-CELL(f1) INST=(00,00,ff) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=GPRS-NSVC(f2) INST=(00,00,ff) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=GPRS-NSVC(f2) INST=(00,01,ff) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=SITE-MANAGER(00) INST=(ff,ff,ff) SW Activate >> Request: <0005> abis_nm.c:418 Software Activate Request, ACKing and >> Activating >> <0005> abis_nm.c:439 Found SW config: 42 12 00 08 31 31 39 61 30 30 32 >> 00 13 00 0a 76 31 34 39 62 31 38 64 30 00 42 12 00 08 31 31 39 61 30 >> 30 32 00 13 00 0a 76 32 30 39 62 32 36 64 30 00 >> <0005> abis_nm.c:419 OC=SITE-MANAGER(00) INST=(ff,ff,ff) STATE CHG: >> OP_STATE=Disabled AVAIL=Not installed(07) >> <0005> abis_nm.c:419 OC=SITE-MANAGER(00) INST=(ff,ff,ff) Software >> Activated Report >> <0005> abis_nm.c:419 OC=SITE-MANAGER(00) INST=(ff,ff,ff) STATE CHG: >> OP_STATE=Disabled AVAIL=Off line(03) >> <0005> abis_nm.c:419 OC=SITE-MANAGER(00) INST=(ff,ff,ff) Sending OPSTART >> <0005> abis_nm.c:419 OC=BTS(01) INST=(00,ff,ff) SW Activate Request: >> <0005> abis_nm.c:418 Software Activate Request, ACKing and Activating >> <0005> abis_nm.c:439 Found SW config: 42 12 00 08 31 31 39 61 30 30 32 >> 00 13 00 0a 76 31 34 39 62 31 38 64 30 00 >> <0005> abis_nm.c:419 OC=GPRS-NSE(f0) INST=(00,ff,ff) SW Activate >> Request: <0005> abis_nm.c:418 Software Activate Request, ACKing and >> Activating >> <0005> abis_nm.c:439 Found SW config: 42 12 00 08 31 31 39 61 30 30 32 >> 00 13 00 0a 76 31 34 39 62 31 38 64 30 00 >> <0005> abis_nm.c:419 OC=SITE-MANAGER(00) INST=(ff,ff,ff) STATE CHG: >> OP_STATE=Enabled >> <0005> abis_nm.c:419 OC=SITE-MANAGER(00) INST=(ff,ff,ff) Sending OPSTART >> <0005> abis_nm.c:419 OC=BTS(01) INST=(00,ff,ff) Software Activated Report >> <0005> abis_nm.c:419 OC=BTS(01) INST=(00,ff,ff) STATE CHG: >> OP_STATE=Disabled AVAIL=Dependency(05) >> <0005> abis_nm.c:1379 Set BTS Attr (bts=0) >> <0005> abis_nm.c:419 OC=BTS(01) INST=(00,ff,ff) Sending OPSTART >> <0005> abis_nm.c:419 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) SW >> Activate Request: <0005> abis_nm.c:418 Software Activate Request, >> ACKing and Activating >> <0005> abis_nm.c:439 Found SW config: 42 12 00 08 31 31 39 61 30 30 31 >> 00 13 00 0a 76 32 30 39 62 32 36 64 30 00 42 12 00 08 31 31 39 61 30 >> 30 32 00 13 00 0a 76 31 34 39 62 31 38 64 30 00 >> <0005> abis_nm.c:419 OC=RADIO-CARRIER(02) INST=(00,00,ff) SW Activate >> Request: <0005> abis_nm.c:418 Software Activate Request, ACKing and >> Activating >> <0005> abis_nm.c:439 Found SW config: 42 12 00 08 31 31 39 61 30 30 31 >> 00 13 00 0a 76 32 30 39 62 32 36 64 30 00 42 12 00 08 31 31 39 61 30 >> 30 32 00 13 00 0a 76 31 34 39 62 31 38 64 30 00 >> <0005> abis_nm.c:419 OC=GPRS-NSE(f0) INST=(00,ff,ff) Software Activated Report >> <0005> abis_nm.c:419 OC=GPRS-NSE(f0) INST=(00,ff,ff) STATE CHG: >> OP_STATE=Disabled AVAIL=Dependency(05) >> <0005> abis_nm.c:419 OC=GPRS-CELL(f1) INST=(00,00,ff) SW Activate >> Request: <0005> abis_nm.c:418 Software Activate Request, ACKing and >> Activating >> <0005> abis_nm.c:439 Found SW config: 42 12 00 08 31 31 39 61 30 30 32 >> 00 13 00 0a 76 31 34 39 62 31 38 64 30 00 >> <0005> abis_nm.c:419 OC=GPRS-NSVC(f2) INST=(00,00,ff) SW Activate >> Request: <0005> abis_nm.c:418 Software Activate Request, ACKing and >> Activating >> <0005> abis_nm.c:439 Found SW config: 42 12 00 08 31 31 39 61 30 30 32 >> 00 13 00 0a 76 31 34 39 62 31 38 64 30 00 >> <0005> abis_nm.c:419 OC=GPRS-NSVC(f2) INST=(00,01,ff) SW Activate >> Request: <0005> abis_nm.c:418 Software Activate Request, ACKing and >> Activating >> <0005> abis_nm.c:439 Found SW config: 42 12 00 08 31 31 39 61 30 30 32 >> 00 13 00 0a 76 31 34 39 62 31 38 64 30 00 >> <0005> abis_nm.c:419 OC=BTS(01) INST=(00,ff,ff) STATE CHG: >> OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked >> <0005> abis_nm.c:419 OC=BTS(01) INST=(00,ff,ff) OPSTART NACK >> CAUSE=Message cannot be performed >> <0005> bsc_init.c:54 Got a NACK going to drop the OML links. >> >> ./ipaccess-telnet 172.44.4.75 3210 >> 14851:DBG:CLI_SKT:Remote client 172.44.4.4 connected >> 16160:DBG:IP_CHANNEL:Assigning RX Client A >> 16160:DBG:IP_CHAN_RX_A:Attempting connection to 172.44.4.4:3002 >> 20572:DBG:IP_CHANNEL:Assigning RX Client A >> 20572:DBG:IP_CHAN_RX_A:Attempting connection to 172.44.4.4:3002 >> 21007:DBG:OAM_IM:Set SYSTEM LINK to 65.255 >> 21051:DBG:OAM_MOI:Can Activate?=TRUE >> 21051:DBG:OAM_MOI:Sw Activate - activating BH idx=1 >> 21051:DBG:OAM_MOI:Sw Activate - BH(def=1 act=1) TRX(def=1 act=255) >> 21051:DBG:OAM_IM:roleInstanceProcClearContaineeFlags: BTS:0 flag 3 not >> setting or set! >> 21051:DBG:OAM_IM:roleInstanceProcClearContaineeFlags: GPRS NSE:0 flag >> 3 not setting or set! >> 21063:DBG:OAM_MOI:Can Activate?=TRUE >> 21063:DBG:OAM_MOI:Sw Activate - already activated BH idx=1 >> 21063:DBG:OAM_MOI:Sw Activate - BH(def=1 act=1) TRX(def=1 act=255) >> 21064:DBG:OAM_MOI:Can Activate?=TRUE >> 21064:DBG:OAM_MOI:Sw Activate - already activated BH idx=1 >> 21064:DBG:OAM_MOI:Sw Activate - BH(def=1 act=1) TRX(def=1 act=255) >> 21067:DBG:GB_OAM:Received OPEN_REQ for NSE 0. >> 21075:DBG:OAM_IM:Ignored imSetFrameNumber. >> 21075:DBG:OAM_MOI:oid=BTS:0 publisher attributes set >> 21077:DBG:OAM_MOI:Can Activate?=TRUE >> 21078:DBG:OAM_MOI:Sw Activate - already activated BH idx=1 >> 21078:DBG:OAM_MOI:Sw Activate - sending trx boot request to activate TRX idx=1 >> 21078:DBG:OAM_MOI:Sw Activate - BH(def=1 act=1) TRX(def=1 act=1) >> 21078:DBG:OAM_MOI:Can Activate?=TRUE >> 21078:DBG:OAM_MOI:Sw Activate - already activated BH idx=1 >> 21079:DBG:OAM_MOI:Sw Activate - already activated TRX idx=1 >> 21079:DBG:OAM_MOI:Sw Activate - BH(def=1 act=1) TRX(def=1 act=1) >> 21079:DBG:OAM_MOI:Can Activate?=TRUE >> 21079:DBG:OAM_MOI:6110:gprs.cell: EVENT 0x000007d4 rxd in STATE initial >> 21079:DBG:OAM_MOI:Sw Activate - already activated BH idx=1 >> 21079:DBG:OAM_MOI:Sw Activate - BH(def=1 act=1) TRX(def=1 act=1) >> 21079:DBG:OAM_MOI:6112:gprs.cell: EVENT 0x000007cb rxd in STATE >> waitopenresources >> 21080:DBG:OAM_MOI:6124:gprs.cell: EVENT 0x000007cd rxd in STATE >> waitregisterdependencycnf >> 21080:DBG:OAM_MOI:6125:gprs.cell: EVENT 0x000007cd rxd in STATE >> waitregisterdependencycnf >> 21080:DBG:OAM_MOI:6126:gprs.cell: EVENT 0x000007cd rxd in STATE >> waitregisterdependencycnf >> 21081:DBG:OAM_MOI:6127:gprs.cell: EVENT 0x000007cd rxd in STATE >> waitregisterdependencycnf >> 21081:DBG:OAM_MOI:6128:gprs.cell: EVENT 0x000007cd rxd in STATE >> waitregisterdependencycnf >> 21081:DBG:OAM_MOI:6129:gprs.cell: EVENT 0x000007cd rxd in STATE >> waitregisterdependencycnf >> 21081:DBG:OAM_MOI:6130:gprs.cell: EVENT 0x000007cd rxd in STATE >> waitregisterdependencycnf >> 21081:DBG:OAM_MOI:6131:gprs.cell: EVENT 0x000007cd rxd in STATE >> waitregisterdependencycnf >> 21082:DBG:OAM_MOI:6132:gprs.cell: EVENT 0x000007cd rxd in STATE >> waitregisterdependencycnf >> 21082:DBG:OAM_MOI:6133:gprs.cell: EVENT 0x000007cd rxd in STATE >> waitregisterdependencycnf >> 21083:DBG:OAM_MOI:6134:gprs.cell: EVENT 0x000007cd rxd in STATE >> waitregisterdependencycnf >> 21086:DBG:OAM_MOI:Can Activate?=TRUE >> 21086:DBG:OAM_MOI:Sw Activate - already activated BH idx=1 >> 21086:DBG:OAM_MOI:Sw Activate - BH(def=1 act=1) TRX(def=1 act=1) >> 21087:DBG:OAM_MOI:Can Activate?=TRUE >> 21087:DBG:OAM_MOI:Sw Activate - already activated BH idx=1 >> 21087:DBG:OAM_MOI:Sw Activate - BH(def=1 act=1) TRX(def=1 act=1) >> 21088:DBG:OAM_MOI:6166:gprs.cell: EVENT 0x000007ca rxd in STATE waitopencnf >> 21088:DBG:GB_OAM:Received OPEN_REQ for NSVC 0. >> 21089:DBG:GB_OAM:Received OPEN_REQ for NSVC 1. >> 21089:DBG:TRX_BOOT:Sending Cnf idx=1 token=969 task=2 >> 21098:DBG:TRX_BOOT:Sending Cnf idx=1 token=1031 task=2 >> 21519:DBG:OAM_IM:Clear SYSTEM LINK >> 21523:DBG:OAM_MOI:6426:gprs.cell: EVENT 0x000007c7 rxd in STATE active >> 21523:DBG:OAM_MOI:6426:gprs.cell: EXITING swactivated >> 21527:DBG:OAM_RES:Failed to deregister dependency: token=1024 not >> found (class=1 instance=7) >> 21527:DBG:OAM_RES:Failed to deregister dependency: token=1017 not >> found (class=1 instance=6) >> 21527:DBG:OAM_RES:Failed to deregister dependency: token=1010 not >> found (class=1 instance=5) >> 21527:DBG:OAM_RES:Failed to deregister dependency: token=1003 not >> found (class=1 instance=4) >> 21527:DBG:OAM_RES:Failed to deregister dependency: token=996 not found >> (class=1 instance=3) >> 21527:DBG:OAM_RES:Failed to deregister dependency: token=989 not found >> (class=1 instance=2) >> 21528:DBG:OAM_RES:Failed to deregister dependency: token=982 not found >> (class=1 instance=1) >> 21528:DBG:OAM_RES:Failed to deregister dependency: token=975 not found >> (class=1 instance=0) >> 21528:DBG:OAM_RES:Failed to deregister dependency: token=969 not found >> (class=0 instance=0) >> 21528:DBG:OAM_RES:Failed to deregister dependency: token=1031 not >> found (class=2 instance=0) >> 21528:DBG:OAM_RES:Failed to deregister dependency: token=964 not found >> (class=2 instance=0) >> 21528:DBG:OAM_RES:Failed to deregister dependency: token=964 not found >> (class=1 instance=0) >> 21528:DBG:OAM_RES:Failed to deregister dependency: token=1047 not >> found (class=2 instance=0) >> 21528:DBG:OAM_RES:Failed to deregister dependency: token=1047 not >> found (class=1 instance=0) >> 21608:DBG:DB_EE:Writing 174 bytes of DBX data to block 3 >> 21608:DBG:DB_EE:Re-using existing DBX block >> 21857:DBG:DB_EE:NV block 3 - wrote block to NV, main and backup OK. >> 21857:DBG:DB_EE:EE update complete. >> 21931:DBG:DB_EE:EE update complete. >> 22004:DBG:DB_EE:EE update complete. >> 22078:DBG:DB_EE:EE update complete. >> 22151:DBG:DB_EE:EE update complete. >> 22225:DBG:DB_EE:EE update complete. >> 22298:DBG:DB_EE:EE update complete. >> 22371:DBG:DB_EE:EE update complete. >> >> >> -- >> Regards, >> Ivan Kluchnikov. >> http://fairwaves.ru > > > > -- > Regards, > Ivan Kluchnikov. > http://fairwaves.ru > -- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru

2 7

SI Generation and multi-trx setup
by Holger Hans Peter Freyther 26 Nov '12

26 Nov '12

Hi Andreas, Harald, the recent "SI generation" fix broke multi trx setups. This is because when the first (c0) TRX is going up bts->si_valid will include SI2 and other SIs scheduled on the BCCH and once the second trx is going up the code decides it only needs to generate the SI5 (and more). But si_valid still includes SI2 and it will be set on the second trx. I have fixed it locally by setting si_valid to 0 early in the set_system_infos routine and added a warning for this case. How should this be properly fixed for master? Will the content of a specific SI differ from TRX0 to TRX1 of a BTS? Should the si_valid be moved to the trx data structure? I have attached my local patch and would like to have a review for it. comments? ideas? holger

2 7

29C3 osmo-nitb sprint and issues
by Holger Hans Peter Freyther 08 Nov '12

08 Nov '12

Hi, as indicated in the previous mail there are some things to be done before we get to the venue. I would like to experiment with sprints to solve some of the stability issues we had with osmo-nitb. The idea is that we assemble (physically or online) and work on some specific issues of osmo-nitb that impact the quality of service for the upcoming event. I can provide food and snacks during these sprints and guidance on OpenBSC code. The first sprint is scheduled for the 9th, 10th (and maybe 11th) of November. There is no venue for it yet, maybe the CCCB. Please indicate if you are interested to join. The general list of osmo-nitb issues are: * Channel release process. There is a branch I created at the last congress but I have never tested it. This includes making a SAPI=3 local release, using the proper timeouts for the abnormal release making sure the SACCH is deactivated and some more issues. This requires quite a bit of testing. * Allow to block/unblock failing lchans. We have had this issue with Nokia BTS but it can happen on other BTS as well. E.g. a given timeslot might not be allocatable, or we get LCHAN ACT NACK. In that case OpenBSC should block the lchan. * smsqueue/auth/paths. In the past years we have seen that the smsqueue and other parts can get stuck because of the 'subscr_get_con' not being properly called in all error conditions. We need to review the code and check how things get stuck. * Handover testing and patching out the 'timestamp' adjusting or fixing it. Right now it can be used to add a lot of delay by switching cells. cheers holger

1 2

triplets calculation
by Yann R. Moupinda 01 Nov '12

01 Nov '12

Hi guys, i'm trying to interconnect a WLAN router with my GSM-sysmoBTS and to use the EAP-SIM authentication protocol. For that i installed a Freeradius on an external board that i use as radius server. The Freeradius should use a database file in order to realise the authentication and the idea is that Freeradius should be able to read the hlr.sqlite3 file from my sysmoBTS. I'm not so far to do this part of the work so, i first want to do some tests using the sim card from sysmoBTS (imsi und ki) and the triplets (RAND, Kc and SRES). I want to create a flat file containing this values so the Freeradius will directly use the file to get the triplets. I thought i could get the triplets stored in one of the tables of hlr.sqlite3 (AuthLastTuples) but there is no information on it. From the table AuthKeys i could find some Ki values (e.g X'019B7083FBAFC928421A147DE795217782'). I found that there is an "osmo-auc-gen" program for computing the triplets. By using the Ki from AuthKeys and a self generated RAND (e.g 0123456789ABCDEF0123456789ABCDEF) the program doesn't run and doesn't give the triplets. The used authentication algorithm is the COMP128v1. Has anyone an idea why it doesn't work and why there is no information in the AuthLastTuples table from sysmoBTS ? best regards Yann

2 2