- baseband-devel - lists.osmocom.org

Calypso BTS: my phone my phone doesn't see my base station

by phreaker1983

hi guys, my phone doesn't see my base station.. To start I used : 1. First terminal: ~/osmocombb/trx/src# sudo host/osmocon/osmocon -m c123xor -p /dev/ttyUSB0 -c target/firmware/board/compal_e88/trx.highram.bin -r 99 2. Second terminal: ~/osmocombb/trx/src/host/layer23/src/transceiver# sudo ./transceiver -a 40 -r 99 Then I showed <0012> l1ctl.c:383 Reset received: Starting sync. <0012> l1ctl.c:338 Sync acquired, setting BTS mode ... <0011> trx.c:194 TRX CLK Indication 1890062 <0011> trx.c:194 TRX CLK Indication 1890113 <0011> trx.c:194 TRX CLK Indication 1890164 <0011> trx.c:194 TRX CLK Indicatn 1890215 ........ 3. third terminal: osmo-nitb -c ~/.osmocom/open-bsc.cfg -l ~/.osmocom/hlr.sqlite3 -P -C —debug=DRLL:DCC:DMM:DRR:DRSL:DNM DB: Database initialized. DB: Database prepared. My open-bsc.cfg contains: ! OpenBSC configuration saved from vty ! ! password foo ! line vty no login ! e1_input e1_line 0 driver ipa network network country code 1 mobile network code 1 short name OpenBSC long name OpenBSC auth policy closed location updating reject cause 13 encryption a5 0 neci 1 rrlp mode none mm info 1 handover 0 handover window rxlev averaging 10 handover window rxqual averaging 1 handover window rxlev neighbor averaging 10 handover power budget interval 6 handover power budget hysteresis 3 handover maximum distance 9999 timer t3101 10 timer t3103 0 timer t3105 0 timer t3107 0 timer t3109 4 timer t3111 0 timer t3113 60 timer t3115 0 timer t3117 0 timer t3119 0 timer t3141 0 bts 0 type sysmobts band DCS1800 cell_identity 0 location_area_code 1 training_sequence_code 7 base_station_id_code 63 ms max power 15 cell reselection hysteresis 4 rxlev access min 0 channel allocator ascending rach tx integer 9 rach max transmission 7 ip.access unit_id 1801 0 oml ip.access stream_id 255 line 0 gprs mode none trx 0 rf_locked 0 arfcn 514 nominal power 23 max_power_red 20 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 timeslot 1 phys_chan_config SDCCH8 timeslot 2 phys_chan_config TCH/F timeslot 3 phys_chan_config TCH/F timeslot 4 phys_chan_config TCH/F timeslot 5 phys_chan_config TCH/F timeslot 6 phys_chan_config TCH/F timeslot 7 phys_chan_config TCH/F arfcn I chose the 514..... 4. fourth terminal: cd /osmocombb/osmo-bts/src/osmo-bts-trx osmo-bts-trx -c ~/.osmocom/osmo-bts.cfg showed me: ((*)) | / \ OsmoBTS <0017> control_if.c:693 CTRL at 127.0.0.1 4238 <0010> telnet_interface.c:95 telnet at 127.0.0.1 4241 <0012> input/ipaccess.c:881 enabling ipaccess BTS mode <0006> phy_link.c:58 PHY link state change shutdown -> connectiong <0006> scheduler.c:174 Init scheduler for trx=0 <000b> trx_if.c:584 Open transceiver for phy0.0 <0006> phy_link.c:58 PHY link state change connectiong -> connected <0006> phy_link.c:68 trx_set_avail(1) <0006> scheduler_trx.c:1514 GSM clock skew: old fn=0, new fn=1908169 <0006> scheduler_trx.c:1519 GSM clock jitter: -691 <0006> scheduler_trx.c:1519 GSM clock jitter: 128 <0006> scheduler_trx.c:1519 GSM clock jitter: 674 <0006> scheduler_trx.c:1519 GSM clock jitter: 204 <0006> scheduler_trx.c:1519 GSM clock jitter: 467 <0006> scheduler_trx.c:1519 GSM clock jitter: -1620 <0006> scheduler_trx.c:1519 GSM clock jitter: 1362 <0006> scheduler_trx.c:1519 GSM clock jitter: -668 <0006> scheduler_trx.c:1519 GSM clock jitter: -846 <0006> scheduler_trx.c:1519 GSM clock jitter: 519 <0006> scheduler_trx.c:1519 GSM clock jitter: 457 <0006> scheduler_trx.c:1519 GSM clock jitter: 384 <0006> scheduler_trx.c:1519 GSM clock jitter: 218 ..... My osmo-bts.cfg contains: !OsmoBTS (0.0.1.100-0455) configuration saved from vty !! ! phy 0 instance 0 bts 0 band DCS1800 ipa unit-id 1801 0 oml remote-ip 192.168.100.11 trx 0 phy 0 instance 0 Where I erred? Thank you. -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Calypso-BTS-my-phone-my-phone-do… Sent from the baseband-devel mailing list archive at Nabble.com.

7 years, 5 months

3
4
0 0

Re: Calypso BTS

by Holger Freyther

> On 12 Dec 2016, at 18:13, ak-74*** ... <87078838964(a)mail.ru> wrote: > > root@osmocombb-VirtualBox:~# osmo-nitb -c ~/.osmocom/open-bsc.cfg -l ~/.osmocom/hlr.sqlite3 -P -C —debug=DRLL:DCC:DMM:DRR:DRSL:DNM > > DB: Failed to init database. Please check the option settings. > if you look at the debian/control libdbd-sqlite3 needs to be installed to run osmo-nitb. Did you install that? holger

7 years, 5 months

1
0
0 0

Sniffing GPRS

by canarion

