Subject: openbsc.git branch jolly/testing updated. 0.13.0-319-g30e0e36
From: [email-masked]
To: [email-masked]
Date: Thu, 13 Mar 2014 07:13:52 GMT

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, jolly/testing has been updated
  discards  65cd751f525460de5ac8e05d92e45da98ec863dd (commit)
  discards  25ac32c900d25b0e713808b79fec55b9af0d84b6 (commit)
  discards  442007458f7438c65ad56249523034e0ec8a2f9c (commit)
  discards  54577109babd3651b5236e95642c5e4310116216 (commit)
  discards  a8bb67eeae3711f39eb0e159db8abbb77a7c49b2 (commit)
  discards  5c9805fe1d816d9320a29d1276e3b50a9620c1c7 (commit)
  discards  f3e49693d3c3da673fdaf67393f2b6b40e40fcdb (commit)
  discards  a5395bf4fba8da61b7199c8aca0511fcc9cb1e46 (commit)
  discards  90fbba8f263f98a2e0640dad14f889a26fbb31bb (commit)
  discards  512c480a30f52d13204e6d50de05372435c8bc87 (commit)
  discards  052110ea4d77b52cdd34ce84748f0e6b078d7f7e (commit)
  discards  366ae9cc7c641def9fdec45ca35ae632e8850bce (commit)
  discards  cd01270dbf63bb312a642e485d711d58d8850f1a (commit)
  discards  a8ec80a56f14f12a9ec06dc5a32d6c2964ec26e9 (commit)
  discards  28ad0f8a78fba3a176ed9af1b49fa8c2974efaa3 (commit)
  discards  74c9c83b25d6a8c6449a84533361087df0726d5c (commit)
  discards  640349ea0bae4c885377eaf9e8f4e821de33dfb7 (commit)
  discards  d96f036773b8ae7167e4eed308797a25f33d0404 (commit)
  discards  021e00a7edd9eeb3606334c767ce720b5b268057 (commit)
  discards  40b11131a979753aba073edb4244457a57b68e58 (commit)
       via  30e0e36b9e6098403ac405c5e9dc65ef7ddef6bd (commit)
       via  2c74baa28e49deab88b31e3f8e43a3b44282eb83 (commit)
       via  eb672b3f83b4a34c8468ac05f21c82a42141387f (commit)
       via  db24133fc8d5ded72b4e4134c5d5f7d9203c5704 (commit)
       via  cffe22743970fbcb25fa07ffc76d9c13d2abfd79 (commit)
       via  586d0f5d0bd8ce76d4d8cdd77b41978dfc9b91d9 (commit)
       via  1c71cd0b0d4f53386ca80fe7cf9e42b4d96d7961 (commit)
       via  e1646a5d595e26b24f1fe2252dabf547bb1b3162 (commit)
       via  b01c271f4d478787448e5e271e2b2a72e040127d (commit)
       via  2949d1dd88f6a0d06fdb5dc798a4526429ed4862 (commit)
       via  8d416870e848ee2e49eb98d14a4700912f37697c (commit)
       via  fd395f45032a9e4d388b95211838cf8116dc8411 (commit)
       via  c2d1a2196ac59dd338bd142e1fbefd9c1e8ae235 (commit)
       via  5dac90de38990b188f499c602bf18a4f232070e8 (commit)
       via  5cf8fb10ea3addcae74d37f4dbf1c1be664df53e (commit)
       via  7bf004903e3b8ee483c3f461199088eb3c84a45b (commit)
       via  9b62b28e38f5377bca3af80d428da53566b6102e (commit)
       via  74900666a2c37f3f3044151483045dee55f85a5e (commit)
       via  b61bf77675d1d1c21c1f2a0502a822a45ab74fe5 (commit)
       via  4cab1c52082a96c7dfd39b8c176145f1b61946bf (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 (65cd751f525460de5ac8e05d92e45da98ec863dd)
            \
             N -- N -- N (30e0e36b9e6098403ac405c5e9dc65ef7ddef6bd)

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 -----------------------------------------------------------------
http://cgit.osmocom.org/openbsc/commit/?id=30e0e36b9e6098403ac405c5e9dc65ef7ddef6bd

commit 30e0e36b9e6098403ac405c5e9dc65ef7ddef6bd
Author: Andreas Eversberg <[email-masked]>
Date:   Thu Mar 7 15:25:48 2013 +0100

    HACK: Fix of several compiler warnings

http://cgit.osmocom.org/openbsc/commit/?id=2c74baa28e49deab88b31e3f8e43a3b44282eb83

commit 2c74baa28e49deab88b31e3f8e43a3b44282eb83
Author: Andreas Eversberg <[email-masked]>
Date:   Sun Mar 31 12:01:25 2013 +0200

    osmo-nitb support for codec negotiation
    
    The caller's most preferred codec is selected out of the union of codecs,
    which both parties support.
    
    Since codec negotiation is done automatically, there is no need to define
    codec for TCH/F and TCH/H via VTY anymore.

http://cgit.osmocom.org/openbsc/commit/?id=eb672b3f83b4a34c8468ac05f21c82a42141387f

commit eb672b3f83b4a34c8468ac05f21c82a42141387f
Author: Andreas Eversberg <[email-masked]>
Date:   Sun Mar 31 11:57:38 2013 +0200

    If requested TCH/H channel is not available, try assigning TCH/F
    
    If MNCC application requests a half rate channel, the channel might not be
    available, due to different cell configuration, so the full rate channel
    is used instead.

http://cgit.osmocom.org/openbsc/commit/?id=db24133fc8d5ded72b4e4134c5d5f7d9203c5704

commit db24133fc8d5ded72b4e4134c5d5f7d9203c5704
Author: Andreas Eversberg <[email-masked]>
Date:   Wed Jan 22 08:57:18 2014 +0100

    Add check to tch_map(), if RTP sockets exist

http://cgit.osmocom.org/openbsc/commit/?id=cffe22743970fbcb25fa07ffc76d9c13d2abfd79

commit cffe22743970fbcb25fa07ffc76d9c13d2abfd79
Author: Andreas Eversberg <[email-masked]>
Date:   Sun Mar 31 11:50:35 2013 +0200

    Fix: If half rate channel is used, indicate hr when modifying channel mode

http://cgit.osmocom.org/openbsc/commit/?id=586d0f5d0bd8ce76d4d8cdd77b41978dfc9b91d9

commit 586d0f5d0bd8ce76d4d8cdd77b41978dfc9b91d9
Author: Andreas Eversberg <[email-masked]>
Date:   Sun Mar 31 11:44:34 2013 +0200

    Fix: If paging for half rate was requested, use hr, if supported by MS

http://cgit.osmocom.org/openbsc/commit/?id=1c71cd0b0d4f53386ca80fe7cf9e42b4d96d7961

commit 1c71cd0b0d4f53386ca80fe7cf9e42b4d96d7961
Author: Andreas Eversberg <[email-masked]>
Date:   Sun Jan 19 11:47:44 2014 +0100

    Add full AMR multirate IE support with VTY config for MS and BTS side

http://cgit.osmocom.org/openbsc/commit/?id=e1646a5d595e26b24f1fe2252dabf547bb1b3162

commit e1646a5d595e26b24f1fe2252dabf547bb1b3162
Author: Andreas Eversberg <[email-masked]>
Date:   Thu Mar 14 09:41:18 2013 +0100

    Drop bad speech frames rather than forwarding them via RTP
    
    Some RTP endpoints may not check for bad frame indications, so a frame
    that is marked as bad may be still forwarded, which creates anoying noise.
    This patch drops these frames. It depends on the other RTP endpoint how
    dropped frames are handled. (insert silence, extrapolate speech...)

http://cgit.osmocom.org/openbsc/commit/?id=b01c271f4d478787448e5e271e2b2a72e040127d

commit b01c271f4d478787448e5e271e2b2a72e040127d
Author: Andreas Eversberg <[email-masked]>
Date:   Mon Mar 11 08:20:48 2013 +0100

    Add check for non existing lchan at tch_frame_down()
    
    Traffic cannot sent to BTS, if there is (currently) no logical channel
    associated with the transaction.
    
    This happens, if TCH traffic is received from upper layer, but there is
    no lchan available before completing immediate assignment, handover or
    assignment process.

http://cgit.osmocom.org/openbsc/commit/?id=2949d1dd88f6a0d06fdb5dc798a4526429ed4862

commit 2949d1dd88f6a0d06fdb5dc798a4526429ed4862
Author: Andreas Eversberg <[email-masked]>
Date:   Sun Mar 10 11:50:19 2013 +0100

    Send RADIO LINK TIMEOUT value via OML attribute to BTS
    
    The same radio link timeout value is used for BTS and MS side.

http://cgit.osmocom.org/openbsc/commit/?id=8d416870e848ee2e49eb98d14a4700912f37697c

commit 8d416870e848ee2e49eb98d14a4700912f37697c
Author: Andreas Eversberg <[email-masked]>
Date:   Sun Mar 10 11:49:35 2013 +0100

    Add option to set RADIO LINK TIMEOUT value via VTY

http://cgit.osmocom.org/openbsc/commit/?id=fd395f45032a9e4d388b95211838cf8116dc8411

commit fd395f45032a9e4d388b95211838cf8116dc8411
Author: Andreas Eversberg <[email-masked]>
Date:   Fri Mar 16 08:14:23 2012 +0100

    Fixed problem of mute audio on some calls
    
    When reading from RTP socket, the first read() may fail right after
    connecting to remote socket. Subsequent read() will work as it should.
    
    If the remote socket does not open fast enough, the transmitted RTP
    payload can cause an ICMP (connection refused) packet reply. This causes
    the read to fail with errno=111. In all other error cases, the errno is
    logged at debug level. In all error cases, reading is not disabled.

http://cgit.osmocom.org/openbsc/commit/?id=c2d1a2196ac59dd338bd142e1fbefd9c1e8ae235

commit c2d1a2196ac59dd338bd142e1fbefd9c1e8ae235
Author: Andreas Eversberg <[email-masked]>
Date:   Thu Mar 8 11:08:37 2012 +0100

    Fixed (ipaccess BTS) delay/silence problems, if RTP stream jitters too much
    
    After OpenBSC stalled for some reason (e.g. CPU overload or database
    access) or after speech frames have been lost (MNCC application problems /
    hold/retrieve call), the timestamp and the sequence number of the RTP
    socket state must be corrected. The amount of incrmentation is calculated
    from the elapsed time. Not incrementing timestamp and sequence number would
    cause all frames to be dropped by ipaccess BTS, because the BTS expects
    frames with more recent timestamps.
    
    If speech frames are received too fast, they must be dropped. The timestamp
    and sequence number of the RTP socket state are not changed in this case.
    Incmenetating timestamp and sequence number would causes high delay at
    ipaccess BTS, because the BTS would queue the frames until the timestamp
    matches the current time.
    
    There is a simple test case:
    
    Make a call between two phones and check the delay. (When using LCR, make
    a call to the echo test.) The press CTRL+z to suspend OpenBSC process for
    a few seconds and enter "fg" to continue OpenBSC process. There shall be no
    change in the delay, even after repeating this test many times.

http://cgit.osmocom.org/openbsc/commit/?id=5dac90de38990b188f499c602bf18a4f232070e8

commit 5dac90de38990b188f499c602bf18a4f232070e8
Author: Andreas Eversberg <[email-masked]>
Date:   Fri Feb 17 15:20:59 2012 +0100

    Allow dynamic RTP payload types between application and MNCC interface
    
    Since EFR/AMR/HR codecs use dynamic RTP payload, the payload type can
    be set. If it is set, the frame type must be set also, so OpenBSC
    knows what frame types are received via RTP.
    
    This modification only affects traffic beween application and MNCC
    interface, not the RTP traffic between OpenBSC and BTS.

http://cgit.osmocom.org/openbsc/commit/?id=5cf8fb10ea3addcae74d37f4dbf1c1be664df53e

commit 5cf8fb10ea3addcae74d37f4dbf1c1be664df53e
Author: Andreas Eversberg <[email-masked]>
Date:   Mon Jan 16 09:29:28 2012 +0100

    Add traffic forwarding via RTP to remote application
    
    Instead of forwarding traffic through MNCC interface, traffic can
    be forwarded to a given RTP peer directly. A special MNCC message
    is used to control the peer's destination. The traffic can still be
    forwarded through MNCC interface when this special MNCC message is
    not used.
    
    It also works with E1 based BTSs.
    
    In conjunction with LCR's "rtp-bridge" feature, the RTP traffic
    can be directly exchanged with a remote SIP endpoint, so that the
    traffic is not forwarded by LCR itself. This way the performance
    of handling traffic only depends on OpenBSC and the remote SIP
    endpoint. Also the traffic is exchanged with the SIP endpoint
    without transcoding, to have maximum performance.
    
    Increment MNCC version to 5.

http://cgit.osmocom.org/openbsc/commit/?id=7bf004903e3b8ee483c3f461199088eb3c84a45b

commit 7bf004903e3b8ee483c3f461199088eb3c84a45b
Author: Andreas Eversberg <[email-masked]>
Date:   Fri Jan 20 20:33:37 2012 +0100

    Add handling of BFI (Bad Frame Indicatior) of received TRAU frames
    
    If a bad TRAU frame is received, it is forwarded to MNCC application
    as GSM_BAD_FRAME. The application can now handle the GAP of missing
    audio. (e.g. by extrapolation)
    
    If TRAU frames are forwarded via RTP, bad frames are dropped, but frame
    counter and timestamp of RTP sender state is incremented.

http://cgit.osmocom.org/openbsc/commit/?id=9b62b28e38f5377bca3af80d428da53566b6102e

commit 9b62b28e38f5377bca3af80d428da53566b6102e
Author: Andreas Eversberg <[email-masked]>
Date:   Thu Mar 8 14:39:19 2012 +0100

    Add support for AMR frames to MNCC/RTP interface
    
    AMR rate is currently fixed to 5.9k.

http://cgit.osmocom.org/openbsc/commit/?id=74900666a2c37f3f3044151483045dee55f85a5e

commit 74900666a2c37f3f3044151483045dee55f85a5e
Author: Andreas Eversberg <[email-masked]>
Date:   Fri Jan 17 19:06:38 2014 +0100

    Add support for half rate V1 frames to MNCC/RTP interface

http://cgit.osmocom.org/openbsc/commit/?id=b61bf77675d1d1c21c1f2a0502a822a45ab74fe5

commit b61bf77675d1d1c21c1f2a0502a822a45ab74fe5
Author: Andreas Eversberg <[email-masked]>
Date:   Mon Mar 11 08:12:43 2013 +0100

    Use helper function to check if an MNCC frame is data (speech/traffic)
    
    Rename method mncc_rcv_tchf() to mncc_rcv_data(), because the check applies
    to all types of data frames, not only TCH/F data.

http://cgit.osmocom.org/openbsc/commit/?id=4cab1c52082a96c7dfd39b8c176145f1b61946bf

commit 4cab1c52082a96c7dfd39b8c176145f1b61946bf
Author: Andreas Eversberg <[email-masked]>
Date:   Fri Jan 31 09:02:01 2014 +0100

    Complete definitions for all speech traffic frames at MNCC interface
    
    The new definitions are: half rate and AMR
    
    Change of definition name for bad frame, because it applies to all types of
    traffic, not only TCH/F.
    
    Increase MNCC interface version to 4. Version 3 is skipped, because it was
    used by older version of Linux-Call-Router which is incompatible with the
    current version of the MNCC interface.

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

Summary of changes:

hooks/post-receive
-- 
The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)