On Sat, Jan 25, 2014 at 2:57 AM, Andreas Eversberg <andreas(a)eversberg.eu> wrote:
> so when i stop sending the bursts, the filler table will continue to
> transmit bursts. do i understand it correctly: if i send a single idle burst
> (frame??) after sending bursts, the filler table is disabled until new
> bursts are sent?
Sorry, I misspoke about disabling transmission. The filler table
resends the last burst in the multiframe, so the idle burst is usually
just a dummy burst, which does not actually stop physical
transmission. To fully turn off the downlink signal on a particular
slot requires disabling the slot by the channel combination.
That said, I agree with Alexander that the retransmission portion of
the filler table should be turned off because the behavior is
incorrect. With a few exceptions (e.g. FCCH), bursts should *not* be
retransmitted at L1 and doing so generates an invalid signal.
Note that the filler table cannot be completely disabled because it is
part of the real-time loop that drives the device I/O. If the upper
layer does not send a burst for a particular slot, or that burst
arrives late (stale burst), something still must be transmitted.
Currently, in that case, the burst comes from the filler table if the
slot is active or zeros if the slot is turned off. Again, I do not
think the current implementation is entirely correct, but that depends
on expectations of the upper layers.
-TT
Hello,
I have found a couple bugs in the read callback of smpp_smsc.c with regards to
guarding against malformed packets.
Please see attached patches for fixes. They are also published in openbsc branch
daniel/smpp-fixes
Regarding the last fix I don't think it is necessary to receive messages up to
SSIZE_MAX, but since I don't have/know a value for the maximum sensible size I
left it like that for now.
Regards,
Daniel
--
- Daniel Willmann <dwillmann(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Schivelbeiner Str. 5
* 10439 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte
Hi Guys,
I just wanted to ask a few questions about packet data
availability/support, because I did not find the specifics on the
site.
1. Is there a working GPRS/EDGE implementation in the moment? If not,
what is the plan or the state of the development process?
2. Which hardware should I buy, if I want to play with GPRS/EDGE? I am
thinking about USRP or BladeRF, but maybe there is a better
alternative. I am willing to spend more in order to get a more
future proof unit (for example: to have a unit which is capable of
doing EDGE if and when it is going to be supported).
3. This is not related to packet data. I wonder if I buy a USRP unit
, it is possible to configure and use one USRP device with more than one TRX?
In general, I think a lot of people are interested in packet data and
OpenBSC/OpenBTS, it would be nice to clarify these informations on the
site.
BR,
Csaba
Dear Ivan,
I noticed that you added a lot of commands to query counters. When
we are designing the interface we made sure to add wildcard commands.
So most counters can be already read without adding a special command
for that.
holger
Hi Thomas,
I'm moving this discussion to the OpenBSC mailing list, as it has
nothing to do with UmTRX, but rather with OsmoTRX.
On Sat, Jan 25, 2014 at 11:36 AM, Tom Tsou <tom(a)tsou.cc> wrote:
> On Sat, Jan 25, 2014 at 1:22 AM, Andreas Eversberg <andreas(a)eversberg.eu> wrote:
>> once a channel was activeated,
>> there will be RF power on the specific TS, even when osmo-bts does not send
>> bursts anymore. i guess that some filler table of osmo-trx causes it. i
>> think it would be nice if osmo-trx would stop transmitting, when there are
>> no more bursts comming from osmo-bts. (at least after a while.)
>
> Yes, this is the behaviour of the filler table, which will resend the
> previous frame until a new frame arrives. Sending an idle frame will
> disable output, which is how the filler table is managed in OpenBTS.
> You can disable the filler table with this patch.
Could you make this configurable from the command line or from the
socket control interface?
I believe we should leave filler table as the default option, but
allow one to disable it when OsmoTRX is used with OsmoBTS.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hello,
When following the network_from_scratch instructions with a Linaro
Ubuntu 12.11 host, I encountered a build error when it came to
OsmoBTS:
linaro-ubuntu-desktop:~/osmocom/osmo-bts> make
Making all in include
make[1]: Entering directory `/home/linaro/osmocom/osmo-bts/include'
Making all in osmo-bts
make[2]: Entering directory `/home/linaro/osmocom/osmo-bts/include/osmo-bts'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linaro/osmocom/osmo-bts/include/osmo-bts'
make[2]: Entering directory `/home/linaro/osmocom/osmo-bts/include'
make[2]: Nothing to be done for `all-am'.
make[2]: Leaving directory `/home/linaro/osmocom/osmo-bts/include'
make[1]: Leaving directory `/home/linaro/osmocom/osmo-bts/include'
Making all in src
make[1]: Entering directory `/home/linaro/osmocom/osmo-bts/src'
Making all in common
make[2]: Entering directory `/home/linaro/osmocom/osmo-bts/src/common'
CC gsm_data_shared.o
CC sysinfo.o
CC logging.o
CC abis.o
abis.c: In function ‘abis_sock_cb’:
abis.c:360:2: warning: #warning HACK [-Wcpp]
CC oml.o
oml.c: In function ‘rx_oml_ipa_rsl_connect’:
oml.c:1049:17: warning: assignment from incompatible pointer type
[enabled by default]
oml.c:1053:2: warning: passing argument 1 of ‘abis_open’ from
incompatible pointer type [enabled by default]
../../include/osmo-bts/abis.h:35:5: note: expected ‘struct ipabis_link
*’ but argument is of type ‘struct e1inp_sign_link *’
CC bts.o
CC rsl.o
rsl.c:140:2: warning: #warning merge lchan_lookup with OpenBSC [-Wcpp]
rsl.c: In function ‘get_rsl_local_ip’:
rsl.c:1265:32: error: ‘struct e1inp_sign_link’ has no member named ‘bfd’
rsl.c: In function ‘rsl_rx_ipac_XXcx’:
rsl.c:1398:5: warning: initialization from incompatible pointer type
[enabled by default]
make[2]: *** [rsl.o] Error 1
make[2]: Leaving directory `/home/linaro/osmocom/osmo-bts/src/common'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/linaro/osmocom/osmo-bts/src'
make: *** [all-recursive] Error 1
linaro-ubuntu-desktop:~/osmocom/osmo-bts>
This was resolved by building from branch jolly/trx_rebased instead of
jolly/trx. Should we now be using the rebased branch? If so I will
update the wiki.
Regards,
Andrew
--
Andrew Back
http://carrierdetect.com
Again, I can't speak to the USRP or BladeRF. OpenBTS is a completely
different project with a completely different scope. The projects share
very little of a common code base therefore I would consider it
incompatible as architecturally they are night and day. OpenBTS is a hack
of GSM protocol while OpenBSC is a emulation of the GSM/GPRS mobile network
infrastructure.
If I had to recommend available compatible hardware, I would suggest
community based hardware like Harald's own sysmoBTS or Alexander's UmTRX.
On Thu, Jan 23, 2014 at 9:37 AM, Sipos Csaba <dchardware(a)gmail.com> wrote:
> Hi Don,
>
>
> Thanks for the answer.
>
>
> THe problem with nanobts that it is unaccessible, and even when it turns
> up on ebay, it costs a fortune.
>
>
> I'd rather pay that fortune for an USRP or half that fortune for a
> bladerf, and I will have an SDR which I can use not only as a BTS.
>
>
> So, at the moment GPRS/EDGE is only possible with nanoBTS? What about USRP
> or BladeRF running OpenBTS?
>
>
> BR,
>
> Csaba
>
>
>
> There has been a working GPRS stack for a while now:
>
> http://openbsc.osmocom.org/trac/wiki/OpenBSC_GPRS
>
>
> As for USRP or OpenBTS, I cannot comment upon having never used either
> platform.
>