24 Nov
2017
24 Nov
'17
10:43 a.m.
Hi,
<000b> trx_if.c:409 transceiver (phy0.0)
rejected TRX command
with response: 'RSP SETTSC -1'
What is the problem and how can fix it?
The OsmocomBB transceiver is a legacy transceiver, so please add
the following line to your 'osmo-bts.cfg':
osmotrx legacy-setbsic
And please let me know about the results, I'll correct the wiki.
With best regards,
Vadim Yanitskiy.
24 Nov
24 Nov
4:04 p.m.
New subject: osmo-bts-trx init problem
Hi,
I added the line to 'osmo-bts.cfg' and got in terminal something like this:
*PH-RTS-IND: Unable to determine actual BS_AG_BLKS_RES value as SI3 is not
available yet, fallback to 1.*
and this :
* Invalid condition detected: Frame difference is 1685248-0 > 1*
What sould I do with that? what is the problem? I thought that I forgot to
change ARFCN in "openbsc.cfg" and then
after changing ARFCN in "openbsc.cfg" I can't even init it. Terminal says:
*root@pc:~# osmo-nitb -c ~/.osmocom/openbsc.cfg -l ~/.osmocom/hlr.sqlite3
-P -C --debug=DRLL:DCC:DMM:DRR:DRSL:DNM<0005> abis_nm.c:2800 (bts=0,trx=0)
Changing adm. state Unlocked -> Unlocked [vty]Reading config failed.
Exiting.*
May be the problem is in *"*hlr.sqlite3"? I don't know. By the way, how can
I make new *"*hlr.sqlite3"? I lost the tutorial about it. Help me, pls.
Thanks!
2017-11-24 12:43 GMT+03:00 Vadim Yanitskiy <axilirator(a)gmail.com>om>:
Hi,
<000b> trx_if.c:409 transceiver (phy0.0)
rejected TRX command
with response: 'RSP SETTSC -1'
What is the problem and how can fix it?
The OsmocomBB transceiver is a legacy transceiver, so please add
the following line to your 'osmo-bts.cfg':
osmotrx legacy-setbsic
And please let me know about the results, I'll correct the wiki.
With best regards,
Vadim Yanitskiy.
4:21 p.m.
New subject: osmo-bts-trx init problem
added my cfg files and hlr
2017-11-24 18:04 GMT+03:00 GSK MOSS <gskmoss(a)gmail.com>om>:
Hi,
I added the line to 'osmo-bts.cfg' and got in terminal something like this:
*PH-RTS-IND: Unable to determine actual BS_AG_BLKS_RES value as SI3 is not
available yet, fallback to 1.*
and this :
* Invalid condition detected: Frame difference is 1685248-0 > 1*
What sould I do with that? what is the problem? I thought that I forgot to
change ARFCN in "openbsc.cfg" and then
after changing ARFCN in "openbsc.cfg" I can't even init it. Terminal says:
*root@pc:~# osmo-nitb -c ~/.osmocom/openbsc.cfg -l ~/.osmocom/hlr.sqlite3
-P -C --debug=DRLL:DCC:DMM:DRR:DRSL:DNM<0005> abis_nm.c:2800 (bts=0,trx=0)
Changing adm. state Unlocked -> Unlocked [vty]Reading config failed.
Exiting.*
May be the problem is in *"*hlr.sqlite3"? I don't know. By the way, how
can I make new *"*hlr.sqlite3"? I lost the tutorial about it. Help me,
pls. Thanks!
2017-11-24 12:43 GMT+03:00 Vadim Yanitskiy <axilirator(a)gmail.com>om>:
Hi,
<000b> trx_if.c:409 transceiver (phy0.0)
rejected TRX command
with response: 'RSP SETTSC -1'
What is the problem and how can fix it?
The OsmocomBB transceiver is a legacy transceiver, so please add
the following line to your 'osmo-bts.cfg':
osmotrx legacy-setbsic
And please let me know about the results, I'll correct the wiki.
With best regards,
Vadim Yanitskiy.
27 Nov
27 Nov
1:13 p.m.
New subject: osmo-bts-trx init problem
On Fri, Nov 24, 2017 at 06:04:10PM +0300, GSK MOSS wrote:
* Invalid condition detected: Frame difference is
1685248-0 > 1*
I'm not 100% sure but I think this is just some startup condition that you can
safely ignore.
Reading config failed.
Exiting.
those usually also output why reading the config failed.
Do you get a more detailed error message?
I took your attached openbsc.cfg and successfully started osmo-nitb with it, so
maybe you just messed up the config name or something so that osmo-nitb *can't
find* your file?
May be the problem is in *"*hlr.sqlite3"? I
don't know.
Ususally that wouldn't result in "reading config failed". The db file is
hardly
ever the problem though, I wouldn't think it is in your case either.
If you want a new db file, simply move it out of the way / rename it / delete
it, and osmo-nitb will create a fresh empty one automatically. After that you
can use the telnet VTY to add subscribers again.
A general remark: it would be appreciated if you sent mails to this list not in
HTML format, but just in plain text. We read mails in plain text, and your line
breaks are messed up because you're sending in HTML. Thanks!
~N
2:06 p.m.
New subject: osmo-bts-trx init problem
Dear Neels, Vadim,
I tried the osmocomBB with my C118 also C117, and I install gnuarm and
osmocomBB with sylvain and jolly to try both.
seems the configuration is fine, but i have problem on the osmocombb
tranceiver.
my problem is :
here are the log output from my transceiver :
https://pastebin.com/8Y1qXWh8
then my osmonitb seems not moving cause transceiver not sync as I presumed:
(its working for the configuration)
https://pastebin.com/5wPhePfT
also my osmo-bts stuck since its not sync with transceiver I guess :
https://pastebin.com/T2s8GJ7e
this is the tcpdump for osmocombb with osmonitb:
https://wsi.li/1c4JhMOIUqOk/746634
THEN...
I also tried with openbts, and the transceiver was terminated after I start
./transceiver -a 51 -r 99.
here are the tcpdump with openbts, seems problem is from the transceiver?
https://wsi.li/huJmuT6TSh3o/746634
so...
hope you guys the problem from the indication I have?
Thanks in advance.
regards,
Sandi
On Mon, Nov 27, 2017 at 7:13 PM, Neels Hofmeyr <nhofmeyr(a)sysmocom.de> wrote:
On Fri, Nov 24, 2017 at 06:04:10PM +0300, GSK MOSS
wrote:
--
best regards,
Krazy Sandi
Blue Soho Recordings
Number One Recordings
* Invalid condition detected: Frame difference is
1685248-0 > 1*
I'm not 100% sure but I think this is just some startup condition that you
can
safely ignore.
Reading config failed.
Exiting.
those usually also output why reading the config failed.
Do you get a more detailed error message?
I took your attached openbsc.cfg and successfully started osmo-nitb with
it, so
maybe you just messed up the config name or something so that osmo-nitb
*can't
find* your file?
May be the problem is in
*"*hlr.sqlite3"? I don't know.
Ususally that wouldn't result in "reading config failed". The db file is
hardly
ever the problem though, I wouldn't think it is in your case either.
If you want a new db file, simply move it out of the way / rename it /
delete
it, and osmo-nitb will create a fresh empty one automatically. After that
you
can use the telnet VTY to add subscribers again.
A general remark: it would be appreciated if you sent mails to this list
not in
HTML format, but just in plain text. We read mails in plain text, and your
line
breaks are messed up because you're sending in HTML. Thanks!
~N
4:02 p.m.
New subject: osmo-bts-trx init problem
Hi all,
The BTS work with Sylvain/testing now, but not with jolly/testing branch.
strange!
regards,
Sandi
On Mon, Nov 27, 2017 at 8:06 PM, Sandi Suhendro <djks74(a)gmail.com> wrote:
Dear Neels, Vadim,
I tried the osmocomBB with my C118 also C117, and I install gnuarm and
osmocomBB with sylvain and jolly to try both.
seems the configuration is fine, but i have problem on the osmocombb
tranceiver.
my problem is :
here are the log output from my transceiver :
https://pastebin.com/8Y1qXWh8
then my osmonitb seems not moving cause transceiver not sync as I
presumed: (its working for the configuration)
https://pastebin.com/5wPhePfT
also my osmo-bts stuck since its not sync with transceiver I guess :
https://pastebin.com/T2s8GJ7e
this is the tcpdump for osmocombb with osmonitb:
https://wsi.li/1c4JhMOIUqOk/746634
THEN...
I also tried with openbts, and the transceiver was terminated after I
start ./transceiver -a 51 -r 99.
here are the tcpdump with openbts, seems problem is from the transceiver?
https://wsi.li/huJmuT6TSh3o/746634
so...
hope you guys the problem from the indication I have?
Thanks in advance.
regards,
Sandi
On Mon, Nov 27, 2017 at 7:13 PM, Neels Hofmeyr <nhofmeyr(a)sysmocom.de>
wrote:
--
best regards,
Krazy Sandi
Blue Soho Recordings
Number One Recordings
On Fri, Nov 24, 2017 at 06:04:10PM +0300, GSK
MOSS wrote:
--
best regards,
Krazy Sandi
Blue Soho Recordings
Number One Recordings
* Invalid condition detected: Frame difference is
1685248-0 > 1*
I'm not 100% sure but I think this is just some startup condition that
you can
safely ignore.
Reading config failed.
Exiting.
those usually also output why reading the config failed.
Do you get a more detailed error message?
I took your attached openbsc.cfg and successfully started osmo-nitb with
it, so
maybe you just messed up the config name or something so that osmo-nitb
*can't
find* your file?
May be the problem is in
*"*hlr.sqlite3"? I don't know.
Ususally that wouldn't result in "reading config failed". The db file is
hardly
ever the problem though, I wouldn't think it is in your case either.
If you want a new db file, simply move it out of the way / rename it /
delete
it, and osmo-nitb will create a fresh empty one automatically. After that
you
can use the telnet VTY to add subscribers again.
A general remark: it would be appreciated if you sent mails to this list
not in
HTML format, but just in plain text. We read mails in plain text, and
your line
breaks are messed up because you're sending in HTML. Thanks!
~N
28 Nov
28 Nov
12:20 a.m.
New subject: osmo-bts-trx init problem
Hi Sandi,
here are the log output from my transceiver :
https://pastebin.com/8Y1qXWh8
According to the attached log, you don't have any clock indications...
sudo ./transceiver -a 51 -r 99
...
<0011> trx.c:365 Setting C0 ARFCN to 51 (GSM900)
Please read the wiki carefully! You are doing wrong.
What are you expecting here? Please refer:
http://osmocom.org/projects/baseband/wiki/CalypsoBTS#Clock-source
use RSSI or cell_log applications to find cells with
good
signal and remember the ARFCN numbers. One of them will be
used as a clock source for our own base station.
http://osmocom.org/projects/baseband/wiki/CalypsoBTS#OsmoNITB-configuration
Channel configuration
Set a proper ARFCN for running BTS (don't confuse with
a clock source). Also, set a corresponding band name.
The AFRCN value, passed to the OsmocomBB transceiver, is a
channel of the clock reference cell. The AFRCN value specified
in the OsmoNiTB configuration is a C0 channel of the BTS you
are going to run. Don't confuse them please.
I also tried with openbts, and the transceiver was
terminated
after I start ./transceiver -a 51 -r 99.
Again, read the wiki:
http://osmocom.org/projects/baseband/wiki/CalypsoBTS#CalypsoBTS-with-OpenBTS
Run the TRX firmware on the phone as described above.
No need to
start transceiver, OpenBTS will run it automatically.
The BTS work with Sylvain/testing now,
but not with jolly/testing branch.
I just tested the latest versions of OsmoNiTB & OsmoBTS.
Everything works as expected.
With best regards,
Vadim Yanitskiy.
2 Dec
2 Dec
8:31 p.m.
New subject: osmo-bts-trx init problem
Hello guys! I inited bsc and bts сfg succesfuly, but I got a problem.
<0004> abis_rsl.c:1922 (bts=0,trx=0,ts=2,ss=0) Activating ARFCN(60) SS(0)
lctype TCH_F r=OTHER ra=0x57 ta=38
<0004> abis_rsl.c:595 (bts=0,trx=0,ts=2,pchan=TCH/F) Tx RSL Channel
Activate with act_type=INITIAL
<0004> abis_rsl.c:1231 (bts=0,trx=0,ts=2,ss=0) state NONE -> ACTIVATION
REQUESTED
<0004> abis_rsl.c:1603 (bts=0,trx=0,ts=2,ss=0) CHANNEL ACTIVATE ACK
<0004> abis_rsl.c:1231 (bts=0,trx=0,ts=2,ss=0) state ACTIVATION REQUESTED
-> ACTIVE
<0004> abis_rsl.c:1721 (bts=0,trx=0,ts=2,ss=0) T3101 expired: no response
to IMMEDIATE ASSIGN
<0004> abis_rsl.c:867 (bts=0,trx=0,ts=2,ss=0) RF Channel Release due to
error: 1
<0004> abis_rsl.c:777 (bts=0,trx=0,ts=2,ss=0) DEACTivate SACCH CMD
<0004> abis_rsl.c:1231 (bts=0,trx=0,ts=2,ss=0) state ACTIVE -> RELEASE DUE
ERROR
<0004> abis_rsl.c:939 (bts=0,trx=0,ts=2,ss=0) RF CHANNEL RELEASE ACK
<0004> abis_rsl.c:826 (bts=0,trx=0,ts=2,ss=0) is back in operation.
What's wrong? Full log files attached.
2017-11-28 2:20 GMT+03:00 Vadim Yanitskiy <axilirator(a)gmail.com>om>:
Hi Sandi,
here are the log output from my transceiver :
https://pastebin.com/8Y1qXWh8
According to the attached log, you don't have any clock indications...
sudo ./transceiver -a 51 -r 99
...
<0011> trx.c:365 Setting C0 ARFCN to 51 (GSM900)
Please read the wiki carefully! You are doing wrong.
What are you expecting here? Please refer:
http://osmocom.org/projects/baseband/wiki/CalypsoBTS#Clock-source
use RSSI or cell_log applications to find cells
with good
signal and remember the ARFCN numbers. One of them will be
used as a clock source for our own base station.
http://osmocom.org/projects/baseband/wiki/CalypsoBTS#
OsmoNITB-configuration
Channel configuration
Set a proper ARFCN for running BTS (don't confuse with
a clock source). Also, set a corresponding band name.
The AFRCN value, passed to the OsmocomBB transceiver, is a
channel of the clock reference cell. The AFRCN value specified
in the OsmoNiTB configuration is a C0 channel of the BTS you
are going to run. Don't confuse them please.
I also tried with openbts, and the transceiver
was terminated
after I start ./transceiver -a 51 -r 99.
Again, read the wiki:
http://osmocom.org/projects/baseband/wiki/CalypsoBTS#
CalypsoBTS-with-OpenBTS
Run the TRX firmware on the phone as described
above. No need to
start transceiver, OpenBTS will run it automatically.
The BTS work with Sylvain/testing now,
but not with jolly/testing branch.
I just tested the latest versions of OsmoNiTB & OsmoBTS.
Everything works as expected.
With best regards,
Vadim Yanitskiy.
10:16 p.m.
New subject: osmo-bts-trx init problem
Hi!
On Sat, Dec 02, 2017 at 10:31:57PM +0300, GSK MOSS wrote:
<0004> abis_rsl.c:1922 (bts=0,trx=0,ts=2,ss=0)
Activating ARFCN(60) SS(0)
lctype TCH_F r=OTHER ra=0x57 ta=38
<0004> abis_rsl.c:595 (bts=0,trx=0,ts=2,pchan=TCH/F) Tx RSL Channel
Activate with act_type=INITIAL
<0004> abis_rsl.c:1231 (bts=0,trx=0,ts=2,ss=0) state NONE -> ACTIVATION
REQUESTED
<0004> abis_rsl.c:1603 (bts=0,trx=0,ts=2,ss=0) CHANNEL ACTIVATE ACK
<0004> abis_rsl.c:1231 (bts=0,trx=0,ts=2,ss=0) state ACTIVATION REQUESTED
-> ACTIVE
<0004> abis_rsl.c:1721 (bts=0,trx=0,ts=2,ss=0) T3101 expired: no response
to IMMEDIATE ASSIGN
<0004> abis_rsl.c:867 (bts=0,trx=0,ts=2,ss=0) RF Channel Release due to
error: 1
The above log is telling you that the BTS+BSC have activated the radio channel
on the BTS side and send the MS an IMMEDIATE ASSIGN command. However, the phone
never established LAPDm (Layer2) on that channel. Usual causes for this error
are insufficient power budget / too high path loss on the RF link.
--
- 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)
2343
days inactive
2351
days old
8 comments
5 participants
participants (5)
-
GSK MOSS -
Harald Welte -
Neels Hofmeyr -
Sandi Suhendro -
Vadim Yanitskiy