diff options
| author | Harald Welte <laforge@gnumonks.org> | 2018-04-09 16:35:01 +0200 |
|---|---|---|
| committer | Harald Welte <laforge@gnumonks.org> | 2018-04-09 16:41:10 +0200 |
| commit | 0e2fa5dcb55f77f282f926570b6da0459bd3971c (patch) | |
| tree | 0dd5b0829ebae764cbbd96066d86be3df90eade6 /include/osmocom/msc/transaction.h | |
| parent | 93c7463fcea24517ef367101609f34264570f1d0 (diff) | |
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 the DTAP header
* storing the received DLCI (from msgb->cb) in the transaction for
mobile-originated transactions
* using the trans->dlci to sent msgb->cb when transmitting L3
* filling the DTAP DLCI value from msgb->cb when transmitting DTAP
For MSC-originated transactions, we choose a DLCI value corresponding
to the service (SAPI=0 for CC, SAPI=3 for SMS) and store that in
trans->dlci.
Closes: OS#3150
Change-Id: If511b20f52575054cab1346d99a8cb68d827fdbf
Diffstat (limited to 'include/osmocom/msc/transaction.h')
| -rw-r--r-- | include/osmocom/msc/transaction.h | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/include/osmocom/msc/transaction.h b/include/osmocom/msc/transaction.h index 272fb3b2e..63b1cc519 100644 --- a/include/osmocom/msc/transaction.h +++ b/include/osmocom/msc/transaction.h @@ -31,6 +31,9 @@ struct gsm_trans { /* The current transaction ID */ uint8_t transaction_id; + /* The DLCI (DCCH/ACCH + SAPI) of this transaction */ + uint8_t dlci; + /* To whom we belong, unique identifier of remote MM entity */ struct vlr_subscr *vsub; |