Osmo-nitb v_0.13.0.48-9e22 broke compatibility with Nokia InSite

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/.

Sipos Csaba dchardware at gmail.com
Tue Jul 30 20:16:34 UTC 2013


Hey Holger,

Thanks for the support.

If you or anybody can answer to one question, it would help the
debugging very much:

In your opinion without explicitly closing the OML and RSL lapd connection, it is
possible, that even after a RELEASE CONFIRMed lapd connection got
restarted improperly, if it receives data from the BTS?

Because that is exactly what is happening:

1. OpenBSC send RESET_REQ to Nokia BTS
2. OpenBSC receives ACK from the BTS
3. OpenBSC releases the LAPD connection (but not closes it, like with Ctrl+C)
4. Some data received by OpenBSC via the E1 link, and the lapd
connection for OML got restarted (despite we are in the RESET state
and RESET_TIMER not expired yet)

According to Dieter (who helped a lot), during the RESET NOkia BTS
sends garbage on the E1 link, therefore during the reset it is wise
not to listen on any timeslots, until the RESET_TIMER expires (15-20
seconds). According to him, it was working like this with mISDN, but
there was no DAHDI when he wrote the Nokia related codes, and now he
don't have much time to debug this issue. SO the problem is that the
LAPD connection somehow got restarted though it shouldn't durin the
RESET state.

So this is where I am at the moment.

BR,
Csaba

> Just try, don't be afraid. We are happy to answer any self motivated
> technical question. We all had to learn how to use gdb and various
> other tools.


>> Will test this in 1-2 days, and report back with the results.


> great





More information about the OpenBSC mailing list