Subject: openbsc.git branch zecke/mgcp-statistics updated. 0.12.0-183-g0a7d553
From: git repository hosting <[email-masked]>
To: [email-masked]
Date: Mon, 17 Dec 2012 13:00:55 +0100

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/mgcp-statistics has been updated
  discards  2cd4981757ffea1d5c7db77cfad9efb40441c522 (commit)
  discards  6bd5361facfd79efd4b8154dd8e8cac7fbdcba7b (commit)
  discards  cf67739df13a0d82fd23cfa8f85ac0e4dd7afd6f (commit)
  discards  778abe2568a4a77c5fc3fe66fcabbf2b3d930132 (commit)
  discards  bb609395f3073121c3d5cb994546bdecffeb0f0f (commit)
  discards  5781c97b1d9de42c3c0e74b5bc9fa6e0a94e26d6 (commit)
  discards  ec702e89aea391142071c1fa1538512133e77100 (commit)
  discards  98ca1c0068ce4103e2fd4e79b87ccd128d7c1208 (commit)
  discards  ba49283cf7456c0374fa8de0aa67654163b26078 (commit)
  discards  1100db152aac40c16011aff1b1e373b85da4507e (commit)
  discards  bbe35fca615300af0ef75439a5408ed63161c7b4 (commit)
       via  0a7d5538eacadcdc86c107f76943e90344b17381 (commit)
       via  76aec0f4da91c9a4f4ff2ddfd89514221d7bf242 (commit)
       via  ae5dd2adff8a4f3a7eb460c465b34f2a9f3517a7 (commit)
       via  a16b0f16452846758174eb722622dadabc69588d (commit)
       via  bf96f83cd0a2ece6bb606aa999468a85c3c1e699 (commit)
       via  c9a1de6b878291bc87d77624d57ef0dbc3901839 (commit)
       via  ba164288c8437a50d8be98f9ebfb8f96cd280758 (commit)
       via  9ce61273865cdfd5eb4ce5c46835e55237827def (commit)
       via  6da4139236c1bb8c3915756daaa2d7a5a54013fd (commit)
       via  69af5d62bedaf9a20e4946558719b6a6a0f8c794 (commit)
       via  1dab79dce9b48cc2fbfee3dd2d8f1cceee1e9d29 (commit)
       via  408208d8874a0f227d09e299db2346fc3f67b5ca (commit)
       via  5ea1bc77a3947f541d576f95e7ecc7249fc65b9b (commit)
       via  7e7ee5f8c6904a607e7505021c16de4c26dadbe0 (commit)
       via  1bf6610ce7341aaf79899cc1bdce5879a069b2c6 (commit)
       via  ce55361e93529522790fa681ef5837237e9492b1 (commit)
       via  29de346b329fc05750b52446f3516f897415b43b (commit)
       via  a769dcb889325dac6ee200ce891d21bb78861981 (commit)
       via  cf2f158caa47e9d1410453309c7aec58e99ac011 (commit)
       via  d267f4d685bccdf6eaa839044db2721b3c3c37c4 (commit)
       via  0d904e004a763a104e40e707c5a3cde7bb0da3d7 (commit)
       via  01d315f19c0ffdbbbd11d425b067169ce08285e9 (commit)
       via  3d4d79d89090fcbe97de9b10aa9f638461648218 (commit)
       via  d2361d970af8fe5d624ed3977982c21c327ac986 (commit)
       via  f589221ed0a00c12fce0fac629475851b2680b77 (commit)
       via  b3089e437da1bc20de199d7688aa255d6ac82601 (commit)
       via  383d3c33e64a1b64da6d04df1ce7d92d88ef6e34 (commit)
       via  c5903a2b01c93e504fb84c513c012481d98758d9 (commit)
       via  536a10b63ba3cbade1ff3808ae056b11a279aaef (commit)
       via  bc6c43f7595ce379b8b754df1321b852b9a20fee (commit)
       via  f7396eac2f03d612ab27ff279dfefaf3058bf591 (commit)
       via  07dec137deaf5505564fdacec5f3b83ee9399a39 (commit)
       via  70ae5d3000edd12aee38497a6f541595a8c7dee8 (commit)
       via  6d818839a9febc5d8ff970b16822fe86f551f266 (commit)
       via  8d0be259cb0ed8c33a373bbdfe88aafe4cfc27c0 (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 (2cd4981757ffea1d5c7db77cfad9efb40441c522)
            \
             N -- N -- N (0a7d5538eacadcdc86c107f76943e90344b17381)

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/cgit/openbsc/commit/?id=0a7d5538eacadcdc86c107f76943e90344b17381

commit 0a7d5538eacadcdc86c107f76943e90344b17381
Author: Holger Hans Peter Freyther <[email-masked]>
Date:   Wed Nov 28 16:05:12 2012 +0100

    WIP.. debian packaging..

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

commit 76aec0f4da91c9a4f4ff2ddfd89514221d7bf242
Author: Holger Hans Peter Freyther <[email-masked]>
Date:   Wed Nov 28 15:58:34 2012 +0100

    Hack: Allow to set the reject cause to experiment with the blacklist

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

commit ae5dd2adff8a4f3a7eb460c465b34f2a9f3517a7
Author: Holger Hans Peter Freyther <[email-masked]>
Date:   Wed Nov 28 15:47:51 2012 +0100

    WIP.. debian package

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

commit a16b0f16452846758174eb722622dadabc69588d
Author: Holger Hans Peter Freyther <[email-masked]>
Date:   Tue Nov 13 21:54:36 2012 +0100

    nat: Name the variable more properly and begin with net.1.bsc.%d
    
    We can identify the NAT and BSC given the types of the variable,
    no need to put them into the value itself.

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

commit bf96f83cd0a2ece6bb606aa999468a85c3c1e699
Author: Holger Hans Peter Freyther <[email-masked]>
Date:   Mon Nov 12 19:05:16 2012 +0100

    nat: Include the sccp_src_ref and sccp_dst_ref for this call
    
    This can help with some post analysis for failed calls and helps
    finding the connection in the pcap trace.

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

commit c9a1de6b878291bc87d77624d57ef0dbc3901839
Author: Holger Hans Peter Freyther <[email-masked]>
Date:   Mon Nov 12 18:36:00 2012 +0100

    nat: Do not allow the amount of pending responses to grow infinitely
    
    Limit the amount of pending DLCX responses to three times the amount
    of available endpoints. Currently all MGCP messages are sent and handled
    in sequence.

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

commit ba164288c8437a50d8be98f9ebfb8f96cd280758
Author: Holger Hans Peter Freyther <[email-masked]>
Date:   Mon Nov 12 18:00:25 2012 +0100

    nat: Reword the log messages as this is normal operation
    
    The bsc_mgcp_dlcx method is called from the mgcp policy callback
    but also from inside the nat core when the SCCP connection is going
    away.

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

commit 9ce61273865cdfd5eb4ce5c46835e55237827def
Author: Holger Hans Peter Freyther <[email-masked]>
Date:   Wed Oct 24 21:53:40 2012 +0200

    nat: We want the remote to respond to our DLCX request
    
    We want to send a TRAP with the MGCP statistics from the NAT and
    the connected BSC. The BSC endpoint can be either released because
    of a DLCX from the MGCP CallAgent or the SCCP Connection release on
    the A-link.
    
    This is why we need to queue the statistics when the deleting the
    endpoint on the BSC. The processing is continued once the response
    arrives. This code assumes that the response of the DLCX will be sent
    by the remote side. The current amount of outstanding responses can be
    seen on the VTY. This assumption is based on the fact that the BSC has
    already responded to the CRCX and maybe to the MDCX.
    
    The MGCP RFC is bended to prefix the transaction identifier with "nat-"
    to easily detect the response and hand it to the handler. This will
    then parse the response and generate the TRAP. The current version is
    v1. We assume that the transaction space is big enough and we will
    not re-assign the transaction identifier too early.

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

commit 6da4139236c1bb8c3915756daaa2d7a5a54013fd
Author: Holger Hans Peter Freyther <[email-masked]>
Date:   Mon Nov 5 14:54:56 2012 +0100

    nat: Make it possible to send MGCP messages through the IPA multiplex
    
    Instead of handling MGCP through the UDP socket, read and write messages
    through the ipa connection to the MSC.

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

commit 69af5d62bedaf9a20e4946558719b6a6a0f8c794
Author: Holger Hans Peter Freyther <[email-masked]>
Date:   Mon Nov 5 13:52:53 2012 +0100

    nat: Move all methods sending a response to the callagent to a single place
    
    For testing it can be nice to handle MGCP messages through the IPA
    protocol. Prepare the code to send the messages through other means.

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

commit 1dab79dce9b48cc2fbfee3dd2d8f1cceee1e9d29
Author: Holger Hans Peter Freyther <[email-masked]>
Date:   Tue Oct 30 16:32:19 2012 +0100

    nat: Address the FIXME and send the MDCX down to the BSC

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

Summary of changes:
 openbsc/include/openbsc/mgcp.h          |    8 +-
 openbsc/include/openbsc/mgcp_internal.h |    6 +
 openbsc/include/openbsc/osmo_bsc.h      |    3 +
 openbsc/include/openbsc/transaction.h   |   11 +-
 openbsc/src/libmgcp/mgcp_network.c      |    2 +-
 openbsc/src/libmgcp/mgcp_protocol.c     |  400 +++++++++++++++------------
 openbsc/src/libmgcp/mgcp_vty.c          |   36 +++
 openbsc/src/libmsc/gsm_04_08.c          |    1 -
 openbsc/src/libmsc/gsm_04_11.c          |  455 +++++++++++++------------------
 openbsc/src/libmsc/osmo_msc.c           |   14 +-
 openbsc/src/libmsc/transaction.c        |   11 +
 openbsc/src/osmo-bsc/osmo_bsc_bssap.c   |   12 +-
 openbsc/src/osmo-bsc/osmo_bsc_filter.c  |   29 ++-
 openbsc/tests/mgcp/mgcp_test.c          |  140 ++++++++++-
 openbsc/tests/mgcp/mgcp_test.ok         |   16 +
 15 files changed, 673 insertions(+), 471 deletions(-)

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