April 2017 - OpenBSC - lists.osmocom.org

by root＠雪碧

Hello, I want to configure the nano3G Access Points through 8089 port ( nano3G AP’s configuration web page )，but i don't konw the username and password . what should i do? http://www.ipaccess.com/uploads/wysiwyg_editor/files/2017/S8_S16-Datasheet-… Best regards.

6 years, 11 months

5
6
0 0

autoreconf: "header not found" in generated source

by Vadim Yanitskiy

Hi all, I am currently working on https://gerrit.osmocom.org/#/c/2075/ The problem is that the conv.h should be shared between several source code files, and it works fine for all of them, excepting the gsm0503_test_vectors.c, which will be generated automatically by the utils/conv_gen.py in the next commit. The header is currently included this way: #include "conv.h" And building in separate directory fails: CC conv/gsm0503_test_vectors.o conv/gsm0503_test_vectors.c:25:18: fatal error: conv.h: No such file or directory #include "conv.h" ^ compilation terminated. This is why I tried to move this header to the global include directory. According to received feedback from Harald and Sylvain, this approach isn't good and I need to find another one. Any suggestions how to make the conv/gsm0503_test_vectors.c able "to see" the conv.h header? With best regards, Vadim Yanitskiy.

6 years, 11 months

4
8
0 0

osmo-bts-trx error / osmo-trx illegal instruction (core dumped)

by Ron

Hi All, Upon running "osmo-bts-trx -c osmo-bts.cfg” while "osmo-nitb -C -c openbsc.conf -T -P -m” and “osmo-trx” are running, the following error shows and also shuts down “osmo-trx” osmo-bts-trx error: root@entropy:~/osmocom_files# osmo-bts-trx -c osmo-bts.cfg ((*)) | / \ OsmoBTS <0017> control_if.c:725 CTRL at 127.0.0.1 4238 <0010> telnet_interface.c:95 telnet at 127.0.0.1 4241 <0012> input/ipaccess.c:885 enabling ipaccess BTS mode, OML connecting to 192.168.1.129:3002 <000b> trx_if.c:584 Open transceiver for phy0.0 <0012> input/ipa.c:129 connection done. <0012> input/ipaccess.c:706 received ID get <0001> oml.c:475 Ignoring T200[0] (150 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:475 Ignoring T200[1] (180 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:475 Ignoring T200[2] (180 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:475 Ignoring T200[3] (1680 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:475 Ignoring T200[4] (520 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:475 Ignoring T200[5] (165 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:475 Ignoring T200[6] (1680 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:844 ADM state already was Unlocked <0012> input/ipa.c:129 connection done. <0012> input/ipaccess.c:706 received ID get <0009> pcu_sock.c:651 PCU socket not connected, dropping message <0009> pcu_sock.c:651 PCU socket not connected, dropping message <0009> pcu_sock.c:651 PCU socket not connected, dropping message <0009> pcu_sock.c:651 PCU socket not connected, dropping message <0009> pcu_sock.c:651 PCU socket not connected, dropping message <0009> pcu_sock.c:651 PCU socket not connected, dropping message <0009> pcu_sock.c:651 PCU socket not connected, dropping message <0009> pcu_sock.c:651 PCU socket not connected, dropping message <0009> pcu_sock.c:651 PCU socket not connected, dropping message <0009> pcu_sock.c:651 PCU socket not connected, dropping message <0009> pcu_sock.c:651 PCU socket not connected, dropping message <0009> pcu_sock.c:651 PCU socket not connected, dropping message <000b> trx_if.c:187 No response from transceiver for phy0.0 <0009> pcu_sock.c:848 PCU socket connected to external PCU <0001> oml.c:72 Reporting FAILURE to BSC: 0.3.20170425 <0000> rsl.c:624 (bts=0,trx=0,ts=4,ss=0) not sending CHAN ACT ACK <0000> rsl.c:624 (bts=0,trx=0,ts=5,ss=0) not sending CHAN ACT ACK <0000> rsl.c:624 (bts=0,trx=0,ts=6,ss=0) not sending CHAN ACT ACK <0000> rsl.c:624 (bts=0,trx=0,ts=7,ss=0) not sending CHAN ACT ACK <000b> trx_if.c:187 No response from transceiver for phy0.0 <000b> trx_if.c:187 No response from transceiver for phy0.0 <000b> trx_if.c:187 No response from transceiver for phy0.0 <000b> trx_if.c:187 No response from transceiver for phy0.0 <000b> trx_if.c:187 No response from transceiver for phy0.0 <000b> trx_if.c:187 No response from transceiver for phy0.0 <000b> trx_if.c:187 No response from transceiver for phy0.0 <000b> trx_if.c:187 No response from transceiver for phy0.0 <0007> l1sap.c:413 Invalid condition detected: Frame difference is > 1! <0001> bts.c:208 Shutting down BTS 0, Reason No clock from osmo-trx <000b> trx_if.c:203 CTRL NOHANDOVER ignored: No clock from transceiver, please fix! <000b> trx_if.c:203 CTRL NOHANDOVER ignored: No clock from transceiver, please fix! <0000> rsl.c:528 (bts=0,trx=0,ts=4,ss=0) not sending REL ACK <000b> trx_if.c:203 CTRL NOHANDOVER ignored: No clock from transceiver, please fix! <000b> trx_if.c:203 CTRL NOHANDOVER ignored: No clock from transceiver, please fix! <0000> rsl.c:528 (bts=0,trx=0,ts=5,ss=0) not sending REL ACK <000b> trx_if.c:203 CTRL NOHANDOVER ignored: No clock from transceiver, please fix! <000b> trx_if.c:203 CTRL NOHANDOVER ignored: No clock from transceiver, please fix! <0000> rsl.c:528 (bts=0,trx=0,ts=6,ss=0) not sending REL ACK <000b> trx_if.c:203 CTRL NOHANDOVER ignored: No clock from transceiver, please fix! <000b> trx_if.c:203 CTRL NOHANDOVER ignored: No clock from transceiver, please fix! <0000> rsl.c:528 (bts=0,trx=0,ts=7,ss=0) not sending REL ACK Shutdown timer expired osmo-trx logs: NOTICE 139966735525632 16:51:01.4 Transceiver.cpp:794:driveControl: Changing TSC from 0 to 7 NOTICE 139966735525632 16:51:01.4 Transceiver.cpp:243:start: Starting the transceiver Illegal instruction (core dumped) osmo-nitb logs: Thu Apr 27 16:50:43 2017 <001e> input/ipa.c:263 accept()ed new link from 192.168.1.129 to port 3002 Thu Apr 27 16:50:43 2017 <001e> input/ipa.c:263 accept()ed new link from 192.168.1.129 to port 3003 Thu Apr 27 16:50:43 2017 <0004> bsc_init.c:288 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 885 using MCC=1 MNC=1 LAC=1 CID=1 BSIC=63 BTS 0 reported connected PCU version 0.3.20170425 Thu Apr 27 16:51:06 2017 <001e> input/ipaccess.c:241 Sign link vanished, dead socket Thu Apr 27 16:51:06 2017 <001e> input/ipaccess.c:69 Forcing socket shutdown with no signal link set Thu Apr 27 16:51:06 2017 <0020> bsc_init.c:341 Lost some E1 TEI link: 1 0x7f5f48820070 Thu Apr 27 16:51:06 2017 <0020> bsc_init.c:341 Lost some E1 TEI link: 2 0x7f5f48820070 ^Csignal 2 received Also attached the configuration files used. What seems causes the issue? OS: Ubuntu 16.04 SDR: B210 Best Regards, Ron Rylan B. Menez Operations Manager +63 998 989 7973 +63 2 893 1781 [cid:bbb8aa9b-ea08-431b-bb55-8cc77a18e169@apcprd06.prod.outlook.com] Singapore * Philippines Products: Gridloc*Intelle*Hype*Lighthouse*Telco Services*Software Development This email (including any attachment to it) is confidential and intended only for the use of the individual named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message (including any attachment to it). Thank you.

