OpenBSC

openbsc@lists.osmocom.org

4317 discussions

AW: Problem testing E1 link
by Andreas.Eversberg 28 May '09

28 May '09

> In my menuconfig I put an * for : > <*> Modular ISDN driver ---> <*>Digital Audio Processing of transparent data > <*>ISDN over IP tunnel > <*>Support for HFC PCI cards > <*>Support for HFC multiport cards (HFC-4S/8S/E1) try compile as module then load after boot modprobe mISDN_core modprobe hfcmulti dslot=1 > Is there something more to do for mISDN? I saw on mISDN.org that mISDNv2 is already in the kernel >= 2.6.27 so I were thinking it should work directly. no it doesn't! it works for ISDN, but not for openbsc. openbsc requires differen SAPI values and multiple layer 2 processes on the d-channel. it will work with the latest mISDN from git repository: git clone git://git.misdn.org/git/mISDN.git cd mISDN sh checkout-branch.sh socket <- change to socket branch (mISDNv2) make force <- delete all mISDN includes from kernel. make make install be sure to disable mISDN support from kernel. the modules from git will be installed under /lib/modules/xxxx/extra. the "extra" modules have lower priority than the kernel modules, so disable mISDN in kernel config and reinstall modules (make modules && make modules_install). unused modules will then be removed. then install the git modules as described above.

1 0

Problem testing E1 link
by Eric Cathelinaud 27 May '09

27 May '09

Hello, Now I can configure the bs11 using the bs11_config. Everything worked fine and I obtained this on bs11_config query : LMT LOGON: ACK PHASE: 3 Normal MBCCU0: Load MBCCU1: No Load Abis-link: Restoring BS11 ATTRIBUTES: BS-11 ESN PCB Serial Number: 001073 BS-11 ESN Hardware Code Number: 135-2044/03.03 BS-11 ESN Firmware Code Number: 135-2044/03.03 PLL Set Value=1053, Work Value=1053 SITE MANAGER ATTRIBUTES: E1 Channel: Port=0 Timeslot=1 (Full Slot) TEI: 25 BS11 Line Interface ATTRIBUTES: PLL Mode: Standalone BS11 Power Amplifier 0 ATTRIBUTES: TRX Power: 30mW (GSM) Mon May 25 16:01:12 2009 <0020> abis_nm.c:811 GET ATTRIBUTE NACK LMT LOGOFF: ACK I didn't doanwload: -the SAFETY LOAD software -the BTS software Is it necessary since I can reach Phase 3 and since I can see the Firmware Code Number? I continued to follow the "getting started" tutorial untill the E1 Link and I have the following problem when launching bsc_hack : ./bsc_hack -f 123 --debug=DRLL:DCC:DMM:DRR:DRSL:DNM:DMI:DMUX:DPAG:DRLL:DSMS DB: Database initialized. DB: Database prepared. 1 device found id: 0 Dprotocols: 00000018 Bprotocols: 0000006e protocol: 4 nrbchan: 30 name: hfc-e1.1 activate bchan activate bchan Mon May 25 16:07:39 2009 <1000> input/misdn.c:125 alen =6, dev(0) channel(0) sapi(63) tei(127) Mon May 25 16:07:39 2009 <1000> input/misdn.c:128 <= len = 12, prim(0x8) id(0x7f3f): DL_INFORMATION_IND Mon May 25 16:07:39 2009 <1000> input/misdn.c:135 DL_INFORMATION_IND: use channel(0) sapi(63) tei(127) for now mISDN message for unknown sign_link May be it's coming from my BN1E1 card from Beronet. I only changed the Dip switches for 120 ohms. I can see 2 steady red led (which means i am in NT mode, TE mode deactivate). Both green leds are off (is it normal?). /* HFC-E1 OEM */ + /* 2 red blinking: NT mode deactivate + * 2 red steady: TE mode deactivate + * left green: L1 active + * left red: frame sync, but no L1 + * right green: L2 active + */ Anyone? Thanks in advance! Best regards Eric Cathelinaud

3 3

Howto for OpenBSC, LCR and Asterisk
by codec 27 May '09

27 May '09

Hi, I wrote a small howto for the setup of OpenBSC, LCR and Asterisk. I'll add it to the wiki within the next days. https://brezn.muc.ccc.de/~codec/openbsc/howto.txt Sorry for the broken english. ;P cheers, -- codec "All children are artists. The problem is how to remain an artist as one grows up." -- Picasso

1 1

AW: Problem testing E1 link
by Andreas.Eversberg 26 May '09

26 May '09

