diff options
| author | Andreas Eversberg <jolly@eversberg.eu> | 2013-02-06 14:13:21 +0100 |
|---|---|---|
| committer | Holger Hans Peter Freyther <zecke@selfish.org> | 2013-04-06 23:23:52 +0200 |
| commit | 6e182087f4ef6cc73f245e0fbc5db11916651ba0 (patch) | |
| tree | 03e38be814962e4d7a00040e3fbf1f273039befd /tests/lapd/lapd_test.ok | |
| parent | b64b2b031344b354b7a59f1eb4c1f97d457613f3 (diff) | |
Fix: LAPDm contention resoltion must acknowledge subsequent SABM
After reception of SABM, the network responds with UA and enters the
establised multiframe state. If UA is not received by mobile, the SABM
is transmitted again, and the network must respond with UA again, unless
it is from a different mobile.
Add LAPDm collision test (contention resolution on network side).
Diffstat (limited to 'tests/lapd/lapd_test.ok')
| -rw-r--r-- | tests/lapd/lapd_test.ok | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/tests/lapd/lapd_test.ok b/tests/lapd/lapd_test.ok index f1b990ea..aa927088 100644 --- a/tests/lapd/lapd_test.ok +++ b/tests/lapd/lapd_test.ok @@ -18,4 +18,7 @@ ms_to_bts_l1_cb: MS(us) -> BTS prim message bts_to_ms_tx_cb: MS->BTS(us) message 14 BTS: Verifying dummy message. I test RF channel release of an unestablished channel. +I test contention resultion by having two mobiles collide and first mobile repeating SABM. +bts_to_ms_tx_cb: MS->BTS(us) message 29 +BTS: Verifying CM request. Success. |