Hi Ron,
sorry for the late response.
First of all, thanks for your two bug / experience reports.
One very important bit was missing: Which exact version of the relevant osmocom programs were you using when observing the two issues, respectively?
There's a lot of development going on, and without pin-pointing the exact versions it's hard to understand whether or not the related problem might still apply to current 'master', or whether it is likely a regression, etc.
You can use "show version" on the VTY or call the respective program with "--version" command-line argument to extract the version information.
If you have the time, it would also be very useful if you could file those two bugs as two separate issues in the respective issue tracker of the respective program (OsmoBSC in this case) on osmocom.org.
Thanks in advance!