- OpenBSC - lists.osmocom.org

Silent Call vs Test Call vs A-bis Proxy (ip.access-proxy)
by j h 08 May '13

08 May '13

Could someone explain to me the difference between Silent Call, Test Call, and A-bis proxy (ip.access-proxy). To my understanding Test Call opens a pass through UDP port straight to the MS. While SilentCall just creates just creates a open channel. My confusion I believe comes from where you're "sitting" in the eco-system between Silent Call and Test Call. I also am confused after looking at ip.access-proxy. It clearly opens a port for injection either towards the BSC or BTS. However, does a silent-call need to be active to get data to the MS? When I try to inject a simple SMS using ip.access-proxy, (via copying traffic seen across ip.access), I get length disagrees with header. What is ip.access injection expecting in terms of data format? Thanks

2 3

Stress-testing sysmobts of osmo-bts
by Holger Hans Peter Freyther 06 May '13

06 May '13

Hi, I have pushed zecke/work/msgq-reading2 with a work in progress improvement for handling a load from a stress-test. The stress test is to allocate all lchan's at the same time (then let them fail through the radio link timeout) and re-allocate them. This forces the BTS to constantly need to open/close the logical channel resources and also send some (idle) frames (LAPDm is not established in this case). The BTS was sending frames too late and after looking at it with perf it looked like a latency issue (no one is really using the CPU). I have implemented various changes, not all of them are ready: * Change the Bad-Frame-Indicator level to have radio link timeouts with no phone being present. In the above test-case channels remained open as there was no bad-frame-indication on these channels. Pro: There is a constant load for all open channels Bad: We could do this as part of the MphTimeInd but then need to add a bit to the counter to remember if the counter was modified and we need to handle bad frame in two places. * Use writev for the write_queue. This code should/could move into the libosmocore. So for our primitives queue all primitives are the same length and we can use writev to write several frames as the same time. 1.) We go through the queued messages and add them to the iovec 2.) We use writev 3.) We do written / prim_size to see how many buffers were written 4.) We go throuh the queued messages with llist_for_each_entry_safe and remove the count of messages sent. 5.) We check if there are messages left and re-set the notify on writable bit. * Use readv for reading from the queue. This means that we need to allocate N msgb's, call readv, dispatch the messages, free the extra msgb's. Pro: In idle mode there is at least one message to read, with channels open it is likely we will read several messages at once. Bad: Allocating memory is not free. We could start using talloc pools, we could add a msgb_alloc_headroom that does not memset (talloc_zero) the memory. * The above made noticable differences but I also had to get the realtime hammer. I have decided to use SCHED_RR (instead of SCHED_FIFO). This is done with osmo-pcu in mind that needs to read from queues as well and both bts/pcu should be able to inerrupt each other. * For the ts_meas_check_compute we can stop processing the entire TS once we reach a lchan of type lchan == GSM_LCHAN_NONE. (We still need to add a memset of the lchan array into the oml.c code in case there is a re-config). TCH/F: Only lchan[0] is used. TCH/H: Only lchan[0,1] are used. SDCCH8: All of them are used CCCH: lchan[4] is used but we will have no power measurements anyway CCCH/SDCCH4: lchan[0-3] are used. What is not done: * Change the l1if primitive to either use or 'steal' the msgb. All the msgb_free could be removed, only if we forward the MSGB to the PCU socket we would 'steal' it. This would allow us to avoid calling msgb_alloc and msgb_free most of the time. * Add SCHED_RR to the pcu code as well. * Create a talloc pool for the primitives (or re-use the msgb across multiple reads). please review and comment holger

4 7

[EVENT ANNOUNCEMENT] Boston Open GSM Meetup on Friday 10 May 2013
by Robin Coxe 04 May '13

04 May '13

