Actions
Bug #4804
closedTCH/F: Prim has wrong chan_nr=0xc5 link_id=00, expecting chan_nr=0x0d link_id=00
Start date:
10/13/2020
Due date:
% Done:
100%
Spec Reference:
Description
This message appears when a dynamic timeslot is switched from PDCH to TCH/F. I assume that somehow the transmit queue of the timeslot is not properly cleaned. So after switching to TCH/F (expected chan_nr=0x0d), the scheduler takes a PDCH frame (21 octets, chan_nr=0xc5) from Tx queue, and discards it. It's not really critical, but may confuse the user. We need to flush the queues.
Actions
