Project

General

Profile

Bug #3493

osmo-bts-trx gprs Attach fails when using TCH/F_PDCH

Added by pespin over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
osmo-bts-trx
Start date:
08/21/2018
Due date:
% Done:

100%

Spec Reference:

Description

When running test voice:trx-b200+mod-bts0-dynts-ipa with osmo-gsm-tester, the modem is unable to GPRS Attach to the network.

That failing test uses TCH/F_PDCH. However, another test using TCH/F_TCH/H_PDCH works fine.
Same test run using osmo-bts-sysmo works fine with both TCH/F_PDCH and TCH/F_TCH/H_PDCH.

I attach an archive with 3 test runs using different configs:
  • run.2018-08-21_17-42-15/gprs:trx-b200+mod-bts0-dynts-ipa: Shows how running osmo-bts-trx with TCH/F_PDCH fails.
  • run.2018-08-21_17-48-47/gprs:sysmo+mod-bts0-dynts-ipa/: Shows how running osmo-bts-sysmo with TCH/F_PDCH succeeds.
  • run.2018-08-21_17-52-16/gprs:trx-b200+mod-bts0-dynts-osmo/: Shows how running osmo-bts-trx with TCH/F_TCH/H_PDCH suceeds.
all-run.tar.gz all-run.tar.gz 3.24 MB pespin, 08/21/2018 04:03 PM

Related issues

Related to OsmoBTS - Bug #1853: validate dynamic TCH/PDCH support in osmo-bts-trxResolved11/18/2016

History

#1 Updated by pespin over 2 years ago

  • Related to Bug #1853: validate dynamic TCH/PDCH support in osmo-bts-trx added

#2 Updated by pespin over 2 years ago

#3 Updated by neels over 2 years ago

comparing the failing run.2018-08-21_17-42-15 to the osmo dyn ts run.2018-08-21_17-52-16:

The succeeding PCU BTS log, on startup, says, for each dyn TS:

20180821175236319 DOML <0001> oml.c:76 Sending PCU version report to BSC: 0.5.1.1-54af
20180821175236319 DPCU <0009> pcu_sock.c:608 Activate request received: TRX=0 TX=2
20180821175236319 DL1C <0006> l1sap.c:1401 activating channel chan_nr=0xc2 trx=0
20180821175236319 DL1C <0006> scheduler.c:621 Activating PDTCH on trx=0 ts=2
20180821175236319 DL1C <0006> scheduler.c:621 Activating PTCCH on trx=0 ts=2
20180821175236319 DL1C <0006> l1sap.c:573 activate confirm chan_nr=0xc2 trx=0
20180821175236319 DRSL <0000> rsl.c:812 (bts=0,trx=0,ts=2,ss=0) not sending CHAN ACT ACK

The failing one lacks the "Activating PxxCH":

20180821174235089 DOML <0001> oml.c:76 Sending PCU version report to BSC: 0.5.1.1-54af
20180821174235096 DPCU <0009> pcu_sock.c:608 Activate request received: TRX=0 TX=2
20180821174235096 DL1C <0006> l1sap.c:1401 activating channel chan_nr=0x0a trx=0
20180821174235097 DL1C <0006> l1sap.c:573 activate confirm chan_nr=0x0a trx=0
20180821174235097 DRSL <0000> rsl.c:812 (bts=0,trx=0,ts=2,ss=0) not sending CHAN ACT ACK

looking now why TCH/F_PDCH fails to activate PDTCH and PTCCH SAPIs...

#4 Updated by neels over 2 years ago

the sysmoBTS version that works has the same chan_nr and still succeeds to activate PDTCH:

20180629135302135 DOML <0001> oml.c:76 Sending PCU version report to BSC: 0.5.1.1-54af
20180629135302137 DPCU <0009> pcu_sock.c:608 Activate request received: TRX=0 TX=2
20180629135302137 DL1C <0006> l1sap.c:1401 activating channel chan_nr=0x0a trx=0
20180629135302137 DL1C <0006> oml.c:1083 (bts=0,trx=0,ts=2,ss=0) MPH-ACTIVATE.req (hL2=0x000200bb, PDTCH TxDL)
20180629135302140 DL1C <0006> oml.c:816 (bts=0,trx=0,ts=2,ss=0) MPH-ACTIVATE.conf (PDTCH TxDL)
20180629135302141 DL1C <0006> oml.c:1083 (bts=0,trx=0,ts=2,ss=0) MPH-ACTIVATE.req (hL2=0x000200bb, PDTCH RxUL)
20180629135302145 DL1C <0006> oml.c:816 (bts=0,trx=0,ts=2,ss=0) MPH-ACTIVATE.conf (PDTCH RxUL)
20180629135302145 DL1C <0006> oml.c:1083 (bts=0,trx=0,ts=2,ss=0) MPH-ACTIVATE.req (hL2=0x000200bb, PTCCH TxDL)
20180629135302150 DL1C <0006> oml.c:816 (bts=0,trx=0,ts=2,ss=0) MPH-ACTIVATE.conf (PTCCH TxDL)
20180629135302150 DL1C <0006> oml.c:1083 (bts=0,trx=0,ts=2,ss=0) MPH-ACTIVATE.req (hL2=0x000200bb, PRACH RxUL)
20180629135302155 DL1C <0006> oml.c:816 (bts=0,trx=0,ts=2,ss=0) MPH-ACTIVATE.conf (PRACH RxUL)
20180629135302155 DL1C <0006> l1sap.c:573 activate confirm chan_nr=0x0a trx=0
20180629135302155 DRSL <0000> rsl.c:812 (bts=0,trx=0,ts=2,ss=0) not sending CHAN ACT ACK

(dropped some log lines in-between for other ts)

#5 Updated by neels over 2 years ago

pespin , can you try an osmo-gsm-tester run of at least osmo-bts-trx for the suites that do

  • osmocom style dyn ts
  • ipa style dyn ts
  • non-dyn ts

with this patch plz: osmo-bts branch neels/trx_dyn_ipa

I hope that fixes it but I have no SDR hardware to test with...
thx!

#6 Updated by pespin over 2 years ago

  • Status changed from New to In Progress
  • Assignee changed from neels to pespin

#7 Updated by pespin over 2 years ago

  • Assignee changed from pespin to neels

Run the 3 tests as requested. The 3 of them pass with branch "neels/trx_dyn_ipa".
https://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester_manual-run/141

#8 Updated by pespin over 2 years ago

Hm wait, I actually run the voice ones. I'll try now with the gprs ones just in case something is wrong there.

#9 Updated by pespin over 2 years ago

The 3 gprs tests pass now too, so your commit fixes the isse: https://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester_manual-run/144

#10 Updated by neels over 2 years ago

  • % Done changed from 0 to 90

#11 Updated by neels over 2 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)