(Apologies for cross-posting. We wanted to reach everyone who might be interested in attending. Please respond responsibly.) Anders Brownworth (Switchcoder), Alexander Chemeris (Fairwaves), and Robin Coxe (Close-Haul Communications & Analog Devices) invite those interested in open GSM hardware and software development to an informal gathering in Cambridge, MA on Friday 10 May 2013 from 6-8 pm. Alexander will be visiting the Boston area from Moscow. If you are interested in participating in any capacity in the Boston-area open source GSM development community, we look forward to meeting you. Our goal is to identify like-minded people involved in or interested in learning more about projects such as OpenBTS, OsmocomBTS, OsmocomBB, and OpenBSC. If you have a portable, self-contained demo, feel free to bring it with you. When: Friday 10 May 2013, 6-8 pm EDT Where: Cambridge Innovation Center, 1 Broadway, 4th Floor, Cambridge, MA 02142 USA Photo ID required for building entry. Please RSVP on Eventbrite: http://opengsmboston.eventbrite.com/

5 5

Uncaught bounce notification
by mailman-bounces＠lists.osmocom.org 02 May '13

02 May '13

The attached message was received as a bounce, but either the bounce format was not recognized, or no member addresses could be extracted from it. This mailing list has been configured to send all unrecognized bounce messages to the list administrator(s). For more information see: https://lists.osmocom.org/mailman/admin/openbsc/bounce

1 0

Nokia InSite GPRS
by Sipos Csaba 01 May '13

01 May '13

Hi, We have two Nokia Insite BTSs and now we are configuring it to work with OpenBSC. But after we installed all the necessary parts (OpenGGSN, OpenSGSN, OpenBSC) we got the following message: "This BTS type does not support gprs" I just wanted to ask that maybe we did something wrong, or the GPRS support for Nokia InSite is not ready yet? If the support is not ready yet maybe there is some alfa or beta stage version that we can try? Nokia Insite family supports GRPS CS-1 and CS-2 according to the specification. Thanks in advance! Csaba

2 1

[PATCH (for jolly/testing)] Fixed seg fault when using sysmobts and added sysmo enum to tch_frame_down
by Alex Duller 27 Apr '13

27 Apr '13

