Project

General

Profile

Actions

Bug #2666

closed

osmo-msc crashes when receiving SCCP with RI=GT from A

Added by laforge over 6 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
A interface (AoIP)
Target version:
-
Start date:
11/20/2017
Due date:
% Done:

0%

Resolution:
Spec Reference:

Description

On the A interface, we use SCCP with PC/SSN only. However, if a SCCP message with RI (Routing Indicator) = GT (Global Title) arrives, the MSC spits out several hundred identical messages (hinting to infinite recursion of some sorts) and finally crashes:

<002e> sccp_scrc.c:279 GT Routing not implemented yet
<002e> sccp_scrc.c:279 GT Routing not implemented yet
<002e> sccp_scrc.c:279 GT Routing not implemented yet
<002e> sccp_scrc.c:279 GT Routing not implemented yet
<002e> sccp_scrc.c:279 GT Routing not implemented yet
<002e> sccp_scrc.c:279 GT Routing not implemented yet
<002e> sccp_scrc.c:279 GT Routing not implemented yet
<002e> sccp_scrc.c:279 GT Routing not implemented yet
<002e> sccp_scrc.c:279 GT Routing not implemented yet
<002e> sccp_scrc.c:279 GT Routing not implemented yet
<002e> sccp_scrc.c:279 GT Routing not implemented yet
[1]    10151 segmentation fault  ./osmo-msc
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)