Hi, After compiling osmocom-bb and apply sylvain/burst_ind branch and gprs_multi.patch, I execute it and try to sniff gprs traffic. I loaded the layer1 into my C139 and I obtained an ARFCN code (883). When I run ccch_scan -a 883 I get the next result: opyright (C) 2010 Harald Welte <laforge(a)gnumonks.org> Contributions by Holger Hans Peter Freyther License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Failed to connect to '/tmp/osmocom_sap'. Failed during sap_open(), no SIM reader <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(1476410343) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(1207963561) <0001> app_ccch_scan.c:400 Paging1: Normal paging chan tch/f to TMSI M(0x1ad1cda) <0001> app_ccch_scan.c:403 Paging2: Normal paging chan tch/f to TMSI M(0x41ae98f9) <0001> app_ccch_scan.c:426 Paging3: Normal paging chan n/a to imsi M(214031385056117) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(3306441249) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to imsi M(214031482053520) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to imsi M(214036185306441) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(4207880193) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(4135931713) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(4214223105) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(3388536385) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(134915836) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(3961436929) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(4229756769) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(531909) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to imsi M(214034185316455) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(3829437761) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to imsi M(214033485554660) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(3639403521) <0001> app_ccch_scan.c:105 SI1 received. <0001> app_ccch_scan.c:464 unknown PCH/AGCH type 0x00 <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(3827744513) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(335734299) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(3561969409) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(4294310401) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(3698994241) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(3682615617) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(67866789) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(4003487553) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(3770351169) <0001> app_ccch_scan.c:400 Paging1: Normal paging chan tch/f to TMSI M(0x41ae98f9) <0001> app_ccch_scan.c:403 Paging2: Normal paging chan tch/f to TMSI M(0x1ad1cda) <0001> app_ccch_scan.c:426 Paging3: Normal paging chan n/a to imsi M(214031385056117) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(3306441249) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to imsi M(214031482053520) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to imsi M(214036185306441) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(4102036289) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(4135931713) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to imsi M(214032485273805) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(3798414145) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(134915836) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(3988859137) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(3735175681) <0001> app_ccch_scan.c:360 Paging1: Normal paging chan tch/f to tmsi M(531909) <0001> app_ccch_scan.c:248 GSM48 IMM ASS (ra=0x78, chan_nr=0x0f, HSN=24, MAIO=1, TS=7, SS=0, TSC=1) Dropping frame with 55 bit errors <000c> l1ctl.c:238 Dropping frame with 55 bit errors <000c> l1ctl.c:290 BURST IND: @(830928 = 0626/20/36) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830928 = 0626/20/36) (-110 dBm, SNR 8) <000c> l1ctl.c:290 BURST IND: @(830929 = 0626/21/37) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830929 = 0626/21/37) ( -83 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830930 = 0626/22/38) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830930 = 0626/22/38) ( -87 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830931 = 0626/23/39) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830931 = 0626/23/39) ( -83 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830932 = 0626/24/40) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830932 = 0626/24/40) ( -88 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830933 = 0626/25/41) (-105 dBm, SNR 8, UL, SACCH) <000c> l1ctl.c:290 BURST IND: @(830933 = 0626/25/41) (-107 dBm, SNR 5, SACCH) <000c> l1ctl.c:290 BURST IND: @(830934 = 0626/00/42) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830934 = 0626/00/42) ( -88 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830935 = 0626/01/43) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830935 = 0626/01/43) ( -83 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830936 = 0626/02/44) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830936 = 0626/02/44) ( -88 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830937 = 0626/03/45) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830937 = 0626/03/45) ( -89 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830938 = 0626/04/46) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830938 = 0626/04/46) ( -88 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830939 = 0626/05/47) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830939 = 0626/05/47) ( -82 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830940 = 0626/06/48) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830940 = 0626/06/48) ( -87 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830941 = 0626/07/49) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830941 = 0626/07/49) ( -87 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830942 = 0626/08/50) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830942 = 0626/08/50) ( -86 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830943 = 0626/09/00) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830943 = 0626/09/00) ( -86 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830944 = 0626/10/01) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830944 = 0626/10/01) ( -87 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830945 = 0626/11/02) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830945 = 0626/11/02) ( -87 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830947 = 0626/13/04) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830947 = 0626/13/04) ( -84 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830948 = 0626/14/05) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830948 = 0626/14/05) ( -85 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830949 = 0626/15/06) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830949 = 0626/15/06) ( -88 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830950 = 0626/16/07) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830950 = 0626/16/07) ( -89 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830951 = 0626/17/08) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830951 = 0626/17/08) ( -88 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830952 = 0626/18/09) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830952 = 0626/18/09) ( -85 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830953 = 0626/19/10) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830953 = 0626/19/10) ( -87 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830954 = 0626/20/11) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830954 = 0626/20/11) ( -87 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830955 = 0626/21/12) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830955 = 0626/21/12) (-106 dBm, SNR 0) <000c> l1ctl.c:290 BURST IND: @(830956 = 0626/22/13) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830956 = 0626/22/13) (-107 dBm, SNR 5) <000c> l1ctl.c:290 BURST IND: @(830957 = 0626/23/14) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830957 = 0626/23/14) (-106 dBm, SNR 2) <000c> l1ctl.c:290 BURST IND: @(830958 = 0626/24/15) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830958 = 0626/24/15) (-108 dBm, SNR 1) <000c> l1ctl.c:290 BURST IND: @(830959 = 0626/25/16) (-106 dBm, SNR 2, UL, SACCH) <000c> l1ctl.c:290 BURST IND: @(830959 = 0626/25/16) (-109 dBm, SNR 5, SACCH) <000c> l1ctl.c:290 BURST IND: @(830960 = 0626/00/17) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830960 = 0626/00/17) (-108 dBm, SNR 3) <000c> l1ctl.c:290 BURST IND: @(830961 = 0626/01/18) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830961 = 0626/01/18) (-106 dBm, SNR 2) <000c> l1ctl.c:290 BURST IND: @(830962 = 0626/02/19) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830962 = 0626/02/19) (-108 dBm, SNR 3) <000c> l1ctl.c:290 BURST IND: @(830963 = 0626/03/20) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830963 = 0626/03/20) (-107 dBm, SNR 0) <000c> l1ctl.c:290 BURST IND: @(830964 = 0626/04/21) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830964 = 0626/04/21) ( -85 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830965 = 0626/05/22) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830965 = 0626/05/22) ( -87 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830966 = 0626/06/23) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830966 = 0626/06/23) ( -85 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830967 = 0626/07/24) ( -47 dBm, SNR 255, UL) <000c> l1ctl.c:290 BURST IND: @(830967 = 0626/07/24) ( -86 dBm, SNR 255) <000c> l1ctl.c:290 BURST IND: @(830968 = 0626/08/25) (-107 dBm, SNR 6, UL) <000c> l1ctl.c:290 BURST IND: @(830968 = 0626/08/25) (-109 dBm, SNR 0) <000c> l1ctl.c:290 BURST IND: @(830969 = 0626/09/26) (-101 dBm, SNR 6, UL) But it stop to capture frames, seems to be left in a standby state and I don't know why that is. With gprsdecode I can see the next image in the wireshark: http://baseband-devel.722152.n3.nabble.com/file/n3712433/wireshark-capture.… If someone knows what is the problem, please tell me. Thanks in advance. Cheers, Dani -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Sniffing-GPRS-tp3712433p3712433.… Sent from the baseband-devel mailing list archive at Nabble.com.

7 years, 5 months

8
12
0 0

OpenBTS the phone does not see

by phreaker1983

Hi, I installed OpenBTS 5.0 for tutorials:https://www.youtube.com/watch?v=Ja7oSyyx7zw, everything went without error , after starting the phone doesn't see my base station, what could be the problem? -- View this message in context: http://baseband-devel.722152.n3.nabble.com/OpenBTS-the-phone-does-not-see-t… Sent from the baseband-devel mailing list archive at Nabble.com.

7 years, 5 months

2
1
0 0

USRP Free BULK SMS SMS device

by superben

https://youtu.be/YJ_qkJEFNcg UGS is a portable system designed to send SMS messages and data to GSM phones in a pre-defined area. Unlike existed advertisement systems UGS sends normal or flash SMS instead of broadcast messages (receipt of broadcast messages can be disabled by mobile phone user); UGS is an independent stand-alone system, which does not require any cooperation with cellular operators. UGS does not use phone numbers of mobile phones, hence there is no need in the lists of phone numbers to be obtained from various sources. Those lists are often not complete, outdated, irrelevant and costly. The UGS can be used for commercial or security purposes: Send commercial advertisements, announcements, free gift coupons, useful information or welcome messages in specific places: shopping areas, banks, restaurants, train or bus stations, exhibitions, shows, etc. Send warning messages or requests to the people in the case of emergency. Send messages with the request to contact police to potential crime witnesses in the crime areas. SMS messages can be sent: To New in the Area or To Known in the Area or To pre-defined groups or To everyone, The UGS can be installed in a fixed location or carried to the places of need in a small, hand carry suitcase. Potential users of the system are small stores, large organizations, advertisement providers, rescue services, police forces and others. System can be operated locally or remotely via the Internet. SMS sent by the system are free of charge; neither owner of the system nor mobile phone users pay for them. The system is comprised of compact Base Station Unit and notebook computer. Because of unique sophisticated algorithm implemented in the system, the UGS transmits very low power and does not interfere with existed GSM networks. User can define any phone number or name of the sender, which will appear on the screens of mobile phones. Main specifications: Frequency coverage: 850, 900, 1800, 1900 MHz Number of SMS: No limitations Number of handsets: No limitations System output: From 10mW up to 10w (adjustable) Power: 220V / 110V / 24V / 12-16V or Batteries Operation Range: 10...1500 m SMS language: All languages -- View this message in context: http://baseband-devel.722152.n3.nabble.com/USRP-Free-BULK-SMS-SMS-device-tp… Sent from the baseband-devel mailing list archive at Nabble.com.

7 years, 5 months

2
1
0 0

RFC: OsmoDevCon 2017 planning

by Harald Welte

Dear Osmocom Community, [please respect the Reply-To and post all follow-up discussion to this to openbsc(a)lists.osmocom.org, so we avoid having long threads cross-posted to several mailing lists.] >From 2012 to 2016 we were running a series of small, invitation-only Osmocom Developer Conferences. Access was intentionally restricted to those community members who have demonstrated an existing track record of contribution to any of the projects under the Osmocom umbrella. This format of a small, tightly knit group of about 20 people has been successful over the years, and I have received a lot of positive feedback from past participants. On the other hand, the Osmocom project has grown in scope and diversity, and some of those projects don't have all that much relationship to each other - except being started by people from within the same group. There's the cellular communications (GSM/GPRS/EDGE/UMTS and hopefully at some point LTE) protocols which is attracting a lot of professional users. And then there's pure community projects like rtl-sdr, OsmocomBB, OsmocomGMR and many other efforts. Particularly the cellular infrastructure projects (OsmoBTS, OsmoPCU, OsmoBTS, OsmoNITB, OsmoSGSN, OpenGGSN, OsmoIuh & co) are somehow "standing out" of the othe projects in the context of having a wider user bsae, and in that user base also primarily commercial users. So I'd like to start a discussion on how to possibly change the event format to accomodate the various interests and parties. I definitely don't want to loose the "annual meeting of old friends" atmosphere, while at the same time also opening up to other interested parties. One idea would be to keep OsmoDevCon as-is and have a separate event where non-contributing/developing users / sysadmins / system integrators could also be attending. Another idea would be to split into a 'user day' and 'developer days' format. This is something the netfilter developer workshops have been using for many years, and from my limited insight quite successfully so. The "user day" is more like a traditional tech conference, with a large auditorium and talks oriented towards users / sysadmins / integrators of the software. The "developer days" are the invitation-only part, for known contributing developers only, similar to what we have at OsmoDevCon. Having both events (or both parts of an event) back-to-back has the advantage that a large number of potential speakers for the 'user day' are already present, and they don't have to travel yet another time. One could even structure it further and say we have one user day, one public 'Osmocom cellular developer day' and then the closed 'OsmoDevCon classic', maybe reduced from 4 days to 3 or even 2 days only? What is the general opinion about this? Are there people lurking on this list who would be interested in attending a public 'user day' or even 'developer day' about the Osmocom cellular projects, with presentations and workshops around topics such as running Osmocom based cellular networks? In terms of when/where, I would suggest to keep the tradition of April in Berlin/Germany. But I'm of course very happy if somebody wants to host it some place else... Regards, and looking forward to meeting you [again] in 2017, 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)

