> 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. I am working on setting up an osmoTRX based base station. Where I
am in the US, between 902 and 928 MHz is part of the ISM spectrum, and
unregulated. Therefore, I would like to configure my base station to use
both an uplink and down link frequency within this range. However, none
of the pre-existing ARFCN options have both the uplink and downlink
frequencies within this band. Is it possible to manually shift the
frequency used by the base station, or manually select the up/down
frequencies so that both remain within this range?
Thank you for your help,
Enzo Damato
Hello. I am working on setting up an osmoTRX based base station. Where I
am in the US, between 902 and 928 MHz is part of the ISM spectrum, and
unregulated. Therefore, I would like to configure my base station to use
both an uplink and down link frequency within this range. However, none
of the pre-existing ARFCN options have both the uplink and downlink
frequencies within this band. Is it possible to manually shift the
frequency used by the base station, or manually select the up/down
frequencies so that both remain within this range?
Thank you for your help,
Enzo Damato
Hi Keith,
> Is it an artwork by any chance?
We are saving a Nokia UltraSite and building an as fully functional
GSM network as much as it is possible.
We have a bit of a LAPD issue on the multi-TRX side of things as the
current RSL bootstrap code is really only practical for the InSite
units, so that needs some work, but at least the OM data we send is
confirmed to be correct, and I can make a single TRX work. One other
thing would be nice to have is Cell Broadcast, that part also does not
work yet, but lets keep that issue separated.
Your second link requires a gitlab login. Is there a more accessible
way to get that patch? :-)
Thanks!
Regards,
Csaba
Dear List,
In the good old NITB days, it was possible to set up an "open" network
where a foreign IMSI was able to register with the network, and at the
first attempt the subscriber received sort of a "welcome" SMS with its
random generated MSISDN. I found the on-demand option in the HLR, but
I am not sure if the welcome SMS part is even possible since the
network elements are now separated, no sign of it in any of the
manuals though.
I am working on a museum setup where there will be some pre-programmed
SIMs in handsets, but it would be nice if the visitors themselves can
use their own phone to connect and use the network. Worst case they
can use the USSD command to get their MSISDN, but a welcome SMS would
be nice to have.
Regards,
Csaba
Hi Keith,
My question was targeting the Osmocom stack and not the (external)
PBX. I already found some AMR patches for Asterisk (it seems it is
still not part of mainline), will try to do that.
The second half of my question was somewhat vaguely tries to ask if it
is possible to do AMR when the call is MO-MT directly, or maybe the
MGW can do transcoding, so in a nutshell: maybe there is a solution to
do GSM FR when the call is outbound from the mobile network and AMR
when it is mobile to mobile. Or the transcoding path is also an
option. Point is: about these capabilities there is very little
information available about what is supported and what is not within
the Osmocom domain.
Regards,
Csaba
