path: root/tests/msc_vlr/msc_vlr_test_ms_timeout.err
diff options
authorNeels Hofmeyr <neels@hofmeyr.de>2018-04-09 23:29:14 +0200
committerHarald Welte <laforge@gnumonks.org>2018-04-11 21:39:44 +0000
commitdc2514b22062af04354c0331f0f5819051c3fdee (patch)
tree18e2b653003c615f08195e76c75490b2daa58fe5 /tests/msc_vlr/msc_vlr_test_ms_timeout.err
parent79beccd93a27796a2ca9be201a5b9cf3695fbf5c (diff)
CC: intentionally release T308 on BSSMAP Clear Request from BSC
So far we hit a running T308 during CC release when caused by a BSSMAP Clear Request, and we loudly log that as error. However, now I understand that T308 is a direct cause of the dispatch of a REL IND towards MNCC, which is used to indicate teardown to MNCC. So during _gsm48_cc_trans_free(), we first clear all timers, then invoke mncc_release_ind() which starts another timer (useful for graceful CC Release, but in this code path the intention is immediate release). Simply immediately cancel the timer again and release the conn. A separate question is whether a BSSMAP Clear Request should be less aggressive in releasing the connections; i.e. instead of calling trans_free() all around, to rather ask each transaction to "please stop soon", somehow. Related: OS#3062 Change-Id: I231fdb574a086a206321148474cbdc7ca9cf39f0
Diffstat (limited to 'tests/msc_vlr/msc_vlr_test_ms_timeout.err')
0 files changed, 0 insertions, 0 deletions