Project

General

Profile

Bug #1827

Ericsson: In some cases SAPI 0 (RSL) LAPD is not established by attempted

Added by laforge almost 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Start date:
10/16/2016
Due date:
% Done:

0%

Estimated time:
Resolution:
fixed
Spec Reference:

Description

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.

History

#1 Updated by laforge almost 2 years ago

attaching a file with protocol trace

#2 Updated by laforge almost 2 years ago

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.

#3 Updated by laforge over 1 year ago

  • Assignee changed from laforge to dexter

#4 Updated by laforge over 1 year ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)