OpenBSC

openbsc@lists.osmocom.org

13 participants
4246 discussions

Ericsson RBS6000 surplus situation
by Mychaela Falconia 17 Sep '24

17 Sep '24

Hello fellow Osmocomers, I just recently came across and watched Harald's ODC 2018 presentation about Ericsson RBS 6000. The part that intrigued me: Harald said in that year that this hardware was available quite inexpensively and plentifully; he said that a DUG10+RUG pair could be had for around 300 EUR in that year. My question to the community: what is the current situation 6 y later? Is there still any above-zero supply of either DUG10+RUG or DUG20+RUS surplus hardware? If a nonzero supply does exist, what is the typical price these days? In that 2018 presentation Harald also mentioned that the successor to DUG20 was DUS31/DUS41, and that those DUS units (which support GSM, WCDMA and LTE all in one box) have integrated SIU02 equivalent instead of native E1 interfaces. Hence question: has anyone in Osmocom cracked the E1-over-IP protocol spoken by SIU02 and its later incarnations, allowing Osmocom CNI to drive the GSM part of DUS31 etc, or is such operation beyond our current community capabilities? There are rumors going around that T-Mobile USA may be shutting down some Ericsson 2G equipment (though I still never got any clear answers as to what equipment it might be, if any), hence I am trying to brush up on my knowledge of this platform. M~

4 5

USRP1 not wanting to transmit (osmo-trx-usrp1)
by laptop fm 05 Sep '24

05 Sep '24

Hello, I tried using the osmocom stack with the usrp1 and I encountered this error : DMAIN NOTICE Starting the transceiver (Transceiver.cpp:287) DDEV NOTICE Setting TX gain to 0 dB. (USRPDevice.cpp:265) DDEV NOTICE Setting RX gain to 20 dB. (USRPDevice.cpp:292) DDEV NOTICE Setting TX gain to 0 dB. (USRPDevice.cpp:265) DDEV NOTICE Setting TX gain to 0 dB. (USRPDevice.cpp:265) DDEV NOTICE Setting TX gain to 0 dB. (USRPDevice.cpp:265) DMAIN NOTICE Stopping the transceiver (Transceiver.cpp:345) after that the osmo-trx-usrp1 seems to crash. I know it is not supported anymore but any possible fix would be appreciated. here is my system and log files together with a pcap : System : Debian 12 amd64 using osmocom-nightly repo (the stable repo still gives the same error)

1 0

subdivide large .ttcn files for faster dev cycle
by Neels Hofmeyr 31 Aug '24

31 Aug '24

