Feature #4219

IPA: no point code insertion to SCCP

Added by laforge 12 days ago. Updated 38 minutes ago.

In Progress
Target version:
Start date:
Due date:
% Done:



As incoming messages on the IPA/SCCPlite protocol do not have a MTP routing label, nor is there any requirement for the SCCP Addresses to contain point codes, the IPA/SCCPlite support of osmo-stp currently inserts/adds “artificial” point codes at the point of IPA/SCCPlite ingress. Those point codes are added both to the [newly-created] MTP label, but also to the SCCP Addresses.

We require a mode of operation for osmo-stp where the point codes are not inserted into the SCCP addresses.

Related issues

Related to OsmoSTP - Bug #4236: osmo-stp segfaults if IPA client sends unparseable SCCPIn Progress10/19/2019


#1 Updated by laforge 1 day ago

  • Assignee changed from pespin to laforge

#2 Updated by laforge 1 day ago

  • Related to Bug #4236: osmo-stp segfaults if IPA client sends unparseable SCCP added

#3 Updated by laforge 1 day ago

  • Status changed from New to In Progress

#4 Updated by laforge 38 minutes ago

  • % Done changed from 0 to 80

Functionality implemented in

Related automatic tests are present as TC_ipa_to_m3ua and TC_ipa_to_m3ua_patch_sccp in STP_Tests.ttcn currently under development.

Let's keep this open until the tests are merged.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)