So far three persons have indicated their interest to join
a meeting at my place.
Considering the time it takes to drive to my place, it
probably makes sense to have the meeting at the weekend
(either Saturday or Sunday) so that there is more time
for the meeting itself. I can suggest one of the following
dates for the first meeting, somewhere between 10:00 to
18:00 on each day:
25.8. (Sa) or 26.8. (Su)
1.9. (Sa) or 2.9. (Su)
8.9. (Sa) or 9.9. (Su)
So please let me know when you have time and also make
suggestions in which Osmocom topic you are interested
in so that we can have some sort of agenda for the
meeting to make best use of the time.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello everyone,
I've just finnished writing together a small web interface for the OpenBSC
HLR. It allows you to modify various parameters in the database and also
provides a set of functions to modify the HLR or sending SMSes in your own
scripts.
The project is still very alpha but it seems to work reasonably good. Feel
free to give any feedback!
Screenshots and source code is available on my website:
https://stormhub.org/simplehlr/
--
*Best regards,
Peter Caprioli*
Hello list,
First of all congratulation to developers of this project making such
wonderful project in an interesting subject. I am new to this project and
for past few days i managed to go through the documentation and get most of
it tested. Thanks for pretty good documentation in most of the areas as
well.
I have the osmo-nitb working very fine using a nano bts.
How ever when i try to install it with LCR to interconnect with external
switch, im facing some problems. Initially i thought i must use
LCR+Asterisk. But later i figured out there is a built in SIP interface on
LCR which there is no need to asterisk or chan_asterisk. I would prefer to
use this LCR SIP interface as i dont want to use asterisk and just want to
forward all calls to another SIP switch.
Now in this context there seems absolutely no documentation on both openbsc
and LCR/mISDN lists.
Can some one please shed me some light here on how to build a LCR with SIP
to be work with osmo-nitb.
All i want to test is
GSM phone > Osmo-nitb > LCR with SIP > SIP softswitch
Thank you very much for every one's effort in this project and would be
glad to see some response for this.
Best Regards
Nava.
Dear Pablo,
getaddrinfo does not work for the combination of AF_INET, SOCK_RAW
and IPPROTO_GRE. I have attached an example application that can be
compiled with:
$ gcc -o fr fr.c `pkg-config --cflags --libs libosmocore libosmogb`
this prints:
getaddrinfo returned NULL: Success
FAILED
gettadrinfo returns -8 which should be this:
# define EAI_SERVICE -8 /* SERVICE not supported for `ai_socktype'. */
I am not sure what is the most clever way to resolve this. Make SOCK_RAW
branch out early and do the socket/bind(/listen) manually, use getaddrinfo
twice with some more unspefici options, just deal with SOCK_RAW differently
now? The attached code has the benefit of at least handling INET and INET6
inside the getaddrinfo result.
any ideas?
holger
Hi guys,
i'm still testing the eap-sim authentication and lately i got acceptable results using
a simple flat file containing the triplets of specific SIM cards. Next step will be to
enable the external radius server to use the sysmoBTS database hlr.sqlite3, so the
OpenBSC users (Users using the OpenBSC-GSM Network) can automatically access
to the internet.
i just want to ask if there are any limitations with the sysmocom SIM cards?
In fact, i noticed that by using the sysmocom sim cards, the eap-sim authentication
failed when the RAND values strong randomly chosen were, e.g
046DBA898016454aB3920C58180DA2F5 or e177842fe16c47de84784be1b4141c27.
But when i chose a RAND like this 10101010101010101010101010101010,
0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F or 00000000000000000000000000000000,
the authentication succeeded.
By using an other sim (not from sysmocom) with the same strong and weak RAND
values the authentication always succeeded.
Why does the authentication succeed buy using sysmocom sim card with weak RAND
(10101010101010101010101010101010) and fail by using strong RAND values
(e177842fe16c47de84784be1b4141c27) ?
best regards
Yann
I have some questions:
1) When I start bsc_hack bsc_init.c first establishes OML link and
initializes the bts then it establishes RSL link and bts starts
broadcasting. However, it takes so much time to start the bts. Instead of
this I want to do the following: it establishes OML link at the beginning
and only once, then when i want to start broadcasting it establishes just
the RSL link and bts will start faster since i don't have to wait for OML
link. What should be done for this?
2) If i send one or two word messages from telnet interface it is okay. But
if i send a longer message the phone could't receive the end of the message
correctly(last words may be incomplete). Did any one encounter with this
problem? What is wrong with me?
3) Could I send SMS in which extension of the sender is text not integer.
For example, i want to send an information SMS that this is a test network.
For this purpose i want to send an SMS from 'OpenBSC'. I set the extension
of the first subscriber in database as text and tried to send the SMS but
SMS wasn't delivered. What should i do?
4) Can i add SMS externally to SMS table of database?
Thanks.
Jason
Hi All
We're selling some of our pico cell stock that has been on our shelf for a few months. We have 1 x brand new model 139 pico cell (1800 MHz GPRS), 1 x model 165g (1800 MHz GPRS/EDGE) and 1 x model 165cu (900 MHz GPRS/EDGE).
These on on offer first come first served.
Kind Regards
Stuart Baggs
Managing Director
BlueWave Communications Limited
Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender immediately . This message contains confidential information and is intended solely for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
Hi Andreas, Harald,
the recent "SI generation" fix broke multi trx setups. This is because
when the first (c0) TRX is going up bts->si_valid will include SI2 and
other SIs scheduled on the BCCH and once the second trx is going up the
code decides it only needs to generate the SI5 (and more).
But si_valid still includes SI2 and it will be set on the second trx. I
have fixed it locally by setting si_valid to 0 early in the set_system_infos
routine and added a warning for this case.
How should this be properly fixed for master? Will the content of a specific
SI differ from TRX0 to TRX1 of a BTS? Should the si_valid be moved to the
trx data structure?
I have attached my local patch and would like to have a review for it.
comments? ideas?
holger
Hey guys i wanted to buy Osmo -NITB is it on sale ??
please let me know
--
Akib Sayyed
Matrix-Shell
akibsayyed(a)gmail.com
akibsayyed(a)matrixshell.com
Mob:- +91-966-514-2243
Hi all,
in case you follow the changelog, you will already have seen this
coming: OsmoNITB now has a SMPP interface for submitting MT-SMS.
This is by no means some kind of competition to a more complete SMSC
developed by other people on this list, but it was a quick solution to
a requirement of a commercial user.
You can use it to submit SMS identifying the recipient subscriber either
by his extension or his IMSI. OsmoNITB will also send SMPP ALERT
NOTIFICATION in case a previously detached subscriber comes online
again. Contrary to the spec, you don't have to subscribe ot ALERT
NOTIFICATIONS, but they will be sent to all ESME's registered.
The SMPP interface supports both store-and-forward (via database) as
well as forward/transactoin mdoe, where the SMS is attempted for
immediate delivery, not buffered and will only send a positive SUBMIT-SM
result in case it was acknowledged by the MS.
You can submit both GSM charset as well as binary messages. UCS2 is not
tested. multi-part SMS (or anything else using UDH) only works with
binary SMS at this point, i.e. GSM alphabet encoded multi-part messages
are broken.
The interface will soon be extended to also cover MO-SMS, where you
would configure a given destination address by VTY and then messages to
that address would be forwarded to the ESME.
Only SMPP 3.4 is currently supported. You will need libsmpp34 from
git://git.osmocom.org/libsmpp34.git and need to build openbsc with
'--enable-smpp'
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)
Hi all,
I have rebased jolly/sms and split it up (first use the routines that were
moved to libosmocore and that create compile errors, then begin to use the
DLSMS debug area, then the actual patches in a way that all of them compile
to allow to bisect them). I am now manually testing them with the help of
the sysmocom modem bank.
There are various issues that needs to be resolved before the 29C3 to be
able to use the code. I am just listing them here for reference.
There is a double trans_free in the new code now that will lead to segfaults
and various 'soft' failures. I am just including some log messages:
gsm0411_smc.c:308 Cannot release yet current state: WAIT_CP_ACK
gsm0411_smc.c:511 Message 0x332/1 unhandled at this state WAIT_CP_ACK.
gsm0411_smc.c:517 RX Unimplemented CP msg_type: 0x332
gsm0411_smc.c:134 TX CP-ERROR, cause 97 (Message Type doesn't exist)
gsm_04_11.c:913 Transaction contains SMS.
gsm_04_11.c:441 RP-DATA (MO) without DST or TPDU ?!?
gsm_04_11.c:420 TX: SMS RP ERROR, cause 96 (Invalid Mandatory Information)
cheers
holger
hi list,
we (ccc meber and me) are trying to get a pri access line (primary rate
isdn) this year. it will provide external connection for the poc
(eventphone) and will also allow interconnection of gsm network with the
rest of the world. it is not yet clear if we get this line, but we are
working on it. the hardware and software side is already tested in our
"labs".
for connection between poc and gsm network (openbsc), we like to use lcr
(linux-call-router via mncc interface). there are two ways to connect to
eventphone, one via isdn line (or virtual isdn over ip) and another one
via sip trunk. we like to use both ways for better testing.
the registration process for gsm extensions is already set up by
evenphone. visit https://www.eventphone.de to register your gsm
extension. for syncing eventphone's database with hlr of openbsc, i can
provide help. also i will provide helpdesk for gsm questions this year
again.
regards,
andreas
Hi All
We've upgraded a couple of our cells to model 165Gs and have the older model 139s we've removed available for sale. They're both in perfect working order and have been used with OpenBSC for a year now.
Thanks
Hi all,
I've been hearing all sorts of rumours about nano- pico- or femto-cells
for sale in California, around $99 capable of G4/LTE.
Does anybody know if that is fact-or-fiction?
If true, might that be something for openbsc?
Hans.
<000f> bsc_api.c:315 Sending ChanModify for speech 1 1
<000c> rtp_proxy.c:258 Correcting frame difference of 38886 frames
I used to get these messages when I make a call using osmo-nitb.
But recently I updated to newest git version and I get something like
<000b> bsc_api.c:374 Sending ChanModify for speech 0 1
<000b> bsc_api.c:118 Using non speech mode: 0
<000b> osmo_msc.c:73 Assignment complete should not have been reached.
And I get no sound for my phones.
There is a year gap between the previous version and the new version, so I
couldn't locate exactly what change is causing this.
Can somebody help me fixing it?
Hi,
as indicated in the previous mail there are some things to be done
before we get to the venue. I would like to experiment with sprints
to solve some of the stability issues we had with osmo-nitb.
The idea is that we assemble (physically or online) and work on some
specific issues of osmo-nitb that impact the quality of service for
the upcoming event. I can provide food and snacks during these sprints
and guidance on OpenBSC code.
The first sprint is scheduled for the 9th, 10th (and maybe 11th) of
November. There is no venue for it yet, maybe the CCCB. Please indicate
if you are interested to join.
The general list of osmo-nitb issues are:
* Channel release process. There is a branch I created at the last
congress but I have never tested it. This includes making a SAPI=3
local release, using the proper timeouts for the abnormal release
making sure the SACCH is deactivated and some more issues. This
requires quite a bit of testing.
* Allow to block/unblock failing lchans. We have had this issue with
Nokia BTS but it can happen on other BTS as well. E.g. a given
timeslot might not be allocatable, or we get LCHAN ACT NACK. In that
case OpenBSC should block the lchan.
* smsqueue/auth/paths. In the past years we have seen that the smsqueue
and other parts can get stuck because of the 'subscr_get_con' not
being properly called in all error conditions. We need to review the
code and check how things get stuck.
* Handover testing and patching out the 'timestamp' adjusting or
fixing it. Right now it can be used to add a lot of delay by switching
cells.
cheers
holger
as for OpenBTS handover, I studied OpenBSC code.
I'm issuing exactly the same handover command, even including the sequence of fields, not only values :)
I'm waiting for the second umTXR back to continue investigating..
Mon, 5 Nov 2012 13:34:33 -0500 от Alexander Chemeris <alexander.chemeris(a)gmail.com>:
>
>
>
>
>Hi Harald,
>
>
On Thu, Nov 1, 2012 at 2:22 PM, Harald Welte <laforge(a)gnumonks.org> wrote:
>
> On Thu, Nov 01, 2012 at 11:33:28AM +0400, Alexander Chemeris wrote:
>
>> Dimitri, we have a working OpenBSC/nanoBTS installation at the hackerspace.
>
>> If you find out how to issue a handover command in OpenBSC, you could try
>
>> by yourself.
>
>
>
> You cannot issue a handover command manually in OpenBSC. The way how we
>
> test handover is to use two BTSs connected to one OsmoNITB, and use
>
> rotary/adjustable attenuators in the Tx path to make one BTS signal
>
> weaker than the other BTS, at which point the handover algorithm will
>
> kick in and perform the hand-over.
>
>
If this is done inside of the OpenBSC, it should be easy to hack a VTY
>
command to force handover. It may be a useful command as well, if you
>
want to do load balancing of your network. Am I missing something?
>
>
> The DMEAS and the DHO debug logging might be useful to monitor what is
>
> happening while you're doing that.
>
>
Thanks.
>
>
--
>
Regards,
>
Alexander Chemeris.
>
CEO, Fairwaves LLC / ООО УмРадио
>http://fairwaves.ru
>
Hi,
I'm implementing handover for OpenBTS project: http://wush.net/trac/rangepublic/wiki/Handover
Some handsets perform handover properly, while the others (such as Nokia) do not appear at the target channel with HandoverAccess.
Handover Command contains the minimal set of parameters that looks reasonable:
-- cellDescription
-- channelDescription
-- handoverReference
-- powerCommand - tried various levels
I'll appreciate real-life traces of handover, non-sync case. As far as I know, this one is used for ipAccess..
Handover Command fields are particularly interesting.
Thank you,
Dmitri
This is a Mailman mailing list bounce action notice:
List: OpenBSC
Member: openbsc(a)slewe.com
Action: Subscription disabled.
Reason: Excessive or fatal bounces.
The triggering bounce notice is attached below.
Questions? Contact the Mailman site administrator at
mailman(a)lists.osmocom.org.
Hi guys,
i'm trying to interconnect a WLAN router with my GSM-sysmoBTS and to use the EAP-SIM authentication protocol. For that i installed a Freeradius on an external board that i use as radius server. The Freeradius should use a database file in order to realise the authentication and the idea is that Freeradius should be able to read the hlr.sqlite3 file from my sysmoBTS. I'm not so far to do this part of the work so, i first want to do some tests using the sim card from sysmoBTS (imsi und ki) and the triplets (RAND, Kc and SRES). I want to create a flat file containing this values so the Freeradius will directly use the file to get the triplets.
I thought i could get the triplets stored in one of the tables of hlr.sqlite3 (AuthLastTuples) but there is no information on it. From the table AuthKeys i could find some Ki values (e.g X'019B7083FBAFC928421A147DE795217782'). I found that there is an "osmo-auc-gen" program for computing the triplets. By using the Ki from AuthKeys and a self generated RAND (e.g 0123456789ABCDEF0123456789ABCDEF) the program doesn't run and doesn't give the triplets. The used authentication algorithm is the COMP128v1.
Has anyone an idea why it doesn't work and why there is no information in the AuthLastTuples table from sysmoBTS ?
best regards
Yann