Re: virtphy and MT SMS

Hi Keith, On Fri, Sep 08, 2017 at 01:27:59PM +0200, Keith Whyte wrote: Thanks for the praise. There is of course he limitation that we're testing Osmocom code with Osmocom code, so a mistake in libosmocore will not break any such test. So real hardware is still needed for interoperability and for thesting PHY/hardware/radio related bits. I haven't tried it. My first question would be: Does it work with a real phone and the OsmocomBB layer1 + real BTS? If yes, then something in virt-phy or osmo-bts-virtual would be broken. If it doesn't work there either, then it seems more like an OsmocomBB layer23/mobile problem. I'd be very interested in some kind of scripting language bindings for OsmocomBB so we can run dozens, hundreds or even thousands of OsmocomBB 'mobile' programs runnung concurrently and control them via scripts to perform certain actions, such as: * disable (triggers imsi detach + "shutdown") * enamble (triggers cell selection + LU (imsi attach)" * manually trigger periodic LU ("time warp") * mo-sms * mt-sms * ussd * voice call related actions (at least signaling, for actual voice we first need to extend GSMTAP) In case anyone would be interested in working on this, I'd be very happy to hear about it. As lua is light-weight and embeddable, it might be an idea to include lua in osmocombb. Given that we may want to run thousands of instances, having somehing light-weight would be a good idea. The other idea would be to introduce some kind of rpc/api instead of script language bindings. That API could then be used by some kind of controller (which could be a script, e.g. python), and we wouldn't need as many controller instances as we'd need osmocom-bb 'mobile' instances. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)