OpenBSC

openbsc@lists.osmocom.org

13 participants
4246 discussions

Start a nNew thread

Open bsc + trixbox
by FABIAN SMITH 14 Jun '09

14 Jun '09

Will openbsc work with trixbox or other pbx's ?

2 1

Ideas regarding BSC/MSC split up
by Holger Freyther 12 Jun '09

12 Jun '09

Hey Guys, some of us started to look into the various 08.0x specs and even SCCP (not me yet) and I think our common goal is to go towards a more "normal" BSS/MSC and in the same way keeping the spirit of bsc_hack to allow to run a whole network with one executable. A rough split up of BSC vs. MSC would be: BSC has the secret of: - init hardware, bcch, oml/rsl setup - paging - channel allocation/management MSC has most of the policies: - HLR/VLR and who to allow into the network - call handling etc... To keep this short ('m quite tired at the moment) my goal/approach is to create a libmsc.a and move the db.c, gsm_subscriber.c and on the way to move policy out of gsm_04_08.c to the libmsc.a. bsc and msc would communicate with an API that resembles the DTAP, BSSMAP interface. The MNCC use case Andreas and Harald are working on should remain supported, same as the bsc_hack.c. The goal of having an interface like DTAP and BSSMAP is to allow implementing the A-Interface. I will start this work in a branch called holger/msc and will seek for feedback once I have something that is worthwhile to share. good night z.

2 2

patch 36: application interface
by Andreas.Eversberg 12 Jun '09

12 Jun '09

<<36_application.patch>> again the application patch based on the current OpenBSC source and the other patches i posted. i cannot split this patch, because all the parts depend on each other. the only thing i can do, i can splitt them into their functional parts. the libbsc will not work without applying all parts then.

2 1

Question: Allow Mobile Attach
by Eric Cathelinaud 12 Jun '09

12 Jun '09

Hi! I am trying to understand the code to make several tests. If I understand, the default setting is to refuse any phone trying to connect the network? I would like to change this in the code to accept everyone. I saw in bsc_hack the Control Channel Description which seems to deal with this. Am I wrong? static u_int8_t si3[] = { /* header */0x49, 0x06, 0x1B, /* cell */0x00, 0x01, /* lai */0x00, 0xF1, 0x10, 0x00, 0x01, /* desc */0x01, 0x03, 0x00, //Control Channel Description /* option*/0x28, /* selection*/0x62, 0x00, /* rach */0xD5, 0x00, 0x00, /* reset*/0x80, 0x00, 0x00, 0x2B }; Which value shall I put to accept everyone? Thanks! Best regards Eric Cathelinaud

3 3

patch 34: paging lac
by Andreas.Eversberg 10 Jun '09

10 Jun '09

this patch will use the gsm_bts_by_lac() function to start paging of all bts' with the same lac. when paging is successfull, the paging_request_stop() function is called with the current lchan, so the callback function will be called. for all other bts', the paging_request_stop() function is called without lchan, so the paging is stopped, but the callback function is not called. this ensures that only one paging result is received when paging multiple BTS.

4 6

patch 28: wrieshark pcap logging
by Andreas.Eversberg 10 Jun '09

10 Jun '09

This patch fixes the PCAP logging. If frames are received from E1 interface, an 8 byte mISDN header (MISDN_HEADER_LEN) is in front of the RSL packet. When frames are transmitted to the E1 interface, the pcap_write_packet function will get a message buffer without the mISDN header in front of the RSL packet. The pcap file was tested and the output is correct.

2 2

AW: layer 1 debugging
by Andreas.Eversberg 10 Jun '09

10 Jun '09

BN1E1 seems to have different layouts over the time. i always jumper the cards to TE, so i use a crosslink cable for NT to TE. ________________________________ Von: openbsc-bounces(a)lists.gnumonks.org [mailto:openbsc-bounces@lists.gnumonks.org] Im Auftrag von Eric Cathelinaud Gesendet: Mittwoch, 10. Juni 2009 10:41 An: Harald Welte Cc: openbsc(a)lists.gnumonks.org Betreff: Re: layer 1 debugging I tried to short the left and to invert the twinax plug (thus pluging them as in the wiki) and it works too. Then it could be a mistake in the jumper plan of BN1E1 cause they say that the left is "TE" and not "NT". Anyone else dealing with a BN1E1 card to confirm? Eric Cathelinaud 2009/6/9, Eric Cathelinaud <e.cathelinaud(a)googlemail.com>: 2009/6/9 Harald Welte <laforge(a)gnumonks.org> Hi Eric, On Tue, Jun 09, 2009 at 12:56:25PM +0200, Eric Cathelinaud wrote: > Thanks a lot for this layer 1 debugging tutorial. It helped me a lot since i > was thinking I did something wrong with mISDN. I checked the step 3 and find > out that my ISDN card was working fine. > Then I tried to invert my twinax plugs and it worked. I think there is a > mistake in the wiki. > It's written in http://bs11-abis.gnumonks.org/trac/wiki/BS11_Configuration : > - left Y01 PCM in (from BSC): RJ45 pin 4,5 > - Y02 PCM out (to BSC): RJ45 pin 1,2 > > but for me it works with : > Y01 PCM : RJ45 pin 1,2 (orange / white orange for a straight cable) > Y02 PCM : RJ45 pin 4,5 (blue / white blue for a straight cable) I think that depends on the jumper configuration of your E1 card. Did you really put the jumpers in "NT Mode" configuration? Yes I put NT Mode following the jumper plan (short pins on the right). My card is a Beronet BN1E1. I will try to short pins on the left and let you know if working as in wiki. > I can now see the network on my mobile phone thanks a lot. great! -- - 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

layer 1 debugging
by Andreas.Eversberg 10 Jun '09

10 Jun '09

hi, i added layer 1 state change (and initial state) reporting to mISDN kernel driver. this is usefull to resolve E1 connection problem. 1. download the latest mISDN driver from www.mISDN.org using git: git-clone git://git.misdn.org/git/mISDN.git/ change to socket branch: cd mISDN ./checkout-branch.sh socket compile and install as usual make force # remove kernel mISDN includes make make install load mISDN as usual. 2. run bsc_hack using debug option: --debug=DMI Allowing everyone? DB: Database initialized. DB: Database prepared. 1 devices found id: 0 Dprotocols: 00000018 Bprotocols: 0000006e protocol: 4 nrbchan: 30 name: hfc-e1.1 activate bchan activate bchan Mon Jun 1 18:51:43 2009 <1000> input/misdn.c:124 alen =6, dev(9) channel(0) sapi(63) tei(127) Mon Jun 1 18:51:43 2009 <1000> input/misdn.c:127 <= len = 12, prim(0x8) id(0x7f3f): DL_INFORMATION_IND Mon Jun 1 18:51:43 2009 <1000> input/misdn.c:134 DL_INFORMATION_IND: use channel(0) sapi(63) tei(127) for now mISDN message for unknown sign_link Mon Jun 1 18:51:43 2009 <1000> input/misdn.c:124 alen =6, dev(9) channel(0) sapi(63) tei(127) Mon Jun 1 18:51:43 2009 <1000> input/misdn.c:127 <= len = 8, prim(0x102) id(0x7f3f): PH_ACTIVATE_IND Mon Jun 1 18:51:43 2009 <1000> input/misdn.c:161 PH_ACTIVATE_IND: channel(0) sapi(63) tei(127) in this case we see "PH_ACTIVATE_IND", because BS11 is connected and sending a signal. 3. check your card: (most common type) close to the plug there are two jumpers. the are used to select between 1,2,4,5 and 1,2,3,6 pin selection. be sure they are to the left for standard 1,2,4,5 pinning. take an rj45 plug and connect pin 1 with 4 and 2 with 5. start bsc_hack and plug it into your card. you should see "PH_ACTIVATE_IND" when you plug it. your card is working. if nothing works, check your termination switches. refer to the card's manual. the must be set to 120 ohms, if the termination jumpers on your BS11 are pulled out. without termination, the card might not work. 4. check your BS11 remove the plug and connect the cable to the BS11: one pair (pin 1 and 2) to Y01 and one pair (pin 4 and 5) to Y02. after bootup ob BS11 you will see "PH_ACTIVATE_IND" if you connect both paris in the correct order. you must connect both pairs because BS11 will only send a signal, if it receives a signal. pin 1 can be wapped with pin 2, pin 4 with pin 5 also. the E1 interface does not care about that. 5. check data link connection: you have already received the management process via "DL_INFORMATION_IND" on sapi 63 tei 127. if BS11 software load is running, you will receive additional data links from BS11: - sapi 62 tei 25 - sapi 0 tei 25 - sapi 0 tei 1 these are three datalinks. each one is created and sends us "DL_INFORMATION_IND" on creation, "DL_ESTABLISH_IND" on activation and "DL_DATA_IND" when receiving data on that link. hope that helps. andreas

3 5

patch 35: information element transcoding
by Andreas.Eversberg 10 Jun '09

10 Jun '09

this patch will do the transcoding of information elements. this patch adds new functions to be used for the application interface patch, and is basis for the application patch (currently patch 36). when applying the patch, the compiler gives warnings, because the "static" functions will not be used. (yet)

2 1

patch 33: db fix
by Andreas.Eversberg 09 Jun '09

09 Jun '09

during attachment, the "tmsi" field of the subscriber may be an empty string, so the string must be quoted in the sql request, or the sql request fails due to incorrect syntax. also i added "extension" field to debug output.

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC