OpenBSC June 2013

openbsc@lists.osmocom.org

17 participants
31 discussions

Pysim error: SW match failed
by Martin Nagy 16 Aug '25

16 Aug '25

Hi all, After buying a super Sim Kit (16 in 1) from China, I tried the reader (green PCB inside a blue transparent plastic case with a blue LED) and SIM (identified as a fakesupersim) with pysim tool. However i am getting the following error: /pySim-prog.py -n 26C3 -c 49 -x 262 -y 42 -z 1234 -j 1 -t auto Insert card now (or CTRL-C to cancel) Autodetected card type fakemagicsim Generated card parameters : > Name : 26C3 > SMSP : e1ffffffffffffffffffffffff058100945555ffffffffffff000000 > ICCID : 8949262427518313026 > MCC/MNC : 262/42 > IMSI : 262422461512085 > Ki : 7b74741a1ee14337ec23f9ab92a13648 > OPC : ccd867d60797d8d45354a51b3ef568ff Programming ... Traceback (most recent call last): File "./pySim-prog.py", line 530, in <module> card.program(cp) File "/home/nadicek/pysim/pysim/pySim/cards.py", line 231, in program self._scc.update_binary('6f30', hplmn + 'ff' * (tl-3)) File "/home/nadicek/pysim/pysim/pySim/commands.py", line 53, in update_binary return self._tp.send_apdu_checksw(pdu) File "/home/nadicek/pysim/pysim/pySim/transport/__init__.py", line 87, in send_apdu_checksw raise RuntimeError("SW match failed ! Expected %s and got %s." % (sw.lower(), rv[1])) RuntimeError: SW match failed ! Expected 9000 and got 9804. I checked mailing lists and haven’t found anybody who had similar problem with pysim. Also I have tried forcing different models of SIM, but nothing is working. Obviously I can remove this check from the script file (__init__.py in /pySim/transport), however somebody had a reason to put such condition there. I would like to ask if it is safe to remove that line of code and the purpose of that line of code. Thanks a lot and best regards Martin

3 3

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: Osmo-nitb v_0.13.0.48-9e22 broke compatibility with Nokia InSite
by Sipos Csaba 02 Aug '13

02 Aug '13

Hi Holger, I was able to narrow it down, and it seems this is the patch that causing the problem: http://cgit.osmocom.org/libosmocore/commit/?id=f5a079f739c57d8be7c59149fd45… Up to that patch it works (more or less), but after I applied it, I got this seg faults. I don't know how to do back traces but I try to get some info about this topic and will send the results. Csaba

3 12

Nokia InSite configuration check
by Sipos Csaba 30 Jun '13

30 Jun '13

