Harald Welte has submitted this change and it was merged.
Change subject: DTAP: Ensure proper DLCI is used in MSC-originated DTAP
..
DTAP: Ensure proper DLCI is used in MSC-originated DTAP
The DLCI field of the DTAP header indi
Patch Set 2: Code-Review+2
--
To view, visit https://gerrit.osmocom.org/7690
To unsubscribe, visit https://gerrit.osmocom.org/settings
Gerrit-MessageType: comment
Gerrit-Change-Id: If511b20f52575054cab1346d99a8cb68d827fdbf
Gerrit-PatchSet: 2
Gerrit-Project: osmo-msc
Gerrit-Branch: master
Gerrit
Patch Set 2: Verified+1
--
To view, visit https://gerrit.osmocom.org/7690
To unsubscribe, visit https://gerrit.osmocom.org/settings
Gerrit-MessageType: comment
Gerrit-Change-Id: If511b20f52575054cab1346d99a8cb68d827fdbf
Gerrit-PatchSet: 2
Gerrit-Project: osmo-msc
Gerrit-Branch: master
Gerrit-Ow
DTAP: Ensure proper DLCI is used in MSC-originated DTAP
The DLCI field of the DTAP header indicates the SAPI as well as the
data link (main DCCH or SACCH). We must make sure to use the correct
DLCI when sending DTAP to the BSC.
We achieve this by
* storing the DLCI in the msgb->cb while parsing
Review at https://gerrit.osmocom.org/7690
DTAP: Ensure proper DLCI is used in MSC-originated DTAP
The DLCI field of the DTAP header indicates the SAPI as well as the
data link (main DCCH or SACCH). We must make sure to use the correct
DLCI when sending DTAP to the BSC.
We achieve this by
* st
