search

RangeNetworks / OpenBTS-UMTS

3G UMTS Data Radio Access Network Node
GNU Affero General Public License v3.0
297 stars 196 forks source link

Compilation issue #2

Closed mekhalleh closed 9 years ago

mekhalleh commented 9 years ago

Hello,

Have you any tricks for compiling ? I have follow your ReadMe notes and I use the recommanded asn1c-0.9.23

I use Debian testing and ./autogen.sh doesn't work.

Thanks in advance.

Preparing the openbts-umts build system...please wait

Found GNU Autoconf version 2.69 Found GNU Automake version 1.11.6 Found GNU Libtool version 2.4.2

Warning: Several files expected of projects that conform to the GNU coding standards were not found. The files were automatically added for you since you do not have a 'foreign' declaration specified.

Considered adding 'foreign' to AM_INIT_AUTOMAKE in configure.ac or to AUTOMAKE_OPTIONS in your top-level Makefile.am file.

Automatically preparing build ... Warning: autoreconf failed libtoolize being run by autoreconf is not creating ltmain.sh in the auxillary directory like it should Attempting to run the preparation steps individually

Preparing build ... configure.ac:97: required file `NodeManager/Makefile.in' not found

ERROR: automake failed

mekhalleh commented 9 years ago

Oups ... I have jump this step.

$ git submodule init $ git submodule update

All work fine :D Thanks for this.

Keskebeu commented 7 years ago

I have the ASN compiling issue. it says it cannot find libtool. I also have installed asn1c compiler. Can you help please.

Generated pdu_collection.c Generated Makefile.am.sample rm -f o/BOOLEAN.c cd o && ln -s ../range_BOOLEAN.c BOOLEAN.c rm -f o/asn_SET_OF.h cd o && ln -s ../asn_SET_OF.h asn_SET_OF.h make libRRCASN.la # Recur to re-load the newly created .c files make[3]: Entering directory '/usr/src/OpenBTS-UMTS/ASN' cd o && libtool --mode=compile --tag=CC cc -O3 -g -w -I. -o DL-DCCH-Message.o -c DL-DCCH-Message.c /bin/sh: 1: libtool: not found makefile:4846: recipe for target 'o/DL-DCCH-Message.o' failed make[3]: [o/DL-DCCH-Message.o] Error 127 make[3]: Leaving directory '/usr/src/OpenBTS-UMTS/ASN' makefile:4803: recipe for target 'all' failed make[2]: [all] Error 2 make[2]: Leaving directory '/usr/src/OpenBTS-UMTS/ASN' Makefile:550: recipe for target 'all-recursive' failed make[1]: [all-recursive] Error 1 make[1]: Leaving directory '/usr/src/OpenBTS-UMTS' Makefile:481: recipe for target 'all' failed make: [all] Error 2

Keskebeu commented 7 years ago

I found the problem libtool was not found at bin directory I moved it there and now it compiled ASN

tiger762 commented 7 years ago

How I got around the problem was to install libtool-bin

apt-get install libtool-bin

dkogue commented 7 years ago

kindly help please. using Ubuntu 16.04 

      ^

makefile:4846: recipe for target 'o/BOOLEAN.o' failed make[3]: [o/BOOLEAN.o] Error 1 make[3]: Leaving directory '/home/dada/Master/OpenBTS-UMTS/ASN' makefile:4803: recipe for target 'all' failed make[2]: [all] Error 2 make[2]: Leaving directory '/home/dada/Master/OpenBTS-UMTS/ASN' Makefile:550: recipe for target 'all-recursive' failed make[1]: [all-recursive] Error 1 make[1]: Leaving directory '/home/dada/Master/OpenBTS-UMTS' Makefile:481: recipe for target 'all' failed make: [all] Error 2

Keskebeu commented 7 years ago

I can see that you need ASN library https://github.com/Keskebeu/asn1c-0.9.23.zip go to this website and click on that link, I made this easy for people. And download this zip file: asn1c-f5ab8ba08c82d6283fe35a9678b6bac4e1fe2337.zip.

Unzip this file and move it in the /usr/src folder.

make sure you add sudo if you are not root.

compile asn1c library (where you unziped the folder) by doing: ./configure make make install ldconfig.

, than go back to the OpenBTS-UMTS folder and do: make clean ./configure make make install ldconfig.

If you have already installed asn1c library already and this is failing do the following in the OpenBTS-UMTS directory

git submodule init, wait for initializing a couple of sentences git submodule update, this will update the repository

and than do: make clean ./configure make make install ldconfig.

Make sure you also copy libtool in /usr/bin directory or do it by: sudo apt-get install libtool-bin.

dkogue commented 7 years ago

Thank you for your feedback! managed to solved this earlier but having below error now. please help!

Loading ezusb.ihx firmware file... resetting EZ-USB sudo: ./RAD1Cmd: command not found 3G PLL register update utility for 61.44Mhz Begin updating Si5338 registers sudo: ./RAD1Cmd: command not found MultiSynth2 frequency Conf MS2_P1[7:0] sudo: ./RAD1Cmd: command not found MultiSynth2 frequency Conf MS2_P1[15:8] sudo: ./RAD1Cmd: command not found MultiSynth2 frequency Conf MS2_P2[5:0] MS2_P1[17:18] Setting clock output 2 to 61.44Mhz complete sudo: ./RAD1Cmd: command not found MultiSynth2 frequency Conf MS2_P3[7:0] sudo: ./RAD1Cmd: command not found MultiSynth3 frequency Conf MS3_P1[7:0] sudo: ./RAD1Cmd: command not found MultiSynth3 frequency Conf MS3_P1[15:8] sudo: ./RAD1Cmd: command not found MultiSynth3 frequency Conf MS3_P2[5:0] MS3_P1[17:18] sudo: ./RAD1Cmd: command not found MultiSynth3 frequency Conf MS3_P3[7:0] Setting clock output 3 to 61.44Mhz complete Completed 61.44MHz configuration... soft resetting sudo: ./RAD1Cmd: command not found Soft reset complete... exiting

On Fri, Jun 2, 2017 at 1:52 PM, Keskebeu notifications@github.com wrote:

I can see that you need ASN library https://github.com/Keskebeu/asn1c-0.9.23.zip go to this website and click on that link, I made this easy for people. And download this zip file: asn1c-f5ab8ba08c82d6283fe35a9678b6ba c4e1fe2337.zip.

Unzip this file and move it in the /usr/src folder.

make sure you add sudo if you are not root.

compile asn1c library (where you unziped the folder) and do: ./configure make make install ldconfig.

, than go back to the OpenBTS-UMTS folder and do: ./configure make clean make make install ldconfig

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/RangeNetworks/OpenBTS-UMTS/issues/2#issuecomment-305765273, or mute the thread https://github.com/notifications/unsubscribe-auth/AY7cXyMQ0L0xx41PX93zYKzyJPmrdvEgks5r__djgaJpZM4Dh9I5 .

Keskebeu commented 7 years ago

Tell me a little bit about what kind of radio you are using and its specifics. Let me know in which folder you have installed OpenBTS-UMTS

dkogue commented 7 years ago

I am using USRP B210 and I install OpenBTS-UMTS in the Home directory.

dada@dada-VPCEH2C1E:~/Master/OpenBTS-UMTS/TransceiverRAD1$ sudo ./clkit_61_44mhz.sh [sudo] password for dada: Loading ezusb.ihx firmware file... resetting EZ-USB sudo: ./RAD1Cmd: command not found 3G PLL register update utility for 61.44Mhz Begin updating Si5338 registers sudo: ./RAD1Cmd: command not found MultiSynth2 frequency Conf MS2_P1[7:0] sudo: ./RAD1Cmd: command not found MultiSynth2 frequency Conf MS2_P1[15:8] sudo: ./RAD1Cmd: command not found MultiSynth2 frequency Conf MS2_P2[5:0] MS2_P1[17:18] Setting clock output 2 to 61.44Mhz complete sudo: ./RAD1Cmd: command not found MultiSynth2 frequency Conf MS2_P3[7:0] sudo: ./RAD1Cmd: command not found MultiSynth3 frequency Conf MS3_P1[7:0]

On Fri, Jun 2, 2017 at 2:09 PM, Keskebeu notifications@github.com wrote:

Tell me a little bit about what kind of radio you are using and its specifics. Let me know in which folder you have installed OpenBTS-UMTS

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/RangeNetworks/OpenBTS-UMTS/issues/2#issuecomment-305768541, or mute the thread https://github.com/notifications/unsubscribe-auth/AY7cX9rLhYlVlFMhE4fxhjZTVPa86yN3ks5r__uLgaJpZM4Dh9I5 .

Keskebeu commented 7 years ago

You dont have to use TransceiverRAD1at all. Thats by default RangeNetworks radio for any RangeNetwork project.

You now have to go to OpenBTS-UMTS folder go to apps and do as root $vim OpenBTS-UMTS.cpp or nano OpenBTS-UMTS.cpp (its better to use vim because you can go a specific line) and find the line

const char* transceiverPath = "./transceiver" and change it to ./TransceiverUHD/transceiver/

if this does not work leave it as it was before and instead do:

dada@dada-VPCEH2C1E:~/Master/OpenBTS-UMTS/TransceiverUHD# cp transceiver /home/Master/OpenBTS-UMTS/apps

and than do the following in the apps directory

ln -sf transceiver transceiver

and now you are ready to go.

dkogue commented 7 years ago

Thank you for your swift feedbacks and support. I think now my OpenBTS-UMTS is up but cannot see it with my phone. Is there any config I am missing. kindly find below my audit and config logs:

OpenBTS> config 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] ........................................................................................ OpenBTS> audit +---------------------------------------------------------------------+ | ERROR : Invalid Values [key current-value (default)] | | To use the default value again, execute: rmconfig key | +---------------------------------------------------------------------+ SMS.MIMEType "application/vnd.3gpp.sms" ("application/vnd.3gpp.sms") UMTS.PRACH.SF "32" ("32") UMTS.Radio.Band "900" ("900") UMTS.Radio.C0 "3050" ("3050") UMTS.SCCPCH.SF "64" ("64")

+---------------------------------------------------------------------+ | WARNING : Site Values Which Are Still Default [key current-value] | | These should be set to fit your installation: config key value | +---------------------------------------------------------------------+ GSM.Identity.BSIC.BCC "2" GSM.Identity.LAC "1000" GSM.Identity.MCC "001" GSM.Identity.MNC "01" GSM.RRLP.SEED.LATITUDE "37.777423" GSM.RRLP.SEED.LONGITUDE "-122.39807" UMTS.Identity.CI "10"

Thank you! Nice Weekend 😉

On Fri, Jun 2, 2017 at 2:27 PM, Keskebeu notifications@github.com wrote:

You dont have to use TransceiverRAD1at all. Thats by default RangeNetworks radio for any RangeNetwork project.

You now have to go to OpenBTS-UMTS folder go to apps and do as root $vim OpenBTS-UMTS.cpp or nano OpenBTS-UMTS.cpp (its better to use vim because you can go a specific line) and find the line

const char* transceiverPath = "./transceiver" and change it to ./TransceiverUHD/transceiver/

if this does not work leave it as it was before and instead do:

dada@dada-VPCEH2C1E:~/Master/OpenBTS-UMTS/TransceiverUHD# cp transceiver /Master/OpenBTS-UMTS/apps

and than do the following in the apps directory

ln -sf transceiver transceiver

and now you are ready to go.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/RangeNetworks/OpenBTS-UMTS/issues/2#issuecomment-305771779, or mute the thread https://github.com/notifications/unsubscribe-auth/AY7cXwSLBEqxSweXD_q5WrT8EdJsmJj4ks5r__-dgaJpZM4Dh9I5 .

Keskebeu commented 7 years ago

if you are testing your network in 900 you have to have a phone compatible with 900 band. now you have to configure out the noise.

in OpenBTS-UMTSCLI do

noise and than do rxgain show me what is it coming back with.

You now have to make sure there is no noise in your radio. Make sure you have the antennas set up in a 90 angle with each-other.

if you have a message saying uplink connectivity is not possible.Than your phone cannot connect see the antenna by the noise generated around you and also noise floor. you have to make sure that noise generated by the MS RSSI is higher in value than floor noise otherwise you will not be able to connect to your phones or transfer data, calls or sms.

Study some of the radio functions. as you have to know what frequency you can use. Since US uses 800 or 850 is better to test it at 900 european standard and if you are in Europe do vice-versa , so you don't conflict any other frequency and have Intelligence officers from energy department looking around your house for RF exposure.

with the usrp you can factory calibrate it by command in the CLI. Theres a book OpenBTS if you read that you will see what I am talking about. Plus if you are good in math you can figure it out fast enough.

From what i can see you are in OpenBTS> not in OpenBTS-UMTS> are you sure you didnt get anything back from the response when you ran ./OpenBTS-UMTS?

dkogue commented 7 years ago

Hi,

OpenBTS> rxgain current RX gain is 10 dB

+---------------------------------------------------------------------+ | ERROR : Invalid Values [key current-value (default)] | | To use the default value again, execute: rmconfig key | +---------------------------------------------------------------------+ SMS.MIMEType "application/vnd.3gpp.sms" ("application/vnd.3gpp.sms") UMTS.PRACH.SF "32" ("32") UMTS.Radio.Band "850" ("900") UMTS.Radio.C0 "4359" ("3050") UMTS.SCCPCH.SF "64" ("64")

+---------------------------------------------------------------------+ | WARNING : Site Values Which Are Still Default [key current-value] | | These should be set to fit your installation: config key value | +---------------------------------------------------------------------+ GSM.Identity.BSIC.BCC "2" GSM.Identity.LAC "1000" GSM.Identity.MCC "001" GSM.Identity.MNC "01" GSM.RRLP.SEED.LATITUDE "37.777423" GSM.RRLP.SEED.LONGITUDE "-122.39807" UMTS.Identity.CI "10" UMTS.Identity.LAC "132" UMTS.Identity.MCC "001" UMTS.Identity.MNC "01" UMTS.Identity.URAI "100"

+---------------------------------------------------------------------+ | INFO : Non-Default Values [key current-value (default)] | | To use the default value again, execute: rmconfig key | +---------------------------------------------------------------------+ GGSN.DNS "8.8.8.8" ("") GGSN.Firewall.Enable "0" ("1") UMTS.Radio.Band "850" ("900") UMTS.Radio.RxGain "10" ("57")

+---------------------------------------------------------------------+ | INFO : Custom/Deprecated Key/Value Pairs [key current-value] | | To clean up any extraneous keys, execute: rmconfig key | +---------------------------------------------------------------------+ UMTS.Identity.ShortName "kudos"

I am still not able to detect the signal on my phone. I will appreciate if you can clarify the following question.

I have a programable USIM card from Sysmocom and an USB reader as well.

my objective is to modify the authentication procedure both on the USIM as well as the one on Openbts-UMTS.

for example add challenge response, generate a nounce send it to the card, whish can perform an XOR operation and revert with it answer.

Is this posiible ? Any advise on how to proceed please?

any books or tutorials that can help me will be most welcomed.

Cheers, Domi

On Fri, Jun 2, 2017 at 4:59 PM, Keskebeu notifications@github.com wrote:

if you are testing your network in 900 you have to have a phone compatible with 900 band. now you have to configure out the noise.

in OpenBTS-UMTSCLI do

noise and than do rxgain show me what is it coming back with.

You now have to make sure there is no noise in your radio. Make sure you have the antennas set up in a 90 angle with each-other.

if you have a message saying uplink connectivity is not possible.Than your phone cannot connect see the antenna by the noise generated around you and also noise floor. you have to make sure that noise generated by the MS RSSI is higher in value than floor noise otherwise you will not be able to connect to your phones or transfer data, calls or sms.

Study some of the radio functions. as you have to know what frequency you can use. Since US uses 800 or 850 is better to test it at 900 european standard and if you are in Europe do vice-versa , so you don't conflict any other frequency and have Intelligence officers from energy department looking around your house for RF exposure.

with the usrp you can factory calibrate it by command in the CLI. Theres a book OpenBTS if you read that you will see what I am talking about. Plus if you are good in math you can figure it out fast enough.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/RangeNetworks/OpenBTS-UMTS/issues/2#issuecomment-305813017, or mute the thread https://github.com/notifications/unsubscribe-auth/AY7cXy8ASKoQAOHhZ9_b4tCmGzYkMwjIks5sACNGgaJpZM4Dh9I5 .

dkogue commented 7 years ago

Hi,

OpenBTS> rxgain current RX gain is 10 dB

+---------------------------------------------------------------------+ | ERROR : Invalid Values [key current-value (default)] | | To use the default value again, execute: rmconfig key | +---------------------------------------------------------------------+ SMS.MIMEType "application/vnd.3gpp.sms" ("application/vnd.3gpp.sms") UMTS.PRACH.SF "32" ("32") UMTS.Radio.Band "850" ("900") UMTS.Radio.C0 "4359" ("3050") UMTS.SCCPCH.SF "64" ("64")

+---------------------------------------------------------------------+ | WARNING : Site Values Which Are Still Default [key current-value] | | These should be set to fit your installation: config key value | +---------------------------------------------------------------------+ GSM.Identity.BSIC.BCC "2" GSM.Identity.LAC "1000" GSM.Identity.MCC "001" GSM.Identity.MNC "01" GSM.RRLP.SEED.LATITUDE "37.777423" GSM.RRLP.SEED.LONGITUDE "-122.39807" UMTS.Identity.CI "10" UMTS.Identity.LAC "132" UMTS.Identity.MCC "001" UMTS.Identity.MNC "01" UMTS.Identity.URAI "100"

+---------------------------------------------------------------------+ | INFO : Non-Default Values [key current-value (default)] | | To use the default value again, execute: rmconfig key | +---------------------------------------------------------------------+ GGSN.DNS "8.8.8.8" ("") GGSN.Firewall.Enable "0" ("1") UMTS.Radio.Band "850" ("900") UMTS.Radio.RxGain "10" ("57")

+---------------------------------------------------------------------+ | INFO : Custom/Deprecated Key/Value Pairs [key current-value] | | To clean up any extraneous keys, execute: rmconfig key | +---------------------------------------------------------------------+ UMTS.Identity.ShortName "kudos"

I am still not able to detect the signal on my phone. I will appreciate if you can clarify the following question.

I have a programmable USIM card from Sysmocom and a USB reader as well.

my objective is to modify the authentication procedure both on the USIM as well as the one on Openbts-UMTS.

for example, add challenge response, generate a nonce send it to the card, which can perform a XOR operation and revert with it answer.

Is this possible? Any advice on how to proceed, please?

any books or tutorials that can help me will be most welcomed.

Cheers, Domi

On Fri, Jun 2, 2017 at 4:59 PM, Keskebeu notifications@github.com wrote:

if you are testing your network in 900 you have to have a phone compatible with 900 band. now you have to configure out the noise.

in OpenBTS-UMTSCLI do

noise and than do rxgain show me what is it coming back with.

You now have to make sure there is no noise in your radio. Make sure you have the antennas set up in a 90 angle with each-other.

if you have a message saying uplink connectivity is not possible.Than your phone cannot connect see the antenna by the noise generated around you and also noise floor. you have to make sure that noise generated by the MS RSSI is higher in value than floor noise otherwise you will not be able to connect to your phones or transfer data, calls or sms.

Study some of the radio functions. as you have to know what frequency you can use. Since US uses 800 or 850 is better to test it at 900 european standard and if you are in Europe do vice-versa , so you don't conflict any other frequency and have Intelligence officers from energy department looking around your house for RF exposure.

with the usrp you can factory calibrate it by command in the CLI. Theres a book OpenBTS if you read that you will see what I am talking about. Plus if you are good in math you can figure it out fast enough.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/RangeNetworks/OpenBTS-UMTS/issues/2#issuecomment-305813017, or mute the thread https://github.com/notifications/unsubscribe-auth/AY7cXy8ASKoQAOHhZ9_b4tCmGzYkMwjIks5sACNGgaJpZM4Dh9I5 .

dkogue commented 7 years ago

Hi, OpenBTS> rxgain current RX gain is 10 dB +---------------------------------------------------------------------+ | ERROR : Invalid Values [key current-value (default)] | | To use the default value again, execute: rmconfig key | +---------------------------------------------------------------------+ SMS.MIMEType "application/vnd.3gpp.sms" ("application/vnd.3gpp.sms") UMTS.PRACH.SF "32" ("32") UMTS.Radio.Band "850" ("900") UMTS.Radio.C0 "4359" ("3050") UMTS.SCCPCH.SF "64" ("64") +---------------------------------------------------------------------+ | WARNING : Site Values Which Are Still Default [key current-value] | | These should be set to fit your installation: config key value | +---------------------------------------------------------------------+ GSM.Identity.BSIC.BCC "2" GSM.Identity.LAC "1000" GSM.Identity.MCC "001" GSM.Identity.MNC "01" GSM.RRLP.SEED.LATITUDE "37.777423" GSM.RRLP.SEED.LONGITUDE "-122.39807" UMTS.Identity.CI "10" UMTS.Identity.LAC "132" UMTS.Identity.MCC "001" UMTS.Identity.MNC "01" UMTS.Identity.URAI "100" +---------------------------------------------------------------------+ | INFO : Non-Default Values [key current-value (default)] | | To use the default value again, execute: rmconfig key | +---------------------------------------------------------------------+ GGSN.DNS "8.8.8.8" ("") GGSN.Firewall.Enable "0" ("1") UMTS.Radio.Band "850" ("900") UMTS.Radio.RxGain "10" ("57") +---------------------------------------------------------------------+ | INFO : Custom/Deprecated Key/Value Pairs [key current-value] | | To clean up any extraneous keys, execute: rmconfig key | +---------------------------------------------------------------------+ UMTS.Identity.ShortName "kudos" I am still not able to detect the signal on my phone. I will appreciate if you can clarify the following question. I have a programmable USIM card from Sysmocom and a USB reader as well. my objective is to modify the authentication procedure both on the USIM as well as the one on Openbts-UMTS. for example, add challenge response, generate a nonce send it to the card, which can perform a XOR operation and revert with it answer. Is this possible? Any advice on how to proceed, please? any books or tutorials that can help me will be most welcomed. Cheers, Domi

On Tue, Jun 27, 2017 at 3:01 PM, Wola Dominique kedoswola@gmail.com wrote:

Hi,

OpenBTS> rxgain current RX gain is 10 dB

+---------------------------------------------------------------------+ | ERROR : Invalid Values [key current-value (default)] | | To use the default value again, execute: rmconfig key | +---------------------------------------------------------------------+ SMS.MIMEType "application/vnd.3gpp.sms" ("application/vnd.3gpp.sms") UMTS.PRACH.SF "32" ("32") UMTS.Radio.Band "850" ("900") UMTS.Radio.C0 "4359" ("3050") UMTS.SCCPCH.SF "64" ("64")

+---------------------------------------------------------------------+ | WARNING : Site Values Which Are Still Default [key current-value] | | These should be set to fit your installation: config key value | +---------------------------------------------------------------------+ GSM.Identity.BSIC.BCC "2" GSM.Identity.LAC "1000" GSM.Identity.MCC "001" GSM.Identity.MNC "01" GSM.RRLP.SEED.LATITUDE "37.777423" GSM.RRLP.SEED.LONGITUDE "-122.39807" UMTS.Identity.CI "10" UMTS.Identity.LAC "132" UMTS.Identity.MCC "001" UMTS.Identity.MNC "01" UMTS.Identity.URAI "100"

+---------------------------------------------------------------------+ | INFO : Non-Default Values [key current-value (default)] | | To use the default value again, execute: rmconfig key | +---------------------------------------------------------------------+ GGSN.DNS "8.8.8.8" ("") GGSN.Firewall.Enable "0" ("1") UMTS.Radio.Band "850" ("900") UMTS.Radio.RxGain "10" ("57")

+---------------------------------------------------------------------+ | INFO : Custom/Deprecated Key/Value Pairs [key current-value] | | To clean up any extraneous keys, execute: rmconfig key | +---------------------------------------------------------------------+ UMTS.Identity.ShortName "kudos"

I am still not able to detect the signal on my phone. I will appreciate if you can clarify the following question.

I have a programmable USIM card from Sysmocom and a USB reader as well.

my objective is to modify the authentication procedure both on the USIM as well as the one on Openbts-UMTS.

for example, add challenge response, generate a nonce send it to the card, which can perform a XOR operation and revert with it answer.

Is this possible? Any advice on how to proceed, please?

any books or tutorials that can help me will be most welcomed.

Cheers, Domi

On Fri, Jun 2, 2017 at 4:59 PM, Keskebeu notifications@github.com wrote:

if you are testing your network in 900 you have to have a phone compatible with 900 band. now you have to configure out the noise.

in OpenBTS-UMTSCLI do

noise and than do rxgain show me what is it coming back with.

You now have to make sure there is no noise in your radio. Make sure you have the antennas set up in a 90 angle with each-other.

if you have a message saying uplink connectivity is not possible.Than your phone cannot connect see the antenna by the noise generated around you and also noise floor. you have to make sure that noise generated by the MS RSSI is higher in value than floor noise otherwise you will not be able to connect to your phones or transfer data, calls or sms.

Study some of the radio functions. as you have to know what frequency you can use. Since US uses 800 or 850 is better to test it at 900 european standard and if you are in Europe do vice-versa , so you don't conflict any other frequency and have Intelligence officers from energy department looking around your house for RF exposure.

with the usrp you can factory calibrate it by command in the CLI. Theres a book OpenBTS if you read that you will see what I am talking about. Plus if you are good in math you can figure it out fast enough.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/RangeNetworks/OpenBTS-UMTS/issues/2#issuecomment-305813017, or mute the thread https://github.com/notifications/unsubscribe-auth/AY7cXy8ASKoQAOHhZ9_b4tCmGzYkMwjIks5sACNGgaJpZM4Dh9I5 .

dkogue commented 7 years ago

maybe u can help me. I am running OpenBTS_UMTS on Ubuntu 16 but can not see the signal when I check on my Nexus phone. here are my audit logs: /OpenBTS$ sudo ./OpenBTS-UMTS 1498833143.790579 140246743963456:

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-06-02T10:56:56 d528034ac8 CommonLibs:d528034ac8 "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 140246743963456 16:32:23.8 OpenBTS-UMTS.cpp:166:main: OpenBTS-UMTS (re)starting, ver 1.0-master build date Jun 2 2017 1498833143.812509 140246743963456: 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 140246743963456 16:32:23.8 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 140246743963456 16:32:23.8 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 140246743963456 16:32:23.8 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 140246743963456 16:32:23.8 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 140246743963456 16:32:23.8 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 ::= {

2 } logicalChannelList: } } 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 ::= { } logicalChannelList: } } 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 ::= { } logicalChannelList: } } 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 140246743963456 16:32:23.8 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 140246743963456 16:32:23.8 UMTSPhCh.cpp:654:chConflict: Attempt to reserve channel: sf=256 chcode=1 which conflicts with reserved channel: sf=128 chcode=0 1498833143.828134 140246743963456: Starting the transceiver... linux; GNU C++ version 5.3.1 20151219; Boost_105800; UHD_003.009.002-0-unknown ** 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 -- Asking for clock rate 16.000000 MHz... -- Actually got clock rate 16.000000 MHz. -- Performing timer loopback test... pass -- Performing timer loopback test... pass -- Setting master clock rate selection to 'automatic'. -- Asking for clock rate 32.000000 MHz... -- Actually got clock rate 32.000000 MHz. -- Performing timer loopback test... pass -- Performing timer loopback test... pass -- Asking for clock rate 25.000000 MHz... -- Actually got clock rate 25.000000 MHz. -- Performing timer loopback test... pass -- Performing timer loopback test... pass ** Device ready RTNETLINK answers: File exists 1498833149.691751 140246743963456: system ready 1498833149.691792 140246743963456: use the OpenBTS-UMTSCLI utility to access CLI OpenBTS> audit +---------------------------------------------------------------------+ | ERROR : Invalid Values [key current-value (default)] | | To use the default value again, execute: rmconfig key | +---------------------------------------------------------------------+ GGSN.DNS "8.8.8.8 " ("") SMS.MIMEType "application/vnd.3gpp.sms" ("application/vnd.3gpp.sms") UMTS.PRACH.SF "32" ("32") UMTS.RLC.TransmissionBufferSize "10000000" ("1000000") UMTS.Radio.C0 "10838" ("3050") UMTS.SCCPCH.SF "64" ("64") +---------------------------------------------------------------------+ | WARNING : Site Values Which Are Still Default [key current-value] | | These should be set to fit your installation: config key value | +---------------------------------------------------------------------+ GSM.Identity.BSIC.BCC "2" GSM.Identity.LAC "1000" GSM.Identity.MCC "001" GSM.Identity.MNC "01" GSM.RRLP.SEED.LATITUDE "37.777423" GSM.RRLP.SEED.LONGITUDE "-122.39807" UMTS.Identity.CI "10" UMTS.Identity.LAC "132" UMTS.Identity.MCC "001" UMTS.Identity.MNC "01" UMTS.Identity.URAI "100" +---------------------------------------------------------------------+ | INFO : Non-Default Values [key current-value (default)] | | To use the default value again, execute: rmconfig key | +---------------------------------------------------------------------+ GGSN.DNS "8.8.8.8 " ("") GGSN.Firewall.Enable "0" ("1") UMTS.RLC.TransmissionBufferSize "10000000" ("1000000") UMTS.Radio.Band "2100" ("900") UMTS.Radio.RxGain "56" ("57") +---------------------------------------------------------------------+ | INFO : Custom/Deprecated Key/Value Pairs [key current-value] | | To clean up any extraneous keys, execute: rmconfig key | +---------------------------------------------------------------------+ UMTS.Identity.ShortName "01001" On Fri, Jun 2, 2017 at 2:01 PM, Wola Dominique wrote: > Thank you for your feedback! managed to solved this earlier but having > below error now. > please help! > > Loading ezusb.ihx firmware file... resetting EZ-USB > sudo: ./RAD1Cmd: command not found > 3G PLL register update utility for 61.44Mhz > Begin updating Si5338 registers > sudo: ./RAD1Cmd: command not found > MultiSynth2 frequency Conf MS2_P1[7:0] > sudo: ./RAD1Cmd: command not found > MultiSynth2 frequency Conf MS2_P1[15:8] > sudo: ./RAD1Cmd: command not found > MultiSynth2 frequency Conf MS2_P2[5:0] MS2_P1[17:18] > Setting clock output 2 to 61.44Mhz complete > sudo: ./RAD1Cmd: command not found > MultiSynth2 frequency Conf MS2_P3[7:0] > sudo: ./RAD1Cmd: command not found > MultiSynth3 frequency Conf MS3_P1[7:0] > sudo: ./RAD1Cmd: command not found > MultiSynth3 frequency Conf MS3_P1[15:8] > sudo: ./RAD1Cmd: command not found > MultiSynth3 frequency Conf MS3_P2[5:0] MS3_P1[17:18] > sudo: ./RAD1Cmd: command not found > MultiSynth3 frequency Conf MS3_P3[7:0] > Setting clock output 3 to 61.44Mhz complete > Completed 61.44MHz configuration... soft resetting > sudo: ./RAD1Cmd: command not found > Soft reset complete... exiting > > > On Fri, Jun 2, 2017 at 1:52 PM, Keskebeu wrote: > >> I can see that you need ASN library >> https://github.com/Keskebeu/asn1c-0.9.23.zip >> go to this website and click on that link, I made this easy for people. >> And download this zip file: asn1c-f5ab8ba08c82d6283fe35a96 >> 78b6bac4e1fe2337.zip. >> >> Unzip this file and move it in the /usr/src folder. >> >> make sure you add sudo if you are not root. >> >> compile asn1c library (where you unziped the folder) and do: >> ./configure >> make >> make install >> ldconfig. >> >> , than go back to the OpenBTS-UMTS folder and do: >> ./configure >> make clean >> make >> make install >> ldconfig >> >> — >> You are receiving this because you commented. >> Reply to this email directly, view it on GitHub >> , >> or mute the thread >> >> . >> > >
JackShadows commented 7 years ago

Board: USRP-B210 System: OpenBTS-UMTS. Probably i have same problem as you. Looks like openBTS-UMTS started, it connected to usrp and download FW, then LED start blinking. But then scanning networks there is nothing. Did you found reason why so happened ??????

Cannot open TMSITable database at /var/run/OpenBTS-UMTS-TMSITable.dbEMERG 139855594477376 14:51:39.0 TMSITable.cpp:66:TMSITable: Cannot open TMSITable database at /var/run/OpenBTS-UMTS-TMSITable.db: unable to open database file ALERT 139855594477376 14:51:39.0 TransactionTable.cpp:641:TransactionTable: Cannot open Transaction Table database at /var/run/OpenBTS-UMTS-TransactionTable.db: unable to open database file 1503489099.019925 139855594477376:

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-08-23T13:44:23 d528034ac8 CommonLibs:d528034ac8 "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.

sqlite3_run_query failed: INSERT OR REPLACE INTO CONFIG (KEYSTRING,VALUESTRING,OPTIONAL,COMMENTS) VALUES ("Log.Level","NOTICE",1,'Default logging level when no other level is defined for a file.'): attempt to write a readonly database ALERT 139855594477376 14:51:39.0 OpenBTS-UMTS.cpp:166:main: OpenBTS-UMTS (re)starting, ver 1.0-master build date Aug 23 2017 1503489099.036520 139855594477376: 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 139855594477376 14:51:39.0 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 139855594477376 14:51:39.0 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 139855594477376 14:51:39.0 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 139855594477376 14:51:39.0 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 139855594477376 14:51:39.0 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 ::= {

2 } logicalChannelList: } } 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 ::= { } logicalChannelList: } } 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 ::= { } logicalChannelList: } } 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 139855594477376 14:51:39.0 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 139855594477376 14:51:39.0 UMTSPhCh.cpp:654:chConflict: Attempt to reserve channel: sf=256 chcode=1 which conflicts with reserved channel: sf=128 chcode=0 1503489099.057899 139855594477376: Starting the transceiver... linux; GNU C++ version 5.3.1 20151219; Boost_105800; UHD_003.009.002-0-unknown ** Configuring logger sqlite3_run_query failed: INSERT OR REPLACE INTO CONFIG (KEYSTRING,VALUESTRING,OPTIONAL,COMMENTS) VALUES ("Log.Level","NOTICE",1,'Default logging level when no other level is defined for a file.'): attempt to write a readonly database ** Using internal clock reference ** Searching for USRP device -- Loading firmware image: /usr/share/uhd/images/usrp_b200_fw.hex... -- Detected Device: B210 -- Loading FPGA image: /usr/share/uhd/images/usrp_b210_fpga.bin... 10%ALERT 139855594477376 14:51:50.0 TRXManager.cpp:66:sendCommandPacket: RSP response ALERT 139855594477376 14:51:50.0 TRXManager.cpp:81:powerOff: POWEROFF failed with status -1 19%ALERT 139855594477376 14:51:56.0 TRXManager.cpp:66:sendCommandPacket: RSP response ALERT 139855594477376 14:51:56.0 TRXManager.cpp:412:tune: TXTUNE failed with status -1 24%ALERT 139855483438848 14:51:59.0 TRXManager.cpp:258:clockHandler: TRX clock interface timed out, assuming TRX is dead. 28%ALERT 139855594477376 14:52:02.0 TRXManager.cpp:66:sendCommandPacket: RSP response ALERT 139855594477376 14:52:02.0 TRXManager.cpp:112:setRxGain: SETRXGAIN failed with status -1 ALERT 139855483438848 14:52:02.0 TRXManager.cpp:258:clockHandler: TRX clock interface timed out, assuming TRX is dead. 33%ALERT 139855483438848 14:52:05.0 TRXManager.cpp:258:clockHandler: TRX clock interface timed out, assuming TRX is dead. 38%ALERT 139855594477376 14:52:08.0 TRXManager.cpp:66:sendCommandPacket: RSP response ALERT 139855594477376 14:52:08.0 TRXManager.cpp:499:powerOn: POWERON failed with status -1 ALERT 139855483438848 14:52:08.0 TRXManager.cpp:258:clockHandler: TRX clock interface timed out, assuming TRX is dead. 42%ALERT 139855483438848 14:52:11.0 TRXManager.cpp:258:clockHandler: TRX clock interface timed out, assuming TRX is dead. 47%ALERT 139855594477376 14:52:14.0 TRXManager.cpp:66:sendCommandPacket: RSP response ALERT 139855594477376 14:52:14.0 TRXManager.cpp:91:setPower: SETPOWER failed with status -1 ALERT 139855483438848 14:52:14.0 TRXManager.cpp:258:clockHandler: TRX clock interface timed out, assuming TRX is dead. ALERT 139855594477376 14:52:14.3 miniggsn.cpp:632:miniggsn_init: Cound not open tun device:sgsntun sh: 1: : not found binding name to cmd datagram socket: Permission denied ALERT 139855594477376 14:52:14.3 OpenBTS-UMTS.cpp:271:main: cannot bind socket for CLI at ��; 48%Ошибка сегментирования (сделан дамп памяти) user@pc-1153:/OpenB done -- Operating over USB 2. -- Detecting internal GPSDO.... No GPSDO found -- 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 -- Asking for clock rate 16.000000 MHz... -- Actually got clock rate 16.000000 MHz. -- Performing timer loopback test... pass -- Performing timer loopback test... pass -- Setting master clock rate selection to 'automatic'. -- Asking for clock rate 32.000000 MHz... -- Actually got clock rate 32.000000 MHz. -- Performing timer loopback test... pass -- Performing timer loopback test... pass -- Asking for clock rate 25.000000 MHz... -- Actually got clock rate 25.000000 MHz. -- Performing timer loopback test... pass -- Performing timer loopback test... pass ** Device ready ^C user@pc-1153:/OpenBTS$ ./OpenBTS-UMTS Cannot open TMSITable database at /var/run/OpenBTS-UMTS-TMSITable.dbEMERG 140414317197120 14:54:39.4 TMSITable.cpp:66:TMSITable: Cannot open TMSITable database at /var/run/OpenBTS-UMTS-TMSITable.db: unable to open database file ALERT 140414317197120 14:54:39.4 TransactionTable.cpp:641:TransactionTable: Cannot open Transaction Table database at /var/run/OpenBTS-UMTS-TransactionTable.db: unable to open database file bind() failed: Address already in use terminate called after throwing an instance of 'SocketError' Аварийный останов (сделан дамп памяти)
Keskebeu commented 7 years ago

Hello fix the parameter of Rxgain power txatten and make sure your phones are not iphone 4g or LTE otherwise the phone will not scan for it since the radio is locked to 4g and LTE. If the phones radio is locked you wont be able to connect to the device. I ran tests today again and was successful. If I were to explain would take a lot of time, but let me know how you guys do and will help you. Take care.

peterm2109 commented 6 years ago

please help:

root@maestria:/home/maestria/OpenBTS-UMTS/TransceiverRAD1# ./clkit_61_44mhz.sh Loading ezusb.ihx firmware file... resetting EZ-USB sudo: imposible resolver el anfitrión maestria sudo: ./RAD1Cmd: orden no encontrada 3G PLL register update utility for 61.44Mhz Begin updating Si5338 registers sudo: imposible resolver el anfitrión maestria sudo: ./RAD1Cmd: orden no encontrada MultiSynth2 frequency Conf MS2_P1[7:0] sudo: imposible resolver el anfitrión maestria sudo: ./RAD1Cmd: orden no encontrada MultiSynth2 frequency Conf MS2_P1[15:8] sudo: imposible resolver el anfitrión maestria sudo: ./RAD1Cmd: orden no encontrada MultiSynth2 frequency Conf MS2_P2[5:0] MS2_P1[17:18] Setting clock output 2 to 61.44Mhz complete sudo: imposible resolver el anfitrión maestria sudo: ./RAD1Cmd: orden no encontrada MultiSynth2 frequency Conf MS2_P3[7:0] sudo: imposible resolver el anfitrión maestria sudo: ./RAD1Cmd: orden no encontrada MultiSynth3 frequency Conf MS3_P1[7:0] sudo: imposible resolver el anfitrión maestria sudo: ./RAD1Cmd: orden no encontrada MultiSynth3 frequency Conf MS3_P1[15:8] sudo: imposible resolver el anfitrión maestria sudo: ./RAD1Cmd: orden no encontrada MultiSynth3 frequency Conf MS3_P2[5:0] MS3_P1[17:18] sudo: imposible resolver el anfitrión maestria sudo: ./RAD1Cmd: orden no encontrada MultiSynth3 frequency Conf MS3_P3[7:0] Setting clock output 3 to 61.44Mhz complete Completed 61.44MHz configuration... soft resetting sudo: imposible resolver el anfitrión maestria sudo: ./RAD1Cmd: orden no encontrada Soft reset complete... exiting

I already did this:

You dont have to use TransceiverRAD1at all. Thats by default RangeNetworks radio for any RangeNetwork project.

You now have to go to OpenBTS-UMTS folder go to apps and do as root $vim OpenBTS-UMTS.cpp or nano OpenBTS-UMTS.cpp (its better to use vim because you can go a specific line) and find the line

const char* transceiverPath = "./transceiver" and change it to ./TransceiverUHD/transceiver/

if this does not work leave it as it was before and instead do:

dada@dada-VPCEH2C1E:~/Master/OpenBTS-UMTS/TransceiverUHD# cp transceiver /home/Master/OpenBTS-UMTS/apps

and than do the following in the apps directory

ln -sf transceiver transceiver

and now you are ready to go.

but in the step "ln -sf transceiver transceiver" give me this error: ln: 'transceiver' y 'transceiver' son el mismo fichero

please help

Keskebeu commented 6 years ago

You will have to do either one of them. After all the files have been made by make command , the transceiver is build in the transceiverUHD folder. All you have to do is copy transceiver from its current folder to apps folder.

In the apps folder delete that transceiver file already being there since you are using uhd(because that's RAD1 transceiver by default. Once you delete that file you copy paste transceiver from transceiveruhd folder to apps.

And than do ln -sf transceiver. And it should be running.

Another way of doing is changing the path of transceiver in the file I described above, but you have to run ./configure after changing the path for it to work otherwise it will still be the same.

The reason why you are getting that error is because in the apps folder there are two files named transceiver. Once you delete that file or move it somewhere else you will be able to paste the new transceiver file from transceiveruhd to apps and be able to do ln -sf transceiver.

Keskebeu commented 6 years ago

content://media/external/file/12787