OpenBSC November 2012

openbsc@lists.osmocom.org

17 participants
25 discussions

SI Generation and multi-trx setup
by Holger Hans Peter Freyther 26 Nov '12

26 Nov '12

Hi Andreas, Harald, the recent "SI generation" fix broke multi trx setups. This is because when the first (c0) TRX is going up bts->si_valid will include SI2 and other SIs scheduled on the BCCH and once the second trx is going up the code decides it only needs to generate the SI5 (and more). But si_valid still includes SI2 and it will be set on the second trx. I have fixed it locally by setting si_valid to 0 early in the set_system_infos routine and added a warning for this case. How should this be properly fixed for master? Will the content of a specific SI differ from TRX0 to TRX1 of a BTS? Should the si_valid be moved to the trx data structure? I have attached my local patch and would like to have a review for it. comments? ideas? holger

2 7

nanoBTS amplifier
by Adolfo Cugat 24 Nov '12

24 Nov '12

What amplifier do you use with ip.access BTS ??? Adolfo

2 1

Need to buy osmo-NITB
by Akib Sayyed 18 Nov '12

18 Nov '12

Hey guys i wanted to buy Osmo -NITB is it on sale ?? please let me know -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243

3 4

SMPP 3.4 interface in OsmoNITB
by Harald Welte 17 Nov '12

17 Nov '12

Hi all, in case you follow the changelog, you will already have seen this coming: OsmoNITB now has a SMPP interface for submitting MT-SMS. This is by no means some kind of competition to a more complete SMSC developed by other people on this list, but it was a quick solution to a requirement of a commercial user. You can use it to submit SMS identifying the recipient subscriber either by his extension or his IMSI. OsmoNITB will also send SMPP ALERT NOTIFICATION in case a previously detached subscriber comes online again. Contrary to the spec, you don't have to subscribe ot ALERT NOTIFICATIONS, but they will be sent to all ESME's registered. The SMPP interface supports both store-and-forward (via database) as well as forward/transactoin mdoe, where the SMS is attempted for immediate delivery, not buffered and will only send a positive SUBMIT-SM result in case it was acknowledged by the MS. You can submit both GSM charset as well as binary messages. UCS2 is not tested. multi-part SMS (or anything else using UDH) only works with binary SMS at this point, i.e. GSM alphabet encoded multi-part messages are broken. The interface will soon be extended to also cover MO-SMS, where you would configure a given destination address by VTY and then messages to that address would be forwarded to the ESME. Only SMPP 3.4 is currently supported. You will need libsmpp34 from git://git.osmocom.org/libsmpp34.git and need to build openbsc with '--enable-smpp' 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

FYI: Testing/merging jolly/sms (and zecke/jolly-sms)
by Holger Hans Peter Freyther 16 Nov '12

16 Nov '12

Hi all, I have rebased jolly/sms and split it up (first use the routines that were moved to libosmocore and that create compile errors, then begin to use the DLSMS debug area, then the actual patches in a way that all of them compile to allow to bisect them). I am now manually testing them with the help of the sysmocom modem bank. There are various issues that needs to be resolved before the 29C3 to be able to use the code. I am just listing them here for reference. There is a double trans_free in the new code now that will lead to segfaults and various 'soft' failures. I am just including some log messages: gsm0411_smc.c:308 Cannot release yet current state: WAIT_CP_ACK gsm0411_smc.c:511 Message 0x332/1 unhandled at this state WAIT_CP_ACK. gsm0411_smc.c:517 RX Unimplemented CP msg_type: 0x332 gsm0411_smc.c:134 TX CP-ERROR, cause 97 (Message Type doesn't exist) gsm_04_11.c:913 Transaction contains SMS. gsm_04_11.c:441 RP-DATA (MO) without DST or TPDU ?!? gsm_04_11.c:420 TX: SMS RP ERROR, cause 96 (Invalid Mandatory Information) cheers holger

3 7

gsm and isdn at 29c3
by Andreas Eversberg 16 Nov '12

16 Nov '12

hi list, we (ccc meber and me) are trying to get a pri access line (primary rate isdn) this year. it will provide external connection for the poc (eventphone) and will also allow interconnection of gsm network with the rest of the world. it is not yet clear if we get this line, but we are working on it. the hardware and software side is already tested in our "labs". for connection between poc and gsm network (openbsc), we like to use lcr (linux-call-router via mncc interface). there are two ways to connect to eventphone, one via isdn line (or virtual isdn over ip) and another one via sip trunk. we like to use both ways for better testing. the registration process for gsm extensions is already set up by evenphone. visit https://www.eventphone.de to register your gsm extension. for syncing eventphone's database with hlr of openbsc, i can provide help. also i will provide helpdesk for gsm questions this year again. regards, andreas

1 0

2 x nanoBTS model 139 Available
by Stuart Baggs 16 Nov '12

16 Nov '12

Hi All We've upgraded a couple of our cells to model 165Gs and have the older model 139s we've removed available for sale. They're both in perfect working order and have been used with OpenBSC for a year now. Thanks

1 0

G4
by Hans Witvliet 14 Nov '12

14 Nov '12

Hi all, I've been hearing all sorts of rumours about nano- pico- or femto-cells for sale in California, around $99 capable of G4/LTE. Does anybody know if that is fact-or-fiction? If true, might that be something for openbsc? Hans.

1 0

nanoBTS for sell
by Axel Walsleben 14 Nov '12

14 Nov '12

I am selling my nanoBTS EGSM900 / 165CU. one is on Ebay item number: 150946617641, i also have a second one, same technical specs.

1 0

ChanModify
by Pierre Kim 11 Nov '12

11 Nov '12

<000f> bsc_api.c:315 Sending ChanModify for speech 1 1 <000c> rtp_proxy.c:258 Correcting frame difference of 38886 frames I used to get these messages when I make a call using osmo-nitb. But recently I updated to newest git version and I get something like <000b> bsc_api.c:374 Sending ChanModify for speech 0 1 <000b> bsc_api.c:118 Using non speech mode: 0 <000b> osmo_msc.c:73 Assignment complete should not have been reached. And I get no sound for my phones. There is a year gap between the previous version and the new version, so I couldn't locate exactly what change is causing this. Can somebody help me fixing it?

3 24

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC November 2012