diff options
author | Neels Hofmeyr <neels@hofmeyr.de> | 2020-07-29 01:22:11 +0200 |
---|---|---|
committer | laforge <laforge@osmocom.org> | 2020-08-13 05:37:44 +0000 |
commit | 90a07524d195b93d5050d7fdbd6675846fe3c7ff (patch) | |
tree | 9f27978f29386f52ac77cc5752c295c37e17f6c0 /bsc | |
parent | a16afdc4c698cb190d6858e432743328ef4cccdd (diff) |
bsc CBSP: cosmetic: rename f_cbsp_init_tail() to f_expect_cbsp_restart()
It might be part of initialization, but what this function does is expect to
receive a CBSP RESTART, period.
Change-Id: Ieffe70cf43eb79b798d93717bbce294ee809f0e2
Diffstat (limited to 'bsc')
-rw-r--r-- | bsc/BSC_Tests_CBSP.ttcn | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/bsc/BSC_Tests_CBSP.ttcn b/bsc/BSC_Tests_CBSP.ttcn index 413ab5df..8b7954da 100644 --- a/bsc/BSC_Tests_CBSP.ttcn +++ b/bsc/BSC_Tests_CBSP.ttcn @@ -125,9 +125,9 @@ private function f_cbsp_init_server(float guard_timeout := 30.0) runs on cbsp_te mtc.stop; } } - f_cbsp_init_tail(); + f_expect_cbsp_restart(); } -private function f_cbsp_init_tail() runs on cbsp_test_CT { +private function f_expect_cbsp_restart() runs on cbsp_test_CT { interleave { [] CBSP[0].receive(tr_CBSP_Recv(?, tr_CBSP_RESTART(?, CBSP_BC_MSGT_CBS, CBSP_RI_DATA_LOST))); /* should we also expect a restart for emergency related messages? */ |