12 Apr
2017
12 Apr
'17
1:35 a.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, laforge/sigtran-rkm has been updated
discards 493106f6d142700b8caf2c8c36e0ad07768579c0 (commit)
discards e79a574fccda66f746945fbab06fdd6afde0fe4c (commit)
discards f90ed904ee8dce327965e0b96a8cc9644001369b (commit)
discards a196f766cc4409c52295d3936a79138312ccdea1 (commit)
discards e7b30bca5c058ba0174616af7d806a384739bfb7 (commit)
discards 0e847aa360da04cf68bf0fb2827da594ce32b7cb (commit)
discards 06c0afa9f5fc9ec53ccc0d58e38dc95f07b20957 (commit)
discards fe5fbc8f488f868665917724f94a00378c94e6e7 (commit)
discards 15a3d4b01c45327be8dd80a30c346012a34572c5 (commit)
discards 35250c8e152f685e9d9cfd0cd212e98e444e0850 (commit)
discards 3dd7175f0b907b343dce3f813ece5e72404e16af (commit)
discards 6a761b1aae9bbb0308001127cf6859c6745ba79b (commit)
discards 0a1d48b752d6ff3da70c17b5cee1cf5b12c14505 (commit)
discards 28502175a49a349d74496b42790b211e82a3f331 (commit)
discards 9b7704d5fce837b9acf861e8cc83f68d828e48b0 (commit)
discards 236fc9938b90fa3300b01a386137adf20ff5cfcc (commit)
via 1bb6b26f3a56d7b62c1299328b8c7c227f1aa816 (commit)
via 8f86bc4a1cc6835e0f3b7dae3a92ee1d67731161 (commit)
via b13114c053f30705506359c6bf57514bb1ef601d (commit)
via f078d11d10b6410e574ab2766c0c3e804d53fe50 (commit)
via d769ce45bcdf22c7e24a4ce6ee4371c03ef271c0 (commit)
via c81bf792313efab16f13bdf37c4380f48d261ecf (commit)
via 47d05fae4f7ffa2b9a680b52a96bff15d1d16df0 (commit)
via 282d1c2ffa7403d1238c308401d66dcd271f761f (commit)
via fb82880905c77e3eead73c0572364fbd0de9b2e3 (commit)
via bba8fe816663e3d7d73219df052dee17a630ff6d (commit)
via 2c2ae5997cb3472ed0330f52892c69b5d8a4d5ba (commit)
via 8af8d643de2bd6a02c65b2659fd0afa62e865cd6 (commit)
via ed18c11de92b4c4596815e8d9ff74c49d6ae853b (commit)
via 1978e3a3203512500da7eeff9a614e096f46a5be (commit)
via b650dd9d77779b745bd062ed73ff7b7c6d2c9c16 (commit)
via 5181c5fe1b2c4b5303ddb0e4608c0cedaeb28d90 (commit)
This update added new revisions after undoing existing revisions. That is
to say, the old revision is not a strict subset of the new revision. This
situation occurs when you --force push a change and generate a repository
containing something like this:
* -- * -- B -- O -- O -- O (493106f6d142700b8caf2c8c36e0ad07768579c0)
\
N -- N -- N (1bb6b26f3a56d7b62c1299328b8c7c227f1aa816)
When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.
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=1bb6b26f3a56d7b62c1299328b8…
commit 1bb6b26f3a56d7b62c1299328b8c7c227f1aa816
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Sun Apr 2 11:58:17 2017 +0200
WIP: Add IPA/SCCPlite stacking
Change-Id: I9098574cddeba10fcf8f1b6c196a7069a6805c56
http://cgit.osmocom.org/libosmo-sccp/commit/?id=8f86bc4a1cc6835e0f3b7dae3a9…
commit 8f86bc4a1cc6835e0f3b7dae3a92ee1d67731161
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Tue Apr 11 20:45:36 2017 +0200
osmo_ss7: Release any dynamically-allocated ASs
When RKM dynamically allocates ASs on the SGP based on RKM registration
requests, we must make sure to properly destroy those at the time the
related ASP disconnects. Also, make sure to send
XUA_ASP_E_SCTP_COMM_DOWN_IND to the layer manager (if any).
Change-Id: Ie6505680bb6890814ae36858c54a2a6d2850f5cf
http://cgit.osmocom.org/libosmo-sccp/commit/?id=b13114c053f30705506359c6bf5…
commit b13114c053f30705506359c6bf57514bb1ef601d
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Tue Apr 11 18:51:58 2017 +0200
xua_rkm: Make dynamic registration of Routing Keys work
The existign xua_rkm code was merged a bit pre-maturely as it was not
properly tested. This adds a lot of fixes to make it work at all in the
first place, as well as the configurable option for fully dynamic
routing key management, where ASs and routing keys must not be
configured statically by administrative means, but clients (ASPs) can
simply come and register for whatever point code they want.
Change-Id: I79a070fa7b271b44995511f7b3ff7cc6beec8278
http://cgit.osmocom.org/libosmo-sccp/commit/?id=f078d11d10b6410e574ab2766c0…
commit f078d11d10b6410e574ab2766c0c3e804d53fe50
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Tue Apr 11 18:50:59 2017 +0200
xua_rkm: Improve comments about functions
Change-Id: I2f17baae37718e277eae54d4d225f8fcb2eb4aae
http://cgit.osmocom.org/libosmo-sccp/commit/?id=d769ce45bcdf22c7e24a4ce6ee4…
commit d769ce45bcdf22c7e24a4ce6ee4371c03ef271c0
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Fri Apr 7 17:14:54 2017 +0200
Add a default layer manager using RKM to register PC with SG
This "default layer manager" can optionally be used by a xUA ASP. It
will handle the xUA Layer Manager (xlm) primitives and use them to
behave as follows:
* bring the ASP into state "INACTIVE"
* see if the SG can match our connection (based on IP address + port
information) to a statically configured ASP configuration with
associated AS(s). If yes, it will send us a NOTIFY message with
AS-INACTIVE.
* if the above doesn't work, try to dynamically register a routing key
using RKM for the point code that was locally confiured on the
ASP/client. If that works, the SG will now have created ASP and AS
objects as well as a routing key and be able to serve us, sending the
NOTIFY with the AS-INACTIVE state.
* After either of the two above, we will attempt to transition into
ASP-ACTIVE. The SG should send us an AS-ACTIVE notification in return
* if anything fails, abort and disconnect the SCTP connection, restart
related FSMs and start from scratch
Change-Id: I78d4623dd213b5c59007a026a6cc3cfe5c04af50
http://cgit.osmocom.org/libosmo-sccp/commit/?id=c81bf792313efab16f13bdf37c4…
commit c81bf792313efab16f13bdf37c4380f48d261ecf
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Wed Apr 5 11:14:24 2017 +0200
Add osmo-stp executable as new "Osmocom Signaling Transfer Point"
osmo-stp is able to define multiple M3UA and/or SUA application servers
(AS) as well as application server processes (ASPs). Clients can then
connect via M3UA or SUA, perform the respective ASPSM / ASPTM state
changes and finally exchange MTP signaling such as ISUP or SCCP on top
of it. Routing is currently only based on point codes (PC). Routing table
is fully configurable with Destination PC and mask.
Shortcomings:
* xUA: only "override" traffic mode supported, no load-balance or broadcast
* xUA: no SNM supported, i.e. DAVA/DUNA/... messages are neither parsed
nor generated
* SCCP: no Global Title based Routing (GTR) yet
* SCCP: no Global Title Translatio (GTT) yet
* no M2PA / M2UA sigtran dialects
* no classic CS7 based signaling links(E1/T1 TDM)
Change-Id: If32227b8d3127c6178e4ee45527ce65f69bc7b1e
-----------------------------------------------------------------------
Summary of changes:
src/osmo_ss7.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
SCCP Library