Actions
Bug #4287
closedPCU_Tests_RAW: Missing handling of PCU_IF_MSG_ACT_REQ from osmo-pcu
Start date:
11/29/2019
Due date:
% Done:
100%
Spec Reference:
Description
We are currently not handling that message, and it's blocking one my WIP tests (TC_mt_ping_pong) because my tests expects tr_PCUIF_DATA_REQ():
18:34:40.726162 mtc PCU_Tests_RAW.ttcn:689 Matching on port BTS PCU_IF_MSG_ACT_REQ (64) with PCU_IF_MSG_DATA_REQ (0) unmatched.u{ act_req := { is_activate := 1 , trx_nr := 0, ts_nr := 7, spare := '00'O } } with { data_req := { sapi := PCU_IF_SAPI_PCH (3), len := ?, data := ?, fn := ?, arfcn := ?, trx_nr := 0, ts_nr := 0, block_nr := ?, rssi := 0, ber10k := 0, ta_offs_qbits := 0, lqual_cb := 0 } } unmatched: First message in the queue does not match the template:
That seems to happen as a result of sending a data packet SGSN->PCU.
I briefly discussed it with fixeria :
<fixeria> I think it needs to be handled in the BTS component <fixeria> i.e. the BTS component could maintain a list of timeslots, where each one can be in two states: active / inactive <fixeria> at least for now we could just receive and ignore it in the BTS componen
Updated by pespin over 4 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/16400 pcu: Handle PCUIF (DE)ACT.req messages
Actions