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, Apr 04, 2016 at 10:06:59AM +0200, Neels Hofmeyr wrote:
> I wasn't aware yet, but in the pcaps, there is indeed an RNC Id sent from
> the HNB-GW during the HNB_REGISTER_ACCEPT (e.g. 14). But subsequently the
> hNodeB sends a different RNC Id (the one configured in the hNodeB
> settings, e.g. 0). So our hNodeB apparently doesn't remember the RNC Id it
> receives during the HNB_REGISTER_ACCEPT.
>
> What would you say, is this just yet another thing that the operator has
> to configure correctly? Is it a spec violation by our particular hNodeB?
Yes, I think it is a bug / spec violation / different interpretation.
> Or should the HNB-GW actually overwrite the RNC-Id going to the CN?
No.
> For the time being I'll just configure the hNodeB and the HNB-GW to use
> the same RNC Id.
Ack.
--
- 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)