osmo-st-openbsc-test

Archived

This repository has been archived on 2022-02-17. You can view files and clone it, but cannot push or open issues or pull requests.

History

Holger Hans Peter Freyther f453b4cc48 test: Add a DoubleRelease for something seen on a Rhizomatica deployment The combination of SAPI=3 not being established, the T200 expiring and a general SACCH Connection Failure is apparently leading to the NITB releasing a channel twice!		2014-04-19 15:00:17 +02:00
..
DoubleRelease.st	test: Add a DoubleRelease for something seen on a Rhizomatica deployment	2014-04-19 15:00:17 +02:00
README	test: Add a DoubleRelease for something seen on a Rhizomatica deployment	2014-04-19 15:00:17 +02:00

README

This tests some odd LAPDm and MS behavior that leads to a double
RF Channel Release by the BSC/NITB.

It is a manual test right now. After the LU a SMS needs to be
queued through the VTY and then the error/failure sequence will
be sent to the BSC.

The test is passed when no exceptions like the below are raised

An instance of SystemExceptions.NotFound
  creator: Dictionary (
)
  tag: an Object
  messageText: 'key not found'
  resumeBlock: a BlockClosure
  onDoBlock: a BlockClosure
  handlerBlock: a BlockClosure
  context: BlockClosure>>on:do: (BlkClosure.st:196)
  isNested: nil
  previousState: 0
  value: 0
With data: ByteArray (2 7 1 32 2 0 20 1 )
RSL Parsing failed with
An instance of Error
  creator: a LogicalChannel
  tag: an Object
  messageText: 'Lchan was not allocated.'
  resumeBlock: a BlockClosure
  onDoBlock: a BlockClosure
  handlerBlock: a BlockClosure
  context: BlockClosure>>on:do: (BlkClosure.st:196)
  isNested: nil
  previousState: 0
With data: ByteArray (8 46 1 32 )