did you load hfcmulti.ko with dslot=1 parameter? this is required to move dchannel slot from 16 to 1. > Mon May 25 16:07:39 2009 <1000> input/misdn.c:125 alen =6, dev(0) channel(0) sapi(63) tei(127) > Mon May 25 16:07:39 2009 <1000> input/misdn.c:128 <= len = 12, prim(0x8) id(0x7f3f): DL_INFORMATION_IND > Mon May 25 16:07:39 2009 <1000> input/misdn.c:135 DL_INFORMATION_IND: use channel(0) sapi(63) tei(127) for now > ISDN message for unknown sign_link >

3 4

AW: patch: 16_subscr_lac
by Andreas.Eversberg 23 May '09

23 May '09

This patch in conjunction with patch 15 (paging lac) makes patch 8 (paging) obsolete. > The patch will store the current LAC in the HLC when the subscriber successfully attaches. If the subscriber detaches, the LAC will be set to 0. > This patch is required to make patch 15 (paging) work. This patch does not depend on any other patch i made.

1 0

patch: 14_DMM
by Andreas.Eversberg 23 May '09

23 May '09

a minor fix of DMM debugging. now MM debugging is shown, if given by debug option, not only by default debugging. the color of DNM debugging changes to cyan as it is supposed to be.

1 0

patch: 15_paging_lac
by Andreas.Eversberg 23 May '09

23 May '09

This patch will resolve all BTS with the LAC of the subscriber and page every BTS with this LAC. If the subscriber is not currently attached, the LAC is not set, so the caller will get cleared with cause 27 (MO out of order). This patch must be applied AFTER patch 12 (application interface) has been applied.

1 0

patch: 16_subscr_lac
by Andreas.Eversberg 23 May '09

23 May '09

The patch will store the current LAC in the HLC when the subscriber successfully attaches. If the subscriber detaches, the LAC will be set to 0. This patch is required to make patch 15 (paging) work. This patch does not depend on any other patch i made.

1 0

patch: 11_trau
by Andreas.Eversberg 23 May '09

23 May '09

I improved trau_mux.c. Now it supports not just bridging only. A new function "trau_recv_lchan" is used to link a channel to a call reference of a transaction. (Transactions are used in later patches.) TRAU frames will then be forwarded to the application with the given call reference (in later patches). Also the application can send TRAU frames by using "trau_send_lchan". A new list is introduced in trau_mux.c. (upqueue_entry) All subslots that must be sent to application are listed here. Received TRAU frames are written in the upqueue of application interface, if a call reference is found in the upqueue-list. If an entry is found the ss_entry list, the TRAU frames are bridged as before. The frames have a message type (msg_type), a call reference (callref) and a trau frame (data). The length of trau frame is defined by the content of the c-bits inside the frame. There is no support for ip-access yet. Harald must add this in order to use application interface with ip-access. The bridging with ip-access works as before.

2 1

AW: patch: 8_paging
by Andreas.Eversberg 23 May '09

23 May '09

i use the calling party's BTS, because the subscriber database does not contain the current BTS number of the subscriber last seen. (or detached) i agree that the subscriber gives us information about the paged bts and we can resolve the gsm_network from that also. -----Ursprüngliche Nachricht----- Von: Harald Welte [mailto:laforge@gnumonks.org] Gesendet: Samstag, 23. Mai 2009 08:30 An: Andreas.Eversberg Cc: openbsc(a)lists.gnumonks.org Betreff: Re: patch: 8_paging Hi again, On Sat, May 23, 2009 at 02:23:11PM +0800, Harald Welte wrote: > On Thu, May 21, 2009 at 02:27:36PM +0200, Andreas.Eversberg wrote: > > Paging refers to a BTS. To page a mobile phone, the current location > > is required. If paging succeeds or expires, the BTS structure is > > also given to the callback function (cbfn). > > > > Because paging refers to a BTS, the cbfn (callback function) must > > include a pointer to bts. > > The paging response includes a lchan pointer, which can be resolved to > the physical channel / timeslot and to the trx and finally to the BTS. > Is this not sufficient? Ah, ok, in the case we do not successfully allocate a lchan, then that's obviously NULL. Still, when you call paging_request() you actually pass on a number of parameters, including: 1) the BTS on which you want to page (whcih, indeed, is currently the BTS of the calling party rather than the called party). So this parameter is likely to get removed soon. 2) The subscriber that was called. This should be used by paging_request() to resolve the BTS that this subscriber was last seen/registered to. 3) a reference to the call, which is treated as an opaque pointer that is passed back as a reference when calling the call-back function. So if the bts of the calling or called party needs to be known, it should probably be referenced from that data structure. Or am I missing something? -- - 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 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC