diff options
| author | Max <msuraev@sysmocom.de> | 2017-06-28 14:29:24 +0200 |
|---|---|---|
| committer | Max <msuraev@sysmocom.de> | 2017-06-28 12:45:22 +0000 |
| commit | 590c402e6cfbdb6dc3953fda7d8e4d55cf293d0a (patch) | |
| tree | 7b8966e542b70b84b106fc2492271680bf2d5644 /src/gb | |
| parent | 70861e33d2c9c65fec19c7ec8328cad67a74e3f4 (diff) | |
BSSGP: handle BVC-RESET-ACK
That's necessary for SGSN to properly handle BSS response to reset
procedure initiated by SGSN (foe example via 'bssgp bvc nsei 101 bvci 0
reset' command).
According to 3GPP TS 48.018 ยง8.4 "after performing the BVC Reset
procedure all affected BVCs are assumed to be unblocked at the SGSN" so
there's no need in any special handling.
Change-Id: I90dfbd0195a8403406429ccc746299d072445f7b
Related: OS#1638
Diffstat (limited to 'src/gb')
| -rw-r--r-- | src/gb/gprs_bssgp.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/src/gb/gprs_bssgp.c b/src/gb/gprs_bssgp.c index 518198fd..8daf39f0 100644 --- a/src/gb/gprs_bssgp.c +++ b/src/gb/gprs_bssgp.c @@ -963,6 +963,9 @@ static int bssgp_rx_sign(struct msgb *msg, struct tlv_parsed *tp, } rc = bssgp_rx_bvc_unblock(msg, tp); break; + case BSSGP_PDUT_BVC_RESET_ACK: + LOGP(DBSSGP, LOGL_ERROR, "BSSGP BVCI=%u Rx BVC-RESET-ACK\n", bvci); + break; case BSSGP_PDUT_BVC_RESET: /* BSS tells us that BVC init is required */ if (!TLVP_PRESENT(tp, BSSGP_IE_BVCI) || |