osmocom
/
libosmo-sccp
mirror of https://gerrit.osmocom.org/libosmo-sccp
14
0
Fork 0
Code Issues Releases Wiki Activity
SCCP + SIGTRAN (SUA/M3UA) libraries as well as OsmoSTP https://osmocom.org/projects/libosmo-sccp
778 Commits 38 Branches 31 Tags 10 MiB
C 68.8%
HTML 28.7%
Shell 0.7%
Makefile 0.7%
M4 0.6%
Other 0.5%
Go to file
Harald Welte 2f8b645ecb sccp_scrc: Ensure we have not just SSN but at least OPC+SSN in CallingParty 
There are implementations out there which send us traffic, specifically
in this case SCMG (SST) that has only SSN in both Called and Calling
Party. This means the inbound SST message is routed correctly to the
local SCCP user of libosmo-sigtran. But when that local SCCP user
responds with inverting Called/Calling Party, the new destination again
just contains a SSN.

As a result, we don't know where to route the message (we always need a PC).

Change-Id: Id66ae960ebe3cb3b09c6dd5454f9ac9c073f46d7
Closes: OS#5146
 		2021-05-13 22:00:14 +02:00
contrib Bump version: 1.3.0.51-6858-dirty → 1.4.0 2021-02-23 17:57:33 +01:00
debian Bump version: 1.3.0.51-6858-dirty → 1.4.0 2021-02-23 17:57:33 +01:00
doc manuals: generate vty reference xml at build time 2021-02-23 17:20:08 +01:00
examples examples/sccp_test_server: Log disconnect indication in echo service 2020-01-21 10:53:34 +01:00
include m3ua/sua: Add new snm_inactive quirk 2021-05-13 18:11:53 +02:00
specs add RFC 3868 (SUA) spec in HTML 2017-01-27 09:59:30 +01:00
src sccp_scrc: Ensure we have not just SSN but at least OPC+SSN in CallingParty 2021-05-13 22:00:14 +02:00
stp stp: generate coredump and exit upon SIGABRT received 2021-02-23 17:40:46 +01:00
tests ss7_asp_test.vty: Allow more asp node commands after shutdown 2021-05-11 20:36:31 +02:00
.gitignore gitignore: Ignore autofoo *~ churn 2021-02-19 13:06:27 +01:00
.gitreview Add gerrit settings 2016-12-21 13:46:12 +01:00
COPYING move openbsc into its own subdirectory 2009-06-10 05:40:52 +08:00
Doxyfile.in Doxugen: s/libosmo-sccp/libosmo-sigtran/g 2017-10-27 21:10:18 +02:00
Makefile.am Makefile.am: EXTRA_DIST: debian, contrib/*.spec.in 2020-05-22 13:29:41 +02:00
README.md Add README.md describing what this repo is about 2021-03-21 22:56:42 +01:00
TODO-RELEASE Bump version: 1.3.0.51-6858-dirty → 1.4.0 2021-02-23 17:57:33 +01:00
configure.ac Bump version: 1.3.0.51-6858-dirty → 1.4.0 2021-02-23 17:57:33 +01:00
git-version-gen git-version-gen: Don't check for .git directory 2018-07-24 18:03:20 +02:00
libosmo-mtp.pc.in Revert "Fix the .pc files so the -l arg matches the installed libraries" 2016-11-03 13:04:34 +00:00
libosmo-sccp.pc.in Revert "Fix the .pc files so the -l arg matches the installed libraries" 2016-11-03 13:04:34 +00:00
libosmo-sigtran.pc.in libosmo-sigtran: Add pkg-config integration 2015-12-22 23:03:44 +01:00
libosmo-xua.pc.in Add missing xua.pc file 2016-11-03 12:36:41 +00:00
osmoappdesc.py osmoappdesc.py, tests: switch to python 3 2019-12-12 09:18:58 +00:00

README.md

libosmo-sccp - Osmocom SCCP, SIGTRAN and STP

This repository contains a C-language library implementation of a variety of telecom signaling protocols, such as M3UA, SUA, SCCP (connection oriented and connectionless), as well as the OsmoSTP, a SS7 Transfer Point.

Homepage

The official homepage of libosmo-sccp is https://osmocom.org/projects/libosmo-sccp/wiki

The official homepage of osmo-stp is https://osmocom.org/projects/osmo-stp/wiki

GIT Repository

You can clone from the official git repository using

git clone git://git.osmocom.org/libosmo-sccp.git
git clone https://git.osmocom.org/libosmo-sccp.git

There is a cgit interface at https://git.osmocom.org/libosmo-sccp/

Documentation

User Manuals and VTY reference manuals are [optionally] built in PDF form as part of the build process.

Pre-rendered PDF version of the current "master" can be found at User Manual as well as the VTY reference manuals

Mailing List

Discussions related to osmo-stp are happening on the openbsc@lists.osmocom.org mailing list, please see https://lists.osmocom.org/mailman/listinfo/openbsc for subscription options and the list archive.

Please observe the Osmocom Mailing List Rules when posting.

Contributing

Our coding standards are described at https://osmocom.org/projects/cellular-infrastructure/wiki/Coding_standards

We us a gerrit based patch submission/review process for managing contributions. Please see https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit for more details

The current patch queue can be seen at https://gerrit.osmocom.org/#/q/project:libosmo-sccp+status:open