How to 'POWERON' the osmo-trx

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

cruise zhankun_bi at 163.com
Mon May 11 08:54:24 UTC 2020


Thanks for your detailed and generous explanation. I am a beginner on 
openBSC, looking forward to your guidance.

There are some files in the attachment, i don't know whether they are 
enough.

1. The config files of osmo-trx, osmo-bts-trx and osmo-nitb. They are 
the original files downloaded from git repository, and i select one of 
them to run the application, i don't know whether they are correct, and 
i don't know how to modify it.

2. config.log files of osmo-trx, osmo-bts-trx and osmo-nitb. I don't 
know whether they are the logs you mentioned in your reply. I guess not, 
but i don't know how to get the complete logs, Maybe you give me some tips ?

3. pcap file which includes the data package whose src ip and dst ip are 
the 127.0.0.1, these packages were captured using wireshark.


I guess there are some problems on the config file osmo-nitb-ipa.cfg , i 
select it as the config file without reason, because i don't know how to 
config the file.


thanks for your help again.


在 2020/5/9 下午8:52, Pau Espin Pedrol 写道:
> Hi,
>
> the problem is not in osmo-bts-trx <-> osmo-trx, that's working fine so
> far on your setup (sending a POWEROFF at startup is fine since then it
> makes sure the osmo-trx is powered off before configuring it and finally
> running POWERON on it). It won't be configured until the BSC (in your
> case osmo-nitb) instructs osmo-bts-trx on how to do it through Abis OML
> connection.
>
> The problem is here:
>
> On 5/9/20 3:15 AM, cruise wrote:
>> *_/About one minutes later, the osmo-bts-trx will exit automatically,
>> and the following messages was printed./_*
>>
>> <0012> e1_input.c:243 abis_sendmsg: msg->dst == NULL: 0c 12 01 90 0f 00 c8
>> <0012> e1_input.c:243 abis_sendmsg: msg->dst == NULL: 0c 12 01 88 12 06
>> 00 00 00 00 00 00
>> <000d> abis.c:143 Signalling link down
>> <0001> bts.c:293 Shutting down BTS 0, Reason Abis close
>> Shutdown timer expired
>
> The  Abis connection, be it OML or RSL, between the BTS and the BSC (in
> your case osmo-nitb) fails at some point. Unfortunately unless you
> provide config files, complete logs and pcap files it's difficult to
> tell you more. Please next time provide those while reporting.
>
>
>> *3. osmo-nitb*
> FYI, osmo-ntib is deprecated and not maintained since years ago.
> Please better use new software stack:
> https://osmocom.org/projects/cellular-infrastructure/wiki
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20200511/327dcdb5/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config_osmo-btx.log
Type: text/x-log
Size: 30953 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20200511/327dcdb5/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config_osmo-nitb.log
Type: text/x-log
Size: 41598 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20200511/327dcdb5/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config_osmo-trx.log
Type: text/x-log
Size: 47612 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20200511/327dcdb5/attachment-0002.bin>
-------------- next part --------------
!
! OsmoBTS (1.2.0.46-40fb) configuration saved from vty
!!
!
log stderr
 logging filter all 1
 logging color 1
 logging print category-hex 1
 logging print category 0
 logging timestamp 0
 logging print file 1
 logging level rsl notice
 logging level oml notice
 logging level rll notice
 logging level rr notice
 logging level meas error
 logging level pag error
 logging level l1c error
 logging level l1p error
 logging level dsp error
 logging level pcu notice
 logging level ho notice
 logging level trx notice
 logging level loop notice
 logging level abis error
 logging level rtp notice
 logging level sum notice
 logging level lglobal notice
 logging level llapd notice
 logging level linp notice
 logging level lmux notice
 logging level lmi notice
 logging level lmib notice
 logging level lsms notice
 logging level lctrl notice
 logging level lgtp notice
 logging level lstats notice
 logging level lgsup notice
 logging level loap notice
 logging level lss7 notice
 logging level lsccp notice
 logging level lsua notice
 logging level lm3ua notice
 logging level lmgcp notice
 logging level ljibuf notice
 logging level lrspro notice
!
stats interval 5
!
line vty
 no login
!
e1_input
 e1_line 0 driver ipa
 e1_line 0 port 0
 no e1_line 0 keepalive
phy 0
 osmotrx ip local 127.0.0.1
 osmotrx ip remote 127.0.0.1
 osmotrx base-port local 5800
 osmotrx base-port remote 5700
 osmotrx fn-advance 20
 osmotrx rts-advance 5
 instance 0
bts 0
 band DCS1800
 ipa unit-id 6969 0
 oml remote-ip 192.168.122.1
 rtp jitter-buffer 100
 rtp port-range 16384 17407
 paging queue-size 200
 paging lifetime 0
 uplink-power-target -75
 gsmtap-sapi ccch
 gsmtap-sapi pdtch
 min-qual-rach 50
 min-qual-norm -5
 max-ber10k-rach 1707
 smscb queue-max-length 15
 smscb queue-target-length 2
 smscb queue-hysteresis 2
 trx 0
  power-ramp max-initial 5000 mdBm
  power-ramp step-size 1000 mdB
  power-ramp step-interval 2
  ms-power-control osmo
  phy 0 instance 0
-------------- next part --------------
!
! OpenBSC configuration saved from vty
!   !
password foo
!
line vty
 no login
!
e1_input
 e1_line 0 driver ipa
network
 network country code 1
 mobile network code 1
 short name OpenBSC
 long name OpenBSC
 auth policy closed
 location updating reject cause 13
 encryption a5 0
 neci 1
 rrlp mode none
 mm info 1
 handover 0
 handover window rxlev averaging 10
 handover window rxqual averaging 1
 handover window rxlev neighbor averaging 10
 handover power budget interval 6
 handover power budget hysteresis 3
 handover maximum distance 9999
 bts 0
  type sysmobts
  band DCS1800
  cell_identity 0
  location_area_code 1
  training_sequence_code 7
  base_station_id_code 63
  ms max power 15
  cell reselection hysteresis 4
  rxlev access min 0
  channel allocator ascending
  rach tx integer 9
  rach max transmission 7
  ip.access unit_id 1801 0
  oml ip.access stream_id 255 line 0
  gprs mode none
  trx 0
   rf_locked 0
   arfcn 514
   nominal power 23
   max_power_red 20
   rsl e1 tei 0
   timeslot 0
    phys_chan_config CCCH+SDCCH4
   timeslot 1
    phys_chan_config SDCCH8
   timeslot 2
    phys_chan_config TCH/F
   timeslot 3
    phys_chan_config TCH/F
   timeslot 4
    phys_chan_config TCH/F
   timeslot 5
    phys_chan_config TCH/F
   timeslot 6
    phys_chan_config TCH/F
   timeslot 7
    phys_chan_config TCH/F
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmo-openbsc.pcap
Type: application/vnd.tcpdump.pcap
Size: 500 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20200511/327dcdb5/attachment-0003.bin>
-------------- next part --------------
log stderr
 logging filter all 1
 logging color 1
 logging print category 1
 logging timestamp 1
 logging print file basename
 logging level set-all info
!
line vty
 no login
!
trx
 bind-ip 127.0.0.1
 remote-ip 127.0.0.1
 egprs disable
 ! 28 dB offset below is valid only for the B2xx in 1800 MHz band, see
 ! https://osmocom.org/issues/4468 for more details
 rssi-offset 28.000000
 tx-sps 4
 rx-sps 4
 clock-ref external
 rt-prio 18
 chan 0



More information about the OpenBSC mailing list