6 years, 11 months

5
13
0 0

nano3G <-> sip-connector <-> asterisk?

by Andreas Mueller

Hello, is it possible to connect the openbsc from the vlr_3G Branch with sip-connector to asterisk as described on https://osmocom.org/projects/osmo-sip-conector/wiki/Osmo-sip-connector, or are there changes in the vlr_3G Branch that makes this impossible? When trying to set this up I was able to call an UMTS-Phone which was connected to the nano3G from a softphone using jitsi, and the UMTS-Phone was ringing, but it was not possible to answer the call. I have only limited experiences with asterisk and so I am for example unsure about what voice-codecs to use, if my asterisk-config is correct,... and so I would like to know if it should work in principle and I have to find the correct configuration. have a nice weekend, Andreas

6 years, 11 months

2
1
0 0

Using repo to make 'regular' releases

by Holger Freyther

Hi, for the topic of making "releases" I wondered if we want to explore using "repo" to tie the different Osmocom repositories into a single "release". Below is an example "default.xml" that would make up a release. The default.xml would be maintained in a git repository that we could tag, e.g. something like v201704.1 (vYYYYMM.MINOR). I could envision we have: * A simple build shell script to build/install everything * A script to update (and tag) the default.xml to make new releases available. How to use it (if repo is installed): repo init -u git://git.osmocom.org/osmocom-cellular-manifest repo sync ./build_all.sh --prefix=/opt/cellular aand on a new release repo sync ./build_all.sh ... ideas? comments? holger default.xml: <?xml version="1.0" encoding="UTF-8"?> <manifest> <remote fetch="git://git.osmocom.org" review="gerrit.osmocom.org" name="osmocom"/> <default revision="refs/heads/master" remote="osmocom"/>  <project name="libosmocore" revision="9e83c3d5ca64428befe74e5aad61bd84bccaf309"/> <project name="libosmo-abis" revision="bf7976c0b0076410ad1bd67061dd18d0f33a7f43"/> <project name="libosmo-netif" revision="c108c9db969c4d4abaccc88419b4ac0c44957365"/> <project name="libsmpp34" revision="cc0bcd6bc051d5ccaf32cdbbc28f073369900857"/> <project name="libosmo-sccp" revision="57d0449d4ed5d82050c52551c8ad6195db38fdf1"/>  <project name="osmo-trx" revision="de116e90c03c534fa4b51ef40dfd2bb9e843c86e"/> <project name="osmo-bts" revision="25742a5929edecc545a4fc254f678cc834f8c3b3"/> <project name="osmo-pcu" revision="e6d26ec09c2bcd2126416a58cb23af27318ec67e"/> <project name="osmo-iuh" revision="46fea15afc38fb995baf4100f4de1d6a3565899f"/> <project name="openggsn" revision="19e19e3609508d121ba46c165e5ed1502a3cf9da"/> <project name="openbsc" revision="d75f11e6f26a50c11f73625de5c0833971900cde"/> <project name="osmo-sip-connector" revision="417f2542163edfe8ac8729918e2452dc7787a3d7"/>  <project name="osmo-hlr" revision="743cf42ac5dfa2661317e73f70b204bde7450ff2"/>  <project name="osmo-gsm-manuals" revision="4b593a2259a107211489940b8b59f44219e73b2d"/>  <project name="osmo-ci" revision="e72f35cfa9969e52d0018ba4661f4519519c39ba"> <linkfile src="build/build.sh" dest="build.sh"/> </project> <project name="python/osmo-python-tests" path="osmo-python-tests" revision="baa6f12260c383f40a477b71743b16940c50e5aa"/> </manifest>

