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
Hello fellow developers,
I am getting ready to implement my own SMSC, connecting to Osmocom CN
via GSUP (see OS#6135), and I have a question about SMSC address
terminology.
In traditional commercial GSM networks, the SMSC address visible to
the user (prepended to the TPDU for MT SMs, stored in EF_SMSP record
on the SIM for MO SMs) looks like a phone number in full international
format, with TON=1 and NPI=1. For example, T-Mobile's SMSC address is
+12063130004 (to an uninitiated eye it looks exactly like a regular
phone number in Seattle, WA), while the SMSC of Mexican Telcel is
+5294100001410 - one digit longer than regular phone numbers in Mexico,
and a little irregular in structure.
What is the correct term for these SC-address phone-number-thingies?
Are they Global Titles - or is GT something different?
If I were to make up fake global-looking SMSC addresses of this form,
e.g., something like +1xxx55501xx for NANP territory, would it be
correct to call such SC-address a fake Global Title?
Just wondering...
M~
Dear list,
I managed to set up my E1 based Nokia BTS, the complete Osmo-CNI
stack, SIP-connector and Asterisk. MO/MT calls do work as well as
external SIP calls to and from mobile as well. But no matter what I do
only plain FullRate calls are possible.
Under osmo-bsc.conf code support is set like this (the BTS HW do
support all of these codecs):
codec-support fr efr amr
but once I also add "codec-list fr3 fr2 fr1" to the MSC section of the
osmo-bsc.conf, the calls wont establish anymore.
I watched Neel's OsmoDevCall presentation on this topic, but it is not
very clear what codecs are supported when osmo-sip-connector and an
external PBX is used?
Regards,
Csaba
I have git-cloned https://gitea.osmocom.org/cellular-infrastructure/osmo-bts this project in order to have a solution for calling 2 mobile phones in my own network. I dont have any experience with this. I have instaled and configured in the past the same solution from PenHerts git but it is a lil bit old. I want to configure and install this solution bu i do not know the exact steps to do that. I dont find any configuration file or i do not know what to do with them. I do not have any experince with this domain and i want to know the steps in order to run this project properly. Could you help me with any directions?
Hi all,
during recent patch review
(https://gerrit.osmocom.org/c/osmo-trx/+/33737) the topic of continuing
to maintain support for big endian machines has come up.
While traditionally I've always been a strong proponent of writing
portable code that can run also on big endian systems, it is not the
year 2003 or 2008 anymore, and PowerPC (the main big endian platform) is
dead by now, as is SPARC. Not just in newly-built processors, but also
in existing and still operating machines, at least of the class that
would run our code.
So unless somebody objects with strong arguments, I'd propose to
officially and explicitly drop supporting big endian systems from
osmocom CNI projects.
From what I can tell, this would primarily mean
* drop the struct_endianness check from the commit verification
* removing all our struct_endianness-generated or other code that
explicitly adds big endian support
* adding some kind of #warning or even #error to a common libosmocore
header file if anyone tries to build on big endian
This obviously doesn't mean we can abandon using [osmo_]{htonl,ntohl},
as network byte order is still network byte order.
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,
It's Alejandro Blanco.
I would like to disable the UST service 124 so that I connect the
smartphone to a gNB based on srsRAN.
However, there is an error after trying it. Find a screenshot below that
shows the error message.
Do you know how to fix this?
Thank you.
[image: image.png]
Best regards,
Alejandro
----------------------------------------------------------
*Alejandro Blanco Pizarro, PhD <https://alejandroblancopizarro.github.io/>*
*Post-Doc at **The University of Edinburgh*
----------------------------------------------------------
