Actions
Bug #5977
closedosmo-bsc unable to bring up osmo-bts-sysmo (BSIC/TSC)
Start date:
03/27/2023
Due date:
% Done:
0%
Spec Reference:
Description
I've just installed the 201705-nightly image on a sysmoBTS 1002:
root@sysmobts-v2:/tmp# osmo-bts-sysmo --version OsmoBTS version 1.6.0.37-e464e root@sysmobts-v2:/tmp# opkg list | grep osmo-bts osmo-bts - 1.6.0+git18+e464ef6524-r1.18.1
When trying to bring it up against a remote osmo-bsc, I'm getting an OML Radio Channel(00,00,00) Set Channel Attrributes NACK from the BTS, with the BTS complaining:
<0001> ../../../git/src/common/oml.c:454 OC=CHANNEL(03) INST=(00,00,00): Sending FOM NACK with cause Parameter value outside permitted range.
The BSC config contains BSIC 63 and TSC 7.
Somehow the BSIC doesn't seem to be set before the TSC7 of TS0, and then the BTS still has its zero-initialized BSIC?
Files
Related issues
Updated by laforge about 1 year ago
- Related to Bug #3789: BTS permits OPSTART of MO without attributes added
Updated by laforge about 1 year ago
- File sysmobts-abis-startup-problem-with-gsmtap.pcap sysmobts-abis-startup-problem-with-gsmtap.pcap added
Attaching a new pcap file containing GSMTAP logging of both BTS and BSC: sysmobts-abis-startup-problem-with-gsmtap.pcap
Updated by laforge about 1 year ago
- Assignee set to pespin
- Priority changed from Normal to High
setting BSIC to 0 in osmo-bsc.cfg works as a work-around. This should be fixed properly, obviously.
Updated by laforge about 1 year ago
- Is duplicate of Bug #5856: Very annoying "this BTS model does not support TSC 7 != BSIC-BCC 0" error. added
Updated by pespin about 1 year ago
- Status changed from New to Closed
Closing as duplicate of #5856, updates are being written there.
Actions
