OpenBSC

openbsc@lists.osmocom.org

4315 discussions

Location Update (IMSI Attach) Procedure
by Thomas Cooper 22 Feb '12

22 Feb '12

Hey Osmoworld, Just a little intro before my rambling questions... I've been working on connecting OpenBTS and osmo-bts/OpenBSC together, and everything works well enough to at least send messages between the two (it's somewhat hackish but it works for me so far). The phone sees the network and when I attempt to connect, it is assigned a SDCCH and starts the typical location update process. This makes me think the underlying issue is in my OpenBSC/network setup. Now for the problems: (probably best to check the console output below first) Even though the MS receives an ID request and returns an ID response, the LU Request times out and returns cause=13 (default from config). I'm not sure what happens after the ID response since it doesn't seem to have sent anything else down to the MS. I also don't know too much about the MS's job, but it seems to send 3 LU requests every time (2 of which are unnecessary and rejected as duplicates). I assume that's what the preceding ERROR IND messages are referring to, but I don't know for certain. My BTS BCCH has LAI=001/01/1, which is correctly set in both OpenBTS and OpenBSC config files. The Location Updating Request contains LAI=001/01/65534, which I think may be the main issue since LAC=65534 is reserved (even looking in GSM-04.08, I couldn't find any details about this; can you shed some light please?). The MS works with standard OpenBTS by the way. I've looked through the gsm_04_08 code and Wireshark capture, but no clues stick out. I'm not too familiar with OpenBSC in general, so this could be as simple as setting some kind of config parameter. I figured I'd ask on here for help in case I'm just missing something basic. Here is the console output (with debug and authorize-everyone flags on): Wed Feb 22 13:06:24 2012 <0004> abis_rsl.c:1317 (bts=0,trx=0,ts=0,ss=0) Activating ARFCN(51) SS(0) lctype SDCCH r=LOCATION_UPDATE ra=0x0e ta=0 Wed Feb 22 13:06:24 2012 <0004> abis_rsl.c:1064 (bts=0,trx=0,ts=0,ss=0) CHANNEL ACTIVATE ACK Wed Feb 22 13:06:25 2012 <0000> abis_rsl.c:1493 (bts=0,trx=0,ts=0,ss=0) SAPI=0 ESTABLISH INDICATION Wed Feb 22 13:06:25 2012 <0002> gsm_04_08.c:1023 LOCATION UPDATING REQUEST: mi_type=0x01 MI(460020020292786) type=NORMAL Wed Feb 22 13:06:25 2012 <0001> gsm_04_08.c:114 (bts 0 trx 0 ts 0 pd 05) Sending 0x18 to MS. Wed Feb 22 13:06:25 2012 <0000> abis_rsl.c:1493 (bts=0,trx=0,ts=0,ss=0) SAPI=0 Wed Feb 22 13:06:25 2012 <0000> abis_rsl.c:1439 (bts=0,trx=0,ts=0,ss=0) ERROR INDICATION cause=unknown 0x0 Wed Feb 22 13:06:25 2012 <0000> abis_rsl.c:1493 (bts=0,trx=0,ts=0,ss=0) SAPI=0 ESTABLISH INDICATION Wed Feb 22 13:06:25 2012 <0002> gsm_04_08.c:1023 LOCATION UPDATING REQUEST: mi_type=0x01 MI(460020020292786) type=NORMAL ignoring request due an existing one: 0x20f1350. Wed Feb 22 13:06:25 2012 <0002> gsm_04_08.c:383 Subscriber 460020020292786: LOCATION UPDATING REJECT LAC=1 BTS=0 Wed Feb 22 13:06:25 2012 <0001> gsm_04_08.c:114 (bts 0 trx 0 ts 0 pd 05) Sending 0x04 to MS. Wed Feb 22 13:06:25 2012 <0000> abis_rsl.c:1493 (bts=0,trx=0,ts=0,ss=0) SAPI=0 Wed Feb 22 13:06:25 2012 <0000> abis_rsl.c:1439 (bts=0,trx=0,ts=0,ss=0) ERROR INDICATION cause=unknown 0x0 Wed Feb 22 13:06:25 2012 <0000> abis_rsl.c:1493 (bts=0,trx=0,ts=0,ss=0) SAPI=0 ESTABLISH INDICATION Wed Feb 22 13:06:25 2012 <0002> gsm_04_08.c:1023 LOCATION UPDATING REQUEST: mi_type=0x01 MI(460020020292786) type=NORMAL ignoring request due an existing one: 0x20f1350. Wed Feb 22 13:06:25 2012 <0002> gsm_04_08.c:383 Subscriber 460020020292786: LOCATION UPDATING REJECT LAC=1 BTS=0 Wed Feb 22 13:06:25 2012 <0001> gsm_04_08.c:114 (bts 0 trx 0 ts 0 pd 05) Sending 0x04 to MS. Wed Feb 22 13:06:25 2012 <0000> abis_rsl.c:1493 (bts=0,trx=0,ts=0,ss=0) SAPI=0 DATA INDICATION Wed Feb 22 13:06:25 2012 <0003> bsc_api.c:430 CLASSMARK CHANGE CM2(len=3) CM3(len=4) Wed Feb 22 13:06:27 2012 <0000> abis_rsl.c:1493 (bts=0,trx=0,ts=0,ss=0) SAPI=0 DATA INDICATION Wed Feb 22 13:06:27 2012 <0002> gsm_04_08.c:446 IDENTITY RESPONSE: mi_type=0x02 MI(357966009107140) Wed Feb 22 13:06:30 2012 <0002> gsm_04_08.c:484 Location Updating Request procedure timedout. Wed Feb 22 13:06:30 2012 <0002> gsm_04_08.c:383 Subscriber 460020020292786: LOCATION UPDATING REJECT LAC=1 BTS=0 Wed Feb 22 13:06:30 2012 <0001> gsm_04_08.c:114 (bts 0 trx 0 ts 0 pd 05) Sending 0x04 to MS. Wed Feb 22 13:06:30 2012 <0000> chan_alloc.c:429 (bts=0,trx=0,ts=0,ss=0) starting release sequence Wed Feb 22 13:06:30 2012 <0003> gsm_04_08_utils.c:231 Sending Channel Release: Chan: Number: 0 Type: 1 Wed Feb 22 13:06:30 2012 <0004> abis_rsl.c:579 (bts=0,trx=0,ts=0,ss=0) DEACTivate SACCH CMD Wed Feb 22 13:06:31 2012 <0000> abis_rsl.c:1493 (bts=0,trx=0,ts=0,ss=0) SAPI=0 RELEASE INDICATION Wed Feb 22 13:06:31 2012 <0004> abis_rsl.c:621 (bts=0,trx=0,ts=0,ss=0) RF Channel Release CMD due error 0 Wed Feb 22 13:06:31 2012 <0004> abis_rsl.c:658 (bts=0,trx=0,ts=0,ss=0) RF CHANNEL RELEASE ACK Thanks for any help, Tom Cooper -- Graduate Research Assistant Wireless @ Virginia Tech tacooper(a)vt.edu

1 1

Re: OsmoDevCon preliminary schedule
by Dieter Spaar 21 Feb '12

21 Feb '12

Hello David, > I could also give a more detailed presentation on the radiomodem and > FEC parts of OpenBTS if there is interest in such low-layer details, > maybe on Monday afternoon if there are still people around. I am interested too, however I have to leave on Monday afternoon. But if I am the only one affected there is of course no need to change the schedule. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

4 4

OsmoDevCon planning / agenda
by Harald Welte 20 Feb '12

20 Feb '12

Hi all! Time is moving fast, and the OsmoDevCon is getting closer. There's still two months, but I think we should start to put together some kind of agenda. First of all, I would like to ask when we should start on Friday. I would make this somewhat dependent on when the participants will be arrviing. So far I was thinking about 10am. Please let me know if you arrive on Friday but significantly later than that. I have collected a number of topics for both 'presentation' style events as well as more round-table/discussion items at https://bs11-abis.gnumonks.org/trac/wiki/OsmoDevCon2012#Presentations and https://bs11-abis.gnumonks.org/trac/wiki/OsmoDevCon2012#WorkingGroupDiscuss… respectively. Please feel free to add topics that you want to speak yourself about, or that you would like to hear about. For example, we don't have anything about OsmoSDR or SIMtrace at this point, but I'm not sure how much interest there is about those topics. I would like to collect topics until 2012-02-15, and then start to make some kind of schedule. 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)

2 1

nanoBTS
by Gsm Freak 18 Feb '12

18 Feb '12

Hi, Can anyone please help me buy used nanoBTS? Thanks,

1 0

nanoBTS with newer firmware (patch)
by flw＠smart.ms 16 Feb '12

16 Feb '12

Hi list, I just had tried to connect a nanoBTS model 165a with firmware v142b13d0 to openBSC. The BTS does connect to OML, starts with the PING - PONG and identifies itself, but nothing else happens (i.e. no software activate request). As recent firmware requires an explict IDENTITY ACK after answering an IDENTITY REQ with the RESP, I made a small patch to ipaccess.c - and voila, BTS connects OML, gets initalised (at the second attempt as usual - I'll try to dig into this later), establishes RSL and is happily showing green. Feel free to integrate the attached patch. Best regards, Flo.

1 0

Newbie question: CM Service reject
by Don Fanning 11 Feb '12

11 Feb '12

Hello All, After some trials and tribulations, I think I got my OpenBSC+LCR+Asterisk compiles and working. The MS connects once I spoof the proper MCC/MNC for the foreign SIM I have (to ensure that no one else can connect within my area). Then when I try to make a test call to an asterisk extension, it give me the following: Thu Feb 9 18:55:58 2012 <0004> abis_rsl.c:1318 (bts=0,trx=0,ts=2,ss=0) Activating ARFCN(514) SS(0) lctype TCH/F r=CALL ra=0x4f ta=1 Thu Feb 9 18:55:58 2012 <0004> abis_rsl.c:1064 (bts=0,trx=0,ts=2,ss=0) CHANNEL ACTIVATE ACK Thu Feb 9 18:55:58 2012 <0000> abis_rsl.c:1490 (bts=0,trx=0,ts=2,ss=0) SAPI=0 ESTABLISH INDICATION Thu Feb 9 18:55:58 2012 <0002> gsm_04_08.c:858 <- CM SERVICE REQUEST serv_type=0x01 mi_type=0x04 M(210271915) Thu Feb 9 18:55:58 2012 <0002> gsm_04_08.c:800 -> CM SERVICE Reject cause: 2 Thu Feb 9 18:55:58 2012 <0001> gsm_04_08.c:114 (bts 0 trx 0 ts 2 pd 05) Sending 0x22 to MS. Thu Feb 9 18:55:58 2012 <0000> abis_rsl.c:1490 (bts=0,trx=0,ts=2,ss=0) SAPI=0 DATA INDICATION Thu Feb 9 18:55:58 2012 <0003> bsc_api.c:430 CLASSMARK CHANGE CM2(len=3) CM3(len=9) Thu Feb 9 18:56:03 2012 <0000> chan_alloc.c:429 (bts=0,trx=0,ts=2,ss=0) starting release sequence Thu Feb 9 18:56:03 2012 <0003> gsm_04_08_utils.c:231 Sending Channel Release: Chan: Number: 0 Type: 2 Thu Feb 9 18:56:03 2012 <0004> abis_rsl.c:579 (bts=0,trx=0,ts=2,ss=0) DEACTivate SACCH CMD Thu Feb 9 18:56:03 2012 <0000> abis_rsl.c:1490 (bts=0,trx=0,ts=2,ss=0) SAPI=0 RELEASE INDICATION Thu Feb 9 18:56:03 2012 <0004> abis_rsl.c:621 (bts=0,trx=0,ts=2,ss=0) RF Channel Release CMD due error 0 Thu Feb 9 18:56:03 2012 <0004> abis_rsl.c:968 (bts=0,trx=0,ts=2,ss=0): MEAS RES for inactive channel Thu Feb 9 18:56:03 2012 <0004> abis_rsl.c:658 (bts=0,trx=0,ts=2,ss=0) RF CHANNEL RELEASE ACK Any assistance would be appreciated. Regards, -Don

3 6

Setting up a fixed IP for the ip.access nanoBTS using ipaccess-telnet
by carcelle 08 Feb '12

08 Feb '12

Hi dear list, After sometimes to get it work, I have set-up a fixed IP on my ip.access nanoBTS and thought that could be helpful to share the howto/tuto from this experience : The best way for linux user is to use the ipaccess-telnet tool from the git (git clone git://git.osmocom.org/libtelnet.git) rather than BTS installer from ip.access which doesn't easily allow the access to the flags of configuration (i.e. NV attributes) of the nanoBTS. 1/installation of ipaccess-telnet I have installed it on a debian 5.0.9 (linux 2.6.26) after git cloning git://git.osmocom.org/libtelnet.git my autotools versions : autoconf 2.61-8 + automake 1:1.10.1-3 after running into the following autotools build #autoreconf; automake --add-missing; autoreconf; autoconf; automake; ./configure --prefix=/usr/local; make -j 2; make install I ran into that error "ltmain.sh: No such file or directory" and used the following command to fix that config error #libtoolize in the libtelnet directory and I had the ipaccess-telnet tool build/installed 2/use of ipaccess-telnet on the nanoBTS once ipaccess-telnet is installed, one should first allow the telnet on port 3210 on the nanobts using that command #ipaccess-config -n 0x400/0x400 BTS_IP which set the correct mask on the flag enabling the telnet on port 3210. Then I could telnet the nanoBTS on port 3210 w/ the following command #ipaccess-telnet <ip> 3210 once on the CLI interface for the nanoBTS, you can get help w/ >help config (...) db::setnetmask <net mask> Sets nBTS IP Net Mask db::setipaddr <ipaddr> Sets nBTS IP address (...) db::getflags (...) db::setflag <flag> Enables Config Flag db::clearflag <flag> Disables Config Flag (...) >dhcp help Expecting 3 arguments DHCP configuration flags in database: - DHCP enabled: TRUE - static IP Address: TRUE - static IP gateway config: FALSE - static VSI config: FALSE DHCP configuration flags in use: - DHCP enabled: TRUE - static IP Address: TRUE - static IP gateway config: FALSE - static VSI config: FALSE DHCP uptime = 52567 seconds DHCP state: BOUND T1 inactive T2 inactive Lease Timer inactive and the static ip configuration : To set-up the IP address >db::setipaddr IP >db::setnetmask netmask To disable the DHCP client >dhcp dhcp false >db::clearflag dhcp Xavier Carcelle

1 0

A-bis OML and OM2000 dissectors in wireshark mainline
by Harald Welte 06 Feb '12

06 Feb '12

Hi all, wireshark has merged all pending patches that we were working on. This means that the daily builds from https://www.wireshark.org/download/automated/osx/ and https://www.wireshark.org/download/automated/win32/ will now work out-of-the-box for any pcap traces of OML (Siemens and ip.access BTS) and OM2000 (Ericsson BTS). The ip.access vendor-specific RSL extensions have also been merged. By the way: If anyone was interested in writing a dissector for the Nokia OML dialect, it would be much appreciated. So far, nobody has started, but the OpenBSC code base contains an implementation of the protocol, and the hardware seems to be used by a number of project members, so getting traces should also not be a problem. Regards, Haralad -- - 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

Issues compiling lcr on debian squeeze for OpenBSC/Asterisk stack
by Don Fanning 02 Feb '12

02 Feb '12

Hello All, I've been working on trying to get OpenBSC to work with Asterisk following this as a guide: http://openbsc.osmocom.org/trac/wiki/OpenBSC_LCR http://www.misdn.org/index.php/Howto_for_Debian Basically I'm missing the mISDN_l1loop kernel module. When trying to compile from the mISDN git repository i'm getting the following error when trying to compile (Ubuntu - 10.04 LTS ) ./configure configure: error: kernel build tree does not exist build:/lib/modules/2.6.32-33-generic/build / source:/lib/modules/2.6.32-33-generic/source (Debian - 6.06) passes configure when "make modules" is running make[3]: Entering directory `/usr/src/linux-headers-2.6.32-5-686' CC [M] /root/mISDN/standalone/drivers/isdn/mISDN/l1oip_core.o CC [M] /root/mISDN/standalone/drivers/isdn/mISDN/l1oip_codec.o CC [M] /root/mISDN/standalone/drivers/isdn/mISDN/core.o CC [M] /root/mISDN/standalone/drivers/isdn/mISDN/fsm.o CC [M] /root/mISDN/standalone/drivers/isdn/mISDN/socket.o CC [M] /root/mISDN/standalone/drivers/isdn/mISDN/clock.o CC [M] /root/mISDN/standalone/drivers/isdn/mISDN/hwchannel.o /root/mISDN/standalone/drivers/isdn/mISDN/hwchannel.c: In function âmISDN_freedchannelâ: /root/mISDN/standalone/drivers/isdn/mISDN/hwchannel.c:113: error: implicit declaration of function âflush_work_syncâ make[6]: *** [/root/mISDN/standalone/drivers/isdn/mISDN/hwchannel.o] Error 1 make[5]: *** [_module_/root/mISDN/standalone/drivers/isdn/mISDN] Error 2 make[4]: *** [sub-make] Error 2 make[3]: *** [all] Error 2 make[3]: Leaving directory `/usr/src/linux-headers-2.6.32-5-686' make[2]: *** [modules_] Error 2 make[2]: Leaving directory `/root/mISDN/standalone' make[1]: *** [modules] Error 2 make[1]: Leaving directory `/root/mISDN/standalone' make: *** [modules] Error 2 root@OpenBSC:~/mISDN# I should note that Centos 5.7 and Gentoo give the same errors as Ubuntu.... Any assistance is appreciated. Regards, -Don

2 1

Re: TCAP Stack
by Holger Hans Peter Freyther 01 Feb '12

01 Feb '12

On 02/01/2012 05:03 PM, Ammar Naamat Hameed wrote: > Hi, this is a Free Software project. You can read about the values of Free Software here[1]. If you do not release the sourcecode you are not part of our community. holger [1] http://simple.wikipedia.org/wiki/Free_software > I haven't published the source code yet, but I have attached two traces, one > of them has the TCAP message that I don't know how to handle which is the > (ReturnResultLast) that has only the InvokeID in it, I hope you can help > figure out this return message. > The other attached trace has (ReturnResultLast ForwardSM) which is normal > reply message to a ForwardSM message about the successful receiving of the SMS > (SMS-Deliver Report). > > Thanks, > Ammar > > *From:* Holger Hans Peter Freyther <holger(a)freyther.de> > *To:* openbsc(a)lists.osmocom.org > *Sent:* Wednesday, February 1, 2012 12:20 AM > *Subject:* Re: TCAP Stack > > On 02/01/2012 12:53 AM, Ammar Naamat Hameed wrote: > > Hi, > > Hi, > > can you send me a link to the sourcecode? > > thanks > > > > >

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC