Hi!
Today I've been working on improving + cleaning up the DAHDI work that
had been done last year by Xavier Carcelle and Matthew Fredrickson, which in
turn uses some simplistic LAPD implementation by Oystein Homelien.
It now seems to be working fine, at least for my TE110P card and a BS-11
in 2-TRX configuration. Haven't tried multi-drop yet.
All you need to do is to
* make sure your dahdi/user.h is found in the include path
* build openbsc
* configure your /etc/dahdi/system.conf according to your T1/E1 physical
setup
* check that dahdi_tool shows no Alarms for the physical line
* use e.g. openbsc.cfg.1-1 as sample and change 'e1_line 0 driver misdn' to
'e1_line 0 driver dahdi'
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)
Notice to all OpenBSC users with mISDN / BS-11:
I've had to introduce some new config file statements in order for the
upcoming DAHDI support.
This means if you update beyond git revision
3016d9f299ea4cfc8961376d20862b9418cfb059, openbsc will not start with
an old 'openbsc.cfg' file.
You will have to add the following two lines to make it work again
(like shonw in the new openbsc.cfg.1-1):
==============
e1_input
e1_line 0 driver misdn
==============
Sorry for that inconvenience.
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)
Hello all,
I am trying to implement a bluetooth RSAP daemon for the iPhone platform.
I read your description on http://openbsc.osmocom.org/trac/wiki/A5_GSM_AT_tricks .
Unfortunately it does not seem to work on my phone.
It always returns error code 0x6E00 for class 0xA0 (GSM application) commands:
> AT+CSIM=14,"A0A40000023F00"
> +CSIM: 4,"6E00"
Which iPhone version and "baseband" firmware was used when doing these
experiments? Any further tips?
By the way, it is better to use one of the virtual serial lines,
e.g. /dev/dlci.spi-baseband.extra_13 to access the X-Gold 608 when doing normal
stuff rather than using the real UART interfaces (/dev/tty.debug etc.) because
one does not need to unload CommCenter to have a reliable connection.
--j
--
Jens David, DG1KJD
jens.david(a)jens-david-consulting.com
http://www.jens-david-consulting.com
Hello everybody,
after setting up a nanoBTS with OpenBSC/SGSN/GGSN,
I had some troubles trying to connect my smartphone
to the GPRS cell.
Investigating the BTS-to-SGSN traffic, I saw that the
frames sent by the SGSN were all marked with the same
N(U) value (at LLC layer), the value was 0.
With some debug, I found that the there was a mismatch
in the TLLI storage, used to keep the status of attached
terminals.
The mentioned code is contained in gprs_llc.c, involving
LL Entity functions and gprs_llc_tx_ui().
/* look-up or create the LL Entity for this (TLLI, SAPI) tuple
*/ lle = lle_by_tlli_sapi(msgb_tlli(msg), sapi);
if (!lle) {
struct gprs_llc_llme *llme;
LOGP(DLLC, LOGL_ERROR, "LLC TX: unknown TLLI 0x%08x, "
"creating LLME on the fly\n", msgb_tlli(msg));
llme = llme_alloc(msgb_tlli(msg));
lle = &llme->lle[sapi];
}
The TX function uses the previously received TLLI to
lookup for the LLE. The lle_by_tlli_sapi() performs the
search, but preliminary it applies a foreign2local TLLI
conversion to ensure to have a local one.
Since no valid entry for the searched TLLI is found,
a new one is created. And the problem is here.
The new entry has the foreign TLLI.
Next time the lookup fails again, and a new entry is created.
This way, the counter N(U) is always reset, and the
mobile do not recognize the message sequence and no attach
is possible.
My question is about foreign and local TLLIs.
I patched the lookup, avoiding the conversion, so that the
LLE is found and everything works fine... but...
What is the sense of the conversion?
Should the TLLI be always stored as a local one?
Can this problem be solved with another foreign2local
while allocating new entries?
Actually, my problem has been solved with that workaround.
But I'm curious to know what is the right way.
Hope somebody can answer :)
Thanks.
Cheers,
LM
Hello Holger,
On Wed, 02 Feb 2011 12:40:13 +0100, "Holger Hans Peter Freyther" <holger(a)freyther.de> wrote:
>
> OpenBSC does not support data calls. You could start implementing it though,
> we should have all the enum values and structs that you need to send the right
> messages to the MS.
You mean CSD ? Then its most certainly also necessary to implement RLP
(Radio Link Protocol) which is the protocol used for non-transparent
CSD. At least I did not manage yet to get a reliable CSD connection
between two phones by just connecting the data traffic between them
(I tried transparent and non-transparent modes).
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
hi list,
have to sync one of my bs-11. got the hfc-s card and soldered the 2
wires.
is any driver needed for the hfc-s?
or is the clock always on c4io and f0io once the card is plugged in?
the hfcmulti driver loads the e1 card, i have a bmask and a dmask
parameter in modprobe.conf. should i remove them or just hang on the
"type=0x00800"?
i have only one try, so i want to clear all possible problems before
T.
--
Wer Rechtschreibfehler findet, darf sie behalten!
Hi,
Can You please help me how to setup a session - packet or CS call session and capture trace messages - protocol traces , Alarms, Performance Management Counters and CDR?
It will be very kind of you if you help me in this issue.
Regards,
Piyush
Please do not print this email unless it is absolutely necessary.
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
www.wipro.com
This Femtocell looks both from a pricing point of view as from a hardware
point of view very interesting. Now that the integration in OpenBSC looks
very promising it would become a good alternative for the more expensive
ip.access picocells. It seems that these HSL femtocell can not be bought
without first investing in the developers pack from HSL which cost as much
as 7000$. Does anyone know how to obtain one of these cells for a
reasonable price? Are they already deployed by operators?
Looking at the internal hardware, it may even become a substitute for the
USRP's....
