osmo-iuh.git branch pre_release updated. 2627a983408cacb58b0a21ddcd6b737a2a72bdac

gitosis at osmocom.org gitosis at osmocom.org
Tue Aug 8 07:04:50 UTC 2017

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 "Osmocom code for Iuh interface".

The branch, pre_release has been updated
  discards  9b9ad6623dff4913f5cac057f435dcae9718944a (commit)
  discards  d5a564775f84814edf23358e9330da13acc90408 (commit)
       via  2627a983408cacb58b0a21ddcd6b737a2a72bdac (commit)
       via  f4ed50c78263ac20cad27494e7b30636dcdc960f (commit)
       via  aae68b2791c636b6a58068bb43cf4c01cfd86c5d (commit)
       via  13850b1e5dc10975bf0452d2b8290bdbe2a8356f (commit)
       via  a3bcd6d1e71e866fa96a40437aeff9a6e44c76a2 (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 (9b9ad6623dff4913f5cac057f435dcae9718944a)
             N -- N -- N (2627a983408cacb58b0a21ddcd6b737a2a72bdac)

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 -----------------------------------------------------------------

commit 2627a983408cacb58b0a21ddcd6b737a2a72bdac
Author: Neels Hofmeyr <nhofmeyr at sysmocom.de>
Date:   Thu Jul 27 14:37:03 2017 +0200

    apply ctx arg to osmo_ss7_vty_init_asp()
    Depends: libosmo-sccp Id4e7f47979001f7856b0b3665c9e94982e75e490
    Change-Id: Idccbdc669d740179153d0a73096745785bd2f5af


commit f4ed50c78263ac20cad27494e7b30636dcdc960f
Author: Neels Hofmeyr <nhofmeyr at sysmocom.de>
Date:   Mon Jul 31 13:13:24 2017 +0200

    make point codes configurable by SCCP address book
    In the vty config, use the SCCP address book to configure the local and remote
    SCCP addresses. Add VTY commands to set the remote SCCP addresses by name,
    derive the ss7 instance from these addresses:
      cs7 instance 1
       point-code 0.23.0
       sccp-address msc
        point-code 0.0.1
       sccp-address sgsn
        point-code 0.0.2
        remote-addr msc
        remote-addr sgsn
    Enforce that both IuCS and IuPS use the same ss7 instance. In the future, we
    may add the feature to use two separate instances.
    Depends: libosmo-sccp I75c67d289693f1c2a049ac61cf2b2097d6e5687d,
    Change-Id: I33a7ba11eb7c2d9a5dc74d10fb0cf04bf664477b


Summary of changes:
 include/osmocom/iuh/hnbgw.h    |  12 ++--
 include/osmocom/iuh/hnbgw_cn.h |   3 +-
 src/hnbgw.c                    |  22 +-------
 src/hnbgw_cn.c                 | 123 +++++++++++++++++++++++++++++++++++------
 src/hnbgw_rua.c                |   4 +-
 src/hnbgw_vty.c                |  74 +++++++++----------------
 6 files changed, 143 insertions(+), 95 deletions(-)

Osmocom code for Iuh interface

More information about the osmocom-commitlog mailing list