so...here are the tcpdump with openbts, seems problem is from the transceiver? https://wsi.li/huJmuT6TSh3o/I also tried with openbts, and the transceiver was terminated after I start ./transceiver -a 51 -r 99.also my osmo-bts stuck since its not sync with transceiver I guess :here are the log output from my transceiver :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 :then my osmonitb seems not moving cause transceiver not sync as I presumed: (its working for the configuration)
https://pastebin.com/5wPhePfT
https://pastebin.com/T2s8GJ7ethis is the tcpdump for osmocombb with osmonitb: https://wsi.li/1c4JhMOIUqOk/746634 THEN...746634 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@sysmocom.de> wrote: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
best regards,Krazy SandiBlue Soho RecordingsNumber One Recordings