The talker requests uplink. The UPLINK REQUEST is rejected by the MSC.
The uplink is marked free again.
Change-Id: Iba4dd21a69d49e6a8508b15b823ffccc7f0dafc9
The existing tests (talker fails, talker establishes, talker releases)
delay, so the MSC acknowledges the UPLINK REQUEST first. It is expected
that the events of the talker (failure, establishment, release) are
forwarded to the MSC after the acknowledgement.
New tests are added, so that the MSC acknowledges the UPLINK REQUEST
late. It is expected that the events of the talker are not forwarded
before the MSC acknowledges.
The BSC (under test) must queue the events of the talker before the MSC
has acknowledged the UPLINK REQUEST.
Change-Id: I28081e62287bdc17a3b477d9368f977aedce01c8
After sending UPLINK SEIZED COMMAND or UPLINK RELEASE COMMAND the timer
must be started, in order to collect data from the outcome of the test.
The test will fail sometimes, if this is not done.
Change-Id: Ic48e9c259b42ee6e030ea5d05b113ce2933e2247
The talker requests uplink. Instead of receiving link establishment from
the BTS, the BSC receives a link failure. The MSC expects to receive an
UPLINK RELEASE INDICATION, caused by radio link failure.
Change-Id: Ied56a6bdc0bfa541b1419e63e9e209ed20af804c
The MSC will block (seize) or unblock (release) the uplink on one BSC,
if a talker requests or releases uplink on a different BSC. An UPLINK
BUSY or UPLINK FREE message es expected to be sent to the BTS.
Change-Id: I7ebf03662e81f59d76ca8d8fa29f581043053564
There is no UPLINK BUSY message sent by BSC, if the talker
requests/establishes the uplink. Due to timing reason, the message is
sent by the BTS itself towards the MS.
Change-Id: I2e3b866eca174ae212ea986980d508e48e31fa57
Andreas Eversberg
Harald Welte