openbsc.git branch zecke/features/rtp-bridge updated. 0.14.0-148-g14a088a

gitosis at gitosis at
Tue Aug 4 13:00:19 UTC 2015

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, zecke/features/rtp-bridge has been updated
  discards  eee8ab5eaeb1aeed3030907c30592e63331d9d2d (commit)
  discards  dba46be6ee15bc38849723678a1b1c9d079e9a4b (commit)
  discards  35ddcac8bef8c148b9312851fe3f3855cc256800 (commit)
       via  14a088a92162fd6abb3031e025ce59fba40af718 (commit)
       via  05a09059145ff4bfb1a09ec50e22fb75f2f4ca1e (commit)
       via  38b66fe3785595dabb59e9eec30d3809d64d54d6 (commit)
       via  7f0f8c690f5122786454eb0b2f6f1a5a58a95574 (commit)
       via  3479a7ca55d650404a7066ef586e887bcaae2500 (commit)
       via  8e969e17cefe0bb99ef4c15710f3a68906a38851 (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 (eee8ab5eaeb1aeed3030907c30592e63331d9d2d)
             N -- N -- N (14a088a92162fd6abb3031e025ce59fba40af718)

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 14a088a92162fd6abb3031e025ce59fba40af718
Author: Holger Hans Peter Freyther <holger at>
Date:   Tue Aug 4 14:41:21 2015 +0200

    mncc: Implement CRCX->MDCX for handover for direct rtp mode
    Implement sending MDCX on the newly allocated channel and send
    the data to the same destination as the currently connected one.
    This way the receiver can implement RTP RFC Appendix A.1 and
    deal with the new source.

commit 05a09059145ff4bfb1a09ec50e22fb75f2f4ca1e
Author: Holger Hans Peter Freyther <holger at>
Date:   Tue Aug 4 13:32:09 2015 +0200

    mncc: Implement the direct RTP mode for ip based systems
    For the LCR rtp-bridge audio should directly flow to the
    remote system. In contrast to the original patch audio
    will now flow directly from the BTS to the remote system.
    This assumes that BTS and the remote system are in the
    same network segment and can directly communicate.
    There are various limitations in the first iteration of
    the implementation:
    We could (and in the future) should delay the assignment
    but currently we are forced to pick the channel and move
    it to the audio state. In case we are located on a SDCCH
    we always need to change but if we are on a TCH we could
    send the ipa.CRCX and change the audio state a lot later.
    The net effect is that the audio codec selection needs to
    be done in the NITB code and not in the system connected
    to it.
    This only works with ip based systems. For E1 systems one
    could still use the RTP socket or even try to move this
    out of the process.
    There is no code for handover handling and it relies on
    the remote system dealing with the SSRC change of the

commit 38b66fe3785595dabb59e9eec30d3809d64d54d6
Author: Holger Hans Peter Freyther <holger at>
Date:   Tue Jul 14 16:03:41 2015 +0200

    mncc: Update the protocol to match LCR
    This adds the protocol definition for the RTP bridge extension
    of Andreas Eversberg and bumps the protocol version.
    I added the missing mncc mappings from value to string.
    [ 5cf8fb10ea3addcae74d37f4dbf1c1be664df53e protocol extension
      5dac90de38990b188f499c602bf18a4f232070e8 payload extension]

commit 7f0f8c690f5122786454eb0b2f6f1a5a58a95574
Author: Holger Hans Peter Freyther <holger at>
Date:   Tue Aug 4 12:22:56 2015 +0200

    subscr: Fix subscr refcount issue in case of message error
    In case the SMPP payload didn't include the right fields we
    would leak the subscr reference count.

commit 3479a7ca55d650404a7066ef586e887bcaae2500
Author: Holger Hans Peter Freyther <holger at>
Date:   Tue Aug 4 11:37:30 2015 +0200

    subscr: Fix potential subscr ref count issue
    In case the subscriber is currently busy we would omit the
    subscr_put. This seems to be very hard to hit as the subscr
    need to be active and at the same time be selected for the
    purge operation.

commit 8e969e17cefe0bb99ef4c15710f3a68906a38851
Author: Holger Hans Peter Freyther <holger at>
Date:   Tue Aug 4 12:52:05 2015 +0200

    paging: Provide information about pending requests
    For debugging it is nice to know how many requests are
    pending. Simply count it and print it besides the paging


Summary of changes:
 openbsc/include/openbsc/gsm_data.h        |  1 +
 openbsc/src/libmsc/gsm_04_08.c            | 53 +++++++++++++++++++++++--------
 openbsc/src/libmsc/gsm_subscriber.c       |  1 +
 openbsc/src/libmsc/smpp_openbsc.c         |  2 ++
 openbsc/src/libmsc/vty_interface_layer3.c | 10 ++++--
 5 files changed, 51 insertions(+), 16 deletions(-)

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

More information about the osmocom-commitlog mailing list