April 2016 - osmocom-commitlog

libosmo-abis.git branch max/tmp created. 0.3.2-5-g1698a81
by gitosis＠osmocom.org 28 Apr '16

28 Apr '16

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 A-bis protcol interface library". The branch, max/tmp has been created at 1698a819d16167a84eff701edb8355865a1bc1e3 (commit) - Log ----------------------------------------------------------------- http://cgit.osmocom.org/libosmo-abis/commit/?id=1698a819d16167a84eff701edb8… commit 1698a819d16167a84eff701edb8355865a1bc1e3 Author: Max <msuraev(a)sysmocom.de> Date: Thu Apr 28 14:08:02 2016 +0200 Do not send RTP to port 0 Previously it was possible to send RTP data to port 0. This is not only producing multiple errors but also breaks RTP transmission with newer (>= 0.25) oRTP leading to calls with no audio. To address this OSMO_RTP_F_DISABLED flag was introduced. It's set by default for all new RTP sessions. It can be manually unset after the call to osmo_rtp_socket_create(). When the flag is set it prevents transmission and reception of RTP frames for the session. The flag is unset automatically in osmo_rtp_socket_connect() when session is bound to non-zero remote port. Fixes: OS#1661, OS#1662 ----------------------------------------------------------------------- hooks/post-receive -- Osmocom A-bis protcol interface library

1 0

libosmo-abis.git branch max/ortp updated. 0.3.2-14-gc87cab8
by gitosis＠osmocom.org 28 Apr '16

28 Apr '16

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 A-bis protcol interface library". The branch, max/ortp has been updated discards 2b18f0850c0b6e40916ae8eb1609478183c4a0ac (commit) discards 4200f66e9ec3acfca4d7c60a8e88b2720e494476 (commit) discards 1a01b217536985f79f71e69e2a2f6d0b38e45270 (commit) discards 801ad99fc9cd7c7df73aa9b2d55b0e6ccf8a5239 (commit) via c87cab8a9e1d8f195f5049d8cd017803ec5d7b77 (commit) via 729f597887bd74318650414ef48d6f405d3de12f (commit) via c80c15d4cfa4458040d22545dbe4623c13429999 (commit) via c08c53206226ae2e6e4b385354715a714709623c (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 (2b18f0850c0b6e40916ae8eb1609478183c4a0ac) \ N -- N -- N (c87cab8a9e1d8f195f5049d8cd017803ec5d7b77) 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/libosmo-abis/commit/?id=c87cab8a9e1d8f195f5049d8cd0… commit c87cab8a9e1d8f195f5049d8cd017803ec5d7b77 Author: Max <msuraev(a)sysmocom.de> Date: Wed Apr 27 18:35:05 2016 +0200 Do not send RTP to port 0 Previously it was possible to send RTP data to port 0. This is not only producing multiple errors but also breaks RTP transmission with newer (>= 0.25) oRTP leading to calls with no audio. To address this OSMO_RTP_F_DISABLED flag was introduced. It's set by default for all new RTP sessions. It can be manually unset after the call to osmo_rtp_socket_create(). When the flag is set it prevents transmission and reception of RTP frames for the session. The flag is unset automatically in osmo_rtp_socket_connect() when session is bound to non-zero remote port. Fixes: OS#1661, OS#1662 http://cgit.osmocom.org/libosmo-abis/commit/?id=729f597887bd74318650414ef48… commit 729f597887bd74318650414ef48d6f405d3de12f Author: Max <msuraev(a)sysmocom.de> Date: Wed Apr 27 18:53:06 2016 +0200 Only update TX timestamp for successful RTP send http://cgit.osmocom.org/libosmo-abis/commit/?id=c80c15d4cfa4458040d22545dbe… commit c80c15d4cfa4458040d22545dbe4623c13429999 Author: Max <msuraev(a)sysmocom.de> Date: Wed Apr 27 18:45:43 2016 +0200 Set connected mode after address ortp: according to oRTP documentation rtp_session_set_connected_mode() uses the address set by rtp_session_set_remote_addr() - move the function call accordingly. http://cgit.osmocom.org/libosmo-abis/commit/?id=c08c53206226ae2e6e4b3853547… commit c08c53206226ae2e6e4b385354715a714709623c Author: Max <msuraev(a)sysmocom.de> Date: Wed Apr 27 18:43:03 2016 +0200 Expand network error callback ortp: use extra parameter for network_error callback in log message as it's described in oRTP documentation (error string). ----------------------------------------------------------------------- Summary of changes: src/trau/osmo_ortp.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- Osmocom A-bis protcol interface library

1 0

osmo-iuh.git branch sysmocom/ipa_nano3G updated. ecb259dbb9bdd5196a89dc3205602bba2ae3de06
by gitosis＠osmocom.org 28 Apr '16

28 Apr '16

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=ecb259dbb9bdd5196a89dc3205602bb… commit ecb259dbb9bdd5196a89dc3205602bba2ae3de06 Author: Neels Hofmeyr <nhofmeyr(a)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=87b3bbfb39aa84239d76796353a3acb… commit 87b3bbfb39aa84239d76796353a3acb1d6aec889 Author: Neels Hofmeyr <nhofmeyr(a)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=e874a5db5aabd717eba5a8dc02b19ce… commit e874a5db5aabd717eba5a8dc02b19cef48cb88ec Author: Neels Hofmeyr <nhofmeyr(a)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=30dc1920bbcbf80146892808a38cfdb… commit 30dc1920bbcbf80146892808a38cfdbffeeafc6a Author: Neels Hofmeyr <nhofmeyr(a)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=4bd1c9f605103b6ff3393ec9185bd47… commit 4bd1c9f605103b6ff3393ec9185bd47501eea6a3 Author: Neels Hofmeyr <nhofmeyr(a)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=81fb7cb24bf5c66d9d196455ad22801… commit 81fb7cb24bf5c66d9d196455ad22801f25e05e61 Author: Neels Hofmeyr <nhofmeyr(a)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 -- Osmocom code for Iuh interface

1 0

libosmo-abis.git branch max/ortp updated. 0.3.2-14-g2b18f08
by gitosis＠osmocom.org 28 Apr '16

28 Apr '16

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 A-bis protcol interface library". The branch, max/ortp has been updated discards 1569cba59f00745c38405f330215781b1f3fc5ba (commit) discards 337e39d5a2f3a9fdc22ec494e3f822c2c0166577 (commit) discards 0d6db6fa4d44551eab31919026160222428e6794 (commit) discards 9966f5246870bef69aea57eef8ea3dff59d37e45 (commit) discards b811e514af1fc1126fa6a6019806defb74a69813 (commit) discards 968f3f877bc9aa5a6fc0588ac8027bda219acde5 (commit) discards 4e3d451c4a301a7fc8c84813dd8c238f4728998b (commit) discards 86c9e4597c1c4a9be160bd44b8a8dc7d13c0b59c (commit) discards f75ec350bd3358e13cb56fd4e9cac22f9075465b (commit) via 2b18f0850c0b6e40916ae8eb1609478183c4a0ac (commit) via 4200f66e9ec3acfca4d7c60a8e88b2720e494476 (commit) via 1a01b217536985f79f71e69e2a2f6d0b38e45270 (commit) via 801ad99fc9cd7c7df73aa9b2d55b0e6ccf8a5239 (commit) via 0fdb1b58d03c3101bd785722b32299f771bab71a (commit) via a371456eeea60bf121e664bf9aed6f978dfbc7a6 (commit) via 694d49d50bfffb8ab0c89dd975d7b4585e50a37e (commit) via 1373f20b0052dd75cfbd3bfb617a17594fde8eca (commit) via bda06d2a0e81247beb063fad27a6cd3b2d2eb524 (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 (1569cba59f00745c38405f330215781b1f3fc5ba) \ N -- N -- N (2b18f0850c0b6e40916ae8eb1609478183c4a0ac) 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/libosmo-abis/commit/?id=2b18f0850c0b6e40916ae8eb160… commit 2b18f0850c0b6e40916ae8eb1609478183c4a0ac Author: Max <msuraev(a)sysmocom.de> Date: Wed Apr 27 18:53:06 2016 +0200 Only update TX timestamp for successful RTP send http://cgit.osmocom.org/libosmo-abis/commit/?id=4200f66e9ec3acfca4d7c60a8e8… commit 4200f66e9ec3acfca4d7c60a8e88b2720e494476 Author: Max <msuraev(a)sysmocom.de> Date: Wed Apr 27 18:35:05 2016 +0200 Do not send RTP to port 0 Previously it was possible to send RTP data to port 0. To address this introduce OSMO_RTP_F_DISABLED flag and use it by default. When set this flag prevents transmission and reception of RTP frames for the session. The flag is unset when session is bound to non-zero remote port. http://cgit.osmocom.org/libosmo-abis/commit/?id=1a01b217536985f79f71e69e2a2… commit 1a01b217536985f79f71e69e2a2f6d0b38e45270 Author: Max <msuraev(a)sysmocom.de> Date: Wed Apr 27 18:45:43 2016 +0200 Set connected mode after address ortp: according to oRTP documentation rtp_session_set_connected_mode() uses the address set by rtp_session_set_remote_addr() - move the function call accordingly. http://cgit.osmocom.org/libosmo-abis/commit/?id=801ad99fc9cd7c7df73aa9b2d55… commit 801ad99fc9cd7c7df73aa9b2d55b0e6ccf8a5239 Author: Max <msuraev(a)sysmocom.de> Date: Wed Apr 27 18:43:03 2016 +0200 Expand network error callback ortp: add extra parameters for network_error callback described in oRTP documentation and use them for log message. http://cgit.osmocom.org/libosmo-abis/commit/?id=0fdb1b58d03c3101bd785722b32… commit 0fdb1b58d03c3101bd785722b32299f771bab71a Author: Max <msuraev(a)sysmocom.de> Date: Wed Apr 27 12:17:11 2016 +0200 Fix log message ortp: use log message which properly describe funcion name and its parameters to simplify troubleshooting. http://cgit.osmocom.org/libosmo-abis/commit/?id=a371456eeea60bf121e664bf9ae… commit a371456eeea60bf121e664bf9aed6f978dfbc7a6 Author: Max <msuraev(a)sysmocom.de> Date: Tue Apr 26 15:25:21 2016 +0200 simplify frame send routine ortp: use higher-level function for sending RTP frames. http://cgit.osmocom.org/libosmo-abis/commit/?id=694d49d50bfffb8ab0c89dd975d… commit 694d49d50bfffb8ab0c89dd975d7b4585e50a37e Author: Max <msuraev(a)sysmocom.de> Date: Tue Apr 26 14:26:59 2016 +0200 Remove use of private oRTP function ortp: the rtp_session_rtcp_recv() function is not part of public oRTP API so we shouldn't use it. Besides it is called internally by oRTP in rtp_session_recvm_with_ts() which we call anyway. http://cgit.osmocom.org/libosmo-abis/commit/?id=1373f20b0052dd75cfbd3bfb617… commit 1373f20b0052dd75cfbd3bfb617a17594fde8eca Author: Max <msuraev(a)sysmocom.de> Date: Tue Apr 26 14:04:04 2016 +0200 Support newer oRTP API ortp: rtp_session_signal_connect() API has changed in 0.24 - add version check and change code accordingly. See http://upstream.rosalinux.ru/diffs/ortp/0.23.0_to_0.24.0/diff.html for details. http://cgit.osmocom.org/libosmo-abis/commit/?id=bda06d2a0e81247beb063fad27a… commit bda06d2a0e81247beb063fad27a6cd3b2d2eb524 Author: Max <msuraev(a)sysmocom.de> Date: Thu Apr 28 12:05:27 2016 +0200 Bump minimum oRTP version We use ortp_set_memory_functions() method which was added in 0.14.3. ----------------------------------------------------------------------- Summary of changes: configure.ac | 2 +- src/trau/osmo_ortp.c | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-) hooks/post-receive -- Osmocom A-bis protcol interface library

1 0

osmo-iuh.git branch master updated. 02601c878585732ec75e33d02a45e5ab1147d4a1
by gitosis＠osmocom.org 27 Apr '16

