tree bf9f0896bd5e26067d29a61a88f8f4f23f909f1a
parent 7dedebada5c5dc08e1c5aa4a90f5d1c41f948e91
author Harald Welte <laforge@osmocom.org> 1583684489 +0100
committer Harald Welte <laforge@osmocom.org> 1583684820 +0100

gsmtap: Solve TCH / FACCH confusion once and for all

* What we used to call TCH/F and TCH/H in gsmtap are actually only
  FACCH/F and FACCH/H, i.e. the signaling part of Bm/Lm channels

* Give them proper names with backwards compatibility #define

* Split VOICE into VOICE_F and VOICE_H.  If we don't differentiate this,
  a receiver is not able to determine the RSL channel ID of a frame
  without looking at external state/context.  That in turn has been a
  design feature of GSMTAP Um format so far, and programs like
  osmo-bts-virtual rely on it.

Change-Id: I952044a17334f35712e087dc41781805000aebc1
Related: OS#2557