tree 19ae145e0f0df9edd01860f290c2929113041af4
parent 1338a5543f38c1e1902032a55d37d95e1aa6fe0f
author Holger Hans Peter Freyther <zecke@selfish.org> 1271323044 +0200
committer Holger Hans Peter Freyther <zecke@selfish.org> 1271323044 +0200

[ipa] Handle losing the RSL/OML connection..

This is addressing multiple issues regarding the loss of the
OML/RSL link to the BTS.

1.) When we lose the OML link, close down all RSL connections
on all TRXs (only tested with one TRX) and free the e1inp_line
allocated for the OML connection.
2.) When we lose the RSL link on any TRX and we know to which
lines this connection belongs, we will close down the OML connection
as we have a problem to just reactivate one RSL link.
3.) When we lose the RSL link on any TRX and we do not know
where it belongs to we will free the bfd we have allocated in the
rsl listen/accept method and we properly close the socket (i could
not test this one properly). This is made under the assumption
the BTS has not responded to the ID request.
4.) When we already have a bts->oml_link we will throw it away
and use the new link (it should not happen) and the same applies
to the rsl link.