OpenBSC

openbsc@lists.osmocom.org

4315 discussions

Problem with running OsmoSGSN and OsmoNITB
by Wojciech Sedlaczek 04 Dec '12

04 Dec '12

Hi, I have a problem with running 2 software programs OpenBSC (osmo-nitb and osmo-sgsn). When I run osmo-nitb: ROOT: /media/obsc_gprs/gitrep/openbsc/openbsc/src/osmo-nitb# ./osmo-nitb There is no such command. Error occurred during reading below line: logging level mi notice <0005> bsc_init.c:496 Failed to parse the config file: 'openbsc.cfg' ______________________________________________________________ However, when I run osmo-sgsn: ROOT: /media/obsc_gprs/gitrep/openbsc/openbsc/src/gprs# ./osmo-sgsn <0011> gprs_ns.c:171 NSVCI=65534 Creating NS-VC <0010> sgsn_libgtp.c:571 Failed to create GTP: -1 <0010> sgsn_main.c:348 Cannot bind/listen on GTP socket Anybody help?

1 0

RNC Support
by AD 03 Dec '12

03 Dec '12

2 1

[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

nanoBTS model 139 and model 165 for sale
by Stuart Baggs 27 Nov '12

27 Nov '12

Hi All We're selling some of our pico cell stock that has been on our shelf for a few months. We have 1 x brand new model 139 pico cell (1800 MHz GPRS), 1 x model 165g (1800 MHz GPRS/EDGE) and 1 x model 165cu (900 MHz GPRS/EDGE). These on on offer first come first served. Kind Regards Stuart Baggs Managing Director BlueWave Communications Limited Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender immediately . This message contains confidential information and is intended solely for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

1 0

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

nanoBTS amplifier
by Adolfo Cugat 24 Nov '12

24 Nov '12

What amplifier do you use with ip.access BTS ??? Adolfo

2 1

Need to buy osmo-NITB
by Akib Sayyed 18 Nov '12

18 Nov '12

Hey guys i wanted to buy Osmo -NITB is it on sale ?? please let me know -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243

3 4

SMPP 3.4 interface in OsmoNITB
by Harald Welte 16 Nov '12

16 Nov '12

Hi all, in case you follow the changelog, you will already have seen this coming: OsmoNITB now has a SMPP interface for submitting MT-SMS. This is by no means some kind of competition to a more complete SMSC developed by other people on this list, but it was a quick solution to a requirement of a commercial user. You can use it to submit SMS identifying the recipient subscriber either by his extension or his IMSI. OsmoNITB will also send SMPP ALERT NOTIFICATION in case a previously detached subscriber comes online again. Contrary to the spec, you don't have to subscribe ot ALERT NOTIFICATIONS, but they will be sent to all ESME's registered. The SMPP interface supports both store-and-forward (via database) as well as forward/transactoin mdoe, where the SMS is attempted for immediate delivery, not buffered and will only send a positive SUBMIT-SM result in case it was acknowledged by the MS. You can submit both GSM charset as well as binary messages. UCS2 is not tested. multi-part SMS (or anything else using UDH) only works with binary SMS at this point, i.e. GSM alphabet encoded multi-part messages are broken. The interface will soon be extended to also cover MO-SMS, where you would configure a given destination address by VTY and then messages to that address would be forwarded to the ESME. Only SMPP 3.4 is currently supported. You will need libsmpp34 from git://git.osmocom.org/libsmpp34.git and need to build openbsc with '--enable-smpp' Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

FYI: Testing/merging jolly/sms (and zecke/jolly-sms)
by Holger Hans Peter Freyther 15 Nov '12

15 Nov '12

Hi all, I have rebased jolly/sms and split it up (first use the routines that were moved to libosmocore and that create compile errors, then begin to use the DLSMS debug area, then the actual patches in a way that all of them compile to allow to bisect them). I am now manually testing them with the help of the sysmocom modem bank. There are various issues that needs to be resolved before the 29C3 to be able to use the code. I am just listing them here for reference. There is a double trans_free in the new code now that will lead to segfaults and various 'soft' failures. I am just including some log messages: gsm0411_smc.c:308 Cannot release yet current state: WAIT_CP_ACK gsm0411_smc.c:511 Message 0x332/1 unhandled at this state WAIT_CP_ACK. gsm0411_smc.c:517 RX Unimplemented CP msg_type: 0x332 gsm0411_smc.c:134 TX CP-ERROR, cause 97 (Message Type doesn't exist) gsm_04_11.c:913 Transaction contains SMS. gsm_04_11.c:441 RP-DATA (MO) without DST or TPDU ?!? gsm_04_11.c:420 TX: SMS RP ERROR, cause 96 (Invalid Mandatory Information) cheers holger

3 7

gsm and isdn at 29c3
by Andreas Eversberg 15 Nov '12

15 Nov '12

hi list, we (ccc meber and me) are trying to get a pri access line (primary rate isdn) this year. it will provide external connection for the poc (eventphone) and will also allow interconnection of gsm network with the rest of the world. it is not yet clear if we get this line, but we are working on it. the hardware and software side is already tested in our "labs". for connection between poc and gsm network (openbsc), we like to use lcr (linux-call-router via mncc interface). there are two ways to connect to eventphone, one via isdn line (or virtual isdn over ip) and another one via sip trunk. we like to use both ways for better testing. the registration process for gsm extensions is already set up by evenphone. visit https://www.eventphone.de to register your gsm extension. for syncing eventphone's database with hlr of openbsc, i can provide help. also i will provide helpdesk for gsm questions this year again. regards, andreas

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC