Author Topic: Cant detect cellular network  (Read 750 times)

Lfsnoob

  • Newbie
  • *
  • Posts: 18
    • View Profile
Re: Cant detect cellular network
« Reply #15 on: October 12, 2018, 06:11:08 AM »
As you can see, I used Radio.Band=1800 and Radio.C0=512 since i recently discovered that this is the only frequency where i dont get the TOA errors, However, I still do not see a cellular network. Heres a comprehensive overview of mobile frequency bands in my country. https://ibb.co/iq8Ug9
« Last Edit: October 12, 2018, 06:33:10 AM by Lfsnoob »

Ioana Stanciu

  • Jr. Member
  • **
  • Posts: 74
    • View Profile
Re: Cant detect cellular network
« Reply #16 on: October 12, 2018, 07:04:40 AM »
Judging by the presence of the 'transceiver' configuration option from the conf file, it seems that you are using the old transceiver and an old version of YateBTS (this was changed 3 years ago)
Could you try with the updated Yate and YateBTS from official sources? The newer version uses a different transceiver.
Instructions are here:
https://wiki.yatebts.com/index.php/Prerequisites
https://wiki.yatebts.com/index.php/Installing

Make sure you've properly cleaned up the previous installation.

Lfsnoob

  • Newbie
  • *
  • Posts: 18
    • View Profile
Re: Cant detect cellular network
« Reply #17 on: October 12, 2018, 09:58:42 AM »
After flashing my SDCard to a Raspbian Stretch for a clean install, I managed to build yate and yate bts. However, the results are the same. Here is my new build:
  bladeRF-cli version:        1.4.0-0.2016.06-1+b2
  libbladeRF version:         1.7.2-0.2016.06-1+b2

  Firmware version:           2.0.0
  FPGA version:               0.1.2

heres the new config files:
cat /usr/local/etc/yate/ybts.conf
[gsm]
;The GSM operating band.
;Valid values are 850 (GSM850), 900 (PGSM900), 1800 (DCS1800) and 1900 (PCS1900).
;For non-multiband units, this value is dictated by the hardware and should not be changed.
Radio.Band=900

;The C0 ARFCN. Also the base ARFCN for a multi-ARFCN configuration.Valid values depend on the selected Radio.Band.
;  GSM850: 128..251.
;  EGSM900: 0..124 or 975..1023.
;  DSC1800: 512..885.
;  PCS1900: 512..810.
;THERE IS NO DEFAULT, YOU MUST SET A VALUE HERE!
Radio.C0=0

;Mobile country code, must be three digits.
;The value 001 is reserved for for test networks.
;Defaults to 001 (Test Network)
Identity.MCC=001

;Mobile network code, two or three digits.
;The value 01 is usual for test networks with MCC 001.
;Defaults to 01 (Test Network, only in association with Identity.MCC=001)
Identity.MNC=01

;Location area code, 16 bits, values 0xFFxx are reserved.
;For multi-BTS networks, assign a unique LAC to each BTS unit.
;Interval allowed: 0..65280.
;Defaults to 1000 (arbitrary)
Identity.LAC=1000

;Cell ID, 16 bits, should be unique.
;Interval allowed: 0..65535.
;Defaults to 10 (arbitrary)
Identity.CI=10

;GSM basestation color code; lower 3 bits of the BSIC.
;BCC values in a multi-BTS network should be assigned so that BTS units with overlapping coverage do not share a BCC.
;This value will also select the training sequence used for all slots on this unit.
;Interval allowed: 0..7.
;Defaults to 2 (arbitrary).
Identity.BSIC.BCC=2

;GSM network color code; upper 3 bits of the BSIC.
;Assigned by your national regulator, must be distinct from NCCs of other GSM operators in your area.
;Interval allowed: 0..7. Defaults to 0.
Identity.BSIC.NCC=0

;Network short name, displayed on some phones.
;Optional but must be defined if you also want the network to send time-of-day.
;Defaults to YateBTS.
Identity.ShortName=thisdoesnotwork

;Maximum transmitter attenuation level, in dB wrt full scale on the D/A output.
;This sets the minimum power output level in the output power control loop.
;Interval allowed: 0..80. Defaults to 10 (-10dB)
Radio.PowerManager.MaxAttenDB=35

;Minimum transmitter attenuation level, in dB wrt full scale on the D/A output.
;This sets the maximum power output level in the output power control loop.
;Interval allowed: 0..80, must be less or equal to Radio.PowerManager.MaxAttenDB.
;Defaults to  0(dB) (maximum).
Radio.PowerManager.MinAttenDB=35


[gsm_advanced]
;Number of Combination-I timeslots to configure.
;The C-I slot carries a single full-rate TCH, used for speech calling.
;Interval allowed: 0..100. Default value: 7(all timeslots of a single ARFCN)
Channels.NumC1s=7

;Number of Combination-VII timeslots to configure.
;The C-VII slot carries 8 SDCCHs, useful to handle high registration loads, SMS or USSD.
;If C0T0 is C-IV, you must have at least one C-VII also.
;Interval allowed: 0..100.
;Defaults to 0(timeslots).
Channels.NumC7s=0

;Allocate C-I slots first, starting at C0T1.
;Defaults to no (allocate C-VII slots first).
Channels.C1sFirst=no

;Number of SDCCHs to reserve for non-LUR operations.
;This can be used to force LUR transactions into a lower priority.
;Interval allowed: 0..10.
;Defaults to 0(SDCCHs)
Channels.SDCCHReserve=0

;Maximum number of access grants to be queued for transmission on AGCH before declaring congestion.
;Interval allowed: 3..8.
;Defaults to 5
CCCH.AGCH.QMax=5

;CCCH configuration type.
;Values allowed: 1 (C-V beacon) or 2 (C-IV beacon).
;Defaults to 1.
CCCH.CCCH-CONF=1

;Seconds before declaring a physical link dead.
;Interval allowed: 10..20.
;Defaults to 15
CellOptions.RADIO-LINK-TIMEOUT=15

;Cell Reselection Hysteresis.
;See GSM 04.08 10.5.2.4, Table 10.5.23 for encoding, Hysteresis is 2N dB.
;Interval allowed: 0..7 (corresponds to 0..14 dB).
;Defaults to 3
CellSelection.CELL-RESELECT-HYSTERESIS=3

;Cell selection parameters.
;See GSM 04.08 10.5.2.4.,Table 10.5.23 for encoding, Hysteresis is 2N dB.
;Interval allowed: 0..7 (corresponds to 0..14 dB).
;Defaults to 0.
CellSelection.MS-TXPWR-MAX-CCH=0

;An 8-bit mask of allowed NCCs.
;Unless you are coordinating with another carrier use -1 which allows to select your own NCC.
;Valid values: 0..255 or -1.
;Defaults to -1 (allow your own NCC only)
CellSelection.NCCsPermitted=-1

;New Establishment Causes support.
;See GSM 04.08 10.5.2.4, Table 10.5.23 and 04.08 9.1.8, Table 9.9.
;This must be set to 1 if you want to support Very Early Assignment
;Check VEA description for details from Control tab.
;Valid values: 0..1
;Defaults to 1
CellSelection.NECI=1

;Cell selection parameters.
;See GSM 04.08 10.5.2.4 for details.
;Interval allowed: 0..63.
;Defaults to 0.
CellSelection.RXLEV-ACCESS-MIN=0

;Probability of a bit getting toggled in a control channel burst for cracking protection.
;Interval allowed: 0.0 - 1.0.
;Defauls to 0
Cipher.CCHBER=0.0

;Encrypt traffic between phone and BTS.
;Defaults to no.
Cipher.Encrypt=no

;Probability of a random neighbor being added to SI5 for cracking protection.
;Interval allowed: 0.0 - 1.0.
;Defauls to 0.
Cipher.RandomNeighbor=0.0

;Scramble filler in layer 2 for cracking protection.
;Defaults to no.
Cipher.ScrambleFiller=no

;Ignore GPRS messages on GSM control channels.
;Value is number of consecutive messages to ignore.
;Interval allowed: 3..8.
;Defaults to 5
Control.GPRSMaxIgnore=5

;Handover determination holdoff time after channel establishment, allows the MS RSSI value to stabilize. 2000 to 7000 ms, default 5000.
Handover.InitialHoldoff=5000

;Handover determination holdoff time after a previous attempt. 750 to 7000 ms, default 3000.
Handover.RepeatHoldoff=3000

;Do not handover if downlink RSSI is above this level (in dBm), regardless of power difference.
;Allowed values -100:-50.
Handover.LocalRSSIMin=-80

;A neighbor downlink signal must be this much stronger (in dB) than this downlink signal for handover to occur.
;Allowed values 5:20.
Handover.ThresholdDelta=10

;Damping value for MS power control loop.
;Interval allowed: 25..75. Defaults to 50.
MS.Power.Damping=50

;Maximum commanded MS power level in dBm.
;Interval allowed: 5..100
;Defaults to 33
MS.Power.Max=33

;Minimum commanded MS power level in dBm.
;Interval allowed: 5..100
;Defaults to 5
MS.Power.Min=5

;Damping value for timing advance control loop.
;Interval allowed: 25..75
;Defaults to 50
MS.TA.Damping=50

;Maximum allowed timing advance in symbol periods.
;One symbol period of round-trip delay is about 0.55 km of distance.
;RACH bursts with delays greater than this are ignored.
;Can be used to limit service range.
;Interval allowed: 1..62.
;Defaults to 62 (maximum range)
MS.TA.Max=62

;Maximum allowed speech buffering latency.
;It is expressed in 20ms frames.
;Frames will be dropped if the jitter is larger than this delay.
;Interval allowed: 1..5.
;Defaults to 2.
MaxSpeechLatency=2

;Maximum number of neighbors to send to handset in a neighbor list in BCCH.
;Interval allowed:1..10.
;Defaults to 8.
Neighbors.NumToSend=8

;Maximum number of repeats of the Physical Information Message during handover procedure, GSM 04.08 11.1.3.
;Interval allowed: 1..10
;Defaults to 5
Ny1=5

;Integer: Access Class flags.
;This is the raw parameter sent on BCCH, see GSM 04.08 10.5.2.29 for encoding.
;DO NOT ALTER THIS UNLESS YOU ARE A REAL OPERATOR!
;Interval allowed: 0..65535 (16 bits, 0x0000..0xffff).
;Defaults to 0x0400 (No emergency services access).
RACH.AC=0x0400

;Maximum RACH retransmission attempts.
;This is the raw parameter sent on BCCH, see GSM 04.08 10.5.2.29 for encoding
;Interval allowed: 0..3 (encodes to 1..7 retransmissions)
;Defaults to 1 (2 retransmissions)
RACH.MaxRetrans=1

;Parameter to spread RACH busts over time.
;This is the raw parameter sent on BCCH, see GSM 04.08 10.5.2.29 for encoding.
;Interval allowed: 0..15 (encodes to 3..50 slots)
;Defaults to 14 (32 slots)
RACH.TxInteger=14

;The number of ARFCNs to use.
;The ARFCN set will be C0, C0+2, C0+4, ...Interval allowed: 1..10
;Defaults to 1 (single ARFCN unit)
Radio.ARFCNs=1

;Expected worst-case delay spread
;Expressed in symbol periods, roughly 3.7 us or 1.1 km per unit.
;This parameter is dependent on the terrain type in the installation area.
;Typical values: 1 -> open terrain, small coverage, 4 -> large coverage area.
;This parameter has a large effect on computational requirements of the software radio.
;Interval allowed: 1..4.
;Defaults to 2.
Radio.MaxExpectedDelaySpread=2

;Does the Radio type require the full BSIC.
;Defaults to no.
Radio.NeedBSIC=no

;Number of samples averaged by the output power control loop
;Interval allowed: 5..20
;Defaults to 10
Radio.PowerManager.NumSamples=10

;Power manager control loop master period, in milliseconds
;Interval allowed: 4500..7500
;Defaults to 6000
Radio.PowerManager.Period=6000

;Sample period for the output power control loopm in milliseconds
;Interval allowed: 1500..2500
;Defaults to 2000
Radio.PowerManager.SamplePeriod=2000

;Target value for T3122, the random access hold-off timer, for the power control loop.
;Interval allowed: 3750..6250.
;Defaults to 5000
Radio.PowerManager.TargetT3122=5000

;Target uplink RSSI for MS power control loop
;Expressed in dB wrt to receiver's A/D convertor full scale
;Should be 6-10 dB above the noise floor (see the 'mbts noise' command)
;Interval allowed: -75..-25
;Defaults to -50
Radio.RSSITarget=-61

;Receiver gain setting in dB
;Ideal value is dictated by the hardware; 47 dB for RAD1, less for USRPs
;Interval allowed: 0..75
;Defaults to empty value. Radios provide their own calibrated default. To see current value run 'mbts trxfactory' after connecting to rmanager interface.
;Radio.RxGain=

;Tell the phone to show the country name based on MCC
;Defaults to no
ShowCountry=no

;Handover timeout in milliseconds, GSM 04.08 11.1.2
;This is the timeout for a handset to sieze a channel during handover.
;Allowed: 2500:7500(100)
;Defaults to 5000
Timer.T3103=5000

;Milliseconds for handset to respond to physical information.GSM 04.08 11.1.2.
;Interval allowed 25:75(5).
;Defaults to 50
Timer.T3105=50

;Paging timer T3113 in milliseconds.
;This is the timeout for a handset to respond to a paging request.
;This should usually be the same as SIP.Timer.B in your VoIP network.
;Allowed interval 5000:15000(500).
;Defaults to 10000
Timer.T3113=10000

;Maximum allowed value for T3122, the RACH holdoff timer, in millseconds.
;Allowed interval 127500:382500(1000).
;It is not required to be a factor of 1000.
;Defaults to 255000.
Timer.T3122Max=255000

;Minimum allowed value for T3122, the RACH holdoff timer, in milliseconds.
;Allowed interval 1000:3000(100).
;Defaults to 2000
Timer.T3122Min=2000

;Registration timer T3212 period in minutes. Should be a factor of 6.
;Set to 0 to disable periodic registration.
;Should be smaller than SIP registration period.
;Allowed interval 0:1530(6)
;Defaults to 24.
Timer.T3212=24


[gprs]
;Advertise GPRS in C0T0 beacon and start service on demand.
;See also Channels.* in [gprs_advanced] for how many channels are reserved.
;Defauts to yes.
Enable=no

;GPRS Routing Area Code, advertised in the C0T0 beacon.
;Interval allowed: 0..255
;Defaults to 0 (arbitrary)
RAC=0

;GPRS Routing Area Color as advertised in the C0T0 beacon
;Interval allowed: 0..7
;Defaults to 0 (arbitrary)
RA_COLOUR=0


