BS-11 link does not come up

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Sergey V. Efimoff risky at mail.ru
Fri Aug 21 16:33:19 UTC 2009


It is all OK now. I've downloaded latest mISDNv2 stack from misdn.org  
and now it works.
Though I can't see network name on my GSM phone, only MCC/MNC.

Also, SMS delivery is extremely unstable. It delivers only after I  
switch recipient phone off/on,
i.e. after re-registration and almost always dies with "Segmentation  
fault" message after that.
Message delivery from one on-line phone to another on-line phone is  
impossible:

...
ERROR REPORT CAUSE=0x62(Message Sequence Error)
...

I will provide more detailed logs if it is interesting for you.

On Aug 21, 2009, at 8:11 PM, Harald Welte wrote:

> Hi Sergey,
>
> sorry to hear about your problems.
>
> On Thu, Aug 20, 2009 at 10:02:49PM +0400, Sergey V. Efimoff wrote:
>
>> When trying to run bsc_hack I get the following messages:
>>
>> bootstrapping OML for BTS 0
>> <0020> abis_nm.c:1644 Set BTS Attr (bts=0)
>> <0020> abis_nm.c:1661 Set TRX Attr (bts=0,trx=0)
>> <0020> abis_nm.c:1754 Set Chan Attr (bts=0,trx=0,ts=0)
>> <0020> abis_nm.c:1754 Set Chan Attr (bts=0,trx=0,ts=1)
>> <0020> abis_nm.c:1624 CONNECT TERR TRAF Um=(bts=0,trx=0,ts=1)  
>> E1=(0,2,1)
>> <0020> abis_nm.c:1754 Set Chan Attr (bts=0,trx=0,ts=2)
>> <0020> abis_nm.c:1624 CONNECT TERR TRAF Um=(bts=0,trx=0,ts=2)  
>> E1=(0,2,2)
>> <0020> abis_nm.c:1754 Set Chan Attr (bts=0,trx=0,ts=3)
>> <0020> abis_nm.c:1624 CONNECT TERR TRAF Um=(bts=0,trx=0,ts=3)  
>> E1=(0,2,3)
>> <0020> abis_nm.c:1754 Set Chan Attr (bts=0,trx=0,ts=4)
>> <0020> abis_nm.c:1624 CONNECT TERR TRAF Um=(bts=0,trx=0,ts=4)  
>> E1=(0,3,0)
>> <0020> abis_nm.c:1754 Set Chan Attr (bts=0,trx=0,ts=5)
>> <0020> abis_nm.c:1624 CONNECT TERR TRAF Um=(bts=0,trx=0,ts=5)  
>> E1=(0,3,1)
>> <0020> abis_nm.c:1754 Set Chan Attr (bts=0,trx=0,ts=6)
>> <0020> abis_nm.c:1624 CONNECT TERR TRAF Um=(bts=0,trx=0,ts=6)  
>> E1=(0,3,2)
>> <0020> abis_nm.c:1754 Set Chan Attr (bts=0,trx=0,ts=7)
>> <0020> abis_nm.c:1624 CONNECT TERR TRAF Um=(bts=0,trx=0,ts=7)  
>> E1=(0,3,3)
>> bootstrapping RSL for BTS/TRX (0/0) using MCC=1 MNC=1 BSIC=1 TSC=7
>> <0020> abis_nm.c:805 OC=SIEMENSHW(a5) INST=(03,00,00) STATE CHG:
>> <0020> abis_nm.c:805 OC=SIEMENSHW(a5) INST=(03,00,00) Failure Event
>> Report Severity=indeterminate failure
>> <0020> abis_nm.c:805 OC=SIEMENSHW(a5) INST=(03,00,00) STATE CHG:
>
> that looks pretty fine.  The indeterminate failure is most likely the
> intrusion detected switch in case you don't have the cover  
> attached.  Nothing
> to worry about, it is just an information for you.
>
>> Debug with -dDMI:DRSL:DNM shows strange lines:
>>
>> ...
>> <1000> input/misdn.c:132 DL_INFORMATION_IND: use channel(0) sapi(63)
>> tei(127) for now
>> mISDN message for unknown sign_link
>> ...
>> <1000> input/misdn.c:132 DL_INFORMATION_IND: use channel(2) sapi(62)
>> tei(1) for now
>> mISDN message for unknown sign_link
>> ...
>>
>>
>> Why TEI=1 or TEI=127 while it should be 25?
>
> those are normal.  TEI 127 is the TEI manager, and TEI 1 is the  
> actual RSL link
> which is coming up.
>
>> Also, dmesg produces:
>>
>> ...
>> mISDN_send: error -12
>
> I've seen them, too (only when stopping bsc_hack unexpectedly, though)
> Nothing serious.
>
>> I thought that these problems may be connected with internal BS11
>> oscillator calibration, so
>> I've performed calibration as described in wiki (though I used
>> Nateks SDH mux with Stratum oscillator
>> as E1 clock source instead of HFC-S ISDN card, which I don't have).
>
> calibration looks fine here.
>
> do you have a spectrum analyzer or similar device that you can use to
> check if the carrier is actually active at the ARFCN that you have
> configured?





More information about the OpenBSC mailing list