I've raised this some years ago, then had gotten the response that our .ttcn files should grow to any size, and we should fix the tooling instead or buy a faster computer. But I'm still having the annoyance when working with our ttcn that even changing a tiny constant will trigger a longish recompilation. It looks like it is dividing a .ttcn into parts, and keeps recompiling *all* of the parts. (not always all of the parts, but usually it is clumsy about compiling more than would be logically required from my POV.) It looks like this: + make -j 5 Creating dependency file for HNBGW_Tests_part_6.cc Creating dependency file for HNBGW_Tests_part_5.cc Creating dependency file for HNBGW_Tests_part_4.cc Creating dependency file for HNBGW_Tests_part_3.cc Creating dependency file for HNBGW_Tests_part_2.cc Creating dependency file for HNBGW_Tests_part_1.cc Creating dependency file for HNBGW_Tests.cc env CCACHE_SLOPPINESS=time_macros ccache g++ -c -DLINUX -DMAKEDEPEND_RUN -DUSE_SCTP -DLKSCTP_MULTIHOMING_ENABLED -DAS_USE_SSL -I/usr/include/titan -fPIC -o HNBGW_Tests.o HNBGW_Tests.cc env CCACHE_SLOPPINESS=time_macros ccache g++ -c -DLINUX -DMAKEDEPEND_RUN -DUSE_SCTP -DLKSCTP_MULTIHOMING_ENABLED -DAS_USE_SSL -I/usr/include/titan -fPIC -o HNBGW_Tests_part_1.o HNBGW_Tests_part_1.cc env CCACHE_SLOPPINESS=time_macros ccache g++ -c -DLINUX -DMAKEDEPEND_RUN -DUSE_SCTP -DLKSCTP_MULTIHOMING_ENABLED -DAS_USE_SSL -I/usr/include/titan -fPIC -o HNBGW_Tests_part_2.o HNBGW_Tests_part_2.cc env CCACHE_SLOPPINESS=time_macros ccache g++ -c -DLINUX -DMAKEDEPEND_RUN -DUSE_SCTP -DLKSCTP_MULTIHOMING_ENABLED -DAS_USE_SSL -I/usr/include/titan -fPIC -o HNBGW_Tests_part_3.o HNBGW_Tests_part_3.cc env CCACHE_SLOPPINESS=time_macros ccache g++ -c -DLINUX -DMAKEDEPEND_RUN -DUSE_SCTP -DLKSCTP_MULTIHOMING_ENABLED -DAS_USE_SSL -I/usr/include/titan -fPIC -o HNBGW_Tests_part_4.o HNBGW_Tests_part_4.cc env CCACHE_SLOPPINESS=time_macros ccache g++ -c -DLINUX -DMAKEDEPEND_RUN -DUSE_SCTP -DLKSCTP_MULTIHOMING_ENABLED -DAS_USE_SSL -I/usr/include/titan -fPIC -o HNBGW_Tests_part_5.o HNBGW_Tests_part_5.cc env CCACHE_SLOPPINESS=time_macros ccache g++ -c -DLINUX -DMAKEDEPEND_RUN -DUSE_SCTP -DLKSCTP_MULTIHOMING_ENABLED -DAS_USE_SSL -I/usr/include/titan -fPIC -o HNBGW_Tests_part_6.o HNBGW_Tests_part_6.cc env CCACHE_SLOPPINESS=time_macros ccache g++ -shared -o HNBGW_Tests.so HNBGW_Tests.o env CCACHE_SLOPPINESS=time_macros ccache g++ -shared -o HNBGW_Tests_part_3.so HNBGW_Tests_part_3.o env CCACHE_SLOPPINESS=time_macros ccache g++ -shared -o HNBGW_Tests_part_4.so HNBGW_Tests_part_4.o env CCACHE_SLOPPINESS=time_macros ccache g++ -shared -o HNBGW_Tests_part_2.so HNBGW_Tests_part_2.o env CCACHE_SLOPPINESS=time_macros ccache g++ -shared -o HNBGW_Tests_part_1.so HNBGW_Tests_part_1.o HNBGW_Tests_part_5.cc: In function ‘OCTETSTRING HNBGW__Tests::f__gen__one__compl__l3(const Compl3Type&, const MobileL3__CommonIE__Types::MobileIdentityLV_template&, const INTEGER&)’: HNBGW_Tests_part_5.cc:2130:1: warning: control reaches end of non-void function [-Wreturn-type] 2130 | } | ^ env CCACHE_SLOPPINESS=time_macros ccache g++ -shared -o HNBGW_Tests_part_5.so HNBGW_Tests_part_5.o env CCACHE_SLOPPINESS=time_macros ccache g++ -shared -o HNBGW_Tests_part_6.so HNBGW_Tests_part_6.o I want a fast dev cycle, and the ttcn dev cycle is slow: after a tiny edit, the CPU spools up and the fan goes for a whole while, and I get bored and irritated. When I'm on a train ttcn compilation drains the battery... My local workaround was to create a second file, like BSC_Tests_2.ttcn, with only my new test in it. Then compilation cycles are rapid. But that requires modifying all sorts of s/private/friend and even only moving the code is another annoyance. If I want to apply CR, I won't move it back and forth, so usually I end up with two copies and get confused. So my local workaround isn't working out very well. Why am I writing this here? Because I would like to request that we start subdividing our ttcn into smaller compilation units, not as my local workaround but permanently in our upstream. Please? ~N -- - Neels Hofmeyr <nhofmeyr(a)sysmocom.de> https://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Siemensstr. 26a * 10551 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

2 2

OsmoTRX+B205mini crashes when having another USB device on a different port
by JPichel 18 Jul '24

18 Jul '24

Hello everyone, I am experiencing problems when trying to run osmotrx with a b205mini and I connect another USB device to a different port on the machine. When I do this, osmotrx crashes instantly. Also, when I have the other device already plugged in when I start osmotrx, it takes ~20 seconds to crash. Sometimes it just crashes without giving a reason, like here: DLGLOBAL NOTICE Setting SCHED_RR priority 18 (cpu_sched_vty.c:471) DLGLOBAL NOTICE Setting SCHED_RR priority 18 (cpu_sched_vty.c:471) DLGLOBAL NOTICE Available via telnet 127.0.0.1 4237 (telnet_interface.c:88) DLCTRL NOTICE CTRL at 127.0.0.1 4236 (control_if.c:1024) [INFO] [UHD] linux; GNU C++ version 11.2.0; Boost_107400; UHD_4.1.0.5-3 DMAIN NOTICE -- Transceiver active with 1 channel(s) (osmo-trx.cpp:621) DLSTATS NOTICE Stats timer expire_count=7: We missed 6 timers (stats.c:169) DLGLOBAL NOTICE Stats timer expire_count=31: We missed 30 timers (rate_ctr.c:350) DTRXCTRL NOTICE Changing TSC from 0 to 7 (Transceiver.cpp:1032) DTRXCTRL NOTICE [chan=0] switching to TRXD version 1 (Transceiver.cpp:1059) DMAIN NOTICE Starting the transceiver (Transceiver.cpp:287) LLDTRXCLK NOTICE Sending CLOCK indications (Transceiver.cpp:1198) UDDEV ERROR No packet received, implementation timed-out (UHDDevice.cpp:782) DDEV FATAL UHD: Receive timed out (UHDDevice.cpp:786) DMAIN FATAL Receive error 0 (radioInterface.cpp:340) DTRXDUL FATAL Something went wrong in thread RxLower, requesting stop (Transceiver.cpp:1359) DMAIN NOTICE Shutting down transceiver... (osmo-trx.cpp:588) DMAIN NOTICE Stopping the transceiver (Transceiver.cpp:345) terminate called without an active exception Aborted And sometimes it reports an USB error and shows the talloc report: DMAIN NOTICE -- Transceiver active with 1 channel(s) (osmo-trx.cpp:621) DLSTATS NOTICE Stats timer expire_count=6: We missed 5 timers (stats.c:169) DLGLOBAL NOTICE Stats timer expire_count=26: We missed 25 timers (rate_ctr.c:350) DTRXCTRL NOTICE Changing TSC from 0 to 7 (Transceiver.cpp:1032) DTRXCTRL NOTICE [chan=0] switching to TRXD version 1 (Transceiver.cpp:1059) DMAIN NOTICE Starting the transceiver (Transceiver.cpp:287) DTRXCLK NOTICE Sending CLOCK indications (Transceiver.cpp:1198) LLUterminate called after throwing an instance of 'uhd::io_error' what(): EnvironmentError: IOError: usb rx6 transfer status: LIBUSB_TRANSFER_OVERFLOW signal 6 received talloc report on 'OsmoTRX' (total 8531 bytes in 29 blocks) rate_ctr.c:233 contains 1160 bytes in 1 blocks (ref 0) 0x559c72388720 trx_rate_ctr.cpp:343 contains 8 bytes in 1 blocks (ref 0) 0x559c723886b0 trx_rate_ctr.cpp:342 contains 40 bytes in 1 blocks (ref 0) 0x559c72389540 trx_rate_ctr.cpp:341 contains 32 bytes in 1 blocks (ref 0) 0x559c723895d0 telnet_connection contains 1 bytes in 1 blocks (ref 0) 0x559c723893d0 struct sched_vty_opts contains 72 bytes in 1 blocks (ref 0) 0x559c723489f0 logging contains 6197 bytes in 13 blocks (ref 0) 0x559c722c5d10 struct trx_ctx contains 1021 bytes in 8 blocks (ref 0) 0x559c722a0e80 msgb contains 0 bytes in 1 blocks (ref 0) 0x559c722c3ac0 full talloc report on 'OsmoTRX' (total 8531 bytes in 29 blocks) rate_ctr.c:233 contains 1160 bytes in 1 blocks (ref 0) 0x559c72388720 trx_rate_ctr.cpp:343 contains 8 bytes in 1 blocks (ref 0) 0x559c723886b0 trx_rate_ctr.cpp:342 contains 40 bytes in 1 blocks (ref 0) 0x559c72389540 trx_rate_ctr.cpp:341 contains 32 bytes in 1 blocks (ref 0) 0x559c723895d0 telnet_connection contains 1 bytes in 1 blocks (ref 0) 0x559c723893d0 struct sched_vty_opts contains 72 bytes in 1 blocks (ref 0) 0x559c723489f0 logging contains 6197 bytes in 13 blocks (ref 0) 0x559c722c5d10 vty_logp_doc_str contains 1377 bytes in 1 blocks (ref 0) 0x559c7231c040 vty_logp_cmd_str contains 260 bytes in 1 blocks (ref 0) 0x559c7231ba00 vty_log_level_doc_str contains 1170 bytes in 1 blocks (ref 0) 0x559c722ff430 vty_log_level_cmd_str contains 236 bytes in 1 blocks (ref 0) 0x559c722ff2d0 vty_log_level_doc_str contains 1305 bytes in 1 blocks (ref 0) 0x559c722fc610 vty_log_level_cmd_str contains 257 bytes in 1 blocks (ref 0) 0x559c722fc4a0 struct log_target contains 330 bytes in 3 blocks (ref 0) 0x559c7220c550 struct osmo_wqueue contains 96 bytes in 1 blocks (ref 0) 0x7ff689ff4090 struct log_category contains 74 bytes in 1 blocks (ref 0) 0x559c722c6290 struct log_info contains 1261 bytes in 3 blocks (ref 0) 0x559c722ac370 uint8_t contains 37 bytes in 1 blocks (ref 0) 0x559c722c6350 struct log_info_cat contains 1184 bytes in 1 blocks (ref 0) 0x559c722c5d80 struct trx_ctx contains 1021 bytes in 8 blocks (ref 0) 0x559c722a0e80 127.0.0.1 contains 10 bytes in 1 blocks (ref 0) 0x559c722c5c20 127.0.0.1 contains 10 bytes in 1 blocks (ref 0) 0x559c722c5ba0 struct cmd_element contains 122 bytes in 2 blocks (ref 0) 0x559c72369030 logging level lms (debug|info|notice|error|fatal) contains 50 bytes in 1 blocks (ref 0) 0x559c7236c1a0 utils.c:386 contains 405 bytes in 1 blocks (ref 0) 0x559c7225e5b0 utils.c:386 contains 65 bytes in 1 blocks (ref 0) 0x559c723524f0 contains 1 bytes in 1 blocks (ref 0) msgb contains 0 bytes in 1 blocks (ref 0) On the BTS side I see several messages of missed timers, but this is something I see also when I don't have the USB plugged in: <0006> scheduler_trx.c:489 GSM clock started, waiting for clock indications <0006> scheduler_trx.c:578 GSM clock skew: old fn=0, new fn=2555007 <0006> scheduler_trx.c:428 FN timer expire_count=4: We missed 3 timers <0006> scheduler_trx.c:606 We were 1 FN slower than TRX, compensated <0006> scheduler_trx.c:606 We were 1 FN slower than TRX, compensated <0006> scheduler_trx.c:428 FN timer expire_count=6: We missed 5 timers <0006> scheduler_trx.c:593 We were 1 FN faster than TRX, compensating <0006> scheduler_trx.c:606 We were 1 FN slower than TRX, compensated <0006> scheduler_trx.c:593 We were 1 FN faster than TRX, compensating <0006> scheduler_trx.c:606 We were 2 FN slower than TRX, compensated <0006> scheduler_trx.c:428 FN timer expire_count=7: We missed 6 timers <0006> scheduler_trx.c:593 We were 1 FN faster than TRX, compensating <0006> scheduler_trx.c:606 We were 1 FN slower than TRX, compensated <0006> scheduler_trx.c:593 We were 1 FN faster than TRX, compensating <0006> scheduler_trx.c:606 We were 1 FN slower than TRX, compensated <0006> scheduler_trx.c:428 FN timer expire_count=7: We missed 6 timers <0006> scheduler_trx.c:593 We were 1 FN faster than TRX, compensating <0006> scheduler_trx.c:606 We were 1 FN slower than TRX, compensated <0006> scheduler_trx.c:428 FN timer expire_count=7: We missed 6 timers <0006> scheduler_trx.c:435 No more clock from transceiver Does anyone know if this is a software or hardware problem? I am thinking maybe it is related to the power supply of the USB port, but I have no idea. I really need to have both devices connected at the same time. Any help or suggestion is appreciated, Jonathan

