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 872c6b2a8e309ca6739ef295f1fc468c189e4ec9 (commit) via 5527df78adc08b76df07c4b682263b5bdd6181d4 (commit) from b3546525024e8a183bb9b2e07eba82ead1397ed0 (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=872c6b2a8e309ca6739ef295f1fc...

commit 872c6b2a8e309ca6739ef295f1fc468c189e4ec9 Author: Harald Welte laforge@gnumonks.org Date: Thu May 4 09:06:09 2017 +0200

SUA-to-SCCP: Fix use of Called/Calling vs. Src/Dest Address

SUA uses different semantics (source / destination) address, while SCCP uses Calling/CalledParty. This leads to some confusion. At least in the CR/CORE and CREF/COREF case, the CallingParty equals the SRC_ADDR.

Change-Id: I1c641aac7b53c6de7c4e369aaf3004523bd85936

http://cgit.osmocom.org/libosmo-sccp/commit/?id=5527df78adc08b76df07c4b68226...

commit 5527df78adc08b76df07c4b682263b5bdd6181d4 Author: Harald Welte laforge@gnumonks.org Date: Thu May 4 08:58:53 2017 +0200

SCOC: When sending a CORE/CR, SUA SRC_ADDR == CallingPartyAddress

SUA uses different semantics (source / destination) address, while SCCP uses Calling/CalledParty. This leads to some confusion. At least in the CR/CORE case, the CallingParty equals the SRC_ADDR.

Change-Id: I5a3c27b112148dd539f092cce7618b4f62fde73c

-----------------------------------------------------------------------

Summary of changes: src/sccp2sua.c | 28 ++++++++++++++++++++++++---- src/sccp_scoc.c | 2 +- 2 files changed, 25 insertions(+), 5 deletions(-)

hooks/post-receive