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--