2 2

Planning to tag a new libosmocore release
by Oliver Smith 17 Jul '24

17 Jul '24

Hi all, we're planning to tag a new libosmocore release. If anyone has concerns about some APIs not being stable in master, then please speak up :) Best regards, Oliver -- - Oliver Smith <osmith(a)sysmocom.de> https://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Siemensstr. 26a * 10551 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

1 0

Annoucement of first tagged release of osmo-epdg
by Harald Welte 15 Jul '24

15 Jul '24

I'm happy to announce that [finally], the osmo-epdg development has reached its first release: 0.1.0. [Link to news item: https://osmocom.org/news/262] osmo-epdg[1] is combined ePDG and AAA to support Voice over Wifi (VoWiFi) calls. An ePDG allows a UE to connect over regular wireless networks to an IMS (untrusted non-3GPP network access). The combined ePDG/AAA is using a modified strongSwan[2] together with osmo-epdg[3], a daemon written in erlang/OTP. The osmo-epdg has been tested with open5gs as EPC and kamailio as IMS. To allow an easy setup of a fully working ePDG/epc/IMS there are ansible playbooks[4] which has been used to create our Hosted ePDG playground Thanks a lot to NLNet[5] for funding development of this project. Thanks also to the main developers of this project: Alexander "lynxis" Couzens and Pau "pespin" Espin Pedrol. Best regards, Harald [1] https://osmocom.org/projects/osmo-epdg/wiki [2] https://gitea.osmocom.org/ims-volte-vowifi/strongswan-epdg [3] https://gitea.osmocom.org/Erlang/osmo-epdg [4] https://gitea.osmocom.org/ims-volte-vowifi/ansible-prototype [5] https://nlnet.nl/project/Osmocom-ePDG/ -- - Harald Welte <laforge(a)osmocom.org> https://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