Dear members, In connection with the problem I found, I kindly ask someone, to please check my configuration, because I want to rule out any configuration related issue, don't want to waste anyones time with sending false bug reports. Currently I am using a GSM1800 Nokia InSite unit with a Dahdi E1 card and OpenBSC, the DAHDI card is the timing source. /etc/dahdi/system.conf span=1,0,0,ccs,hdb3,crc4 bchan=2-31 dchan=1 OpenBSC conf: password foo line vty no login e1_input e1_line 0 driver dahdi network network country code 1 mobile network code 1 short name OpenBSC long name OpenBSC mm info 1 timer t3101 10 timer t3113 60 bts 0 type nokia_site band GSM1800 cell_identity 1 location_area_code 1 base_station_id_code 63 training_sequence_code 7 ms max power 40 periodic location update 10 oml e1 line 0 timeslot 5 sub-slot full oml e1 tei 1 trx 0 arfcn 885 nominal power 22 max_power_red 0 rsl e1 line 0 timeslot 4 sub-slot full rsl e1 tei 1 timeslot 0 phys_chan_config CCCH+SDCCH4 e1 line 0 timeslot 2 sub-slot 0 timeslot 1 phys_chan_config TCH/F e1 line 0 timeslot 2 sub-slot 1 timeslot 2 phys_chan_config TCH/F e1 line 0 timeslot 2 sub-slot 2 timeslot 3 phys_chan_config TCH/F e1 line 0 timeslot 2 sub-slot 3 timeslot 4 phys_chan_config TCH/F e1 line 0 timeslot 3 sub-slot 0 timeslot 5 phys_chan_config TCH/F e1 line 0 timeslot 3 sub-slot 1 timeslot 6 phys_chan_config TCH/F e1 line 0 timeslot 3 sub-slot 2 timeslot 7 phys_chan_config TCH/F e1 line 0 timeslot 3 sub-slot 3 My main concern is about the OML and RSL TEI addresses. If I understand it correctly, OML TEI identifies the BTS, RSL TEI identifies the TRX of that BTS. So if I have 2 BTSs and 2-2 TRXs, then the correct configuration would be looking like this: BTS0: oml: te1 1 trx0: tei 1 trx1: tei 2 trx2: tei 3 .... BTS1: oml: tei 2 trx0: tei 1 trx1: tei 2 trx2: tei 3 ... ? Even the Nokia BTS commissioning documentation is unclear about the specifics: sapi =Service access point identifier. (62 for OMUSIG, 0 for TRXSIG.) tei =Terminal end point identifier. Must the same as defined in the BTS. Usually the same as the TRX number. For OMU link, the value is 1. According to this, every OML TEI of every BTS should be "1" ? The other funny part is, that it sais it must be the same as defined in the BTS, but Nokia BTS Manager does not have any parameter for TEI or SAPI to set. My other concerns are BSIC and Training Sequence Code (TSC). As I know, BSIC identifies the BTS in a location and/or routing area, it means that a location/routing area can have 64 BTSs at top (BSIC=0-63), and every BTS have to use unique BSIC in the same LAC? TSC is another mystery. Nokia Docs sais: train_seq = Training sequence code. (eg. BCC value of the BSIC, eg. 7) This has to be 7 all the time, or if I have more than one BTS (in the same LAC and on the same E1)I have to change this? Finally, DAHDI configuration: How many D channels should I specify? For example if I have 2 BTSs on the same E1, I have to specify two D channels for every OMUSIG timeslots? Or I have to specify D channels for every timeslots I use for signalling (OMUSIG and TRXSIG for all BTSs)? Or maybe I don't have to allocate even one D channel, because I dedicate separate signalling and TCH timeslots for every BTS? I searched a lot about this topic, but the information available is limited, not specific and most of the time lead to more questions... I hope someone can enlighten me in this topic. BR, Csaba

1 0

[PATCH] contrib: A shell script to send command(s) to osmo-nitb/osmo-bts live instances.
by Alexander Chemeris 30 Jun '13

30 Jun '13

Hi all, Attached is a shell script I found useful for monitoring a live installation of OsmoNITB. I hope it'll be useful for someone else and propose to check it into the 'contrib' directory of the OpenBSC repository. Actually I believe that Holger's zecke/features/nitb-ctrl-interface branch should be merged into the master, as it makes such monitoring much easier and failsafe. PS I think it would be useful create a wiki-page with cheat-sheet of useful commands during the OpenBSC operation. I could start putting something together if there are no objections to that. I would appreciate recommendations for the wiki page name and location too. -- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru

2 1

Osmo-nitb v_0.13.0.48-9e22 broke compatibility with Nokia InSite
by Sipos Csaba 28 Jun '13

28 Jun '13

