handover: re-enable legacy neighbor configuration

By adding the new 'neighbor' vty config, I actually broke legacy configuration
of neighbors by 'neighbor-list': even though the System Information will send
out the configured ARFCN+BSIC, when the MS reports a better RXLEV on one of
them, we would not actually find this neighbor, since an explicit neighbor
mapping is not present.

Add a fallback to looking for a matching cell in all local cells, only if no
explicit neighbor mappings exist, to still allow legacy neighbor configuration
without explicit mappings.

Change-Id: I568359e7744a3fe6f835d717229402214bcf5ab4

0 files changed, 0 insertions, 0 deletions