Hi all!
This is the announcement for the re-incarnation of our bi-weekly
Osmocom Berlin Meeting.
Nov 11, 8pm @ CCC Berlin, Marienstr. 11, 10117 Berlin
There is no formal presentation this time, but
* there will be SDR equipment, antenna and a working/tested setup of a
gnuradio based MPT1327 decoder
* there will be SIMtrace equipment in case somebody wants to play with
it there will be a sysmoBTS with OsmoBTS, OsmoPCU, OsmoNITB, OsmoSGSN
and OpenGGSN if somebody wants to play with it
* there will be Huawei Femtocells to play with
* Harald would like to discuss OpenBSC website / documentation improvements
The meeting is open to anyone interested in mobile communications. You
do not have to be involved with the Osmocom projects in order to attend.
Anyone interested in mobile communications protocols is welcome.
If you are interested to show up, feel free to do so. The meeting is
"free as in free beer", despite no actual free beer being around ;)
More information can be found at
http://openbsc.osmocom.org/trac/wiki/OsmocomMeeting/Berlin
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org>
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi,
This is the first series of my gtp kernel updates.
It contains mostly the removal of Linux version ifdefs. After this the
module builds only on 4.3+. The goal here is the preparation for main
line inclusion.
The other small change is a update to the Makefile for simpler out-of-tree
build
Andreas
--
Andreas Schultz (6):
build: update Makefile for simpler out of tree builds
gtp: remove genl_ops compat ifdef for Linux < 3.13
gtp: remove per cpu stats compat ifdef for Linux < 3.13
gtp: update for Linux > 4.1+, __ip_select_ident arguments have changed
gtp: update for Linux > 4.1+, genlmsg_end return should be ignored
gtp: update for Linux > 4.2+, set NO_QUEUE flag on gtp device
Makefile | 17 ++++++++++++-----
gtp.c | 11 +++++------
gtp.h | 4 ----
3 files changed, 17 insertions(+), 15 deletions(-)
--
2.5.0
Hi.
I've enabled extra logging for BTS <-> BSC communication and I can see following
neverending cycle - see attachement. Is th constant flow of "Set Chan Attr" and
channel state alternating between Enabled and Disabled states an expected thing or
it's some sort of misconfiguration on my part?
regards,
Max.
Hi.
If I enable detailed-enough logs of OpenBSC I can get data regarding call and sms
transactions:
new state INITIATED -> MO_CALL_PROC, 1 active transactions
new state MO_CALL_PROC -> CONNECT_IND, 1 active transactions
new state CONNECT_IND -> ACTIVE, 1 active transactions
new state ACTIVE -> DISCONNECT_IND, 1 active transactions
new state DISCONNECT_IND -> RELEASE_REQ, 1 active transactions
new state RELEASE_REQ -> NULL, 0 active transactions
However there's no information regarding which mobile is participating in the
transaction.
Is there some way to get CDR-like data from OpenBSC? Smth like
imsi=123 call_to 35345345 duration 12
imsi=53 sms_from 234234
...
cheers,
Max.
Dear Holger, Alexander, list
In the last couple of weeks we experiencing an issue programmin the SJS1 USIm cards with PySIM.
We can read them, but during programming, a lot of us got the following error:
root@D6420:~/pysim#
root@D6420:~/pysim# ./pySim-read.py -p 0
Reading ...
ICCID: 8988211000000073729
IMSI: 901700000007372
SMSP: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
ACC: 0004
MSISDN: Not available
Done !
root@D6420:~/pysim# ./pySim-prog.py -p 0 -t sysmoUSIM-SJS1 -i 208920000000001 -s 8988211000000073729 -x 208 -y 92 --op=11111111111111111111111111111111 -k 8BAF473F2F8FD09487CCCBD7097C6862 -a 55127679
Insert card now (or CTRL-C to cancel)
Generated card parameters :
> Name : Magic
> SMSP : e1ffffffffffffffffffffffff0581005155f5ffffffffffff000000
> ICCID : 8988211000000073729
> MCC/MNC : 208/92
> IMSI : 208920000000001
> Ki : 8BAF473F2F8FD09487CCCBD7097C6862
> OPC : 8e27b6af0e692e750f32667a3b14605d
> ACC : None
Programming ...
Traceback (most recent call last):
File "./pySim-prog.py", line 626, in <module>
card.program(cp)
File "/root/pysim/pySim/cards.py", line 438, in program
r = self._scc.select_file(['3f00'])
File "/root/pysim/pySim/commands.py", line 44, in select_file
data, sw = self._tp.send_apdu_checksw(self.cla_byte + "a4000002" + i)
File "/root/pysim/pySim/transport/__init__.py", line 87, in send_apdu_checksw
raise RuntimeError("SW match failed ! Expected %s and got %s." % (sw.lower(), rv[1]))
RuntimeError: SW match failed ! Expected 9000 and got 6a86.
root@D6420:~/pysim#
Please note that in this particular case I was trying to reprogram an SJS1 card with a card reader (and the exact command) that was worked in the past, and yet its not working now.
I don't think this is a PySIM error, but more likely a Pyscard or PCSC-lite problem. I tried several Pyscard versions (1.6.10, 1.6.12, 1.6.16. 1.7.0 and 1.9.0) and the it was all the same.
At this point I don't have any more ideas what to try, if anyone would have any suggestions I would apreciate it.
I am certainly not alone with this issue, several folks from OpenAIR and OpenLTE are also having the very same problem.
Regards,
Csaba
I've just noticed that my code cannot handle the same GSN's Ctrl address
handing out differing User plane addresses to various other GSNs. That's
the point of load balancing, after all.
So far I've paired up a Ctrl and a User peer 1:1, that won't do. That and
the reply-to-same-port will make the structures a bit more complex still:
- Each User address has its one managing Ctrl address, but the same Ctrl
address may be used for several User addresses.
- One address can have several ports, and a sequence number that came from
a given port should get its reply with the same sequence number back to
that port (discussion pending?).
~Neels
Here is the fixed OAP patch set of those changes not merged yet.
For decode_big_endian(), see the new API comment and my mail from thursday
night/friday morning.
Thanks for the review!
~Neels
I have configured osmocom openbsc.Everything runs fine.But the configurations do not change
in real time,everytime the system needs to be restarted as changing lac
or cellid in openbsc.cfg file after running the entire setup halts the
osmo-nitb log.I want to change cellid,lac and some other configuration
parameters in runtime as such in openbts so, can you provide some
assistance in this regard?
Any help will be greatly appreciated.
Hey All,
I have configured osmocom openbsc.Everything runs fine.But the configurations do not change
in real time,everytime the system needs to be restarted as changing lac
or cellid in openbsc.cfg file after running the entire setup halts the
osmo-nitb log.I want to change cellid,lac and some other configuration
parameters in runtime as such in openbts so, can you provide some
assistance in this regard?
Any help will be greatly appreciated.
