pespin uploaded patch set #2 to this change.

View Change

asp: Tx DAUD when ASP becomes activated

Otherwise the local Signalling Point has no way to know whether the
remote Signalling Points it wants to talk to are actually already
connected to the STP when it becomes active after the process starts up.
This pocedure is documented both for M3UA and SUA:
* RFC4666 4.6, RFC3868 4.6
* RFC4666 4.5.3, RFC3868 4.5.3 "ASP Auditing"
* RFC4666 5.5.1.1.3 "Support for ASP Querying of SS7 Destination States"

The M3UA specs (RFC4666 5.5.1.1.3) explicitly state that the point codes to audit are not
to be provided by uppers layers, so picking the ones from the locally
configured address book for now:
"""
 Note: there is no primitive for the
   MTP3-User to request this audit from the M3UA layer, as this is
   initiated by an internal M3UA management function.
"""

Related: OS#5917
Related: SYS#7501
Change-Id: I7c8c5099d4d00ea6f4a8db59ed6b833fb0ffa43d
---
M src/m3ua.c
M src/sua.c
M src/xua_asp_fsm.c
M src/xua_internal.h
M src/xua_snm.c
5 files changed, 110 insertions(+), 4 deletions(-)

git pull ssh://gerrit.osmocom.org:29418/libosmo-sigtran refs/changes/01/40501/2

To view, visit change 40501. To unsubscribe, or for help writing mail filters, visit settings.