I tried to install CalypsoBTS have libosmocore installed, osmo-bts osmobsc,
libosmo-netif, libosmo-abis, ortp, trx, libosmo-dsp everything went without
errors, following the instructions I created: touch ~/.osmocom/open-bsc.cfg
, then when you run : osmo-nitb -c ~/.osmocom/open-bsc.cfg-l
~/.osmocom/hlr.sqlite3-P-C --debug=DRLL:CC:MM:RR:RSL:NM shows me:<0005>
bsc_init.c:498 Failed to parse the config file:
'/root/.osmocom/open-bsc.cfg' file tried to create as administrator but
without success , pleas help me
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/Calypso-BTS-tp4026753.html
Sent from the baseband-devel mailing list archive at Nabble.com.
Hello! I Need Help
I install these three programs OpenBTS, OsmocomBB, Asterisk
Then run them, Everything works well
OpenBTS sent an SMS to my phones
I answered and he checked me
I registered into OpenBTS a second phone
I tried to transfer SMS between phones - all good
but when I try to call from one to another I did not get
Asterisk writes
================================================================
*CLI> Retransmission timeout reached on transmission 755803415(a)127.0.0.1 for
seqno 179 (Critical Response) -- See
wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 32001ms with no response
================================================================
Why?
What do I do?
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/OpenBTS-OsmocomBB-Asterisk-tp402…
Sent from the baseband-devel mailing list archive at Nabble.com.
Hey guys, first of all I want to express my deep respect for this project,
this is truly amazing project and very well developed.
Second, I'm doing a few studies regarding GSM security (no, I'm not
hacking.) and I need to develop a feature for osmocombb, which is: the
ability to turn the L23 app as a zombie (C unix domain socket) waiting for
instructions (e.g.: connect to the network with predefined parameters
(IMSI), collect RAND, send sms,...).
Is there any documentation or flow regarding the code? It's very hard for a
non C coder to follow the flow... Or is there someone that can help me in
the Architectural level?
Thank you.
Hi,
> I'm guessing I would need to perform surgery on OSMOCOM-BB code in order
to
> connect it to another network? Is there any in built feature that would
> allow me to do so directly?
As I understand, you want to connect the network you running yourself on
OpenBTS.
There are two modes of network selection: manual and automatic (when MCC/MNC
from SIM card are used). Have a look at the 'network-selection-mode' in
your config
file (~/.osmocom/bb/mobile.cfg). Also, have a look at the 'network' command
in VTY.
You can also create a virtual SIM card in your ~/.osmocom/bb/mobile.cfg
(look at the
'test-sim' section) with desired IMSI and RPLMN (001 / 01 by default). Then
you will
be able to attach one using the 'sim testcard 1'.
With best regards,
Vadim Yanitskiy.
Greetings,
I have been working with Layer23 stack of OsmocomBB since a couple of
months.
I decided to try MNCC socket interface without LCR (I'm aware there is an
implementation embedded in LCR gsm-ms).
I reverse engineered and wrote a simple C application taking mncc.h.
Problem: I'm unable to make a call on live network, although it does channel
allocation, ciphering etc.
Flow:
1. Create MNCC struct and write on to the osmocomBB socket
2. OsmocomBB parses it well and request for channel, ciphering mode, init
MM, sending SETUP etc works great.
3. However, in response to step.2 after sending SETUP it returns with (ms 1)
Received 'RELEASE_COMPL' in CC state INITIATED. Why does it release CC?
4. I further debugged, the reason for release is in fn.
gsm48_cc_rx_release_compl in (gsm8_cc.c) it says mncc-cause =
*GSM48_IE_CAUSE*. with no description.
I really don't know whats causing this issue. Any help would be much
appreciated.
Or It would be very kind if someone could guide me.
My mncc socket create code:
struct gsm_mncc *mncc;
int i = 0;
int call_ref = new_callref++;
mncc = create_mncc(MNCC_SETUP_REQ, call_ref);
if (!strncasecmp(number, "emerg", 5)) {
printf("Make emergency call\n");
mncc->emergency = 1;
} else {
printf("make call to %s\n", number);
mncc->fields |= MNCC_F_CALLED;
if(number[0] == '+') {
number++;
mncc->called.type = 1; /*international*/
} else {
mncc->called.type = 0; /*auto-unknown -prefix must be used*/
}
mncc->called.plan = 1;
strncpy(mncc->called.number, number,
sizeof(mncc->called.number) - 1);
printf("Calling number %s\n", mncc->called.number);
/* bearer capability (mandatory) */
mncc->fields |= MNCC_F_BEARER_CAP;
mncc->bearer_cap.coding = 0;
mncc->bearer_cap.speech_ctm = 0;
mncc->bearer_cap.radio = 3; /** Support TCH/H also*/
/** Supported rates **/
mncc->bearer_cap.speech_ver[i++] = 2; /* support full rate v2 */
mncc->bearer_cap.speech_ver[i++] = 0; /* support full rate v1 */
mncc->bearer_cap.speech_ver[i++] = 1; /* support half rate v2 */
mncc->bearer_cap.speech_ver[i] = -1; /* end of list */
/** END **/
mncc->bearer_cap.transfer = 0;
mncc->bearer_cap.mode = 0;
/* CC capabilities (optional) DTMF */
mncc->fields |= MNCC_F_CCCAP;
mncc->cccap.dtmf = 1;
mncc->fields |= MNCC_F_CCCAP;
mncc->clir.inv = 1;
mncc->clir.sup = 1;
}
return send_and_free_mncc(mncc->msg_type, mncc);
Looking forward to the reply,
Thanks,
Gerard
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/OsmocomBB-MNCC-socket-implementa…
Sent from the baseband-devel mailing list archive at Nabble.com.
Dear Osmocom members,
I am new in OsmocomBB but trying to understand how all the stuff works.
And I have a question.
As I understood we have DigitalBB Calypso in our Motorola phones which
consist of DSP and ARM Cores.
If we are talking about "normal" phone firmware, In DSP L1 processing is
done, in ARM core L2 and L3 processing of GSM stack is done.
But we must also have some "regular" OS somewhere, am I right? So I mean
all the menus, applications like "Settings", "Phone book", etc.
In modern phones, I believe Adnroid or iOS communicate with some RTOS
running in ARM core of DigitalBB. But what is about Motorola phone? Does it
have separate ARM processor/RAM for a refular firmware?
Did you create some applications for ARM part of DigitalBB and some
applications for UI which run outside the RTOS?
It's possible that I am confusing with all the terms but I would appreciate
if you help me to understand.
Kind regards,
Anton
I recently set up OpenBTS which is working perfectly. I can make a test
call by calling 2600 using an Android phone.
However when I try "show subscriber" in OSMOCOM, various BTS are listed,
with their MNC and MCC values but OpenBTS is not listed.
Any solution to this?
P.S. I've determined the MNC and MCC values for OpenBTS which are 001 and
01 respectively.
Hi all,
today I've deployed some cgit improvements on https://git.osmocom.org/,
in the hope that it makes this tool even more useful:
1) syntax highlighting of source code (requested by Hoernchen)
The source code is now highlighted by pygments. I don't really
understand why somebody would want to look at source code a lot in a
browser, but well, it was as easy as to enable the existing pygments
based filter plugin.
2) rendering of "about" page from README.md
As you might have noticed, I've introduced a README.md in a number of
repositoires, and cgit is now rendering an about page for every
repository, e.g. at http://git.osmocom.org/libosmo-abis/about/
3) gerrit change-ID hyperlink generation
All gerrit Change-IDs in commit messages are now automatically converted
to hyperlinks to the respective gerrit change, see e.g. the below
example:
http://git.osmocom.org/openbsc/commit/?id=6dd0fc685b7149f67a5fe17a5bce55c44…
Please note that this works for the "Change-Id" line of the actual
change, but also for change-ids in the free text (e.g. "this depends on
change-id ... in libosmocore")
4) Osmocom ticket/issue hyperlink generation
Any Line that matches the "^((Relate|Close|Fixe)[ds]):" prefix is
scanned for occurrences of "OS#(\d+)" which are then amended with
hyperlinks to the respective issue on osmocom.org
Please note the OS# prefix is mandatory, so things like "OS#1614, 1615"
will not work, as can be seen at
http://git.osmocom.org/osmo-pcu/commit/?id=0a8fae8d141c2cfa4387ffe9b35402d5…
Please format your commit messages accordingly.
Regards,
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)