Hi all,
I have a SysmoISIM-SJA2 which I believe doesn't have a CAT application and
doesn't support the SUSPEND APDU (per the manual). Given that, is there any
way to reset/refresh the card through APDU commands (or through any other
means)? Would something along the lines of deactivating and then
reactivating the USIM application work?
Thanks,
Bryan
Dear Osmocom community,
today our mailing list server lists.osmocom.org has finally been migrated
from mailman2-on-freebsd to mailman3-on-linux. This also included a variety
of changes to DNS. I'll spare you the details, but everything _should_ be up
and running now.
* The List-Id headers should not have changed.
* all list subscriptions + user accounts have been converted.
* old 'static html' archives are still available (read only) at URLs like
https://lists.osmocom.org/pipermail/baseband-devel/
* old List URLs like https://lists.osmocom.org/mailman/listinfo/baseband-devel
are redirected to their respective modern counterparts
In case you notice any mailing list related problem, please don't hesitate to
contact me.
Happy hacking,
Harald
--
- Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
those harmonics) must be above:
-30 dBm @ 30 kHz span above 1 GHz
-36 dBm @ 30 kHz span below 1 GHz
In case of UmTRX without an amplifier it's enough to use a ceramic or
SAW duplexer to bring harmonics below those levels.
For those buying UmTRX's as a lab package of universal UmDESKs, we
offer to buy an external ceramic duplexers. These improves coverage
and solves the out of band noise issues.
For those buying band-specific UmDESK's, we use SAW duplexers, which
are even more efficient in reducing out of band noise.
>> A calibrated USRP N200 running osmo-trx passes RF spectrum and
>> modulation accuracy requirements of 3GPP 05.05 by very large margins
>> and is competitive with commercial GSM equipment in this regard. Other
>> SDR devices are also capable to varying degrees.
>
> The policy of FCC vs. European Union is quite different. There are more
> norms that apply in Europe.
You're obviously more proficient in European norms. Could you point me
to a link where we could find these differences between the ETSI
published GSM Standard and European harmonized norms?
It would be a very good addition to the OpenBSC wiki's "Standards" page.
--=20
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / =D0=9E=D0=9E=D0=9E =D0=A3=D0=BC=D0=A0=D0=B0=D0=B4=D0=
=B8=D0=BE
http://fairwaves.ru
> Anyway, I thought that the GPRS support is part of the OpenBTS
> development, and any hardware that can run OpenBTS is also capable of
> doing GPRS, but it is clear, that there are differences in the level
> of support, even between SDR like devices.
The majority of the code of osmo-pcu has been contributed by or on
behalf of sysmocom. If you take a look at the development of the PCU
for the last 6 months you will clearly see that sysmocom is doing all
the work. Just like with OpenBSC a lot of others benefit from our work
though. ;)
> I still think that it would be nice, to clarify all this packet data
> related stuff on the site.
* When an external protocol changes, the version number needs to
change. I added MNCC protocol versioning as OpenBSC and LCR were
out of sync and then funny things happened. This one line change
of the version number can save you hours in debugging!
* When a new feature is added, ask for a testcase. E.g. specially
the E1 bit fiddling as it is so rarely used that it is likely
to bitrot.
* Check the error paths. Developers tend to only test with a single
phone, not run into error paths, not force them to be taken during
development (faul injection).
* For things like device work-arounds ask if they are really necessary,
e.g. I have my doubts for the RTP timestamp handling.
* General code hygiene. Don't have the action take place four tabs in
in a thousand line code method, don't use magic numbers, don't repeat
yourself etc. Code is read a lot more than it is written. Besides smaller
methods being easier to write unit tests for, they are easier to
understand/review.
I have merged two patches from this patchset but they required multiple
rounds and my spare time is really limited.
cheers
holger
I deduct that
" #if defined(L1_HAS_EFR) && defined(USE_L1_RTP_MODE) "
is why I'm seeing this message logged, but it seems to be #define...
Any pointers, ideas ? This doesn't seem like a configuration thing, but a
compilation time option?
I'd have expected that EFR is fully supported?
osmo-bts.cfg snippet
------------------------------
bts 0
band 850
ipa unit-id 1801 0
oml remote-ip 127.0.0.1
rtp jitter-buffer 100
paging queue-size 200
paging lifetime 0
trx 0
clock-calibration 603
trx-calibration-path (null)
clock-source ocxo
uplink-power-target -75
min-qual-rach -5
min-qual-norm -5
Regards,
Roelf.
--bcaec51b1b6f7f08e204e11a4392
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div>I have FINALLY gotten to play with my sysmoBTS acquired many months ag=
o, and updated to the latest packages using okpg, and am running a NITB.</d=
iv><div><br></div><div>GSM850 test setup in open mode A5/0, and I can SMS a=
nd call between devices.</div>
<div><br></div><div>However, there is no audio, and BTS console logs report=
s many repeats of the following during an established call.</div><div><br><=
/div><0006> tch.c:601 (bts=3D0,trx=3D0,ts=3D7,ss=3D0) Rx Payload Type=
EFR is unsupported<div>
<0006> tch.c:601 (bts=3D0,trx=3D0,ts=3D7,ss=3D0) Rx Payload Type EFR =
is unsupported</div><div><0006> tch.c:601 (bts=3D0,trx=3D0,ts=3D7,ss=
=3D0) Rx Payload Type EFR is unsupported</div><div><br><div><br></div><div>=
about it and demonstrate it operating OpenBTS and OsmoBTS. I could
talk about our open-source development of OpenBTS, if there would be
any interest.
Also I'd love to talk about OsmoBTS/OpenBSC which the new cool. Only
few people heard about OsmoBTS, while it provides great capabilities:
* it works with off-the-shelf SDR transceivers like UmTRX
* it could use VoIP (SIP) soft-switches to connect calls
* it connects to MSCs of legacy GSM networks
* it supports encryption, handover, FR/HR/AMR codecs and GPRS (in beta)
* standards compliant L1/L2 layers, so there are no issues with
various phone models
I love Osmocom approach to development as well - development is open
to all contributors, the code is well structured and tested, even
build results for all sub-projects are available through a continuous
integration suite:
http://jenkins.osmocom.org/jenkins/
On Sat, May 4, 2013 at 9:00 AM, Robin Coxe <coxe(a)close-haul.com> wrote:
> (Apologies for cross-posting. We wanted to reach everyone who might be
> interested in attending. Please respond responsibly.)
>
> Anders Brownworth (Switchcoder), Alexander Chemeris (Fairwaves), and Robi=
n
> Coxe (Close-Haul Communications & Analog Devices) invite those interested=
in
> open GSM hardware and software development to an informal gathering in
> Cambridge, MA on Friday 10 May 2013 from 6-8 pm. Alexander will be visit=
ing
> the Boston area from Moscow.
>
> If you are interested in participating in any capacity in the Boston-area
> open source GSM development community, we look forward to meeting you. O=
ur
> goal is to identify like-minded people involved in or interested in learn=
ing
> more about projects such as OpenBTS, OsmocomBTS, OsmocomBB, and OpenBSC.
> If you have a portable, self-contained demo, feel free to bring it with y=
ou.
>
> When: Friday 10 May 2013, 6-8 pm EDT
> Where: Cambridge Innovation Center, 1 Broadway, 4th Floor, Cambridge, MA
> 02142 USA
> Photo ID required for building entry.
>
> Please RSVP on Eventbrite: http://opengsmboston.eventbrite.com/
>
>
>
>
>
>
>
>
--=20
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / =D0=9E=D0=9E=D0=9E =D0=A3=D0=BC=D0=A0=D0=B0=D0=B4=D0=
=B8=D0=BE
http://fairwaves.ru
keep doing the same style. Good food makes a brain work better.
> Venue-wise, I would again suggest to hold it in Berlin, as it's
> reasonbly well connected, has lots of low-cost flights to it,
> accomodation is not too expensive and holger/me/sysmocom can take care
> of local organization related activities. Hoewver, if somebody has a
> strong opinion against berlin _and_ is willing to organize it, I'm not
> completely against another venue.
Berlin is perfect.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / =D0=9E=D0=9E=D0=9E =D0=A3=D0=BC=D0=A0=D0=B0=D0=B4=D0=
=B8=D0=BE
http://fairwaves.ru
of what if the msgb is 'borrowed' or 'owned/transferred'. Whenever we reach a
_send method we actually transfer the ownership (as the data might be queued
or such).
The other technical part is to make sure we first establish a rule by
1.) adding doxygen/API documentation to the sendmsg function
2.) maybe look into introducing dummy annotations like __borrow, __takes that
we could autocheck in the future (e.g. by extending spaze/smack)
The issue with reviewing such a patch is the question if you have catched
everything. E.g. I think you missed need to convert (and what it calls):
static int gprs_ns_tx(struct gprs_nsvc *nsvc, struct msgb *msg)
{
...
default:
LOGP(DNS, LOGL_ERROR, "unsupported NS linklayer %u\n", nsvc->ll);
msgb_free(msg);
ret = -EIO;
break;
}
return ret;
}
> As reported in ticket #55 SGSN can crash due to double free-ing. You
> can replace 'can' by 'will' in that last phrase. I had a sift through
> the code and tried to solve this by removing the free in gprs_ns.c.
> Whenever the calling function created the msgb-struct, I have made the
> function free it after its use. If the function got the msgb from a
> calling function, there will not be a free (hoping that will be done
> on the higher level).
>
> HTH/F
If you need higher bitrates, implementing header and payload compression
at the SNDCP level in the SGSN is possible.
Also, always keep in mind that while you can offer 7 TS with GPRS/EDGE,
almost no phone has support for a multislot class that allows for 7 TS
in DL. So multiple phones can fill the 7 TS, but it's unlikely one
phone can use all of them.
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)
OpenBSC Startup:
http://pastebin.com/bXEhizAG
moi::states:
http://pastebin.com/9MiRRGP0
In the nano startup - the two things that stand out are the complains
about flag 3 and the NSE:
27855:DBG:OAM_IM:roleInstanceProcClearContaineeFlags: BTS:0 flag 3 not
setting or set!
27855:DBG:OAM_IM:roleInstanceProcClearContaineeFlags: GPRS NSE:0 flag
3 not setting or set!
42142:DBG:GBHSS_STACK:bgp_error_reporter() : PROTO_ERR:
Msg=3DGPRS_BGP_RL_UL_UNITDATA_REQ, Err=3DGPRS_NSEI_NOT_OPERATIONAL
42142:DBG:GBHSS_STACK:bgp_process_msg failed :
msg=3DGPRS_BGP_NM_BVC_RESET_REQ err=3DGPRS_NSEI_NOT_OPERATIONAL
Any thoughts or additional data points I should collect?
Thanks,
Gus
<a href=3D"http://pastebin.com/qLatWdtB" target=3D"_blank">http://pastebin.=
com/qLatWdtB</a><br>
<br>
OpenBSC Startup:<br>
<a href=3D"http://pastebin.com/bXEhizAG" target=3D"_blank">http://pastebin.=
com/bXEhizAG</a><br>
<br>
moi::states:<br>
<a href=3D"http://pastebin.com/9MiRRGP0" target=3D"_blank">http://pastebin.=
com/9MiRRGP0</a><br>
<br>
In the nano startup - the two things that stand out are the complains<br>
about flag 3 and the NSE:<br>
<br>
27855:DBG:OAM_IM:roleInstanceProcClearContaineeFlags: BTS:0 flag 3 not<br>
setting or set!<br>
27855:DBG:OAM_IM:roleInstanceProcClearContaineeFlags: GPRS NSE:0 flag<br>
3 not setting or set!<br>
<br>
42142:DBG:GBHSS_STACK:bgp_error_reporter() : PROTO_ERR:<br>
Msg=3DGPRS_BGP_RL_UL_UNITDATA_REQ, Err=3DGPRS_NSEI_NOT_OPERATIONAL<br>
42142:DBG:GBHSS_STACK:bgp_process_msg failed :<br>
msg=3DGPRS_BGP_NM_BVC_RESET_REQ err=3DGPRS_NSEI_NOT_OPERATIONAL<br>
<br>
Any thoughts or additional data points I should collect?<br>
<br>
Thanks,<br>
<font color=3D"#888888">Gus<br>
<br>
</font></blockquote></div><br>
--00163646d380b12b2004ae744714--
OpenBSC Startup:
http://pastebin.com/bXEhizAG
moi::states:
http://pastebin.com/9MiRRGP0
In the nano startup - the two things that stand out are the complains
about flag 3 and the NSE:
27855:DBG:OAM_IM:roleInstanceProcClearContaineeFlags: BTS:0 flag 3 not
setting or set!
27855:DBG:OAM_IM:roleInstanceProcClearContaineeFlags: GPRS NSE:0 flag
3 not setting or set!
42142:DBG:GBHSS_STACK:bgp_error_reporter() : PROTO_ERR:
Msg=GPRS_BGP_RL_UL_UNITDATA_REQ, Err=GPRS_NSEI_NOT_OPERATIONAL
42142:DBG:GBHSS_STACK:bgp_process_msg failed :
msg=GPRS_BGP_NM_BVC_RESET_REQ err=GPRS_NSEI_NOT_OPERATIONAL
Any thoughts or additional data points I should collect?
Thanks,
Gus
My init.d script does the following in short:
modprobe mISDN_dsp
modprobe mISDN_l1loop nchannel=30 interfaces=2
sleep 1
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -t nat -A POSTROUTING -s 192.168.253.0/24 -o eth0 -j
MASQUERADE
screen -S bsc -d -m su gsm -c "osmo-nitb -d
DRLL:DCC:DMM:DRR:DRSL:DNM:DSMS:DMNSMS:DPAG:DMUX -c /etc/openbsc/openbsc.cfg
-m -P"
screen -S lcr -d -m su gsm -c "/usr/sbin/lcr start"
I'm using mISDN_l1loop.ko from current mISDN git because it was not included
in my kernel. Small patch to make it compile:
--- a/drivers/isdn/mISDN/hwchannel.c
+++ b/drivers/isdn/mISDN/hwchannel.c
@@ -19,6 +19,8 @@
#include <linux/module.h>
#include <linux/mISDNhw.h>
+bool flush_work_sync (struct work_struct *);
+
static void
dchannel_bh(struct work_struct *ws)
{
-- Lennart
--00504502c5d4681bbb04a8fd3d31
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<br><div class=3D"gmail_quote">2011/7/26 Konrad Meier <span dir=3D"ltr"><=
;<a href=3D"mailto:meierk@informatik.uni-freiburg.de">meierk(a)informatik.uni=
-freiburg.de</a>></span><br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I could solve the above problem by a system restart. The mISDN_l1loop modul=
e was loaded but for some reason could not be used by LCR. The LCR error me=
ssage was:<br>
000000 ERROR loop port 1 failed to bind socket. (errno 93)<br>
<br>
<br>
By playing with the mISDN_l1loop module I discovered a strange problem. If =
I load the module with "modprobe mISDN_l1loop pri=3D1 nchannel=3D30&qu=
ot; all system memory is allocated by LCR after some seconds.<br>
<br>
If I load it with "nchannel=3D20" than everithing works fine.<br>
<br>
Can someone confirm this problem?<br>
<br>
Regards<br><font color=3D"#888888">
Konrad<br></font></blockquote><div><br>From my experience, no.<br>My init.d=
script does the following in short: <br><br>=A0=A0=A0=A0=A0=A0=A0 modprobe=
mISDN_dsp<br>=A0=A0=A0=A0=A0=A0=A0 modprobe mISDN_l1loop nchannel=3D30 int=
erfaces=3D2<br>=A0=A0=A0=A0=A0=A0=A0 sleep 1<br>
<br>=A0=A0=A0=A0=A0=A0=A0 echo 1 > /proc/sys/net/ipv4/ip_forward<br>=A0=
=A0=A0=A0=A0=A0=A0 iptables -t nat -A POSTROUTING -s <a href=3D"http://192.=
168.253.0/24">192.168.253.0/24</a> -o eth0 -j MASQUERADE<br><br>=A0=A0=A0=
=A0=A0=A0=A0 screen -S bsc -d -m su gsm -c "osmo-nitb -d DRLL:DCC:DMM:=
DRR:DRSL:DNM:DSMS:DMNSMS:DPAG:DMUX -c /etc/openbsc/openbsc.cfg -m -P"<=
br>
=A0=A0=A0=A0=A0=A0=A0 screen -S lcr -d -m su gsm -c "/usr/sbin/lcr sta=
rt"<br>=A0<br>I'm using mISDN_l1loop.ko from current mISDN git bec=
ause it was not included in my kernel. Small patch to make it compile:<br><=
br>--- a/drivers/isdn/mISDN/hwchannel.c<br>
+++ b/drivers/isdn/mISDN/hwchannel.c<br>@@ -19,6 +19,8 @@<br>=A0#include &l=
t;linux/module.h><br>=A0#include <linux/mISDNhw.h><br><br>+bool fl=
ush_work_sync (struct work_struct *);<br>+<br>=A0static void<br>=A0dchannel=
_bh(struct work_struct *ws)<br>
=A0{<br><br>-- Lennart<br></div></div>
--00504502c5d4681bbb04a8fd3d31--
systems from the same vendor, as it is assumed that these systems have
seen a priori more testing time and are thus more reliable than any
multi-vendor combination has seen/would be.
Should there be a problem, it is also a lot easier and faster to get
support from a vendor, when he can't first try and blame the other
vendors box, or the translator in between. Here, again, risk
management...
While the lock-in is indeed a bad thing, it is still considered the
lesser evil, compared to the effort needed to do q/a testing in mixed
systems on nation-size scale plus R&D for the translators plus
battling for support with N competing vendors, all blaming each other.
This is the oh-so-familiar argument on why many companies use
exclusively Microsoft, or everything Apple, etc...
Just my 0.05 chf on why translators did not happen... (yet?)
Cheers,
Thomas
--=20
Excercise 17:
If the human brain was simple enough for us to understand we'd be so
simple we couldn't understand.
Prove this by induction.
Sure, it would be a nice addition, but it's not something that I consider
extremely important. With regard to 'near future': I would say that in
something like six months the osmo-bts (BTS-side A-bis) code will have matured,
and is ready for an relaatively painless integration with OpenBTS.
I personally think the USRP hardware cost is still way too high, and I would
rather want to work on something that puts the financial entrance barrier to
private BTS ownership much lower.
Most of the people using OpenBSC today either use it commercially (and can
afford the nanoBTS units), or they use it private and either with a very
cheap second hand nanoBTS, or with a inexpensive BS-11. The recent work
on supporting the RBS2308 that can be found for < 1000 USD goes into the
same direction.
I think whatever hardware will be affordable to hackers will see OpenBSC
support - just as well as any hardware where we have a commercial customer
will get OpenBSC support.
> > This is where I don't get you. All that needs to be removed is the L3-to-SIP
> > bridge. It doesn't make the vast majority of OpenBTS code disappear,
> > and it does not render that latter part useless. A full-blown GSM network with
> > all its components brings a lot of complexity. The stand-alone OpenBTS is
> > much more simple. And why would you want all the complexity if you don't
> > need to interoperate with legacy GSM?
>
> Well, because the the osmocom-integrated version will be, before or
> later, more full-featured than OpenBTS standalone.
>
> Features such as multi-arfcn, handover, maybe GPRS/EDGE will be usable
> only jointly with Osmocom integration but not by the opensource OpenBTS
> standalone version.
If you use the USRP hardware (or any other SDR hardware), you cannot use
GPRS/EDGE whether you use Osmocom + OpenBTS or OpenBTS standalone. As for
hand-over, you may be right, but I don't know the OpenBTS plans here.
Multi-ARFCN: This is an aspect of the radio-modem. So again, on the same
hardware any OpenBTS/OpenBSC integration will not change this.
> Obviously the community will then use the OpenBTS/OpenBSC integration
> that would reach more features than just OpenBTS in the opensource edition.
well, but you loose the important 'simplicity' feature. Right now I doubt
there are that many people in our community who understand OpenBSC and the
GSM/GPRS network architecture enough to deploy a network (like the burning man
or CCC event networks) with it. We have close to zero documentation, and
unless you know GSM protocol details, you are lost. VoIP is much better
understood in the FOSS and Internet community!
> So the integrated code will grow while the "OpenBTS commercial code"
> will leave behind with less features and more buggy code (because less
> used).
you are making assumptions here. Do you have evidence or at least some
other indication that bug fixes are not being propagated from the commercial
to the free version?
> Osmocom and it's possible future changes to the market of GSM
> technologies could be defined as "the WikiLeaks of the GSM Industry" :-)
I think this is a very bad comparison. We do not leak any proprietary/secret
information. We just break the ignorance of the Free Software community to
ever implement any of those openly-specified protocols. Not different from
Free Software entering any other area of technology.
And while we're doing that, we of course also like to challenge the ridiculous
claims of hundred-man-year efforts that allegedly went into some proprietary
GSM protocol stack implementations, which are often claimed by the existing
carrier equipment industry.
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)
> Meanwhile, Andreas Eversberg has been working on a BTS-side A-bis implementation
> for the OsmocomBB-BTS (idea: using 2 heavily modified phones to run a
> simplistic BTS), and I have started to split that code out into a separate
> repository at http://cgit.osmocom.org/cgit/osmo-bts/
>
> This code should eventually be used with the OpenBTS, and potentially other
> BTS types, too.
That's cool!!!!
>
>> With that approach the 'GSM-um' interface would be a very simplified
>> module of the overall system and osmocom would completely replace
>> OpenBTS all-in-one project.
>
> This is where I don't get you. All that needs to be removed is the L3-to-SIP
> bridge. It doesn't make the vast majority of OpenBTS code disappear,
> and it does not render that latter part useless. A full-blown GSM network with
> all its components brings a lot of complexity. The stand-alone OpenBTS is
> much more simple. And why would you want all the complexity if you don't
> need to interoperate with legacy GSM?
Well, because the the osmocom-integrated version will be, before or
later, more full-featured than OpenBTS standalone.
Features such as multi-arfcn, handover, maybe GPRS/EDGE will be usable
only jointly with Osmocom integration but not by the opensource OpenBTS
standalone version.
Obviously the community will then use the OpenBTS/OpenBSC integration
that would reach more features than just OpenBTS in the opensource edition.
That means that in few times only the "integrated code" will works
better, because it will attract more user and will start getting used in
"production environment".
So the integrated code will grow while the "OpenBTS commercial code"
will leave behind with less features and more buggy code (because less
used).
That's why i just think that the destinity of OpenBTS is to integrate
(directly or just some piece) with OpenBSC, but doing that it will loose
several important value of the "OpenBTS commercial edition" and people
will start using what can be used for free instead of paying.
That's what usually happen within the opensource environment, before or
later.
It could reasonably happen also with that opensource gsm environment.
My comments was just consideration on this to stimulate the
considerations on this by the various project players.
I am just an opensource advocacy troll that like telephony stuff and
perceive very valuable the achievement of the hacking community in
opening a closed technology like GSM.
Osmocom and it's possible future changes to the market of GSM
technologies could be defined as "the WikiLeaks of the GSM Industry" :-)
-naif
p.s. i have no commercial interests of any kind in that stuff
is not in the TLV table and this explains why we end up here. It might be a
good opportunity to see what else we are missing.
>
> BTW, the output of the patch is in git format, so I think that you can
> apply it with git am. It's the inner patch (which is contained inside
> this patch) that it's in svn format 8-).
Yes, I am talking about git am -3 for the inner part as this (wireshark svn)
is the place where having a three way merge is going to be the most useful
thing to do. :)
have a similar situation (see how OpenBTS folks managed to get licenses for
their burining man tests).
> - Is there some part of the official gsm bands that overlaps with local ISM
> or other not-so-tightly-regulated frequencies?
> (i.e, GSM1900 seems to have a small part that's not used by DECT...)
This is a rumour. Only one of the uplink/downlink bands is in there, so you
will still need a test license. Also, AFAIK the DECT band is not everywhere
unlicensed for any kind of application, but actually restricted to be used with
the DECT system.
> - Are there any "standard" gsm handsets that could be modified (preferably
> in software) to work at 2,4GHz?
no.
> - Is UMA/GAN (http://en.wikipedia.org/wiki/Generic_Access_Network) something
> that could be used with OpenBSC? As far as i understand the specification,
> UMA is GSM Layer 3 over an GPRS/IPSEC tunnel to the BSC, so all the
> GSM-Goodies should be there.
You would have to implemet a UMA gateway and somehow glue that to the layer3
inside OpenBSC. I don't think you can do it cleanly with the current code.
Later this year, once the new "real MSC" codebase emerges, this might be easier.
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)
understand that we only have to configure the Unit-id and Oml Address right
and I understand that the firmware is already installed .
I have tried the following :
ipaccess-config -f FIRMWARE -w
and sure it doesn't work :) .
And I also read the -w argument options that needs to be used to download
the firmware from BTS into debian system it should be used with -f .
Is it necessary to download it into our linux box or you need to configure
it only as it is already installed into BTS from ipaccess company .
Thanks,
Omar Atia
-----Original Message-----
From: openbsc-bounces(a)lists.osmocom.org
[mailto:openbsc-bounces@lists.osmocom.org] On Behalf Of Peter Hasse
Sent: Wednesday, January 19, 2011 12:14 PM
To: openbsc(a)lists.osmocom.org
Subject: Re: How to run openbsc on nanoBTS
On 19.01.2011 06:16, Ravi Shankar wrote:
> Dear sir
Hi Ravi
>
> I am new to openbsc.I have two NanoBTS(165cu).I'm facing some
> difficulty which I'm summarizing below
> I'm using Ubuntu10.04
> 1) Can we proceed with one nanobts.?
Yes, in fact i would recommend to start with one and if you get familar
with openbsc you can add more bts.
> 2)I've configured bts ip,unit id, oml ip of one bts.But not able to
> get the firmware.
Check out ipaccess-config util from the openbts source. You can download
the firmware out of the bts you have configured.
> How to get it and configure for NanoBTS??
nanoBTS is a different project and based on the USRP. checkout
openbts.org to get further informations.
>
> 3)how to run openbsc ??
http://openbsc.osmocom.org/trac/wiki/BscHack
>
> Please suggest the procedure to run the openbsc.
>
> Thanks
mfg derPeter
seems weird:
> but bts1 tells that:
>
> LMT LOGON: ACK
>
> PHASE: 3 Normal MBCCU0: No Load MBCCU1: Load
^^^^^
you have no software in TRX0!!
> PLL Set Value=1042, Work Value=1221
this is not good. your clock seems to be very far off, probably you have not
been running it in pll standalone mode at some point in the past. However,
this is unrelated to your E1 problems. The only consequence of this is that
phones might not see your BTS.
> SITE MANAGER ATTRIBUTES:
> E1 Channel: Port=1 Timeslot=17 (Full Slot)
> TEI: 25
This is the weird part. Why would the E1 channel of the site manager run on
Port=1? That is the not connected port of this BTS. It must run on Port=0.
> BS11 Power Amplifier 0 ATTRIBUTES:
> TRX Power: 2W (GSM)
I strongly recommend you do your testing with something like 30mW power limits,
unless you have a faraday cage and/or 2W-capable termiators.
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)
Number of symbols in a burst =3D 156.25 symbols, and burst time 156.25 x<br=
>
3.69... =3D 576,92=ECs<br>
Number of symbols in TDMA frame is 8 x 156.25 =3D 1250 symbols,<br>
Number of symbols in Multiframe is 26 x 1250 symbols.<br>
<div><div></div><div class=3D"h5"><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
On Fri, Jan 7, 2011 at 8:51 AM, Nataraju A B <<a href=3D"mailto:nataraju=
ab.tech(a)gmail.com">natarajuab.tech(a)gmail.com</a>> wrote:<br>
><br>
> Hi Andreas,<br>
> Thanks for the speedy reply.<br>
> The link which sent you is=A0definitely=A0useful. But the very basic q=
uestion I wanted to get a clarification was that, what is the drive behind =
selection of burst time to be 577us.<br>
> For example the audio frequency can range upto 4Khz. The sampling freq=
uency should be 8Khz. If each sample is of 8 bit accuracy. This lead to 64K=
bits of data. ...... =A0If we explore further on these lines we should be =
able to correlate to the time 577us for each burst.<br>
> I wanted some more info these lines. What was/were the drives behind s=
election of this burst time. Otherwise what are the other end requirements =
led to selection of this burst time and in turn TDMA frame hierarchy.<br>
> Thanks,<br>
> Nataraju A B<br>
> On Fri, Jan 7, 2011 at 7:01 PM, Andreas.Eversberg <<a href=3D"mailt=
o:Andreas.Eversberg@versatel.de">Andreas.Eversberg(a)versatel.de</a>> wrot=
e:<br>
>><br>
>> in addition:<br>
>><br>
>> Traffic Multiframe Structures - The 26 traffic multiframe structur=
e is<br>
>> used to send information on the traffic channel. The 26 traffic<br=
>
>> multiframe structure is used to combine user data (traffic), slow<=
br>
>> control signaling (SACCH), and idle time period. The idle time per=
iod<br>
>> allows a mobile device to perform other necessary operations such =
as<br>
>> monitoring the radio signal strength level of a beacon channel fro=
m<br>
>> other cells. The time interval of a 26 frame traffic multiframe is=
6<br>
>> blocks of speech coder data (120 msec).<br>
>> (<a href=3D"http://www.althos.com/tutorial/GSM-tutorial-frame-stru=
cture.html" target=3D"_blank">http://www.althos.com/tutorial/GSM-tutorial-f=
rame-structure.html</a>)<br>
>><br>
>> one encoded speech block lasts 20ms.<br>
>><br>
>><br>
>> =A0 =A0 =A0 =A0576,92307692307692307692307692308us per slot<br>
>> =A0 =A0 =A0 =A04615,3846153846153846153846153846 per 8 slots (1 fr=
ame)<br>
>> =A0 =A0 =A0 =A0120ms per 26 frames (6 speech blocks)<br>
>><br>
>><br>
>><br>
><br>
><br>
><br>
> --<br>
> Thanks,<br>
> Nataraju A B<br>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>Thanks,<div=
>Nataraju A B</div><br>
--00163641691bea689c04996d367c--
Number of symbols in a burst =3D 156.25 symbols, and burst time 156.25 x
3.69... =3D 576,92=ECs
Number of symbols in TDMA frame is 8 x 156.25 =3D 1250 symbols,
Number of symbols in Multiframe is 26 x 1250 symbols.
On Fri, Jan 7, 2011 at 8:51 AM, Nataraju A B <natarajuab.tech(a)gmail.com> wr=
ote:
>
> Hi Andreas,
> Thanks for the speedy reply.
> The link which sent you is=A0definitely=A0useful. But the very basic ques=
tion I wanted to get a clarification was that, what is the drive behind sel=
ection of burst time to be 577us.
> For example the audio frequency can range upto 4Khz. The sampling frequen=
cy should be 8Khz. If each sample is of 8 bit accuracy. This lead to 64K bi=
ts of data. ...... =A0If we explore further on these lines we should be abl=
e to correlate to the time 577us for each burst.
> I wanted some more info these lines. What was/were the drives behind sele=
ction of this burst time. Otherwise what are the other end requirements led=
to selection of this burst time and in turn TDMA frame hierarchy.
> Thanks,
> Nataraju A B
> On Fri, Jan 7, 2011 at 7:01 PM, Andreas.Eversberg <Andreas.Eversberg@vers=
atel.de> wrote:
>>
>> in addition:
>>
>> Traffic Multiframe Structures - The 26 traffic multiframe structure is
>> used to send information on the traffic channel. The 26 traffic
>> multiframe structure is used to combine user data (traffic), slow
>> control signaling (SACCH), and idle time period. The idle time period
>> allows a mobile device to perform other necessary operations such as
>> monitoring the radio signal strength level of a beacon channel from
>> other cells. The time interval of a 26 frame traffic multiframe is 6
>> blocks of speech coder data (120 msec).
>> (http://www.althos.com/tutorial/GSM-tutorial-frame-structure.html)
>>
>> one encoded speech block lasts 20ms.
>>
>>
>> =A0 =A0 =A0 =A0576,92307692307692307692307692308us per slot
>> =A0 =A0 =A0 =A04615,3846153846153846153846153846 per 8 slots (1 frame)
>> =A0 =A0 =A0 =A0120ms per 26 frames (6 speech blocks)
>>
>>
>>
>
>
>
> --
> Thanks,
> Nataraju A B
" Raw mode
cfmakeraw() sets the terminal to something like the "raw" mode of the
old Version 7 terminal driver: input is available character by charac‐
ter, echoing is disabled, and all special processing of terminal input
and output characters is disabled. The terminal attributes are set as
follows:
termios_p->c_iflag &= ~(IGNBRK | BRKINT | PARMRK | ISTRIP
| INLCR | IGNCR | ICRNL | IXON);
termios_p->c_oflag &= ~OPOST;
termios_p->c_lflag &= ~(ECHO | ECHONL | ICANON | ISIG | IEXTEN);
termios_p->c_cflag &= ~(CSIZE | PARENB);
termios_p->c_cflag |= CS8;
"
If that is set on the socket for the telnet interface it does make a difference.
GSM handset like the Motorola C123 and talk to GSM-R BTSs. Of course you still
need to implement the GSM-R specific features on layer 3 like ASCI.
In both cases I think the hardware is there for whoever has a serious interest in
experimenting with this technology, and who is not afraid to implement the GSM-R
specific bits.
--
- 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)
but not the new.
But in any case, the OP can fix the sql. The OP seem to have a
new/more picky version of sqlite. Before in case of ambiguous column
name, it took the one from the first table in the FROM list. (not sql
standard but that's why it didn't matter before).
> Could you also give us the "old" and "new" git hashes so we can take a
> look at what changed?
The hash (short) are in the version string, the log is :
git log b938..f7a1c
Sylvain
'type' used and the corresponding codec.
For GSM FR the RFC specifies PT=3 but for HR/EFR/AMR, they are dynamic and
must be chosed in the 96-127 range.
AFAIK, we could just use a static mapping in openbsc or load that from the
config. Does anyone sees a downside to that ?
Sylvain
--000325564d6aac09c2047af385f6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Hi,<br><br>I have a nanobts unit 139 with a software that somehow only acce=
pts GSM FR (and not EFR), unless I also send the RTP payload type IE ( RSL_=
IE_IPAC_RTP_PAYLOAD ) in the CRCX and MDCX messages. (and only the "RT=
P payload type" IE, the "RTP payload type 2" has no effect I=
can see).<br>
<br>From the ip.access dissector, I think it's just a mapping between t=
he RTP 'type' used and the corresponding codec.<br><br>For GSM FR t=
he RFC specifies PT=3D3 but for HR/EFR/AMR, they are dynamic and must be ch=
osed in the 96-127 range.<br>
AFAIK, we could just use a static mapping in openbsc or load that from the =
config. Does anyone sees a downside to that ?<br><br>=C2=A0=C2=A0=C2=A0 Syl=
vain<br><br>
--000325564d6aac09c2047af385f6--
messages in 12.21 are simply used to communicate state changes ?!?
--
- 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)
updating/running the most recent version.
> For me now, it's still much easier to debug in windows than in Linux, because
> I'm not yet comfortable with gdb in comman-line.
There are GUI frontends for gdb, including the old "ddd" as well as modern
bloatware like eclipse ;)
--
- 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)
"The requirements yielded by the page mode information element are as
follows:
a) normal paging: no additional requirements;
b) extended paging: the mobile station is required in addition to receive
and analyse the next but one message on the PCH;
c) paging reorganization: The mobile station shall receive all messages on
the CCCH regardless of the BS-AG-BLKS-RES setting. It is required to receive
all BCCH messages. When the mobile station receives the next message to its
(possibly new) paging subgroup the subsequent action is defined in the page
mode information element in that message.
d) same as before: No change of page mode from the previous page mode."
I think the paging reorganization mode is fine. Does anyone know this mode?
I don't know if the mobile phone will answer everytimes if i try to do a
paging on it for each successive frame. Or if he will answer the first time
and ignore the other paging requests after.
In addition, this solution enable the cell phone to listen every frames of
the CCCH but I don't know if the BTS is abble to do a paging on the same
mobile phone on every frames or if it still needs to follow the BS_PA_MFRMS
parameter. I saw that the paging group is calculated from the IMSI. And then
the paging block is calculated. Is it calculated in the BTS or in OpenBSC?
link of the explanation on the paging :
http://etutorials.org/Mobile+devices/gprs+mobile+internet/Chapter+5+Radio+I…
Thanks
Best regards
Eric Cathelinaud
2009/7/15 Eric Cathelinaud <e.cathelinaud(a)googlemail.com>
> 2009/7/15 Dieter Spaar <spaar(a)mirider.augusta.de>
>
> Hello Eric,
>>
>> On Wed, 15 Jul 2009 11:00:14 +0200, "Eric Cathelinaud" <
>> e.cathelinaud(a)googlemail.com> wrote:
>> >
>> > I was just thinking about performing a recursive paging in order to see
>> how
>> > much time I have until the battery of a mobile phone run out.
>> > Does anyone know if the mobile phone answers at every paging or if it
>> > doesn't "listen" all the time? I think it listens periodically. If
>> anyone
>> > can give me a clue, that would be appreciated.
>>
>> This is an excerpt from a posting to another mainling list, I just
>> quote it because I don't want to repeat what I already wrote:
>>
>> > - The phone is in "idle" mode (no speech/data traffic)
>> > and periodically receives the paging channel (PCH) to
>> > find out if its being called. Further the phone measures
>> > the signal strength of neighbor cells and every now
>> > and then (not that frequent as the above actions)
>> > receives the cell information in the broadcast common
>> > control channel (BCCH) of the serving cell and of
>> > at most six neighbor cells with the strongest signal.
>>
>> ....
>>
>> > - The time between receiving the PCH is determined by a
>> > parameter of the serving cell (BS_PA_MFRMS, range 2 to 9).
>> > Its measured in 51-multiframes until the PCH for the phone
>> > repeats (if you want to know the details have a look at
>> > the GSM specs ;-) . The length of a 51-multiframe is
>> > 235.8 ms, this means the time between receiving the PCH
>> > is in the range 471.9 ms to 2122.2 ms. In this time the
>> > idle phone most of the time sleeps or receives the BCCH
>> > of the serving cell or one of the neighbor cells with
>> > the strongest signal (at most six).
>>
>> Best regards,
>> Dieter
>> --
>> Dieter Spaar, Germany spaar(a)mirider.augusta.de
>>
>
> Thanks a lot for the explanation. It's a pity that the minimum period is 2
> multiframes. I wish I could realize a paging on a mobile phone every frame
> but it seems to be impossible finally.
>
> Best regards,
> Eric Cathelinaud
>
>
--001636499281749655046ed2de53
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Hi,<br><br>Finally I think I find a solution to make the cell phone listeni=
ng to every frames of the CCCH.<br><br>From gsm04_08:<br><meta http-equiv=
=3D"Content-Type" content=3D"text/html; charset=3Dutf-8"><meta name=3D"Prog=
Id" content=3D"Word.Document"><meta name=3D"Generator" content=3D"Microsoft=
Word 11"><meta name=3D"Originator" content=3D"Microsoft Word 11"><link rel=
=3D"File-List" href=3D"file:///C:%5CTmp%5Cmsohtml1%5C01%5Cclip_filelist.xml=
"><style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0cm;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
p.MsoList, li.MsoList, div.MsoList
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:14.15pt;
margin-bottom:.0001pt;
text-indent:-14.15pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
p.B1, li.B1, div.B1
{mso-style-name:B1;
mso-style-parent:Liste;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:28.4pt;
margin-bottom:.0001pt;
text-indent:-14.2pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
@page Section1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;
mso-header-margin:36.0pt;
mso-footer-margin:36.0pt;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
</style>
<p class=3D"MsoNormal">"The requirements yielded by the page mode info=
rmation
element are as follows:</p>
<p class=3D"B1">a)<span style=3D"">=A0 </span>normal paging: no
additional requirements;</p>
<p class=3D"B1">b)<span style=3D"">=A0 </span>extended paging: the
mobile station is required in addition to receive and analyse the next but =
one
message on the PCH;</p>
<p class=3D"B1">c)<span style=3D"">=A0 </span>paging reorganization: The
mobile station shall receive all messages on the CCCH regardless of the
BS-AG-BLKS-RES setting. It is required to receive all BCCH messages. When t=
he
mobile station receives the next message to its (possibly new) paging subgr=
oup
the subsequent action is defined in the page mode information element in th=
at
message.</p>
<p class=3D"B1">d)<span style=3D"">=A0 </span>same as before: No change
of page mode from the previous page mode."</p>
<br>I think the paging reorganization mode is fine. Does anyone know this m=
ode? I don't know if the mobile phone will answer everytimes if i try t=
o do a paging on it for each successive frame. Or if he will answer the fir=
st time and ignore the other paging requests after.<br>
<br>In addition, this solution enable the cell phone to listen every frames=
of the CCCH but I don't know if the BTS is abble to do a paging on the=
same mobile phone on every frames or if it still needs to follow the BS_PA=
_MFRMS parameter. I saw that the paging group is calculated from the IMSI. =
And then the paging block is calculated. Is it calculated in the BTS or in =
OpenBSC?<br>
link of the explanation on the paging :<br><a href=3D"http://etutorials.org=
/Mobile+devices/gprs+mobile+internet/Chapter+5+Radio+Interface+RLC+MAC+Laye=
r/Listening+to+MS+Paging+Blocks/">http://etutorials.org/Mobile+devices/gprs=
+mobile+internet/Chapter+5+Radio+Interface+RLC+MAC+Layer/Listening+to+MS+Pa=
ging+Blocks/</a><br>
<br>Thanks<br>Best regards<br><br>Eric Cathelinaud<br><br><div class=3D"gma=
il_quote">2009/7/15 Eric Cathelinaud <span dir=3D"ltr"><<a href=3D"mailt=
o:e.cathelinaud@googlemail.com">e.cathelinaud(a)googlemail.com</a>></span>=
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class=3D"gma=
il_quote">2009/7/15 Dieter Spaar <span dir=3D"ltr"><<a href=3D"mailto:sp=
aar(a)mirider.augusta.de" target=3D"_blank">spaar(a)mirider.augusta.de</a>><=
/span><div>
<div></div><div class=3D"h5"><br><blockquote class=3D"gmail_quote" style=3D=
"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padd=
ing-left: 1ex;">
Hello Eric,<br>
<div><br>
On Wed, 15 Jul 2009 11:00:14 +0200, "Eric Cathelinaud" <<a hre=
f=3D"mailto:e.cathelinaud@googlemail.com" target=3D"_blank">e.cathelinaud@g=
ooglemail.com</a>> wrote:<br>
><br>
> I was just thinking about performing a recursive paging in order to se=
e how<br>
> much time I have until the battery of a mobile phone run out.<br>
> Does anyone know if the mobile phone answers at every paging or if it<=
br>
> doesn't "listen" all the time? I think it listens period=
ically. If anyone<br>
> can give me a clue, that would be appreciated.<br>
<br>
</div>This is an excerpt from a posting to another mainling list, I just<br=
>
quote it because I don't want to repeat what I already wrote:<br>
<br>
> =A0- The phone is in "idle" mode (no speech/data traffic)<br=
>
> =A0 =A0and periodically receives the paging channel (PCH) to<br>
> =A0 =A0find out if its being called. Further the phone measures<br>
> =A0 =A0the signal strength of neighbor cells and every now<br>
> =A0 =A0and then (not that frequent as the above actions)<br>
> =A0 =A0receives the cell information in the broadcast common<br>
> =A0 =A0control channel (BCCH) of the serving cell and of<br>
> =A0 =A0at most six neighbor cells with the strongest signal.<br>
<br>
....<br>
<br>
> =A0- The time between receiving the PCH is determined by a<br>
> =A0 =A0parameter of the serving cell (BS_PA_MFRMS, range 2 to 9).<br>
> =A0 =A0Its measured in 51-multiframes until the PCH for the phone<br>
> =A0 =A0repeats (if you want to know the details have a look at<br>
> =A0 =A0the GSM specs =A0;-) . The length of a 51-multiframe is<br>
> =A0 =A0235.8 ms, this means the time between receiving the PCH<br>
> =A0 =A0is in the range 471.9 ms to 2122.2 ms. In this time the<br>
> =A0 =A0idle phone most of the time sleeps or receives the BCCH<br>
> =A0 =A0of the serving cell or one of the neighbor cells with<br>
> =A0 =A0the strongest signal (at most six).<br>
<br>
Best regards,<br>
=A0Dieter<br>
<font color=3D"#888888">--<br>
Dieter Spaar, Germany =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <=
a href=3D"mailto:spaar@mirider.augusta.de" target=3D"_blank">spaar(a)mirider.=
augusta.de</a><br>
</font></blockquote></div></div></div><br>Thanks a lot for the explanation.=
It's a pity that the minimum period is 2 multiframes. I wish I could r=
ealize a paging on a mobile phone every frame but it seems to be impossible=
finally.<br>
<br>Best regards,<br><font color=3D"#888888">Eric Cathelinaud<br><br>
</font></blockquote></div><br>
--001636499281749655046ed2de53--
Hi,
I'm wondering if anyone has a pcap file containing an Iu (or Iuh)
interface protocol trace of a classic 3G circuit-switched video call
around?
I would be curious particularly in the user plane side, i.e. showing
the RTP with IuUP for video calls. But I presume the RAB assignments
are also going to be interesting...
I know Dieter used to play with 3G CS video with one of his handset testers.
Hoewver, I doubt that device would have any Iu interface internally, so this
will unlikely provide any help here :/
Thanks in advance,
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 community,
It's my pleasure to announce the next OsmoDevCall at
December 10, 2021 at 20:00 CET
at
https://meeting4.franken.de/b/har-xbc-bsx-wvs
This meeting will have the following schedule:
20:00 meet + greet
20:10 presentation "osmo-dev and running Osmocom TTCN3 tests suites locally" by osmith
21:00 unstructured supplementary social event [*]
Attendance is free of charge and open to anyone with an interest
in Osmocom or open source cellular technologies.
More information about OsmoDevCall, including the schedule
for further upcoming events can be found at
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall
Looking forward to meeting you on Friday.
Best regards,
Harald
[*] this is how we started to call the "unstructured" part of osmocom
developer conferences in the past, basically where anyone can talk about
anything, no formal schedule or structure.
--
- Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi Osmocom,
I'm trying to integrate the FreeSwitch as my external MNCC in my test lab using split stack. Currently, I'm getting an error message on FreeSwitch SIP/2.0 400 Missing Contact Header. I'm little bit confused with the error and I don't know where to troubleshoot this.
I've attached my osmo configurations and pcap trace for your reference. Hoping for your reply. Thank you.
Regards,
Justin Mark Repollo
Hello all!
I'm sorry for a stupid question, but I can't find an answer by myself.
We are using Osmocom solution in University to demonstrate to students
how GSM works.
We have and fully virtualized workplaces with osm-bts-virtual and
osmocom-bb UE via virtual Um.
We are making an IMSI Attach procedure and capturing traces with
wireshark. Virtual Um messages are visible in wireshark traces with
"gsmtap" filter. According standart description, after RACH request UE
should receive channel assignment via AGCH channel. But AGCH is not
visible in traces. Am I wrong in my expectations somewhere? I tried to
filter out messages, tried to filter gsmtap.chan_type == 4 but still
no luck.
Thank you
Vania
Dear Osmocom community,
It's my pleasure to announce the next OsmoDevCall at
November 25, 2021 at 20:00 CET (yes, Thursday instead of Friday this time!)
at
https://meeting4.franken.de/b/har-xbc-bsx-wvs
This meeting will have the following schedule:
20:00 meet + greet
20:10 presentation "Control/User Plane Separation (CUPS) + PFCP" by laforge
21:00 unstructured supplementary social event [*]
Attendance is free of charge and open to anyone with an interest
in Osmocom or open source cellular technologies.
More information about OsmoDevCall, including the schedule
for further upcoming events can be found at
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall
Looking forward to meeting you on Friday.
Best regards,
Harald
[*] this is how we started to call the "unstructured" part of osmocom
developer conferences in the past, basically where anyone can talk about
anything, no formal schedule or structure.
--
- Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Dear all,
I am pleased to announce new tagged releases for Osmocom Cellular
Network Infrastructure components.
Find more information about the release here [1].
Osmocom "Latest" repositories in OBS [2] should already contain packages
for the new versions.
OpenEmbedded related meta-layers such as meta-telephony usual
stable/testing branch "201705" [3] have also been updated to build
recipes for new versions.
Regards,
Pau
[1] https://osmocom.org/news/152
[2] https://osmocom.org/projects/cellular-infrastructure/wiki/Latest_Builds
[3] https://git.osmocom.org/meta-telephony/log/?h=201705
--
- Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
Dear Osmocom community,
It's my pleasure to announce the next OsmoDevCall at
November 12, 2021 at 20:00 CET
at
https://meeting4.franken.de/b/har-xbc-bsx-wvs
This meeting will have the following schedule:
20:00 meet + greet
20:10 presentation "E1 / TDM / PDH / SDH basics" by laforge
20:30 presentation "icE1usb in practice" by tnt
later USSE: unstructured supplementary social event [*]
Attendance is free of charge and open to anyone with an interest
in Osmocom.
More information about OsmoDevCall, including the schedule
for further upcoming events can be found at
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall
Looking forward to meeting you on Friday.
Best regards,
Harald
[*] this is how we started to call the "unstructured" part of osmocom
developer conferences in the past, basically where anyone can talk about
anything, no formal schedule or structure.
--
- Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Dear Osmocom users,
the Linux kernel developers are considering to remove mISDN from the
kernel, as can be seen in posts like
https://marc.info/?l=linux-netdev&m=163636911918302&w=2
They are aware that Osmocom still supports mISDN, but it would of course
be interesting if anyone is actually still using this approach.
I've switched to DAHDI a long time ago (4- and 8-port cards for PCIe
available) and only used mISDN very early on with the HFC-E1 in the
2008-2011 timeframe.
These days, I'm using both DAHDI and icE1usb.
IMHO, mISDN based interface cards are becomming less and less
attractive, as the chips only support parallel PCI bus and I've never
seen cards with more than two ports.
So the point of this post is to find out if anyone still is using
[or planning to use] mISDN. If so, please let me, netdev + Anrd Bergmann
know about it.
Basically it is kind of a "speak now or forever hold your peace" kind of
moment, as mISDN would then likely be phased out from mainline Linux.
Even in that case I think libosmo-abis should keep mISDN support, as
there will be Linux systems on older kernels for many years to come, and
the mISDN support doesn't hurt the rest of our code base in any way.
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,
i recently noticed that the `export` command from pysim-shell is failing on some basic files like EF.ICCID.
However if i manually select the file it can be read. This happens on a generic USIM and on the orange sysmousim-SJS1.
see the logs below to illustrate.
Cheers
Bjoern
sysmo usim:
<..snip..>
################################################################################
# Export summary #
################################################################################
# total files visited: 165
# bad files: 75
# MF/EF.DIR, string indices must be integers
# MF/EF.ICCID, string indices must be integers
<...snip...>
pySIM-shell (MF)> select EF.ICCID
"621e8202412183022fe2a506c00100ca01808a01058b032f06048002000a8800"
pySIM-shell (MF/EF.ICCID)> read_binary_decoded
{
"iccid": "8988211000000169394"
}
-------
KDDI USIM:
Using PC/SC reader interface
Waiting for card...
ATR: [59, 157, 149, 128, 63, 199, 160, 128, 49, 160, 115, 190, 33, 83, 81, 6, 131, 5, 144, 0, 63]
Autodetected card type: Generic-UISIM
AIDs on card:
USIM: a0000000871002ff81ff108904150001
Welcome to pySim-shell!
pySIM-shell (MF)> select EF.ICCID
"0000000a2fe204000fffff01020000"
pySIM-shell (MF/EF.ICCID)> read_binary_decoded
{
"iccid": "8981100055906574179"
}
pySIM-shell (MF/EF.ICCID)> select MF
"0000ffff3f0001000000000011b304110400838a838a0000000000000000"
pySIM-shell (MF)> export
################################################################################
# MF/EF.DIR #
################################################################################
# directory: MF (3f00)
# file: EF.DIR (2f00)
# bad file: MF/EF.DIR, string indices must be integers
#
################################################################################
# MF/EF.ICCID #
################################################################################
# directory: MF (3f00)
# file: EF.ICCID (2fe2)
# bad file: MF/EF.ICCID, string indices must be integers
#
Hi all,Is there some special routine for enabling ssh on nano 3gs8 device?Or is the unit "useless" if the ssh-daemon is not running?(I have no way of seeing whether or not it is running)
I can access by telnet to dmi interface, the telnet commands from the wiki are present and have read the docs from accelerate 3g but I think there might be some subtle info I miss regarding starting ssh.
Port 22 is blocked is the errror message I get and i also tested the aes-method suggested in the wiki, same error, port 22 blocked also in that case.
Could this be the situation where one has to try setting up a tr069 server?
Regards
/erich
Hello fellow telecom hackers,
Seeing that OsmoDevCon 2022 is being discussed, I would like to propose
a more inclusive alternative, to be held in either USA or Mexico.
There are two severe lack-of-inclusion problems with OsmoDevCon:
1) Since its very beginning, ODC has been exclusionary, limited only
to Osmocom developers specifically, excluding those developers and
tinkerers who work on non-Osmocom projects in the "indie" telecom
space, "indie" being defined as independent of major commercial
vendors and industry. I hold the opinion that all monocultures are
bad in principle, and an Osmocom monoculture is no better than, say,
a Microsoft monoculture. Osmocom is currently in the dominant
position, outweighing all others by some orders of magnitude, but
might does not make right, and we need more diversity. We need more
players in this niche space than just Osmocom!
2) The recent decision to limit OsmoDevCon only to those who have
agreed to put a certain class of pharmaceutical into their bodies,
*on top* of the Osmocom-only restriction of the previous paragraph,
makes the proposed conference even more exclusionary and therefore of
no service to the wider telecom hacker community.
Of course it is not my place as a Russian-American to try to tell EU
countries whom to allow or not allow within their borders, nor is it
my place to tell private individuals like our Fearless Leader Harald
whom to allow or not allow in their private spaces. But what I *can*
do instead is to step forward and offer to organize and host a more
inclusive alternative, and that is what I am doing with this post.
Specifically I am offering to organize and host a physical in-person
gathering of telecom (all telecom, not just wireless) hackers,
enthusiasts and tinkerers, very similar in spirit to OsmoDevCon, but
more inclusive:
1) Welcoming everyone who has devoted a major portion of his or her
life to *any* project in the indie telecom space, regardless of which
domain that project is hosted under, and regardless of whether that
project is FOSS or merely PSS. (PSS = Published Source Software, a
superset of FOSS.)
2) Welcoming everyone regardless of personal medical choices - what
you do with your body is your business, not mine - you don't tell me
what I should or shouldn't put in my body, and I won't tell you what
you should or shouldn't put into yours. Also no forced testing: if
you wish to get yourself tested for this or that before attending, it
is your sovereign choice to do so, but no one will *ever* be turned
away from an event which I organize and host, neither for refusing to
test nor for any other reason.
If there is anyone interested in such an inclusive in-person gathering
of telecom hackers, I am offering to host one in my part of the world.
Where is it geographically? I live in USA, near San Diego, and right
next to the border between USA and Mexico. Depending on who is
interested in joining and where they will come from, I can host our
InclusiveDevCon on either side of the border, i.e., either in USA or
in Mexico.
It is my understanding that gaining entry into Mexico is much easier
than gaining entry into USA, hence for that reason I suggest that we
hold our get-together on the Mexican side of the border. If we do
choose Mexico as our host country, the specific location will need to
be in the northern part of that country, specifically in the Mexican
state of Baja California; the candidate cities would be Tijuana or
Ensenada, somewhere close to the border with USA. However, if the
only people who are interested in joining either already live in USA
or can easily enter this lovely country, then holding our Inclusive-
DevCon in USA would make more sense - in that case it will be somewhere
in San Diego area.
Alternatively, if there is anyone in the community who shares my stated
values of wider inclusion but cannot or does not wish to travel to USA
or Mexico, if you would be willing to host an inclusive event in your
part of the world, then I will consider traveling to attend your event
- but *only* if your event is open to non-Osmocom PSS developers *and*
open to those who refuse injections. Please note, however, that I
cannot enter Russia - other parts of the former USSR including
Transnistria are potentially accessible to me, but not Russia - I was
born there, but I permanently lost the ability to visit my birthplace
as a result of having done my gender transition while living in USA,
with all steps for legal name and gender change done under the
American system, as opposed to Russian.
In hacking solidarity,
Mother Mychaela of FreeCalypso
Hi list,
today I fixed a header file in libosmocore:
https://gerrit.osmocom.org/c/libosmocore/+/26044
TL;DR, using OSMO_IS_{LITTLE,BIG}_ENDIAN macros without including the
<osmocom/core/endian.h> header leads to empty struct definitions, and
thus weird compiler warnings like 'struct `foo` has no member `bar`'.
We may want to catch missing #include of the <endian.h> automatically,
so I wrote a simple script to check whether it is absent:
https://gerrit.osmocom.org/c/osmo-ci/+/26045
Below is an example of using it:
$ cd libosmocore/
$ verify_endian_header.sh $(find . -name "*.[hc]")
File './include/osmocom/gsm/protocol/gsm_44_004.h'
does not #include <osmocom/core/endian.h>
What's still missing is the actual integration into the build
verification process. I guess there is currently no easy way other than
calling this script from 'contrib/jenkins.sh' of each project?
P.S. I found out that we also have 'scripts/verify_log_statements.py' in
osmo-ci.git, but we don't seem to call it anywhere?
Best regards,
Vadim.
--
- Vadim Yanitskiy <vyanitskiy at sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
Dear All,
I am running a GSM stack:
osmo-stp
smo-msc
osmo-hlr
osmo-bsc
osmo-bts-trx
osmo-trx-lms
It seems that my transmitter is emitting radio-waves into air (osmo-bts-trx and osmo-trx-lms communicate with each other through ports 5702 / 5802 — pls see attached printscreen), however i could not make GSMTAP tracing. Osmo-bts-trx does not send GSMTAP messages to port 4729.
In most recent version of osmo-bts, GSMTAP tracing is arranged through config file:
bts 0
gsmtap-remote-host 127.0.0.1
gsmtap-sapi ccch
I could not run the GSMTAP tracing even in previous verions of osmo-bts where you have to specify in synopsis when you call a program:
/usr/bin/osmo-bts-trx -s -c /etc/osmocom/osmo-bts-trx.cfg --gsmtap-ip 127.0.0.1
I thought may be i am having some issues in stack components behind osmo-bts for example in osmo-bsc or behind and i tried to run virtual bts.
When i tried to run osmo-bts-virtual GSMTAP messages were visible in wireshark (please see attached file osmo-bts-virtual), therefore bts-bsc communication is good.
However I still could not figure out why my osmo-bts-trx does not send GSMTAP messages.
Or would you advise what log might be helpful to see what i am doing wrong ….
Thank you for your always helpful assistance
--
Mario Lucas
----------------------------------------------------------------------
--
Mario Lucas
Dear Osmocom community,
today we finally upgraded our redmine installation from the unmaintained
3.4.x to the latest 4.2.3. The upgrade had been overdue for years,
but today we (actually, Kevin) finally managed to find out how to make
the openid_provider plugin to work with modern rails 5.x.
In any case, I'm just informing you in case there is some unexpected fallout.
I've verified that at least the following appears working:
* logging into redmine
* openid authentication from gerrit.osmocom.org (also after logout/relogin)
* graphviz rendering
* mscgen rendering
There could however still be unexpected problems, particularly in features
such as
* e-mail notifications from redmine
* updating redmine issues via e-mail
* git integration ("Closes: OS#xxxx")
If you run into any troubles, pleas report to https://osmocom.org/projects/osmocom-servers
or if that also fails, feel free to send e-mails.
Regards,
Harald
--
- Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Not sure if this is a repost, i just joined the list and i don't think i
had confirmed my account when i sent it (the confirmation was in my spam).
Anyways, not trying to be a bad list member.
I just picked up this IPAccess model which supports band 2/5 and has the
same housing as the other units on the accelerate3g5 project docs. I've
been pouring over docs and trying a lot of network configurations in my
home lab. I have the login information for the factory reset and can access
the web gui on port 8089 during the reset process, but ssh and telnet DMI
seem to be disabled. I've been fuzzing ports and i've tried static as well
as DHCP for IP addresses.
My thought was that if i point the nano3G to the IP of my osmo-hNodeB
machine that it would at least stimulate the device and maybe i'd see some
log messages in the HNodeB gateway, but so far i haven't seen anything in
the logs. i've also tried abisip-find and that doesn't find anything.
Wireshark shows basic 'who has' Layer 2 messages and also DHCP requests
sent to 0.0.0.0, both from the nano3g. The nano3g does get an ip from my
lab router and i can ping it. The LAN behind that router can also access
the 0.ipaccess ntp server, but again no telnet DMI or ssh so i'm unsure
where to go from here.
Layer 1 seems to show nothing on the uarfcn in the web gui, so it seems
that its not crossing all the right bridges.
I will admit, i haven't run any other osmo network components for the
network, but as far as i was reading the home nodeb gateway and ntp should
be the only things necessary to at least start the process.
Any insight on what to try next would be very helpful. Does anyone have
experience with this model?
thanks