27 Apr '16

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, master has been updated via 02601c878585732ec75e33d02a45e5ab1147d4a1 (commit) from 64f5639eae65e9f0d16e330315aceea7058de715 (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/osmo-iuh/commit/?id=02601c878585732ec75e33d02a45e5a… commit 02601c878585732ec75e33d02a45e5ab1147d4a1 Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com> Date: Wed Apr 27 22:36:20 2016 +0200 contrib: Put asn1c into the PATH as well ----------------------------------------------------------------------- Summary of changes: contrib/jenkins.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- Osmocom code for Iuh interface

1 0

osmo-iuh.git branch master updated. 64f5639eae65e9f0d16e330315aceea7058de715
by gitosis＠osmocom.org 27 Apr '16

27 Apr '16

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, master has been updated via 64f5639eae65e9f0d16e330315aceea7058de715 (commit) from b248c8c8ca60aefe0b670efcb7da1dc733985742 (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/osmo-iuh/commit/?id=64f5639eae65e9f0d16e330315aceea… commit 64f5639eae65e9f0d16e330315aceea7058de715 Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com> Date: Wed Apr 27 22:06:46 2016 +0200 contrib: Add build script used on the jenkins to build it This tests compilation, runs the tests, regenerates the ASN1 code, compiles it and tests it as well. The make distcheck target is not working right now. ----------------------------------------------------------------------- Summary of changes: contrib/jenkins.sh | 64 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 64 insertions(+) create mode 100755 contrib/jenkins.sh hooks/post-receive -- Osmocom code for Iuh interface

1 0

libosmocore.git branch master updated. 0.9.0-137-gaa16d63
by gitosis＠osmocom.org 27 Apr '16

27 Apr '16

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 "An utility library for Open Source Mobile Communications". The branch, master has been updated via aa16d63c273204dc69108f7361d38b751bfb69e4 (commit) from 7d004a1d69acc09707860334ccdfcf71604206be (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/libosmocore/commit/?id=aa16d63c273204dc69108f7361d3… commit aa16d63c273204dc69108f7361d38b751bfb69e4 Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com> Date: Sat Apr 23 17:55:39 2016 +0200 milenage/aes: Address undefined behavior on bitshift Extend the u8 to u32 before going to shift it. Fixes: milenage/aes-internal.c:799:4: runtime error: left shift of 128 by 24 places cannot be represented in type 'int' #0 0x7f84e9fe86a2 in rijndaelKeySetupEnc (/home/builder/jenkins/workspace/Osmocom_Sanitizer/source/libosmocore/src/gsm/.libs/libosmogsm.so.5+0xfa6a2) #1 0x7f84e9febad8 in aes_encrypt_init (/home/builder/jenkins/workspace/Osmocom_Sanitizer/source/libosmocore/src/gsm/.libs/libosmogsm.so.5+0xfdad8) #2 0x7f84e9fe7d14 in aes_128_encrypt_block (/home/builder/jenkins/workspace/Osmocom_Sanitizer/source/libosmocore/src/gsm/.libs/libosmogsm.so.5+0xf9d14) #3 0x7f84e9febe7d in milenage_f1 (/home/builder/jenkins/workspace/Osmocom_Sanitizer/source/libosmocore/src/gsm/.libs/libosmogsm.so.5+0xfde7d) #4 0x7f84e9fee2ce in milenage_generate (/home/builder/jenkins/workspace/Osmocom_Sanitizer/source/libosmocore/src/gsm/.libs/libosmogsm.so.5+0x1002ce) #5 0x7f84e9fe76d7 in milenage_gen_vec (/home/builder/jenkins/workspace/Osmocom_Sanitizer/source/libosmocore/src/gsm/.libs/libosmogsm.so.5+0xf96d7) #6 0x7f84e9fe6c08 in osmo_auth_gen_vec (/home/builder/jenkins/workspace/Osmocom_Sanitizer/source/libosmocore/src/gsm/.libs/libosmogsm.so.5+0xf8c08) #7 0x401441 in main (/home/builder/jenkins/workspace/Osmocom_Sanitizer/source/libosmocore/tests/auth/.libs/lt-milenage_test+0x401441) #8 0x7f84e8e33a3f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x20a3f) #9 0x400e58 in _start (/home/builder/jenkins/workspace/Osmocom_Sanitizer/source/libosmocore/tests/auth/.libs/lt-milenage_test+0x400e58) ----------------------------------------------------------------------- Summary of changes: src/gsm/milenage/aes_i.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- An utility library for Open Source Mobile Communications

1 0

libosmo-abis.git branch max/ortp updated. 0.3.2-14-g1569cba
by gitosis＠osmocom.org 27 Apr '16

27 Apr '16

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 A-bis protcol interface library". The branch, max/ortp has been updated discards d7063c98853e4a412d0a8fd44dc2c4dc7a22ad25 (commit) via 1569cba59f00745c38405f330215781b1f3fc5ba (commit) via 337e39d5a2f3a9fdc22ec494e3f822c2c0166577 (commit) via 0d6db6fa4d44551eab31919026160222428e6794 (commit) via 9966f5246870bef69aea57eef8ea3dff59d37e45 (commit) via b811e514af1fc1126fa6a6019806defb74a69813 (commit) via 968f3f877bc9aa5a6fc0588ac8027bda219acde5 (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 (d7063c98853e4a412d0a8fd44dc2c4dc7a22ad25) \ N -- N -- N (1569cba59f00745c38405f330215781b1f3fc5ba) 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/libosmo-abis/commit/?id=1569cba59f00745c38405f33021… commit 1569cba59f00745c38405f330215781b1f3fc5ba Author: Max <msuraev(a)sysmocom.de> Date: Tue Apr 26 17:22:22 2016 +0200 Set non-blocking mode explicitly ortp: do not rely on library default - set non-blocking mode explicitly. http://cgit.osmocom.org/libosmo-abis/commit/?id=337e39d5a2f3a9fdc22ec494e3f… commit 337e39d5a2f3a9fdc22ec494e3f822c2c0166577 Author: Max <msuraev(a)sysmocom.de> Date: Wed Apr 27 18:53:06 2016 +0200 Only update TX timestamp for successful RTP send http://cgit.osmocom.org/libosmo-abis/commit/?id=0d6db6fa4d44551eab319190261… commit 0d6db6fa4d44551eab31919026160222428e6794 Author: Max <msuraev(a)sysmocom.de> Date: Wed Apr 27 18:35:05 2016 +0200 Do not send RTP to port 0 Previously it was possible to send RTP data to port 0. To address this introduce OSMO_RTP_F_DISABLED flag and use it by default. When set this flag prevents transmission and reception of RTP frames for the session. The flag is unset when session is bound to non-zero remote port. http://cgit.osmocom.org/libosmo-abis/commit/?id=9966f5246870bef69aea57eef8e… commit 9966f5246870bef69aea57eef8ea3dff59d37e45 Author: Max <msuraev(a)sysmocom.de> Date: Wed Apr 27 18:45:43 2016 +0200 Set connected mode after address ortp: according to oRTP documentation rtp_session_set_connected_mode() uses the address set by rtp_session_set_remote_addr() - move the function call accordingly. http://cgit.osmocom.org/libosmo-abis/commit/?id=b811e514af1fc1126fa6a601980… commit b811e514af1fc1126fa6a6019806defb74a69813 Author: Max <msuraev(a)sysmocom.de> Date: Wed Apr 27 18:43:03 2016 +0200 Expand network error callback ortp: add extra parameters for network_error callback described in oRTP documentation and use them for log message. http://cgit.osmocom.org/libosmo-abis/commit/?id=968f3f877bc9aa5a6fc0588ac80… commit 968f3f877bc9aa5a6fc0588ac8027bda219acde5 Author: Max <msuraev(a)sysmocom.de> Date: Wed Apr 27 12:17:11 2016 +0200 Fix log message ortp: use log message which properly describe funcion name and its parameters to simplify troubleshooting. ----------------------------------------------------------------------- Summary of changes: include/osmocom/trau/osmo_ortp.h | 1 + src/trau/osmo_ortp.c | 26 +++++++++++++++++++------- 2 files changed, 20 insertions(+), 7 deletions(-) hooks/post-receive -- Osmocom A-bis protcol interface library

1 0

openbsc.git branch neels/cscn updated. 0.15.0-418-g7d8d866
by gitosis＠osmocom.org 27 Apr '16

27 Apr '16

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, neels/cscn has been updated discards babe676570fc755c9d712d8eb175ec526335b7b8 (commit) discards d8d9d8fee9d594743f2cf33c7f5aa155888233d6 (commit) via 7d8d86644746dafed2263ede8e75cc7d43b3a6f3 (commit) via e87078e4469ca12483645022c06e8c7d4af7e1ff (commit) via 84d0e05d89115c189791284676a492c5f9b97d30 (commit) via 318eaf3aea3367b88bee5a5084c3352b4748a065 (commit) via b2c66d12bab45df939133fc65eae30c3a7759340 (commit) via 3494f218422a326cee7b188350fbee61b388bbd3 (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 (babe676570fc755c9d712d8eb175ec526335b7b8) \ N -- N -- N (7d8d86644746dafed2263ede8e75cc7d43b3a6f3) 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=7d8d86644746dafed2263ede8e75cc7d… commit 7d8d86644746dafed2263ede8e75cc7d43b3a6f3 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Apr 27 14:29:30 2016 +0200 wip: paging and mscsplit http://cgit.osmocom.org/openbsc/commit/?id=e87078e4469ca12483645022c06e8c7d… commit e87078e4469ca12483645022c06e8c7d4af7e1ff Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Apr 27 13:01:53 2016 +0200 msc: paging resp: carry on even though subscr was not paging If the subscriber's paging flag was not set when a paging response is received, it can't hurt to anyway carry out paging responses if there are any. Reduce the handling to a log message, don't abort. http://cgit.osmocom.org/openbsc/commit/?id=84d0e05d89115c189791284676a492c5… commit 84d0e05d89115c189791284676a492c5f9b97d30 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Apr 27 12:57:42 2016 +0200 msc: tweak logging for paging Use the DPAG logging category and tweak some log output http://cgit.osmocom.org/openbsc/commit/?id=318eaf3aea3367b88bee5a5084c3352b… commit 318eaf3aea3367b88bee5a5084c3352b4748a065 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Apr 27 12:55:25 2016 +0200 msc: paging response: properly evaluate auth event In paging_resp_action(), don't carry on when auth reports a failure. In handle_paging_resp(), pass a meaningful auth event to paging_resp_action() in case no auth needs to be established. http://cgit.osmocom.org/openbsc/commit/?id=b2c66d12bab45df939133fc65eae30c3… commit b2c66d12bab45df939133fc65eae30c3a7759340 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Apr 27 02:47:54 2016 +0200 msc: paging response: use key seq from incoming msg http://cgit.osmocom.org/openbsc/commit/?id=3494f218422a326cee7b188350fbee61… commit 3494f218422a326cee7b188350fbee61b388bbd3 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Apr 27 02:08:07 2016 +0200 msc: paging: add Integrity Protection for IuCS Do the paging response actions from new function paging_resp_action(), plugged as cb function to gsm48_secure_channel() in case Integrity Protection needs to be established first (IU), or called directly otherwise. BTW, we can't reuse gsm0408_authorize() as-is, it is tied closely to a Location Updating Request. Just copy its two lines of guts, calling static authorize_subscriber() and gsm48_secure_channel() directly. ----------------------------------------------------------------------- Summary of changes: openbsc/include/openbsc/gsm_subscriber.h | 8 ++- openbsc/src/libmsc/gsm_04_08.c | 77 +++++++++++++++------------- openbsc/src/libmsc/gsm_04_11.c | 3 +- openbsc/src/libmsc/gsm_subscriber.c | 88 ++++++++++++++++++-------------- 4 files changed, 99 insertions(+), 77 deletions(-) hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

1 0

osmo-trx.git branch options deleted. 9a41f67cf3ca7db41af57fe5568302f47ab56dd5
by gitosis＠osmocom.org 27 Apr '16

27 Apr '16

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 "OpenBTS' transceiver retro-fit". The branch, options has been deleted was 9a41f67cf3ca7db41af57fe5568302f47ab56dd5 ----------------------------------------------------------------------- 9a41f67cf3ca7db41af57fe5568302f47ab56dd5 uhd: Allow device specific default amplitude settings ----------------------------------------------------------------------- hooks/post-receive -- OpenBTS' transceiver retro-fit

1 0