Dear members, It seems that the latest Osmo-nitb (0.13.0.48-9e22) broke compatibility with Nokia InSite. I am using a GSM1800 unit with an E1 dahdi card, and with the following config it was working fine with a previous version (osmo-nitb v.0.13.0.33-e152a4): openbsc.cfg: ! OpenBSC configuration saved from vty ! ! password foo ! line vty no login ! e1_input e1_line 0 driver dahdi network network country code 1 mobile network code 1 short name OpenBSC long name OpenBSC mm info 1 timer t3101 10 timer t3113 60 bts 0 type nokia_site band GSM1800 cell_identity 1 location_area_code 1 base_station_id_code 63 training_sequence_code 7 ms max power 40 periodic location update 10 oml e1 line 0 timeslot 5 sub-slot full oml e1 tei 1 trx 0 arfcn 885 nominal power 22 max_power_red 0 rsl e1 line 0 timeslot 4 sub-slot full rsl e1 tei 1 timeslot 0 phys_chan_config CCCH+SDCCH4 e1 line 0 timeslot 2 sub-slot 0 timeslot 1 phys_chan_config TCH/F e1 line 0 timeslot 2 sub-slot 1 timeslot 2 phys_chan_config TCH/F e1 line 0 timeslot 2 sub-slot 2 timeslot 3 phys_chan_config TCH/F e1 line 0 timeslot 2 sub-slot 3 timeslot 4 phys_chan_config TCH/F e1 line 0 timeslot 3 sub-slot 0 timeslot 5 phys_chan_config TCH/F e1 line 0 timeslot 3 sub-slot 1 timeslot 6 phys_chan_config TCH/F e1 line 0 timeslot 3 sub-slot 2 timeslot 7 phys_chan_config TCH/F e1 line 0 timeslot 3 sub-slot 3 /etc/dahdi/system.conf span=1,0,0,ccs,hdb3,crc4 bchan=2-31 dchan=1 Error message with the most recent verion: root@openbsc:~# osmo-nitb -c /root/1800_nokia.cfg <0018> input/lapd.c:212 LAPD Allocating SAP for SAPI=62 / TEI=1 <0018> input/lapd.c:223 k=1 N200=3 N201=260 T200=1.0 T203=10.0 <0018> input/lapd.c:485 LAPD DL-ESTABLISH request TEI=1 SAPI=62 <0018> input/lapd.c:212 LAPD Allocating SAP for SAPI=62 / TEI=1 <0018> input/lapd.c:223 k=1 N200=3 N201=260 T200=1.0 T203=10.0 <0018> input/lapd.c:485 LAPD DL-ESTABLISH request TEI=1 SAPI=62 DB: Database initialized. DB: Database prepared. <001d> sms_queue.c:220 Attempting to send 20 SMS <0018> input/lapd.c:624 LAPD DL-ESTABLISH confirm TEI=1 SAPI=62 <0005> bts_nokia_site.c:58 bootstrapping OML for BTS 0 <0005> bts_nokia_site.c:1679 ABIS_OM_MDISC_FOM <0005> bts_nokia_site.c:1507 (0x81) NOKIA_BTS_ACK <0005> bts_nokia_site.c:1539 ACK = 1 <0018> input/lapd.c:513 LAPD DL-RELEASE request TEI=1 SAPI=62 <0018> input/lapd.c:628 LAPD DL-RELEASE confirm TEI=1 SAPI=62 <0018> input/lapd.c:513 LAPD DL-RELEASE request TEI=1 SAPI=62 <0018> input/lapd.c:628 LAPD DL-RELEASE confirm TEI=1 SAPI=62 Segmentation fault (core dumped) root@openbsc:~# I have to admit that even with the previous versions I had issues, like a lot of radio link failures, unstable voice calls (lasting only 1-2 minutes), but now it wont start at all. Thanks in advance! Csaba

2 1

OpenBSC unsubscribe notification
by mailman-bounces＠lists.osmocom.org 26 Jun '13

26 Jun '13

situsaja(a)bshellz.net has been removed from OpenBSC.

1 0

Slow database access at OpenBSC
by Andreas Eversberg 24 Jun '13

24 Jun '13

