11 Nov
2017
11 Nov
'17
8:52 p.m.
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "SCCP Library".
The branch, master has been updated
via 510375efd3893bf927d9b50823e080d79020e8de (commit)
via bc44437a4370843886dc993223885cafbcd50ea4 (commit)
via f4a127ef9940c650ad2c633028998b0c6e8524a9 (commit)
via 450cdd8b187c9508889a379cd882800468a870fe (commit)
from 0bd848c11229fad572b478d0515ea36dc0a18e48 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/libosmo-sccp/commit/?id=510375efd3893bf927d9b50823e…
commit 510375efd3893bf927d9b50823e080d79020e8de
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Sat Nov 11 23:46:29 2017 +0900
ipa: Automatically create / destroy route on IPA connect/disconnect
From the STP point of view: In order to be able to route messages back
to an IPA client, we need to create a route at the time we have
successfully identified the AS for this client based on the name
presented in the IPA CCM ACK "name" field. Once the IPA client is
destroyed, the route must be deleted again.
With this commit present, we can have an IPA client (such as
osmo-bsc-sccplite) connect to OsmoSTP and exchange BSS[M]AP
with an M3UA-speaking osmo-msc. Basically, the STP reaches
the point where it can translate between IPA-style SCCPlite
and proper M3UA/SUA on the other side.
Change-Id: I901f06c5d0f2eae60f8d931215ed65190330ce66
http://cgit.osmocom.org/libosmo-sccp/commit/?id=bc44437a4370843886dc9932238…
commit bc44437a4370843886dc993223885cafbcd50ea4
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Fri Nov 10 16:42:43 2017 +0900
ipa: Patch DPC/OPC information into SCCP Calling/Called Party Address
When we receive a SCCPlite message from an IPA peer, it may simply
contain a SSN number but no point codes. Similarly to creating a fake
MTP routing label from override DPC and routing key OPC, we can also
add that point code information to the SCCP header. This way the rest
of the SS7 network can handle the message and route it accordingly.
Change-Id: I4a2ff063e3c060641b3fd181a1cd600da3ec568b
http://cgit.osmocom.org/libosmo-sccp/commit/?id=f4a127ef9940c650ad2c6330289…
commit f4a127ef9940c650ad2c633028998b0c6e8524a9
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Fri Nov 10 16:44:56 2017 +0900
initialize msg->l2h in sccp_msgb_alloc()
Change-Id: I5fb11075593696b110bfd3e0541e3aa790029903
http://cgit.osmocom.org/libosmo-sccp/commit/?id=450cdd8b187c9508889a379cd88…
commit 450cdd8b187c9508889a379cd882800468a870fe
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Fri Nov 10 13:25:58 2017 +0900
ipa: Fix endianness of pseud-M3UA header
Change-Id: I70b420fc2105bb6e486adecf9285fed2fb471f73
-----------------------------------------------------------------------
Summary of changes:
src/ipa.c | 108 +++++++++++++++++++++++++++++++++++++++++++-------
src/sua.c | 9 ++++-
src/xua_asp_fsm.c | 33 +++++++++++++++
tests/xua/xua_test.ok | 22 +++++-----
4 files changed, 144 insertions(+), 28 deletions(-)
hooks/post-receive
--
SCCP Library