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 "Osmocom code for Iuh interface".

The branch, sysmocom/ipa_nano3G has been updated discards 30188bb5a81e2ba5e02e9c0a522d5848d2212550 (commit) discards 6bdba59239e4353da96bcae05ce2f8f9a6a3b680 (commit) discards dd072a90d77eafd2252d31834ad1cc18afed031d (commit) discards fd7ce5f9b48839013617aef8c7f410ced2672754 (commit) discards cbb8db325c2bdfbd5495d4b8d0edbbbfb360d3d1 (commit) discards 5b6fb9c301f4906f2fceac33bb74485d298711e3 (commit) via ecb259dbb9bdd5196a89dc3205602bba2ae3de06 (commit) via 87b3bbfb39aa84239d76796353a3acb1d6aec889 (commit) via e874a5db5aabd717eba5a8dc02b19cef48cb88ec (commit) via 30dc1920bbcbf80146892808a38cfdbffeeafc6a (commit) via 4bd1c9f605103b6ff3393ec9185bd47501eea6a3 (commit) via 81fb7cb24bf5c66d9d196455ad22801f25e05e61 (commit) via 02601c878585732ec75e33d02a45e5ab1147d4a1 (commit) via 64f5639eae65e9f0d16e330315aceea7058de715 (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 (30188bb5a81e2ba5e02e9c0a522d5848d2212550) \ N -- N -- N (ecb259dbb9bdd5196a89dc3205602bba2ae3de06)

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/osmo-iuh/commit/?id=ecb259dbb9bdd5196a89dc3205602bba...

commit ecb259dbb9bdd5196a89dc3205602bba2ae3de06 Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Sat Apr 23 13:53:28 2016 +0200

hnbgw: dumb fix of context map hnb_list double delete

http://cgit.osmocom.org/osmo-iuh/commit/?id=87b3bbfb39aa84239d76796353a3acb1...

commit 87b3bbfb39aa84239d76796353a3acb1d6aec889 Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Mon Apr 25 15:05:32 2016 +0200

hack: simply accept UE Register Requests with TMSI

HNBGW would usually keep track of UEs that have registered, with their IMSI. When a UE registers with only a TMSI, we obviously can't store an IMSI. However, since we're so far never *using* the list of UEs in osmo-hnbgw, we might as well just accept the TMSI registration and carry on as usual.

This is particularly helpful with an ip.access nano3G femto cell, as it tends to send UE registrations with a TMSI+LAI identification instead of an IMSI when the subscriber is known. This causes timeouts of several minutes until a UE registration switches back to IMSI. When simply accepting the TMSI in osmo-hngw, no problems are apparent in our current code state.

We could use the subscriber list during paging, but on the other hand, it doesn't hurt to anyway always page to all HNBs connected to osmo-hnbgw. The paging procedure does include a page-to-all-HNBs in case the first HNB paging fails. However, since we're now failing to record UEs that register by TMSI, we must be aware that trying to page such UE on only its last seen HNB will fail; it is plainly missing in the list.

http://cgit.osmocom.org/osmo-iuh/commit/?id=e874a5db5aabd717eba5a8dc02b19cef...

commit e874a5db5aabd717eba5a8dc02b19cef48cb88ec Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Mon Apr 25 14:55:35 2016 +0200

UE Register with TMSI: reply with a Register Reject

When receiving a UE Register Request with TMSI and no IMSI, compose a Register Reject with the same UE Identity and send.

The accepting function expects a ue_context argument and composes the message from the IMSI found there. This new rejection message cannot rely on a ue_context struct and hence uses the asn1 uE_Identity directly.

http://cgit.osmocom.org/osmo-iuh/commit/?id=30dc1920bbcbf80146892808a38cfdbf...

commit 30dc1920bbcbf80146892808a38cfdbffeeafc6a Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Mon Apr 25 15:21:09 2016 +0200

RAB parameters: add Extended Max Bitrate

Adjust test expectation in test-ranap.c.

This IE is seen in a "real life" pcap of hNodeB operation. We did not need it so far, but add it to test the ip.access nano3G.

Comment from the future: the ip.access nano3G rebooted upon RAB Assignment Request, and after adding/tweaking some IEs it stopped rebooting. This is one of the changes that fixed the reboot issue. The changes have been tested incrementally until reboots vanished, but it's not clear/hasn't been tested whether omitting this change alone will cause reboots to re-appear.

http://cgit.osmocom.org/osmo-iuh/commit/?id=4bd1c9f605103b6ff3393ec9185bd475...

commit 4bd1c9f605103b6ff3393ec9185bd47501eea6a3 Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Mon Apr 25 15:17:25 2016 +0200

RAB parameters: tweak the Allocation Or Retention Priority

Adjust test expectation in test-ranap.c.

These values are seen in a "real life" pcap from hNodeB operation.

Comment from the future: the ip.access nano3G rebooted upon RAB Assignment Request, and after adding/tweaking some IEs it stopped rebooting. This is one of the changes that fixed the reboot issue. The changes have been tested incrementally until reboots vanished, but it's not clear/hasn't been tested whether omitting this change alone will cause reboots to re-appear.

http://cgit.osmocom.org/osmo-iuh/commit/?id=81fb7cb24bf5c66d9d196455ad22801f...

commit 81fb7cb24bf5c66d9d196455ad22801f25e05e61 Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Mon Apr 25 15:14:08 2016 +0200

RAB parameters: add Traffic Handling Priority

Add this 'missing' IE from the RAB Assignment Request (while hacking on the ip.access nano3G).

Adjust test expectation in test-ranap.c.

Comment from the future: the ip.access nano3G rebooted upon RAB Assignment Request, and after adding/tweaking some IEs it stopped rebooting. This is one of the changes that fixed the reboot issue. The changes have been tested incrementally until reboots vanished, but it's not clear/hasn't been tested whether omitting this change alone will cause reboots to re-appear.

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

Summary of changes: contrib/jenkins.sh | 64 +++++++++++++++++++++++++++++++++++++++++++++++++ src/tests/test-ranap.ok | 16 ++++++------- 2 files changed, 72 insertions(+), 8 deletions(-) create mode 100755 contrib/jenkins.sh

hooks/post-receive