RangeNetworks / OpenBTS-UMTS

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

Unable to see my OpenBTS-UMTS network #9

Open dkogue opened 7 years ago

dkogue commented 7 years ago

I am running OpenBTS_UMTS on Ubuntu 16 but can not see the signal when I check on my Nexus and Iphine6 phones. 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"
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 d528034 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'

EugeneBogush commented 7 years ago

-- Operating over USB 2.0 need mode USB 3.0!!!(maybe need to change cable)

dkogue commented 7 years ago

you first need to make sure your USB port is a version tree and the antennas must form 90 degree very important as well. also, add the identity key when adding a subscriber because of the mutual authentication. start asterisk before Openbts-UMTS.

Keskebeu commented 6 years ago

Asterisk doesnt have anything to do with this. Smqueue and subruscribers registry sipauthserve should be run before running umts. In this guys case his fpga was loading as the system started. Meaning he is running his radio on usb 2.0 instead of 3.0

The speed in which umtz started building passed over the speed of loading fpga, so in this case the transceiver is still running but its not detecting the radio because of failure to load fpga on time.

killall transceiver command and restarting openbts-umts solves this issue. Take care.

gmg2719 commented 6 years ago

You should use a short USB cable on USB2.0 PC, or use USB3.0 PC is prefered. I confront this issue. When I use a shorter USB cable. It shows Operating over USB 3 .Everything is OK

dominicantonyv commented 6 years ago

Hi

I am facing the same issue...the OpenBTS-UMTS network is not showing on my mobile when I scan for available networks. The source code build was fine. When I start OpenBTS, even the USRP (Ettus N210) is generating the beacon signal it seems. I have analysed using a spectrum analyser. But my test mobile (Mi A1) is not showing the OpenBTS-UMTS network.

My OS is Ubuntu 14.04 LTS.

@dkogue @JackShadows Have you succeeded in receiving the network on your phone. If yes, how did you achieve it. Could anyone please help me. Any sort of help is highly appreciated. Thanks

dkogue commented 6 years ago

Can you check if 3G is enable on your phone. as well make sure your phone can operate at the same frequency as the one your are propagating at.

hope that can help, good luck :)

On Apr 24, 2018, at 10:21 AM, dominicantonyv notifications@github.com wrote:

Hi

I am facing the same issue...the OpenBTS-UMTS network is not showing on my mobile when I scan for available networks. The source code build was fine. When I start OpenBTS, even the USRP (Ettus N210) is generating the beacon signal it seems. I have analysed using a spectrum analyser. But my test mobile (Mi A1) is not showing the OpenBTS-UMTS network.

My OS is Ubuntu 14.04 LTS.

@dkogue https://github.com/dkogue @JackShadows https://github.com/JackShadows Have you succeeded in receiving the network on your phone. If yes, how did you achieve it. Could anyone please help me. Any sort of help is highly appreciated. Thanks

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

Keskebeu commented 6 years ago

Is your phone on gsm 900? Most of the phones in us are 850/1900. Umts starts on gsm 900 for a test network. So you won't be able to see.

dominicantonyv commented 6 years ago

@dkogue yes 3G is enabled in my phone. Actually my phone supports 4G too. I am from India, hence my phone operates in band 900.

dominicantonyv commented 6 years ago

@Keskebeu Yes my phone is on GSM 900 band. I am from India, so here the supported band is 900. Even the band is set to 900 in OpenBTS-UMTS.db with ARFCN 3050. Why I wouldn't be able to see the network.

Keskebeu commented 6 years ago

Is your phone unlocked?

Keskebeu commented 6 years ago

If it is select a different arfcn and try it. Yoi gotta play with it for a little bit. Dont keep you phone too close to the bts. Plus lower your gain and attenuation to 0 as this can cause saturation on the network and you wont be able to see it.

Keskebeu commented 6 years ago

screenshot_2018-02-03-17-05-37

Keskebeu commented 6 years ago

Power gain is at 20 and txatten is 0

dominicantonyv commented 6 years ago

I tried with different ARFCN, reducing Gain and attenuation, still no network is shown.

Power gain is at 20 and txatten is 0