7 years, 5 months

1
0
0 0

"Type not handled! 40" gprsdecode

by George Andguladze

Hey there, I bumped into this error when testing gprsdecode from srldabs.de When I try the sample .dat files provided from srlabs.de it works fine though. Any hints? Kind Regards George AndguladzeSenior Software EngineerBusiness Management Technology www.bmt.ge

7 years, 5 months

2
1
0 0

Re: omsocombb not receiving calls

by robert

Hi, I didn’t find anything useful yet. Everything seems normal during the IMSI attach procedure (location updating request, authentication request/response, identity request/response …), I can call and send SMS normally but the phone doesn’t get paged in any way. It seems strange that no differences can be seen during the IMSI attach procedure while some sim cards do not work. On Mar 4, 2016, at 7:13 PM, Dennis Eisenbarth <dennis.eisenbarth(a)gmail.com> wrote: > GSM specs, it is. > > On 04.03.2016 17:32, robert wrote: >> >> I read about sim card types since it must be a sim card problem but I didn’t find anything useful. >> >> >> On Mar 4, 2016, at 6:05 PM, Dennis Eisenbarth <dennis.eisenbarth(a)gmail.com> wrote: >> >>> A good start would be a look into the specifications. >>> >>> >>> On 04.03.2016 14:31, robert wrote: >>>> >>>> Hi, >>>> >>>> I tried two sim cards one that works fine and another one that doesn’t get paged, I noticed that during the location update procedure everything is exactly the same (using wireshark). The log files are also similar. Although both cards work fine if used in a normal phone (even with a motorola c123/118 …). >>>> >>>> Another thing to mention is that some sim cards only work when i stick them on a BTS that has the "SI type 3, GPRS indicator" as follows: >>>> "3G Early Classmark Sending Restriction: Neither UTRAN, CDMA2000 nor GERAN IU MODE CLASSMARK CHANGE message shall be sent with the Early classmark sending" >>>> while they can only make calls without being able to receive anything on other BTS where the "SI type 3, GPRS indicator" is as follows: >>>> "3G Early Classmark Sending Restriction: The sending of UTRAN,CDMA2000 and GERAN IU MODE CLASSMARK CHANGE messages are controlled by the Early Classmark Sending Control parameter" >>>> I would be very grateful if anyone has some explanations to what is going on. >>>> >>>> >>>> >>>> Best regards, >>>> Robert, >>>> >>>> >>>> On Jan 26, 2016, at 6:30 PM, Tomcsányi Domonkos <domi(a)tomcsanyi.net> wrote: >>>> >>>>> Hi Robert, >>>>> >>>>> I think it would help us out a lot if you could provide at least one complete log file from the output of the mobile app, so we can start having some ideas. >>>>> >>>>> >>>>> Cheers, >>>>> Domi >>>>> >>>>> >>>>>> 2016. jan. 26. dátummal, 17:24 időpontban robert steve <robert.steve07(a)gmail.com> írta: >>>>>> >>>>>> Hi, >>>>>> I would first like to thank all those who participated in this nice project. >>>>>> I recently started working with osmocombb and was able to have it working fine on a motorola c118. >>>>>> However, I noticed that some sim cards can connect normally to the BTS, can make calls and send SMS but can’t receive anything. They simply don't get paged. While for some other sim cards everything seems to be working fine. >>>>>> >>>>>> Does anyone know what might be causing this issue ? >>>>>> >>>>>> thanks, >>>>>> Robert >>>>> >>>> >>> >> >

7 years, 6 months

4
22
0 0

Solution to the shortage of Calypso devices

by Mychaela Falconia

Hello baseband hacking folks, I have heard several people complain that they are no longer able to find/obtain a Motorola C1xx phone or any other Calypso device for playing with OsmocomBB. I assume these complaints probably come from people in the EU and other 900/1800 MHz regions, as US band C139 phones are still readily available on ebay (63 listings as of right now, all dirt cheap), but either way, I have what I believe to be the proper solution to the shortage and the crippled nature of all pre-existing Calypso devices: a new Calypso board. Back in 2012 Harald Welte posted here saying that his company was going to be making a new Calypso board for the very same purpose of addressing the shortage and the deficiencies of pre-existing devices, but as far as I know, no such product has ever been produced - nor do I know if whoever was behind that project even got as far as creating the design for it. Fast-forwarding to the present, we now have a ready-to-build design for a Calypso development board called FCDEV3B, which stands for FreeCalypso development board, triband. It is based on a reuse of the known-working Calypso modem design from Openmoko, reuse at the level of physical PCB layout, based on the GTA02 design files which Openmoko founder Mr. Sean Moss-Pultz released in April of 2015 at my urging. Back in 2012 Harald was saying that he was only going to release PDF schematics but not the full design files for his board; I feel differently about such matters, hence the complete design files for *my* board are free to the world: ftp://ftp.freecalypso.org/pub/GSM/FreeCalypso/fcdev3b/ Now we need to get these boards physically made, and toward that end I have started a crowdfunding campaign: https://www.gofundme.com/fcdev3b-board-production-2umevjw In the interest of transparency, I have to disclose (most people know it already, but I have to state it anyway) that I do not use OsmocomBB and will never contribute to Osmocom software because I am working on my own personally preferred alternative GSM MS firmware implementation, but when it comes to the hardware I seek to build and offer to the community, there is no reason why it won't work with OsmocomBB - it should work just fine. Because my board is a derivative of Openmoko's modem design and the part that is different between Openmoko's board and mine (the flash chip - I will populate a higher-capacity chip on the same footprint) is not used by OsmocomBB software, the images currently built in board/gta0x/*.highram.bin should work as-is on my FCDEV3B without needing any code changes. Hasta la Victoria, Siempre, M~

7 years, 7 months

2
2
0 0

[PATCH] adjust Makefile.mtk so that mtk-firmware works again

by Craig Comstock

--- src/target/firmware/Makefile.mtk | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/src/target/firmware/Makefile.mtk b/src/target/firmware/Makefile.mtk index 30fa2fc..927e31a 100644 --- a/src/target/firmware/Makefile.mtk +++ b/src/target/firmware/Makefile.mtk @@ -4,14 +4,16 @@ BOARDS?=mt62xx # List of all applications (meant to be overridden on command line) APPLICATIONS?=loader_mtk -mtkram_LDS=board/mediatek/ram.lds -mtkram_OBJS=board/mediatek/start.ram.o +APP_loader_mtk_ENVIRONMENTS=mtkram + +ENV_mtkram_LDS=board/mediatek/ram.lds +ENV_mtkram_OBJS=board/mediatek/start.ram.o mtk_COMMON_OBJS=board/mediatek/uart.o # Mediatek MT62xx -mt62xx_OBJS=$(mtk_COMMON_OBJS) board/mt62xx/init.o -mt62xx_ENVIRONMENTS=mtkram +BOARD_mt62xx_OBJS=$(mtk_COMMON_OBJS) board/mt62xx/init.o +BOARD_mt62xx_ENVIRONMENTS=mtkram # Global include path INCLUDES=-Iinclude/ -I../../../include -I../../shared/libosmocore/include -- 2.1.4

7 years, 7 months

1
0
0 0

Re: nuttx-bb layout? inside or outside nuttx?

by Craig Comstock

Yes, my plan was: - get osmocom-bb (layer1/rssi) firmware working (without graphics probably) - use that work side-by-side to integrate into fernvale nuttx - create a layer1 "app" in nuttx - port "mobile" app to nuttx With the goal being that you can call/text from the nuttx shell. I have the following hardware with which to experiment: - c139 motorola phones - pirelli phone - a few other calypso phones - seeedstudio rephone (mtk6261) - sim800 of various types - several watch phones (dz09 gt08 v9, both 6260 and 6261) - raw 6260 chips which I hope to design a custom pcb for My end goal which is far too ambitious is to make a rock-like device which has no ports/holes: - bluetooth serial to nuttx shell - qi wireless charging - accelerometer gestures for basic controls - bone conducting speaker - speech synth (sam/espeak) and voice recognition (pocketsphinx) - all source is included on-device, even to the point that I would like to port all this work to a forth-like language of my own invention so you can debug, learn and experiment on the device I have so far fixed up the existing mtk-firmware target and was debating whether to submit that small patch or wait until I get some 626x work done. On that front I have the basic registers and an initial BSI power on routine written (but not tested). Thanks to all the giants upon whose shoulders I stand to do this work, Craig -------------------------------------------- On Thu, 10/13/16, Harald Welte <laforge(a)gnumonks.org> wrote: Subject: Re: nuttx-bb layout? inside or outside nuttx? To: "Craig Comstock" <craig_comstock(a)yahoo.com> Cc: "Marcin Mielczarczyk" <marcin.mielczarczyk(a)gmail.com>, "baseband-devel" <baseband-devel(a)lists.osmocom.org> Date: Thursday, October 13, 2016, 2:09 AM Hi Craig, this is just a small note that I just met Marcin Mielczarczyk (who did the existing but still incomplete MTK support work a few years back) at Embedded Linux Conf Europe, and informed him about your work. It is really exciting for both of us to see somebody picking this up and trying to bring things together. If I'm not mistaken, you basically have the following agenda: * Structure OsmocomBB in a way that it can be built 'side-by-side into Nuttx * Build /integrate it from the fernvale nuttx port that is available * Implement the bulk of the MTK L1 integration, i.e. the interface to the DSP. And afterwards hope that you have something that supports either the Fernvale, SIM800H, Linkit One, or other MTK 2G baseband chips out there. Please let me know this was an accurate understanding. 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)

7 years, 7 months

1
0
0 0

osmocom+c118+openbts send sms

by superben

osmocom+c118+openbts send sms : youtube: https://youtu.be/r_U7DKFYuqo blog: http://gsmsuperben.blogspot.my/2016/07/osmocomc118openbts-send-sms.html First you need to successfully install osmocom： http://gsmsuperben.blogspot.my/2016/07/osmocombbc118-gsm-sniffer.html Assuming you have installed the gnu-arm-build.3.sh 1：Download and compile osmocomBB and libosmo-dsp $ git clone git://git.osmocom.org/libosmocore.git $ git clone git://git.osmocom.org/libosmo-dsp.git $ git clone git://git.osmocom.org/osmocom-bb.git $ sudo apt-get install libfftw3-dev libfftw3-doc When installing libosmocore execute ./configure many people will encounter No package 'talloc' found such a mistake , because they can not talloc, Here is the solution $ wget https://www.samba.org/ftp/talloc/talloc-2.1.7.tar.gz $ tar -zxvf talloc-2.1.7.tar.gz $ cd talloc-2.1.7/ $ ./configure $ make $ sudo make install install libosmocore $ cd libosmocore/ $ autoreconf -i $ ./configure $ make $ sudo make install $ cd .. install libosmo-dsp $ cd libosmo-dsp/ $ autoreconf -i $ ./configure $ make $ sudo make install Compile osmocombb $ cd osmocom-bb $ git checkout sylvain/testing $ cd src $ make HOST_layer23_CONFARGS=--enable-transceiver 2:Download openbts and install dependencies（The best use of root privileges） $ su $ apt-get install subversion $ svn co http://wush.net/svn/range/software/public $ sudo apt-get install autoconf libtool libosip2-dev libortp-dev libusb-1.0-0-dev g++ sqlite3 libsqlite3-dev erlang libreadline6-dev libncurses5-dev 3:install openbts $ cd pubilc $ cd a53/trunk $ make install $ cd openbts/trunk $ autoreconf -i $ ./configure $ make $ cd apps $ ln -s ../TransceiverRAD1/transceiver . $ cd .. $ sudo mkdir /etc/OpenBTS $ sudo sqlite3 -init ./apps/OpenBTS.example.sql /etc/OpenBTS/OpenBTS.db ".quit" $ sqlite3 /etc/OpenBTS/OpenBTS.db .dump $ sudo mkdir -p /var/lib/asterisk/sqlite3dir 4:install sipauthserve in pubilc $ cd subscriberRegistry/trunk $ make $ sudo sqlite3 -init subscriberRegistry.example.sql /etc/OpenBTS/sipauthserve.db ".quit" 5:install smqueue in public $ cd smqueue/trunk $ autoreconf -i $ ./configure $ make $ sudo sqlite3 -init smqueue/smqueue.example.sql /etc/OpenBTS/smqueue.db ".quit" 6:open all osmocom: $ osmocom-bb/src/host/osmocon/osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/trx.compalram.bin transceiver: $ osmocom-bb/src/host/layer23/src/transceiver/transceiver ARFCN smqueue: $ public/smqueue/trunk/smqueue/smqueue sipauthserve: $ public/subscriberRegistry/trunk/sipauthserve OpenBTS: $ public/openbts/trunk/apps/OpenBTS $ public/openbts/trunk/apps/OpenBTSCLI 7:Configuration openbts OpenBTSCLI $ config $ config Control.LUR.OpenRegistration .* $ config GSM.Radio.Band 900 $ config GSM.Radio.C0 YOU transceiver ARFCN $ config GSM.Identity.MCC 001 $ config GSM.Identity.MNC 01 （001 01 test） Configuration is complete, reboot your openbts 8:Mobile search and access OpenBTS 9:View tmsis OpenBTSCLI $ tmsis 10:try send sms OpenBTSCLI $ sendsms YOUTMSIS number messege -- View this message in context: http://baseband-devel.722152.n3.nabble.com/osmocom-c118-openbts-send-sms-tp… Sent from the baseband-devel mailing list archive at Nabble.com.

7 years, 8 months

1
0
0 0

smocombb+c118 gsm-sniffer

by superben

osmocombb+c118 gsm-sniffer： youtube: https://youtu.be/ZDToZIYHmJM blog: http://gsmsuperben.blogspot.my/2016/07/osmocombbc118-gsm-sniffer.html System ： ubuntu12.04-i386（or kali）一：update system update（or vi /etc/apt/sources.list ） settings Inside find software update source download from modifying their own country Then save the exit now open terminal $ sudo apt-get update $ sudo apt-get upgrade 二：Then install a series of dependency $ sudo apt-get install libusb-0.1-4 libpcsclite1 libccid pcscd $ sudo apt-get install libtool shtool autoconf git-core pkg-config make gcc build-essential libgmp3-dev libmpfr-dev libx11-6 libx11-dev texinfo flex bison libncurses5 libncurses5-dbg libncurses5-dev libncursesw5 libncursesw5-dbg libncursesw5-dev zlibc zlib1g-dev libmpfr4 libmpc-dev libpcsclite-dev （copy）三：Create several directories , download ARM compiler $ mkdir osmocombb $ cd osmocombb $ mkdir build install src $ cd src $ wget ftp://sources.redhat.com/pub/newlib/newlib-1.19.0.tar.gz 四：install gnu-arm-build.3.sh $ cd .. $ chmod +x gnu-arm-build.3.sh $ ./gnu-arm-build.3.sh See here you can directly enter 五：After you install the add environment $ cd install/bin $ pwd $ vi ~/./. bashrc export PATH=$PATH:/osmocombb/ install/bin $ source ~/.bashrc 六：Download and compile osmocomBB back osmocombb download osmocom $ git clone git://git.osmocom.org/libosmocore.git $ git clone git://git.osmocom.org/osmocom-bb.git When installing libosmocore execute ./configure many people will encounter No package 'talloc' found such a mistake , because they can not talloc, Here is the solution $ wget https://www.samba.org/ftp/talloc/talloc-2.1.7.tar.gz $ tar -zxvf talloc-2.1.7.tar.gz $ cd talloc-2.1.7/ $ ./configure $ make $ sudo make install install libosmocore $ cd libosmocore/ $ autoreconf -i $ ./configure $ make $ sudo make install $ cd .. Compile osmocombb $ cd osmocom-bb $ git checkout --track origin/luca/gsmmap $ cd src $ make 七：Modify the problem file ( if you are gnu-arm-build.2.sh and no cell scanning immobile problem , skip this step ) Enter osmocom-bb find these files and modify them vi osmocom-bb/ src/target/firmware/board/compal/highram.lds vi osmocom-bb/ src/target/firmware/board/compal/ram.lds vi osmocom-bb/ src/target/firmware/board/compal_e88/flash.lds vi osmocom-bb/ src/target/firmware/board/compal_e88/loader.lds vi osmocom-bb/ src/target/firmware/board/mediatek/ram.lds Found inside this string of code KEEP(*(SORT(.ctors))) In the following is added KEEP(*(SORT(.init_array))) Listed as： To save , all changes well in entering osmocom-bb / src recompile $ make -e CROSS_TOOL_PREFIX=arm-none-eabi- 八：Insert your brush into the firmware 118 in osmocom-bb directory $ cd src/host/osmocon $ sudo ./osmocon -m c123xor -p /dev/ttyUSB0 ../../target/firmware/board/compal_e88/layer1.compalram.bin Enter appear so wait when you click c118 power button , click on it If this is the brush into failure , look at your c118 cable, if you are buying a new phone line proposed to insert a little tight . . Best to shell removed 九：Scanning station information Open a new terminal or in osmocom-bb directory $ cd src/host/layer23/src/misc $ sudo ./cell_log -O Then enter $ sudo ./ccch_scan -i 127.0.0.1 -a ARFCN ARFCN is circled out above that value , such as column $ sudo ./ccch_scan -i 127.0.0.1 -a 59 十：install wireshark Open a new terminal $ sudo apt-get install wireshark $ sudo wireshark -k -i lo -f 'port 4729' In the filter input gsm_sms Then quietly wait for it。。。 -- View this message in context: http://baseband-devel.722152.n3.nabble.com/smocombb-c118-gsm-sniffer-tp4026… Sent from the baseband-devel mailing list archive at Nabble.com.

7 years, 8 months

1
0
0 0

layer 1 port to nuttx-bb progress?

by Craig Comstock

I have fernvale-nuttx running on a couple of MTK6260-based watch phones and plan on working on porting layer1 to these devices. https://www.kosagi.com/forums/viewtopic.php?id=407 I saw the most recent activity on nuttx-bb seems to be http://cgit.osmocom.org/nuttx-bb/log/?h=gnutoo/layer1-2015-wip wondering if anyone else is working on this elsewhere that we can coordinate? If there are any particular suggestions/hints/warnings please chime in so I make better progress and have less trouble when I submit pull requests and such. Cheers,Craig

7 years, 9 months

2
1
0 0

OsmocomBB - C155 - stuck at flashing firmware

by Gerard Pinto

Greetings, I have been working with OsmocomBB with C155 model. After a lot of reading and understanding issues on mailing list, following the right instructions I am unable to understand where the problem is - cable or the locked tracfone C155 or my setup. I was successfully able to build the project. I am stuck on executing the following command ~/osmocom-bb/src/host/osmocon# ./osmocon -p /dev/ttyUSB0 -m c155 ../../target/firmware/board/compal_e99/layer1.compalram.bin <No output at all> <Even on slight push on power button no output> Please find my specifications and findings below: 1. C155 locked tracfone. 2. FTDI adapter USB serial from - Fonefunshop Is there a way to test the FTDI adapter ? dmesg - list that FTDI adapter attached to ttyUSB0. FTDI VCP driver is built into the Linux kernel. Do I need D2XX driver ? 3. I'm trying to write the firmware (layer1) with a working GSM sim inside and not tracfone sim card. 4. strace gives me no trouble other than this access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) - Is it a worry ? 5. When I execute ./osmocon with all necessary params. I open a new console and type the following ./osmoload memdump 0x000000 0x2000 dump. - Is this valid at this point? just to see where the actual firmware is located at? Dumping 12288 bytes of memory at 0x0 to file dump - Nothing gets dumped into file dump Although, I see some output - 'got 2 bytes from modem... ' in the osmocon window - ./osmocon It would be very kind if someone could guide me. How do I verify there is a cable issue <Any software to test TX> since I have bought these and if not the cable them am I doing something wrong ? Looking forward to the reply! Thanks, Gerard. -- View this message in context: http://baseband-devel.722152.n3.nabble.com/OsmocomBB-C155-stuck-at-flashing… Sent from the baseband-devel mailing list archive at Nabble.com.

7 years, 9 months

2
1
0 0

Re: osmocombb paging group problem

by Vadim Yanitskiy

Hi, My advice you is to stop waiting for someone, who will help you. Just try to dig into the source code yourself, it's interesting! And in case of any successes, patches are welcome. With best regards, Vadim Yanitskiy.

7 years, 9 months

2
1
0 0

layer2/3 ported to target? paging attack code?

by Craig Comstock

Hey, I finally watched Nico's talk "let me answer that for you" and heard him say he ported layer2/3 to target. Also found a mailing list message about him cleaning it up and putting it up on git and sending it to a few folks. Did that code ever get shared? Would be cool to play around with and is certainly something I would eventually want to accomplish for my project of making a phone that works by itself. -Craig

7 years, 9 months

8
15
0 0

osmocombb paging group problem

by sami

Dear all, I have been testing the mobile app for some time but I faced a small problem where not all my sim cards work fine when listening to paging messages. I have seen the patch presented by Harald Welte and I printed the value of ‘tn’ and found out that it is always 0 whatever the IMSI of the sim card is. Did I miss something or is the paging group part still not implemented in the mobile app. I really appreciate any help.

7 years, 9 months

1
1
0 0

Re: rx sensitivity issue

by Vadim Yanitskiy

Hi Robert, There are many possible issues, which can cause your problem. So, it would be good to see more details. Please, prepare two measurements using cell_log application: one inside any building, and another one outside. Attach both outputs from the cell_log and from the osmocon. I have several phones, and some of them have different RX signal level. I think, it's due to individual calibration tables, which aren't used in OsmocomBB firmware. BTW: if your phone's case is open, make sure that antenna is connected to the phone's board. With best regards, Vadim Yanitskiy.

7 years, 9 months

2
1
0 0

rx sensitivity issue

by robert

Hi, when using the mobile app I cannot connect to the BTS unless I get my phone outside any building, although when using the original firmware I can connect from inside my room. Is there a way to increase the sensitivity of the phone ?

7 years, 9 months

1
0
0 0

[PATCH] Makefile: add forgotten gsmmap to (dist)clean section

by Vadim Yanitskiy

--- src/Makefile | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/Makefile b/src/Makefile index 8075082..2d43f9c 100644 --- a/src/Makefile +++ b/src/Makefile @@ -99,6 +99,7 @@ clean: make -C host/layer23 $@ make -C host/osmocon $@ make -C host/trxcon $@ + make -C host/gsmmap $@ make -C target/firmware $@ make -C target/firmware -f Makefile.mtk $@ @@ -107,5 +108,6 @@ distclean: make -C host/layer23 $@ make -C host/osmocon $@ make -C host/trxcon $@ + make -C host/gsmmap $@ # 'firmware' also handles 'mtk-firmware' make -C target/firmware $@ -- 2.9.0

7 years, 10 months

1
1
0 0

OsmocomBB hardware migration to SDR

by Вадим Яницкий

Hi lists! It's no secret for everyone, that today OsmocomBB is not actively maintained as well as OpenBSC, for example. I think it's mostly due to supported hardware limitations. Currently supported platforms is still a bit of 'black box'. Moreover every day it's harder to find and buy a new one. Fortunately, there are many SDR platforms available now. Especially interesting devices are USRP, UmTRX, bladeRF, and recently introduced LimeSDR. They can be easily programmed to support just about any type of wireless standard, of course, including some mobile telecommunication stacks. As well as for network side back-end, they can be used to perform MS side operations, excepting frequency-hopping and some phone specific features (like SIM I/O). So, I think there is a way to bring a new live to, amazing child of the Osmocom umbrella, OsmocomBB. We can make one work on SDR hardware platforms implementing a 'bridge' between both already implemented L2/L3 and OsmoTRX. I know that there already was some attempts (see sylvain/ms-sdr branch) to make described dreams come true, but development was stopped. And now I am going to start to work around this direction. What for? - GPRS and EDGE support - More flexible voice routing - Multi SIM support - Next generation networks support (UMTS, LTE) - ... Currently I am looking for developers interested in this subject. So, any ideas and contributions are welcome! Together we can realize all the things faster and create a new area of research and development. Also for me it's very important to know opinions of Osmocom community members and exactly OsmocomBB founders/developers. Thanks! С наилучшими пожеланиями, Яницкий Вадим.

7 years, 10 months

5
15
0 0

Issue with c139

by Ajay Fuloria

