Dear List,
I am in the process of further updating the following Wiki article:
The goal is to have a clean, up to date manual which tells in detail how to set up OpenBSC.
In the light of recent changes I decided to change this already working setup to use the "master" branches of every involved Osmocom project.
It is finally possible to compile and run every project after the proper dependencies are met. But some new problem popped up I haven't seen before.
After everything is started up (OpenBSC, GGSN, SGSN, LCR, TRX, and PCU), when a phone tries to RACH, this is what I get in the BSC log:
Sat Nov 28 14:09:08 2015 <0004> abis_rsl.c:1423 BTS 0 CHAN RQD: no resources for SDCCH 0xf Sat Nov 28 14:09:19 2015 <0004> abis_rsl.c:1423 BTS 0 CHAN RQD: no resources for SDCCH 0x6 Sat Nov 28 14:09:30 2015 <0004> abis_rsl.c:1423 BTS 0 CHAN RQD: no resources for SDCCH 0x6
On the BTS side, this is what I get:
<0006> scheduler.c:1186 Received Access Burst on RACH fn=9868 toa=5.88 <0006> scheduler.c:1192 Received bad AB frame at fn=9868 (25/51) <0006> scheduler.c:1186 Received Access Burst on RACH fn=52459 toa=-1.50 <0006> scheduler.c:1192 Received bad AB frame at fn=52459 (31/51) <0006> scheduler.c:1186 Received Access Burst on RACH fn=67956 toa=-0.06 <0006> scheduler.c:1192 Received bad AB frame at fn=67956 (24/51)
Because I used exactly the same config files I used before when it all worked, I analyzed the logs a littlebit more.
In the BTS log, during the OML setup this is what I found:
<0001> oml.c:802 ADM state already was Unlocked <0001> oml.c:256 OC=BASEBAND-TRANSCEIVER INST=(00,00,ff) OPER STATE NULL -> Enabled <0001> oml.c:217 OC=BASEBAND-TRANSCEIVER INST=(00,00,ff) Tx STATE CHG REP <000b> trx_if.c:366 Response message 'RSP ERR 1' does not match command message 'CMD SETBSIC 62' !!!!!! <0001> oml.c:1059 Rx IPA RSL CONNECT IP=127.0.0.1 PORT=3003 STREAM=0x00 <0011> input/ipa.c:129 connection done. <0011> input/ipaccess.c:693 received ID get <0000> rsl.c:279 Tx RSL RF RESource INDication
Maybe the recent changes in the BSIC/TSC handling part is causing this? Anyway it seems that the BSIC I set in the BSC is the correct one the BTS tries to configure during the timeslot, transceiver and BTS setup.
I attached the corresponding OML trace, and the logs.
If someone has any ideas, please let me know.
Regards, Csaba
Just to further add to this issue:
Both "fairwaves/master" and "201509-fairwaves-rebase" branches of Osmo-BTS are working fine (all other Osmocom projects are latest master), only the "master" branch of Osmo-BTS is affected with this issue.
Because the 201509rebease is introducing a lot of important fixes and features (and it seems to be working fine), I am now changing the Wiki to suggest to use "master" for OpenBSC, and "201509-fairwaves-rebase" for Osmo-BTS, but maybe this would be a good time to finally get the projects in sync, so we can use the master branches for every projects onwards.
Regards, Csaba
----- Eredeti üzenet ----- Feladó: "Sipos Csaba" sipos.csaba@kvk.uni-obuda.hu Címzett: "OpenBSC Mailing List" openbsc@lists.osmocom.org Elküldött üzenetek: Szombat, 2015. November 28. 16:07:19 Tárgy: <0004> abis_rsl.c:1423 BTS 0 CHAN RQD: no resources for SDCCH 0xf
Dear List,
I am in the process of further updating the following Wiki article:
The goal is to have a clean, up to date manual which tells in detail how to set up OpenBSC.
In the light of recent changes I decided to change this already working setup to use the "master" branches of every involved Osmocom project.
It is finally possible to compile and run every project after the proper dependencies are met. But some new problem popped up I haven't seen before.
After everything is started up (OpenBSC, GGSN, SGSN, LCR, TRX, and PCU), when a phone tries to RACH, this is what I get in the BSC log:
Sat Nov 28 14:09:08 2015 <0004> abis_rsl.c:1423 BTS 0 CHAN RQD: no resources for SDCCH 0xf Sat Nov 28 14:09:19 2015 <0004> abis_rsl.c:1423 BTS 0 CHAN RQD: no resources for SDCCH 0x6 Sat Nov 28 14:09:30 2015 <0004> abis_rsl.c:1423 BTS 0 CHAN RQD: no resources for SDCCH 0x6
On the BTS side, this is what I get:
<0006> scheduler.c:1186 Received Access Burst on RACH fn=9868 toa=5.88 <0006> scheduler.c:1192 Received bad AB frame at fn=9868 (25/51) <0006> scheduler.c:1186 Received Access Burst on RACH fn=52459 toa=-1.50 <0006> scheduler.c:1192 Received bad AB frame at fn=52459 (31/51) <0006> scheduler.c:1186 Received Access Burst on RACH fn=67956 toa=-0.06 <0006> scheduler.c:1192 Received bad AB frame at fn=67956 (24/51)
Because I used exactly the same config files I used before when it all worked, I analyzed the logs a littlebit more.
In the BTS log, during the OML setup this is what I found:
<0001> oml.c:802 ADM state already was Unlocked <0001> oml.c:256 OC=BASEBAND-TRANSCEIVER INST=(00,00,ff) OPER STATE NULL -> Enabled <0001> oml.c:217 OC=BASEBAND-TRANSCEIVER INST=(00,00,ff) Tx STATE CHG REP <000b> trx_if.c:366 Response message 'RSP ERR 1' does not match command message 'CMD SETBSIC 62' !!!!!! <0001> oml.c:1059 Rx IPA RSL CONNECT IP=127.0.0.1 PORT=3003 STREAM=0x00 <0011> input/ipa.c:129 connection done. <0011> input/ipaccess.c:693 received ID get <0000> rsl.c:279 Tx RSL RF RESource INDication
Maybe the recent changes in the BSIC/TSC handling part is causing this? Anyway it seems that the BSIC I set in the BSC is the correct one the BTS tries to configure during the timeslot, transceiver and BTS setup.
I attached the corresponding OML trace, and the logs.
If someone has any ideas, please let me know.
Regards, Csaba
Hi Sipos,
On Sun, Nov 29, 2015 at 05:30:48PM +0100, Sipos Csaba wrote:
but maybe this would be a good time to finally get the projects in sync, so we can use the master branches for every projects onwards.
As indicated, I am waiting for the proponents and users of osmo-bts-trx to submit any fixes that they may have in other branches. I think I did my fair share by re-basing and brining forward the code, but that's all I could do.
Submitting patches and maintaining a particular hardware port is always up to the users of that particular hardware, I think that's only fair.
Regards, Harald
Dear Harald,
I think I did my fair share
Nobody sais or implicates the opposite :-)
I just put you on this mail because I thought maybe you have some ideas what might trigger an issue like this.
The interesting part is that between the osmo-bts master and the fairwaves rebase branch there is not a lot of difference, and I do not see anything that can relate to an issue like this.
Will continue to look at the code, maybe I can find what causes it.
Regards, Csaba
----- Eredeti üzenet ----- Feladó: "Harald Welte" laforge@gnumonks.org Címzett: "Sipos Csaba" sipos.csaba@kvk.uni-obuda.hu Másolatot kap: "OpenBSC Mailing List" openbsc@lists.osmocom.org, "Alexander Chemeris" alexander.chemeris@gmail.com Elküldött üzenetek: Vasárnap, 2015. November 29. 18:41:38 Tárgy: Re: <0004> abis_rsl.c:1423 BTS 0 CHAN RQD: no resources for SDCCH 0xf
Hi Sipos,
On Sun, Nov 29, 2015 at 05:30:48PM +0100, Sipos Csaba wrote:
but maybe this would be a good time to finally get the projects in sync, so we can use the master branches for every projects onwards.
As indicated, I am waiting for the proponents and users of osmo-bts-trx to submit any fixes that they may have in other branches. I think I did my fair share by re-basing and brining forward the code, but that's all I could do.
Submitting patches and maintaining a particular hardware port is always up to the users of that particular hardware, I think that's only fair.
Regards, Harald
-
Harald Welte -
Sipos Csaba