Project

General

Profile

Bug #2666

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

Added by laforge about 2 months ago. Updated 26 days ago.

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

0%

Resolution:

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

History

#1 Updated by laforge 26 days ago

  • Category set to A interface (AoIP)

Also available in: Atom PDF