May 2018 - OpenBSC - lists.osmocom.org

OsmoCon 2018 CfP / submit your topic[s] *now* !
by Harald Welte 25 May '18

25 May '18

Dear Osmocom community, one of the main difficulty with OsmoCon 2017 last year was that nobody submitted talks / discussions within the deadline, early enough to allow for proper planning. This lead to the situation where the sysmocom team had to come up with a schedule/agenda on their own. Later on *much after the CfP deadline*, people then squeezed in talks, making the overall schedule too full. It is up to you to avoid this situation again in 2018 by submitting your talk *RIGHT NOW*. We will be very strict regarding late submissions. So if you would like to shape the Agenda of OsmoCon 2018, this is your chance. Please use it. We will have to create a schedule soon, as [almost] nobody will register to a conference unless the schedule is known. If there's not sufficient contribution in terms of CfP response from the wider community, don't complain later that 90% of the talks are from sysmocom team members and only about the Cellular Network Infrastructure topics. You have been warned. Please make your CfP submission in time at https://pretalx.sysmocom.de/osmocon2018/cfp before the CfP deadline on *2018-05-30 23:59 (Europe/Berlin)* Thanks for your kind attention. Looking forward to meet with the community at OsmoCon 2018 in October. 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)

1 0

IPAccess Nanobts error
by Akib Sayyed 24 May '18

24 May '18

Dear list I am trying to register IPAccess NanotBTS using OsmoNiTB after some time BTS gives error and restarts. I have attached log of osmonitb. Here is some part of log ERROR <0004> (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4) Abis RSL rx IPACC: mismatching chan_nr=0x08 ERROR <0004> (bts=0,trx=0,ts=1,pchan=SDCCH8) Abis RSL rx IPACC: mismatching chan_nr=0x09 BTS 0: Failure Event Report: Type=processing failure, Severity=warning level failure, Probable cause=Manufacturer specific values: Software warning, Additional Text=9105:WARN:OAM_RES:res_trx_status.c#209:TRX is not responding - reinitialising t. BTS 0: Failure Event Report: Type=processing failure, Severity=warning level failure, Probable cause=Manufacturer specific values: Software warning, Additional Text=FSM Unhandled Event class=Baseband Transceiver inst=0 ev="DISABLED RSP" st=ini. BTS 0: Failure Event Report: Type=processing failure, Severity=warning level failure, Probable cause=Manufacturer specific values: Software warning, Additional Text=FSM Unhandled Event class=Channel inst=0 ev="DISABLED RSP" st=initial -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243

2 1

The reason why you see paging by IMSI in real-world GSM networks
by loay abdelrazek 22 May '18

22 May '18

Hello All I wanted to ask your about something regarding user privacy leakage in the broadcast channels. As i have been sniffing and testing myself and i found that on the paging requests type 1 IMSI along with TMSI is sent. I have came to understand that first sending two identifications is the norm, but what i dont understand the high rate of sending IMSI as mobile identification, and as per specification its noted that either TMSI OR IMSI are sent, so does that by any mean could be a configuration issues from the MSC/VLR side that should be changed, is this the norm? if its the norm, then why using TMSI. >From your experience what are the countermeasures you think that should be taken from the operator side to protect against such information leaks, or there is nothing that an operator can do much for this ?What could be the different cases where the IMSI could be sent ? Thanks

3 5

requesting working demo config files for 2g setup osmomsc, osmobsc, osmostp,osmohlr, osmomgw
by toby 22 May '18

22 May '18

Dear All, I was wondering whether anyone could please provide me a set of fully working configuration files for a network-in-the-box setup with msc, bsc, stp, hlr, mgw parts (not osmo-nitb). I have successfully compiled all the required software from source, however, the migration guide is incomplete and I cannot seem to find a simple tutorial for building an osmo network from scratch using all the new components. I want to set up a 2g network for calls/sms, i don't need gprs though. Thanks! Sincerely, Toby M.

4 5

libsmpp34 C code sample to receive SMS
by Rafael Diniz 18 May '18

18 May '18

Hi all, In libsmpp34 git there are examples on how to send an SMS (esme in test_app directory, for example), but none to receive on SMS (from osmo-nitb / osmo-msc tcp smpp port). In case anyone has some sample C code to receive SMS using libsmpp34... it will help me. ; ) Thanks, Rafael Diniz

1 0

LIBVERSION of libsmpp34
by Thorsten Alteholz 16 May '18

16 May '18

Hi, I stumbled upon LIBVERSION in src/Makefile.am of libsmpp34. Is there a reason why it changed from 0:1:0 to 1:0:0? At least the names of all exported symbols did not change!? Thorsten

2 1

OsmoHLR understanding/documentation/testing
by Mykola Shchetinin 16 May '18

16 May '18

Good day, ladies and gentlemen that's a great community you have. Mobile communications programming is a demanding field requiring best developers. I would be extremely grateful if you find time to answer a couple of my simple questions. I found myself reading the code of OsmoHLR project in order to understand how it works and how the GSUP protocol works (it seems that the only example of the GSUP-server is OsmoHLR). How do you understand the code when you need to modify it or accomplish other things that programmers usually do? It seems to not be documented much. Though I feel fluent in C, I find it hard to understand what is going on there. I've come up with an idea of running the OsmoHLR with a debugger. But in order to see what actually happens in the code when the location update is being performed (for example) I need to have the real phone and the real BTS, don't I? How do you check that the code is working as intended? Thank you very much! Kind regards, Mykola Shchetinin

6 12

Re: Huawei BBU3900
by Harald Welte 14 May '18

14 May '18

Hi Shingy, On Mon, May 14, 2018 at 07:51:28PM +0200, Shingirai Simba wrote: > My name is shingy and like Nico it's my first post on mailing list. welcome! > I have access to both the Huawei BBU3900 and Old ZTE BTS at my > university.(Not sure of model as yet). Would love to do that on my > masters degree. We would be more than happy to integrate any code for supporting more vendors in OsmoBSC. > Does anyone have an idea how we can get our hands on protocol traces. I would expect your university has some BSC/network simulator or a core network+BSC to get those BTSs up and running? How were they used so far? If you have some kind of environment where the BTSs can be brought up, and you have some additional E1 interface cards so you can trace the interface between BSC and BTS, a significant step forward is made. However, if you don't have protocol-level documentation from Huawei or ZTE, and you cannot get any Abis protocol traces of BTS bring-up, it is almost impossible to get them ever supported from Osmocom, sorry. -- - 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)

1 0

expected osmocom.org downtime on Sunday, 2018-05-13
by Harald Welte 14 May '18

14 May '18

Dear Osmocom community, this sunday (May 13), I'm planning to do some of the pending migration of osmocom.org services from our old server to a new machine. This will cause some downtime. Hopefully it will be minimal, but I'm sure there will be unexpected events that will mean some of the osmocom.org services will be unavailable at some point during Sunday. In terms of priorities, gerrit is high up on the list, so this will be my primary focus. If that goes well, redmine is the next on the list. In case you're interested in the gory details, https://osmocom.org/issues/3076 is the overview ticket. -- - 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)

1 1

Huawei BBU3900
by NG 14 May '18

14 May '18

Hello everybody, My name is Niko, and it's my first post on mailing list. Is it possible to use OpenBSC together with Huawei BBU3900, or Ericsson RBS6601? Thanks in advice Niko

2 1