diff options
author | Philipp Maier <pmaier@sysmocom.de> | 2018-02-22 16:44:41 +0100 |
---|---|---|
committer | Philipp Maier <pmaier@sysmocom.de> | 2018-03-07 18:10:23 +0100 |
commit | ce1298b7dce06a6577da1df328f901d6f8a12501 (patch) | |
tree | 916e6d650b967c6d0d0908a62079398dc7c3574d /src/libmsc/osmo_msc.c | |
parent | 48d4ec06e180cfb60556ce6c565620078bbea8db (diff) |
a_iface: fix BSSMAP reset handling
When osmo-msc restarts it looses all information about the BSC. The
BSC will not be aware of the reboot and on the next communication
attemt it will notice that something is wrong and start the reset
procedure on his side. osmo-msc will receive the reset messages
and send a reset.
The reset is received. Osmo-msc detects that no context information
is created yet. The context is created. Then it is checked if the
UNITTDATA message that came in is a reset. If it is one. Nothing
happens. The UNITTDATA is passed on and triggers the RESET-ACK
some layers above. Unfortunately by the current code this also
means that no reset FSM is created and therefore a_reset_conn_ready()
can never be true. Which means it will also drop any legitimate
reset from the BSC in the future.
- Ensure that the reset FSM is always created when a new BSC
context is created
- Make sure that reset related traffic always passes so that
the higher layers can handle the procedure properly
Change-Id: I3fdcec5dbeaa0e21fd6a92568a623faa368239be
Diffstat (limited to 'src/libmsc/osmo_msc.c')
0 files changed, 0 insertions, 0 deletions