Menu
▾
▴
Re: [Openbts-discuss] OpenBTS-UMTS Success anyone?
|
From: Keith E. F. <ke...@ya...> - 2016-04-27 21:04:33
|
Hi Neel,
I successfully compiled OpenBTS-UMTS but like most on this list, was never able to get a handset to see the network. I used a "16-in-1" SIM programmed with a known Ki, but I could never get the handsets (Samsung Galaxy S-3 and Blackberry 9700 Bold) to even see the UMTS network.
Any configuration details you can share would be greatly appreciated. One thing I did notice were warnings of excessive signal strength.
On Wednesday, April 27, 2016 4:59 PM, Neel Pandeya <nee...@et...> wrote:
Hello Frédéric:
About six months ago, we successfully ran OpenBTS-UMTS, Release 5, using either a B210 or N210 with WBX (I don't remember which, it might have been both). We didn't stress-test the network with a large number of handsets and high data traffic, but we ran it for many hours, with handsets camped on the networks doing various things.
I noticed from one of your previous emails that you're running UHD version 3.9.3. There was an issue in that release with full-duplex operation. I would suggest that you step back to version 3.9.2, and try running it again. Please let us know your results.
I assume that you're using TransceiverUHD, which should be fine. Which USRP are you using? Any B200/B210, N200/N210, X300/X310 should also be fine.
--Neel Pandeya
On 27 April 2016 at 10:28, Daigle, Frédéric <fd...@cm...> wrote:
Hi Harvind,
Thank you for the motivation message. ;)
Attached you will find the ouput resulting from launching OpenBTS-UMTS. The log shows some alertt at the end, the CLI opens up and TX/RX/Clk Leds are lit on my USRP. However, no signal is detected at the output of my USRP (I have verified with a spectrum analyser and 3 different phones)
Please tell me what other logs/information you would need.
Thanks again,
Frédéric
________________________________
De : Harvind Samra <ha...@ra...>
Envoyé : 27 avril 2016 11:49
À : Daigle, Frédéric
Cc : ope...@li...
Objet : Re: [Openbts-discuss] OpenBTS-UMTS Success anyone?
Lots of people are using our commercial and public UMTS stacks. So relax. :)
Have you posted a partial or full log file for us to see? I haven’t seen one yet.
Harvind Samra
Founder, CTO
Range Networks
[cid:image001.png@01D04D54.55755990]<http://www.rangenetworks.com/>
<http://www.rangenetworks.com/>
<http://www.rangenetworks.com/>
<http://www.rangenetworks.com/>
<http://www.rangenetworks.com/>
<http://www.rangenetworks.com/>
<http://www.rangenetworks.com/>
<http://www.rangenetworks.com/>
LinkedIn<https://www.linkedin.com/company/range-networks> | Facebook<https://www.facebook.com/RangeNetworks> | Twitter<https://twitter.com/RangeNetworks> | Jobs <http://www.rangenetworks.com/#!careers/cd2h> | #RangeNetworks #OpenBTS
____________________________________________
Cellular networks made simple and affordable.
http://www.rangenetworks.com<http://www.rangenetworks.com/>
____________________________________________
On Apr 27, 2016, at 6:47 AM, Daigle, Frédéric <fd...@cm...<mailto:fd...@cm...>> wrote:
Hi again ,
Should I conclude that OpenBTS -UMTS is not ready yet as no one seems to have achieved to install a functionnal UMTS network?!
I'm simply trying to have a clear idea on the feasibilty of seeting up OpenBTS -UMTS before spending more time on this project.
Thanks again ,
Frédéric
________________________________
De : Daigle, Frédéric <fd...@cm...<mailto:fd...@cm...>>
Envoyé : 21 avril 2016 15:19
À : 'ope...@li...<mailto:ope...@li...>'
Objet : Re: [Openbts-discuss] OpenBTS-UMTS Success anyone?
Hi Harvind,
Your mean the HW?
It’s a i3, and here are the result of “lscpu”command:
Architecture: i686
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 2
Core(s) per socket: 2
Socket(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 42
Stepping: 7
CPU MHz: 1600.000
BogoMIPS: 6185.37
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 3072K
De : Harvind Samra [mailto:ha...@ra...]
Envoyé : 21 avril 2016 15:11
À : Daigle, Frédéric
Cc : ope...@li...<mailto:ope...@li...>
Objet : Re: [Openbts-discuss] OpenBTS-UMTS Success anyone?
What is your host platform?
Sent from my iPhone
On Apr 21, 2016, at 12:10 PM, Daigle, Frédéric <fd...@cm...<mailto:fd...@cm...><mailto:fd...@cm...>> wrote:
Hi all,
As the default UARFCN is 3050, I have looked at 950 MHz (DL frequency) with a spectrum analyser and realized that nothing was getting out of my USRP N210. In fact, 4 or 5 seconds after sending the “start openbts-umts” command, I can see a short burst, and nothing after. I see the same burst immediately after sending the “stop openbts-umts” command.
In other words my BTS is not transmitting!
Here are my alarms messages:
OpenBTS-UMTS> alarms
ALERT 3072493312 15:00:38.9 OpenBTS-UMTS.cpp:166:main: OpenBTS-UMTS (re)starting, ver 1.0-master build date Apr 19 2016
ALERT 3072493312 15:00:38.9 UMTSPhCh.cpp:654:chConflict: Attempt to reserve channel: sf=64 chcode=2 which conflicts with reserved channel: sf=32 chcode=1
ALERT 3072493312 15:00:38.9 UMTSPhCh.cpp:654:chConflict: Attempt to reserve channel: sf=256 chcode=2 which conflicts with reserved channel: sf=128 chcode=1
ALERT 3072493312 15:00:38.9 UMTSPhCh.cpp:654:chConflict: Attempt to reserve channel: sf=64 chcode=3 which conflicts with reserved channel: sf=32 chcode=1
ALERT 3072493312 15:00:38.9 UMTSPhCh.cpp:654:chConflict: Attempt to reserve channel: sf=256 chcode=4 which conflicts with reserved channel: sf=128 chcode=2
ALERT 3072493312 15:00:38.9 UMTSPhCh.cpp:654:chConflict: Attempt to reserve channel: sf=64 chcode=2 which conflicts with reserved channel: sf=32 chcode=1
ALERT 3072493312 15:00:38.9 UMTSPhCh.cpp:654:chConflict: Attempt to reserve channel: sf=256 chcode=0 which conflicts with reserved channel: sf=128 chcode=0
ALERT 3072493312 15:00:38.9 UMTSPhCh.cpp:654:chConflict: Attempt to reserve channel: sf=256 chcode=1 which conflicts with reserved channel: sf=128 chcode=0
Anyone has a clue on how to solve this issue?
Any form of help or encouragement will be appreciated!
Thank you,
Frédéric
PS: Here is the full message thread the I have after launching OpenbenBTS-UMTS (i.e. sudo ./OpenBTS-UMTS)
openbts@UMTS:/OpenBTS$ sudo ./OpenBTS-UMTS
1461265388.424099 3073120000:
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 2016-04-19T10:41:27 1df760735b CommonLibs:1df760735b
"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 3073120000 15:03:08.5 OpenBTS-UMTS.cpp:166:main: OpenBTS-UMTS (re)starting, ver 1.0-master build date Apr 19 2016
1461265388.556708 3073120000:
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 3073120000 15:03:08.5 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 3073120000 15:03:08.5 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 3073120000 15:03:08.5 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 3073120000 15:03:08.5 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 3073120000 15:03:08.5 UMTSPhCh.cpp:654:chConflict: Attempt to reserve channel: sf=64 chcode=2 which conflicts with reserved channel: sf=32 chcode=1
Dumping SIB5...
SysInfoType5 ::= {
sib6indicator: FALSE
pich-PowerOffset: -10
modeSpecificInfo: fdd ::= {
aich-PowerOffset: -10
}
primaryCCPCH-Info: fdd ::= {
tx-DiversityIndicator: FALSE
}
prach-SystemInformationList: PRACH-SystemInformationList ::= {
PRACH-SystemInformation ::= {
prach-RACH-Info: PRACH-RACH-Info ::= {
modeSpecificInfo: fdd ::= {
availableSignatures: 20 00
availableSF: 0 (sfpr32)
preambleScramblingCodeWordNumber: 0
puncturingLimit: 15 (pl1)
availableSubChannelNumbers: 00 20
}
}
transportChannelIdentity: 3
rach-TransportFormatSet: CommonTransChTFS ::= {
tti: CommonDynamicTF-InfoList ::= {
CommonDynamicTF-Info ::= {
rlc-Size: fdd ::= {
octetModeRLC-SizeInfoType2: 26
}
numberOfTbSizeList: numberOfTbSizeList ::= {
<present>
2
}
logicalChannelList: <present>
}
}
semistaticTF-Information: SemistaticTF-Information ::= {
channelCodingType: 0 (half)
rateMatchingAttribute: 256
crc-Size: 3 (crc16)
}
}
rach-TFCS: TFCS-ReconfAdd ::= {
ctfcSize: ctfc2Bit ::= {
TFCS-ReconfAdd-foo2 ::= {
ctfc2: 0
powerOffsetInformation: PowerOffsetInformation ::= {
gainFactorInformation: SignalledGainFactors ::= {
modeSpecificInfo: fdd ::= {
gainFactorBetaC: 15
}
gainFactorBetaD: 15
}
powerOffsetPp-m: 2
}
}
TFCS-ReconfAdd-foo2 ::= {
ctfc2: 1
powerOffsetInformation: PowerOffsetInformation ::= {
gainFactorInformation: SignalledGainFactors ::= {
modeSpecificInfo: fdd ::= {
gainFactorBetaC: 15
}
gainFactorBetaD: 15
}
powerOffsetPp-m: 2
}
}
}
}
prach-Partitioning: fdd ::= {
ASCSetting-FDD ::= {
accessServiceClass-FDD: AccessServiceClass-FDD ::= {
availableSignatureStartIndex: 0
availableSignatureEndIndex: 0
assignedSubChannelNumber: F0
}
}
}
ac-To-ASC-MappingTable: AC-To-ASC-MappingTable ::= {
0
0
0
0
0
0
0
}
modeSpecificInfo: fdd ::= {
primaryCPICH-TX-Power: 10
constantValue: -10
prach-PowerOffset: PRACH-PowerOffset ::= {
powerRampStep: 1
preambleRetransMax: 64
}
rach-TransmissionParameters: RACH-TransmissionParameters ::= {
mmax: 32
nb01Min: 0
nb01Max: 50
}
aich-Info: AICH-Info ::= {
channelisationCode256: 2
sttd-Indicator: FALSE
aich-TransmissionTiming: 1 (e1)
}
}
}
}
sCCPCH-SystemInformationList: SCCPCH-SystemInformationList ::= {
SCCPCH-SystemInformation ::= {
secondaryCCPCH-Info: SecondaryCCPCH-Info ::= {
modeSpecificInfo: fdd ::= {
dummy1: 0 (mayBeUsed)
sttd-Indicator: FALSE
sf-AndCodeNumber: 3
pilotSymbolExistence: FALSE
tfci-Existence: TRUE
positionFixedOrFlexible: 0 (fixed)
timingOffset: 0
}
}
tfcs: TFCS-ReconfAdd ::= {
ctfcSize: ctfc2Bit ::= {
TFCS-ReconfAdd-foo2 ::= {
ctfc2: 0
}
TFCS-ReconfAdd-foo2 ::= {
ctfc2: 1
}
}
}
fach-PCH-InformationList: FACH-PCH-InformationList ::= {
FACH-PCH-Information ::= {
transportFormatSet: CommonTransChTFS ::= {
tti: CommonDynamicTF-InfoList ::= {
CommonDynamicTF-Info ::= {
rlc-Size: fdd ::= {
octetModeRLC-SizeInfoType2: 3
}
numberOfTbSizeList: numberOfTbSizeList ::= {
<present>
<present>
}
logicalChannelList: <present>
}
}
semistaticTF-Information: SemistaticTF-Information ::= {
channelCodingType: 0 (half)
rateMatchingAttribute: 256
crc-Size: 2 (crc12)
}
}
transportChannelIdentity: 1
ctch-Indicator: FALSE
}
}
pich-Info: fdd ::= {
channelisationCode256: 4
pi-CountPerFrame: 0 (e18)
sttd-Indicator: FALSE
}
}
SCCPCH-SystemInformation ::= {
secondaryCCPCH-Info: SecondaryCCPCH-Info ::= {
modeSpecificInfo: fdd ::= {
dummy1: 0 (mayBeUsed)
sttd-Indicator: FALSE
sf-AndCodeNumber: 2
pilotSymbolExistence: FALSE
tfci-Existence: TRUE
positionFixedOrFlexible: 0 (fixed)
timingOffset: 0
}
}
tfcs: TFCS-ReconfAdd ::= {
ctfcSize: ctfc2Bit ::= {
TFCS-ReconfAdd-foo2 ::= {
ctfc2: 0
}
TFCS-ReconfAdd-foo2 ::= {
ctfc2: 1
}
}
}
fach-PCH-InformationList: FACH-PCH-InformationList ::= {
FACH-PCH-Information ::= {
transportFormatSet: CommonTransChTFS ::= {
tti: CommonDynamicTF-InfoList ::= {
CommonDynamicTF-Info ::= {
rlc-Size: fdd ::= {
octetModeRLC-SizeInfoType2: 3
}
numberOfTbSizeList: numberOfTbSizeList ::= {
<present>
<present>
}
logicalChannelList: <present>
}
}
semistaticTF-Information: SemistaticTF-Information ::= {
channelCodingType: 0 (half)
rateMatchingAttribute: 256
crc-Size: 2 (crc12)
}
}
transportChannelIdentity: 1
ctch-Indicator: FALSE
}
}
}
}
}
SysInfoType11 ::= {
sib12indicator: FALSE
measurementControlSysInfo: MeasurementControlSysInfo ::= {
use-of-HCS: hcs-not-used ::= {
cellSelectQualityMeasure: cpich-Ec-N0 ::= {
}
}
}
}=== Phase1 Encoding SIB MIB
=== Phase1 Encoded SIB MIB size 152 blocks 0.672566
SIB0: bytes: ByteVector(size=19 data: 00 00 40 25 00 00 44 20 64 20 33 21 91 51 00 30 74 a0 3b)
=== Phase1 Encoding SIB SIB1
=== Phase1 Encoded SIB SIB1 size 94 blocks 0.415929
SIB1: bytes: ByteVector(size=12 data: c4 02 10 8b 20 00 01 00 ce 01 ab 40)
=== Phase1 Encoding SIB SIB2
=== Phase1 Encoded SIB SIB2 size 20 blocks 0.0884956
SIB2: bytes: ByteVector(size=3 data: 00 06 40)
=== Phase1 Encoding SIB SIB3
=== Phase1 Encoded SIB SIB3 size 102 blocks 0.451327
SIB3: bytes: ByteVector(size=13 data: 00 00 00 00 42 c0 60 00 04 b4 ff ff fc)
=== Phase1 Encoding SIB SIB5
=== Phase1 Encoded SIB SIB5 size 466 blocks 2.06195
SIB4: bytes: ByteVector(size=59 data: 80 30 0e 88 00 00 f0 02 14 00 68 2c 0a ff 60 00 32 3f de c7 fb 84 03 c0 00 00 fa 99 1f fc 0c 80 91 e0 40 d0 00 08 22 00 43 08 8b fd 00 04 18 08 12 00 01 04 40 08 61 11 7f a0 00)
=== Phase1 Encoding SIB SIB7
=== Phase1 Encoded SIB SIB7 size 20 blocks 0.0884956
SIB5: bytes: ByteVector(size=3 data: 4a 00 00)
=== Phase1 Encoding SIB SIB11
=== Phase1 Encoded SIB SIB11 size 10 blocks 0.0442478
SIB6: bytes: ByteVector(size=2 data: 01 00)
chReserve(256,0)
ALERT 3073120000 15:03:08.5 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 3073120000 15:03:08.5 UMTSPhCh.cpp:654:chConflict: Attempt to reserve channel: sf=256 chcode=1 which conflicts with reserved channel: sf=128 chcode=0
1461265388.569272 3073120000: Starting the transceiver...
linux; GNU C++ version 4.6.3; Boost_104601; UHD_003.009.003-release
** Configuring logger
** Using internal clock reference
** Searching for USRP device
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
** Device ready
RTNETLINK answers: File exists
1461265394.437909 3073120000:
system ready
1461265394.437979 3073120000:
use the OpenBTS-UMTSCLI utility to access CLI
De : Daigle, Frédéric [mailto:fd...@cm...]
Envoyé : 21 avril 2016 12:34
À : 'ope...@li...<mailto:ope...@li...><mailto:ope...@li...>'
Objet : [Openbts-discuss] OpenBTS-UMTS Success anyone?
Hi all,
I’m an OpenBTS (GSM) user and this week, I decided to give a try at the UMTS version.
I’ve started with a clean HDD, installed Ubuntu server 12.04.5 and then followed the instructions here:
http://openbts.org/w/index.php?title=OpenBTS-UMTS
After taking some hurdles I succeeded to “start openbts-umts” and open “OpenBTS-UMTSCLI”
Asterisk, Sipauthserve and SMQueue doesn’t seems to be installed. I guess I will have to installed them eventually?!
The bad news is that I can’t find my network with any of my phones….
My main questions are:
1.Does anyone ever connected to OpenBTS-UMTS?
2.Is there any tips and tricks about the setup?
3.Is is better to install OpenBTS-UMTS on top of regular (GSM) OpenBTS or on a new HDD?
Thank you for your assistance!
Frédéric
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Openbts-discuss mailing list
Ope...@li...<mailto:Ope...@li...>
https://lists.sourceforge.net/lists/listinfo/openbts-discuss
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Openbts-discuss mailing list
Ope...@li...
https://lists.sourceforge.net/lists/listinfo/openbts-discuss
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Openbts-discuss mailing list
Ope...@li...
https://lists.sourceforge.net/lists/listinfo/openbts-discuss
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Openbts-discuss mailing list
Ope...@li...
https://lists.sourceforge.net/lists/listinfo/openbts-discuss
|
