This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Harald Welte laforge at gnumonks.orgHi Neels,
On Mon, Jul 24, 2017 at 03:35:37PM +0200, Neels Hofmeyr wrote:
> What about this one: I assume handover will be an entirely different issue to
> be tackled with the new A-interface and we can drop this VTY command without
> substitute for now?
You have to differentiate between intra-BSC hand-over and inter-BSC hand-over
(or even inter-MSC hand-over).
Intra-BSC hand-over is exactly like it is now. The command you're referring
to thus simply has to go to into the BSC. The only problem is that the
subscriber will probably not be possible to be identified by the IMSI
as the BSC doesn't normally cache that information. But what kind of
identifier do we show in "show lchan"? TMSI? SCCP Connection ID?
This VTY command is quite essential to test hand-over during development and testing.
Once we have the Osmocom extension TLVs by which the MSC can provide a
subscriber identity to the BSC, we can re-introduce identifying the subscriber
connection by such identity/name.
Inter-BSC or Inter-MSC handover is something that we didn't have in NITB,
but which is not really relevant to this question.
--
- Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)