hi, i experienced audio glitches while another phone does location updating: <0001> gsm_04_08.c:191 (bts 1 trx 0 ts 0 pd 05) Sending 0x18 to MS. <0008> abis_rsl.c:1027 [262421104120913] MEASUREMENT RESULT NR=0 RXL-FULL-ul=-110dBm RXL-SUB-ul=-47dBm R Q-FULL-ul=0 RXQ-SUB-ul=0 BS_POWER=0 L1_MS_PWR= 0dBm L1_FPC=0 L1_TA=0 NOT VALID NUM_NEIGH=0 <0003> bsc_api.c:615 CLASSMARK CHANGE CM2(len=3) CM3(len=4) dbi access time 95ms Stalled 96ms <0008> abis_rsl.c:1027 [262421104120913] MEASUREMENT RESULT NR=1 RXL-FULL-ul=-66dBm RXL-SUB-ul=-47dBm RX -FULL-ul=0 RXQ-SUB-ul=0 BS_POWER=0 L1_MS_PWR= 0dBm L1_FPC=0 L1_TA=0 RXL-FULL-dl=-47dBm RXL-SUB-dl=-47dB RXQ-FULL-dl=0 RXQ-SUB-dl=0 NUM_NEIGH=7 dbi access time 50ms dbi access time 0ms dbi access time 49ms dbi access time 58ms dbi access time 83ms dbi access time 0ms dbi access time 0ms dbi access time 0ms dbi access time 72ms <0003> gsm_04_08_utils.c:315 TX CIPHERING MODE CMD Stalled 319ms <0008> abis_rsl.c:1027 [262421104120913] MEASUREMENT RESULT NR=2 RXL-FULL-ul=-65dBm RXL-SUB-ul=-47dBm RX -FULL-ul=0 RXQ-SUB-ul=0 BS_POWER=0 L1_MS_PWR= 0dBm L1_FPC=0 L1_TA=0 RXL-FULL-dl=-47dBm RXL-SUB-dl=-47dB RXQ-FULL-dl=0 RXQ-SUB-dl=0 NUM_NEIGH=7 <0003> osmo_msc.c:105 CIPHERING MODE COMPLETE dbi access time 0ms dbi access time 69ms <0001> gsm_04_08.c:191 (bts 1 trx 0 ts 0 pd 05) Sending 0x02 to MS. <0001> gsm_04_08.c:191 (bts 1 trx 0 ts 0 pd 05) Sending 0x32 to MS. dbi access time 66ms dbi access time 0ms dbi access time 0ms <0003> gsm_04_08.c:1249 TX APPLICATION INFO id=0x00, len=4 <0001> gsm_04_08.c:191 (bts 1 trx 0 ts 0 pd 06) Sending 0x38 to MS. dbi access time 0ms Stalled 140ms the total time that openbsc was stalling is 555ms in this case. there are only 4 subscribers in hlr and counter writing is disabled. is there any trick to make database access faster? speeding up the db access does not solve the problem. an async db access is one solution, but there is other code at openbsc that might require some time. (e.g. handling of many measurement reports) one solution is to have an own thread for the audio processing. this thread must access different interfaces independently from the rest of the openbsc code: - RTP sockets - MNCC socket - TRAU sockets of E1 timeslots MNCC socket could be split into two sockets: one for signalling, one for audio traffic. this way it is not required to use queues and signals between main thread and audio thread. a problem in case of multithreading is osmo_select_main(). it uses global list of file descriptors and global rb-tree for timers. one solution would be having multiple lists and trees for each thread id. this way it is not required to change timer and file descriptor api. another solution could be a seperate process, which handles audio only. i don't really like a sepeate process, since it requires some interface to openbsc and makes everything more complex. even though i don't like threads, multithreading seems to be the best solution to me at the moment. was there any effort to solve the problem or to handle audio? are there any suggestions about it? regard, andreas

2 2

SGSN Crash Report
by Caleb Pal 24 Jun '13

24 Jun '13

Hello, I just updated my machine with the latest OpenBSC code from git. In the past under heavy data load (EDGE), the BTS would crash. Now, after updating the code, the BTS stays up, but the SGSN crashes. Below are a few details about my setup and debugging output. BTS: NanoBTS 165BU 1900 PC: Atom Z530 1GB ram, Running Debian (Wheezy) Output from gdb: <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=52 <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0xc3123cCMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0xac6064CMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0xdc7cc7CMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0x18af79CMD=UI DATA <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0x84caf1CMD=UI DATA <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0xf1f6b6CMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0xd9e63bCMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0xbadc11CMD=UI DATA <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=64 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=197 <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0xb7e07cCMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0x987e00CMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0xf386aaCMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0x38700eCMD=UI DATA <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0x62743eCMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0x1cba00CMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0x6e4346CMD=UI DATA <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0xb20578CMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0x49f5d0CMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0x760e46CMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0xc839b5CMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0xacd5a3CMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0xdaf317CMD=UI DATA <0011> gprs_bssgp.c:747 BSSGP BVCI=3 Rx Flow Control BVC <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0x7d7a91CMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0x1eef1aCMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0xd83b65CMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0xf6a775CMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0x855a58CMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0x18aa6fCMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0x167b76CMD=UI DATA <0011> gprs_bssgp.c:376 BSSGP TLLI=0xce3dde6f Rx UPLINK-UNITDATA <0012> gprs_llc.c:502 LLC SAPI=3 C FCS=0x55d812CMD=UI DATA <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 <000f> sgsn_libgtp.c:425 GTP DATA IND from GGSN, length=1500 Program received signal SIGFPE, Arithmetic exception. fc_queue_timer_cfg (fc=fc@entry=0x808def0) at gprs_bssgp.c:596 596 msecs = (fcqe->llc_pdu_len * 1000) / fc->bucket_leak_rate; (gdb) OpenBSC Console Output: Fri Jun 21 16:36:19 2013 <0005> abis_nm.c:315 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) Failure Event Report Type=quality of service failure Severity=warning level failure Probable cause= 03 05 01 Additional Text=UDP overflow alarm on port 23000 (1 occurences) Fri Jun 21 16:36:20 2013 <0005> abis_nm.c:315 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) Failure Event Report Type=quality of service failure Severity=warning level failure Probable cause= 03 05 01 Additional Text=UDP overflow alarm on port 23000 (1 occurences) Fri Jun 21 16:38:00 2013 <0005> abis_nm.c:315 OC=GPRS-NSVC(f2) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Failed(01) Fri Jun 21 16:38:00 2013 <0005> abis_nm.c:315 OC=GPRS-NSE(f0) INST=(00,ff,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) Fri Jun 21 16:38:00 2013 <0005> abis_nm.c:1757 OC=GPRS-NSE(f0) INST=(00,ff,ff) Sending OPSTART Fri Jun 21 16:38:00 2013 <0005> abis_nm.c:315 OC=GPRS-CELL(f1) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) Fri Jun 21 16:38:00 2013 <0005> abis_nm.c:1757 OC=GPRS-CELL(f1) INST=(00,00,ff) Sending OPSTART Fri Jun 21 16:38:00 2013 <0005> abis_nm.c:315 OC=GPRS-NSE(f0) INST=(00,ff,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) Fri Jun 21 16:38:00 2013 <0005> abis_nm.c:315 OC=GPRS-CELL(f1) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) Fri Jun 21 16:38:00 2013 <0005> abis_nm.c:2418 OC=GPRS-NSE(f0) INST=(00,ff,ff) IPACCESS(0xf6): SET ATTR ACK Fri Jun 21 16:38:00 2013 <0005> abis_nm.c:2418 OC=GPRS-CELL(f1) INST=(00,00,ff) IPACCESS(0xf6): SET ATTR ACK Fri Jun 21 16:38:42 2013 <0005> abis_nm.c:315 OC=GPRS-NSVC(f2) INST=(00,00,ff) Failure Event Report Type=communication failure Severity=critical failure Probable cause= 03 03 11 Additional Text= Let me know if you need any further information. Regards, Caleb

4 4

NanoBTS 139 PCS1900 for sale
by Pierre Kim 23 Jun '13

23 Jun '13

Hello, I have a nanoBTS 139 unit for sale. It is from the united states, it operates on PCS1900. I'd sell it for 1200 euro. Please contact me if you are interested. Thank you.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC June 2013