Cell coverage of OsmoBTS B205mini-i
by JPichel 11 Jul '24

11 Jul '24

Hi, I am using osmo-bts-trx with a B205-mini-i, using only CS services. I am currently running the following elements on Ubuntu 22.04, all built from source from the latest version: - osmo-trx-uhd - osmo-bts-trx - osmo-bsc - osmo-msc - osmo-hlr - osmo-mgw - osmo-stp - osmo-sip-connector I have been testing the range of the cell, and I can't seem to get more than around 50 meters, even when I transmit at ~21 dBm using a power amplifier at TX. I find this range too low, since I am used to getting 200-300 meters out of the box when running 4G and 5G networks with the same device, so I suspect I am not configuring the network correctly. I've tried looking at every parameter, so far I've only noticed improvements when setting the min-qual-* to the minimum values and ms_max_power to the maximum. These are my configs for TRX, BTS and BSC: OsmoTRX: ``` log stderr ... ! line vty no login ! cpu-sched policy rr 18 trx bind-ip 127.0.0.1 remote-ip 127.0.0.1 egprs disable tx-sps 4 rx-sps 4 clock-ref gpsdo chan 0 ``` ``` ! ! OsmoBTS () configuration saved from vty !! ! log stderr ... ! line vty no login ! phy 0 instance 0 osmotrx tx-attenuation 0 osmotrx rx-gain 50 osmotrx ip local 127.0.0.1 osmotrx ip remote 127.0.0.1 bts 0 band GSM900 ipa unit-id 1234 0 oml remote-ip 127.0.0.1 gsmtap-remote-host 127.0.0.1 gsmtap-sapi enable-all min-qual-rach -100 min-qual-norm -100 trx 0 phy 0 instance 0 nominal-tx-power 10 ``` ``` ! osmo-bsc default configuration ! (assumes STP to run on 127.0.0.1 and uses default point codes) ! log stderr logging color 1 logging print category-hex 0 logging print category 1 logging timestamp 0 logging print file basename last logging print level 1 e1_input e1_line 0 driver ipa network network country code 1 mobile network code 1 encryption a5 0 neci 1 paging any use tch 0 handover 0 handover algorithm 1 handover1 window rxlev averaging 10 handover1 window rxqual averaging 1 handover1 window rxlev neighbor averaging 10 handover1 power budget interval 6 handover1 power budget hysteresis 3 handover1 maximum distance 9999 ! T3212 is in units of 6min, so below we set 5 * 6 = 30min timer net T3212 5 mgw 0 remote-ip 127.0.0.1 remote-port 2427 local-port 2727 bts 0 type osmo-bts band GSM900 cell_identity 1234 location_area_code 0x0001 base_station_id_code 63 ms max power 40 !default: cell reselection hysteresis 4 cell reselection hysteresis 14 radio-link-timeout 32 channel allocator mode set-all ascending rxlev access min 0 rach tx integer 9 rach max transmission 7 channel-description attach 1 channel-description bs-pa-mfrms 5 channel-description bs-ag-blks-res 1 early-classmark-sending forbidden ipa unit-id 1234 0 oml ipa stream-id 255 line 0 codec-support fr gprs mode none trx 0 rf_locked 0 ! 945M DL/900M UL arfcn 50 nominal power 10 max_power_red 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 ms-power-control mode dyn-bts rxlev-thresh lower 0 upper 63 msc 0 allow-emergency allow amr-config 12_2k forbidden amr-config 10_2k forbidden amr-config 7_95k forbidden amr-config 7_40k forbidden amr-config 6_70k forbidden amr-config 5_90k allowed amr-config 5_15k forbidden amr-config 4_75k forbidden bsc mid-call-timeout 0 ``` You might notice I am using the gpsdo as the clock-ref. That's because I've also tried with a B210 with the internal GPSDO, but the results are the same. Thanks in advance, Jonathan Pichel

