tree dc0c0217ef4360053518a3a48b183c01709cd040
parent 803af35d25e879eaeef2093f2b07771e9381aa9a
author Neels Hofmeyr <nhofmeyr@sysmocom.de> 1687819868 +0200
committer neels <nhofmeyr@sysmocom.de> 1689003297 +0000

hnbgw: drop dead code from MSC_UnitdataCallback

This RANAP RESET code...

a) is not used:
osmo-hnbgw has only recently started sending RANAP UnitData by its own initiative.
Until very recently, osmo-hnbgw has only responded to receiving a RESET, with an ACK.
It has never sent a RESET message to the peer, here titan.

b) makes no sense implementation wise:
RANAP RESET handling is actually implemented in RAN_EMulation.ttcnpp.

c) makes no sense protocol wise:
The UnitDataCallback happens when osmo-hnbgw sends a RANAP UnitData to
titan: if at all, the only logical response would be a RESET ACK
message, not a RESET message.

Change-Id: Ie7b9022e991b63b945c7ec6e5c9f7c4eb5da4d7e