Dear Osmocom society,
I am trying to connect a cell phone (lets call it phone #1) through OpenBTS to real GSM network…
To do so i have to introduce a osmocomBB phone which will be connected to my linux machine which runs OpenBTS
So kind of it will be a following structure:
Phone #1 → OpenBTS → OsmocomBB phone → real GSM netwok.
No my goal is to have OpenBTS and OsmocomBB phone to talk to each other… for example authentication parameters which to be exchanged between phone #1 and real network to happen through the chain described above ….
Has this case been or something like this done before ? Or are you aware of any cases when OpenBTS and OsmocomBB phone exchange data?
Thank you very much
--
Mario Lucas
Dear Osmocom community,
It's my pleasure to announce the next OsmoDevCall at
August 27, 2021 at 20:00 CEST
at
https://meeting4.franken.de/b/har-xbc-bsx-wvs
This meeting will have the following schedule:
20:00 meet + greet
20:15 presentation on "osmo-remsim in practice"
21:00 USSE: unstructured supplementary social event [*]
22:00 close of call
Attendance is free of charge and open to anyone with an interest
in Osmocom.
More information about OsmoDevCall, including the schedule
for further upcoming events can be found at
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall
Looking forward to meeting you on Friday.
Best regards,
Harald
[*] this is how we started to call the "unstructured" part of osmocom
developer conferences in the past, basically where anyone can talk about
anything, no formal schedule or structure.
--
- 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)
Hey Vadim,
Just now I came across this code,
with an early return in case of BCCH. But right below that, BCCH is still
mentioned in the comment, and there are more IEs being parsed.
So I get the impression the early return may prevent that OSMO_MIN limiting for
BCCH, and that may not be intended?
/* Osmocom specific extension for BCCH carrier power reduction */
if (dch->chan_nr == RSL_CHAN_BCCH) {
int rc = bts_set_c0_pwr_red(trx->bts, new);
if (rc != 0) {
const uint8_t cause = (rc == -ENOTSUP) ?
RSL_ERR_SERV_OPT_UNIMPL : RSL_ERR_IE_CONTENT;
return rsl_tx_error_report(trx, cause, &dch->chan_nr, NULL, msg);
}
return 0;
}
/* BS power reduction is generally not allowed on BCCH/CCCH carrier.
* However, we allow it in the BCCH carrier power reduction operation.
* Constrain BS power value by the maximum reduction for this timeslot. */
if (trx->bts->c0 == trx)
new = OSMO_MIN(new, lchan->ts->c0_power_red_db);
/* 9.3.32 (TLV) BS Power Parameters IE (vendor specific) */
if ((ie = TLVP_GET(&tp, RSL_IE_BS_POWER_PARAM)) != NULL) {
https://git.osmocom.org/osmo-bts/tree/src/common/rsl.c?id=6611e7f3059d26794…
Dear Osmocom community,
It's my pleasure to announce the next OsmoDevCall at
August 13, 2021 at 20:00 CEST
at
https://meeting4.franken.de/b/har-xbc-bsx-wvs
This meeting will have the following schedule:
20:00 meet + greet
20:15 presentation on "GSM-R and its differences to GSM"
21:00 USSE: unstructured supplementary social event [*]
22:00 close of call
Attendance is free of charge and open to anyone with an interest
in Osmocom.
More information about OsmoDevCall, including the schedule
for further upcoming events can be found at
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall
Looking forward to meeting you on Friday.
Best regards,
Harald
[*] this is how we started to call the "unstructured" part of osmocom
developer conferences in the past, basically where anyone can talk about
anything, no formal schedule or structure.
--
- 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 I currently have to clear my basement for water-damage related renovation,
I'm going to use the opportunity to get rid of some of the things I'm unlikely
going to use ever again
https://osmocom.org/projects/miscellaneous-projects/wiki/LaForge_surplus_20…
If anyone is interested: I'm not looking for any money in return. I just want
to find a new home for it rather than actually disposing of it at some recycling
facility.
Let me know ASAP if you're interested in any of it, thanks.
Happy hacking,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi,
I would like to know if it is possible to disconnect a connected device to
my osmo-bsc system?
After running my osmo-bsc setup and my test phone is connected to my usrp
via 2g, is it possible to send a vty command or what are the steps to make
the connected device to detach to my bts?
Thank you so much.
Hnjojo
Dear Osmocom community,
It's my pleasure to announce the next OsmoDevCall at
July 23, 2021 at 20:00 CEST
at
https://meeting4.franken.de/b/har-xbc-bsx-wvs
This meeting will have the following schedule:
20:00 meet + greet
20:15 presentation on "high-level overview on IMS, VoLTE, VoWiFi"
21:00 USSE: unstructured supplementary social event [*]
22:00 close of call
Attendance is free of charge and open to anyone with an interest
in Osmocom.
More information about OsmoDevCall, including the schedule
for further upcoming events can be found at
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall
Looking forward to meeting you on Friday.
Best regards,
Harald
[*] this is how we started to call the "unstructured" part of osmocom
developer conferences in the past, basically where anyone can talk about
anything, no formal schedule or structure.
--
- 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)