[gprs_advanced]
;Toggle GPRS debugging. Defaults to no.
Debug=no

;MS power control parameter, unitless, in steps of 0.1, so a parameter of 5 is an alpha value of 0.5.
;Determines sensitivity of handset to variations in downlink RSSI.
;Valid range is 0...10 for alpha values of 0.0 ... 1.0. See GSM 05.08 10.2.1.
MS.Power.Alpha=10

;MS power control parameter, in 2 dB steps.
;Determines baseline of handset uplink power relative to downlink RSSI
;The optimum value will tend to be lower for BTS units with higher power output
;Valid range is 0...31 for gamma values of 0...62 dB. See GSM 05.08 10.2.1.
MS.Power.Gamma=31

;MS power control parameter; see GSM 05.08 10.2.1.
;Valid range is 0...25.
MS.Power.T_AVG_T=15

;MS power control parameter; see GSM 05.08 10.2.1.
;Valid range is 0...25
;Defaults to 15.
MS.Power.T_AVG_W=15

;Maximum number of channels used for a single MS in downlink
;Valid range is 0...10
;Defaults to 3.
Multislot.Max.Downlink=3

;Maximum number of channels used for a single MS in uplink
;Valid range is 0...10. Defaults to 2.
Multislot.Max.Uplink=2

;List of allowed GPRS downlink codecs 1..4 for CS-1..CS-4.
;Currently, only 1 and 4 are supported e.g. 14.
Codecs.Downlink=14

;List of allowed GPRS uplink codecs 1..4 for CS-1..CS-4.
;Currently, only 1 and 4 are supported e.g. 14.
Codecs.Uplink=14

;How often to send keep-alive messages for persistent TBFs in milliseconds; must be long enough to avoid simultaneous in-flight duplicates, and short enough that MS gets one every 5 seconds.
;Allowed interval 200:5000(100)
;Defauts to 300
Uplink.KeepAlive=300

;After completion, uplink TBFs are held open for this time in milliseconds
;If non-zero, must be greater than GPRS.Uplink.KeepAlive
;This is broadcast in the beacon and it cannot be changed once BTS is started
;Allowed interval 0:6000(100)
;Defauts to 4000.
Uplink.Persist=4000

;When the first poll is sent for a downlink tbf, measured in blocks sent.
;Allowed values 5:15
;Defauts to 10
TBF.Downlink.Poll1=10

;Allow MS to request another uplink assignment at end up of uplink TBF. See GSM 4.60 9.2.3.4
;Defauts to yes.
TBF.EST=yes

;How long to try before giving up on a TBF
;Allowed interval 20000:40000
;Defauts to 30000
TBF.Expire=30000

;How many expired TBF structs to retain; they can be viewed with gprs list tbf -x
;Allowed interval 15:25
TBF.KeepExpiredCount=20

;If 0, no tbf retry, otherwise if a tbf fails it will be retried with this codec, numbered 1..4.
TBF.Retry=1

;Number of advance blocks to use in the CCCH reservation.
;Allowed interval 5:15
;Defaults to 10.
advanceblocks=10

;Timer 3168 in the MS controls the wait time after sending a Packet Resource Request to initiate a TBF before giving up or reattempting a Packet Access Procedure, which may imply sending a new RACH.
;This code is broadcast to the MS in the C0T0 beacon in the GPRS Cell Options IE. See GSM 04.60 12.24.
;Range 0..7 to represent 0.5sec to 4sec in 0.5sec steps.
CellOptions.T3168Code=5

;Timer 3192 in the MS specifies the time MS continues to listen on PDCH after all downlink TBFs are finished, and is used to reduce unnecessary RACH traffic.
;This code is broadcast to the MS in the C0T0 beacon in the GPRS Cell Options IE.
;The value must be one of the codes described in GSM 04.60 12.24.
;Value 0 implies 500msec
;2 implies 1500msec
;3 imples 0msec.
CellOptions.T3192Code=0

;If the initial unlink signal strength is less than this amount in DB GPRS uses a lower bandwidth but more robust encoding CS-1.
;This value should normally be GSM.Radio.RSSITarget + 10 dB.
;Interval allowed -65:-15
;Defaults to -40.
ChannelCodingControl.RSSI=-40

;The GPRS channel is considered congested if the desired bandwidth exceeds available bandwidth by this amount, specified in percent
;Interval allowed 100:300(5)
;Defaults to 200.
Channels.Congestion.Threshold=200

;How long in seconds GPRS congestion exceeds the Congestion
;Threshold before we attempt to allocate another channel for GPRS
;Interval allowed 30:90(5)
;Defaults to 60.
Channels.Congestion.Timer=60

;Minimum number of channels allocated for GPRS service on ARFCN C0.
;Interval allowed 0:7.
;Defaults to 3.
Channels.Min.C0=3

;Minimum number of channels allocated for GPRS service on ARFCNs other than C0
;Interval allowed 0:100
;Defaults to 0.
Channels.Min.CN=0

;Maximum number of channels allocated for GPRS service.
;Interval allowed 0:10.
;Defaults to 4.
Channels.Max=4

;Maximum number of assign messages sent.
;Interval allowed 5:15
;Defaults to 10
Counters.Assign=10

;Counts unused USF responses to detect nonresponsive MS. Should be > 8. See GSM04.60 sec 13.
;Interval allowed 8:32
;Defaults to 20
Counters.N3101=20

;Counts ACK/NACK attempts to detect nonresponsive MS. See GSM04.60 sec 13
;Interval allowed 4:12
;Defaults to 8.
Counters.N3103=8

;Counts unused RRBP responses to detect nonresponsive MS. See GSM04.60 sec 13
;Interval allowed 6:18
;Defaults to 12
Counters.N3105=12

;Maximum number of reassign messages sent
;Interval allowed 3:9
;Defaults to 6
Counters.Reassign=6

;Maximum number of TBF release messages sent
;Interval allowed 3:8
;Defaults to 5
Counters.TbfRelease=5

;How often to send keep-alive messages for persistent TBFs in milliseconds
;must be long enough to avoid simultaneous in-flight duplicates, and short enough that MS gets one every 5 seconds.
;GSM 5.08 10.2.2 indicates MS must get a block every 360ms.
;Interval allowed 200:5000(100)
;Defaults to 300
Downlink.KeepAlive=300

;After completion, downlink TBFs are held open for this time in milliseconds
;If non-zero, must be greater than GPRS.Downlink.KeepAlive.
Downlink.Persist=0

;Enable recognition of local TLLI.
LocalTLLI.Enable=yes

;How many expired MS structs to retain; they can be viewed with gprs list ms -x.
;Interval allowed 10:30
;Defaults to 20
MS.KeepExpiredCount=20

Lfsnoob

  • Newbie
  • *
  • Posts: 18
    • View Profile
Re: Cant detect cellular network
« Reply #18 on: October 12, 2018, 09:58:57 AM »
;Controls measurement reports and cell reselection mode (MS autonomous or under network control); should not be changed
;Interval allowed 0:3
;Defaults to 2.
NC.NetworkControlOrder=2

;Network Mode of Operation. See GSM 03.60 Section 6.3.3.1 and 24.008 4.7.1.6.
;Allowed values are 1, 2, 3 for modes I, II, III.
;Mode II (2) is recommended.
;Mode I implies combined routing updating procedures.
NMO=2

;Code contols GPRS packet access priorities allowed. See GSM04.08 table  10.5.76.
;0=Packet access not allowed in the cell,
;3=Packet access allowed for priority level 1,
;4=Packet access allowed for priority level 1 to 2,
;5=Packet access allowed for priority level 1 to 3,
;6=Packet access allowed for priority level 1 to 4
PRIORITY-ACCESS-THR=6

;Minimum value for RRBP reservations, range 0..3. Should normally be 0. A non-zero value gives the MS more time to respond to the RRBP request.
RRBP.Min=0

;Enable TBF Reassignment.
Reassign.Enable=yes

;Should be 0 for current transceiver or 1 for deprecated version of transceiver.
SendIdleFrames=no

;Port number of the SGSN required for GPRS service.
;This must match the port specified in the SGSN config file, currently osmo_sgsn.cfg.
SGSN.port=1920

;How long in milliseconds a GPRS channel is idle before being returned to the pool of channels.
;Also depends on Channels.Min.
;Currently the channel cannot be returned to the pool while there is any GPRS activity on any channel.
;Interval allowed 3000:6000(100)
;Defaults to 6000.
Timers.Channels.Idle=6000

;How long in seconds an MS is idle before the BTS forgets about it
;Interval allowed 300:900(10)
;Defaults to 600.
Timers.MS.Idle=600

;How long in milliseconds a TBF is non-responsive before the BTS kills it
;Interval allowed 3000:9000(100)
;Defaults to 6000.
Timers.MS.NonResponsive=6000

;Nonresponsive downlink TBF resource release timer, in milliseconds. See GSM04.60 Section 13
;Interval allowed 2500:7500(100)
;Defaults to 5000
Timers.T3169=5000

;Nonresponsive downlink TBF resource release timer, in milliseconds. See GSM04.60 Section 13
;Interval allowed 2500:7500(100)
;Defaults to 5000
Timers.T3191=5000

;Timer T3193 (in milliseconds) in the base station corresponds to T3192 in the MS, which is set by GPRS.CellOptions.T3192Code
;The T3193 value should be slightly longer than that specified by the T3192Code
;If 0, the BTS will fill in a default value based on T3192Code
;Interval allowed 0:5000(100)
;Defaults to 0
Timers.T3193=0

;Nonresponsive downlink TBF resource release timer, in milliseconds. See GSM04.60 Section 13
;Interval allowed 2500:7500(100)
;Defaults to 5000
Timers.T3195=5000


[sgsn]
;Add layer-3 messages to the GGSN.Logfile, if any.
Debug=no

