Hello Everybody,
I'm just trying to connect the E-1 host card to the BS-11, but I can't
get it work. The serial connection works fine, I'm also seeing the
"Abis-link: Restoring" message.
My hardware configuration:
1) I removed the green jumpers TB01 - TB04
2) Jumper settings below the Twinax-board: 1-4 ON, 5-8 OFF
3) HFC-E1: NT Mode, Config A (all jumpers on the left side to the left)
4) 'hfcmulti' modprobed with 'dslot=1'
5) Forced the BS-11 to use correct TEI and E1 slot by using 'bs11_config'
Have I missed something? I put a scope upon the rx/tx pins - traffic
flows into both directions, so I think there's no collision (tx->tx, rx->rx)
Thanks,
Holger
Hello Holger,
On Sat, 28 Feb 2009 12:55:04 +0100, "Holger Adams" <holger(a)kernreaktor.org> wrote:
>
> OK, I think I know where the problem is - there must be a cableing
> problem with the Twinax connectors.
>
> So there is my next question:
> Which pin of Y01 is TX+ and TX-?
> Which pin of Y02 is RX+ and RX-?
The polarity does not care, you can exchange TX+ with TX- and RX+
with RX-. A simple test for just the correct wire without connection
the BS-11:
- On the cable which goes to Y01 you should be able to see a
signal with an oscilloscop between TX+ and TX-.
- If you connect the two TX lines with the two RX lines (loopback,
polarity does not care), the card should synchronise and the LEDs
should not longer blink. Attention: I have tested this on Windows
only, with a loopback, I can see that the card synchronises, however
I don't know what mISDN does, but I guess it will also synchronise.
If this works, you know that the cable is OK.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hi All!
I'll be on holidays pretty much throughout the time from March 4th through
March 25th. I will check my email only in very irregular intervals,
particularly not after March 11.
I will try to get back to any inquiries after I have returned. Meanwhile,
the list (particularly subscribers like zecke, dieter spaar, nibbler and
others) will hopefully be able to adress all issues you might have.
Regards,
--
- 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 Folks,
yesterday i´ve tried to do the initial config of my BS-11.
But i have a problem after warmup while querying the BS-11:
rene@nb-stegmaier:~/data/development/bs-11/svn/trunk/openbsc/src
$ ./bs11_config -p /dev/ttyUSB0 query
bs11_config (C) 2009 by Harald Welte and Dieter Spaar
This is FREE SOFTWARE with ABSOLUTELY NO WARRANTY
LMT LOGON: ACK
PHASE: 1 Software required Abis-link: Down
No valid Safety Load file "BTSBMC76.SWI"
PHASE: 1 Software required Abis-link: Down
No valid Safety Load file "BTSBMC76.SWI"
Whatis going wrong?
I read in the wiki that the projekt doesn't provide any firmware images,
but how can i get the BS-11 working?
Is there any way to generate this "Safety Load file" and upload it to
the BS-11?
cheers,
René
--
Rene Stegmaier <rene(a)rr47.de>
LAN-TEX
Schuberstr. 14
38518 Gifhorn
Mobil: 01703183653
Hello Everybody,
we have several Tektronix K1103 protocol analyzers standing around here
and it was quite complicated to get the pinout of the SUB-D 9 connectors.
Monitor A:
Pin Purpose
9 RX+B
4 RX-B
6 RX+A
1 RX-A
2,3,4 GND
A = E-1-Linecard -> BTS
B = BTS -> E-1-Linecard
Monitor C:
9 RX+D
5 RX-D
6 RX+C
1 RX-C
2,3,4 GND
Telephone socket:
1 mic input (-)
2 hearer output (+)
3 hearer output (-)
4 mic input (+)
Factsheet of this analyzer:
http://www2.tek.com/cmswpt/psdetails.lotr?ct=PS&lc=EN&ci=14411&cs=psu
Holger
hi!
I've put together a new page at
http://bs11-abis.gnumonks.org/trac/wiki/BS11_Getting_Started
which explains the individual steps from unpacking the BTS, verifying its
configuration using bs11_config up to connecting and getting it up and running
with a HFC-E1 Eval Board and the bsc_hack program.
Once again, feel free to add information to the wiki, I will happily provide
accounts to every user!
Regards,
--
- 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'm sending this mail to all recent buyers of a BS-11.
I would like to ask you to raise any questions you might have regarding
setup/configuration/installation of the BS-11 unit or OpenBSC at the
openbsc(a)lists.gnumonks.org
mailing list. You can subscribe to the list online at
https://lists.gnumonks.org/mailman/listinfo/openbsc
The benefit of asking your question at this list is that other BS-11 / OpenBSC
users and developers will see your questions and learn from the answers or at
some point even provide the respective answers themselves.
I would also want to invite you to contribute to our wiki at
http://bs11-abis.gnumonks.org/. We do not allow public editing, so if you
want an account, just email me privately and I will send you username and
password.
I hope we can now finally start to build a community around the project, with
some 30 BS-11 distributed to various GSM enthusiasts all over the world.
Regards,
--
- 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)
Hello,
Does anyone has a sample database to test the hlrstat.pl script against ?
I am specifically after the subscriber database.
Best regards,
Abdul Hakeem
Hi!
Some of you have already received their BS-11 and built the power cord for it.
Next step is to obviously try bs11_config on the serial port. Unfortunately
it doesn't build right now since I restructured some shared code. I'll work
on this tonight, should be fixed soon.
--
- 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 David,
hope you don't mind me Cc'in the list, as other people might find this
information useful.
On Tue, Feb 17, 2009 at 08:31:53PM -0800, David A. Burgess wrote:
> Congratulations!!
thanks!
> So if you need the channel mode modify, does that mean you're doing very
> early assignment?
yes, it is the most simple option. commit the TCH early and you don't have to
do conflict resolval in the middle of the call setup if you first only have a
SDCCH and then want to switch to a TCH but don't have a free one.
> It took me a few days to figure that out when I decided to try very early
> assignment.
I was pretty clear that I have to do CHANNEL MODE MODIFY on GSM 04.08 to tell
the MS to switch to voice mode.
However, what is a bit weird is that in addition you have to send a MODE MODIFY
REQUEST (08.58) packet to the BTS. Plus, the actual channel mode values for
EFR are different on 04.08 and 08.58 ;)
Why is it weird? Because typically in a case like this, you would send one
08.58 packet to the BTS, with the payload for the 04.08 packet. The BTS would
then do the local state change, and send the 04.08 packet over the air to cause
the MS state change. This is how it works with many other operations, you
almost never have to explicitly talk to both sides separately.
> For early or late assignment, started call setup on the SDCCH, I didn't
> need that channel mode modify step.
I was aware of that, but then you need another channel assignment and a more
complex resource management, at least that's what I think. So I went for very
early assingment for now.
> Are you transcoding, or just copying raw vocoder frames from TCH to TCH?
No, I'm not transcoding. But in order to route TRAU frames from one TCH to the
other, you already need to do quite a bit of parsing and re-encoding. It's
just how they stuff the bits in the TRAU frames, not actually touching any of
the voice processing.
I think what is useful is to 'outsource' this TRAU frame processing into a
separate process. Apart from simple commands like 'map this sub-channel to
another sub-channel' it doesn't need much interaction with the actual
signalling part. In fact, the relatively high data rates clog the debug log
and make it hard to strace OpenBSC for further work on the signalling side.
On the ip.access nanoBTS it's even easier. You can directly feed the RTP
streams over the loopback device on the BTS, so the voice data naver even has
to go to the BTS (unless you want to route between multiple BTS, which I haven't
done yet but is very easy with nanoBTS too, in fact the code _should_ already
work.
What will be interesting is to figure out the actual RTP payload of the
ip.access. I've already seen they use RTP payload type 127 and the size of the
packets looks like it is one 40-byte TRAU frame per RTP packet. If that is
true, I would probably work on E1-to-RTP interworking to route calls between
traditional E1-based BTS and IP-based ones.
Cheers,
--
- 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)
