Hello all,
I have recently tried migrating an OsmoNITB setup to the new standard using mostly this guide right here: https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_I… <https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_I…>
However, while my nanoBTS works perfectly fine in the old setup, it just doesn not work at all in the new one. When I start osmo-bsc the LED on the BTS starts flashing green after a few seconds and then stops flashing and just stays green all the time, which is the expected behaviour. Unfortunately though, after another couple of seconds, the LED starts flashing green again and then turns red.
This is what the log shows:
BTS 0: Failure Event Report: Type=processing failure, Severity=critical failure, Probable cause=Manufacturer specific values: Fatal software error, Additional Text=l2_bch.c:1154
****
** l2_bch.c#1154:BCHbcchSItypeValid( prim_p->infoType )
** IPA_SW_FATAL_ERROR
** In task "TRX Proc:L2_BCH" @ (1063).
****
.
BTS 0: Failure Event Report: Type=processing failure, Severity=critical failure, Probable cause=Manufacturer specific values: Fatal software error, Additional Text=TRX Proc:L2_BCH:l2_bch.c#1154 (1063).
BTS 0: Failure Event Report: Type=processing failure, Severity=warning level failure, Probable cause=Manufacturer specific values: Software warning, Additional Text=31385:WARN:OAM_RES:trx_fatal_error_log.c#255:TRX has logged the error:
.
BTS 0: Failure Event Report: Type=processing failure, Severity=warning level failure, Probable cause=Manufacturer specific values: Software warning, Additional Text=31385:WARN:OAM_RES:trx_fatal_error_log.c#256:TRX Proc:L2_BCH:l2_bch.c#1154 (1063)
.
BTS 0: Failure Event Report: Type=processing failure, Severity=critical failure, Probable cause=Manufacturer specific values: Fatal software error, Additional Text=BCHbcchSItypeValid( prim_p->infoType ).
BTS 0: Failure Event Report: Type=processing failure, Severity=warning level failure, Probable cause=Manufacturer specific values: Software warning, Additional Text=31385:WARN:OAM_RES:trx_fatal_error_log.c#260:BCHbcchSItypeValid( prim_p->infoType )
20180328072641280 DLINP <0013> input/ipaccess.c:247 Sign link vanished, dead socket
20180328072641281 DLINP <0013> input/ipaccess.c:71 Forcing socket shutdown with no signal link set
20180328072641282 DCTRL <000e> osmo_bsc_ctrl.c:160 No more BTS connected, sending TRAP.
Now I'm not claiming that my config is already 100% correct but I feel like this isn't a configuration issue. I'm using the most recent nightly builds of the entire osmocom library.
Does anyone know what could be at fault here?
Kind regards,
Michael Spahn
Dear list,
I'm having trouble using the A5/3 encryption in my setup. A5/1 works perfectly fine [attachment a5_1.pcapng]. As soon as I switch to A5/3 and e.g. send an SMS, the last valid message I see in the Wireshark traces of the GSMTAP of osmo-bts-trx is the Ciphering Mode Command requesting A5/3. After that, several messages arrive at the bts, but it seems like it can't make any sense of them. The MS repeatedly tries to send the SMS but never succeeds [attachment a5_3.pcapng]. Both MSs are connected to the same bts.
According to the Classmarks of all MSs, A5/1 as well as A5/3 are supported.
This is my Setup:
- USRP N210
- osmo-trx
- osmo-bts-trx
- osmo-nitb
- osmo-pcu
- osmo-sgsn
- osmo-ggsn
I'm using a Debian 9 VM and tried both the packages from osmocom-latest as well as osmocom-nightly.
The MSs I've tested are two Nexus 6 and one Samsung Galaxy S I9000. All three with sysmocom nano USIMs.
Could the decryption at the bts be incorrect? Has anyone tested/used it recently?
I'll be happy to provide additional information if needed.
Thanks,
Jan
Hi All,
Can anyone confirm if the maximum MO-SMS that can be sent is less than 60 characters including spaces?
For OSMO-NITB, we reach a maximum of 59 characters for MO-SMS, while for OSMO-BSC, we only reach a maximum of 50 characters (MO-SMS).
Is this a known issue?
TIA.
Best Regard,
Ron Menez
ron.menez(a)entropysolution.com<mailto:ron.menez@entropysolution.com>
Dear All,
I have just uploaded my modified osmo-iuh, which a new version asn1c is
applied, to :
https://github.com/brchiu/osmo-iuh/tree/new-asn1c
Code generated by this new asn1c can handle necessary ASN.1 information
object class feature used in several 3gpp specs, thus it remove the need of
asn1tostruct.py.
Because Lev Walkin has not accepted corresponding pull requests yet, it
should be built from Velchkov's repository :
https://github.com/velichkov/asn1c/tree/s1ap
And link to new libasn1c :
https://github.com/brchiu/libasn1c/tree/new-asn1c
I use RANAP 14.1.0, RUA 14.0.0 and HNBAP 14.0.0 to generate files.
There are still several compilation error which are irrelevant to this new
asn1c.
https://gist.github.com/brchiu/17b5d306dd3e95f5e7b255a7dbb81344
Hope someone can help solving them.
Because I do not have test environment nor have no time to verify this
porting, you are welcomed to use this result on your own.
thanks.
regards,
Bi-Ruei, Chiu.
Hi all,
I've set git.osmocom.org to read-only while I'm doing the migration
to the new server. So don't be surprised if you won't be able to push
there (or if gerrit is not able to push there).
I'll try to make this quick, should be back within the afternoon.
--
- 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)
When libosmocore/contrib/fsm-to-dot.py hinted me at errors in the new gscon FSM
in osmo-bsc, I took a moment to render and look at all our FSM definitions.
The osmo-bsc ones are fixed by https://gerrit.osmocom.org/7501
I also found OS#3110 and OS#3111
I published the FSM graphs as rendered today at
http://people.osmocom.org/neels/osmo_fsm_graphs/ and might do so every now and
then. If anyone likes, we could do it from jenkins regularly.
~N
Hi stsp,
I noticed in the recent gsm0808_cell_id_list2 a review item slipped by:
A "LAI" is by definition a PLMN (MCC+MNC) plus a LAC.
So saying "LAI and LAC" is like saying "My family and my brother".
So maybe we want to rename the "lai_and_lac" member of struct
gsm0808_cell_id_list2 before it gets tagged for release. Just "lai" would be
accurate, as its type (struct osmo_location_area_id) suggests.
~N
Hi Support,
In Half Rate configuration of OSMO-BSC, is there a way to used ETSI TS 101 318 standard for its RTP Payload Format? As per testing, the RTP Payload format used by OSMO is RFC5993.
Can this be configured in OSMO-BSC or OSMO-BTS-TRX? Or the configuration of this is hard coded?
Logs from OSMO-BTS-TRX:
[0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14)
[0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14)
[0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14)
[0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14)
[0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14)
[0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14)
[0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14)
[0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14)
[0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14)
[0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14)
[0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14)
[0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14)
[0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0015> trau/osmo_ortp.c:0 Receiving packet with unknown payload type 111.[0;m<0006> scheduler_trx.c:543 Cannot send payload with invalid length! (expecting 15, received 14)
TIA!
Best Regard,
Ron Menez
ron.menez(a)entropysolution.com<mailto:ron.menez@entropysolution.com>
In recent weeks, many of you have encountered and worked at failures of
OsmoMSC's subscriber conn FSM / the conn itself to handle corner cases and/or
cleanly handle error situations.
I have plans for that FSM to be reviewed, adding probably two more states to
it, a) to properly handle the early startup and b) gracefully release in all
situations; and to probably more closely glue the conn struct to the FSM.
My humble suggestion is to wait for me to review it and not spend more time on
it until that is through. I wrote the FSM initially, and it makes sense that I
clarify its structuring before all of you need to learn its current quirks.
I hope it won't take too long, just need to sort the priorities of this fix
versus the other tasks I have...
~N
Dear all,
I've changed some details related to logging:
* we now generate per-testcase merged TITAN log files with the same name
prefix as the pcap files (Module.Testcase.{pcap,merged}) and remove
the hundreds of per-component log files generated by the parallel
executor after merging them.
* the console log verbosity has been incresed to include all output from
explicit "log()" statements. This is particularly useful when running
the tests interactively.
Unrelated to the above, I removed our own copies of the MTP3/M3UA/SCCP
emulation and replaced it with the proper upstream git repositories
under 'deps' like most other external modules. This means that you
will need to
* update your 'deps' (make deps-update)
* remove/re-generate your symlinks (gen_links.sh) from e.g. 'bsc' or 'msc'
* re-generate the makefile subsequently
It may be that the make file dependency logic doesn't pick this up
automatically, so if you see some strange build errors, it may be a good
idea to clean your local work tree.
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)