osmo-msc: Use osmo-mgw instead of osmo-bsc_mgcp osmo-msc now requires osmo-mgw and it's not expected to work properly anymore with old mgcp code. Change-Id: I93033f7b6133a4914f12f37511ad870b3dea3201
jenkins: use env POKY_VERSION POKY_PATH to find poky Instead of hardcoded values, use defaults and allow jenkins to override the defaults. Change-Id: I1403b32cdf30420f3b02c41c2627b71fcbeae9ab
contrib: build-osmo-bsc: Add aibsip-find and ipaccess-config binaries to archive They will be required by Nanobts class. Change-Id: Ib0e003f74603c3146aa76d581ab493f960f73ab5
modem: get IMSI from ofono There's no need to specify the IMSI manually in resource config and it's also prone to errors. Let's take it from ofono. Add a 'sim' feature to allow modem to auto-discover it, otherwise if not supported leave that feature out of the config for that modem and an imsi can still be manually providen. Change-Id: I20f9e8d97775293925205e4ea576d814214bf1a8
example: Maintain different resources.conf for RnD and prod We still want to maintain this file in the same osmo-gsm-tester repo because we frequently neef to update the config when adding new features. Until now only 1 file was maintained (which was used for RnD setup), and then when runnin in prod the jenkins script used sed to change the file to accomodate slightly changes. This way is too hacky, so let's just maintain too separate files, keeping the original resources.conf key name used by osmo-gsm-tester free, so that jenkins job can symlink one of the 2 files to it. Take the chance to remove OctoBTS and Sysmocell5k from the RnD resources file, as we don't have those them. Change-Id: Ifec851c7ac6fca6b294e57dfe86b92f214ae8f42
modem: workaround ofono crash Since commit bfd0b2310cf09e32cb7d5dbe74ec57606a7d2aab, the IMSI is retreived from ofono. To get the IMSI, the modme must be powered ON previously. The imsi() method is called before calling connect() in order to set up the IMSI in the HLR. As a result, the following behaviour occurs: - Powered=true (in imsi()) - SimManager.GetProperties() (several of them) - Powered=false (power_cycle() in connect() It seems powering off the modem immediately after using the SIM service makes ofono crash. Proof of it is that crashes were seen mainly on tests using only 1 MS, in which we don't spend that much time between SimManager.GetProperties() and Powered=false for the same modem. Let's workaround the crash for now increasing the time between using the SIM services and powering the modem off. Related: OS#3064 Change-Id: Ief052cac5a862d6ef9391d40c294ba017387506c
