> I don't understand. This callback will be called with data you need to
write
> to the network. In case of MTP Level3 you will need to wrap that around
the
> msgb you got.
I means: is the interaction with mtp3 layer implemented (is sending sccp
data by mtp3 implemented by the library?)?
Also, what about the reception of data from mtp3 layer. is that implemented
in the sccp lib.
I am asking these questions because I see the code of mtp3 in the lib but no
significant call is present in the sccp part of the lib.
Thank you for your help.
On Tue, Jun 28, 2016 at 10:05:28AM +0200, Harald Welte wrote:
> [translated from german]
> is it certain that we switch a channel to PDCH only when
> gprs mode != none?
A TS can be GSM_PCHAN_TCH_F_PDCH; those are the only ones for which we
send a PDCH ACT message.
We send a PDCH ACT message
- during init (CHANNEL OML's state changed to enabled -> send PDCH ACT),
- and upon channel release ack when pchan == GSM_PCHAN_TCH_F_PDCH.
So the question is, when we receive a channel release ack, could that be
the PDCH release and we switch PDCH right back on by accident? No, because
we only receive a chan rel ack when the *TCH/F* is being released.
That is because the PDCH release is initiated "internally" from the PDCH
DEACT, and thus this condition in common/rsl.c rsl_tx_rf_rel_ack() catches
on, which existed before dyn PDCH:
if (lchan->rel_act_kind != LCHAN_REL_ACT_RSL) {
LOGP(DRSL, LOGL_NOTICE, "%s not sending REL ACK\n",
gsm_lchan_name(lchan));
return 0;
}
In rsl_rx_rf_chan_rel() the rel_act_kind is set to LCHAN_REL_ACT_RSL, but
not in the rsl_rx_dyn_pdch().
This is analogous to the ip.access way -- the ip.access nanobts replies to
a PDCH DEACT with a PDCH DEACT ACK and doesn't send a separate channel
release ack.
Maybe we could set rel_act_kind to some new LCHAN_REL_ACT_IPAC_DYN_PDCH
for clarity? (But we shouldn't actually send a release ack, to stay
compatible.)
Even though it works as-is, we should indeed add another flag check:
- We do check the flags that no ACT/DEACT is already pending;
- And we do send a PDCH DEACT only if ts->flags & TS_F_PDCH_ACTIVE;
- But we would send a PDCH ACT despite ts->flags & TS_F_PDCH_ACTIVE.
This should never happen, but it would make sense to ensure that.
~Neels
Hi,
My name is Brackley Cassinga Form DRC, we run a community network called
pamoja net where we offer gsm services using osmocom open source software
and OC Base station.
Recently I have tried to install another base station as the same installed
but I could not find any resource guiding through all the steps to take to
run NIB on a base station.
I'm currently running Ubuntu and I will appreciate if you could guide me on
the installation of BSC,hlr,MSC , in order to run a basic gsm network.
Thank you. Regards
--
*Ir Brackley heshima Casinga **Pacifique*
*CEO and Founder of kwanzatechnologie*
KwanzaTechnologies ,GlobalElectronics
+243977265291 | +243977265291 | Pcassinga(a)gmail.com/
brackley(a)ensemblepourladifference.org
www.kwantechnologies.jimdosite.com <http://www.kwantechnologies.com/> |
Skype: Brackley cassinga <https://webapp.wisestamp.com/#>
Av Semliki N 43
Hi all,
What are the plans to expand support for new SDR devices?
When I check the contents of osmo-trx/Transceiver52M/device/ on the git
master I see the supported lms, uhd and usrp1 devices. For example the XTRX
SDR was presented at OsmoDevCon 2018. I expected it to be included in the
master soon. At this point I see its addition in the fairwaves /
libxtrx-wip branch from 2018. That doesn't give me much encouragement for
my next question.
Would it be possible to add support for PCIe SDR from Amarisoft?
Some information about SDR is here
https://discourse.myriadrf.org/t/amarisoft-sdr-integration-with-oai/2288
Based on the
https://media.ccc.de/v/osmocon2018-82-osmotrx-status-support-for-more-drive…
I tried to create support by myself. I've gotten into a state that some MS
with weak requirements for signal quality and timing can connect. My branch
is here https://github.com/XK1ZU/osmo-trx/tree/PCIeSDR-LMSstyle
gr-osmosdr support is here
https://github.com/XK1ZU/gr-osmosdr/commits/PCIeSDR
This osmo-trx is able to run for a few tens of seconds then it quits and I
have to restart it, so I would need a deeper understanding of the timing
and scheduling of processes within osmo-trx. Who should be a clock master
SW stack or SDR device?
I see a lot of log error messages as
0000> Transceiver.cpp:422 [tid=140137319651072][chan=0] dumping STALE burst
in TRX->SDR interface (1:1408722 vs 7:1408723), retrans=0
<0000> Transceiver.cpp:1122 [tid=140137311258368] ClockInterface: sending
IND CLOCK 1408899
or
0000> Transceiver.cpp:280 [tid=140137328043776] Starting the transceiver
<0000> radioInterface.cpp:181 [tid=140137328043776] Starting radio device
<0000> PCIESDRDevice.cpp:199 [tid=140137328043776] PCIESDRDevice::start
<0000> PCIESDRDevice.cpp:205 [tid=140137328043776] starting PCIeSDR...,
sample rate:1.08333e+06
<0000> PCIESDRDevice.cpp:234 [tid=140137328043776] PCIESDRDevice::flush
<0000> PCIESDRDevice.cpp:219 [tid=140137328043776] msdr_start ok:
<0000> PCIESDRDevice.cpp:532 [tid=140137328043776] Update Alignment
<0000> PCIESDRDevice.cpp:532 [tid=140137328043776] Update Alignment
<0000> radioInterface.cpp:202 [tid=140137328043776] Radio started
<0000> Threads.cpp:119 [tid=140137294472960] Thread 140137294472960 (task
18522) set name: TxLower
<0000> Threads.cpp:119 [tid=140137311258368] Thread 140137311258368 (task
18524) set name: RxUpper0
<0001> Transceiver.cpp:923 [tid=140137328043776][chan=0] response is 'RSP
POWERON 0'
<0000> Threads.cpp:119 [tid=140137302865664] Thread 140137302865664 (task
18523) set name: RxLower
<0002> PCIESDRDevice.cpp:363 [tid=140137302865664] rc < 0
<0002> PCIESDRDevice.cpp:364 [tid=140137302865664] Sample buffer: Requested
timestamp is not valid
<0000> Threads.cpp:119 [tid=140137319651072] Thread 140137319651072 (task
18525) set name: TxUpper0
<0002> PCIESDRDevice.cpp:365 [tid=140137302865664] timestamp = 10960,
length = 262144, time_start = 6765960, time_end = 6766960, data_start =
223320, data_end = 224320
<0002> PCIESDRDevice.cpp:482 [tid=140137294472960] tx_underflow_count:3
rx_overflow_count:0
<0002> PCIESDRDevice.cpp:491 [tid=140137294472960] PCIeSDR: tx underrun
ts_tmp:10976 ts:10960 hwts:6762040
<0000> radioInterface.cpp:334 [tid=140137302865664] Receive error 0
<0000> Transceiver.cpp:1162 [tid=140137302865664] Something went wrong in
thread RxLower, requesting stop
<0002> PCIESDRDevice.cpp:482 [tid=140137294472960] tx_underflow_count:4
rx_overflow_count:0
<0002> PCIESDRDevice.cpp:491 [tid=140137294472960] PCIeSDR: tx underrun
ts_tmp:13476 ts:13460 hwts:6762278
<0001> Transceiver.cpp:778 [tid=140137328043776][chan=0] command is
'SETRXGAIN 40'
<0000> PCIESDRDevice.cpp:318 [tid=140137328043776] Setting RX gain to 40 dB.
<0001> Transceiver.cpp:923 [tid=140137328043776][chan=0] response is 'RSP
SETRXGAIN 0 40'
<0001> Transceiver.cpp:778 [tid=140137328043776][chan=0] command is
'SETPOWER 0'
<0000> PCIESDRDevice.cpp:297 [tid=140137328043776] Setting TX gain to 60
dB. device:0x1f6e0e0 chan:0
<0001> Transceiver.cpp:923 [tid=140137328043776][chan=0] response is 'RSP
SETPOWER 0 0'
<0001> Transceiver.cpp:778 [tid=140137328043776][chan=0] command is
'SETSLOT 0 5'
<0001> Transceiver.cpp:923 [tid=140137328043776][chan=0] response is 'RSP
SETSLOT 0 0 5'
<0001> Transceiver.cpp:778 [tid=140137328043776][chan=0] command is
'SETSLOT 1 7'
<0001> Transceiver.cpp:923 [tid=140137328043776][chan=0] response is 'RSP
SETSLOT 0 1 7'
<0001> Transceiver.cpp:778 [tid=140137328043776][chan=0] command is
'SETSLOT 2 13'
<0001> Transceiver.cpp:923 [tid=140137328043776][chan=0] response is 'RSP
SETSLOT 0 2 13'
<0001> Transceiver.cpp:778 [tid=140137328043776][chan=0] command is
'SETSLOT 3 13'
<0001> Transceiver.cpp:923 [tid=140137328043776][chan=0] response is 'RSP
SETSLOT 0 3 13'
<0001> Transceiver.cpp:778 [tid=140137328043776][chan=0] command is
'SETSLOT 4 13'
<0001> Transceiver.cpp:923 [tid=140137328043776][chan=0] response is 'RSP
SETSLOT 0 4 13'
<0001> Transceiver.cpp:778 [tid=140137328043776][chan=0] command is
'SETSLOT 5 8'
<0001> Transceiver.cpp:923 [tid=140137328043776][chan=0] response is 'RSP
SETSLOT 0 5 8'
<0001> Transceiver.cpp:778 [tid=140137328043776][chan=0] command is
'SETSLOT 6 8'
<0001> Transceiver.cpp:923 [tid=140137328043776][chan=0] response is 'RSP
SETSLOT 0 6 8'
<0001> Transceiver.cpp:778 [tid=140137328043776][chan=0] command is
'SETSLOT 5 13'
<0001> Transceiver.cpp:923 [tid=140137328043776][chan=0] response is 'RSP
SETSLOT 0 5 13'
<0001> Transceiver.cpp:778 [tid=140137328043776][chan=0] command is
'SETSLOT 7 13'
<0001> Transceiver.cpp:923 [tid=140137328043776][chan=0] response is 'RSP
SETSLOT 0 7 13'
<0001> Transceiver.cpp:778 [tid=140137328043776][chan=0] command is
'SETSLOT 6 13'
<0001> Transceiver.cpp:923 [tid=140137328043776][chan=0] response is 'RSP
SETSLOT 0 6 13'
<0000> osmo-trx.cpp:485 [tid=140137400406720] Shutting down transceiver...
<0000> Transceiver.cpp:338 [tid=140137400406720] Stopping the transceiver
<0000> Transceiver.cpp:351 [tid=140137400406720] Stopping the device
<0000> PCIESDRDevice.cpp:254 [tid=140137400406720] PCIESDRDevice::stop
<0000> PCIESDRDevice.cpp:261 [tid=140137400406720] PCIESDR stopped
<0000> Transceiver.cpp:364 [tid=140137400406720] Transceiver stopped
<0000> PCIESDRDevice.cpp:78 [tid=140137400406720] Closing PCIESDR Device
Yours XK1Zu
Hi all,
Just wondering what the status of OsmoCBC is?
I started compiling from source, but I couldn't find any docs on
interfacing with it other than that it's via a HTTP REST API,
If there aren't any docs are there packet captures or examples I can work
from that'd be quicker than trying to reverse it from the source code,
Happy to contribute some docs once I work it out,
Cheers,
Nick
Good Afternoon,
I recently acquired a NIB Ericsson RBS 6402. The specific model number
appears to be KRD 901 060/83. I see that the osmocom crew has integrated
this RBS with NextEPC at the 2019 CCC Camp event. I have used other
vendors eNodeB's with NextEPC, and would like to try the RBS with it as
well.
So far, I have booted up the RBS, and set my machine with a 10.1.1.1/24
IP address. The limited documentation I found online said the RBS should
respond to http at 10.1.1.11, at which point an XML site configuration
file can be uploaded. I see arp responses in WireShark from 10.1.1.11,
but cannot ping, or access http @ 10.1.1.11. If I place the RBS on a
network with a DHCP server, it obtains an address, but in the same
state, no response to pings, and no http access. Also tried ssh on the
standard port, with no response.
I see the wiki has information that appears to be output from a
terminal. Is that SSH or serial to the board itself?
I do have a rasbpi available on the network with a GPS/1PPS source for
timing. Is this as simple as setting opt 042 in the DHCP server that the
RBS will use?
Any guidance is appreciated!
v/r,
Caleb
dear Pau,
please fix either osmo-bts or ttcn3-bsc-tests so that running ttcn3-bsc-tests works again.
The failure I get for each and every BSC test:
Verdict: fail reason: "Timeout waiting for BTS0 oml-connection-state ""degraded"
When I downgrade osmo-bts to 580a27e97c3f0e139dfd7b0c10de24463d4b5294 (just
before the shutdown FSM was introduced), the tests work again.
(I didn't bisect, just picked that commit.)
This failure is particularly harmful now because we're currently struggling
with quite a couple of other reasons that cause the ttcn3-bsc-tests to fail. So
when we fix those, jenkins won't show the fix, but yet a different error.
I'm reluctant to revert your patches now, hopefully you can find a fix quickly
to move forward instead.
BTW, I also have introduced another new segfault in osmo-bsc myself, testing
the fix now and merging it directly when successful, so that we don't all go
insane.
~N
Hi Philipp (and lurkers on this list),
I've just pushed an update to the @laforge/trau@ branch of libosmo-abis,
which contains the new code modules for E1 / TRAU usage, and also a small
test program and test data.
The test program takes a raw binary dump created from an E1 timeslot with
TRAU frames captured of a BS-11 and converts that to RTP packets. You can feed
those RTP packets into osmo-gapk to play them back. The audio is clear, there
are just a few seconds of quiet at the beginning before anything is audible.
The patches also add an "I460" mode to e1_input. So from the osmo-mgw side,
I think we need to
* link against libosmo-abis and call e1inp_init + e1inp_vty_init()
* use existing VTY code to configure E1 line numbers / drivers / ports
* call e1inp_ts_config_i460() on every timeslot we want to use (this should *not*
happen on all timeslots, as some of them are used for signalling by the BSC)
* call osmo_i460_subchan_add() / osmo_i460_subchan_del() for each i.460 sub-slot
we want to use
* build the processing chain like in libosmo-abis/contrib/trau2rtp/trau2rtp.c
via i460 -> trau_sync -> osmo_trau_frame_decode_16k/osmo_trau_frame_decode_8k -> osmo_trau2rtp
I believe this should be at a stage where it can be integrated into osmo-mgw. The API
may not be 100% stable yet, but it shouldn't change completely. The main missing
bits are:
* allow selection of sync pattern in trau_sync.c (or auto-detect?)
* handling of T-bits for alignment of air-interface timing with downlink
TRAU frame timing
I will next be hacking on a small tool that will speak the 'osmo-e1d' protocol
but use binary capture files that are looped over and over again. This way
you should be able to use libosmo-abis e1_input without any physical card and
still get TRAU frame data.
At a lower priority, I'd like to look into support for HRv1 and AMR TRAU
frames on 16k sub-slots.
--
- Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi!
I just realized that since OsmoCon was discontinued after 2018 didn't
result in sufficient turn-out, and only the 2017 incarnation contained
some entry-level talks, we actually only have introductory level
presentations / videos about a setup that still covers OsmoNITB.
(https://media.ccc.de/v/osmocon17-4002-running_a_basic_circuit_switched_osmo…)
This may or may not be a reason why some people still want to set up OsmoNITB
in 2020. While our wiki and user manuals all have deprecated OsmoNITB years ago,
people who only look for videos might be mislead.
Also, I'm sure that several other presentation (like the one about 3G / osmo-iuh before
the CNI split) would similarly benefit from an update.
So I think we should try to create/update some slide decks and record related
lectures / tutorials at some point this year. I wouldn't bother setting up a
virtual conference or some kind of remote interaction at this point. Recording
some talks and/or screencasts allows us to create and release them one-by-one.
I would like to get started by collecting a list of topics at https://osmocom.org/issues/4578
before we start to actually work on the presentations.
One question is also how to record, but let's first work on the content before
we worry about recording and publication.
Regards,
Harald
--
- Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi all,
as was noticed during the weekly review, all TTCN-3 BSC test cases from
LCLS group are failing since build #987 (May 29) [1], so I am trying to
investigate this.
Until now I thought that it's somehow related to my IPA/RSL refactoring
patch set, so I spent half of a day reading the code of those test cases
and trying to figure out what could be the reason. But then I checked
ttcn3-bsc-test-latest [2]. I should have done this first, of course.
Magically all LCLS test cases are green there.
So I assume that it's not related to the recent IPA/RSL changes, and
most likely caused by recent changes to osmo-bsc and/or libosmo-*. I
already tried to downgrade osmo-bsc to v1.6.0 (Jan 3) with no luck.
If anyone was working on something related to RSL, MGCP or LCLS, please
let me know - this might help to find the problem faster. Thanks!
[1] https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bsc-test/
[2]
https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bsc-test-latest/
--
- Vadim Yanitskiy <vyanitskiy at sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
