OpenBSC

openbsc@lists.osmocom.org

8 participants
4276 discussions

Re: New Defects reported by Coverity Scan for Osmocom
by Neels Hofmeyr 15 Sep '21

15 Sep '21

On Tue, Sep 14, 2021 at 02:45:51AM +0000, scan-admin(a)coverity.com wrote: > 178 } else { > >>> CID 240100: Memory - illegal accesses (BUFFER_SIZE_WARNING) > >>> Calling "strncpy" with a maximum size argument of 64 bytes on destination array "codec->audio_name" of size 64 bytes might leave the destination string unterminated. > 179 strncpy(codec->audio_name, audio_name, sizeof(codec->audio_name)); strncpy() is another word for pitfall. We should *always* use osmo_strlcpy(), or OSMO_STRLCPY_ARRAY() to save typing 'sizeof'. osmith, could we put such a check in the linter maybe? i.e. forbid use of strncpy() and strcpy(). ~N

2 1

Connect cell phone to real GSM network through OpenBTS
by Mario Lucas 29 Aug '21

29 Aug '21

Dear Osmocom society, I am trying to connect a cell phone (lets call it phone #1) through OpenBTS to real GSM network… To do so i have to introduce a osmocomBB phone which will be connected to my linux machine which runs OpenBTS So kind of it will be a following structure: Phone #1 → OpenBTS → OsmocomBB phone → real GSM netwok. No my goal is to have OpenBTS and OsmocomBB phone to talk to each other… for example authentication parameters which to be exchanged between phone #1 and real network to happen through the chain described above …. Has this case been or something like this done before ? Or are you aware of any cases when OpenBTS and OsmocomBB phone exchange data? Thank you very much -- Mario Lucas

1 0

Announcement of "OsmoDevCall" on August 27, 2021
by Harald Welte 24 Aug '21

24 Aug '21

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at August 27, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation on "osmo-remsim in practice" 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Attendance is free of charge and open to anyone with an interest in Osmocom. More information about OsmoDevCall, including the schedule for further upcoming events can be found at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall Looking forward to meeting you on Friday. Best regards, Harald [*] this is how we started to call the "unstructured" part of osmocom developer conferences in the past, basically where anyone can talk about anything, no formal schedule or structure. -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

rsl_rx_bs_pwr_ctrl()
by Neels Hofmeyr 14 Aug '21

14 Aug '21

Hey Vadim, Just now I came across this code, with an early return in case of BCCH. But right below that, BCCH is still mentioned in the comment, and there are more IEs being parsed. So I get the impression the early return may prevent that OSMO_MIN limiting for BCCH, and that may not be intended? /* Osmocom specific extension for BCCH carrier power reduction */ if (dch->chan_nr == RSL_CHAN_BCCH) { int rc = bts_set_c0_pwr_red(trx->bts, new); if (rc != 0) { const uint8_t cause = (rc == -ENOTSUP) ? RSL_ERR_SERV_OPT_UNIMPL : RSL_ERR_IE_CONTENT; return rsl_tx_error_report(trx, cause, &dch->chan_nr, NULL, msg); } return 0; } /* BS power reduction is generally not allowed on BCCH/CCCH carrier. * However, we allow it in the BCCH carrier power reduction operation. * Constrain BS power value by the maximum reduction for this timeslot. */ if (trx->bts->c0 == trx) new = OSMO_MIN(new, lchan->ts->c0_power_red_db); /* 9.3.32 (TLV) BS Power Parameters IE (vendor specific) */ if ((ie = TLVP_GET(&tp, RSL_IE_BS_POWER_PARAM)) != NULL) { https://git.osmocom.org/osmo-bts/tree/src/common/rsl.c?id=6611e7f3059d26794…

2 2

Announcement of "OsmoDevCall" on August 13, 2021
by Harald Welte 12 Aug '21

12 Aug '21

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at August 13, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation on "GSM-R and its differences to GSM" 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Attendance is free of charge and open to anyone with an interest in Osmocom. More information about OsmoDevCall, including the schedule for further upcoming events can be found at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall Looking forward to meeting you on Friday. Best regards, Harald [*] this is how we started to call the "unstructured" part of osmocom developer conferences in the past, basically where anyone can talk about anything, no formal schedule or structure. -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

HR / AMR Lab Testing Using OSMO-NITB
by Sonny Lafuente 11 Aug '21

11 Aug '21

Hello Community! Would like to as if anyone here have experience testing Half rate /AMR in osmo-nitb and Freeswitch. Basically we are testing it in our lab with our devices Samsung Note 9 and iPhone and we are having issue / errors as observed during testing. Below are the details of the NITB we using: OpenBSC# show version OpenBSC 1.1.0.76-0bbb9 (OpenBSC). Copyright (C) 2008-2016 Harald Welte, Holger Freyther Contributions by Daniel Willmann, Jan Lübbe, Stefan Schmidt Dieter Spaar, Andreas Eversberg, Sylvain Munaut, Neels Hofmeyr License AGPLv3+: GNU AGPL version 3 or later <http://gnu.org/licenses/agpl-3.0.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. OpenBSC# Osmo running-config: stats interval 5 ! line vty no login ! e1_input e1_line 0 driver ipa e1_line 0 port 0 no e1_line 0 keepalive network network country code 10 mobile network code 1 short name testnetwork long name testnetwork auth policy closed authorized-regexp .* location updating reject cause 13 encryption a5 0 neci 1 paging any use tch 0 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 t3113 60 timer t3103 1 timer t3101 10 timer t3109 1 timer t3122 10 timer t3105 1 dyn_ts_allow_tch_f 0 subscriber-keep-in-ram 1 bts 0 type sysmobts band GSM900 cell_identity 1 location_area_code 1 base_station_id_code 63 ms max power 23 cell reselection hysteresis 4 rxlev access min 0 periodic location update 30 radio-link-timeout 32 channel allocator descending rach tx integer 9 rach max transmission 7 channel-descrption attach 1 channel-descrption bs-pa-mfrms 5 channel-descrption bs-ag-blks-res 1 early-classmark-sending forbidden ip.access unit_id 1000 0 oml ip.access stream_id 255 line 0 neighbor-list mode automatic codec-support fr hr efr amr amr tch-h modes 0 amr tch-h start-mode auto trx 0 rf_locked 0 arfcn 122 nominal power 0 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 hopping enabled 0 timeslot 1 phys_chan_config SDCCH8 hopping enabled 0 timeslot 2 phys_chan_config SDCCH8 hopping enabled 0 timeslot 3 phys_chan_config TCH/H hopping enabled 0 timeslot 4 phys_chan_config TCH/H hopping enabled 0 timeslot 5 phys_chan_config TCH/H hopping enabled 0 timeslot 6 phys_chan_config TCH/H hopping enabled 0 timeslot 7 phys_chan_config TCH/H hopping enabled 0 trx 1 rf_locked 0 arfcn 42 nominal power 0 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 hopping enabled 0 timeslot 1 phys_chan_config TCH/H hopping enabled 0 timeslot 2 phys_chan_config TCH/H hopping enabled 0 timeslot 3 phys_chan_config TCH/H hopping enabled 0 timeslot 4 phys_chan_config TCH/H hopping enabled 0 timeslot 5 phys_chan_config TCH/H hopping enabled 0 timeslot 6 phys_chan_config TCH/H hopping enabled 0 timeslot 7 phys_chan_config TCH/H hopping enabled 0 mncc-int default-codec tch-f fr default-codec tch-h amr nitb subscriber-create-on-demand subscriber-create-on-demand random 100000 199999 no assign-tmsi smpp local-tcp-ip 127.0.0.1 2776 system-id password policy closed smpp-first esme admin password password default-route NITB Logs: Not Working: Tue Aug 10 17:08:40 2021 <0004> abis_rsl.c:1848 (bts=0) CHAN RQD: reason: call re-establishment (ra=0x49, neci=0x01, chreq_reason=0x02) Tue Aug 10 17:08:40 2021 <0004> abis_rsl.c:1924 (bts=0,trx=1,ts=7,ss=0) Activating ARFCN(73) SS(0) lctype TCH_H r=CALL ra=0x49 ta=0 Tue Aug 10 17:08:40 2021 <0004> abis_rsl.c:595 (bts=0,trx=1,ts=7,pchan=TCH/H) Tx RSL Channel Activate with act_type=INITIAL Tue Aug 10 17:08:40 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=7,ss=0) state NONE -> ACTIVATION REQUESTED Tue Aug 10 17:08:40 2021 <0004> abis_rsl.c:1603 (bts=0,trx=1,ts=7,ss=0) CHANNEL ACTIVATE ACK Tue Aug 10 17:08:40 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=7,ss=0) state ACTIVATION REQUESTED -> ACTIVE Tue Aug 10 17:08:41 2021 <000a> bsc_api.c:415 Sending (bts=0,trx=1,ts=7,ss=0) ChanModify for speech: SPEECH_AMR on channel TCH_H Tue Aug 10 17:08:41 2021 <0003> gsm_04_08_utils.c:517 -> CHANNEL MODE MODIFY mode=0x41 <—————————————————————————————————————— This is what we observed, no Channel Modify Ack Tue Aug 10 17:08:47 2021 <000a> bsc_api.c:139 Assignment T10 timeout on 0x15b4350 Tue Aug 10 17:08:47 2021 <0003> osmo_msc.c:82 MSC assign failure (do nothing). Tue Aug 10 17:08:51 2021 <0004> abis_rsl.c:1848 (bts=0) CHAN RQD: reason: call re-establishment (ra=0x49, neci=0x01, chreq_reason=0x02) Tue Aug 10 17:08:51 2021 <0004> abis_rsl.c:1924 (bts=0,trx=1,ts=7,ss=1) Activating ARFCN(73) SS(1) lctype TCH_H r=CALL ra=0x49 ta=0 Tue Aug 10 17:08:51 2021 <0004> abis_rsl.c:595 (bts=0,trx=1,ts=7,pchan=TCH/H) Tx RSL Channel Activate with act_type=INITIAL Tue Aug 10 17:08:51 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=7,ss=1) state NONE -> ACTIVATION REQUESTED Tue Aug 10 17:08:51 2021 <0004> abis_rsl.c:1603 (bts=0,trx=1,ts=7,ss=1) CHANNEL ACTIVATE ACK Tue Aug 10 17:08:51 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=7,ss=1) state ACTIVATION REQUESTED -> ACTIVE Tue Aug 10 17:08:53 2021 <0017> smpp_smsc.c:746 [entropy] smpp_pdu_rx(00 00 00 10 00 00 00 15 00 00 00 00 00 00 00 24 ) Tue Aug 10 17:08:53 2021 <0017> smpp_smsc.c:595 [entropy] Rx Enquire Link Tue Aug 10 17:08:53 2021 <0017> smpp_smsc.c:599 [entropy] Tx Enquire Link Response Tue Aug 10 17:09:03 2021 <0004> abis_rsl.c:1848 (bts=0) CHAN RQD: reason: call re-establishment (ra=0x47, neci=0x01, chreq_reason=0x02) Tue Aug 10 17:09:03 2021 <0004> abis_rsl.c:1924 (bts=0,trx=1,ts=6,ss=0) Activating ARFCN(73) SS(0) lctype TCH_H r=CALL ra=0x47 ta=0 Tue Aug 10 17:09:03 2021 <0004> abis_rsl.c:595 (bts=0,trx=1,ts=6,pchan=TCH/H) Tx RSL Channel Activate with act_type=INITIAL Tue Aug 10 17:09:03 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=6,ss=0) state NONE -> ACTIVATION REQUESTED Tue Aug 10 17:09:03 2021 <0004> abis_rsl.c:1603 (bts=0,trx=1,ts=6,ss=0) CHANNEL ACTIVATE ACK Tue Aug 10 17:09:03 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=6,ss=0) state ACTIVATION REQUESTED -> ACTIVE Tue Aug 10 17:09:13 2021 <0004> abis_rsl.c:1358 (bts=0,trx=1,ts=7,ss=0) CONNECTION FAIL: RELEASING state ACTIVE CAUSE=0x01(Radio Link Failure) Tue Aug 10 17:09:13 2021 <0004> abis_rsl.c:867 (bts=0,trx=1,ts=7,ss=0) RF Channel Release due to error: 1 Tue Aug 10 17:09:13 2021 <0004> abis_rsl.c:777 (bts=0,trx=1,ts=7,ss=0) DEACTivate SACCH CMD Tue Aug 10 17:09:13 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=7,ss=0) state ACTIVE -> RELEASE DUE ERROR Tue Aug 10 17:09:13 2021 <0004> abis_rsl.c:939 (bts=0,trx=1,ts=7,ss=0) RF CHANNEL RELEASE ACK Tue Aug 10 17:09:17 2021 <0004> abis_rsl.c:826 (bts=0,trx=1,ts=7,ss=0) is back in operation. Tue Aug 10 17:09:17 2021 <0004> abis_rsl.c:1231 (bts=0,trx=1,ts=7,ss=0) state RELEASE DUE ERROR -> NONE Tue Aug 10 17:09:19 2021 <0004> abis_rsl.c:1848 (bts=0) CHAN RQD: reason: Location updating (ra=0x07, neci=0x01, chreq_reason=0x03) Tue Aug 10 17:09:19 2021 <0004> abis_rsl.c:1924 (bts=0,trx=0,ts=1,ss=0) Activating ARFCN(8) SS(0) lctype SDCCH r=LOCATION_UPDATE ra=0x07 ta=0 Tue Aug 10 17:09:19 2021 <0004> abis_rsl.c:595 (bts=0,trx=0,ts=1,pchan=SDCCH8) Tx RSL Channel Activate with act_type=INITIAL Tue Aug 10 17:09:19 2021 <0004> abis_rsl.c:1231 (bts=0,trx=0,ts=1,ss=0) state NONE -> ACTIVATION REQUESTED Tue Aug 10 17:09:19 2021 <0004> abis_rsl.c:1603 (bts=0,trx=0,ts=1,ss=0) CHANNEL ACTIVATE ACK Tue Aug 10 17:09:19 2021 <0004> abis_rsl.c:1231 (bts=0,trx=0,ts=1,ss=0) state ACTIVATION REQUESTED -> ACTIVE Osmo-sip-connector Logs: <0000> sip.c:330 sip_release_call(): Release with MNCC cause(NORM_CALL_CLEAR) <0000> sip.c:302 cause2status(): Mapping cause(NORM_CALL_CLEAR) to status(200) <0000> sip.c:353 Ending leg(0x8dc700) in con <0000> sip.c:223 SIP event(33) status(200) phrase(OK) 0x8dc700 <0000> sip.c:257 leg(0x8dc700) got resp to bye <0000> sip.c:223 SIP event(9) status(200) phrase(Session Terminated) 0x8d7150 <0000> sip.c:265 leg(0x8d7150) got bye, releasing. <0000> sip.c:223 SIP event(7) status(0) phrase(INVITE sent) 0x8d7150 <0000> sip.c:223 SIP event(1) status(100) phrase(Trying) (nil) <0000> sip.c:89 Incoming call handle(0x8d96a0) <0000> sip.c:223 SIP event(7) status(100) phrase(Trying) 0x8dc700 <0000> sip.c:330 sip_release_call(): Release with MNCC cause(RESOURCE_UNAVAIL) <0000> sip.c:302 cause2status(): Mapping cause(RESOURCE_UNAVAIL) to status(503) <0000> sip.c:341 Canceling leg(0x8dc700) in cnfd state <0000> sip.c:223 SIP event(31) status(503) phrase(Service Unavailable) 0x8d7150 <0000> sip.c:242 leg(0x8d7150) unknown SIP status(503), releasing. <0000> sip.c:248 Releasing other leg (0x8d6f30) with status(503) <0001> mncc.c:54 cmd(0x204) never arrived for leg(2147483656) <—————————————————————————————————————— Basically it didn’t arrived in B Leg. <0001> mncc.c:495 call(2147483656) can not be found Very well appreciated your help on this. Best Regards, Sonny

3 2

Harald's surplus telecom equipment for free
by Harald Welte 10 Aug '21

10 Aug '21

Hi all, as I currently have to clear my basement for water-damage related renovation, I'm going to use the opportunity to get rid of some of the things I'm unlikely going to use ever again https://osmocom.org/projects/miscellaneous-projects/wiki/LaForge_surplus_20… If anyone is interested: I'm not looking for any money in return. I just want to find a new home for it rather than actually disposing of it at some recycling facility. Let me know ASAP if you're interested in any of it, thanks. Happy hacking, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

Can't establish calls between two handsets [nanoBTS 165AU]
by Sebastian Mauer 02 Aug '21

02 Aug '21

Hello there, In my lab I have access to an ip.access nanoBTS 165AU which I have setup with OsmoBSC. Sending SMS between my two test handsets (Nokia 105) are working fine, however it seems there is a problem when making calls. From the logs it seems the radio is unable to assign a TCH_F channel. Any idea what could be causing this and how I would debug this further? Cheers, Sebastian <0003> abis_rsl.c:1533 (bts=0) CHAN RQD: reason: call re-establishment (ra=0x49, neci=0x01, chreq_reason=0x02) <000f> lchan_select.c:262 lchan(0-0-0-CCCH_SDCCH4-0)[0xaaaadc4251c0]{UNUSED}: (type=SDCCH) Selected <000f> lchan_fsm.c:636 lchan(0-0-0-CCCH_SDCCH4-0)[0xaaaadc4251c0]{WAIT_TS_READY}: (type=SDCCH) Activation requested: FOR_MS_CHANNEL_REQUEST voice=no MGW-ci=none type=SDCCH tch-mode=SIGNALLING encr-alg=A5/0 ck=none <0007> osmo_bsc_sigtran.c:297 Initializing resources for new SCCP connection to MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP... <0007> osmo_bsc_sigtran.c:343 Opening new SCCP connection (id=4) to MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP <0007> osmo_bsc_bssap.c:1147 Rx MSC DT1 BSSMAP COMMON ID <0007> osmo_bsc_bssap.c:1251 Rx MSC DTAP, SAPI: RR/MM/CC CHAN: 0 <0007> gsm_08_08.c:567 Tx MSC DTAP LINK_ID=0x00 <0007> osmo_bsc_sigtran.c:383 Tx MSC: DTAP <0007> osmo_bsc_bssap.c:1251 Rx MSC DTAP, SAPI: RR/MM/CC CHAN: 2 <0007> osmo_bsc_bssap.c:1110 Rx MSC UDT BSSMAP PAGING <0007> osmo_bsc_bssap.c:126 (msc0) Paging: subscr-IMSI-901700000050081-TMSI-0x06e8ff82: (bts0) Paging on LAC 1 <0007> osmo_bsc_bssap.c:1147 Rx MSC DT1 BSSMAP ASSIGNMENT REQ <000f> lchan_select.c:262 lchan(0-0-2-TCH_F-0)[0xaaaadc432ba0]{UNUSED}: (type=TCH_F) Selected <0011> assignment_fsm.c:570 assignment(msc0-conn4_subscr-IMSI-901700000050080-TMSI-0xbf4aa84d_0-0-2-TCH_F-0)[0xaaaadc43e930]{WAIT_LCHAN_ACTIVE}: (bts=0,trx=0,ts=2,ss=0) Starting Assignment: chan_mode=SPEECH_V1, chan_type=FR, aoip=yes MSC-rtp=192.168.148.159:4074 (osmux=no) <000f> lchan_fsm.c:636 lchan(0-0-2-TCH_F-0)[0xaaaadc432ba0]{WAIT_TS_READY}: (type=TCH_F) Activation requested: FOR_ASSIGNMENT voice=yes MGW-ci=new type=TCH_F tch-mode=SPEECH_V1 encr-alg=A5/0 ck=none <000f> lchan_fsm.c:81 lchan(0-0-2-TCH_F-0)[0xaaaadc432ba0]{WAIT_RLL_RTP_ESTABLISH}: (type=TCH_F) lchan-rtp failure in state WAIT_IPACC_CRCX_ACK: Received NACK on IPACC CRCX <000f> lchan_fsm.c:81 lchan(0-0-2-TCH_F-0)[0xaaaadc432ba0]{WAIT_RLL_RTP_ESTABLISH}: (type=TCH_F) lchan allocation failed in state WAIT_RLL_RTP_ESTABLISH: Failed to setup RTP stream: LCHAN_EV_RTP_ERROR in state WAIT_RLL_RTP_ESTABLISH <000f> lchan_fsm.c:116 lchan(0-0-2-TCH_F-0)[0xaaaadc432ba0]{WAIT_RLL_RTP_ESTABLISH}: (type=TCH_F) Signalling Assignment FSM of error (lchan allocation failed in state WAIT_RLL_RTP_ESTABLISH: Failed to setup RTP stream: LCHAN_EV_RTP_ERROR in state WAIT_RLL_RTP_ESTABLISH ) <0011> assignment_fsm.c:821 assignment(msc0-conn4_subscr-IMSI-901700000050080-TMSI-0xbf4aa84d_0-0-2-TCH_F-0)[0xaaaadc43e930]{WAIT_RR_ASS_COMPLETE}: (bts=0,trx=0,ts=2,ss=0) Assignment failed in state WAIT_RR_ASS_COMPLETE, cause RADIO INTERFACE MESSAGE FAILURE: Failed to activate lchan (bts=0,trx=0,ts=2,ss=0) <0007> osmo_bsc_sigtran.c:379 Tx MSC: BSSMAP: ASSIGNMENT FAIL <0011> assignment_fsm.c:148 assignment(msc0-conn4_subscr-IMSI-901700000050080-TMSI-0xbf4aa84d_0-0-2-TCH_F-0)[0xaaaadc43e930]{WAIT_RR_ASS_COMPLETE}: (bts=0,trx=0,ts=2,ss=0) Assignment failed <0007> osmo_bsc_bssap.c:1251 Rx MSC DTAP, SAPI: RR/MM/CC CHAN: 2 <0007> osmo_bsc_bssap.c:1147 Rx MSC DT1 BSSMAP CLEAR COMMAND <0007> osmo_bsc_sigtran.c:379 Tx MSC: BSSMAP: CLEAR COMPLETE <0005> paging.c:84 (bts=0) Going to send paging commands: subscr-IMSI-901700000050081-TMSI-0x06e8ff82 for ch. type 0 (attempt 0) <000f> gsm_04_08_rr.c:1021 lchan(0-0-0-CCCH_SDCCH4-0)[0xaaaadc4251c0]{WAIT_BEFORE_RF_RELEASE}: (type=SDCCH) Got data in non active state, discarding. <0005> paging.c:84 (bts=0) Going to send paging commands: subscr-IMSI-901700000050081-TMSI-0x06e8ff82 for ch. type 0 (attempt 1) <0005> paging.c:84 (bts=0) Going to send paging commands: subscr-IMSI-901700000050081-TMSI-0x06e8ff82 for ch. type 0 (attempt 2) <0003> abis_rsl.c:1533 (bts=0) CHAN RQD: reason: answer to paging (ra=0x9f, neci=0x01, chreq_reason=0x01) <000f> lchan_select.c:262 lchan(0-0-0-CCCH_SDCCH4-1)[0xaaaadc425390]{UNUSED}: (type=SDCCH) Selected <000f> lchan_fsm.c:636 lchan(0-0-0-CCCH_SDCCH4-1)[0xaaaadc425390]{WAIT_TS_READY}: (type=SDCCH) Activation requested: FOR_MS_CHANNEL_REQUEST voice=no MGW-ci=none type=SDCCH tch-mode=SIGNALLING encr-alg=A5/0 ck=none <0005> paging.c:84 (bts=0) Going to send paging commands: subscr-IMSI-901700000050081-TMSI-0x06e8ff82 for ch. type 0 (attempt 3) <0007> osmo_bsc_sigtran.c:297 Initializing resources for new SCCP connection to MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP... <0007> osmo_bsc_sigtran.c:343 Opening new SCCP connection (id=5) to MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP <0007> osmo_bsc_bssap.c:1147 Rx MSC DT1 BSSMAP COMMON ID <0007> osmo_bsc_bssap.c:1147 Rx MSC DT1 BSSMAP CLEAR COMMAND <0007> osmo_bsc_sigtran.c:379 Tx MSC: BSSMAP: CLEAR COMPLETE <0003> abis_rsl.c:1533 (bts=0) CHAN RQD: reason: answer to paging (ra=0x88, neci=0x01, chreq_reason=0x01) <000f> lchan_select.c:262 lchan(0-0-0-CCCH_SDCCH4-0)[0xaaaadc4251c0]{UNUSED}: (type=SDCCH) Selected <000f> lchan_fsm.c:636 lchan(0-0-0-CCCH_SDCCH4-0)[0xaaaadc4251c0]{WAIT_TS_READY}: (type=SDCCH) Activation requested: FOR_MS_CHANNEL_REQUEST voice=no MGW-ci=none type=SDCCH tch-mode=SIGNALLING encr-alg=A5/0 ck=none <0007> osmo_bsc_sigtran.c:297 Initializing resources for new SCCP connection to MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP... <0007> osmo_bsc_sigtran.c:343 Opening new SCCP connection (id=6) to MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP <0007> osmo_bsc_bssap.c:1147 Rx MSC DT1 BSSMAP COMMON ID <0007> osmo_bsc_bssap.c:1147 Rx MSC DT1 BSSMAP CLEAR COMMAND <0007> osmo_bsc_sigtran.c:379 Tx MSC: BSSMAP: CLEAR COMPLETE

3 4

MS Power Transmit not changing
by Sonny Lafuente 30 Jul '21

30 Jul '21

Hello Neels and Community, Good day! We are doing some testing on our Lab specifically in Voice. During this testing we observed that the MS power transmit is not changing during ongoing call and the value is 5dbm. We also do walk test in order to lower the received power level and to observed if the MS Transmit power will increase. We tried to change some parameters in osmo-bts-trx uplink-power-target but however, the MS Transmit power still the same which is 5dbm. The MS power in the osmo-nitb config is set to 23dbm. Below is the version and configuration we used on our testing in Lab. Version: OpenBSC# show version OpenBSC 1.3.2.2-d2550 (OpenBSC). Copyright (C) 2008-2016 Harald Welte, Holger Freyther Contributions by Daniel Willmann, Jan Lübbe, Stefan Schmidt Dieter Spaar, Andreas Eversberg, Sylvain Munaut, Neels Hofmeyr License AGPLv3+: GNU AGPL version 3 or later <http://gnu.org/licenses/agpl-3.0.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. OpenBSC# OsmoBTS# show version OsmoBTS 1.2.0.48-6392 (OsmoBTS). Copyright (C) 2010, 2011 by Harald Welte, Andreas Eversberg and On-Waves License AGPLv3+: GNU AGPL version 3 or later <http://gnu.org/licenses/agpl-3.0.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. OsmoBTS# Logs: OpenBSC# show lchan BTS 0, TRX 1, Timeslot 0, Lchan 0: Type SDCCH Connection: 1, State: ACTIVE BS Power: 0 dBm, MS Power: 23 dBm Channel Mode / Codec: signalling Subscriber: ID: 1816, Authorized: 0 Extension: 164324 IMSI: 515039102991665 Use count: 1 Bound IP: 0.0.0.0 Port 0 RTP_TYPE2=0 CONN_ID=0 Measurement Report: Flags: DLinval RXL-FULL-ul: -50 dBm, RXL-SUB-ul: -50 dBm RXQ-FULL-ul: 7, RXQ-SUB-ul: 7 BTS 0, TRX 1, Timeslot 6, Lchan 0: Type TCH_F Connection: 1, State: ACTIVE BS Power: 0 dBm, MS Power: 23 dBm Channel Mode / Codec: FR or HR Subscriber: ID: 1782, Authorized: 1 Extension: 05837654321 IMSI: 515032920153135 Use count: 2 Bound IP: X.X.X.X Port 16386 RTP_TYPE2=0 CONN_ID=0 Measurement Report: Flags: MS Timing Offset: 0 L1 MS Power: 5 dBm, Timing Advance: 0 RXL-FULL-dl: -47 dBm, RXL-SUB-dl: -47 dBm RXQ-FULL-dl: 0, RXQ-SUB-dl: 0 RXL-FULL-ul: -47 dBm, RXL-SUB-ul: -47 dBm RXQ-FULL-ul: 0, RXQ-SUB-ul: 0 BTS 0, TRX 1, Timeslot 7, Lchan 0: Type TCH_F Connection: 1, State: ACTIVE BS Power: 0 dBm, MS Power: 23 dBm Channel Mode / Codec: FR or HR Subscriber: ID: 4, Authorized: 1 Extension: 05831234567 IMSI: 515032919099978 Use count: 2 Bound IP: X.X.X.X Port 16384 RTP_TYPE2=0 CONN_ID=0 Measurement Report: Flags: MS Timing Offset: 0 L1 MS Power: 5 dBm, Timing Advance: 0 RXL-FULL-dl: -47 dBm, RXL-SUB-dl: -47 dBm RXQ-FULL-dl: 4, RXQ-SUB-dl: 5 RXL-FULL-ul: -47 dBm, RXL-SUB-ul: -47 dBm RXQ-FULL-ul: 7, RXQ-SUB-ul: 7 OpenBSC# Ongoing Call Logs: OpenBSC# show lchan summary BTS 0, TRX 1, Timeslot 6 TCH/F, Lchan 0, Type TCH_F, State ACTIVE - L1 MS Power: 5 dBm RXL-FULL-dl: -47 dBm RXL-FULL-ul: -47 dBm BTS 0, TRX 1, Timeslot 7 TCH/F, Lchan 0, Type TCH_F, State ACTIVE - L1 MS Power: 5 dBm RXL-FULL-dl: -47 dBm RXL-FULL-ul: -47 dBm OpenBSC# Osmo-BTS current config: e1_input e1_line 0 driver ipa e1_line 0 port 0 no e1_line 0 keepalive phy 0 osmotrx ip local 127.0.0.1 osmotrx ip remote 127.0.0.1 no osmotrx ms-power-loop osmotrx base-port local 5800 osmotrx base-port remote 5700 osmotrx fn-advance 20 osmotrx rts-advance 5 instance 0 osmotrx rx-gain 0 osmotrx tx-attenuation 13 osmotrx maxdly 0 instance 1 osmotrx rx-gain 0 osmotrx tx-attenuation 10 osmotrx maxdly 0 bts 0 band GSM900 ipa unit-id 1000 0 oml remote-ip x.x.x.x rtp jitter-buffer 100 paging queue-size 200 paging lifetime 0 uplink-power-target -75 gsmtap-sapi ccch gsmtap-sapi pdtch min-qual-rach 50 min-qual-norm -5 max-ber10k-rach 1707 trx 0 power-ramp max-initial 0 mdBm power-ramp step-size 2000 mdB power-ramp step-interval 1 ms-power-control dsp phy 0 instance 0 trx 1 power-ramp max-initial 0 mdBm power-ramp step-size 2000 mdB power-ramp step-interval 1 ms-power-control dsp phy 0 instance 1 Osmo-Nitb Current Config: root@ubuntu:/etc/osmocom# cat osmo-nitb.cfg ! log stderr logging filter all 1 logging color 1 logging print category 0 logging timestamp 1 logging level all everything logging level rll notice logging level cc notice logging level mm notice logging level rr notice logging level rsl notice logging level nm info logging level mncc notice logging level pag notice logging level meas notice logging level sccp notice logging level msc notice logging level mgcp notice logging level ho notice logging level db notice logging level ref notice logging level gprs debug logging level ns info logging level bssgp debug logging level llc debug logging level sndcp debug logging level nat notice logging level ctrl notice logging level smpp debug logging level filter debug logging level ranap debug logging level sua debug logging level pcu debug logging level lglobal notice logging level llapd notice logging level linp notice logging level lmux notice logging level lmi notice logging level lmib notice logging level lsms notice logging level lctrl notice logging level lgtp notice logging level lstats notice logging level lgsup notice logging level loap notice logging level lss7 notice logging level lsccp notice logging level lsua notice logging level lm3ua notice logging level lmgcp notice ! stats interval 5 ! line vty no login ! e1_input e1_line 0 driver ipa e1_line 0 port 0 no e1_line 0 keepalive network network country code 10 mobile network code 1 short name testnetwork long name testnetwork auth policy closed authorized-regexp .* location updating reject cause 13 encryption a5 0 neci 1 paging any use tch 0 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 t3113 60 timer t3103 1 timer t3101 10 timer t3109 1 timer t3122 10 timer t3105 1 dyn_ts_allow_tch_f 0 subscriber-keep-in-ram 1 bts 0 type sysmobts band GSM900 cell_identity 1 location_area_code 1 base_station_id_code 63 ms max power 23 cell reselection hysteresis 4 rxlev access min 0 periodic location update 30 radio-link-timeout 32 channel allocator descending rach tx integer 9 rach max transmission 7 channel-descrption attach 1 channel-descrption bs-pa-mfrms 5 channel-descrption bs-ag-blks-res 1 early-classmark-sending forbidden ip.access unit_id 1000 0 oml ip.access stream_id 255 line 0 neighbor-list mode automatic codec-support fr hr efr amr amr tch-h modes 0 amr tch-h start-mode auto gprs mode gprs gprs 11bit_rach_support_for_egprs 0 gprs routing area 1 gprs network-control-order nc0 gprs cell bvci 2 gprs cell timer blocking-timer 3 gprs cell timer blocking-retries 3 gprs cell timer unblocking-retries 3 gprs cell timer reset-timer 3 gprs cell timer reset-retries 3 gprs cell timer suspend-timer 10 gprs cell timer suspend-retries 3 gprs cell timer resume-timer 10 gprs cell timer resume-retries 3 gprs cell timer capability-update-timer 10 gprs cell timer capability-update-retries 3 gprs nsei 101 gprs ns timer tns-block 3 gprs ns timer tns-block-retries 3 gprs ns timer tns-reset 3 gprs ns timer tns-reset-retries 3 gprs ns timer tns-test 30 gprs ns timer tns-alive 3 gprs ns timer tns-alive-retries 10 gprs nsvc 0 nsvci 101 gprs nsvc 0 local udp port 23000 gprs nsvc 0 remote udp port 23000 gprs nsvc 0 remote ip 127.0.0.2 gprs nsvc 1 nsvci 0 gprs nsvc 1 local udp port 0 gprs nsvc 1 remote udp port 0 gprs nsvc 1 remote ip 0.0.0.0 no force-combined-si trx 0 rf_locked 0 arfcn 122 nominal power 0 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 hopping enabled 0 timeslot 1 phys_chan_config SDCCH8 hopping enabled 0 timeslot 2 phys_chan_config SDCCH8 hopping enabled 0 timeslot 3 phys_chan_config TCH/F hopping enabled 0 timeslot 4 phys_chan_config TCH/F hopping enabled 0 timeslot 5 phys_chan_config TCH/F hopping enabled 0 timeslot 6 phys_chan_config TCH/F hopping enabled 0 timeslot 7 phys_chan_config TCH/F hopping enabled 0 trx 1 rf_locked 0 arfcn 42 nominal power 0 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 hopping enabled 0 timeslot 1 phys_chan_config TCH/F hopping enabled 0 timeslot 2 phys_chan_config TCH/F hopping enabled 0 timeslot 3 phys_chan_config TCH/F hopping enabled 0 timeslot 4 phys_chan_config TCH/F hopping enabled 0 timeslot 5 phys_chan_config TCH/F hopping enabled 0 timeslot 6 phys_chan_config TCH/F hopping enabled 0 timeslot 7 phys_chan_config TCH/F hopping enabled 0 mncc-int default-codec tch-f fr default-codec tch-h amr nitb subscriber-create-on-demand subscriber-create-on-demand random 100000 199999 no assign-tmsi smpp local-tcp-ip 127.0.0.1 2776 system-id password policy closed smpp-first esme admin password password default-route Rootubuntu:/etc/osmocom# Regards, Sonny Lafuente | Systems Engineer | Entropy Solution Philippines Mobile: +639985365206 | Office: 028931781 | Email: sonny.lafuente(a)entropysolution.com<mailto:sonny.lafuente@entropysolution.com> Office Address: Unit 2103 Antel Corporate Centre 121 Valero St. Salcedo Village Makati City Philippines 1227 [cid:936BCCE1-8AAB-4E96-8413-E1075D00DBE3] Singapore * Philippines Products: Gridloc*Intelle*Hype*Lighthouse*Telco Services*Software Development This email (including any attachment to it) is confidential and intended only for the use of the individual named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message (including any attachment to it). Thank you.

2 1

(no subject)
by Henry Caga 26 Jul '21

26 Jul '21

Hi, I would like to know if it is possible to disconnect a connected device to my osmo-bsc system? After running my osmo-bsc setup and my test phone is connected to my usrp via 2g, is it possible to send a vty command or what are the steps to make the connected device to detach to my bts? Thank you so much. Hnjojo

3 4

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC