Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Ib9856d93d1f925380177d22ddb1266e08c67485d
|
|
Change-Id: I36404b34b8a85fc98670a3eeb8aaf29a4a6f10ea
|
|
The bsc side currently can not receive reset commands from an
MSC. This patch adds required functionality to receive a reset
command and acknowlege it properly. The effects are the same
as with when sending resets (all drop all ongoing calls and
sccp connections)
Change-Id: I44c7e54c845948c54614b36d97d2ba1e760ac46b
|
|
The AoIP standard also describes an MSC->BSC reset procedure. We
currently do not implement it. However, the fsm that is used to
issue the reset request from the bsc side is not generalized. This
patch generalizes the code in order to be able to use the same
code on the MSC side to perform a reset procedure from there.
Change-Id: I65e20bebb126ba35122ca3a545393d18fcadf5ad
|
|
Change-Id: I4220bc9a3a6f13fd6b09c3a7edadea5b8823d1c5
|
|
Improve the way the BSC executes its RESET/RESET-ACK sequence.
Currently only a simple bool variable serves as a state holder.
We set this variable to true when we receive the RESET-ACK
message. Unfortunately no further checking is done. This
patch replaces the old mechanism with a more elaborated
implementation which also detects a loss of the connection
and makes sure to reconnect properly afterwards. Also the
all open connections are closed on connection loss
Change-Id: I876319b15103cc395e74597a52ce4d1a934915f4
|
|
Change-Id: I5ae4e05ee7c57cad341ea5e86af37c1f6b0ffa77
|