4 6

E1 to IP with iCE40 E1 USB interface
by Alina Androne 15 Jun '24

15 Jun '24

Hello, How can I utilize the iCE40 E1 USB adapter to transition from E1 to IP in a GSM network, connecting a physical Siemens BSC (which has a BTS connected) to OsmoMSC? Only the BTS and BSC are physical. I already have osmo-e1d installed. Should I use osmo-e1d or dahdi version for this transition? What would be the best approach to begin the process? Regards, Alina

5 10

how do I configure half-rate voice support
by cocfarabicoc＠gmail.com 14 Jun '24

14 Jun '24

I opened this issue for your support and suggestions. I have doing call testing with msisdn(Private network serving the local user). When osmo-bsc-cfg's timeslots are 0->CCCH+SDCCH4, rest 1-7 TCH/F, I can successfully connect 6 phones to each other. When I try to call between 7th and 8th phones, I get an error (from osmo-bts), "Resources unavailable,unspecified"(GSM48_CC_CAUSE_RESOURCE_UNAVAIL). Since each timeslot is allocated to 1 user, I receive an insufficient resource warning. My osmo-bsc-cfg; e1_input e1_line 0 driver ipa e1_line 0 port 0 no e1_line 0 keepalive cs7 instance 0 point-code 1.23.0 asp asp-clnt-msc-0 2905 0 m3ua remote-ip 127.0.0.1 sctp-role client sccp-address msc routing-indicator PC point-code 0.23.1 network network country code 901 mobile network code 75 encryption a5 1 3 neci 1 paging any use tch 0 handover 1 handover algorithm 1 handover1 power budget hysteresis 999 handover1 power budget interval 99 bts 0 type sysmobts band GSM900 cell_identity 0 location_area_code 23 base_station_id_code 63 ms max power 39 cell reselection hysteresis 14 rxlev access min 0 radio-link-timeout 64 penalty time 20 temporary offset 0 cell bar qualify 0 cell reselection offset 31 channel allocator ascending rach tx integer 14 rach max transmission 1 rach emergency call allowed 1 channel-description attach 1 channel-description bs-pa-mfrms 5 channel-description bs-ag-blks-res 2 no access-control-class-ramping access-control-class-ramping-step-interval 5 access-control-class-ramping-step-size 1 access-control-class-ramping-chan-load 71 89 early-classmark-sending allowed early-classmark-sending-3g allowed ipa unit-id 1800 0 oml ipa stream-id 255 line 0 neighbor-list mode manual-si5 codec-support fr hr efr amr amr tch-f modes 0 2 4 7 amr tch-f threshold ms 32 32 32 amr tch-f hysteresis ms 8 8 8 amr tch-f threshold bts 32 32 32 amr tch-f hysteresis bts 8 8 8 amr tch-f start-mode auto amr tch-h modes 0 2 4 amr tch-h threshold ms 32 32 amr tch-h hysteresis ms 8 8 amr tch-h threshold bts 32 32 amr tch-h hysteresis bts 8 8 amr tch-h start-mode auto gprs mode none ms-power-control mode static trx 0 rf_locked 0 arfcn 100 nominal power 23 max_power_red 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 msc 0 codec-list hr1 fr1 allow-emergency deny amr-config 12_2k forbidden amr-config 10_2k forbidden amr-config 7_95k forbidden amr-config 7_40k forbidden amr-config 6_70k forbidden amr-config 5_90k allowed amr-config 5_15k forbidden amr-config 4_75k forbidden amr-payload octet-aligned msc-addr msc asp-protocol m3ua lcls-mode disabled lcls-codec-mismatch forbidden mgw remote-ip 127.0.0.1 mgw remote-port 2427 bsc mid-call-timeout 0 cbc no remote-ip no listen-port end I wanted to set half-rate on one trx so that more phones could talk. On my first try, I get this warning("Assignment for this trans already started earlier"- from osmo-msc- function : msc_a_try_call_assignment) and I cannot make any calls. My bsc-cfg for TCH/H; e1_input e1_line 0 driver ipa e1_line 0 port 0 no e1_line 0 keepalive cs7 instance 0 point-code 1.23.0 asp asp-clnt-msc-0 2905 0 m3ua remote-ip 127.0.0.1 sctp-role client sccp-address msc routing-indicator PC point-code 0.23.1 network network country code 901 mobile network code 75 encryption a5 1 3 neci 1 paging any use tch 0 handover 1 handover algorithm 1 handover1 power budget hysteresis 999 handover1 power budget interval 99 bts 0 type sysmobts band GSM900 cell_identity 0 location_area_code 23 base_station_id_code 63 ms max power 39 cell reselection hysteresis 14 rxlev access min 0 radio-link-timeout 64 penalty time 20 temporary offset 0 cell bar qualify 0 cell reselection offset 31 channel allocator ascending rach tx integer 14 rach max transmission 1 rach emergency call allowed 1 channel-description attach 1 channel-description bs-pa-mfrms 5 channel-description bs-ag-blks-res 2 no access-control-class-ramping access-control-class-ramping-step-interval 5 access-control-class-ramping-step-size 1 access-control-class-ramping-chan-load 71 89 early-classmark-sending allowed early-classmark-sending-3g allowed ipa unit-id 1800 0 oml ipa stream-id 255 line 0 neighbor-list mode manual-si5 codec-support fr hr efr amr amr tch-f modes 0 2 4 7 amr tch-f threshold ms 32 32 32 amr tch-f hysteresis ms 8 8 8 amr tch-f threshold bts 32 32 32 amr tch-f hysteresis bts 8 8 8 amr tch-f start-mode auto amr tch-h modes 0 2 4 amr tch-h threshold ms 32 32 amr tch-h hysteresis ms 8 8 amr tch-h threshold bts 32 32 amr tch-h hysteresis bts 8 8 amr tch-h start-mode auto gprs mode none ms-power-control mode static trx 0 rf_locked 0 arfcn 100 nominal power 23 max_power_red 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 msc 0 codec-list hr1 fr1 allow-emergency deny amr-config 12_2k forbidden amr-config 10_2k forbidden amr-config 7_95k forbidden amr-config 7_40k forbidden amr-config 6_70k forbidden amr-config 5_90k allowed amr-config 5_15k forbidden amr-config 4_75k forbidden amr-payload octet-aligned msc-addr msc asp-protocol m3ua lcls-mode disabled lcls-codec-mismatch forbidden mgw remote-ip 127.0.0.1 mgw remote-port 2427 bsc mid-call-timeout 0 cbc no remote-ip no listen-port end What needs to be done to connect more than 6 phones? Am I making a mistake in the config for the half-rate setting? I am waiting for your suggestions and opinions.

2 1

Re: RFC: new type for NAS/EPS in gsmtap.h and question
by md jashin88 13 Jun '24

13 Jun '24

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC