Ericsson: In some cases SAPI 0 (RSL) LAPD is not established by attempted
It seems that in some cases, the SAPI=62 connection on TEI=62 to the IXU/DXU/MU and the SAPI=62 connection to the TRX (TEI=0) is established, but not the SAPI=0 (RSL) connection to the TRX (TEI=0). This means that OM2000 can get fully established, but RSL is stuck in a way that higher-layer code is ready to use it, but the connection is missing.
This might be related to the fact that normally the LAPD re-connect logic is in the BTS and the BSC doesn't have to care about that. Only in the Ericsson case, the BSC intitiates all LAPD connections. Let's check if we do this the right way.
#2 Updated by laforge about 3 years ago
- File 0002-RBS2000-re-establish-any-lost-signalling-links.patch 0002-RBS2000-re-establish-any-lost-signalling-links.patch added
- Status changed from New to Resolved
- Assignee changed from dexter to laforge
- Resolution set to fixed
I have had some positive results using below patch which is now also part of the laforge/om2000-rebase branch
Pleaes note its dependency on a recent libosmo-abis commit.