Project

General

Profile

Bug #2259

problem with local reference

Added by dexter 5 months ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assignee:
Start date:
05/16/2017
Due date:
% Done:

0%

Spec Reference:

Description

When a connection attemt (local reference = 2) is made, libosmo-sccp complains with "<000d> sccp_scoc.c:1528 Cannot find connection for local reference 2". Current master is at 872c6b2a8e309ca6739ef295f1fc468c189e4ec9. The problem seems to be introduced with commit 5527df78adc08b76df07c4b682263b5bdd6181d4 (libosmo-sccp.git). When the commit is reverted, the correct functionality of libosmo-sccp seems to be restored.

The problem can be demonstrated by using the client/server example that is shipped with libosmo-sccp. The following VTY-Commands were used to trigger the problem:

enable 
sccp-user 
called-addr-ssn 202
connect-req 2 hello

Note: In the good case I can see the normal CR with payload attached and the CC that with the payload that is echoed by the the echo subsystem. The bad case results in an CREF message, which contains an refusal cause code 0x0F (unqalified)

sccp-bug.tar.gz (7.59 KB) dexter, 05/16/2017 01:03 PM

History

#1 Updated by dexter 5 months ago

Note: Normal behaviour can be restored when 5527df78adc08b76df07c4b682263b5bdd6181d4 (libosmo-sccp.git) is reverted.

#2 Updated by laforge 3 months ago

In Ic76aacc81f87f8885fe04121aead5c79a761ef07 this was reverted in master. We need to test against other SCCP implementations to ensure we don't only interoperate with our own code on both ends of the SCCP connection.

Also available in: Atom PDF