>You would have to talk to the manufacturer and its distributors about
>this. I have no commercial or other relationship with the manufacturer.
I myself tried this route as I'm a student looking for an inexpensive
way to work with OpenBSC, but...
1: they require a mutual shared NDA before they'll even talk prices;
2: they claim it REQUIRES their proprietary BSC software and thus you
must purchase a femtocell developer kit including their A-bis specs
and a bunch of stuff you don't need, inflating the price; and
3: they only offer their NDA to companies -- individuals and students
need not apply.
4: ... but they DO ship internationally -- GSM1800 only.
But looking at the /only/ price they mention - $7200 US for two
femtocells and all the software -- why bother? You're better off
buying two, maybe three NanoBTS for that price.
And I also seem to question my own point #2 -- they first tell me "If
you do want to use the HSL Femtocell with an alternative to the HSL
BSC..." and then in the latest mail "... our femtocell is designed to
be used with our own BSC" making it seem as if you're not supposed to
be taking it elsewhere.
Le sigh.
-DC
Hi all,
I have moved the cellmgr_ng code to GNU AGPLv3 as well. I am going to land
M2UA code, a simple STP tomorrow and also the linkset cleanups I have been doing.
Hi,
Found a perl (!) SIGTRAN stack on the net, thought someone here might be
interested. Includes a very basic HLR emulator and various other bits. Looks
fairly easy to extend to send/respond to various GSM MAP messages, could be
useful for testing.
http://mtve.livejournal.com/13725.htmlhttp://frox25.no-ip.org/~mtve/wiki/SigTranSol.html
Enjoy!
Duncan
Hi all,
the cellmgr_ng code has gained M2UA handling and is on the way that it could
play the classic role of a Media Gateway (MGW) as of RFC3331, or a plain
Signalling Transfer Point.
Is someone interested in helping to finish that up and using it somewhere?
regards
holger
Hi!
The 'preferred' address for the openbsc mailinglist has changed to
openbsc(a)lists.osmocom.org and http://lists.osmocom.org/
However, since the latter is just a virtual instance on the same list server,
the old addresses will continue to work.
Please note, though, the 'List-Id' header will change the doamin name, so you
may have to update your message filter scripts.
Sorry for any inconvenience, but I'm just making sure all the GSM network
related projects are on osmocom.org (like the recent git repository move).
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
im still trying to make 2 bts work in multidrop mode. bts0, the one on
the pc, tells that:
LMT LOGON: ACK
PHASE: 3 Normal MBCCU0: Load MBCCU1: No Load
Abis-link: Restoring
BS11 ATTRIBUTES:
BS-11 ESN PCB Serial Number: 001104
BS-11 ESN Hardware Code Number: 135-2044/03.07
BS-11 ESN Firmware Code Number: 135-2044/03.07
PLL Set Value=1006, Work Value=1038
SITE MANAGER ATTRIBUTES:
E1 Channel: Port=0 Timeslot=1 (Full Slot)
TEI: 25
BS11 Line Interface ATTRIBUTES:
PLL Mode: Standalone
BS11 CCLK ATTRIBUTES:
CCLK Accuracy: High (1)
CCLK Type=0
BS11 Power Amplifier 0 ATTRIBUTES:
TRX Power: 30mW (GSM)
BPORT0 ATTRIBUTES:
Line Configuration: Multi-Drop (1)
BPORT1 ATTRIBUTES:
Line Configuration: Multi-Drop (1)
LMT LOGOFF: ACK
this bs11 works pretty well as single config.
but bts1 tells that:
LMT LOGON: ACK
PHASE: 3 Normal MBCCU0: No Load MBCCU1: Load
Abis-link: Restoring
BS11 ATTRIBUTES:
BS-11 ESN PCB Serial Number: 001111
BS-11 ESN Hardware Code Number: 135-2044/03.03
BS-11 ESN Firmware Code Number: 135-2044/03.03
PLL Set Value=1042, Work Value=1221
SITE MANAGER ATTRIBUTES:
E1 Channel: Port=1 Timeslot=17 (Full Slot)
TEI: 25
BS11 Line Interface ATTRIBUTES:
PLL Mode: Standalone
BS11 CCLK ATTRIBUTES:
CCLK Accuracy: Medium (0)
CCLK Type=0
BS11 Power Amplifier 0 ATTRIBUTES:
TRX Power: 2W (GSM)
BPORT0 ATTRIBUTES:
Line Configuration: Star (0)
BPORT1 GET ATTR NACK
LMT LOGOFF: ACK
as you can see, i configured the 2nd bs11 with ts 17 on port 1,
according the bmask and dmask settings(sorry for that yesterday, but
sometimes there are so many trees you dont see the forest - german
saying), and bsc_hack starts now without problems, but bootstrapping is
only on bts0, bts1 isnt recognised.
when i connect bts1 to the pc and run it in single mode(with line 1
timeslot 17 settings in openbsc.cfg), it is recogised with
bootstrapping, but dont function. it isnt seen by any handy. i put 2
attachments in the mail, hope they arent dropped
could the different pll and work values be the reason?
is the BPORT1 GET ATTR NACK from bts1 a possible reason?
what about the strange messages seen in the bts1_err.jpg?
T.
--
Wer Rechtschreibfehler findet, darf sie behalten!
Hi all!
Since more people are currently looking into using OsmoSGSN, let me write
down some technical notes on its current status:
NS (08.16) implementation (BSS and SGSN side)
* complete + stable
* supports NS/UDP/IP and NS/FR/GRE/IP stacking
BSSGP (08.18) implementation
* no support for per-BSS/per-MS flow control yet, this is WIP
* otherwise complete and stable
LLC (04.64) implementation, network side
* No support for Async Balanced Mode (ABM), as to the best of
my knowledge, it is not used if IP is transported over GPRS
* Encryption stub functionality using external plugins for actual
GEA encryption. GEA3 reference code is published, but we cannot
redistribute it
* No full support for the XID mechanism yet
SNDCP (04.65) implementation
* Fragmentation/defragmentation implenented but not widely tested
* No full support for the XID mechanism yet
* No support for any of the header compression formats
* is optional anyway, but helps performance
* No support for V.42bis payload compression
* is optional anyway, but helps performance
GPRS Mobility Management (04.08) implementation
* Supports GPRS ATTACH, RA UPDATE
* Known bugs with inter-cell hand-over
* No access to HLR yet, i.e. all MS are permitted to enter
* No persistent storage of MM state, i.e. all state is lost
if process crashes or restart
* We don't yet work around a fairly common MS bug which makes
them try to do GPRS RA UPD without ever sending GPRS ATTACH first
GPRS Session Management (04.08) implementation
* Supports only one PDP Context per MS so far
* Only IPv4, no IPv6 contexts yet
* No persistent storage of active PDP contexts, i.e. all state
is lost if process crashes or restarts
* only supports one APN, routed to one single GGSN
The TODO list in order of priority is:
* Implement BSSGP flow control (per BSS and per MS)
* Fix MM state machine issues, make sure inter-cell hand-over of GPRS works
* Add access from SGSN to HLR (possibly using libosmo-{tcap,map}, maybe again
a quick sqlite database hack meanwhile
* Verify encrpytion support in LLC code
* Work on header/payload compression
I don't have a precise schedule yet for it. Anyone who wants to work on those
issues is of course much welcome.
Meanwhile, if you experience problems with GPRS, please take pcap files of
the A-bis, Gb and GTP links and send them to me, with a detailed description
of what goes wrong when. I'm happy to look at those issues and resolve them,
if I get sufficiently verbose bug reports.
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)
Hi!
Today I've done the first push of the 'laforge/hsl' branch, an attempt
to support the HSL 2.75G Femtocell from OpenBSC.
It is far from being complete, but you can get the BTS to start up
on the right ARFCN and process location area updates and other signalling
traffic. Voice support is still being worked on.
To give you a quick overview of what you are dealing with:
== Hardware ==
* Ti DaVinci TMS320DM6443A (ARM9 CPU + DSP)
* Xilinx Spartan-3A FPGA (XC3SD1800A)
* 128 MByte DDR-2 RAM
* 128 MByte NAND flash
* Realtek RTL8201 Ethernet MAC
* Dual 12-bit 65Ms/sec ADC (ADS5232)
* Dual 14-bit 275Ms/sec DAC (DAC5672)
As you can see, the hardware is _much_ more powerful than you would ever
need for a simple single-ARFCN femtocell. Using the high-speed DAC/ADC,
the combined power of the FPGA (with DSP slices) and DSP, you can probably
expect that they will at least want to do multi-ARFCN (if not 3G) on the
same hardware at some later point.
== Protocol ==
They use an odd down-sized minimalistic dialect of the ip.access Abis/IP.
=== ACS ===
Prior to connecting to the BSC, the cell downloads its current configuration
via https, using a HTTP POST of its serial number.
=== IPA layer ===
The IPA multiplex layer does not have PING/PONG keepalives, and it does
not do the ID_GET/ID_RESP/ID_CONF identification with the Unit ID.
Furthermore, both OML and RSL are encapsulated in the same TCP connection.
Stream identifier 0xDD is used for passing string debug messages from the
BTS to the BSC.
Neither OML nor RSL are implemented fully, as per 12.21 / 08.58
=== RSL ===
It seems to have a very 'creative' interpretation of the RSL specification. Some examples:
* use of SACCH INFO MODIFY instead of SACCH FILLING for default SI5/SI6
* it forgets to send RSL CHAN REL ACK on TS1...7
* it does not implement RSL CHAN MODIFY
* it seems to be unable to run without DTX
* it often detects RACH requests where there are none (!)
=== OML ===
OML is almost not present at all. Only software download and setting of
ARFCN + BSIC are supported. No managed objects, no state transitions, no
software activation procedures/events at all.
The configuration of each timeslot seems to happen 'on demand', i.e.
there are no OML commands to configure the timeslots, but it depends on your
RSL CHAN ACT whether a timeslot will become a TCH/H or TCH/F.
I have not managed to use a SDCCH/8 anywhere, just TCH/F and TCH/H as well as
SDCCH/4.
The BCCH _claims_ to be a Combination 4, but in reality it is a Combination 5
(i.e. including the SDCCH/4)
=== GPRS ===
GPRS is quiite odd, too. The BSSGP is encapsulated in the RSL L3_INFO_IE,
this means we will have to run a NS link from the BSC to the SGSN, combining
all the BSSGP links from HSL Femtocells to the BSC.
--
- 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)
Dear Holger,
Yes , I found two 1 location update reject and one location update accept .is this abis oml ?
Thanks,
Omar
------Original Message------
From: Holger Hans Peter Freyther
Sender: openbsc-bounces(a)lists.gnumonks.org
To: openbsc(a)lists.gnumonks.org
Subject: Re: Adding patches to wireshark...
Sent: Jan 11, 2011 11:37 PM
On 01/11/2011 09:08 PM, Omar Atia wrote:
> Thanks It is clear for me !! just send me 1 pcap file to open it with the
> patched wireshark
Hmm, who do you address with this request? Have you attempted to search for
'pcap' in the OpenBSC wiki?
Sent via BlackBerry® from mtc touch
hi all,
the misdn driver is nice configured now(dmask=0x00020002,
bmask=0x0000fffc,0xfffc0000), but i get the error message "could not
bind l2 socket Invalid argument". the full output is:
2 devices found
id: 0
Dprotocols: 00000018
Bprotocols: 0000000e
protocol: 4
nrbchan: 14
name: hfc-e1.1-1
activate bchan
activate bchan
2 devices found
id: 1
Dprotocols: 00000018
Bprotocols: 0000000e
protocol: 4
nrbchan: 14
name: hfc-e1.1-2
could not bind l2 socket Invalid argument
bts1 (connected to the pc) is configured port 0 ts 1 tei 25 in multidrop
config
bts2 is configured port 1 ts 6 tei 26 in line config
any ideas?
--
Wer Rechtschreibfehler findet, darf sie behalten!
