Actions
Bug #3253
closedosmo-bts-trx doesn't enable A5/3
Start date:
05/09/2018
Due date:
% Done:
100%
Spec Reference:
Description
I've implemented a set of encryption related test cases in BTS_Tests.ttcn
, see the laforge/bts-encryption
branch at http://git.osmocom.org/osmo-ttcn3-hacks/commit/?h=laforge/bts-encryptionx%x%
TC_chan_act_a51
and TC_chan_act_a52
pass without trouble, while TC_chan_act_a53
fails: The RSL/RLL message sent on Abis to the BTS never is received on L1CTL.
trxcon seems to correctly detect that A5/3 is selected, but then appears to be unable to make sense of the bursts it receives:
<0001> l1ctl.c:731 L1CTL_CRYPTO_REQ (algo=A5/3, key_len=8) <0006> sched_lchan_xcch.c:106 Received bad data frame at fn=185 (83/102) for SDCCH/4(2) <0006> sched_lchan_xcch.c:106 Received bad data frame at fn=195 (93/102) for SACCH/4(2) <0005> sched_clck.c:140 Clock indication: fn=204 <0006> sched_lchan_xcch.c:106 Received bad data frame at fn=236 (32/102) for SDCCH/4(2) <0005> sched_clck.c:140 Clock indication: fn=255 <0006> sched_lchan_xcch.c:106 Received bad data frame at fn=287 (83/102) for SDCCH/4(2) <0006> sched_lchan_xcch.c:106 Received bad data frame at fn=297 (93/102) for SACCH/4(2) <0005> sched_clck.c:140 Clock indication: fn=306 <0006> sched_lchan_xcch.c:106 Received bad data frame at fn=338 (32/102) for SDCCH/4(2) <0005> sched_clck.c:140 Clock indication: fn=357 <0006> sched_lchan_xcch.c:106 Received bad data frame at fn=389 (83/102) for SDCCH/4(2) <0006> sched_lchan_xcch.c:106 Received bad data frame at fn=399 (93/102) for SACCH/4(2) <0005> sched_clck.c:140 Clock indication: fn=408 <0006> sched_lchan_xcch.c:106 Received bad data frame at fn=440 (32/102) for SDCCH/4(2) <0005> sched_clck.c:140 Clock indication: fn=459 <0006> sched_lchan_xcch.c:106 Received bad data frame at fn=491 (83/102) for SDCCH/4(2) <0006> sched_lchan_xcch.c:106 Received bad data frame at fn=501 (93/102) for SACCH/4(2) <0005> sched_clck.c:140 Clock indication: fn=510 <0006> sched_lchan_xcch.c:106 Received bad data frame at fn=542 (32/102) for SDCCH/4(2) <0005> sched_clck.c:140 Clock indication: fn=561 <0006> sched_lchan_xcch.c:106 Received bad data frame at fn=593 (83/102) for SDCCH/4(2) <0006> sched_lchan_xcch.c:106 Received bad data frame at fn=603 (93/102) for SACCH/4(2) <0005> sched_clck.c:140 Clock indication: fn=612 <0006> sched_lchan_xcch.c:106 Received bad data frame at fn=644 (32/102) for SDCCH/4(2) <0005> sched_clck.c:140 Clock indication: fn=663 <0006> sched_lchan_xcch.c:106 Received bad data frame at fn=695 (83/102) for SDCCH/4(2) <0006> sched_lchan_xcch.c:106 Received bad data frame at fn=705 (93/102) for SACCH/4(2) <0005> sched_clck.c:140 Clock indication: fn=714 <0006> sched_lchan_xcch.c:106 Received bad data frame at fn=746 (32/102) for SDCCH/4(2) <0005> sched_clck.c:140 Clock indication: fn=765 <0006> sched_lchan_xcch.c:106 Received bad data frame at fn=797 (83/102) for SDCCH/4(2) <0006> sched_lchan_xcch.c:106 Received bad data frame at fn=807 (93/102) for SACCH/4(2) <0005> sched_clck.c:140 Clock indication: fn=816
Files
Related issues
Actions