> 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.
An according change in the OpoenBSC is following.
Since we're changing the external API we should probably increase a
lib version as well.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves, Inc. / ООО УмРадио
https://fairwaves.co
Hi all;
I have deployed one ipaccess nanoBTS 1800, with OpenBSC (osmo-nitb) and all the osmocom suite apps.
I have already make succesfully GSM calls, SMS, and GPRS/EDGE packet data connections.
I now want support for sending binary SMS, i have read that with SMPP i would can.
I have compiled OpenBSC with SMPP but now I don´t know how to use it, i think it is in the OpenBSC vty, but i don´t know the commands or how to use the interface.
If you can give me some light in this thread i will grant you.
Sorry for my English
Best Regards
Jesús Vega Diaz
hi,
Daniel and me started a small report for the 30C3 network but we
are kind of stalled. Anyone feels like doing some review and
providing feedback?
holger
Hi list,
wouldn't be useful to have the possibility to choose (at least) between
UNIX and INET socket to be used for connecting to an external MNCC?
If this will be the case where should the choice be made? I was thinking to
add an extra option to bsc_hack but the choice can also be hard-coded
(prior to compilation).
cheers
luca
I wrote a blog post about running Osmocom on Parallella, with UmTRX:
http://www.rs-online.com/designspark/electronics/eng/blog/building-a-gsm-ba…
Just using the dual-core ARM in the Zynq, so nothing
surprising/interesting to this list and it's more of just an intro.
However, I'm curious as to opportunities for improving the performance
by offloading parts of the transceiver to the Epiphany chip. Does
anyone have any views on how practical this might be, effort involved
and potential gains etc?
Cheers,
Andrew
--
Andrew Back
http://carrierdetect.com
Currently ADM state change request that tries to set the
administrative state to the current value are immediately ACK'ed.
Beside the caching problem, this could lead the protocol
inconsistencies if two such requests are sent one after the other and
the second arrives before the procedure of the first has finished.
This patch removes the shortcut in oml_rx_chg_adm_state() which
immediately called oml_mo_statechg_ack(mo).
Ticket: OW#1132
Sponsored-by: On-Waves ehf
---
src/common/oml.c | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/src/common/oml.c b/src/common/oml.c
index 9ec773b..b7c12f7 100644
--- a/src/common/oml.c
+++ b/src/common/oml.c
@@ -765,11 +765,10 @@ static int oml_rx_chg_adm_state(struct gsm_bts *bts, struct msgb *msg)
return oml_fom_ack_nack(msg, NM_NACK_OBJINST_UNKN);
/* Step 2: Do some global dependency/consistency checking */
- if (mo->nm_state.administrative == adm_state) {
- DEBUGP(DOML, "... automatic ACK, ADM state already was %s\n",
- get_value_string(abis_nm_adm_state_names, adm_state));
- return oml_mo_statechg_ack(mo);
- }
+ if (mo->nm_state.administrative == adm_state)
+ LOGP(DOML, LOGL_NOTICE,
+ "ADM state already was %s\n",
+ get_value_string(abis_nm_adm_state_names, adm_state));
/* Step 3: Ask BTS driver to apply the state chg */
return bts_model_chg_adm_state(bts, mo, obj, adm_state);
--
1.7.9.5
Hi there,
I'm fairly new to the mobile world and am still coming to terms with a
whole new world of terminologies. The project is to test out a theory in
my lab before wanting to scale this at a larger level for commercial
purposes.
The intent is to be able to have roaming available with a roaming
aggregator in the United States with a small-scale mobile network enabled
using OpenSource software.
We are probably looking at implementing no more than 15 BTS's nationwide to
attract roaming customers at high traffic locations.
Our roaming aggregator would like us to send them MAP SS7 Messages from our
MSC.
My understanding of the requirements so far are:
1 x BTS (this could be a PC with some radio cards or something like a
nanoBTS)
1 x MSC/BSC/VLR
We won't be issuing any sim cards on our own network in the long run and
hence I don't see the point in us having a unique HLR.
Are there any gurus here that would be willing to share their intelligence?
--
Thanks,
Sahil
--
Thanks,
Sahil