Hello,
second try to add support to bs11_config for bport0/1 configuration. This
time with enum abis_bs11_line_cfg.
It seems sometimes creating bport1 fails, even LMT shows create obj
greyed out. Don't know why yet.
Regards,
Daniel Willmann
Daniel Willmann (1):
Add {create,delete}-bport1 and bport0-{star,multidrop} to bs11-config
openbsc/include/openbsc/abis_nm.h | 10 +++++++++-
openbsc/src/abis_nm.c | 31 +++++++++++++++++++++++++++++--
openbsc/src/bs11_config.c | 26 ++++++++++++++++++++++++++
3 files changed, 64 insertions(+), 3 deletions(-)
hi,
check if you selected the right timeslot for d-channel: use "dslot=1"
(old driver) or "layermask=0x02" (newer driver) when loading the
hfcmulti.ko.
use "--debug=DMI" and loop your line (connect pin 1 to pin 4, and pin 2
to pin 5). do you get activation-message when looping? if not, be sure
to shift all jumpers toward the slot cover.
if you see the loop, but no activation-message after booting BS11 (takes
about 15 minutes), swap connector 1 and 2. one connector must be
connected to pin 1 and 2, and the other to pin 4 and 5.
andreas
________________________________
Von: openbsc-bounces(a)lists.gnumonks.org
[mailto:openbsc-bounces@lists.gnumonks.org] Im Auftrag von Ihab el Bakri
Gesendet: Donnerstag, 25. Februar 2010 14:59
An: openbsc
Betreff: bsc_hack
Hello there,
finally, got nearly everything to work, but am unable to see the network
on my mobile and am getting this message when running bsc_hack with a
config file :
DB: Database initialized.
DB: Database prepared.
1 device found
id: 0
Dprotocols: 00000018
Bprotocols: 0000000e
protocol: 4
nrbchan: 30
name: hfc-e1.1
activate bchan
activate bchan
<000c> trau_frame.c:116 can't decode unknown TRAU Frame Type 0x00
Thank in advance
Ihab el Bakri
Hi,
I have been looking for a Sangoma E1 card patch (Sangoma A200/Remora FXO/FXS Analog AFT dual E1 card), and found the old patch from http://lists.gnumonks.org/pipermail/openbsc/2009-August/000821.html
Unfortunately it didnt help, wanpipe modules are loaded , card is working but when connecting to Siemens Bs-11 and (./bsc_hack -c bs11.conf) the following error message pops out :
DB: Database initialized.
DB: Database prepared.
mi_e1_line_update could not open socket Address family not supported by protocol
and when trying to load hfcmulti dslot=1 i get :
FATAL: Error inserting mISDN_l1 (/lib/modules/2.6.24-24-server/extra/mISDN_l1.ko): Unknown symbol in module, or unknown parameter (see dmesg)
dmesg says:
[ 3136.216408] mISDN_l1: Unknown symbol mISDN_SetHandledPID
[ 3136.216507] mISDN_l1: Unknown symbol mISDN_register
[ 3136.216573] mISDN_l1: Unknown symbol mISDN_ctrl
[ 3136.216628] mISDN_l1: Unknown symbol mISDN_debug
[ 3136.216663] mISDN_l1: Unknown symbol mISDN_module_register
[ 3136.216751] mISDN_l1: Unknown symbol mISDN_init_instance
[ 3136.216795] mISDN_l1: Unknown symbol mISDN_queue_message
[ 3136.216834] mISDN_l1: Unknown symbol mISDN_module_unregister
[ 3136.216916] mISDN_l1: Unknown symbol mISDN_getrev
[ 3136.216975] mISDN_l1: Unknown symbol mISDN_unregister
I've checked out the patch file, and there was an error in the path of the wanpipe api ---> should be /etc/wanpipe/api/legacy/aft/ ... also didnt help.
is any body using Sangoma E1 card ?
Ubuntu 8.04.3 kernel (2.6.24-24-server)
mISDN V2 + core.c patch
working asterisk setup
Best regards
Ihab el Bakri
_________________________________________________________________
Hotmail: Trusted email with powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
Hello,
Due to lack of time I have to sell my equipment:
1x Siemens BS11, GSM900, Dual-Trx
1x CologneChip HFC-E1 Board
Unit is working in this setup.
Fixed price excluding shipping: Euro 500
The Unit is located in 69436 Schönbrunn (Germany) (Heidelberg Area).
I still got the original packaging of the BS11 so shipping is possible.
(additional costs)
Regards,
Kai
hi,
two questions
> FATAL: Error inserting mISDN_l1
(/lib/modules/2.6.24-24-server/extra/mISDN_l1.ko): Unknown symbol in
module, or unknown parameter (see dmesg)
mISDN_l1 i part of mISDN version 1. why do you load it? is it because
your hfcmulti module is also version 1? just remove all extra
(mISDN-)modules and re-install mISDN.
> is any body using Sangoma E1 card ?
does it have an HFC-E1 chipset? maybe you should enable init-debugging:
modprobe hfcmulti debug=0x40000
in case it loads, see dmesg if it is detected. also do "lspci -nv" to
see device ids.
regards,
andreas
Hi!
JFYI: Zecke and myself have been playing around with the first steps towards a
layer2 of the mobile station side.
In order to reduce code duplicaiton, we have moved a lot of header files
and some code such as msgb.c, signal.c, bitvec.c and others into the library
"libosmocore" (LIBrary Open Source MObile [communications] CORE).
This library resides at git://git.osmocore.org/libosmocore.git
You will have to download, compile and install the library before you can
compile/install openbsc. This is done with the usual 'autoreconf -i &&
./configure && make' steps.
Sorry for the minor inconvenience, but we really didn't want to have code
duplication between our projects.
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)
Good news, everyone [tm]!
I am hereby publicly announcing project OsmocomBB: A Free and Open Source
software project to create a Free Software GSM baseband firmware.
The baseband chipset is the part of a mobile phone that actuall communicates
directly with the GSM network. It typically includes a DSP and a
microprocessor running some RTOS, drivers for the baseband chipset,
the GSM protocol stack and some kind of user interface.
GSM has been deployed first 19 years ago. Despite billions of phones deployed
world wide, all of them run a proprietary baseband firmware, consisting of
proprietary drivers, RTOS and GSM protocol stack.
OsmocomBB has set out to change this. We do not want our phones to be
a black box connected 24/7 to a public network. We want to decide what
kind of data our phone reveals about us or not.
The authors behind the project have already spent the last 15 months
implementing an Open Source GSM network side protocol implementation called
OpenBSC. In January 2010, they decided to go after the phone side protocol
stack - which turned into OsmocomBB.
=> What is the project status?
Right now we are at a state where we have full control over the baseband
hardware, including the DSP and ARM cores, the analog baseband chip,
the RF transceiver, keypad, LCD display and other components.
We can scan the GSM band for cells, perform FCCH detection, run automatic
gain control to synchronize to the cells carrier, detect the SCH to get
BSIC and GSM frame number, as well as dump the BCCH and CCCH of the cell.
=> What does Osmocom mean?
Open Source MObile COMmunications. It is meant as an umbrella name for
various FOSS projects related to communications, including OsmocomBB but
also including sister projects like OpenBSC.
=> Can I make phone calls yet?
No. We are currently in Rx (receive) only mode, and have no Layer2 or Layer3
implementation yet. However, the difficult parts of driving the GMS hardware
and implementing a minimal Layer1 are behind us, so we are confident to proceed
to actual phone calls during the months to come.
=> Where can I get the source?
The git repository is at git://git.osmocom.org/osmocom-bb.git
The mailing lists are at http://lists.osmocom.org/
The project homepage including wiki is at http://bb.osmocom.org/
=> What phones are supported?
We are implementing OsmocomBB as hardware-independent as possible. At the
moment, we only have drivers for the Ti Calypso Digital Baseband chip.
Our main target are the following Motorola-branded phones (made by Compal):
C115/116/117/118/119/120/121/122/123/139/140/155
Adding support for other Calypso-based phones should be relatively easy,
but porting it to a different baseband chip is a lot of work, especially
without access to good documentation.
=> How can you help?
We need developers who have experience in microcontroller development working
on an ARM7TDMI core. You do not need to know anything about GSM in order to
help us with tasks such as the UI, driving the battery charging controller,
etc. If you want to join, get yourself a phone, serial cable, join the
developer mailing list and introduce yourself!
Happy Hacking
Harald Welte
--
- 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)
Hi,
I am having some trouble installing OpenBSC on kernel 2.6.32 (Ubuntu), the actual error message:
make[2]: Entering directory `/home/bs11/openbsc/openbsc/src'
gcc -DHAVE_CONFIG_H -I. -I.. -I../include -Wall -g -O2 -MT gsm_04_11.o -MD -MP -MF .deps/gsm_04_11.Tpo -c -o gsm_04_11.o gsm_04_11.c
gsm_04_11.c:349:16: error: invalid suffix "b111" on integer constant
gsm_04_11.c:350:8: error: invalid suffix "b000" on integer constant
gsm_04_11.c:352:8: error: invalid suffix "b001" on integer constant
gsm_04_11.c:354:8: error: invalid suffix "b010" on integer constant
gsm_04_11.c:356:8: error: invalid suffix "b011" on integer constant
make[2]: *** [gsm_04_11.o] Error 1
make[2]: Leaving directory `/home/bs11/openbsc/openbsc/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/bs11/openbsc/openbsc'
make: *** [all] Error 2
any other information about connecting to the BS-11 with a sangoma E1 card will be very helpfull !
best regards
Ihab el Bakri
_________________________________________________________________
Hotmail: Powerful Free email with security by Microsoft.
https://signup.live.com/signup.aspx?id=60969
Hello,
I am working at the university of Freiburg in Germany and I am very
interested in buying some nanoBTS for a project at the computation
department.
Who has a nanoBTS (GSM1800) for sale? Depending on the price I need 3-5
units.
Regards
Konrad Meier
Hello,
I have a nanoBTS from ipaccess. I used ipaccess-config to set the
Unit-ID of the nanoBTS and also the Primary OML IP address. Everything
worked OK and OpenBSC and the nanoBTS where communicating.
My problem now is that I want to connect the nanoBTS back to my
original BSC (from Zynetix). By using ipaccess-config I set the OML IP
address back to what it was originally but the unit does not connect
to the original BSC.
I have two other nanoBTS's and their Unit-ID is 65535/255/255 before
they 'sign up' to the BSC, where they get another Unit-ID. I've tried
using ipaccess-config to set the Unit-ID to that value but get an
error: "Failure to set attribute. This seems fatal"
Does anyone know how I can reset the Unit-ID to 65535/255/255 ?
Best regards,
Bjarni S. Sigurdsson
Hi,
I'm currently implementing Early Assignment in the On Waves branch and as part
of this I will have to take care of RSL channel releases as well.
Someone else was pointing this out as well but I could not find the email. Our
channel release is a bit sloppy and I will fix it and start using T3111 and
T3109 in the rsl code for doing so.
In the "normal" case (bsc on the left, bts on the right):
RSL Channel Release -->
<- RSL Channel Release Ack
<- Release Indication SAPI=0
RSL Channel Release ->
<- RSL Channel Release Ack
In the "abnormal" case:
<- Error Indication
RSL Channel Release ->
<- RSL Channel Release Ack
<- Release Indication SAPI=0
RSL Channel Release ->
<- RSL Channel Release Ack
I'm going to change that into the following way.
"normal" case:
1.) Release the established SAPIs
2.) After their ACKs release the Channel
Have all this guarded by T3109 (or whatever is more appropriate)
"abnormal" case:
1.) Start T3109
2.) Then do the normal case.
During the shutdown sequence I need to make sure that we are not allocating
the channel again. I'm thinking of either using the chan mode Harald was
introducing while doing the hand over work, or just a "locked" flag to not
assign the channel.
I hope to be done with this by tomorrow or the day after, anyone has comments
or ideas on how to approach this?
z.
Hi,
i have problems bringing up the second TRX. I used the following procedure:
./bs11_config -p /dev/ttyUSB0 disconnect
./bs11_config -p /dev/ttyUSB0 create-trx1
After reboot the query tells me:
./bs11_config -p /dev/ttyUSB0 query
LMT LOGON: ACK
PHASE: 3 Normal MBCCU0: Load MBCCU1: Load Abis-link: Restoring
...
BS11 Power Amplifier 0 ATTRIBUTES:
TRX Power: 30mW (GSM)
LMT LOGOFF: ACK
Now i wondered where is the trx1, did anyone has a similar problem? I have the BS-11 ESN PCB Serial Number: 001127 which should have two TRX.
Greets & thx Till
--
Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 -
sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser
