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/.
Sebastian Stumpf sebastian.stumpf87 at googlemail.comHi Harald, here is an update on the virt-phy (and some more problems ;)). I implemented the simple scheduler and it seems to work fine. I was happy to find the assignment of channels to their respective frame in the mframe in https://github.com/osmocom/osmocom-bb/blob/master/src/target/firmware/layer1/mframe_sched.c#L67-L292 and used that to calculate the fn the messages should be scheduled in. Thanks to your suggestions I could also fix some errors and produced a new capture file. https://www.dropbox.com/s/145w5c5kqwlk5ey/mobile--ms-virt--bts-virt--bsc-nitb_170228%3Ahyperframe_fast_repeat_test.pcapng?dl=0 I come some steps further but are still having trouble to: Send an sms to myself using the extension assigned to my ms from osmo-nitb (see 2341 in cap-file). VTY: sms 1 12 "Hallo zusammen" OsmocomBB# % (MS 1) % SMS to 12 failed: Semantically Incorrect Message Call myself (11851 in cap file) VTY: OsmocomBB# call 1 12 OsmocomBB# % (MS 1) % Call has been released Losing RR connection after some time. LOG-mobile: Tue Feb 28 17:16:35 2017 DRR <0001> gsm48_rr.c:662 MON: no cell info LOG-virt-phy: Tue Feb 28 17:16:34 2017 DL1C Message incoming from layer 2: 0d 00 00 00 01 00 00 00 Tue Feb 28 17:16:34 2017 DL1C Received and handled from l23 - L1CTL_RESET_REQ (type=FULL) Tue Feb 28 17:16:34 2017 DL1C Sending to l23 - L1CTL_RESET_CONF (reset_type: 1) Tue Feb 28 17:16:34 2017 DL1C Message incoming from layer 2: 08 00 00 00 01 00 00 00 00 00 00 7c Tue Feb 28 17:16:34 2017 DL1C Received from l23 - L1CTL_PM_REQ TYPE=1, FROM=0, TO=124 Tue Feb 28 17:16:34 2017 DL1C Message incoming from layer 2: 08 00 00 00 01 00 00 00 00 80 00 fb Tue Feb 28 17:16:34 2017 DL1C Received from l23 - L1CTL_PM_REQ TYPE=1, FROM=128, TO=251 Tue Feb 28 17:16:34 2017 DL1C Message incoming from layer 2: 08 00 00 00 01 00 00 00 02 00 02 99 Tue Feb 28 17:16:34 2017 DL1C Received from l23 - L1CTL_PM_REQ TYPE=1, FROM=512, TO=665 Tue Feb 28 17:16:34 2017 DL1C Message incoming from layer 2: 08 00 00 00 01 00 00 00 02 9b 03 75 Tue Feb 28 17:16:34 2017 DL1C Received from l23 - L1CTL_PM_REQ TYPE=1, FROM=667, TO=885 Tue Feb 28 17:16:34 2017 DL1C Message incoming from layer 2: 08 00 00 00 01 00 00 00 03 bb 03 ff Tue Feb 28 17:16:34 2017 DL1C Received from l23 - L1CTL_PM_REQ TYPE=1, FROM=955, TO=1023 Tue Feb 28 17:16:34 2017 DL1C Message incoming from layer 2: 08 00 00 00 01 00 00 00 82 00 83 2a Tue Feb 28 17:16:34 2017 DL1C Received from l23 - L1CTL_PM_REQ TYPE=1, FROM=33280, TO=33578 Tue Feb 28 17:16:34 2017 DL1C Message incoming from layer 2: 0d 00 00 00 01 00 00 00 Tue Feb 28 17:16:34 2017 DL1C Received and handled from l23 - L1CTL_RESET_REQ (type=FULL) Tue Feb 28 17:16:34 2017 DL1C Sending to l23 - L1CTL_RESET_CONF (reset_type: 1) Tue Feb 28 17:16:34 2017 DL1C Message incoming from layer 2: 01 00 00 00 83 2a 00 64 27 10 03 20 03 07 00 00 3f Tue Feb 28 17:16:34 2017 DL1C Received and handled from l23 - L1CTL_FBSB_REQ (arfcn=33578, flags=0x7) What I do not understand here is why I get a full power measurement request from mobile although I did set a fixed arfcn in the config. And of course a fbsb req for arfcn 33578 seems simply wrong... Next step after fixing the false fbsb request from l23 would be to add a second mobile and then try to get the mobile originated call to work. Of course i would be happy about other suggestions :). With kind regards, Sebastian Stumpf -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20170228/c889d8b3/attachment.htm>