openbsc.git branch neels/vlr updated. 0.15.0-672-g2466a23

gitosis at gitosis at
Mon Dec 19 03:11:05 UTC 2016

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 "The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)".

The branch, neels/vlr has been updated
  discards  891405ba0c994e22d5c879921b7bdf19b0914b28 (commit)
  discards  e4ba3ef176702ba6e9b532e98450a73498f7646d (commit)
  discards  d771af192aae1c8acae45aac75df8f34c2e6a5d1 (commit)
       via  2466a2385ff061926a20e95dd4e8a46fc029b0d4 (commit)
       via  26e05c01b7516788e790403895b455ccab2b00aa (commit)
       via  f4f464e27db256190aa38862d315b87d802fe03b (commit)
       via  5f244333b074837f986ef49e820d98c61b69b988 (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 (891405ba0c994e22d5c879921b7bdf19b0914b28)
             N -- N -- N (2466a2385ff061926a20e95dd4e8a46fc029b0d4)

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 2466a2385ff061926a20e95dd4e8a46fc029b0d4
Author: Neels Hofmeyr <nhofmeyr at>
Date:   Mon Dec 19 04:07:29 2016 +0100

    vlr: debug log: log received GSUP MSISDN
    Change-Id: I80c00862be880b58ada39d1585c7cbdbe96228ee

commit 26e05c01b7516788e790403895b455ccab2b00aa
Author: Neels Hofmeyr <nhofmeyr at>
Date:   Mon Dec 19 03:51:11 2016 +0100

    vlr: fix: decode GSUP MSISDN from BCD without leading '0'
    When using gsm48_mi_to_string() to decode the MSISDN, odd-length numbers are
    preceded by a leading zero, which may break things. Instead, use
    gsm48_decode_bcd_number() to do the job properly.
    E.g. when the hlr.db contains '12345', it gets encoded as bcd hex L=03 V=2143f5
    in GSUP, which apparently gets right-justified to "012345" in
    gsm48_mi_to_string(). gsm48_decode_bcd_number()'s result is just "12345".
    However, to benefit from the available length (gsup_msg->msisdn_enc_len),
    provide a function decode_bcd_number_safe(), which adds input length checks to
    gsm48_decode_bcd_number() by means of an additional argument.
    Todo: maybe add such a length check to libosmocore, deprecating the original
    gsm48_decode_bcd_number(); add unit tests for the length checks and BCD
    Change-Id: Ia3428792562c3f7f4ba339d000536373e0513f8e

commit f4f464e27db256190aa38862d315b87d802fe03b
Author: Neels Hofmeyr <nhofmeyr at>
Date:   Mon Dec 19 02:46:41 2016 +0100

    tmp log: ussd
    Change-Id: I5cc462111054207d8022ea801e9ef3a77d11d780

commit 5f244333b074837f986ef49e820d98c61b69b988
Author: Neels Hofmeyr <nhofmeyr at>
Date:   Mon Dec 19 04:10:19 2016 +0100

    vlr: ussd: use vlr_subscriber's msisdn
    Change-Id: I1b4b0aa1ccb5417294148ca54572319d042aa8a7


Summary of changes:

The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

More information about the osmocom-commitlog mailing list