Revert "osmo-bts-trx: rx_tchf_fn(): do not treat AFS_SID_UPDATE as SUB frame"
This reverts commit 1f9fbd8816
, which
was a workaround rather than a proper fix. The root problem has
been fixed in libosmocoding [1], so ~50% BER is not the case for
AFS_SID_UPDATE frames anymore.
Related: I813081a4c0865958eee2496fe251ae17235ac842 (libosmocore.git)
Change-Id: Iebe139632daf1d1f72e39fe9d1497059f68625b9
This commit is contained in:
parent
1f9fbd8816
commit
2baf54dd46
|
@ -171,11 +171,7 @@ int rx_tchf_fn(struct l1sched_ts *l1ts, const struct trx_ul_burst_ind *bi)
|
|||
"Received AMR DTX frame (rc=%d, BER %d/%d): %s\n",
|
||||
rc, n_errors, n_bits_total,
|
||||
gsm0503_amr_dtx_frame_name(chan_state->amr_last_dtx));
|
||||
/* ... except AFS_SID_UPDATE, which is in fact a precursor of
|
||||
* the actual SID UPDATE frame (AFS_SID_UPDATE_CN) and only
|
||||
* used internally by gsm0503_tch_afs_decode_dtx() */
|
||||
if (chan_state->amr_last_dtx != AFS_SID_UPDATE)
|
||||
is_sub = 1;
|
||||
is_sub = 1;
|
||||
}
|
||||
|
||||
/* The occurrence of the following frames indicates that we
|
||||
|
|
Loading…
Reference in New Issue