@Keskebeu Gain means UMTS.Radio.RxGain and txatten means UMTS.Radio.PowerManager.MaxAttenDB...right?

Could you guys please share the build instructions you were following. Have you done any configuration changes or code changes after building the source code.

Also what about smqueue and asterisk? Are those required for network detection?

Also the OpenBTS-UMTS and transceiver runs automatically on system startup. Is there any way to disable this autostartup?

dominicantonyv commented 6 years ago

Is your phone unlocked?

@Keskebeu yes, my phone is unlocked

Keskebeu commented 6 years ago

No code change just changed interface from eth0 to wlan0 in my case. Try that in iptables.rules. change it to your interface.

Keskebeu commented 6 years ago

If the transceiver starts before the load of fpga than you gotta shut it down. Killall transceiver. And restart it again.

dominicantonyv commented 6 years ago

No code change just changed interface from eth0 to wlan0 in my case. Try that in iptables.rules. change it to your interface.

@Keskebeu I thought iptables.rules is only for data (i mean 3G). Is it required for detecting the network. Also where did you get the build instructions for OpenBTS-UMTS?

Keskebeu commented 6 years ago

I said I didnt change the code but the iptables. No it is not needed to detect. You are using usb 3.0 right?

dominicantonyv commented 6 years ago

I am not using any USB port. Sorry to ask, what USB port is required for?

Keskebeu commented 6 years ago

You are using Network series my bad.

On Apr 25, 2018 9:00 AM, "dominicantonyv" notifications@github.com wrote:

I am not using any USB port. Sorry to ask, what USB port is required for?

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

dominicantonyv commented 6 years ago

I am using Ettus Research N210 USRP which is connected to my PC via ethernet cable.

dominicantonyv commented 6 years ago

You are using Network series my bad.

Yes.

May I ask, how can we see the downlink power in OpenBTS-UMTS? In OpenBTS 2G, we had the option to enter command "power" and it returns the current downlink power. In OpenBTS-UMTS, "power" command exits the code.

dkogue commented 6 years ago

can you try with USB 3 connector..it can be the source of your problem.

On Apr 25, 2018, at 3:02 PM, dominicantonyv notifications@github.com wrote:

You are using Network series my bad.

Yea

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/RangeNetworks/OpenBTS-UMTS/issues/9#issuecomment-384278363, or mute the thread https://github.com/notifications/unsubscribe-auth/AY7cXxxNZdyw-TzeunopStKm6LR_U1-kks5tsHPygaJpZM4OKr9I.

dominicantonyv commented 6 years ago

@Keskebeu Could you please provide the link or doc of the build instructions you have followed? Also I am not much clear of the subscriberRegistry. Do I need to run it before running OpenBTS-UMTS?

dominicantonyv commented 6 years ago

can you try with USB 3 connector..it can be the source of your problem.

There is no USB port in this USRP.

dominicantonyv commented 6 years ago

But USRP and its communication with PC is fine I think, for I have successfully ran OpenBTS 2G using the same.

dominicantonyv commented 6 years ago

@Keskebeu Are you able to see the network consistently or is it like sometimes it shows up sometimes it doesnt?

What all could be the factors affecting the network detection?

Keskebeu commented 6 years ago

No i know i thought you were using bus usrp. Theres no usb on that one. I consistenly see it. All the time.

On Wed, Apr 25, 2018, 9:19 AM dominicantonyv notifications@github.com wrote:

@Keskebeu https://github.com/Keskebeu Are you able to see the network consistently or is it like sometimes it shows up sometimes it doesnt?

What all could be the factors affecting the network detection?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/RangeNetworks/OpenBTS-UMTS/issues/9#issuecomment-384283483, or mute the thread https://github.com/notifications/unsubscribe-auth/AYP2GEGZNZNVbSe8i9P11ob-y2B9ATcnks5tsHfvgaJpZM4OKr9I .

Keskebeu commented 6 years ago

Do you have any wbx daughter board mounted on that radio?

On Tue, Apr 24, 2018, 10:56 AM dominicantonyv notifications@github.com wrote:

@dkogue https://github.com/dkogue yes 3G is enabled in my phone. Actually my phone supports 4G too. I am from India, hence my phone operates in band 900.

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

dominicantonyv commented 6 years ago

