Bug #1578
closed
might make sense to start with a BTS_Tests.ttcn TTCN-3 test case to check modification of encryption parameters. That will then fail and should get fixed with a proper bugfix in osmo-bts.
laforge wrote in #note-1:
might make sense to start with a BTS_Tests.ttcn TTCN-3 test case to check modification of encryption parameters. That will then fail and should get fixed with a proper bugfix in osmo-bts.
For the record, we do have BTS_Tests.TC_rsl_modify_encr in ttcn3-bts-test. According to Jenkins, "it's Failing for the past 697 builds (Since 905)".
- Status changed from New to Resolved
- Assignee changed from osmith to fixeria
- % Done changed from 0 to 100
The problem has been fixed months ago:
https://gerrit.osmocom.org/c/osmo-bts/+/29217
commit 52da5b6f6474183bb399f6de7d731335bb050041
Author: Vadim Yanitskiy <vyanitskiy@sysmocom.de>
Date: Sat Aug 27 18:45:05 2022 +0700
osmo-bts-trx: fix handling of ciphering params in PRIM_INFO_MODIFY
Also available in: Atom
PDF
