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/osmux-reliability has been updated discards c9923e4e8a8752fe084fbf2bdb6c0755c11fed2e (commit) discards a63000032940bd32331d0a5529f85ff57ddc7d72 (commit) discards c7a776c496f21d5e044bc030dc61b01ab7b36aa2 (commit) discards 46a518979424913841a3f512eb04838333f64481 (commit) discards d10daee17fd32369a103e11dac1482638df462ec (commit) discards 97bf148af933b8c80bbc3a79e830208b9c172039 (commit) via 864db676cd56213dd59594eae62a576acf55ee62 (commit) via f55bb41c326b3d9582912818d38b7b492d63a4ce (commit) via fb664ad57d853565bca3289f2b83ee8347bb5ef5 (commit) via 9b54b132599ee366a642008a41c63c855b666deb (commit) via ed96fdb774da99313f2ffbc08511451b3f33330e (commit) via ba67df65233121043568c299c5d868c6d63e74a3 (commit) via fded0a7362cbe4507ccb9d4c5e75a3700fca9657 (commit) via 0e62e595a697eb6075349b586ed264bdb9462cd0 (commit) via 06cfe00c711a037981b53946dbaa5b042acb2fbb (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 (c9923e4e8a8752fe084fbf2bdb6c0755c11fed2e) \ N -- N -- N (864db676cd56213dd59594eae62a576acf55ee62)

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=864db676cd56213dd59594eae62a576ac...

commit 864db676cd56213dd59594eae62a576acf55ee62 Author: Holger Hans Peter Freyther holger@moiji-mobile.com Date: Thu Oct 8 16:58:13 2015 +0200

osmux: Make sure that bigger Osmux ids actually fit

We put a signed integer into this string but did not account for the newline and for the terminating NUL of the string. Add the newline to the string and add one for NUL. Spotted while accidently having a CID of 255.

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

commit f55bb41c326b3d9582912818d38b7b492d63a4ce Author: Holger Hans Peter Freyther holger@moiji-mobile.com Date: Sun Oct 4 11:11:11 2015 +0200

osmux: Remember the allocated CID and make sure it is released

There appears to be a leak of CIDs: <000b> mgcp_osmux.c:544 All Osmux circuits are in use!

There are paths that a CID had been requested and never released of the NAT. Remember the allocated CID inside the endpoint so it can always be released. It is using a new variable as the behavior for the NAT and MGCP MGW is different.

The allocated_cid must be signed so that we can assign outside of the 0-255 range of it.

Fixes: OW#1493

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

commit fb664ad57d853565bca3289f2b83ee8347bb5ef5 Author: Holger Hans Peter Freyther holger@moiji-mobile.com Date: Fri Oct 2 18:15:18 2015 +0200

osmux: Enforce Osmux only global and per BSC configuration

Extend the osmux only setting from the MGCP MGW to the NAT. This is applied when an endpoint is allocated and/or when the allocation is confirmed by the remote system.

Not tested. The impact should only be when the new option is being used.

Fixes: OW#1492

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

commit 9b54b132599ee366a642008a41c63c855b666deb Author: Holger Hans Peter Freyther holger@moiji-mobile.com Date: Fri Oct 2 17:38:27 2015 +0200

osmux: Allow to enforce using Osmux for the client

Some systems only want to use Osmux. In case only Osmux should be used fail if it has not be offered/acked.

Client:

Verified On, Off and Only with X-Osmux: 3 and without this field. <000b> mgcp_protocol.c:823 Osmux only and no osmux offered on 0x14 <000b> mgcp_protocol.c:884 Resource error on 0x14

NAT:

Not tested and implemented

Fixes: OW#1492

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

commit ed96fdb774da99313f2ffbc08511451b3f33330e Author: Holger Hans Peter Freyther holger@moiji-mobile.com Date: Fri Oct 2 16:25:21 2015 +0200

osmux: Add introspection for osmux.

* Print number of used CIDs for the system * Hopefully this is just the beginning

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

commit ba67df65233121043568c299c5d868c6d63e74a3 Author: Holger Hans Peter Freyther holger@moiji-mobile.com Date: Fri Oct 2 16:11:15 2015 +0200

osmux: Do not divide the number of bytes by eight.

sizeof(uint8_t) == 1 and there is no need to create an array with 16 bytes and then only use the first two of them. This means the CID range is from 0 to 127 and we should be able to extend this to 256 by changing the array size to 32. Update the testcase now that we can have more than 16 calls with Osmux.

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

commit fded0a7362cbe4507ccb9d4c5e75a3700fca9657 Author: Holger Hans Peter Freyther holger@moiji-mobile.com Date: Fri Oct 2 15:56:35 2015 +0200

osmux: Test cid allocation and de-allocation

* Test that one can get an id * That they are assigned predicatble right now * That returning them will make the number of used ones go down * That allocating more will fail

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

Summary of changes: openbsc/doc/osmocom-authn-protocol.txt | 250 ++++++++++++++++++++++++++++++ openbsc/include/openbsc/mgcp_internal.h | 2 +- openbsc/src/gprs/gprs_gsup_client.c | 12 +- openbsc/src/osmo-bsc_nat/bsc_mgcp_utils.c | 6 +- 4 files changed, 263 insertions(+), 7 deletions(-) create mode 100644 openbsc/doc/osmocom-authn-protocol.txt

hooks/post-receive