Do you have any wbx daughter board mounted on that radio?

Yes I think so. When I run " uhd_usrp_probe", I get the following response


/ Device: USRP2 / N-Series Device _____ / Mboard: N210r4 hardware: 2577 mac-addr: 00:80:2f:0a:d1:24 ip-addr: 192.168.10.2 subnet: 255.255.255.255 gateway: 255.255.255.255 gpsdo: none serial: F31574 FW Version: 12.4 FPGA Version: 11.1
Time sources: none, external, external, mimo
Clock sources: internal, external, mimo
Sensors: mimo_locked, ref_locked
_____
/
RX DSP: 0
Freq range: -50.000 to 50.000 MHz
_____
/
RX DSP: 1
Freq range: -50.000 to 50.000 MHz
_____
/
RX Dboard: A
ID: WBX v3, WBX v3 + Simple GDB (0x0057)
Serial: F2FAA8
_____
/
RX Frontend: 0
Name: WBXv3 RX+GDB
Antennas: TX/RX, RX2, CAL
Sensors: lo_locked
Freq range: 68.750 to 2200.000 MHz
Gain range PGA0: 0.0 to 31.5 step 0.5 dB
Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz
Connection Type: IQ
Uses LO offset: No
_____
/
RX Codec: A
Name: ads62p44
Gain range digital: 0.0 to 6.0 step 0.5 dB
Gain range fine: 0.0 to 0.5 step 0.1 dB
_____
/
TX DSP: 0
Freq range: -50.000 to 50.000 MHz
_____
/
TX Dboard: A
ID: WBX v3 (0x0056)
Serial: F2FAA8
ID: WBX + Simple GDB, WBX v3 + Simple GDB, WBX v4 + Simple GDB, WBX-120 + Simple GDB (0x004f)
Serial: 0
_____
/
TX Frontend: 0
Name: WBXv3 TX+GDB
Antennas: TX/RX, CAL
Sensors: lo_locked
Freq range: 68.750 to 2200.000 MHz
Gain range PGA0: 0.0 to 31.0 step 1.0 dB
Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz
Connection Type: IQ
Uses LO offset: No
_____
/
TX Codec: A
Name: ad9777
Gain Elements: None
Keskebeu commented 6 years ago

One reason is that you could be operating on a nearby operator frequency. Yor frequency gets outbound ed by the operators frequency. Try another ARFCN with mnc mcc codes not being taken by another operator.

On Fri, Apr 27, 2018, 3:13 AM dominicantonyv notifications@github.com wrote:

Do you have any wbx daughter board mounted on that radio?

Yes I think so. When I run " uhd_usrp_probe", I get the following response

/ Device: USRP2 / N-Series Device _____ / Mboard: N210r4 hardware: 2577 mac-addr: 00:80:2f:0a:d1:24 ip-addr: 192.168.10.2 subnet: 255.255.255.255 gateway: 255.255.255.255 gpsdo: none serial: F31574 FW Version: 12.4 FPGA Version: 11.1
Time sources: none, external, external, mimo
Clock sources: internal, external, mimo
Sensors: mimo_locked, ref_locked
_____
/
RX DSP: 0
Freq range: -50.000 to 50.000 MHz
_____
/
RX DSP: 1
Freq range: -50.000 to 50.000 MHz
_____
/
RX Dboard: A
ID: WBX v3, WBX v3 + Simple GDB (0x0057)
Serial: F2FAA8
_____
/
RX Frontend: 0
Name: WBXv3 RX+GDB
Antennas: TX/RX, RX2, CAL
Sensors: lo_locked
Freq range: 68.750 to 2200.000 MHz
Gain range PGA0: 0.0 to 31.5 step 0.5 dB
Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz
Connection Type: IQ
Uses LO offset: No
_____
/
RX Codec: A
Name: ads62p44
Gain range digital: 0.0 to 6.0 step 0.5 dB
Gain range fine: 0.0 to 0.5 step 0.1 dB
_____
/
TX DSP: 0
Freq range: -50.000 to 50.000 MHz
_____
/
TX Dboard: A
ID: WBX v3 (0x0056)
Serial: F2FAA8
ID: WBX + Simple GDB, WBX v3 + Simple GDB, WBX v4 + Simple GDB,

WBX-120 + Simple GDB (0x004f) | | | Serial: 0 | | | _____ | | | / | | | | TX Frontend: 0 | | | | Name: WBXv3 TX+GDB | | | | Antennas: TX/RX, CAL | | | | Sensors: lolocked | | | | Freq range: 68.750 to 2200.000 MHz | | | | Gain range PGA0: 0.0 to 31.0 step 1.0 dB | | | | Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz | | | | Connection Type: IQ | | | | Uses LO offset: No | | | ____ | | | / | | | | TX Codec: A | | | | Name: ad9777 | | | | Gain Elements: None

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/RangeNetworks/OpenBTS-UMTS/issues/9#issuecomment-384885945, or mute the thread https://github.com/notifications/unsubscribe-auth/AYP2GFYVHkGrZCl0wUzD-vpNuU3_6Feoks5tssUEgaJpZM4OKr9I .

Keskebeu commented 6 years ago

Another way to look at it is to check if the phone supports the band indicated by range operating over gsm 900.

On Tue, Apr 24, 2018, 10:56 AM dominicantonyv notifications@github.com wrote:

@dkogue https://github.com/dkogue yes 3G is enabled in my phone. Actually my phone supports 4G too. I am from India, hence my phone operates in band 900.

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

peterm2109 commented 6 years ago

@dominicantonyv Excuse my meddling ... What type of SIM card are you using? with my cell phone it happened to me that when I used a certain type of SIM card, I could not detect the UMTS network

Keskebeu commented 6 years ago

That doesn't mean anything. I see my network with my usim and I can attempt to connect with it. Sim card doesn't search for network the radio does it.

On Apr 28, 2018 11:49 PM, "peterm2109" notifications@github.com wrote:

@dominicantonyv https://github.com/dominicantonyv Excuse my meddling ... What type of SIM card are you using? with my cell phone it happened to me that when I used a certain type of SIM card, I could not detect the UMTS network

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/RangeNetworks/OpenBTS-UMTS/issues/9#issuecomment-385223572, or mute the thread https://github.com/notifications/unsubscribe-auth/AYP2GKFhaIeu5xM1OhKtJPu3yK-3RLjBks5ttThBgaJpZM4OKr9I .

dominicantonyv commented 6 years ago

@Keskebeu @peterm2109 I use a commercial LTE sim from the operator Airtel. My phone supports the UMTS frequency band. I am even able to avail 3G service offered by my home operator (Airtel). The MCC and MNC I use is 001 and 01 respectively. Anyway this MNC and MCC will not be used by any other operators I hope as these are meant for test networks.

dominicantonyv commented 6 years ago

@peterm2109 How did you finally succeeded in detecting the network? Could you please brief me the steps you have taken. Also I would like to know configuration you have set..like UMTS.Radio.Band, UMTS.Radio.C0, UMTS.Radio.RxGain, TRX.TxAttenOffset, UMTS.Radio.PowerManager.MinAttenDB, UMTS.Radio.PowerManager.MaxAttenDB, UMTS.Identity.MCC, UMTS.Identity.MNC

Keskebeu commented 6 years ago

@dominicantonyv

Are you using a gigabyte Ethernet cable? You sure your not using a adsl or phone cable just checking ?

peterm2109 commented 6 years ago

@dominicantonyv I don't have much experience in this topic, in fact, in the network that I have implemented there are several things that don't work. @Keskebeu 's comments can be much more useful than mine. What I can tell you is that for example, with my cell phone I see the network and I connect to it through a sim card 16-1 supersim. But with my at&t sim card, the cell phone does not detect the network. Another thing I can tell you is that OpenBTS-UMTS does not support USIM cards. You may see the UMTS network, but you will not be able to register. When you get a compatible sim card to connect to the network, keep in mind that when you are going to write the IMSI and Ki values, the algorithm you should use is comp128v1. good luck.

Keskebeu commented 6 years ago

I will send you mines by the weekend but make sure you are using a gigabyte internet cable. When i used mine in 2.0 usb = 500mb cable i could not see the network. Bts starts but 2.0 interface and 500mb cable won't send the data at the speed required by the bts. If you are using 900 mhz frequency make sure your phone supports the actual band.

