Second call on encrypted connection

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/.

Andreas Eversberg andreas at eversberg.eu
Wed Jul 10 19:27:16 UTC 2013


Holger Hans Peter Freyther wrote:
> it should not happen (as the periodic LU timer should be stopped),
> but imagine the 'unsigned int' would be an 'enum', we would now have
> a warning about unhandled cases (e.g. not building a partition over
> the enum) and it is good practice to avoid it.
there is a "default:", which will not cause any warning, since it 
handles all unhandled cases above.
> a.) If it can happen support it
> b.) If it can not happen, use LOGL_ERROR so we potentially notice
> if it does happen and then we can re-consider.
LOGL_ERROR makes sense. maybe it tuns out that there is a call setup 
that caused a cell re-selection and a location updating is sent right 
afterwards.




More information about the OpenBSC mailing list