Subject: openbsc.git branch master updated. 0.13.0-110-g3db24b5
From: [email-masked]
To: [email-masked]
Date: Sat, 3 Aug 2013 17:24:24 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, master has been updated
       via  3db24b5fe4d169afcde9195d2255b7a7f342d0bc (commit)
       via  045f4022984bd682cc6ddd68e363c04b88fe557e (commit)
       via  99e273db00a09d68adce36709f84cf43e0efb5a7 (commit)
       via  1aeb2af75d27fdb4ab31d145ec49e84e29ecd501 (commit)
      from  14d1177735bb751aa9e2796c58c1d746a5b0de9c (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/openbsc/commit/?id=3db24b5fe4d169afcde9195d2255b7a7f342d0bc

commit 3db24b5fe4d169afcde9195d2255b7a7f342d0bc
Merge: 14d1177 045f402
Author: Holger Hans Peter Freyther <[email-masked]>
Date:   Sat Aug 3 19:22:38 2013 +0200

    Merge branch 'laforge/smpp-fixes'
    
    These commits have been deployed by sysmocom and it should qualify
    as some form of smoke testing. Let's see how things go from here.
    The by IMSI alertion has not been used, the rest should have been
    executed by the system.

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

commit 045f4022984bd682cc6ddd68e363c04b88fe557e
Author: Harald Welte <[email-masked]>
Date:   Tue Jul 30 23:45:01 2013 +0800

    SMPP: use VTY setting for E212/E164 in ALERT NOTIFICATION
    
    There's a VTY option by which for every ESME the user can specify if the
    E.212 or E.164 number should be used in DELIVER-SM.  The ALERT
    notifications generate by subscriber LU have so far always contained the
    E.212 (IMSI) rather than E.164 (MSISDN) which is a bit inconsistent.
    
    Rather than copying code, we create a new function that implements
    ALERTing all ESMEs.

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

commit 99e273db00a09d68adce36709f84cf43e0efb5a7
Author: Harald Welte <[email-masked]>
Date:   Tue Jul 30 23:39:18 2013 +0800

    SMPP: convert a SMMA to a SMPP ALERT NOTIFICATION

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

commit 1aeb2af75d27fdb4ab31d145ec49e84e29ecd501
Author: Harald Welte <[email-masked]>
Date:   Tue Jul 30 22:30:24 2013 +0800

    SMPP: don't get stuck in case of SMS memory exceeded
    
    If the MS memory for SMS is exceeded and we get an RP-layer error, we
    need to report that back to the (transaction-mode) ESME.  Otherwise the
    ESME will wait forever after sending a SUBMIT-SM without ever receiving
    a response to it.
    
    Thanks to Holger for catching this.

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

Summary of changes:
 openbsc/src/libmsc/smpp_openbsc.c | 53 +++++++++++++++++++++++++++++++--------
 1 file changed, 43 insertions(+), 10 deletions(-)

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