--- openbsc/src/libbsc/bts_ipaccess_nanobts.c | 6 +++--- openbsc/src/libbsc/bts_sysmobts.c | 4 ++++ openbsc/src/libmsc/gsm_04_08.c | 1 + 3 files changed, 8 insertions(+), 3 deletions(-) diff --git a/openbsc/src/libbsc/bts_ipaccess_nanobts.c b/openbsc/src/libbsc/bts_ipaccess_nanobts.c index 16f6a6b..c20d240 100644 --- a/openbsc/src/libbsc/bts_ipaccess_nanobts.c +++ b/openbsc/src/libbsc/bts_ipaccess_nanobts.c @@ -280,7 +280,7 @@ static int nm_statechg_event(int evt, struct nm_statechg_signal_data *nsd) struct gsm_bts_trx_ts *ts; struct gsm_bts_gprs_nsvc *nsvc; - if (nsd->bts->type != GSM_BTS_TYPE_NANOBTS) + if (!is_ipaccess_bts(nsd->bts)) return 0; /* This event-driven BTS setup is currently only required on nanoBTS */ @@ -400,7 +400,7 @@ static int sw_activ_rep(struct msgb *mb) if (!trx) return -EINVAL; - if (trx->bts->type != GSM_BTS_TYPE_NANOBTS) + if (!is_ipaccess_bts(trx->bts)) return 0; switch (foh->obj_class) { @@ -460,7 +460,7 @@ int bts_ipa_nm_sig_cb(unsigned int subsys, unsigned int signal, return 0; } -static struct gsm_network *ipaccess_gsmnet; +struct gsm_network *ipaccess_gsmnet; static int bts_model_nanobts_start(struct gsm_network *net) { diff --git a/openbsc/src/libbsc/bts_sysmobts.c b/openbsc/src/libbsc/bts_sysmobts.c index 9479206..0f0b6eb 100644 --- a/openbsc/src/libbsc/bts_sysmobts.c +++ b/openbsc/src/libbsc/bts_sysmobts.c @@ -45,6 +45,8 @@ extern struct gsm_bts_model bts_model_nanobts; static struct gsm_bts_model model_sysmobts; +extern struct gsm_network *ipaccess_gsmnet; + static int bts_model_sysmobts_start(struct gsm_network *net) { model_sysmobts.features.data = &model_sysmobts._features_data[0]; @@ -56,6 +58,8 @@ static int bts_model_sysmobts_start(struct gsm_network *net) osmo_signal_register_handler(SS_NM, bts_ipa_nm_sig_cb, NULL); + ipaccess_gsmnet = net; + return 0; } diff --git a/openbsc/src/libmsc/gsm_04_08.c b/openbsc/src/libmsc/gsm_04_08.c index e560653..30be610 100644 --- a/openbsc/src/libmsc/gsm_04_08.c +++ b/openbsc/src/libmsc/gsm_04_08.c @@ -1774,6 +1774,7 @@ int tch_frame_down(struct gsm_network *net, uint32_t callref, struct gsm_data_fr } bts = trans->conn->lchan->ts->trx->bts; switch (bts->type) { + case GSM_BTS_TYPE_OSMO_SYSMO: case GSM_BTS_TYPE_NANOBTS: if (!trans->conn->lchan->abis_ip.rtp_socket) { DEBUGP(DMNCC, "TCH frame to lchan without RTP connection\n"); -- 1.7.9.5

3 2

Latest OpenBSC repo regression
by ty 22 Apr '13

22 Apr '13

Hi folks I pulled the latest repo of OpenBsc but upon compilation, it breaks while running 'make' Everything else compiled fine, libosmocore and libosmo-abis. I'm running this on Ubuntu 12.04 LTS. Here is the make error. make[3]: Entering directory `/home/tyrus/openbsc/openbsc/src/libcommon' CC common_vty.o In file included from common_vty.c:30:0: ../../include/openbsc/bsc_nat.h:35:37: fatal error: osmocom/sccp/sccp_types.h: No such file or directory compilation terminated. make[3]: *** [common_vty.o] Error 1 make[3]: Leaving directory `/home/tyrus/openbsc/openbsc/src/libcommon' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/tyrus/openbsc/openbsc/src' make[1]: *** [all-recursive] Error 1 After fiddling around I couldnt find the sccp dir with its contents so when i checked the git diff I found it was in this tree http://git.zerfleddert.de/cgi-bin/gitweb.cgi/bs11/commitdiff/e9359db5803bae… However when i manually created the files and dirs, it was just a nightmare. Anyone with pointers how to fix this, ill really appreciate -tyrus

2 2

[ANNOUNCE] UmTRX sales start on the Hardware Freedom Day
by Alexander Chemeris 20 Apr '13

20 Apr '13

Dear all, (I'm sorry for cross-posting to several mailing lists, but it really belongs to all of them. Please respond only to a mailing list you're subscribed to.) UmTRX sales start =============== It's the Hardware Freedom Day and we're starting sales of UmTRX to celebrate it! Now you could order it directly from Fairwaves web-shop [1], UmTRX is a completely open-source hardware SDR transceiver designed for professional/industrial applications. We designed it for use with OpenBTS software [2], but it also works well with OsmoBTS/OpenBSC [3]. UmTRX uses a UHD [4] with only minor changes to interact with a host and thus works well with GnuRadio and other applications based on UHD. 1. http://shop.fairwaves.ru/ 2. https://code.google.com/p/umtrx/wiki/RunningOpenBTS 3. http://openbsc.osmocom.org/trac/wiki/OsmoBTS 4. https://github.com/fairwaves/UHD-Fairwaves Technical details ============== UmTRX is an SDR transceiver inspired by USRP N series. If you worked with USRP N you will find it familiar, but there are significant differences which are described below as well. * Single board with an integrated RF part. * Optimized for industrial use and high MTBF. * 1GbE Ethernet connectivity to a computer. * Two full-duplex RF channels (side "A" and "B" in UHD). * Single chip transceivers LMS6002D are used for AD/DA and RF processing (300MHz to 3.8GHz) * Stable reference clocks: - 26MHz TCXO (integer multiple of GSM sample rate) with 100ppb frequency stability. - DAC for TCXO frequency fine tuning. - Integrated GPS module for automatic TCXO frequency stabilization. - External clock source is possible. * Thermal sensors for temperature based calibration. * 100mW @ 900MHz, 50mW @ 1800MHz RF output power. * 8-28V DC input power supply. * Spartan 6 LX75 FPGA. PS Big thank you to Lime Microsystems for their excellent support of open-source users! Check out their chips if you're planning to develop and SDR system. GSM specific info ============== UmTRX was designed to be easy to use to use with OpenBTS and OsmoBTS. So far it's the easiest way to get them up and running in your lab. * Quad-band support without any changes * 100-200m coverage (with an external duplexer and a small omni antenna). * >2km coverage with an external 2W GSM repeater and a patch antenna * Two independent TRXs (*). * Single-ARFCN and Multi-ARFCN support. (*) OpenBTS doesn't support the second channel on UmTRX yet. We're working to implement this and plan to release this soon. I also want to say thank you to our beta testers who received earlier versions of UmTRX. Some of them even blogged about their experience :) http://blog.shimaore.net/2013/03/umtrx.html http://genesysguru.com/blog/blog/2013/03/23/umtrx-is-alive-again/ UmTRX package contents ======================== * UmTRXv2.1, flashed and ready to use. * Power supply, 12V/30W - http://www.phihong.com/assets/pdf/PSAC30U.pdf * U.FL-to-SMA-F pigtail cables. * Two small GSM antennas - one for Tx and one for Rx. * An active GPS antenna. * Thermal pads. Note 1: The power supply comes without a 220V power cord. Make sure to prepare one before you receive the UmTRX to be able to power it on immediately. ;) Note 2: You'll need a heatsink or a fan to prevent UmTRX from overheating during long continuous operation. We provide thermal pads, but you have to find a heatsink by yourself. HDD heatsinks are good options, because UmTRX has almost the same size as an HDD. -- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru

1 0

(no subject)
by ty 19 Apr '13

19 Apr '13

1 0

[PATCH] osmo-bts: fix linking order in Makefile.am
by Nicolas J. Bouliane 18 Apr '13

18 Apr '13

On some system (e.g. ubuntu) libosmovty must precede libosmocore otherwise we get undefined reference errors while linking. Signed-off-by: Nicolas J. Bouliane <nicolas.bouliane(a)nutaq.com> --- src/osmo-bts-sysmo/Makefile.am | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/osmo-bts-sysmo/Makefile.am b/src/osmo-bts-sysmo/Makefile.am index 80a23d3..1064acf 100644 --- a/src/osmo-bts-sysmo/Makefile.am +++ b/src/osmo-bts-sysmo/Makefile.am @@ -1,6 +1,6 @@ INCLUDES = $(all_includes) -I$(top_srcdir)/include -I$(OPENBSC_INCDIR) AM_CFLAGS = -Wall $(LIBOSMOCORE_CFLAGS) $(LIBOSMOGSM_CFLAGS) $(LIBOSMOVTY_CFLAGS) $(LIBOSMOTRAU_CFLAGS) -LDADD = $(LIBOSMOCORE_LIBS) $(LIBOSMOGSM_LIBS) $(LIBOSMOVTY_LIBS) $(LIBOSMOTRAU_LIBS) -lortp +LDADD = $(LIBOSMOVTY_LIBS) $(LIBOSMOCORE_LIBS) $(LIBOSMOGSM_LIBS) $(LIBOSMOTRAU_LIBS) -lortp EXTRA_DIST = misc/sysmobts_mgr.h misc/sysmobts_misc.h misc/sysmobts_par.h \ misc/sysmobts_eeprom.h femtobts.h hw_misc.h l1_fwd.h l1_if.h \ -- 1.7.10.4

1 0