In my unlocked 3g iphone umts does not show my wcdma test channel only umts. Usually wcdma in 4g outbands your wcdma band. You dont have to select the specific 3g option only let it run on 4g the phones radio should be able to pick it up. My network was visible in all options on the phones supporting wcdma. If you select 3g only you might not let the phone's radio to pick up every signal.

In this case your phone should support HSPA or HSPA+. (WCDMA)

Theres another file which describes the actual band i think its 4 or 5 for umts 900. I will look and let you know. I have not been doing this lately as I have been waiting for a gpsdo to come by.

In your case you are using a wbx board for distributing rf frequency. Make sure your antennas are connected to the wbx board not the radio. (But you said your were succesful with openbts so you dont have to worry) but just an advice.

In your case I would recommend looking at what frequencies the carriers around you transmit and receive, if your selected arfcn corrensponds close to the frequency of the carrier it won't be visible.

Keskebeu commented 6 years ago

@dominicantonyv Ok man so txatten is 0 rxgain is 57 and do not connect the rx antenna to the wbx board because thats what causing saturation in your system to not be visible. It happens the same with my radio when I connect both antennas. UMTS is made to transmit and receive from trx port. Take care.

If you guys are looking to buy a gpsdo for better call functionality I recently bought a cheap gpsdo from china company which has pretty much replicated the ettus b210. I bought their gpsdo for 150$ and it works like a charm(190$now), (compared to 690$ from ettus website).

take care and let me know if this solved your issue.

dominicantonyv commented 6 years ago

@peterm2109 Hey Peter, thanks for the tip. I think my sim could be a problem too. I am not sure if my sim is USIM or not? I will find it out. Meanwhile could you please help me to get a compatible sim and a sim writer. Like if you have any link to buy online, please share.

@Keskebeu Yes I am using a gigabyte ethernet cable, Thanks :-) I have tried with arfcn no other operators use in my area but still the mobile failed to detect the OpenBTS-UMTS network. I will try without the antennas and let you know what happend.

Keskebeu commented 6 years ago

Try wothout the rx antenna. Trx should be fine.

On Wed, May 9, 2018, 11:34 AM dominicantonyv notifications@github.com wrote:

@peterm2109 https://github.com/peterm2109 Hey Peter, thanks for the tip. I think my sim could be a problem too. I am not sure if my sim is USIM or not? I will find it out. Meanwhile could you please help me to get a compatible sim and a sim writer. Like if you have any link to buy online, please share.

@Keskebeu https://github.com/Keskebeu Yes I am using a gigabyte ethernet cable, Thanks :-) I have tried with arfcn no other operators use in my area but still the mobile failed to detect the OpenBTS-UMTS network. I will try without the antennas and let you know what happend.

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

peterm2109 commented 6 years ago

@dominicantonyv A simple way to check if your card is USIM, is trying to decode the secret Ki key with the woron scan program ... it is very difficult for a SIM from any telecom provider not to be USIM ... so you can authenticate the UE In the UMTS radiobase, you must get a compatible SIM and write the IMSI and Ki values ... good luck

Smart Card Writer: https://www.ebay.com/itm/PC-SC-Contact-IC-Chip-Smart-Card-Reader-Writer-ACR38U-I1-USB- 5pcs-SLE5542-Cards/131343378011?ssPageName=STRK%3AMEBIDX %3AIT&_trksid=p2055119.m1438.l2649

https://www.ebay.com/itm/ACR38U-I1-Protable-Contact-Smart-IC-Chip-Card-Reader-Writer-Support- CT-API-M2OE/161899321970?ssPageName=STRK%3AMEBIDX %3AIT&_trksid=p2055119.m1438.l2649

https://www.ebay.com/itm/PC-SC-Contact-IC-Chip-Smart-Card-Reader-Writer-ACR38U-I1-USB-5- Cards-Hot-M2OG/172011462145?ssPageName=STRK%3AMEBIDX %3AIT&_trksid=p2055119.m1438.l2649

https://www.ebay.com/itm/ACR38U-R4-PC-SC-Contact-IC-Chip-Smart-Card-Reader-Writer-Support- SIM-Micro-Card/282393509205?ssPageName=STRK%3AMEBIDX %3AIT&_trksid=p2055119.m1438.l2649

SuperSIM 16-1:

https://www.ebay.com/p/16-in-1-Max-SIM-Cell-Phone-Magic-Super-Card-Backup-W-Gyth/852994001? iid=142210528523&_trkparms=aid%3D222007%26algo%3DSIM.MBE%26ao%3D2%26asc%3D41375%26meid %3Db4d64676982f48a0b36cb4fc5aeb0fd9%26pid%3D100005%26rk%3D5%26rkt%3D6%26mehot%3Dpp%26sd %3D141535450979&_trksid=p2047675.c100005.m1851

https://www.ebay.com/itm/16-in-1-Max-SIM-Cell-Phone-Magic-Blank-Copy-Super-Card-Backup- Cloner-/112586136143?epid=1787822310&hash=item1a36a81a4f:g:lBMAAOSwfrxZ0g~M

https://www.ebay.com/itm/16-in-1-Max-SIM-Cell-Phone-Magic-Super-Card-Backup-W-/272048352906? epid=0&hash=item3f57586e8a:g:ZUoAAOSwlV9WSyiR

https://www.ebay.com/itm/NEW-16-in-1-Max-SIM-Cell-Phone-Magic-Super-Card-Backup-W-/132033063506? epid=1888752442&hash=item1ebdc8aa52:g:6psAAOSwJs1ZybyA

Keskebeu commented 6 years ago

UMTSBand UMTS850=850, // Band V UMTS900=900, // Band VII UMTS1700=1700, // Band IV UMTS1800=1800, // Band III UMTS1900=1900, // Band II UMTS2100=2100 // Band I

check if your phone actually uses the proper band for the the proper channel selection.

dominicantonyv commented 6 years ago

Thanks @peterm2109 for the info on SIM card writer and SuperSIM.

@Keskebeu Thanks for the tip. But, yea, my phone uses proper band.

sajidrahman commented 6 years ago

Hi @dominicantonyv , I'm late to the party but I'm interested to know if (and how) you'd solved your issue. Currently I'm trying to setup a 2G network using OpenBTS and USRP N210. When I run OpenBTS, my mobile phones (android, with 2G sims) cannot detect the test network. Now, I have the following questions:

  1. What is your configuration for GSM.Radio? Mine is as below: screen shot 2018-09-04 at 9 34 06 am
  2. Do I need a programmable sim in order to make a test call? Can't I use any available over-the-counter 2G sims?

I'm running OpenBTS in Ubuntu 16 and my USRP N210 is connected with my laptop via a Gigabit Ethernet cable.

Any help/suggestions will be highly appreciated, thanks!!

Keskebeu commented 6 years ago

check if you got noise. you should be able to register with your current sim card. you do not need to get another to program.

On Tue, Sep 4, 2018 at 9:38 AM, Sajid Rahman notifications@github.com wrote:

Hi @dominicantonyv https://github.com/dominicantonyv , I'm late to the party but I'm interested to know if (and how) you'd solved your issue. Currently I'm trying to setup a 2G network using OpenBTS and USRP N210. When I run OpenBTS, my mobile phones (android, with 2G sims) cannot detect the test network. Now, I have the following questions:

  1. What is your configuration for GSM.Radio? Mine is as below:

[image: screen shot 2018-09-04 at 9 34 06 am] https://user-images.githubusercontent.com/4258481/45034522-c7f80980-b025-11e8-878a-f3bedc44e35e.png

  1. Do I need a programmable sim in order to make a test call? Can't I use any available over-the-counter 2G sims?

I'm running OpenBTS in Ubuntu 16 and my USRP N210 is connected with my laptop via a Gigabit Ethernet cable.

Any help/suggestions will be highly appreciated, thanks!!

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

dominicantonyv commented 6 years ago

@sajidrahman

Detecting the 2G network is not a difficult task. As @Keskebeu suggested, you could check for the current noise level by passing the command "noise" at the CLI. If the noise is within the limits, try adjusting the RxGain.

For me...GSM.Radio.PowerManager.MaxAttenDB is 10, and GSM.Radio.PowerManager.MinAttenDB is 0.