> 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 all,
Just wanted to share an issue and a quick workaround I found for it in case
anyone else has the same problem. I believe a cmd2 update is causing
pySim-shell to fail. After installing it on a fresh install of Ubuntu
Server 20.04 and getting the following error when I run "python3
pySim-shell -p0":
>Using PC/SC reader interface
>Autodetected card type: sysmoUSIM-SJS1
>AIDs on card:
> USIM: a0000000871002ffffffff8907090000
>Traceback (most recent call last):
> File "pySim-shell.py", line 512, in <module>
> app = PysimApp(card, rs, opts.script)
> File "pySim-shell.py", line 59, in __init__
> super().__init__(persistent_history_file='~/.pysim_shell_history',
allow_cli_args=False, use_ipython=True, auto_load_commands=False,
command_sets=basic_commands, >startup_script=script)
>TypeError: __init__() got an unexpected keyword argument 'use_ipython'
If you run into this you can fix it by uninstalling cmd2 and reinstalling
cmd2 with "pip3 install cmd2==1.5".
Best,
Bryan
Hi,
I had a problem placing MO GSM calls from a Siemens S11E: The calls
were dropped immediately; Osmo-MSC reports "Cannot compose Channel
Type from bearer capabilities"
After investigating the SETUP request from the S11E, the phone does
not use octet 3a (no extension bit set in IE 3). Wireshark decodes the
radio channel requirement as "Full rate support only MS/fullrate
speech version 1 supported", so I added a condition to the gsm48_ie.c
function of libosmocore to include at least GSM FR in the list of
available speech_ver in case octet 3 has no extension.
Attached to this message are the Abis-IP PCAP traces of MO calls, and
the patch for gsm48_ie.c.
Regards,
Lennart
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
Hello Osmocom community,
I have a question about TCP port number assignment for programs using
libosmovty. Every Osmo-official server program gets official port
number assignments listed in the wiki, in PDF manuals etc - so far, so
good. But what about non-Osmo-official 3rd-party programs that wish
to use common Osmocom libraries, including the vty facility? Suppose
that an operator of an Osmocom-based cellular network needs to develop
some additional programs to satisfy some operational need, and some of
these additional programs are long-lived server processes for which an
Osmocom-style vty interface would be very useful. But implementing
such a telnet vty i/f requires a TCP port number...
Has anyone thought about designating an official range of TCP port
numbers which would be recommended for vty/ctrl/etc ports of processes
that use Osmocom libraries and extend Osmocom CNI in various ways, but
aren't official Osmocom projects?
M~
Hi all!
[cross-post to make sure everyone knows about it, please follow-up-to
the osmodevcon(a)lists.osmocom.org mailing list for further discussion]
As I mentioned several times at different occasions, I really think we
should put together a OsmoDevCon again. In case you don't know what that
is, please see https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCon
We should have restarted already in 2023, but I really was too busy and
it was a somewhat difficult year for me at times, sorry.
Date
----
In terms of timing, I am thinking about "after April but before the main
summer holiday season (June-August)". That leaves May.
Given that May has the whitsunday weekend as well as GPN
(Gulaschprogrammiernacht, a CCC event that will likely conflict
of interest with some people interested at attending OsmoDevCon), I'm
currently considering the following candidate dates:
* May 3 to 6
* May 24 to 27
This is as usual a friday-to-monday timeframe, allowing people who don't
work professionally on osmocom to attend just the two weekendd days,
while others can attend the full 4 days.
Venue
-----
In terms of venue, I'm hoping we can move to a slightly different
arrangement where the whole group stays together for the whole duration
of the event - as opposed to everyone staying at different hotels and
having to commute from hotel to venue and back every day. So something
like a hotel with a sufficiently large meeting room, hotels and catering
all day. And all of that ideally at a nice venue with some kind of park /
outdoor area, not downtown at the city center. Yes, that will obviously
come at a higher price tag than we're used to - but I'm confident we can
get that covered between sponsors and sysmocom.
Do you guys think this is a good idea? Or would you prefer the
traditional ad-hoc approach at IN-Berlin?
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> https://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi all,
does anyone have feedback on this dubious libosmo-mgcp-devel we publish in our
osmo-mgw.spec?
More detail in https://osmocom.org/issues/6300
Thanks!
~N
--
- Neels Hofmeyr <nhofmeyr(a)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
* Geschäftsführer / Managing Directors: Harald Welte
Hi all,
I'd like to drop the 'sdp audio fmtp-extra ...' cfg option from osmo-mgw.
If this option needs to stay, I'd like to hear about that.
There is more context in https://osmocom.org/issues/6313
Thanks!
~N
--
- Neels Hofmeyr <nhofmeyr(a)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
* Geschäftsführer / Managing Directors: Harald Welte
Dear mailing list,
I'm looking into releasing a new osmo-pcu version to finish up OS#6198,
and to have a release with the fix for OS#6191. Apparently that fix
requires a new PCUIF version. And osmo-pcu master now has a check that
requires the *exact* PCUIF version:
https://cgit.osmocom.org/osmo-pcu/commit/?id=46140948d9800bca6a7b4299f08b25…
pcu_i1_if.cpp:
} else if (info_ind->version != PCU_IF_VERSION) {
fprintf(stderr, "PCU interface version number of BTS/BSC (%u) is
different (%u).\nPlease use a BTS/BSC with a compatble interface!\n",
info_ind->version, PCU_IF_VERSION);
exit(-1);
}
So we will need to create releases of osmo-bts and osmo-bsc with the new
PCUIF version as well. As this is a breaking change, I think we should
bump the major version, and that in turn makes more sense with tagging
current master instead of cherry picking a few patches.
So I propose to do the following:
* tag a new libosmocore patch release with the few patches required for
osmo-pcu, osmo-bts and osmo-bsc master (see their TODO-RELEASE).
* tag major releases of osmo-pcu, osmo-bts and osmo-bsc from their
current master
Does that make sense?
Best regards,
Oliver
--
- Oliver Smith <osmith(a)sysmocom.de> https://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