;GPRS attached MS is implicitly detached in seconds
;Should be at least 240 seconds greater than SGSN.Timer.RAUpdate. 3GPP 24.008 11.2.2.
;Interval allowed 2000:4000(10).
;Defaults to 3480.
Timer.ImplicitDetach=3480

;How long an MS is idle before the SGSN forgets TLLI specific information. Interval allowed 300:900(10). Defaults to 600.
Timer.MS.Idle=600

;How often the MS reports into the SGSN when it is idle, in seconds.
;Also known as T3312, 3GPP 24.008 4.7.2.2.
;Setting to 0 or >12000 deactivates entirely, i.e., sets the timer to effective infinity.
;Note: to prevent GPRS Routing Area Updates you must set both this and GSM.Timer.T3212 to 0.
;Interval allowed 0:11160(2)
;Defaults to 3240.
Timer.RAUpdate=3240

;Also known as T3314, 3GPP 24.008 4.7.2.1
;Inactivity period required before MS may perform another routing area or cell update, in seconds. Interval allowed 30:90. Defaults to 44.
Timer.Ready=44


[ggsn]
;The list of DNS servers to be used by downstream clients.
;By default, DNS servers are taken from the host system.
;To override, specify a space-separated list of the DNS servers, in IP dotted notation, eg: 1.2.3.4 5.6.7.8.
;To use the host system DNS servers again, execute 'unconfig GGSN.DNS'
;DNS=

; 0=no firewall; 1=block MS attempted access to OpenBTS or other MS; 2=block all private IP addresses
;Defaults to 1.
Firewall.Enable=1

;Maximum size of an IP packet.Should normally be 1520
;Allowed value 1492:9000
IP.MaxPacketSize=1520

;How long IP addresses are reserved after a session ends. Allowed value 120:240.
IP.ReuseTimeout=180

;Toss duplicate TCP/IP packets to prevent unnecessary traffic on the radio.
IP.TossDuplicatePackets=no

;If specified, internet traffic is logged to this file e.g. ggsn.log
Logfile.Name=ggsn.log

;Base IP address assigned to MS.
MS.IP.Base=192.168.99.1

;Number of IP addresses to use for MS. Allowed values 1:254
;Defaults to 254
MS.IP.MaxCount=254

;A route address to be used for downstream clients.
;By default, OpenBTS manufactures this value from the GGSN.MS.IP.Base assuming a 24 bit mask
;To override, specify a route address in the form xxx.xxx.xxx.xxx/yy.
;The address must encompass all MS IP addresses. To use the auto-generated value again, execute 'unconfig GGSN.MS.IP.Route'
;MS.IP.Route=

;A shell script to be invoked when MS devices attach or create IP connections.
;By default, this feature is disabled.
;To enable, specify an absolute path to the script you wish to execute e.g. /usr/bin/ms-attach.sh.
;To disable again, execute 'unconfig GGSN.ShellScript'
;ShellScript=

;Tunnel device name for GGSN.
TunName=sgsntun


[control]
;Use very early assignment for speech call establishment.
;See GSM 04.08 Section 7.3.2 for a detailed explanation of assignment types.
;See GSM 04.08 Sections 9.1.8 and 10.5.2.4 for an explanation of the NECI bit.
;Some handsets exhibit bugs when VEA is used that can affect performance.
;If VEA is selected, [gsm_advanced] CellSelection.NECI should be set to 1.
;Defaults to yes.
VEA=yes

;Use the attach/detach procedure. This will make initial LUR more prompt.
;It will also cause an un-registration if the handset powers off and really heavy LUR loads in areas with spotty coverage.
;Defaults to yes.
LUR.AttachDetach=yes

;RSSI decrease amount. Decrease the RSSI by this amount to induce more power in the MS each time we fail to receive a response from it.
;Interval allowed: 1..3
;Defaults to 1
SACCHTimeout.BumpDown=1


[transceiver]
;Path to the transceiver relative to where MBTS is started.
;Should be one of: ./transceiver-bladerf ./transceiver-rad1 ./transceiver-usrp1 ./transceiver-uhd.
;Defaults to ./transceiver
Path=./transceiver

;Extra arguments to be passed by MBTS to the transceiver executable.
;Defaults to no arguments.
;Args=

;Minimum signal strength (in dB) of acceptable bursts.
;Bursts received at the physical layer below this threshold are ignored.
;Do not adjust without proper calibration.
;Interval allowed: -90..90
;Defaults to -63
MinimumRxRSSI=-63

;Master clock frequency adjustment. Fine-tuning adjustment for the transceiver master clock, roughly 170 Hz/step.
;Set at the factory, do not adjust without proper calibration.
;Interval allowed: 64..192
;Defaults to empty value. Radios provide their own calibrated default. To see current value run 'mbts trxfactory' after connecting to rmanager interface.
;RadioFrequencyOffset=

;Transmitter attenuation in dB.
;Hardware-specific gain adjustment for transmitter, matched to the amplifier.
;Do not adjust without proper calibration
;Interval allowed: 0..100
;Defaults to empty value. Radios provide their own calibrated default. To see current value run 'mbts trxfactory' after connecting to rmanager interface.
;TxAttenOffset=

