> 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.
Hi all,
This patch set adds to libosmocore an optimized Viterbi decodeer for
architecture specific (Intel SSE) and non-specific cases. The
implementation covers codes with constraint lengths of K=5 and K=7 and
rates 1/4 to 3/4, which make up the majority of GSM use cases. Speedup
from the current implementation is in the range of 5 to 20 depending on
the processor and code type. API is unchanged.
Tested on Haswell (i7-4770K) and Atom (D2550). Additional test codes
from osmo-bts are included. Further tests for AWGN bit-error-rate
and benchmarks can be found in the following repository.
https://github.com/ttsou/osmo-conv-test
Here are some examples.
Bit error test for GPRS CS2 with SNR of 5 dB and 100000 bursts.
$ ./conv_test -c 2 -e -r 5 -i 100000
=================================================
[+] Testing: GPRS CS2
[.] Specs: (N=2, K=5, non-recursive, flushed, not punctured)
[.] Input length : ret = 290 exp = 290 -> OK
[.] Output length : ret = 588 exp = 588 -> OK
[.] BER tests:
[..] Testing base:
[..] Input BER.......................... 0.042443
[..] Output BER......................... 0.000006
[..] Output FER......................... 0.001350 (135)
[..] Testing SIMD:
[..] Input BER.......................... 0.042460
[..] Output BER......................... 0.000005
[..] Output FER......................... 0.001240 (124)
Timed AFS benchmark with 8 threads and 100000 bursts per thread.
$ ./conv_test -b -c 10 -j 8 -i 100000
=================================================
[+] Testing: GSM TCH/AFS 6.7
[.] Specs: (N=4, K=5, recursive, flushed, punctured)
[.] Input length : ret = 140 exp = 140 -> OK
[.] Output length : ret = 448 exp = 448 -> OK
[.] Performance benchmark:
[..] Encoding / Decoding 800000 bursts on 8 thread(s):
[..] Testing base:
[..] Elapsed time....................... 4.320001 secs
[..] Rate............................... 25.925920 Mbps
[..] Testing SIMD:
[..] Elapsed time....................... 0.458272 secs
[..] Rate............................... 244.396341 Mbps
[..] Speedup............................ 9.426718
-TT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi! First a small update:
we finally decided to _not_ use token mode, as it confuses a lot of
phones, after receiving the token message the SIM goes into an error
state and the only way to recover is to reboot the phone. Now we just
read the IMSI straight from the SIM (using the card python library,
just like osmo-sim-auth does) and register them.
Now, the issue we see is that 1-2 users every day reach a point where
they can make phone calls and send messages, but they can't receive
neither of them. Sometimes the problem can be fixed by running:
> subscriber extension <EXT> clear-requests
but this only work when there are pending requests. In other cases,
the phone has to be rebooted. Did anyone encounter the same issue?
Cheers
Ciaby
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJUef1WAAoJEPU83OtbD4fQ69kQAI7peg30lHwbDPMXnTX80gUu
0dGsiK2iB5oWZ6Ohbs3W+/+xVoMseuG1di6Rk0XT9buN2IOR5fMfAs3INQ2EuAlV
qz1RRn5Ux8uV0RJWyAJoSt7eFh3gbnDgsJ+x8SXEHQRw4rYHG2P+HXyEtncW6A6y
L8/oPeIxH/LlP/55MP3KUY5BnQmN658LnJU9AFSwPkpjn2f/dj4o6mUdWo8haTTQ
UWPWEdhQoeXPBqHsn2cKamT13SmiepMYAGuDEJci9LCS+J8vd70ukAP/oa1L6u1w
+3+RbcNvC9fwAKDLU01b/cu630v6/mhk0lxWNlIz/kNL1aHPZe8QhP5sM4SuLtzj
UaeHLxp4u2Pb7N31b3qtRA4jgl+5YFla5376F3d00jPSfZpmFggFgdRB2qWhF1m8
WucfzLc41dV1AVTdL90ISSRt1LZ/fLHBea8kgUxK+KrhBO7U7AV3PXk9of4EAf7y
VKMX3KZWwtEKhpi0v3PihgW8bS/RaG3zEmsr30QXzXVaZknCfjGi8OOOB0JaHY48
o3g40YpzeyEq1gOyKKfBmtf1qk4GgLyPKfMUoTvXE2oNHmrg3ZlJldABKNzR9qz3
5hsHJ6/QGsBST1E3dphI0Zb6ubLnFwqBl02GyeJELLbtPCLPQMDicx03cqT4BjO3
vzDcPdIWg1sfSomYKMK9
=Zw4T
-----END PGP SIGNATURE-----
Dear all,
the valuable L1SAP abstraction has been sitting out of master for too
long time. It is a pity that this has taken so long. I've finally been
able to put some time into osmo-bts again and reviewed the following
patch series. It consists of mostly Andreas' work, interspersed with
smaller patches/fixups that I introduced after the respective original
patch from Andreas.
I have started a sysmobts between all of the major steps in this patch
series and did a short manual tests involving registration (LU) of two
MS, mobile-to-mobile call and vty-to-mobile SMS. So far I couldn't see
any problems. What has not been tested yet is the PCU interface as well
as encryption support. I plan to do this later this week.
I intend to merge the code after this current review cycle. Please take
your time to have a look and provide feedback (if any), so we can get
this over and work on new features again, rather than infrastrutural
changes.
I didn't yet rebase the osmo-bts-trx interface on top of the L1SAP, as I
don't have a hardware setup for it, and I will leave it to the owners of
such hardware to publish/push the respective code after L1SAP is merged.
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)
Dear Osmocom.org project members,
I'm happy to be able to announce the annual incarnation of OsmoDevCon.
The Date is set for March 27 through 30. Venue: As usual, IN-Berlin
e.V. in Berlin, Germany.
Further details can be obtained from
http://openbsc.osmocom.org/trac/wiki/OsmoDevCon2015
Attendance, as usual, is restricted to people with an active history in
the Project by contributions in terms of code, patches, discussions,
documentation or in other form.
= Registration =
If you have wiki access, please add yourself to the #Requested section.
Alternatively, you can send me private e-mail about it.
After review, your (nick)name will be listed in the #Confirmed section.
Looking forward to meeting all of you again soon!
--
- 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)
Dear Holger,
Thanks for the commit on my previous patch.
Here is a new one:
This pacth makes hopping type (baseband or RF) a user changeable parameter.
Tested with:
- MetroSite: baseband and RF hopping works
- UltraSite: RF hopping works
As previously, the default behavior of OpenBSC is not changed. If the configuration parameter is not provided, it will default to baseband hopping, as before.
It builds against the latest version of OpenBSC master.
Regards,
Csaba
Dear Holger,
I think I found a better way for initialization. The attached version of the patch builds against latest master OpenBSC, contains the fixes I missed from the previous version.
Tested:
1. Without using the config parameter, the reset timer defaults to 15 seconds (as before),
2. With the configuration parameter, the reset timer will use the specified value.
Tested with: InSite (daisy chained, two BTSes), MetroSite and UltraSite units.
Will create another patch for hopping (both baseband and sytheiser hopping works, but it needs a change in the sourcecode, like the reset timer before).
There is another minor problem at the moment: UltraSite needs additional time after OMU configuration done, before it can bootstrap the RSL links. This is due to the fact that UltraSite starts to load the TRX SW after it got the "Use current" command, and it takes arouned 45-50 seconds for the TRXes to be ready for LAPD. So to first RSL bootstrap should be delayed after OMU config complete is received by the BSC. Now the RSL link is bootstrapped right after the OMU is configured and the LAPD link times out way before the TRX will be ready for LAPD. Will try to create a patch for this too, until then, a small hack can make this problem go away (changing n200 parameter to 100).
Regards,
Csaba
----- Eredeti üzenet -----
Feladó: "Holger Hans Peter Freyther" <holger(a)freyther.de>
Címzett: "Sipos Csaba" <sipos.csaba(a)kvk.uni-obuda.hu>
Elküldött üzenetek: Hétfő, 2015. Február. 2. 9:50:50
Tárgy: Re: Patch for OpenBSC [Nokia Site family]
On Sun, Feb 01, 2015 at 10:53:19PM +0100, Sipos Csaba wrote:
> Can you please tell me where should I initialize the timer, when the config parameter is not used (user not specified it in the cfg file)?
>
> I tried to look at other parts of the code but I don't see where the default values are stored, if a parameter is not set in the config file.
>
> Otherwise I fixed the remaining problems.
It is not the best place but gsm_bts_alloc would allow you to
initialize this field correctly. The other option would be when
the type of the bts is set to nokia.
Hello
I have a question on sms
Is it possible to send hex data using telnet localhost port 4242
I saw the posting in forum about SMPP+OpenBSC (march-april 2014), which
talk about Kannel
Can somebody suggest how to configure Kannel with OpenBSC.
regards
Ramesh
