You can subscribe to this list here.
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(13) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2012 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
(1) |
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
(2) |
Jul
(1) |
Aug
(10) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
2017 |
Jan
(2) |
Feb
|
Mar
|
Apr
(2) |
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(3) |
Nov
|
Dec
|
2018 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(3) |
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
2019 |
Jan
|
Feb
(2) |
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Mania M. <m.m...@gm...> - 2022-07-06 04:32:43
|
Hi I an looking to see what parameters should be set in Openbts_UMTS for emergency calls? |
From: Mania M. <m.m...@gm...> - 2022-07-05 05:31:45
|
Hi everyone Is it possible to see the captured packets from openbts_umts in the wireshark? If it is possible what config sould i use? |
From: Yasir M. <yas...@ya...> - 2022-02-01 04:47:18
|
Hi,I am new to OpenBTS-UMTS and I was wondering that whether there is an option of downgrading a connected user from UMTS to GSM by changing any parameter such as TAU, Reject Cause Message or any other parameter.Urgent help is required. Thanks. |
From: billy.peter <bil...@pr...> - 2019-05-02 08:39:56
|
Hello. I am using R-pi 3 model B and OS is raspbian stretch. while trying to build, i am unable to get liba53 successfully build, which inturn make openbts build impossible. I have manually install subscriber registry and liba53 but the script doesn't seem to pick manual installation. What necessary build script and MAKE file changes are required? What does this script line do "sayAndDo dpkg-buildpackage -us -uc"? Thanks Sent with [ProtonMail](https://protonmail.com) Secure Email. |
From: billy.peter <bil...@pr...> - 2019-04-23 05:25:16
|
Hello all, I am just working with openbts-umts logs to extract IMSI from it but the issue is that log file gets too large to be analyzed if you just let the system run for half an hour or little long. I want to know if there is any way to truncate the file or just let the code know to split the data into multiple log file after certain specified limit. I want the log files to be analyze-able/ parse-able. It's better if anyone of you suggest change other than code change because I am not a programmer or if its only changed through code then which file is to look for? Thanks and Regards Sent with [ProtonMail](https://protonmail.com) Secure Email. |
From: billy.peter <bil...@pr...> - 2019-02-08 05:55:30
|
Sent with [ProtonMail](https://protonmail.com) Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, February 8, 2019 10:52 AM, billy.peter <bil...@pr...> wrote: > Hey list, > > I am trying to deploy openbts-umts on my core I-7, but i am facing issue during $ make. Following is output of unsuccessful $ make > > collect2: error: ld returned 1 exit status > Makefile:538: recipe for target 'transceiver' failed > make[2]: *** [transceiver] Error 1 > make[2]: Leaving directory '/home/terminal/OpenBTS-UMTS/TransceiverUHD' > Makefile:550: recipe for target 'all-recursive' failed > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory '/home/terminal/OpenBTS-UMTS' > Makefile:481: recipe for target 'all' failed > make: *** [all] Error 2 > > Can anyone comprehend the error? I couldn't find anything helpful while I googled the issue. > Thanks > > Sent with [ProtonMail](https://protonmail.com) Secure Email. |
From: billy.peter <bil...@pr...> - 2019-02-08 05:52:57
|
Hey list, I am trying to deploy openbts-umts on my core I-7, but i am facing issue during $ make. Following is output of unsuccessful $ make collect2: error: ld returned 1 exit status Makefile:538: recipe for target 'transceiver' failed make[2]: *** [transceiver] Error 1 make[2]: Leaving directory '/home/terminal/OpenBTS-UMTS/TransceiverUHD' Makefile:550: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/terminal/OpenBTS-UMTS' Makefile:481: recipe for target 'all' failed make: *** [all] Error 2 Can anyone comprehend the error? I couldn't find anything helpful while I googled the issue. Thanks Sent with [ProtonMail](https://protonmail.com) Secure Email. |
From: john wu <joh...@ho...> - 2018-12-03 13:37:28
|
Hi All, i read the tutorial for how to configure openbts-umts. http://openbts.org/w/index.php?title=OpenBTS-UMTS#Setup it said configure sim card parameter like this: http://openbts.org/w/index.php?title=BuildInstallRun#Build_and_Install_the_Subscriber_Registry_and_Sipauthserve but it did not tell which one is ki value. so how to specify the ki value to Openbts-umts setting? |
From: john wu <joh...@ho...> - 2018-11-19 06:52:43
|
hi all, sorry for disturbing. I want to introduce an sdr that compatible with usrp b210. we develop an sdr according to b210 schematic. the performance and interface is the same as b210. it works fine with openbts, openbts-umts, openairinterface, srslte, gnuradio and so on. www.zhixun-wireless.top<http://www.zhixun-wireless.top/> provide SDR PA LNA duplexer Best Regards |
From: Sonny L. <son...@en...> - 2018-10-09 03:13:43
|
Hello Community, We are trying to setup a 3G network in our lab using OpenBTS-UMTS package from Range Networks. The installation also includes the OpenBTS dev package. I would like to ask if there is somebody in the community accomplished to worked on the 3G setup using the below. Pre-requisites: 1. ASN1C version 0.9.22 2. libzmq 3. git clone https://github.com/RangeNetworks/dev.git Lab Setup: * Ettus SDR B210 SingleTRX - Version Release 3.9.2 * Linux entropy 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux * Programmable SIM Card Configuration: OpenBTS> Control.LUR.AttachDetach 1 [default] Control.LUR.FailedRegistration.Message Your handset is not provisioned for this network. [default] Control.LUR.FailedRegistration.ShortCode 1000 [default] Control.LUR.NormalRegistration.Message (disabled) [default] Control.LUR.NormalRegistration.ShortCode 0000 [default] Control.LUR.OpenRegistration (disabled) [default] Control.LUR.OpenRegistration.Message Welcome to the test network. Your IMSI is [default] Control.LUR.OpenRegistration.ShortCode 101 [default] Control.LUR.QueryClassmark 0 [default] Control.LUR.QueryIMEI 0 [default] Control.LUR.SendTMSIs 0 [default] Control.LUR.UnprovisionedRejectCause 0x04 [default] Control.Reporting.TMSITable /var/run/OpenBTS-UMTS-TMSITable.db [default] Control.Reporting.TransactionTable /var/run/OpenBTS-UMTS-TransactionTable.db [default] Control.VEA 0 [default] GGSN.DNS (disabled) [default] GGSN.Firewall.Enable 1 [default] GGSN.IP.TossDuplicatePackets 0 [default] GGSN.MS.IP.Base 192.168.99.1 [default] GGSN.MS.IP.MaxCount 254 [default] GGSN.MS.IP.Route (disabled) [default] GGSN.ShellScript (disabled) [default] GPRS.Multislot.Max.Downlink 1 [default] GPRS.Multislot.Max.Uplink 1 [default] GPRS.NMO 1 [default] GSM.CCCH.CCCH-CONF 1 [default] GSM.CellSelection.CELL-RESELECT-HYSTERESIS 3 [default] GSM.CellSelection.NCCsPermitted 1 [default] GSM.CellSelection.NECI 1 [default] GSM.Identity.BSIC.BCC 2 [default] GSM.Identity.LAC 1000 [default] GSM.Identity.MCC 001 [default] GSM.Identity.MNC 01 [default] GSM.MaxSpeechLatency 2 [default] GSM.RACH.AC 0x0400 [default] GSM.RACH.MaxRetrans 1 [default] GSM.RACH.TxInteger 14 [default] GSM.RRLP.SEED.LATITUDE 37.777423 [default] GSM.RRLP.SEED.LONGITUDE -122.39807 [default] GSM.ShowCountry 0 [default] GSM.Timer.T3212 0 [default] Log.Alarms.Max 20 [default] Log.Level NOTICE [default] RTP.Range 98 [default] RTP.Start 16484 [default] SIP.DTMF.RFC2833 1 [default] SIP.DTMF.RFC2833.PayloadType 101 [default] SIP.DTMF.RFC2967 0 [default] SIP.Local.IP 127.0.0.1 [default] SIP.Local.Port 5062 [default] SIP.Proxy.Registration 127.0.0.1:5064 [default] SIP.Proxy.SMS 127.0.0.1:5063 [default] SIP.Proxy.Speech 127.0.0.1:5060 [default] SIP.SMSC smsc [default] SMS.FakeSrcSMSC 0000 [default] SMS.MIMEType application/vnd.3gpp.sms [default] SubscriberRegistry.A3A8 /OpenBTS/comp128 [default] SubscriberRegistry.Port 5064 [default] SubscriberRegistry.UpstreamServer (disabled) [default] SubscriberRegistry.db /var/lib/asterisk/sqlite3dir/sqlite3.db [default] TRX.IP 127.0.0.1 [default] UMTS.Identity.CI 10 [default] UMTS.Identity.LAC 132 [default] UMTS.Identity.MCC 001 [default] UMTS.Identity.MNC 01 [default] UMTS.Identity.URAI 100 [default] UMTS.PRACH.SF 32 [default] UMTS.Radio.ARFCNs 1 [default] UMTS.Radio.C0 3050 [default] UMTS.Radio.MaxExpectedDelaySpread 50 [default] UMTS.Radio.PowerManager.MaxAttenDB 10 [default] UMTS.Radio.PowerManager.MinAttenDB 0 [default] UMTS.SCCPCH.SF 64 [default] UMTS.Timer.T3212 30 [default] I was trying to authenticate the subscriber but failed. Please see below logs. Appreciate to provide any logs needed for this. Logs: OpenBTS> 42:31.3 UL_CCCH_MessageType_PR_rrcConnectionRequest UE#1 URNTI=5ee3 stIdleMode rbid=0 newState: 1 1 42:31.3 DL_CCCH RRC_Connection_Setup_Message message size=58 UE#1 URNTI=5ee3 stIdleMode rbid=0 newState: 2 1 ALERT 140609924806400 08:42:31.7 URLC.cpp:1755:rlcWriteLowSide: stateChange: before 0 0 after 0 0 42:31.9 UL_DCCH_MessageType_PR_rrcConnectionSetupComplete UE#1 URNTI=5ee3 stCELL_FACH rbid=2 42:32.2 UL_DCCH_MessageType_PR_initialDirectTransfer UE#1 URNTI=5ee3 stCELL_FACH rbid=3 42:32.2 UL GMM Msg: AttachRequest UE#1 URNTI=5ee3 stCELL_FACH imsi=515941111111116 PDP of 0 is 0, gmm = 80043d0, si = 8004c20 PDP of 5 is 0, gmm = 80043d0, si = 8004c20 42:32.2 DL_DCCH AuthenticationAndCipheringReq message size=25 UE#1 URNTI=5ee3 stCELL_FACH rbid=3 PDP of 0 is 0 Regards, Sonny Regards, [Entropy Logo]<http://www.entropy-solution.com><http://www.entropy-solution.com> Sonny Lafuente | Systems Engineer | Entropy Solution Philippines, Inc.<http://www.entropy-solution.com> Unit 2103 Antel Corporate Centre 121 Valero St. Salcedo Village Makati City 1227 (02) 8931781 | SMART: +63998 536 5206 | GLOBE: +63966 492 6180 | EMAIL: son...@en...<mailto:son...@en...> | su...@en...<mailto:su...@en...> Singapore*Philippines Products: Gridloc|Intelle|Hive|Lighthouse|eReach|ReachNet|ReachHQ|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. |
From: wu jo <joh...@ho...> - 2018-06-09 08:51:49
|
hi all, I want to introduce an sdr that compatible with usrp b210. we develop an sdr according to b210 schematic. the performance and interface is the same as b210. it works fine with openbts, openairinterface, srslte, gnuradio, uhd and so on. anyone need a b210 and can not afford its price can use this one instead. the price is 550$/pcs. now this device is in pre-sale the first 100 orders can have the discounted price 450$/pcs. i attach the picture of the sdr board. |
From: mazen a. <maz...@gm...> - 2018-05-12 16:29:52
|
Dears, I want to ask if any ready app used to scan UMTS from receiver side, as i know open BTS UMTS performs the decoding from BTS side , i want just to scan the cells arround me and return info about cell id , rx poer and so ... just decode the BCH channel. there is already gr gsm in for GSM which can do that but Is there for UMTS? If no app for that can anyone give me Tips and guides so that i use Open BTS UMTS as starting point for me and do that...thank you in Advance. |
From: Vladimir <www...@ma...> - 2018-04-19 12:05:30
|
Just in case anybody else gets stuck with this: in my case it was due to having built some other project that replaced the ans1c by newer version (0.9.24 instead of 0.9.23), and all the files in /usr/local/share/asn1c turned to be from 0.9.24. Solution: reinstall asn1c 0.9.23. Vladimir >Среда, 18 апреля 2018, 16:50 +03:00 от Vladimir via Openbts-umts-discuss < ope...@li... >: > >An update to this problem: > >> make[3]: *** No rule to make target 'o/ENUMERATED.o', needed by 'libRRCASN.la'. Stop. > >I have another machine where OpenUMTS has built successfully and I looked into ~/OpenBTS-UMTS/ASN/o directory there. I found out that all those files that are missing on the machine where I have error, correspond to asn1 standard files that are located in /usr/local/share/asn1c dirctory and just symlinked from OpenBTS-UMTS/ASN/o dir (ENUMERATED.c/.h, INTEGER.c/.h etc). > >Obviously, make does not find those symlinks in ASN/o and thus stops. But I cannot find the place in makefiles which is responsible for creating those links. Can anyone shed some light on the mechanism that should work here? > >Vladimir > > >>Среда, 18 апреля 2018, 16:37 +03:00 от Vladimir via Openbts-umts-discuss < ope...@li... >: >> >>Hello all, >> >>I have succeeded to build and run OpenBTS-UMTS on Ubuntu 16.10 with B210 board (UHD 3.10.2), but now cannot rebuild it after making changes to OpenBTS.cpp file. I see that some people also encounter the same error which is the following: >> >>make[3]: *** No rule to make target 'o/ENUMERATED.o', needed by 'libRRCASN.la'. Stop. >> >>The problem is in make procedure for ASN directory (btw, I'm using asn1c-0.9.23.tar.gz version of ASN1). For some reason it cannot build none of the ASN modules added to ASN_MODULE_HEADERS and ASN_MODULE_SOURCES lists later in ASN/makefile (around the line #4729): >> >>ASN_MODULE_HEADERS+=BOOLEAN.h >>ASN_MODULE_SOURCES+=BOOLEAN.c >>ASN_MODULE_HEADERS+=ENUMERATED.h >>ASN_MODULE_SOURCES+=ENUMERATED.c >>...etc... >> >>All modules that are contained in initial assignments to those lists are successfully built, but not these latters. >> >>Most embarassing is that I tried to reinstall all OpenBTS-UMTS sources from scratch (according to this guide http://openbts.org/w/index.php?title=OpenBTS-UMTS#Build.2C_Install.2C_Setup.2C_and_Run_Instructions , removing the whole base directory and git-cloning it again) and it still stops at the same point in the build! >> >>Can someone who encountered this kind of problem share how to overcome it? Or, what is the known working sequence to make OpenBTS-UMTS after modifications? >> >>Thanks, >>Vladimir >>------------------------------------------------------------------------------ >>Check out the vibrant tech community on one of the world's most >>engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>_______________________________________________ >>Openbts-umts-discuss mailing list >>Ope...@li... >>https://lists.sourceforge.net/lists/listinfo/openbts-umts-discuss > > > >------------------------------------------------------------------------------ >Check out the vibrant tech community on one of the world's most >engaging tech sites, Slashdot.org! http://sdm.link/slashdot >_______________________________________________ >Openbts-umts-discuss mailing list >Ope...@li... >https://lists.sourceforge.net/lists/listinfo/openbts-umts-discuss |
From: Vladimir <www...@ma...> - 2018-04-18 13:50:12
|
An update to this problem: > make[3]: *** No rule to make target 'o/ENUMERATED.o', needed by 'libRRCASN.la'. Stop. I have another machine where OpenUMTS has built successfully and I looked into ~/OpenBTS-UMTS/ASN/o directory there. I found out that all those files that are missing on the machine where I have error, correspond to asn1 standard files that are located in /usr/local/share/asn1c dirctory and just symlinked from OpenBTS-UMTS/ASN/o dir (ENUMERATED.c/.h, INTEGER.c/.h etc). Obviously, make does not find those symlinks in ASN/o and thus stops. But I cannot find the place in makefiles which is responsible for creating those links. Can anyone shed some light on the mechanism that should work here? Vladimir >Среда, 18 апреля 2018, 16:37 +03:00 от Vladimir via Openbts-umts-discuss <ope...@li...>: > >Hello all, > >I have succeeded to build and run OpenBTS-UMTS on Ubuntu 16.10 with B210 board (UHD 3.10.2), but now cannot rebuild it after making changes to OpenBTS.cpp file. I see that some people also encounter the same error which is the following: > >make[3]: *** No rule to make target 'o/ENUMERATED.o', needed by 'libRRCASN.la'. Stop. > >The problem is in make procedure for ASN directory (btw, I'm using asn1c-0.9.23.tar.gz version of ASN1). For some reason it cannot build none of the ASN modules added to ASN_MODULE_HEADERS and ASN_MODULE_SOURCES lists later in ASN/makefile (around the line #4729): > >ASN_MODULE_HEADERS+=BOOLEAN.h >ASN_MODULE_SOURCES+=BOOLEAN.c >ASN_MODULE_HEADERS+=ENUMERATED.h >ASN_MODULE_SOURCES+=ENUMERATED.c >...etc... > >All modules that are contained in initial assignments to those lists are successfully built, but not these latters. > >Most embarassing is that I tried to reinstall all OpenBTS-UMTS sources from scratch (according to this guide http://openbts.org/w/index.php?title=OpenBTS-UMTS#Build.2C_Install.2C_Setup.2C_and_Run_Instructions , removing the whole base directory and git-cloning it again) and it still stops at the same point in the build! > >Can someone who encountered this kind of problem share how to overcome it? Or, what is the known working sequence to make OpenBTS-UMTS after modifications? > >Thanks, >Vladimir >------------------------------------------------------------------------------ >Check out the vibrant tech community on one of the world's most >engaging tech sites, Slashdot.org! http://sdm.link/slashdot >_______________________________________________ >Openbts-umts-discuss mailing list >Ope...@li... >https://lists.sourceforge.net/lists/listinfo/openbts-umts-discuss |
From: Vladimir <www...@ma...> - 2018-04-18 13:37:28
|
Hello all, I have succeeded to build and run OpenBTS-UMTS on Ubuntu 16.10 with B210 board (UHD 3.10.2), but now cannot rebuild it after making changes to OpenBTS.cpp file. I see that some people also encounter the same error which is the following: make[3]: *** No rule to make target 'o/ENUMERATED.o', needed by 'libRRCASN.la'. Stop. The problem is in make procedure for ASN directory (btw, I'm using asn1c-0.9.23.tar.gz version of ASN1). For some reason it cannot build none of the ASN modules added to ASN_MODULE_HEADERS and ASN_MODULE_SOURCES lists later in ASN/makefile (around the line #4729): ASN_MODULE_HEADERS+=BOOLEAN.h ASN_MODULE_SOURCES+=BOOLEAN.c ASN_MODULE_HEADERS+=ENUMERATED.h ASN_MODULE_SOURCES+=ENUMERATED.c ...etc... All modules that are contained in initial assignments to those lists are successfully built, but not these latters. Most embarassing is that I tried to reinstall all OpenBTS-UMTS sources from scratch (according to this guide http://openbts.org/w/index.php?title=OpenBTS-UMTS#Build.2C_Install.2C_Setup.2C_and_Run_Instructions, removing the whole base directory and git-cloning it again) and it still stops at the same point in the build! Can someone who encountered this kind of problem share how to overcome it? Or, what is the known working sequence to make OpenBTS-UMTS after modifications? Thanks, Vladimir |
From: JOHN E. B. T. <jeb...@uq...> - 2018-03-12 16:20:47
|
Hello. I'm trying to set up a UMTS network with a USRP N210 which has an Ethernet connection with the pc, I already managed to register the sim, however it is not assigned an IP address. Using the sgsn list command I get this: OpenBTS-UMTS> sgsn list GMM Context: imsi=00101010123456799 ptmsi=0x9a001 tlli=0xc009a001 state=GmmRegisteredNormal age=20 idle=20 UE#1 URNTI=a783 stCELL_FACH IPs=none and in the OpenBTS console: 17:32.4 UL SM Msg: ActivatePDPContextContextRequest UE#1 URNTI=a783 stCELL_FACH imsi=001010123456799 kbps: 0, ops: 0 configDchPS: UL SF=4 RF=1x9600=9600 pb=16 turbo=1 maxprecoded=3180 tb=8x380=3040 coded=9132 configDchPS: DL SF=8 RF=1x9120=9120 pb=16 turbo=1 maxprecoded=3020 tb=8x340=2720 coded=8172 PDU sizes: 42 42 PDU sizes: 42 42 PDU sizes: 42 42 Opening DCH 17:32.4 DL_DCCH RRC Radio Bearer Setup Message message size=127 UE#1 URNTI=a783 stCELL_FACH rbid=2 ALERT 3030297408 11:17:32.6 URLC. cpp: 1755: rlcWriteLowSide: stateChange: before 6 7 after 6 7 7 17:32.8 UL_DCCH_MessageType_PR_radioBearerSetupFailure UE#1 URNTI=a783 stCELL_FACH rbid=2 unhooking DCH 8dbacf8 waiting to remove.... removed What I need is to connect the user with an ftp server installed on the same pc. I hope and can help me, thank you |
From: Access L. <lab...@gm...> - 2018-01-25 04:31:00
|
Hi List, Recently i have successfully build and run OpenBTS-UMTS, by following the guide from the wiki page and some external resources. I have some problems with the connection process from handset to BTS. I'm using USRP B200 with 2 antenna (VERT900) connected to Tx/Rx and Rx port, at my first attempt i've got the following errors: ALERT 140679777597184 15:29:02.9 RadioInterface.cpp:341:pullBuffer: Overpower detected on receive input I've also seen that the BTS receive attach request from the handset: 29:02.9 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=426d stCELL_FACH rbid=3 29:02.9 UL GMM Msg: AttachRequest UE#1 URNTI=426d stCELL_FACH imsi=901700000013840 PDP of 0 is 0, gmm = 40003280, si = 40004d70 PDP of 5 is 0, gmm = 40003280, si = 40004d70 but the previous alert always shown up and the handset failed to connect. I try to reduce the rxgain by typing the following commands: OpenBTS-UMTS> rxgain 47 current RX gain is 57 dB Invalid new value for RX gain. It must be in range () bad argument(s) On my second attempts, i unplug the antenna at Rx port, so i'm only using 1 antenna at Tx/Rx port and i move more further from the BTS. The "Overpower detected on receive input" alarm, doesn't show up anymore but the phone still failed to connect, here are the logs from the OpenBTS-UMTS terminal: OpenBTS> ALERT 139844615943936 09:58:51.8 URRC.cpp:615:findUeByAsnId: no match ptmsi=0x0 raimatch=0 findHandlebyPTmsi-urnti=0x0 58:51.8 UL_CCCH_MessageType_PR_rrcConnectionRequest (new UE) UE#1 URNTI=4755 stIdleMode rbid=0 newState: 1 1 58:51.8 DL_CCCH RRC_Connection_Setup_Message message size=58 UE#1 URNTI=4755 stIdleMode rbid=0 newState: 2 1 ALERT 139844615943936 09:58:52.7 URLC.cpp:1755:rlcWriteLowSide: stateChange: before 0 0 after 0 0 58:53.3 UL_DCCH_MessageType_PR_rrcConnectionSetupComplete UE#1 URNTI=4755 stCELL_FACH rbid=2 58:54.7 UL_DCCH_MessageType_PR_initialDirectTransfer UE#1 URNTI=4755 stCELL_FACH rbid=3 58:54.7 UL GMM Msg: AttachRequest UE#1 URNTI=4755 stCELL_FACH PDP of 0 is 0, gmm = dc005300, si = dc004440 PDP of 5 is 0, gmm = dc005300, si = dc004440 59:07.7 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=4755 stCELL_FACH rbid=3 59:07.7 UL GMM Msg: AttachRequest UE#1 URNTI=4755 stCELL_FACH imsi=901700000013840 PDP of 0 is 0, gmm = dc005300, si = dc004440 PDP of 5 is 0, gmm = dc005300, si = dc004440 59:22.5 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=4755 stCELL_FACH rbid=3 59:22.5 UL GMM Msg: AttachRequest UE#1 URNTI=4755 stCELL_FACH imsi=901700000013840 PDP of 0 is 0, gmm = dc005300, si = dc004440 PDP of 5 is 0, gmm = dc005300, si = dc004440 59:42.8 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=4755 stCELL_FACH rbid=3 59:42.8 UL GMM Msg: AttachRequest UE#1 URNTI=4755 stCELL_FACH imsi=901700000013840 PDP of 0 is 0, gmm = dc005300, si = dc004440 PDP of 5 is 0, gmm = dc005300, si = dc004440 59:48.2 UL_DCCH_MessageType_PR_signallingConnectionReleaseIndication UE#1 URNTI=4755 stCELL_FACH rbid=2 59:48.2 DL_DCCH RRC_Connection_Release_Message message size=3 UE#1 URNTI=4755 stCELL_FACH rbid=2 59:49.5 UL_DCCH_MessageType_PR_rrcConnectionReleaseComplete UE#1 URNTI=4755 stCELL_FACH rbid=2 newState: 1 2 00:12.9 UL_CCCH_MessageType_PR_rrcConnectionRequest UE#1 URNTI=4755 stIdleMode rbid=0 newState: 1 1 00:12.9 DL_CCCH RRC_Connection_Setup_Message message size=58 UE#1 URNTI=4755 stIdleMode rbid=0 newState: 2 1 ALERT 139844615943936 10:00:13.5 URLC.cpp:1755:rlcWriteLowSide: stateChange: before 0 0 after 0 0 00:14.0 UL_DCCH_MessageType_PR_rrcConnectionSetupComplete UE#1 URNTI=4755 stCELL_FACH rbid=2 00:15.0 UL_DCCH_MessageType_PR_initialDirectTransfer UE#1 URNTI=4755 stCELL_FACH rbid=3 00:15.0 UL GMM Msg: AttachRequest UE#1 URNTI=4755 stCELL_FACH imsi=901700000013840 PDP of 0 is 0, gmm = dc005300, si = dc004440 PDP of 5 is 0, gmm = dc005300, si = dc004440 00:28.6 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=4755 stCELL_FACH rbid=3 00:28.6 UL GMM Msg: AttachRequest UE#1 URNTI=4755 stCELL_FACH imsi=901700000013840 PDP of 0 is 0, gmm = dc005300, si = dc004440 PDP of 5 is 0, gmm = dc005300, si = dc004440 00:43.6 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=4755 stCELL_FACH rbid=3 00:43.6 UL GMM Msg: AttachRequest UE#1 URNTI=4755 stCELL_FACH imsi=901700000013840 PDP of 0 is 0, gmm = dc005300, si = dc004440 PDP of 5 is 0, gmm = dc005300, si = dc004440 00:58.6 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=4755 stCELL_FACH rbid=3 00:58.6 UL GMM Msg: AttachRequest UE#1 URNTI=4755 stCELL_FACH imsi=901700000013840 PDP of 0 is 0, gmm = dc005300, si = dc004440 PDP of 5 is 0, gmm = dc005300, si = dc004440 01:13.6 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=4755 stCELL_FACH rbid=3 01:13.6 UL GMM Msg: AttachRequest UE#1 URNTI=4755 stCELL_FACH imsi=901700000013840 PDP of 0 is 0, gmm = dc005300, si = dc004440 PDP of 5 is 0, gmm = dc005300, si = dc004440 01:49.7 UL_DCCH_MessageType_PR_signallingConnectionReleaseIndication UE#1 URNTI=4755 stCELL_FACH rbid=2 01:49.7 DL_DCCH RRC_Connection_Release_Message message size=3 UE#1 URNTI=4755 stCELL_FACH rbid=2 01:50.7 UL_DCCH_MessageType_PR_rrcConnectionReleaseComplete UE#1 URNTI=4755 stCELL_FACH rbid=2 newState: 1 2 01:51.7 UL_CCCH_MessageType_PR_rrcConnectionRequest UE#1 URNTI=4755 stIdleMode rbid=0 newState: 1 1 01:51.7 DL_CCCH RRC_Connection_Setup_Message message size=58 UE#1 URNTI=4755 stIdleMode rbid=0 newState: 2 1 ALERT 139844615943936 10:01:52.4 URLC.cpp:1755:rlcWriteLowSide: stateChange: before 0 0 after 0 0 01:53.0 UL_DCCH_MessageType_PR_rrcConnectionSetupComplete UE#1 URNTI=4755 stCELL_FACH rbid=2 01:56.4 UL_DCCH_MessageType_PR_initialDirectTransfer UE#1 URNTI=4755 stCELL_FACH rbid=3 01:56.4 UL GMM Msg: AttachRequest UE#1 URNTI=4755 stCELL_FACH imsi=901700000013840 PDP of 0 is 0, gmm = dc005300, si = dc004440 PDP of 5 is 0, gmm = dc005300, si = dc004440 02:07.3 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=4755 stCELL_FACH rbid=3 02:07.3 UL GMM Msg: AttachRequest UE#1 URNTI=4755 stCELL_FACH imsi=901700000013840 PDP of 0 is 0, gmm = dc005300, si = dc004440 PDP of 5 is 0, gmm = dc005300, si = dc004440 02:22.3 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=4755 stCELL_FACH rbid=3 02:22.3 UL GMM Msg: AttachRequest UE#1 URNTI=4755 stCELL_FACH imsi=901700000013840 PDP of 0 is 0, gmm = dc005300, si = dc004440 PDP of 5 is 0, gmm = dc005300, si = dc004440 02:37.3 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=4755 stCELL_FACH rbid=3 02:37.3 UL GMM Msg: AttachRequest UE#1 URNTI=4755 stCELL_FACH imsi=901700000013840 PDP of 0 is 0, gmm = dc005300, si = dc004440 PDP of 5 is 0, gmm = dc005300, si = dc004440 02:52.3 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=4755 stCELL_FACH rbid=3 02:52.3 UL GMM Msg: AttachRequest UE#1 URNTI=4755 stCELL_FACH imsi=901700000013840 PDP of 0 is 0, gmm = dc005300, si = dc004440 PDP of 5 is 0, gmm = dc005300, si = dc004440 03:07.2 UL_DCCH_MessageType_PR_signallingConnectionReleaseIndication UE#1 URNTI=4755 stCELL_FACH rbid=2 03:07.2 DL_DCCH RRC_Connection_Release_Message message size=3 UE#1 URNTI=4755 stCELL_FACH rbid=2 03:08.1 UL_DCCH_MessageType_PR_rrcConnectionReleaseComplete UE#1 URNTI=4755 stCELL_FACH rbid=2 newState: 1 2 03:23.3 UL_CCCH_MessageType_PR_rrcConnectionRequest UE#1 URNTI=4755 stIdleMode rbid=0 newState: 1 1 03:23.3 DL_CCCH RRC_Connection_Setup_Message message size=58 UE#1 URNTI=4755 stIdleMode rbid=0 newState: 2 1 ALERT 139844615943936 10:03:23.9 URLC.cpp:1755:rlcWriteLowSide: stateChange: before 0 0 after 0 0 03:24.3 UL_DCCH_MessageType_PR_rrcConnectionSetupComplete UE#1 URNTI=4755 stCELL_FACH rbid=2 03:25.2 UL_DCCH_MessageType_PR_initialDirectTransfer UE#1 URNTI=4755 stCELL_FACH rbid=3 03:25.2 UL GMM Msg: AttachRequest UE#1 URNTI=4755 stCELL_FACH imsi=901700000013840 PDP of 0 is 0, gmm = dc005300, si = dc004440 PDP of 5 is 0, gmm = dc005300, si = dc004440 03:38.8 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=4755 stCELL_FACH rbid=3 03:38.8 UL GMM Msg: AttachRequest UE#1 URNTI=4755 stCELL_FACH imsi=901700000013840 PDP of 0 is 0, gmm = dc005300, si = dc004440 PDP of 5 is 0, gmm = dc005300, si = dc004440 03:55.5 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=4755 stCELL_FACH rbid=3 03:55.5 UL GMM Msg: AttachRequest UE#1 URNTI=4755 stCELL_FACH imsi=901700000013840 PDP of 0 is 0, gmm = dc005300, si = dc004440 PDP of 5 is 0, gmm = dc005300, si = dc004440 04:09.0 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=4755 stCELL_FACH rbid=3 04:09.0 UL GMM Msg: AttachRequest UE#1 URNTI=4755 stCELL_FACH imsi=901700000013840 PDP of 0 is 0, gmm = dc005300, si = dc004440 PDP of 5 is 0, gmm = dc005300, si = dc004440 04:30.0 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=4755 stCELL_FACH rbid=3 04:30.0 UL GMM Msg: AttachRequest UE#1 URNTI=4755 stCELL_FACH imsi=901700000013840 PDP of 0 is 0, gmm = dc005300, si = dc004440 PDP of 5 is 0, gmm = dc005300, si = dc004440 05:20.1 UL_DCCH_MessageType_PR_signallingConnectionReleaseIndication UE#1 URNTI=4755 stCELL_FACH rbid=2 05:20.1 DL_DCCH RRC_Connection_Release_Message message size=3 UE#1 URNTI=4755 stCELL_FACH rbid=2 05:22.3 UL_DCCH_MessageType_PR_rrcConnectionReleaseComplete UE#1 URNTI=4755 stCELL_FACH rbid=2 newState: 1 2 My questions for the above conditions are: 1. What command should i use to reduce rxgain in OpenBTS-UMTSCLI? 2. Is there any settings that i should enable to make the phone connected to the BTS? I'm using programmable sim card and already add subscriber using nmcli.py command. Could someone please give some explanation regarding the above conditions? Thanks & Regards, Erik |
From: wu jo <joh...@ho...> - 2017-10-31 13:56:37
|
Hi all, i test with an iphone which sometimes can detect the umts nodeb and somtimes not. i don't know if the signal is not stable. i use manual search network in the phone. has anyone tested this software can work stable? i know in openbts 2g when there is no signal need to send it will send idle burst. i don't know if this is also implemented in umts? |
From: wu jo <joh...@ho...> - 2017-10-26 14:16:06
|
Hi all, i make openbts umts according to the steps in: http://openbts.org/w/index.php?title=OpenBTS-UMTS but meet this error : No rule to make target `o/ENUMERATED.o', needed by `libRRCASN.la'. Stop. how to fix this problem? |
From: wu jo <joh...@ho...> - 2017-10-26 02:14:16
|
Hi all, i find in openbts umts source the sendRrcConnectionSetup did not assign the uplink radio resouce to UE. the source is commented by // These IEs are all skipped, needed only for DCH: so when to assign DCH to UE during a location update procedure? shouldn't assign DCH to the UE once the UE init the location update procedure by sending rrc connect request? |
From: Yile Ku <sti...@gm...> - 2017-08-04 01:00:20
|
We want to build a GSM and UMTS basestation. We want to run at European frequencies for both GSM and UMTS for testing reasons. We are going to run GSM at the 900 Mhz frequencies, but we are trying to figure out what we should run UMTS at. The UMTS bands are 900 and 2100 Mhz. Can we run both GSM and UMTS in the 900 Mhz bands simultaneously, or do we need to separate them and run GSM at 900 and UMTS at 2100 if we want to run them simultaneously? Thanks, Y- |
From: Dominique K. <ked...@gm...> - 2017-05-29 22:35:16
|
Hi, I am currently trying to run Openbts-umts but have below error message. Any help will be much appreciated. Thank you in advance. > OpenBTS, OpenBTS-UMTS > Copyright 2008, 2009, 2010 Free Software Foundation, Inc. > Copyright 2010 Kestrel Signal Processing, Inc. > Copyright 2011, 2012, 2013, 2014 Range Networks, Inc. > Release 1.0-master P formal build date 2017-05-23T17:37:36 7ab6471a4e CommonLibs:7ab6471a4e > "OpenBTS" is a trademark of Range Networks, Inc. > "OpenBTS-UMTS" is a trademark of Range Networks, Inc. > > Contributors: > Range Networks, Inc.: > David Burgess, Harvind Samra, Donald Kirker, Doug Brown, Pat Thompson, Michael Iedema > Kestrel Signal Processing, Inc.: > David Burgess, Harvind Samra, Raffi Sevlian, Roshan Baliga > GNU Radio: > Johnathan Corgan > Others: > Anne Kwong, Jacob Appelbaum, Joshua Lackey, Alon Levy > Alexander Chemeris, Alberto Escudero-Pascual > Incorporated GPL libraries and components: > libosip2 (LGPL), liportp2 (LGPL) > > This program comes with ABSOLUTELY NO WARRANTY. > > Use of this software may be subject to other legal restrictions, > including patent licsensing and radio spectrum licensing. > All users of this software are expected to comply with applicable > regulations and laws. See the LEGAL file in the source code for > more information. > > ALERT 140630392444736 19:40:11.7 OpenBTS-UMTS.cpp:166:main: OpenBTS-UMTS (re)starting, ver 1.0-master build date May 23 2017 > 1495906811.707257 140630392444736: > Starting the system... > TBSIZE: 260 > RACH radioFrameSize=1200 total=1200 tbsize=256 > TBSIZE: 360 > FACH SF=64 radioFrameSize=1080 total=1080 tbsize=360 > > TBSIZE: 260 > RACH radioFrameSize=1200 total=1200 tbsize=256 > TBSIZE: 360 > FACH SF=64 radioFrameSize=1080 total=1080 tbsize=360 > > RACH TFS: mPresent=2 mMaxTfSize=0 mMaxTbSize=0 multiplexed=1 mTTI=10 mTypeOfChannelCoding=2 mRateMatchingAttribute=256 mCRCSize=16 TF( mTBSize=256 mNumTB=1) TF( mTBSize=256 mNumTB=2) > FACH TFS: mPresent=2 mMaxTfSize=0 mMaxTbSize=0 multiplexed=1 mTTI=10 mTypeOfChannelCoding=2 mRateMatchingAttribute=256 mCRCSize=12 TF( mTBSize=360 mNumTB=0) TF( mTBSize=360 mNumTB=1) > chReserve(64,2) > ALERT 140630392444736 19:40:11.7 UMTSPhCh.cpp:654:chConflict: Attempt to reserve channel: sf=64 chcode=2 which conflicts with reserved channel: sf=32 chcode=1 > chReserve(256,2) > ALERT 140630392444736 19:40:11.7 UMTSPhCh.cpp:654:chConflict: Attempt to reserve channel: sf=256 chcode=2 which conflicts with reserved channel: sf=128 chcode=1 > chReserve(64,3) > ALERT 140630392444736 19:40:11.7 UMTSPhCh.cpp:654:chConflict: Attempt to reserve channel: sf=64 chcode=3 which conflicts with reserved channel: sf=32 chcode=1 > chReserve(256,4) > ALERT 140630392444736 19:40:11.7 UMTSPhCh.cpp:654:chConflict: Attempt to reserve channel: sf=256 chcode=4 which conflicts with reserved channel: sf=128 chcode=2 > chReserve(64,2) > ALERT 140630392444736 19:40:11.7 UMTSPhCh.cpp:654:chConflict: Attempt to reserve channel: sf=64 chcode=2 which conflicts with reserved channel: sf=32 chcode=1 > Dumping SIB5... > SysInfoType5 ::= { > sib6indicator: FALSE > pich-PowerOffset: -10 > modeSpecificInfo: fdd ::= { > aich-PowerOffset: -10 > } > primaryCCPCH-Info: fdd ::= { > tx-DiversityIndicator: FALSE > } > prach-SystemInformationList: PRACH-SystemInformationList ::= { > PRACH-SystemInformation ::= { > prach-RACH-Info: PRACH-RACH-Info ::= { > modeSpecificInfo: fdd ::= { > availableSignatures: 20 00 > availableSF: 0 (sfpr32) > preambleScramblingCodeWordNumber: 0 > puncturingLimit: 15 (pl1) > availableSubChannelNumbers: 00 20 > } > } > transportChannelIdentity: 3 > rach-TransportFormatSet: CommonTransChTFS ::= { > tti: CommonDynamicTF-InfoList ::= { > CommonDynamicTF-Info ::= { > rlc-Size: fdd ::= { > octetModeRLC-SizeInfoType2: 26 > } > numberOfTbSizeList: numberOfTbSizeList ::= { > <present> > 2 > } > logicalChannelList: <present> > } > } > semistaticTF-Information: SemistaticTF-Information ::= { > channelCodingType: 0 (half) > rateMatchingAttribute: 256 > crc-Size: 3 (crc16) > } > } > rach-TFCS: TFCS-ReconfAdd ::= { > ctfcSize: ctfc2Bit ::= { > TFCS-ReconfAdd-foo2 ::= { > ctfc2: 0 > powerOffsetInformation: PowerOffsetInformation ::= { > gainFactorInformation: SignalledGainFactors ::= { > modeSpecificInfo: fdd ::= { > gainFactorBetaC: 15 > } > gainFactorBetaD: 15 > } > powerOffsetPp-m: 2 > } > } > TFCS-ReconfAdd-foo2 ::= { > ctfc2: 1 > powerOffsetInformation: PowerOffsetInformation ::= { > gainFactorInformation: SignalledGainFactors ::= { > modeSpecificInfo: fdd ::= { > gainFactorBetaC: 15 > } > gainFactorBetaD: 15 > } > powerOffsetPp-m: 2 > } > } > } > } > prach-Partitioning: fdd ::= { > ASCSetting-FDD ::= { > accessServiceClass-FDD: AccessServiceClass-FDD ::= { > availableSignatureStartIndex: 0 > availableSignatureEndIndex: 0 > assignedSubChannelNumber: F0 > } > } > } > ac-To-ASC-MappingTable: AC-To-ASC-MappingTable ::= { > 0 > 0 > 0 > 0 > 0 > 0 > 0 > } > modeSpecificInfo: fdd ::= { > primaryCPICH-TX-Power: 10 > constantValue: -10 > prach-PowerOffset: PRACH-PowerOffset ::= { > powerRampStep: 1 > preambleRetransMax: 64 > } > rach-TransmissionParameters: RACH-TransmissionParameters ::= { > mmax: 32 > nb01Min: 0 > nb01Max: 50 > } > aich-Info: AICH-Info ::= { > channelisationCode256: 2 > sttd-Indicator: FALSE > aich-TransmissionTiming: 1 (e1) > } > } > } > } > sCCPCH-SystemInformationList: SCCPCH-SystemInformationList ::= { > SCCPCH-SystemInformation ::= { > secondaryCCPCH-Info: SecondaryCCPCH-Info ::= { > modeSpecificInfo: fdd ::= { > dummy1: 0 (mayBeUsed) > sttd-Indicator: FALSE > sf-AndCodeNumber: 3 > pilotSymbolExistence: FALSE > tfci-Existence: TRUE > positionFixedOrFlexible: 0 (fixed) > timingOffset: 0 > } > } > tfcs: TFCS-ReconfAdd ::= { > ctfcSize: ctfc2Bit ::= { > TFCS-ReconfAdd-foo2 ::= { > ctfc2: 0 > } > TFCS-ReconfAdd-foo2 ::= { > ctfc2: 1 > } > } > } > fach-PCH-InformationList: FACH-PCH-InformationList ::= { > FACH-PCH-Information ::= { > transportFormatSet: CommonTransChTFS ::= { > tti: CommonDynamicTF-InfoList ::= { > CommonDynamicTF-Info ::= { > rlc-Size: fdd ::= { > octetModeRLC-SizeInfoType2: 3 > } > numberOfTbSizeList: numberOfTbSizeList ::= { > <present> > <present> > } > logicalChannelList: <present> > } > } > semistaticTF-Information: SemistaticTF-Information ::= { > channelCodingType: 0 (half) > rateMatchingAttribute: 256 > crc-Size: 2 (crc12) > } > } > transportChannelIdentity: 1 > ctch-Indicator: FALSE > } > } > pich-Info: fdd ::= { > channelisationCode256: 4 > pi-CountPerFrame: 0 (e18) > sttd-Indicator: FALSE > } > } > SCCPCH-SystemInformation ::= { > secondaryCCPCH-Info: SecondaryCCPCH-Info ::= { > modeSpecificInfo: fdd ::= { > dummy1: 0 (mayBeUsed) > sttd-Indicator: FALSE > sf-AndCodeNumber: 2 > pilotSymbolExistence: FALSE > tfci-Existence: TRUE > positionFixedOrFlexible: 0 (fixed) > timingOffset: 0 > } > } > tfcs: TFCS-ReconfAdd ::= { > ctfcSize: ctfc2Bit ::= { > TFCS-ReconfAdd-foo2 ::= { > ctfc2: 0 > } > TFCS-ReconfAdd-foo2 ::= { > ctfc2: 1 > } > } > } > fach-PCH-InformationList: FACH-PCH-InformationList ::= { > FACH-PCH-Information ::= { > transportFormatSet: CommonTransChTFS ::= { > tti: CommonDynamicTF-InfoList ::= { > CommonDynamicTF-Info ::= { > rlc-Size: fdd ::= { > octetModeRLC-SizeInfoType2: 3 > } > numberOfTbSizeList: numberOfTbSizeList ::= { > <present> > <present> > } > logicalChannelList: <present> > } > } > semistaticTF-Information: SemistaticTF-Information ::= { > channelCodingType: 0 (half) > rateMatchingAttribute: 256 > crc-Size: 2 (crc12) > } > } > transportChannelIdentity: 1 > ctch-Indicator: FALSE > } > } > } > } > } > SysInfoType11 ::= { > sib12indicator: FALSE > measurementControlSysInfo: MeasurementControlSysInfo ::= { > use-of-HCS: hcs-not-used ::= { > cellSelectQualityMeasure: cpich-Ec-N0 ::= { > } > } > } > }=== Phase1 Encoding SIB MIB > === Phase1 Encoded SIB MIB size 152 blocks 0.672566 > SIB0: bytes: ByteVector(size=19 data: 00 00 40 25 00 00 44 20 64 20 33 21 91 51 00 30 74 a0 3b) > === Phase1 Encoding SIB SIB1 > === Phase1 Encoded SIB SIB1 size 94 blocks 0.415929 > SIB1: bytes: ByteVector(size=12 data: c4 02 10 8b 20 00 01 00 ce 01 ab 40) > === Phase1 Encoding SIB SIB2 > === Phase1 Encoded SIB SIB2 size 20 blocks 0.0884956 > SIB2: bytes: ByteVector(size=3 data: 00 06 40) > === Phase1 Encoding SIB SIB3 > === Phase1 Encoded SIB SIB3 size 102 blocks 0.451327 > SIB3: bytes: ByteVector(size=13 data: 00 00 00 00 42 c0 60 00 04 b4 ff ff fc) > === Phase1 Encoding SIB SIB5 > === Phase1 Encoded SIB SIB5 size 466 blocks 2.06195 > SIB4: bytes: ByteVector(size=59 data: 80 30 0e 88 00 00 f0 02 14 00 68 2c 0a ff 60 00 32 3f de c7 fb 84 03 c0 00 00 fa 99 1f fc 0c 80 91 e0 40 d0 00 08 22 00 43 08 8b fd 00 04 18 08 12 00 01 04 40 08 61 11 7f a0 00) > === Phase1 Encoding SIB SIB7 > === Phase1 Encoded SIB SIB7 size 20 blocks 0.0884956 > SIB5: bytes: ByteVector(size=3 data: 4a 00 00) > === Phase1 Encoding SIB SIB11 > === Phase1 Encoded SIB SIB11 size 10 blocks 0.0442478 > SIB6: bytes: ByteVector(size=2 data: 01 00) > chReserve(256,0) > ALERT 140630392444736 19:40:11.7 UMTSPhCh.cpp:654:chConflict: Attempt to reserve channel: sf=256 chcode=0 which conflicts with reserved channel: sf=128 chcode=0 > chReserve(256,1) > ALERT 140630392444736 19:40:11.7 UMTSPhCh.cpp:654:chConflict: Attempt to reserve channel: sf=256 chcode=1 which conflicts with reserved channel: sf=128 chcode=0 > 1495906811.723922 140630392444736: Starting the transceiver... > > linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.001.001-release > > ** Configuring logger > ** Using internal clock reference > ** Searching for USRP device > -- Detected Device: B210 > -- Operating over USB 2. > -- Initialize CODEC control... > -- Initialize Radio control... > -- Performing register loopback test... pass > -- Performing register loopback test... pass > -- Performing CODEC loopback test... pass > -- Performing CODEC loopback test... pass > -- Setting master clock rate selection to 'automatic'. > -- Asking for clock rate 16.000000 MHz... > -- Actually got clock rate 16.000000 MHz. > -- Performing timer loopback test... pass > -- Performing timer loopback test... pass > terminate called after throwing an instance of 'std::bad_alloc' > what(): std::bad_alloc > ALERT 140630392444736 19:40:22.7 TRXManager.cpp:66:sendCommandPacket: RSP response > ALERT 140630392444736 19:40:22.7 TRXManager.cpp:81:powerOff: POWEROFF failed with status -1 > ALERT 140630392444736 19:40:28.7 TRXManager.cpp:66:sendCommandPacket: RSP response > ALERT 140630392444736 19:40:28.7 TRXManager.cpp:412:tune: TXTUNE failed with status -1 > ALERT 140630281410304 19:40:31.7 TRXManager.cpp:258:clockHandler: TRX clock interface timed out, assuming TRX is dead. > ALERT 140630281410304 19:40:34.7 TRXManager.cpp:258:clockHandler: TRX clock interface timed out, assuming TRX is dead. > ALERT 140630392444736 19:40:34.7 TRXManager.cpp:66:sendCommandPacket: RSP response > ALERT 140630392444736 19:40:34.7 TRXManager.cpp:112:setRxGain: SETRXGAIN failed with status -1 > ALERT 140630281410304 19:40:37.7 TRXManager.cpp:258:clockHandler: TRX clock interface timed out, assuming TRX is dead. > ALERT 140630392444736 19:40:40.7 TRXManager.cpp:66:sendCommandPacket: RSP response > ALERT 140630392444736 19:40:40.7 TRXManager.cpp:499:powerOn: POWERON failed with status -1 > ALERT 140630281410304 19:40:40.7 TRXManager.cpp:258:clockHandler: TRX clock interface timed out, assuming TRX is dead. > ALERT 140630281410304 19:40:43.7 TRXManager.cpp:258:clockHandler: TRX clock interface timed out, assuming TRX is dead. > ALERT 140630392444736 19:40:46.7 TRXManager.cpp:66:sendCommandPacket: RSP response > ALERT 140630392444736 19:40:46.7 TRXManager.cpp:91:setPower: SETPOWER failed with status -1 > ALERT 140630281410304 19:40:46.7 TRXManager.cpp:258:clockHandler: TRX clock interface timed out, assuming TRX is dead. > RTNETLINK answers: File exists > 1495906847.511946 140630392444736: > system ready > > 1495906847.512018 140630392444736: > use the OpenBTS-UMTSCLI utility to access CLI > > > OpenBTS> ALERT 140630281410304 19:40:49.7 TRXManager.cpp:258:clockHandler: TRX clock interface timed out, assuming TRX is dead. > ALERT 140630281410304 19:40:52.7 TRXManager.cpp:258:clockHandler: TRX clock interface timed out, assuming TRX is dead. > ALERT 140630281410304 19:40:55.7 TRXManager.cpp:258:clockHandler: TRX clock interface timed out, assuming TRX is dead. > ALERT 140630281410304 19:40:58.7 TRXManager.cpp:258:clockHandler: TRX clock interface timed out, assuming TRX is dead. Regards, Dominique |
From: Keith E. F. <ke...@ya...> - 2017-04-28 23:11:50
|
Hi Luis, I have made a little more progress myself, since we spoke last in January. I am now running OpenBTS-UMTS in an Ubuntu 16.04 virtual machine (KVM) on a host with quad-core i5-7600K and 16GB RAM. I also elected to run the 'low-latency' kernel (4.4.0-75-lowlatency). These things together seem to improve the situation enough for the BlackBerry 9700 to see my network ("KEF", 00101) When it first started searching for a 3G network to attach to, I got a lot of warnings on the console about clipping on the RACH channel. By default, the RxGain was 57 :O I turned that shit down to 10db :D I am using ARFCN 3050 (900mhz uplink, 945mhz downlink) so as to not interfere with real cell carriers I too had authentication failures after the radio situation was straightened out. I used a SmartSIM and a USB SIM programmer. Using PySim, I assigned it IMSI 001010000000001 and (this is critical) a Ki of '12345678123456781234567812345678'. Make sure you have sipauthserve running. In the 'sip_buddies' table, create an entry for your IMSI and set Ki equal to your 128-bit Ki, as a 32-digit hexadecimal string. Because OpenBTS-UMTS is data only, a lot of the other fields in that table are unused. The instant I saved the table and exited sqlite3, the repeating messages to the console, changed. The state machine on each end was now able to move past authentication. Here are some console snippets: When sipauthserver is not running it will look like this: ALERT 2986593088 18:47:40.3 SIPEngine.cpp:288:Register: SIP REGISTER timed out; is the registration server 127.0.0.1:5064 OK? ALERT 2986593088 18:47:40.3 Sgsn.cpp:614:sendAuthenticationRequest: SIP registration timed out. Is sipauthserve running? Where I am at with it now is this console output which is typical: 48:32.8 UL_CCCH_MessageType_PR_rrcConnectionRequest UE#1 URNTI=c533 stIdleMode rbid=0 newState: 1 1 48:32.8 DL_CCCH RRC_Connection_Setup_Message message size=60 UE#1 URNTI=c533 stIdleMode rbid=0 newState: 2 1 ALERT 3028949824 18:48:33.5 URLC.cpp:1755:rlcWriteLowSide: stateChange: before 0 0 after 0 0 48:35.2 UL_DCCH_MessageType_PR_rrcConnectionSetupComplete UE#1 URNTI=c533 stCELL_FACH rbid=2 48:36.1 UL_DCCH_MessageType_PR_initialDirectTransfer UE#1 URNTI=c533 stCELL_FACH rbid=3 48:36.1 UL GMM Msg: AttachRequest UE#1 URNTI=c533 stCELL_FACH imsi=001010000000001 PDP of 0 is 0, gmm = b2d03e88, si = b2d04fc0 PDP of 5 is 0, gmm = b2d03e88, si = b2d04fc0 48:36.1 DL_DCCH AuthenticationAndCipheringReq message size=25 UE#1 URNTI=c533 stCELL_FACH rbid=3 PDP of 0 is 0 48:39.4 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=c533 stCELL_FACH rbid=3 48:39.4 UL GMM Msg: AuthenticationAndCipheringResp UE#1 URNTI=c533 stCELL_FACH imsi=001010000000001 PDP of 0 is 0 PDP of 0 is 0 48:39.4 DL_DCCH RRC Security Mode Command message size=15 UE#1 URNTI=c533 stCELL_FACH rbid=2 48:42.0 UL_DCCH_MessageType_PR_securityModeComplete UE#1 URNTI=c533 stCELL_FACH rbid=2 48:42.0 DL_DCCH AttachAccept message size=26 UE#1 URNTI=c533 stCELL_FACH rbid=3 48:43.9 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=c533 stCELL_FACH rbid=3 48:43.9 UL GMM Msg: AttachComplete UE#1 URNTI=c533 stCELL_FACH imsi=001010000000001 48:46.5 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=c533 stCELL_FACH rbid=3 48:46.5 UL SM Msg: ActivatePDPContextRequest UE#1 URNTI=c533 stCELL_FACH imsi=001010000000001 kbps: 0, ops: 0 48:46.5 DL_DCCH ActivatePDPContextReject message size=11 UE#1 URNTI=c533 stCELL_FACH rbid=3 48:53.1 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=c533 stCELL_FACH rbid=3 48:53.1 UL SM Msg: ActivatePDPContextRequest UE#1 URNTI=c533 stCELL_FACH imsi=001010000000001 IP address: 163a8c0 48:53.1 DL_DCCH ActivatePDPContextAccept message size=82 UE#1 URNTI=c533 stCELL_FACH rbid=3 48:56.3 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=c533 stCELL_FACH rbid=3 48:56.3 UL GMM Msg: ServiceRequest UE#1 URNTI=c533 stCELL_FACH imsi=001010000000001 20 0 1 1 1 PDP of 5 is b1e63ee8, gmm = b2d03e88, si = b2d04fc0 PDP of 5 is b1e63ee8, gmm = b2d03e88, si = b2d04fc0 PDP of 5 is b1e63ee8, gmm = b2d03e88, si = b2d04fc0 48:56.3 DL_DCCH AuthenticationAndCipheringReq message size=30 UE#1 URNTI=c533 stCELL_FACH rbid=3 PDP of 5 is b1e63ee8 48:57.6 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=c533 stCELL_FACH rbid=3 48:57.6 UL GMM Msg: AuthenticationAndCipheringResp UE#1 URNTI=c533 stCELL_FACH imsi=001010000000001 PDP of 5 is b1e63ee8 PDP of 5 is b1e63ee8 48:57.6 DL_DCCH RRC Security Mode Command message size=15 UE#1 URNTI=c533 stCELL_FACH rbid=2 49:00.6 UL_DCCH_MessageType_PR_securityModeFailure UE#1 URNTI=c533 stCELL_FACH rbid=2 49:04.3 UL_DCCH_MessageType_PR_signallingConnectionReleaseIndication UE#1 URNTI=c533 stCELL_FACH rbid=2 49:04.3 DL_DCCH RRC_Connection_Release_Message message size=7 UE#1 URNTI=c533 stCELL_FACH rbid=2 49:10.5 UL_DCCH_MessageType_PR_initialDirectTransfer UE#1 URNTI=c533 stCELL_FACH rbid=3 49:10.5 UL GMM Msg: RoutingAreaUpdateRequest UE#1 URNTI=c533 stCELL_FACH imsi=001010000000001 49:10.5 DL_DCCH RoutingAreaUpdateAccept message size=36 UE#1 URNTI=c533 stCELL_FACH rbid=3 49:20.5 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=c533 stCELL_FACH rbid=3 49:20.5 UL GMM Msg: RoutingAreaUpdateRequest UE#1 URNTI=c533 stCELL_FACH imsi=001010000000001 49:20.5 DL_DCCH RoutingAreaUpdateAccept message size=36 UE#1 URNTI=c533 stCELL_FACH rbid=3 49:38.0 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=c533 stCELL_FACH rbid=3 49:38.0 UL GMM Msg: RoutingAreaUpdateRequest UE#1 URNTI=c533 stCELL_FACH imsi=001010000000001 49:38.1 DL_DCCH RoutingAreaUpdateAccept message size=36 UE#1 URNTI=c533 stCELL_FACH rbid=3 49:51.0 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=c533 stCELL_FACH rbid=3 49:51.0 UL GMM Msg: RoutingAreaUpdateRequest UE#1 URNTI=c533 stCELL_FACH imsi=001010000000001 49:51.0 DL_DCCH RoutingAreaUpdateAccept message size=36 UE#1 URNTI=c533 stCELL_FACH rbid=3 50:06.2 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=c533 stCELL_FACH rbid=3 50:06.2 UL GMM Msg: RoutingAreaUpdateRequest UE#1 URNTI=c533 stCELL_FACH imsi=001010000000001 50:06.2 DL_DCCH RoutingAreaUpdateAccept message size=36 UE#1 URNTI=c533 stCELL_FACH rbid=3 50:19.9 UL_DCCH_MessageType_PR_signallingConnectionReleaseIndication UE#1 URNTI=c533 stCELL_FACH rbid=2 50:19.9 DL_DCCH RRC_Connection_Release_Message message size=7 UE#1 URNTI=c533 stCELL_FACH rbid=2 50:35.6 UL_DCCH_MessageType_PR_initialDirectTransfer UE#1 URNTI=c533 stCELL_FACH rbid=3 50:35.6 UL GMM Msg: RoutingAreaUpdateRequest UE#1 URNTI=c533 stCELL_FACH imsi=001010000000001 50:35.6 DL_DCCH RoutingAreaUpdateAccept message size=36 UE#1 URNTI=c533 stCELL_FACH rbid=3 50:51.5 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=c533 stCELL_FACH rbid=3 50:51.5 UL GMM Msg: RoutingAreaUpdateRequest UE#1 URNTI=c533 stCELL_FACH imsi=001010000000001 50:51.5 DL_DCCH RoutingAreaUpdateAccept message size=36 UE#1 URNTI=c533 stCELL_FACH rbid=3 51:05.7 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=c533 stCELL_FACH rbid=3 51:05.7 UL GMM Msg: RoutingAreaUpdateRequest UE#1 URNTI=c533 stCELL_FACH imsi=001010000000001 51:05.7 DL_DCCH RoutingAreaUpdateAccept message size=36 UE#1 URNTI=c533 stCELL_FACH rbid=3 51:20.6 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=c533 stCELL_FACH rbid=3 51:20.6 UL GMM Msg: RoutingAreaUpdateRequest UE#1 URNTI=c533 stCELL_FACH imsi=001010000000001 51:20.6 DL_DCCH RoutingAreaUpdateAccept message size=36 UE#1 URNTI=c533 stCELL_FACH rbid=3 51:38.0 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=c533 stCELL_FACH rbid=3 51:38.0 UL GMM Msg: RoutingAreaUpdateRequest UE#1 URNTI=c533 stCELL_FACH imsi=001010000000001 51:38.0 DL_DCCH RoutingAreaUpdateAccept message size=36 UE#1 URNTI=c533 stCELL_FACH rbid=3 51:49.6 UL_DCCH_MessageType_PR_signallingConnectionReleaseIndication UE#1 URNTI=c533 stCELL_FACH rbid=2 51:49.6 DL_DCCH RRC_Connection_Release_Message message size=7 UE#1 URNTI=c533 stCELL_FACH rbid=2 52:06.1 UL_DCCH_MessageType_PR_initialDirectTransfer UE#1 URNTI=c533 stCELL_FACH rbid=3 52:06.1 UL GMM Msg: RoutingAreaUpdateRequest UE#1 URNTI=c533 stCELL_FACH imsi=001010000000001 52:06.1 DL_DCCH RoutingAreaUpdateAccept message size=36 UE#1 URNTI=c533 stCELL_FACH rbid=3 52:22.4 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=c533 stCELL_FACH rbid=3 52:22.4 UL GMM Msg: RoutingAreaUpdateRequest UE#1 URNTI=c533 stCELL_FACH imsi=001010000000001 52:22.4 DL_DCCH RoutingAreaUpdateAccept message size=36 UE#1 URNTI=c533 stCELL_FACH rbid=3 52:37.0 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=c533 stCELL_FACH rbid=3 52:37.0 UL GMM Msg: RoutingAreaUpdateRequest UE#1 URNTI=c533 stCELL_FACH imsi=001010000000001 52:37.0 DL_DCCH RoutingAreaUpdateAccept message size=36 UE#1 URNTI=c533 stCELL_FACH rbid=3 So I still have something hokey going on but I am thrilled that I am now this far. What I'm going to look at over the weekend is how to get GSMTAP working, to see the console messages above in Wireshark -KEF On Tuesday, April 18, 2017 12:01 PM, luis castañeda <lui...@ho...> wrote: #yiv3013435028 #yiv3013435028 -- P {margin-top:0;margin-bottom:0;}#yiv3013435028 hi all, I wrote starting the year because I got the error "autentication failure" and thanks to Harvind, I noticed that the sim I was using (sysmousim) was not compatible becouse he use milenage algorithm, then i buy a supersim that use comp128 v1 and And now I dont get the error "autentication failure", now the phone try to conect , Even pick up signal for a few minutes But not yet finished register. I do not know what to do, maibe I'm mistaken when I use pysim or when i used sipauthserve (I clarify that I am using complete authentication with ki), Someone can give me an idea or advice? thanks for your time bes regards to all ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ Openbts-umts-discuss mailing list Ope...@li... https://lists.sourceforge.net/lists/listinfo/openbts-umts-discuss |
From: luis c. <lui...@ho...> - 2017-04-18 16:01:16
|
hi all, I wrote starting the year because I got the error "autentication failure" and thanks to Harvind, I noticed that the sim I was using (sysmousim) was not compatible becouse he use milenage algorithm, then i buy a supersim that use comp128 v1 and And now I dont get the error "autentication failure", now the phone try to conect , Even pick up signal for a few minutes But not yet finished register. I do not know what to do, maibe I'm mistaken when I use pysim or when i used sipauthserve (I clarify that I am using complete authentication with ki), Someone can give me an idea or advice? thanks for your time bes regards to all |
From: Keith E. F. <ke...@ya...> - 2017-01-19 19:03:13
|
I apologize for being a little offtopic but there are several of us that have tried UMTS and can't even get it to show up as a network in the handset. Did you have to do much to the configuration to get it to work? On Thursday, January 19, 2017 12:16 PM, luis castañeda <lui...@ho...> wrote: <!--#yiv9945651854 P {margin-top:0;margin-bottom:0;}-->Hi, all I'm running OpenBTS-UMTS with an EttusB200 , and works fine , i see the OpenBTS-UMTS network in my phone, also i used sysmoSIM-SJS1-4FF simcard and i know the SIM’s Ki value, i have entered IMSI and Ki value in database whit ./nmcli.py sipauthserve subscribers create name imsi msisdn ki. But attempts to register the phone, the authentication fails and i see this in the terminal OpenBTS> 20:18.1 UL_CCCH_MessageType_PR_rrcConnectionRequest UE#1 URNTI=d424 stCELL_FACH rbid=0 newState: 1 2 20:18.2 DL_CCCH RRC_Connection_Setup_Message message size=58 UE#1 URNTI=d424 stIdleMode rbid=0 newState: 2 1 ALERT 140058231088896 10:20:18.5 URLC.cpp:1755:rlcWriteLowSide: stateChange: before 0 0 after 0 0 20:18.6 UL_DCCH_MessageType_PR_rrcConnectionSetupComplete UE#1 URNTI=d424 stCELL_FACH rbid=2 20:19.0 UL_DCCH_MessageType_PR_initialDirectTransfer UE#1 URNTI=d424 stCELL_FACH rbid=3 20:19.0 UL GMM Msg: AttachRequest UE#1 URNTI=d424 stCELL_FACH imsi=901700000011060 PDP of 0 is 0, gmm = 90003cc0, si = 90005460 PDP of 5 is 0, gmm = 90003cc0, si = 90005460 20:19.0 DL_DCCH AuthenticationAndCipheringReq message size=25 UE#1 URNTI=d424 stCELL_FACH rbid=3 PDP of 0 is 0 20:19.3 UL_DCCH_MessageType_PR_uplinkDirectTransfer UE#1 URNTI=d424 stCELL_FACH rbid=3 20:19.3 UL GMM Msg: AuthenticationAndCipheringFailure UE#1 URNTI=d424 stCELL_FACH imsi=901700000011060 the registration with the B200 works? thanks for your time ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Openbts-umts-discuss mailing list Ope...@li... https://lists.sourceforge.net/lists/listinfo/openbts-umts-discuss |