;Transceiver read timeout in seconds.
;How long to wait during a read operation from the transceiver before giving up
;Interval allowed: 5..15
;Defaults to 10
Timeout.Clock=10


[tapping]
;Capture GSM signaling at L1/L2 interface via GSMTAP
;Do not leave tapping enabled after finishing troubleshooting.
;Defaults to no.
GSM=no

;Capture GPRS signaling and traffic at L1/L2 interface via GSMTAP.
;Do not leave tapping enabled after finishing troubleshooting
;Defaults to no
GPRS=no

;Target IP address for GSMTAP packets.
;The IP address of receiving Wireshark, if you use it for real time traces.
TargetIP=127.0.0.1


[test]
;Probability (0-100) of dropping any downlink frame to test robustness.
SimulatedFER.Downlink=0

; Probability (0-100) of dropping any uplink frame to test robustness.
SimulatedFER.Uplink=0

;Probability (0-100) of flipping a bit in any uplink frame to test robustness.
UplinkFuzzingRate=0


[ybts]
;BTS mode of operation. This setting will specify which Javascript script
;to load for the operation. Possible values are:
;    - nipc: loads script necessary for Network In a PC mode of operation
;    - roaming: loads script necessary for the voice roaming mode of operation
mode=nipc

;Interval, in milliseconds, to send heartbeat (PING) to MBTS application.
;Ping is sent only if idle, e.g. it is not sent if there are other signalling packets to be sent.
;This parameter is applied on reload.
;Allowed interval: 1000 .. 120000
;Defaults to 30000
heartbeat_ping=30000

;Interval, in milliseconds, to wait for heartbeat (PING) or any other signalling packets from mbts application
;MBTS will be restarted if this timer ellapses
;This parameter is applied on reload
;Minimum allowed value is heartbeat_ping plus 3000, it will be automatically adjusted
;Maximum allowed value is 180000
;Defaults to 60000.
heartbeat_timeout=60000

;Interval, in milliseconds, to wait for handshake from the MBTS application after it's started
;MBTS will be restart if this timer ellapses
;This parameter is applied on reload
;Allowed interval: 10000 .. 300000
;Defaults to 60000.
handshake_start=60000

;Maximum number of restart attempts
;When start counter reaches this value the entire Yate application will exit!
;The start index is reset each time the peer notifies radio up after handshake.
;This parameter is applied on reload.
;Defaults to 10, minimum allowed value is 3
max_restart=10

;Command used to run the MBTS application.
;Defaults to expansion of ${modulepath}/server/bts/mbts
peer_cmd=${modulepath}/server/bts/mbts

;Optional command line parameter for the MBTS application.
;Defaults to no parameter.
;peer_arg=

;Directory to change after forking the MBTS application.
;Defaults to expansion of ${modulepath}/server/bts
peer_dir=${modulepath}/server/bts

;Print sent/received messages to output if debug is at level 9.
;Allowed values are boolean values or string.
;If a non boolean value is specified message buffer will be shown.
;This parameter is applied on reload.
;Defaults to yes if empty or missing.
print_msg=yes

;Print sent/received messages data.
;This parameter is ignored if message print is disabled.
;Allowed values are boolean values or string.
;If a non boolean value is specified (empty string also) message data will be printed in a friendly way (e.g. XML data will be printed with children on separate lines).
;This parameter is applied on reload.
;Defaults to verbose.
print_msg_data=verbose

;Ask for IMEI when updating location.
;This parameter is applied on reload.
;Defaults to yes
imei_request=yes

;Interval, in seconds, to keep TMSIs.
;This interval should be enforced in the applications, not ybts.cpp
;This parameter is applied on reload.
;Allowed interval: 7200..2592000.
tmsi_expire=864000

;Disconnect (hangup) timeout interval in milliseconds.
;After sending Disconnect the call will wait for Release or Release Complete.
;Release will be sent on timer expiry.
;This parameter is applied on reload.
;Interval allowed: 20000..60000
;Defaults to 30000
t305=30000

;Release timeout interval in milliseconds (wait for Release Complete).
;Release will be sent on first expiry, call reference will be released on second expiry.
;This parameter is applied on reload.
;Interval allowed: 4000..20000
;Defaults to 5000
t308=5000

;Connect (answer) timeout interval in milliseconds (wait for Connect Ack)
;Call reference will be released on expiry
;This parameter is applied on reload
;Interval allowed: 4000..20000
;Defaults to 5000
t313=5000

;Interval, in milliseconds, to wait for a MT SMS to complete
;This interval includes paging if needed.
;This parameter can be overridden in the msg.execute message by a 'timeout' parameter.
;This parameter is applied on reload.
;Interval allowed: 5000..600000
;Defaults to 300000
sms.timeout=300000

;Timeout, in milliseconds, of USSD sessions.
;This parameter configures the overall USSD session duration.
;When timed out a session will be terminated.
;This parameter can be overridden in the msg.execute message by a 'timeout' parameter.
;This parameter is applied on reload.
;Minimum allowed value is 30000.
;Defaults to 600000 (10 minutes)
ussd.session_timeout=600000

;Specify in which way the XML will be passed along into Yate messages.
;Allowed values are:
;- string: pass the XML as a string
;- object: pass the XML as an object
;- both: pass the XML as a string and object
;This parameter is applied on reload
;Defaults to object.
export_xml_as=object


[security]
;Interval (in milliseconds) to wait for a response to authentication requests.
;Authentication will be aborted on timer expiry.
;This parameter is applied on reload.
;Interval allowed: 5000..3600000
;Defaults to 720000
t3260=720000

;Authenticate MS on MT calls. This parameter is applied on reload. Defaults to 'no'.
auth.call=no

;Authenticate MS on MT SMS. This parameter is applied on reload. Defaults to 'no'.
auth.sms=no

;Authenticate MS on MT USSD. This parameter is applied on reload. Defaults to 'no'.
auth.ussd=no


[roaming]
;Expire time for registrations.
expires=3600

;String: ip:port where SIP requests are sent.
;It is REQUIRED to set reg_sip or nodes_sip.
;Example: reg_sip=192.168.1.245:5058
;reg_sip=

;json object: node => ip:port of each YateUCN server
;node, which is computed based on the TMSI received from the handset.
;This ensures that registrations are always sent to the same YateUCN server.Example: nodes_sip={"123":"192.168.1.245:5058","101":"192.168.1.176:5059"}
;nodes_sip=

;Int: Number of bits to use for
;the Non Access Stratum (NAS) Node Selection Function (NNSF).
nnsf_bits=8

;string: ip:port for the local SIP listener.
;Unless otherwise configured, this is the IP of the machine
;where YateBTS is installed.
;Example: my_sip=198.168.1.168
;my_sip=

;String: unique number that identies the cell in the national database
;Associated to each base station by the network operator.
;gstn_location=

;If possible decode and send the SMS as text/plain SIP MESSAGE body.
;By default the binary type application/vnd.3gpp.sms is used.
text_sms=no


[handover]
;Globally enable handover functions.
;Default is enabled.
enable=yes

;Comma separated list of neighbor SIP addresses.
;Each neighbor will be periodically queried for target handover availability.
;Example: neighbors=10.0.0.1, 10.0.0.2, 10.0.0.3:5065.
;Default is empty.
;neighbors=

;Text to place in the Reason SIP header.
;An empty or boolean false value disables the Reason header.
;Default: GSM;text="Handover".
reason=GSM;text="Handover"


[logging]
; This section controls the logging levels of MBTS.
; Level: keyword: Default logging level of MBTS.
; Valid values are: EMERG, ALERT, CRIT, ERR, WARNING, NOTICE, INFO, DEBUG.
; Defaults to NOTICE.
;Level=NOTICE

Lfsnoob

  • Newbie
  • *
  • Posts: 18
    • View Profile
Re: Cant detect cellular network
« Reply #19 on: October 12, 2018, 09:06:42 PM »

Ioana Stanciu

  • Jr. Member
  • **
  • Posts: 74
    • View Profile
Re: Cant detect cellular network
« Reply #20 on: October 15, 2018, 02:59:43 AM »
Is this a clean install (meaning you removed configuration files also)? I stil see the transciever configuration that disappeared 3 years ago.
Is the install from the official sources (using YATE SVN https://wiki.yatebts.com/index.php/Installing) as per the tutorials from the YateBTS wiki links?
Which is the YATE version ('yate --version' command in a terminal) ?

Also, there is an option to attach files to forum posts.

Lfsnoob

  • Newbie
  • *
  • Posts: 18
    • View Profile
Re: Cant detect cellular network
« Reply #21 on: October 15, 2018, 07:02:48 AM »
Yes this is a clean install since I flashed the sd card for os raspbian stretch. Thats strange, that the old transceiver files are there because I did follow the install guide you sent me.

yate --version
Yate 6.1.1 devel1 r6325

david.burgess

  • Newbie
  • *
  • Posts: 22
    • View Profile
Re: Cant detect cellular network
« Reply #22 on: November 06, 2018, 10:31:34 AM »
These are the common reasons for the phone not to see the network:

- Hardware or USB errors corrupting the beacon transmission. If this were happening you would get a lot of warnings. (The "TOA error" message at the "ALL" debug level is not a warning. It is part of a routine timing calculation.)

- Weak signal. What kind of antenna are you using?  Also, set Radio.PowerManager.MaxAttenDB and Radio.PowerManager.MinAttenDB both to 0 maximize output power.

- Excessive CPU loading corrupting the beacon transmission. The log shows a few places where the radio ran late and dropped the signal, but not so much that it should be a problem. What does "top" show for yate when you are running YateBTS?

- Bad frequency calibration. Have you enabled NTP on your computer and BladeRF frequency calibration in YateBTS?

- Interference. What country are you in? What band and ARFCN have you configured? The config file you sent shows Radio.C0 = 0. Did you fix that before running?