Hi all, I have been using C123 for a long time with FTDI cable. I recently bought a C139 on which I wanted to run layer1 fw, i check the SW version using #02# and software version is "1.3.29", UART Flag is "0" On going through the mailing list I found these to be sufficient for using osmocom-bb but some how there is a problem on loading. When I use the fwg command ./osmocon -p /dev/ttyUSB0 -m c140 -c ../../target/firmware/board/compal_e86/layer1.highram.bin I get the following got 2 bytes from modem, data looks like: 04 81 .. got 5 bytes from modem, data looks like: 1b f6 02 00 41 ....A got 1 bytes from modem, data looks like: 01 . got 1 bytes from modem, data looks like: 40 @ Received PROMPT1 from phone, responding with CMD read_file(chainloader): file_size=32, hdr_len=4, dnload_len=15341 got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: f6 . got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 41 A got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 43 C Received PROMPT2 from phone, starting download handle_write(): 4096 bytes (4096/15341) handle_write(): 4096 bytes (8192/15341) handle_write(): 4096 bytes (12288/15341) handle_write(): 3053 bytes (15341/15341) handle_write(): finished It receives prompt2 and loads the file but doesn't move ahead, the phone does not show layer1 on the screen either. when i use fwg command (add -m c140xor ) ./osmocon -p /dev/ttyUSB0 -m c140xor -c ../../target/firmware/board/compal_e86/layer1.highram.bin I get the fwg: got 1 bytes from modem, data looks like: 04 . got 1 bytes from modem, data looks like: 81 . got 5 bytes from modem, data looks like: 1b f6 02 00 41 ....A got 1 bytes from modem, data looks like: 01 . got 1 bytes from modem, data looks like: 40 @ Received PROMPT1 from phone, responding with CMD read_file(chainloader): file_size=32, hdr_len=4, dnload_len=15341 got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: f6 . got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 41 A got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 43 C Received PROMPT2 from phone, starting download handle_write(): 4096 bytes (4096/15341) handle_write(): 4096 bytes (8192/15341) handle_write(): 4096 bytes (12288/15341) handle_write(): 3053 bytes (15341/15341) handle_write(): finished got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: f6 . got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 41 A got 1 bytes from modem, data looks like: 03 . got 1 bytes from modem, data looks like: 57 W Received MAGIC NACK from phone, you need to have "1003" at 0x803ce0 got 1 bytes from modem, data looks like: 66 f got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6d m got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6c l Received FTMTOOL from phone, ramloader has aborted got 1 bytes from modem, data looks like: 65 e got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 72 r It now move ahead and says the received MAGIC NACK and also that you need to have "1003" at 0x803ce0, this is a documented problem and i believe in compal_e86 binaries must have been taken care of. Any ideas on how can I get around this and load the firmware on my c139 ? I am again usung the same cable FTDI which works perfectly with c123. My setup is native Ubuntu 14.04 , host machine and Intel i5.. (hw does not seem to be the problem) Looking forward to hear from you guys. Thanks in advance. Regards, Ajay merlinsignals.blogspot.in

7 years, 10 months

1
0
0 0

Issue with C139

by Ajay Fuloria

Hi all, I have been using C123 for a long time with FTDI cable. I recently bought a C139 on which I wanted to run layer1 fw, i check the SW version using #02# and software version is "1.3.29", UART Flag is "0" On going through the mailing list I found these to be sufficient for using osmocom-bb but some how there is a problem on loading. When I use the fwg command ./osmocon -p /dev/ttyUSB0 -m c140 -c ../../target/firmware/board/compal_e86/layer1.highram.bin I get the following got 2 bytes from modem, data looks like: 04 81 .. got 5 bytes from modem, data looks like: 1b f6 02 00 41 ....A got 1 bytes from modem, data looks like: 01 . got 1 bytes from modem, data looks like: 40 @ Received PROMPT1 from phone, responding with CMD read_file(chainloader): file_size=32, hdr_len=4, dnload_len=15341 got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: f6 . got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 41 A got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 43 C Received PROMPT2 from phone, starting download handle_write(): 4096 bytes (4096/15341) handle_write(): 4096 bytes (8192/15341) handle_write(): 4096 bytes (12288/15341) handle_write(): 3053 bytes (15341/15341) handle_write(): finished It receives prompt2 and loads the file but doesn't move ahead, the phone does not show layer1 on the screen either. when i use fwg command (add -m c140xor ) ./osmocon -p /dev/ttyUSB0 -m c140xor -c ../../target/firmware/board/compal_e86/layer1.highram.bin I get the fwg: got 1 bytes from modem, data looks like: 04 . got 1 bytes from modem, data looks like: 81 . got 5 bytes from modem, data looks like: 1b f6 02 00 41 ....A got 1 bytes from modem, data looks like: 01 . got 1 bytes from modem, data looks like: 40 @ Received PROMPT1 from phone, responding with CMD read_file(chainloader): file_size=32, hdr_len=4, dnload_len=15341 got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: f6 . got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 41 A got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 43 C Received PROMPT2 from phone, starting download handle_write(): 4096 bytes (4096/15341) handle_write(): 4096 bytes (8192/15341) handle_write(): 4096 bytes (12288/15341) handle_write(): 3053 bytes (15341/15341) handle_write(): finished got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: f6 . got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 41 A got 1 bytes from modem, data looks like: 03 . got 1 bytes from modem, data looks like: 57 W Received MAGIC NACK from phone, you need to have "1003" at 0x803ce0 got 1 bytes from modem, data looks like: 66 f got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6d m got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6c l Received FTMTOOL from phone, ramloader has aborted got 1 bytes from modem, data looks like: 65 e got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 72 r It now move ahead and says the received MAGIC NACK and also that you need to have "1003" at 0x803ce0, this is a documented problem and i believe in compal_e86 binaries must have been taken care of. Any ideas on how can I get around this and load the firmware on my c139 ? I am again usung the same cable FTDI which works perfectly with c123. My setup is native Ubuntu 14.04 , host machine and Intel i5.. (hw does not seem to be the problem) Looking forward to hear from you guys. Thanks in advance. Regards, Ajay merlinsignals.blogspot.in

7 years, 10 months

1
0
0 0

Openphone

by Madhu Macaque Labs