6 years, 11 months

6
14
0 0

Accelerate3g5 femto-cell configuration

by Nikolya

Hello It may not be an appropriate mail-list to ask questions about OsmoBTS inside femto-cell of Accelerate3g5 "promo", but i need some directions. I undestand that i need to build OpenBSC (OpenNITM), so that femto-cell start "working" . But i can't find any documentation regarding how to configure OsmoBTS inside femto-cell . I knew root account password for the cell, but didn't find passwords resting in [root@ip302ff:~#]cat /var/www/.htpasswd nano-admin:SO0umwXJnpBjo femto-admin:gRWqmPZknka4g developer:.QIQ0JPRQ3PKA [root@ip302ff:~#] so i just move this file aside and access http://cell-ip:8089/ cgi-bin/connection_config.cgi . It giving this HTML <pre> $ curl http://cell-ip:8089/cgi-bin/connection_config.cgi <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" " http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title>ip.access 3G AP Web-if</title> <link href="/styles.css" rel="stylesheet" type="text/css"> </head> <NOSCRIPT> <meta http-equiv=REFRESH content=0;URL="/no_javascript.html"> </NOSCRIPT> <body onLoad="myOnLoad()"> <div id="header"> <img src="/top_banner.png" usemap="#logomap" border="0" align="middle" vspace="0"> <MAP name="logomap" border="0"> <AREA href="http://www.ipaccess.com" shape="rect" coords="0,0,160,65"/> </MAP> </div> <div id="container"> <div id="title"><h2>3G AP</h2></div> <div id="leftcol"> <ul id="nav" class="nav">  </ul> </div> <div id="content"> <b>Serial Number: </b></p> <b>Sorry - couldn't find '/cgi-bin/connection_config.cgi' page here.</b><br> Server name: ip302ff<br>PathTranslated: <br>PathInfo: <br> </div> <div id="footer"> <p/> <hr/> <h3>Copyright © 2010 <a href="http://www.ipaccess.com">ip.access ltd</a></h3> </div> </div> </body> </html> $ </pre> one of the URLs that work is http://cell-ip:8089/cgi-bin/swversion.cgi , which giving <pre> Serial Number: Firmware Version Information Flash Contents Kernel Bank 1: xc-220.3.0 Kernel Bank 2: xc-225.2.0 Filesystem Bank 1: EMPTY Filesystem Bank 2: 579.26.7 Default Filesystem: ## Error: "rootdev" not defined sh: 5: unknown operand sh: 6: unknown operand Default OS: ## Error: "kernel_flash_addr" not defined sh: 0x20080000: unknown operand sh: 0x20280000: unknown operand Booted version: Bootloader version: OS version: xc-225.2.0 #1 PREEMPT Thu Jul 11 17:54:07 BST 2013 Filesystem version: 579.26.7 Detailed List: etc </pre> There are open TCP ports on femto-cell ip 22,8089,8090,10002 . One of them 8090, when telnet to it, it providing some "vty" <pre> dmi> help SYNTAX : help [cmd]|[attribute_id_list] where cmd is one of quit q call wait get set action alarm getobj restore regatt deregatt regact deregact dmidata endscript exitscript history buildco print help dmi> </pre> But it doesn't look like VTY that documented in http://ftp.osmocom.org/docs/latest/osmobts-usermanual.pdf I may need to build linux for femto-cell by myself, but need some help of how to build and write builded image to femto-cell --- WBR Nikolay

6 years, 11 months

2
1
0 0

osmo-stp / nightly builds

by Neels Hofmeyr

Just asked holger: the osmo-stp build from cellmgr in the nightly debian packages can be switched off. Since you've been fixing debian these days, could you do that one as well? Hopefully we will have no more failures then. (...except on the new ubuntu 17.04 of course, no idea what's up with that. Not sure who added it and who will resolve those, or whether that's already done?) Thanks! ~N

6 years, 12 months

3
3
0 0

ip.access nano3G Help

by Junaid Saeed Uppal

Hi, I am trying to setup the 3G Project and have bought a used nano3G BTS (S8 - Model 237A) . The problem i am facing is that the telnet port is not open. I have tried to reset the device using the pin-hole reset button as per documentation but it still doesn't open up the ports and still tries to lookup operator's NTP and tries to establish a IPSEC tunnel. Any pointers on how i can reset this so that I can get it to work with the project? Thanks,

6 years, 12 months

2
1
0 0

nano3G S8 Help

by Junaid Saeed Uppal

##Resending again as the previous message didn't make it to the list. Hi, I am trying to setup the 3G Project and have bought a used nano3G BTS (S8 - Model 237A) . The problem i am facing is that the telnet port is not open. I have tried to reset the device using the pin-hole reset button as per documentation but it still doesn't reset or open up the ports and still tries to lookup operator's NTP and tries to establish a IPSEC tunnel. Any pointers on how i can reset this so that I can get it to work with the project? Thanks,

6 years, 12 months

1
0
0 0

Thoughts on a next generation MIB/VTY replacement

by Harald Welte

Hi All, Using zebra/quagga VTY code was a great idea back then and has served us nicely in all those years. I like the general style of the command-line based interface with its various nodes, the strict syntax checking, the tab completion and the interactive context-sensivive help. However, it feels a bit 20ieth-century-ish to have to manually write code to parse and to save the respective values. This is not a productive way to spend our development resources, and it is error prone. The "save" can be forgotten, resulting in non-saveable config parameters. The save can store values that the "parse" function will not be able to read again, etc. Furthermore, the VTY is inherently a human user interface, not intended for programmatic consumption. For programmatic access, we have developed the control interface. In reality though, only 1% of the parameters available in the VTY are exported via the control interface. And rather than adding all the missing bits and pieces with hand-crafted code to the control interface, we should have a generic way to define a new configuration value, and that value should then be automatically parse- and storable via VTY as well as a programmatic interface. The next "problem' is that the current telnet connections live within the process of the application. This means that a user can effectively "stall" the main application by performing I/O intensive operation on the VTY, or even on as many VTY/telnet sessions as he wants. There shouldn't be any need for this, at least not for something as mundane as performing configuration changes. Of course the VTY has different use cases such as runtime introspection of system state as well as logging. But still. Yet another concern is "VTY and telnet port proliferation". Particularly with the conversion from NITB to BSC+MSC+HLR, we are yet again getting more network elements with their own telnet ports. Remembering the port numbers is clumsy. It would be more convenient if a single command line interface could provide access to the configuration and the state of multiple different processes / network elements. Last, but not least, the current implementation is fixed to telnet, without any form of authentication, and without a path to migrate e.g. to something like SSL or SSH. I don't think it is a major concern (you can always SSH to the system and then telnet locally). So what I had in mind for quite some time (actually since netconf 1.2 about one year ago), is to have some kind of an external "VTY/MIB daemon" (or even separate daemons for each) which maintains a hierarchical database of configuration values. The MIB deamon simply offers an API (via client library) to GET or SET the individual values, or to NOTIFY an application about a changed value. This API is both used by the actual Osmocom programs to obtain their configuration (and obtain updates to it during runtime), as well as by the "VTY daemon" providing interactive shell access to it. Finally, other external applications could use the same interface/client library to do the same. A proxy to SNMP or REST interfaces can be imagined, for even more interfacing with the outside world. What I don't like about many existing MIBs I've used (as a sysadmin/user, not a developer) is their simple type system. You can often specify any random value to such a MIB, even one that is completely useless. A simple INT or STRING type is not sufficient, we really want the ability to have ENUM types, to have integers with ranges, etc. - just like we have in the VTY. Also, the MIBs I've used typically are nothing more than a hierarchical key-value store. They do not contain the information required for interactive, context-sensitive help needed for the "VTY" feel :( This is btw also the problem I have with OpenWRT's uci: It just has keys and values, with no way to constrain those values to something that's reasonable to the given program/context that is being configured, and there's no help or other information associated with those keys and values. So what I would like to see in this context, is some way to have a machine-parseable description of a "MIB/config item", together with syntax, ranges, enum values, help texts, etc (ideally in the C source code, possibly in comments?) which is used by some kind of MIB compiler to build up the hierarchical structure of the MIB and all of its keys as well as their permitted values and syntax reference. This information is then available to the VTY/telnet connections, irrespective of whether a given application [using those values] is running at all. Once an application starts, it can query for the configuration values it is interested in and populate its internal data structures from it. Ideally, one would even be able to generate a 'struct' from the MIB compiler, so that there is no need to explicitly call a "get" function on each single configuration value, but one simply gets a C-language 'struct' with all the values filled in by the client library. As stated above, there should be some way how he MIB can notify applications about changes to certain nodes in the MIB tree, so the application[s] can react to that. I don't have a clear picture yet how transaction logic (like changing multiple values and then committing them at once) would work, or whether applications should even be able to reject/revert a modification? In either case, I just wanted to share my thoughts on this. I know it sounds rather complex, but I think the investment in some kind of unified configuration database system would save us of a lot of boilerplate code and subtle bugs and inconsistencies. I've created https://osmocom.org/issues/1975 with above text to keep track of it, but I think at this point it's more of a mailing list discussion rather than something we can put into an issue. I guess the progress would rather be * first discuss it here and/or at OsmoDevCon * create something like a specification in the wiki * then follow-up with actual tickets on the work items All of this is brainstorming and vaporware, but I can't help to think of better ways of doing this. If somebody has experience with any existing systems and wants to share if and how they might fit, or what other ideas are useful to borrow: Please share! 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)

6 years, 12 months

6
8
0 0

openbsc 3G supoort with octasic phy

by Snehasish Kar

Hi I just wanted to know has anyone tried to use openbsc 3G with octasic 3G phy. BR Snehasish

6 years, 12 months

3
4
0 0

gerrit trouble "Change is New"

by Harald Welte

I want to merge the patchset from my libosmo-sccp sigtran branch to master, but gerrit doesn't allow me to. I've re-pushed the patch set already multiple times, the last time also doing a minor cosmetic change to the commit log message of the first patch in the series (https://gerrit.osmocom.org/#/c/2191/). gerrit refuses to merge even that very first patch in the series with "change is new". What should I do to get this merged? -- - 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)

6 years, 12 months

4
7
0 0

Video Recordings of OsmoCon 2017

by Harald Welte

Hi all, the Osmocom Conference 2017 last week was an overwhelming success. We received lots of positive feedback from all sides. Thanks to all the speakers, to the attendees as well as to the anonymous sponsor of the travel grant funds. It is my great pleasure that due to the great support by C3VOC (The CCC Video Operation Center), we have full recordings of all talks given at OsmoCon 2017. You can find the videos on the C3VOC site at https://media.ccc.de/search/?q=osmocon They are also linked individually from the OsmoCon 2017 homepage at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2017 I hope the video recordings will be of help for everyone who could not make it to the event in person. We will also be collecting the slides and put them up on the wiki during the next few days. Please don't hesitate to raise any feedback and/or questions. Technical feedback/questions regarding Osmocom software / projects should be addressed to the appropriate mailing lists, such as openbsc(a)lists.osmocom.org. Feedback to the organizers should be sent to osmocon2017(a)sysmocom.de. Looking forward to the next OsmoCon, which we'll expect to be spanning ore than just a single day. 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)

6 years, 12 months

1
0
0 0

osmocom-bb moved to gerrit

by Neels Hofmeyr

The osmocom-bb git repository has now moved to gerrit. For patch submission to osmocom-bb, see https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit ~N

7 years

1
0
0 0

FSM for lchan release handling -- release indication after SACCH deactivation timeout

by Holger Freyther

Good Evening, this is a bit of speculation but Keith showed me a trace with some network delay that makes a case for using FSM for the lchan itself. It seems the following can happen: * LU REJECT * Start Channel Release ** Send RR Release to the MS ** Deactivate SACCH ** Start Timer ... network transmission issues... at least 5s * SACCH deactivate timeout ** Start error release procedure.. ... * LATE RELEASE INDICATION arrives triggering other release procedure? So with a proper FSM we would have transitioned into the error path and would just ignore the RELEASE INDICATION. The question is if someone has budget to do a FSM transition here? I will try to build a simulated testcase for that. The other part that seems to happen (and I don't understand yet): * Allocating a lchan before it is fully freed?! * The BTS sending us RF Channel Releasse ACK twice cheers holger

7 years

1
0
0 0

Control interface introspection of FSMs

by Harald Welte

Good News, everyone [tm] Some may have already played with it: The osmo_fsm's already have gained a VTY interface (see http://git.osmocom.org/libosmocore/tree/src/vty/fsm_vty.c) some time ago, which is nice for manual debugging and the like. However, for automatic testing one would normally want to do something like the following: 1) send a packet to the implementation under test (IUT) 2) then check if a given FSM has been created, a state has changed, a timer is running, etc. 3) go to '1' for the next packet, or wait for a timeout and then re-check, ... I've just introduced a generic CTRL interface for programmatic access to osmo_fsm. See https://gerrit.osmocom.org/#/c/2377 for details. The general idea is that you can send a CTRL command like GET 1 fsm.FSM_NAME.id.INSTANCE_ID.state GET 1 fsm.FSM_NAME.id.INSTANCE_ID.timer GET 1 fsm.FSM_NAME.id.INSTANCE_ID.parent-name GET 1 fsm.FSM_NAME.id.INSTANCE_ID.dump Where FSM_NAME is the name of the osmo_fsm (class) and INSTANCE_ID is the identity of the instance (e.g. the IMSI of a subscriber in the VLR code). So in OsmoMSC, something like GET 1 fsm.vlr_lu_fsm.id.901700123456789.state would return the string name of the state for the location update FSM of the given IMSI, e.g. "VLR_ULA_S_WAIT_LU_COMPL_STANDALONE" I presume Neels will like this. Could be used from osmo-gsm-tester to not just do "black box testing" from MS to MS or MS to MNCC, but to actually verify individual states/transitions on all osmo_fsm enabled elements. It's of course questionable if an end-to-end test should care, but I can think of all kinds of other testing (particularly of my new SIGTRAN work) where it is absolutely useful. Once the above-mentioned patches are merged, applications with a control inteface will have this functionality enabled automatically. I think this makes osmo_fsm even more useful. I can imagine use cases not only related to testing, but also use cases of e.g. user interfaces or visualization. Regards, Harald p.s.: In German we say "self praise stinks", but I really think osmo_fsm is one of the best things happening to the Osmocom cellular projects in recent years. Now we just need to convert more code to use it. -- - 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)

7 years

2
1
0 0

OpenBSC

by Bizhan Changizi

Dear Sipos Csaba Hi firstly my english languages is not good, and excuse me. i find Your contact info from blow link. http://lists.osmocom.org/pipermail/openbsc/2015-September/000413.html dear Sips i need to help to run OsmoNITB <https://osmocom.org/projects/osmonitb/wiki> but i have a problem when compile the source. but i can’t resolve it, can you help me to to run OpenBSC plz, tnx. Problem : CC abis_om2000_vty.o CC abis_rsl.o CC bsc_rll.o CC paging.o CC bts_ericsson_rbs2000.o CC bts_ipaccess_nanobts.o In file included from bts_ipaccess_nanobts.c:39:0: /usr/local/include/osmocom/abis/ipaccess.h:7:8: error: redefinition of ‘struct ipaccess_unit’ struct ipaccess_unit { ^ In file included from bts_ipaccess_nanobts.c:38:0: /usr/local/include/osmocom/gsm/ipa.h:11:8: note: originally defined here struct ipaccess_unit { ^ make[3]: *** [bts_ipaccess_nanobts.o] Error 1 make[3]: Leaving directory `/home/telecom/osmo/src/osmonitb/openbsc/openbsc/src/libbsc' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/telecom/osmo/src/osmonitb/openbsc/openbsc/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/telecom/osmo/src/osmonitb/openbsc/openbsc' make: *** [all] Error 2 telecom@OpenBCS:~/osmo/src/osmonitb$ best regurds

7 years

2
1
0 0

UMTS-Stick on nano3G?

by Andreas Mueller

Hello, I tried to use a Huawei E1823 UMTS-Stick on a debian8-laptop with wvdial and pppd to connect to a nano3G for getting an IP/Internet-connection via UMTS/HSDPA. The setup is mainly as described on http://osmocom.org/projects/cellular-infrastructure/wiki/Getting_Started_wi…. When using an android-Smartphone with the same configuration of the ggsn and the other components the IP/Internet-connection is working. After pppd is started from wvdial it receives his local IP-address from the "net 192.168.99.0/24" parameter of ggsn.conf and also the configured DNS-Server, but no remote-IP, so 10.64.64.64 is used by pppd as a default value: ... --> local IP address 192.168.99.5 --> pppd: ï¿½[7f] --> remote IP address 10.64.64.64 --> pppd: ï¿½[7f] --> primary DNS address 8.8.8.8 --> pppd: ï¿½[7f] ..which results in an unusable ppp0-device: ppp0 Link encap:Point-to-Point Protocol inet addr:192.168.99.5 P-t-P:10.64.64.64 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 Has anybody successfully used an UMTS-Stick with ggsn? How can I tell ggsn to send his IP-Adress, which can be used by pppd as "remote IP address"? Are there special options for pppd which I have to use? thanks and greetings, Andreas

7 years

4
7
0 0

OpenBSC TCH/H

by robert

Hello, I have set all the traffic channels to TCH/H and started the BTS but I was not able to perform a call. Is there something else that should be done ? Best regards,

7 years

2
1
0 0

Control Interface related testing

by Harald Welte

Dear all, I have just submitted some patches which allow test cases to use the Control Interface internally, without binding to a TCP port. See https://gerrit.osmocom.org/#/c/2375/ and https://gerrit.osmocom.org/#/c/2376/ Using this, one can now write unit tests for control commands, without having to go for a multi-process setup with an external control client connected to the control TCP port (which is not easily possible in CI as the port might be used by another test case, ...) -- - 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)

7 years

1
0
0 0

Running osmo-trx and osmo-bts-trx Shows Errors

by Ron

Hi, We just finished installing the following osmo elements using Ubuntu 14.04 and the procedures from this link: https://osmocom.org/projects/cellular-infrastructure/wiki/Ettus_USRP_B2xx_f… https://osmocom.org/projects/cellular-infrastructure/wiki/Build_from_source * libosmocore * libosmo-abis * libosmo-netif * openggsn * libosmo-sccp * openbsc * osmo-pcu * osmo-trx * osmo-bts We are now trying to run each applications to test osmo. All applications were run smoothly except for osmo-trx and osmo-bts-trx. We also installed the UHD driver of Ettus B2xx series using both “apt-get install” process and binary process as well using this link: https://files.ettus.com/manual/page_install.html https://files.ettus.com/manual/page_build_guide.html But still, the same errors were received. Errors received: # osmo-trx [INFO] [UHD] linux; GNU C++ version 4.8.4; Boost_105400; UHD_3.11.0.git-128-g379f922d opening configuration table from path :memory: Config Settings Log Level............... NOTICE Device args............. TRX Base Port........... 5700 TRX Address............. 127.0.0.1 Channels................ 1 Tx Samples-per-Symbol... 4 Rx Samples-per-Symbol... 1 EDGE support............ Disabled Reference............... Internal C0 Filler Table......... Disabled Multi-Carrier........... Disabled Diversity............... Disabled Tuning offset........... 0 RSSI to dBm offset...... 0 Swap channels........... 0 osmo-trx: symbol lookup error: osmo-trx: undefined symbol: _ZN3uhd6device4findERKNS_13device_addr_tE # osmo-bts-trx -c /etc/osmo-bts.cfg ((*)) | / \ OsmoBTS There is no such command. Error occurred during reading below line: fn-advance 20 Failed to parse the config file: '/etc/osmo-bts.cfg’ What seems to cause this errors? What logs do we need to check? Best Regards, Ron Rylan B. Menez Operations Manager +63 998 989 7973 +63 2 893 1781 [cid:D7861C66-51ED-4DB6-B9ED-BADEB28148EC] Singapore * Philippines Products: Gridloc*Intelle*Hype*Lighthouse*Telco Services*Software Development This email (including any attachment to it) is confidential and intended only for the use of the individual named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message (including any attachment to it). Thank you.

7 years

4
4
0 0

weekly test report (w14 2017)

by Joachim Steiger

Hi, this is the BTS test report for week14 2017. BTS models which have been tested with OsmoNITB are: - sysmoBTS1002 - octasic OCTBTS3500 - ettus USRP B200 - nanoBTS model:165G Most test cases have passed: sysmobts and nanobts worked without issue. the only one failing were with the octbts: the issues there were reliability of establishing a voicecall and or gprs. only every 2nd or 3rd attempt works. on the 3 TCH/H, 3 PDCH config gprs was not working at all with the ettus B200 everything worked but gprs seemed extremely slow or lossy. i could only view small testpages, big graphics do not load. For additional information related to test cases, timeslots configuration and voice codecs used, please visit: https://osmocom.org/projects/cellular-infrastructure/wiki/Weekly_BTS_Tests following are some git hashes/version strings of tested components: libosmo-abis: bf7976c0b0076410ad1bd67061dd18d0f33a7f43 libosmocore: ff20641d9e3bb4373f9577c3382df1480ace4e91 libosmo-netif: 5fe77a4656f3590c343861ea96bcec18e370e437 libosmo-sccp: 8e708d1f2da1b187f631bf08172a5194a85b1a23 libsmpp34: cc0bcd6bc051d5ccaf32cdbbc28f073369900857 openbsc: 2d92162a6b6720d72129bee1bcbef353b0fd0aa6 openggsn: 19e19e3609508d121ba46c165e5ed1502a3cf9da osmo-bts: e16b59357411ffa4903ac110ac4ce46d343e878d osmo-bts-octphy: e16b59357411ffa4903ac110ac4ce46d343e878d osmo-pcu: e6d26ec09c2bcd2126416a58cb23af27318ec67e osmo-trx: 6031734f448c6308d67b1ee464a13d60b33cd843 sysmobts: OsmoBTS version 0.4.0.414-e16b5 sysmobts: Osmo-PCU version 0.2.900-e6d2 octbts: (name='octsdr_gsm', desc='Software Define Radio', ver='02.07.00-B1039', ver_hdr='02.07.00-B1039') octbts: (platform='Opus2', version='OCTSYS_VERSION=01.02.19.B1;OCTODK_VERSION=01.15.01-B1;OCTADF_VERSION=04.05.01-B2637;') nanobts: Equipment_Version='165g029_79' nanobts: Software_Version='168d462_v200b202d0' if you are interested in the details, drop me a mail and i'll forward the whole report. kind regards -- - Joachim Steiger <jsteiger(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Directors: Harald Welte

7 years

1
0
0 0

[RFC] Coding Style: Longer Line Lengths?

by Harald Welte

Dear all, [Despite today being April 1st, this is not an april fool's joke] ever since the start of the Osmocom project, we have adopted pretty much 1:1 the Linux Kernel coding style. Having a uniform coding style all over the project is important for readability, and from my point of view it doesn't really matter too much which style it is, as long as it is uniform accross the projects. I'm still fine with the Linux kernel coding style for most parts, but I think we could consider allowing longer lines. 80 characters is still nice here and there, but maybe something like 100, 120 or even 130 might actually make the code more readable and permit us to use slightly longer identifiers without having to wrap every second statement in the code. What do people generally think here? 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)

7 years

10
16
0 0

DBus usage

by Neels Hofmeyr

Hi Pau (and maybe others), here is a test script that showcases how I'd like to use DBus in the osmo-gsm-tester: use pydbus and keep the glib main loop in a thread (to handle DBus signals only). It sounds ambitious but the test program actually works. Would be great to hear your opinion on it: http://git.osmocom.org/osmo-gsm-tester/tree/selftest/dbus_test/ofono_client… The same thing cosmetically rearranged as module stub: http://git.osmocom.org/osmo-gsm-tester/tree/src/osmo_gsm_tester/dbus_client… Thanks! ~N Related: OS#1980 https://osmocom.org/issues/1980 -- - Neels Hofmeyr <nhofmeyr(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschäftsführer / Managing Directors: Harald Welte

7 years

1
0
0 0

osmo-bts Installation Issue

by Ron

Hi All, Requesting your help regarding the case that we had encountered during the installation of osmo-bts using UBUNTU 14.04 as OS. Without using the 201509-fairwaves-rebase, the installation go past through. Unfortunately, there is no “osmo-bts-trx” executable. Below are the steps we followed for the installation of osmo-bts. cd /opt/osmo/src/ git clone git://git.osmocom.org/osmo-bts cd osmo-bts autoreconf -fi ./configure make -j5 make check make install We tried using the 201509-fairwaves-rebase, but unfortunately the installation stops and an error was encountered during the “make” process. Below are the installation steps and error encountered: cd /opt/osmo/src/ git clone git://git.osmocom.org/osmo-bts cd osmo-bts git checkout 201509-fairwaves-rebase autoreconf -fi ./configure --enable-trx make Error encountered: make[2]: Entering directory `/opt/osmo/src/osmo-bts/src' Making all in common make[3]: Entering directory `/opt/osmo/src/osmo-bts/src/common' CC gsm_data_shared.o CC sysinfo.o CC logging.o CC abis.o abis.c: In function ‘abis_open’: abis.c:233:25: warning: assignment discards ‘const’ qualifier from pointer target type [enabled by default] bts_dev_info.unit_name = model_name; ^ abis.c:236:25: warning: assignment discards ‘const’ qualifier from pointer target type [enabled by default] bts_dev_info.location2 = model_name; ^ CC oml.o oml.c:46:30: error: conflicting type qualifiers for ‘abis_nm_att_tlvdef_ipa’ static struct tlv_definition abis_nm_att_tlvdef_ipa = { ^ In file included from oml.c:33:0: /usr/local/include/osmocom/gsm/abis_nm.h:37:36: note: previous declaration of ‘abis_nm_att_tlvdef_ipa’ was here extern const struct tlv_definition abis_nm_att_tlvdef_ipa; ^ oml.c:373:6: error: nested redefinition of ‘enum abis_nm_t200_idx’ enum abis_nm_t200_idx { ^ oml.c:373:6: error: redeclaration of ‘enum abis_nm_t200_idx’ In file included from oml.c:32:0: /usr/local/include/osmocom/gsm/protocol/gsm_12_21.h:647:6: note: originally defined here enum abis_nm_t200_idx { ^ oml.c:374:2: error: redeclaration of enumerator ‘T200_SDCCH’ T200_SDCCH = 0, ^ In file included from oml.c:32:0: /usr/local/include/osmocom/gsm/protocol/gsm_12_21.h:648:2: note: previous definition of ‘T200_SDCCH’ was here T200_SDCCH = 0, ^ oml.c:375:2: error: redeclaration of enumerator ‘T200_FACCH_F’ T200_FACCH_F = 1, ^ In file included from oml.c:32:0: /usr/local/include/osmocom/gsm/protocol/gsm_12_21.h:649:2: note: previous definition of ‘T200_FACCH_F’ was here T200_FACCH_F = 1, ^ oml.c:376:2: error: redeclaration of enumerator ‘T200_FACCH_H’ T200_FACCH_H = 2, ^ In file included from oml.c:32:0: /usr/local/include/osmocom/gsm/protocol/gsm_12_21.h:650:2: note: previous definition of ‘T200_FACCH_H’ was here T200_FACCH_H = 2, ^ oml.c:377:2: error: redeclaration of enumerator ‘T200_SACCH_TCH_SAPI0’ T200_SACCH_TCH_SAPI0 = 3, ^ In file included from oml.c:32:0: /usr/local/include/osmocom/gsm/protocol/gsm_12_21.h:651:2: note: previous definition of ‘T200_SACCH_TCH_SAPI0’ was here T200_SACCH_TCH_SAPI0 = 3, ^ oml.c:378:2: error: redeclaration of enumerator ‘T200_SACCH_SDCCH’ T200_SACCH_SDCCH = 4, ^ In file included from oml.c:32:0: /usr/local/include/osmocom/gsm/protocol/gsm_12_21.h:652:2: note: previous definition of ‘T200_SACCH_SDCCH’ was here T200_SACCH_SDCCH = 4, ^ oml.c:379:2: error: redeclaration of enumerator ‘T200_SDCCH_SAPI3’ T200_SDCCH_SAPI3 = 5, ^ In file included from oml.c:32:0: /usr/local/include/osmocom/gsm/protocol/gsm_12_21.h:653:2: note: previous definition of ‘T200_SDCCH_SAPI3’ was here T200_SDCCH_SAPI3 = 5, ^ oml.c:380:2: error: redeclaration of enumerator ‘T200_SACCH_TCH_SAPI3’ T200_SACCH_TCH_SAPI3 = 6 ^ In file included from oml.c:32:0: /usr/local/include/osmocom/gsm/protocol/gsm_12_21.h:654:2: note: previous definition of ‘T200_SACCH_TCH_SAPI3’ was here T200_SACCH_TCH_SAPI3 = 6 ^ make[3]: *** [oml.o] Error 1 make[3]: Leaving directory `/opt/osmo/src/osmo-bts/src/common' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/opt/osmo/src/osmo-bts/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/opt/osmo/src/osmo-bts' make: *** [all] Error 2 We followed the installation process from the URLs below: https://osmocom.org/projects/cellular-infrastructure/wiki/Ettus_USRP_B2xx_f… https://osmocom.org/projects/cellular-infrastructure/wiki/Build_from_source Best Regards, Ron Rylan B. Menez Operations Manager +63 998 989 7973 +63 2 893 1781 [cid:D7861C66-51ED-4DB6-B9ED-BADEB28148EC] Singapore * Philippines Products: Gridloc*Intelle*Hype*Lighthouse*Telco Services*Software Development This email (including any attachment to it) is confidential and intended only for the use of the individual named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message (including any attachment to it). Thank you.

7 years

2
2
0 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC April 2017