Hi all!
I just installed and configured osmo-bts-virtual and osmocom-bb with virtphy.
Let me say - this is brilliant! It's so easy to do such things as trigger IMSI Attach and Detach - so much easier than entering and exiting airplane mode or power off/on.
Also, MO sms is a breeze.. I have a script to inject SMS regularly, so I don't have to turn to the mobile and press buttons with each code change in my SMS handler, I just make the change and wait for the next SMS to hit it!
So thanks so much to those responsible for making this happen!
Now, one thing that is failing badly for me right "out-of-the-box" is MT SMS.
As I am totally new to the osmocom-bb code, I guess the best would be a ticket with some pcaps, but I thought I would ask first if it is a known issue?
Basically, BSC is doing this:
DLSMS <0024> gsm_04_11.c:127 GSM4.11 TX [HEX of msg redacted] DLSMS <0024> gsm0411_smc.c:247 SMC(954) TC1* timeout, retrying...
while on the mobile side:
<0005> gsm48_mm.c:3909 (ms 1) Received 'RR_EST_IND' from RR in state MM idle (sapi 0) <0005> gsm48_mm.c:912 new state MM IDLE, normal service -> wait for network command
Then this repeats:
<0001> gsm48_rr.c:4775 Indicated ta 0 (actual ta 0) <0001> gsm48_rr.c:4777 Indicated tx_power 19 <0001> gsm48_rr.c:4799 ACCH message type 0x00 unknown. <0001> gsm48_rr.c:664 MON: f=56 lev=>=-47 snr= 0 ber= 63 LAI=262 42 0001 ID=0000 TA=0 pwr=19 TS=1/1 <0001> gsm48_rr.c:2866 MEAS REP: pwr=19 TA=0 meas-invalid=0 rxlev-full=-47 rxlev-sub=-47 rxqual-full=0 rxqual-sub=0 dtx 0 ba 0 no-ncell-n 7 <0001> gsm48_rr.c:2161 PAGING ignored, we are not camping.
Hi Keith,
On Fri, Sep 08, 2017 at 01:27:59PM +0200, Keith Whyte wrote:
I just installed and configured osmo-bts-virtual and osmocom-bb with virtphy.
Let me say - this is brilliant! It's so easy to do such things as trigger IMSI Attach and Detach - so much easier than entering and exiting airplane mode or power off/on.
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.
Now, one thing that is failing badly for me right "out-of-the-box" is MT SMS.
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 -
Keith Whyte