I am the project lead for the SHAKTI open source processor project. See bitbucket.org/casl This is a large Indian processor development effort that aims to develop a range of processors (from uController to high end servers) based on the RISCV ISA. We work closely with UCB and Cambridge as part of this effort. As part of our processor family, we have just started on a mobile SoC. The goal is to have an octa core SoC with the performance of a snapdragon 820 or the Apple A9. the CPU core is pretty much under control but we are exploring the DSP needed for running the lower levels of the 3G/LTE stack. Another group does LTE stacks and so we have complete testing equipment available to test for compliance. I am basically looking for co-conspirators who can help identify the components I can use from the osmocom stack and figure out what else we need to develop. Then of course we need to develop the DSP core. We are currently reusing the UCB vector processor and we are trying to figure out if a vector thread processor or a conventional DSP will do the trick. Our goal is to have am SoC that will the functionality of a basic smart phone but we do not intend to focus only on a basic phone with voice/data ca[ability but with basic display (even 4 line display is OK). Plan to use the AD SDR board for the SDR section. So it will be a large board that is not optimized for size. Any comments, thoughts appreciated . In case you are wondering, yes we realize this a mammoth task but we are well funded ! This is part of the India processor project. And most importantly all our work will be patent free open source. HW will be BSD, SW will be GPL3/2 -- Regards, Madhu

7 years, 11 months

7
9
0 0

Re: Sv: 2G repeater/booster w/ osmocom-bb? or 3G w/ osmocom-bb?

by Craig Comstock

I found a 1900 band analog booster/repeater to try. > On Jun 20, 2016, at 2:32 PM, Erich Dachleger <edachleger(a)yahoo.com> wrote: > > Does anybody know if it would be possible to use some of the old vodaphone-femtocells together with openbsc/osmo-bts? > RegardsErich > > Den Mandag, 23. mai 2016 11.46 skrev etienne . <etiennehelluy(a)gmail.com>: > > > Short answer: no & no > 1 - A gsm repeater is an analog device. With osmocom-bb phones you would need to demodulate/remodulate bursts. > This wi

7 years, 11 months

1
0
0 0

OsmocomBB on Openmoko GTA02

by Cosmin - Ioan PETRI?OR

Hi guys, I have a lot of problems using osmocom-bb with an Openmoko GTA02. First of all, I followed all the instructions from here [1] and uploaded layer1.highram.bin via external jack serial port (second tutorial). Well, after the firmware is downloaded on the phone osmocon prints: " Finished, sent 54 blocks in total Received branch ack, your code is running now! " and nothing is printed anymore. Moreover, I see no activity on the serial port, all LEDs on my USB adapter being off. When I try to run cell_log from my PC, it prints the following error message and blocks / does nothing: " Failed to connect to '/tmp/osmocom_sap'. Failed during sap_open(), no SIM reader <000e> cell_log.c:804 Scanner initialized Mobile initialized, please start phone now! " I've read about this error and figured out that it is not fatal, but still cell_log doesn't work, nor does the 'mobile' application. I tried the code from master and from sylvain/testing branch and I uncommented "CONFIG_TX_ENABLE". I even tried hello_world.highram.bin and that doesn't print anything after loading it. I don't know what to do anymore. [1] http://bb.osmocom.org/trac/wiki/OpenMoko#no1

7 years, 11 months

1
0
0 0

L1 power measurement logs

by Вадим Яницкий

Hello everyone! During power measurement process we can see some messages like: PM MEAS: ARFCN=8, 55 dBm at baseband, -83 dBm at RF If I understood correctly, in this example received signal has -83 dBm (about 5e-12 W) strength before amplifier and 55 dBm (about 316.2 W) strength after one. It looks like the strength of amplified signal should be printed as -55 (about 3.2e-9 W), because 316.2 W is very high value. Am I right? Or is it internal signal strength representation used by DSP? С наилучшими пожеланиями, Яницкий Вадим.

7 years, 11 months

2
1
0 0

Please can anyone advise me - FMTOOL Error and no further processing

by Raz Sharif

Dear all, I vae the C115 with a T1 USB to Serial cable with the Prolific chipset. When i run osmocon i get :- an its just sits there with no further processing. ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin read_file(../../target/firmware/board/compal_e88/loader.compalram.bin): file_size=17120, hdr_len=4, dnload_len=17127 read_file(../../target/firmware/board/compal_e88/loader.compalram.bin): file_size=17120, hdr_len=4, dnload_len=17127 got 1 bytes from modem, data looks like: 00 . got 2 bytes from modem, data looks like: 2f 00 /. got 1 bytes from modem, data looks like: 1b . got 3 bytes from modem, data looks like: f6 02 00 ... got 1 bytes from modem, data looks like: 41 A got 1 bytes from modem, data looks like: 01 . got 1 bytes from modem, data looks like: 40 @ Received PROMPT1 from phone, responding with CMD got 1 bytes from modem, data looks like: 66 f got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6d m got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6c l Received FTMTOOL from phone, ramloader has aborted got 1 bytes from modem, data looks like: 65 e got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . I think the cable is ok as when i run my fingers on the tip i get random Zeros so it appears to be talking to the cable. Also when i tried to run Mobile i get the :- even though i created the Mobile.cfg file in /etc/osmoco Failed to parse the config file: '/home/raz/.osmocom/bb/mobile.cfg' Please check or create config file using: 'touch /home/raz/.osmocom/bb/mobile.cfg' I have spent some hours researching the lists and trying various things to no avail but I want to continue until I resolve this issues and use this great stack to learn about the GSM network. Please advise. Great full for any help or pointers but this maybe a timing issue that is difficult to debug. Thanks Raz

7 years, 11 months

5
6
0 0

Re: Terminal-profile DB

by Вадим Яницкий

> What are your ideas to make this database alive? I think we can make it more friendly to user. What do you think about merging both TAC and terminal-profile databases? One common DB and one web-interface seems good for me. Also I am thinking about implementation of a simple Java cardlet which will be aimed to extract device's profile and provide the results through SIM-menu. In this case everything that user need is get one programmable SIM and install this app. С наилучшими пожеланиями, Яницкий Вадим. 2016-05-21 10:13 GMT+06:00 Kévin Redon <kevredon(a)mail.tsaitgaist.info>: > What are your ideas to make this database alive? > > The easiest way to get the terminal profile of a phone is to monitor the > SIM interface. To automate that a script to be used along with SIMtrace is > provided. Alternatively you can use the email address. > Currently the database it is not very active because no one is submitting > entries since it's not as easy as getting a TAC/IMEI. > I also kind of like read only. It keeps external from messing around with > it. > But I'm happy to here what you have to propose. > > On Sat, May 21, 2016 at 12:13:56AM +0600, Вадим Яницкий wrote: > > Hi, > > > > I think it would be cool to "make alive" the terminal-profile database. > > Currently it can be visited in readonly mode: > > > > https://terminal-profile.osmocom.org/ > > > > I can make a page simular to http://tacdb.osmocom.org/ where > > anybody will be abble to contribute and download the lastest > > version of database. > > > > But before I begin, I would like to know your opinions. > > > > С наилучшими пожеланиями, > > Яницкий Вадим. >

7 years, 12 months

1
0
0 0

Terminal-profile DB

by Вадим Яницкий

Hi, I think it would be cool to "make alive" the terminal-profile database. Currently it can be visited in readonly mode: https://terminal-profile.osmocom.org/ I can make a page simular to http://tacdb.osmocom.org/ where anybody will be abble to contribute and download the lastest version of database. But before I begin, I would like to know your opinions. С наилучшими пожеланиями, Яницкий Вадим.

7 years, 12 months

1
0
0 0

Calypso_BTS stopping after few minutes

by robert

Hi, While experimenting with the calypsoBTS using a Motorola C118, I noticed that the transceiver always stops after a few minutes and displays the following messages: <0011> trx.c:419 TRX Control recv: |POWEROFF| <0011> trx.c:220 TRX Control send: |RSP POWEROFF 0| Does anyone know what is causing this problem? Best regards, Robert,

8 years

1
0
0 0

disable force rekey

by frank.holtz＠tutanota.com

Hello, I am facing an issue with the mobile app inside osmocom-bb. I checked with gr-gsm that my telecom operator changes the Kc ( by sending auth request) every 5 events (call or sms). But with the same sim card, I can see on Wireshark connected to the mobile app, the osmocom-bb phone received an auth request before every event. So my guess something causes the BTS to send a new auth request but only with osmocom-bb mobile app. I checked the source code, i found the option "force-rekey". Even with this option in mobile.cfg disabled I got the same issue. I saw that when enabled this option set the key sequence to 7. I tried with the latest version of osmocombb/libosmocore. Even with previous version from 2012 and last 2011 both osmocom-bb/libosmocore, different computer/ different phone (C123, c118 and c139), different cables (I use a shielded FTDI and a CP2102). Has anybody faced the same situation ? Have you an idea from where it can come from ? Thank you for your help Frank

8 years

1
0
0 0

Help with a bricked C118

by Simone Margaritelli

Hi everyone, I just got today a Motorola C118 with a CP2102 interface, so I’ve cloned and compiled the osmocom-bb and started playing with it, everything looked great ( osmocon working, hello world app, rssi and so forth, everything 100% perfect ). Then I started following this page http://osmocom.org/projects/baseband/wiki/Flashing_new <http://osmocom.org/projects/baseband/wiki/Flashing_new> Until I reached the point where the menu.e88loader.bin file was referenced … I don’t have this file (I’m on the master branch), so I closed every tabs of the terminal to search which branch contained that file. Problem is, I’ve executed all the commands prior to this one: host/osmocon/osmoload fprogram 0 0x012000 target/firmware/board/compal_e88/menu.e88loader.bin ( also saved the original loader ) and now the phone doesn’t turn on anymore, neither osmocon is able to detect it … so I guess it’s bricked? is there any way to unbrick it? Thanks for your help.

8 years

1
0
0 0

OsmoDevCon 2016 update

by Harald Welte

Dear attendees of OsmoDevCon 2016, below are some updates regarding OsmoDevCon 2016 = Lunch Catering = OsmoDevCon lunch catering has been finalized by now. I wanted to try some change by having (authentic) thai food, but unfortunately that didn't work out and we're back to our trusted old suppliers for all of the lunches. More details are available on http://projects.osmocom.org/projects/openbsc/wiki/OsmoDevCon2016 = Dinner Catering = In terms of dinner catering, we didn't plan/schedule anything yet. I know it was a request to have it and we introduced it (last year?) but I didn't have time to actively look for a sponsor for this in 2016, sorry. If you think it's important, I can try to get something organized for dinner too, but there's not much time left. It might be easier to simply go out in 2-3 groups, order pizza from the place down the road or even place a larger 'a la carte' order from another place. = Schedule / Talks = Thre's already a list of topics listed at the wiki, specifically: http://projects.osmocom.org/projects/openbsc/wiki/OsmoDevCon2016#TalksDiscu… I think we still have plenty of slots for talks, presentations, discussions, workshops, you name it. Each of you: Please take some time to think about a) topics that you would be able to contribute to the event by giving a talk or leading a discussion or workshop b) topics that you would like to hear about from somebody else Even if we do the actual scheduling ad-hoc at the event itself, it still is useful to have some advance notice about the topics, as the speaker(s) will need to prepare accordingly. = Attendance = If you have registered but will not attend, please let us know as we can still adjust the amount of food we get delivered, and we might offer your seat to somebody else. If you did not register but are an active contributor to the project(s) and would like to attend, let me know, too. I will let you know if somebody cancels their attendance. Looking forward to meeting all of you in Berlin soon. 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)

8 years, 1 month

2
2
0 0

ANN: https://patchwork.osmocom.org

by Holger Freyther

Hi, we are now running our own copy of patchwork at https://patchwork.osmocom.org. In addition to single patches this version can track series and has a REST API and git-pw client support. The system is currently subscribed to the GPRS, OpenBSC and OsmocomBB mailinglist. The installation is running offlineimap every couple of minutes to fetch new mail, this means it can take some minutes for your comment or patch to be visible. kind regards holger

8 years, 1 month

1
0
0 0

Can't flash app on C140(E86)

by Alex

I'm trying to flash the EMI app on a C140 using this tutorial: http://bb.osmocom.org/trac/wiki/flashing_new I can't fine menu.e86loader.bin file so I've flashed the menu.compalram.bin instead. All seem to be fine, but if I press the power button the screen doesn't turn on. I've made this procedure many times, but without success. Instead if I flash it in the ram, it work great. Why?

8 years, 1 month

1
0
0 0

BSIC neighboring cells dedicated mode

by asghar.mustafa

I am working on obtaining BSIC of neighbouring cells in dedicated mode. Any help would be highly appreciated. -- View this message in context: http://baseband-devel.722152.n3.nabble.com/BSIC-neighboring-cells-dedicated… Sent from the baseband-devel mailing list archive at Nabble.com.

8 years, 1 month

1
0
0 0

Re: Time to rename projects.osmocom.org to osmocom.org

by Вадим Яницкий

> I added: > proxy_set_header X-Forwarded-Ssl on; I think if nginx is used as main back-end (without Apache), this header means nothing. In this case just refer this guide: https://scotthelme.co.uk/setting-up-hsts-in-nginx/ If I'm not right, and there is also Apache server, follow: http://stackoverflow.com/questions/16042647/whats-the-de-facto-standard-for… С наилучшими пожеланиями, Яницкий Вадим.

8 years, 1 month

1
0
0 0

Time to rename projects.osmocom.org to osmocom.org

by Holger Freyther

Hi, I think we all liked tnt's proposal to just call it osmocom.org. Are we ready to make the redmine available as osmocom.org (and redirect www.osmocom.org, projects.osmocom.org to it)? As first step of redirects I propose: http://bb.osmocom.org/ -> http://osmocom.org/projects/baseband http://openbsc.osmocom.org/ -> http://osmocom.org/projects/openbsc http://tetra.osmocom.org/ -> http://osmocom.org/projects/tetra http://simtrace.osmocom.org/ -> http://osmocom.org/projects/simtrace http://security.osmocom.org/ -> http://osmocom.org/projects/security http://gmr.osmocom.org/ -> http://osmocom.org/projects/gmr http://sdr.osmocom.org/ -> http://osmocom.org/projects/sdr any objections or corrections to that? kind regards holger

8 years, 1 month

5
7
0 0

Record call

by robert

Hi, Is is possible to record a specific call using osmocombb? I want to record a call being made on the osmocombb phone not to sniff calls over the air. Best regards, Robert,

8 years, 2 months

3
3
0 0

Redmine theme

by Вадим Яницкий

Dear all, I suggest to change a stock Redmine theme to something more beautiful, for example gitmike: https://github.com/makotokw/redmine-theme-gitmike which used by srlabs.de and looks like pretty. Furthermore, the Osmocom logo will look better on light background. Opinions? С наилучшими пожеланиями, Яницкий Вадим.

8 years, 2 months

5
8
0 0

toolchain problem

by fotos-aller-art＠web.de

Hallo zusammen, ich wollte toolchain auf meinem Backtrack5r3 als VM installieren, dabei sind Fehler aufgetreten die ich nicht verstehe. Wie kann ich da Abhilfe schaffen? Bis hierhin war noch alles gut. GNU ARM toolchain This page will describe the procedure for compiling a GNU ARM toolchain. We will build a toolchain consisting of: * GCC 4.8.2 * Binutils 2.21.1 * Newlib 1.19 Getting the buildscript First of all, create a directory you want to use for building the toolchain, and download the buildscript <http://bb.osmocom.org/trac/raw-attachment/wiki/GnuArmToolchain/gnu-arm-buil d.3.sh> gnu-arm-build.3.sh there. You will need to make it executable: $ chmod +x gnu-arm-build.3.sh Dependencies In order to build the toolchain, you will need to install the following packages (assuming you're using a Debian-based distribution): $ sudo apt-get install build-essential libgmp3-dev libmpfr-dev libx11-6 libx11-dev texinfo flex bison libncurses5 \ libncurses5-dbg libncurses5-dev libncursesw5 libncursesw5-dbg libncursesw5-dev zlibc zlib1g-dev libmpfr4 libmpc-dev Preparation Open a shell in the directory of gnu-arm-build.sh and create the following directories: $ mkdir build install src Download the needed sources to src/: $ cd src/ $ wget http://ftp.gnu.org/gnu/gcc/gcc-4.8.2/gcc-4.8.2.tar.bz2 $ wget http://ftp.gnu.org/gnu/binutils/binutils-2.21.1a.tar.bz2 $ wget ftp://sources.redhat.com/pub/newlib/newlib-1.19.0.tar.gz Building the toolchain $ cd .. $ ./gnu-arm-build.3.sh I will build an arm-none-eabi cross-compiler: Prefix: <YOURPATH>/install Sources: <YOURPATH>/src Build files: <YOURPATH>/build Press ^C now if you do NOT want to do this. Dann kam folgendes, als wenn er Probleme mit den Ordnern hatte. cid:image001.jpg@01D17613.420C17C0 Könnt ihr mir weiterhelfen? Gruß Peseta3

8 years, 2 months

2
1
0 0

cell re-selection

by Andreas.Eversberg

hi, i did a lot of resarch and testing on cell selection and re-selection process the last two week. the cell selection process, network selection process (manual and automatic) and mobility management process were already implemented in OsmocomBB a long time, but turned out to be buggy and incomplete. i made test drives to check the process and debugged it. the re-selection process is new. it is used to track surrounding cells while listening to the BCCH of the current cell (camping on a cell). special extension to the layer1 firmare is used to measure neighbour cells. if an neighbour cell becomes 'better', the mobile switches to that cell, depening on different criteria. now it is possible to move with OsmocomBB. the re-selection process is not handover! handover is a process where a phone switches between cells while doing a call. handover is one next step to implement. the process is a little more complex, because it requires not only neighbour cell measurements, but also syncing to them without interrupting the traffic channel. most layer 3 stuff of handover is already implemented. if you like to play and test your moving OsmocomBB, you can check out the "jolly/roaming" branch. it contains the extension to layer1, as well as sim reader and fixes from "sylvain/testing" branch. use both "mobile" and "layer1" firmware from this branch. in order to see some process at VTY, you can do: enable monitor network 1 (continously display the strongest cell and neighbour cells) show ms 1 (to see current states) show neighbour-cells 1 (to see a more detailed current list of neighbours) andreas

8 years, 2 months

3
3
0 0

omsocombb not receiving calls

by robert steve

Hi, I would first like to thank all those who participated in this nice project. I recently started working with osmocombb and was able to have it working fine on a motorola c118. However, I noticed that some sim cards can connect normally to the BTS, can make calls and send SMS but can’t receive anything. They simply don't get paged. While for some other sim cards everything seems to be working fine. Does anyone know what might be causing this issue ? thanks, Robert

8 years, 2 months

3
2
0 0

Re: Record call

by robert

Can it be done without using LCR ? On Mar 4, 2016, at 10:21 AM, Dennis Eisenbarth <dennis.eisenbarth(a)gmail.com> wrote: > It should not be a problem. > > Have a nice day, > Dennis > > On 03.03.2016 18:47, robert wrote: >> Hi, >> >> Is is possible to record a specific call using osmocombb? I want to record a call being made on the osmocombb phone not to sniff calls over the air. >> >> >> Best regards, >> Robert, >

8 years, 2 months

1
0
0 0

Re: Record call

by robert

On Mar 4, 2016, at 10:21 AM, Dennis Eisenbarth <dennis.eisenbarth(a)gmail.com> wrote: > It should not be a problem. > > Have a nice day, > Dennis > > On 03.03.2016 18:47, robert wrote: >> Hi, >> >> Is is possible to record a specific call using osmocombb? I want to record a call being made on the osmocombb phone not to sniff calls over the air. >> >> >> Best regards, >> Robert, >

8 years, 2 months

1
0
0 0

Mobility Management in OsmocomBB code

by Ahmed Salman

Hello, I hope that this email finds you in good health. I am working on implementing the call handover part of mobility management in the OsmocomBB code as part of my Senior Year Project in University. I would like to ask you a few things about what you have implemented. Your help will guide me a lot in my endeavor. Please let me know whenever we can skype or call. Thanks and Regards, Ahmed

8 years, 2 months

1
0
0 0

Set fixed TMSI and Kc

by Simian Denson

Hi, in the osmocom bb mobile.cfg I don't see any posibility to set a fixed Kc encryption key and the tmsi. How could I achieve that osmocom uses my defined Kc and tmsi? cheers, Simian

8 years, 2 months

5
21
0 0

Re: Set fixed TMSI and Kc

by Вадим Яницкий

Look at this strings from your log: <0005> subscriber.c:601 Requesting SIM file 0x2fe2 <000f> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004) <000f> sim.c:697 go MF <000f> sim.c:241 SELECT (file=0x3f00) <000f> sim.c:187 sending APDU (class 0xa0, ins 0xa4) <000f> sim.c:876 received APDU (len=0 sw1=0x00 sw2=0x00) <000f> sim.c:952 command failed <000f> sim.c:151 sending result to callback function (type=1) <0005> subscriber.c:657 SIM reading failed Maybe something wrong with your SIM? Try another one. Are you at the master branch? С наилучшими пожеланиями, Яницкий Вадим.

8 years, 2 months

1
0
0 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel