osmocom-commitlog September 2016

osmocom-commitlog@lists.osmocom.org

1 participants
225 discussions

osmo-iuh.git branch sysmocom/ipa_nano3G updated. 3eb4ad86835b8e16c6d12becc390ec89298174fd

by gitosis＠osmocom.org

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 75bfa56be9aa9fe98e88278e3a58ade29c2d69f0 (commit) discards 6ffacf5ea61308243cf2b0bb0b74e2f0923d19c0 (commit) discards 8380eb2a01e6b5eb375adf1e570fa7293226fd47 (commit) via 3eb4ad86835b8e16c6d12becc390ec89298174fd (commit) via 6ec179e7647958b0ab4431b055c3e68136cf8d15 (commit) via dfd3e11be57852d334107a0f08cd3d6ba4229c77 (commit) via 065b584f9b771a0a0a8df6cfef77dea932f00a48 (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 (75bfa56be9aa9fe98e88278e3a58ade29c2d69f0) \ N -- N -- N (3eb4ad86835b8e16c6d12becc390ec89298174fd) 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=3eb4ad86835b8e16c6d12becc390ec8… commit 3eb4ad86835b8e16c6d12becc390ec89298174fd Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Thu Sep 8 15:39:18 2016 +0200 RAB Assign for voice: heed the x213 nsap flag Add use_x213_nsap arg to ranap_new_msg_rab_assign_voice() and new_transp_info_rtp(). Pass this to new_transp_layer_addr() to compose 32bit addresses when use_x213_nsap == false. This is analogous to ranap_new_msg_rab_assign_data(). Particularly, the ip.access nano3G does not accept x213 NSAP 56bit addresses, so we want to send 32bit addresses there. Change-Id: I0c3c95d709c8a2b1c48d7a187faca34102226329 http://cgit.osmocom.org/osmo-iuh/commit/?id=6ec179e7647958b0ab4431b055c3e68… commit 6ec179e7647958b0ab4431b055c3e68136cf8d15 Author: Harald Welte <laforge(a)gnumonks.org> Date: Sat Apr 30 23:52:02 2016 +0200 hack: Accept also UE_Identity_PR_pTMSIRAI in HNBAP from nano3G I have the feeling that the nano3G simply forwards whatever identity it receives from the MS in RRC via HNBAP, without sending any IDENTITY REQUESTS by itself. That seems like a violation of the RANAP specification, but well. As opposed to Neels' earlier commit, the phone I was testing with (GT-I9100) is using the UE_Identity_PR_pTMSIRAI (PS identity) instead of UE_Identity_PR_tMSILAI (CS identity) when trying its first attempt to register to the network, so let's support that equally. http://cgit.osmocom.org/osmo-iuh/commit/?id=dfd3e11be57852d334107a0f08cd3d6… commit dfd3e11be57852d334107a0f08cd3d6ba4229c77 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. A workaround to make sure the phone uses an IMSI to register: attempt to register the phone to a different mobile network, which may discard the TMSI for your network, and then switch back to your network. Recording the IMSI in hnbgw: 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. Change-Id: I87bc1aa3e85815ded7ac1dbdca48f1680b468589 http://cgit.osmocom.org/osmo-iuh/commit/?id=065b584f9b771a0a0a8df6cfef77dea… commit 065b584f9b771a0a0a8df6cfef77dea932f00a48 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. Change-Id: Ia47e398e50e316842cd260dc0d9a4e2d8a1c627c ----------------------------------------------------------------------- Summary of changes: include/osmocom/ranap/ranap_msg_factory.h | 4 +++- src/hnbgw_hnbap.c | 3 ++- src/ranap_msg_factory.c | 12 ++++++++---- src/tests/test-ranap.c | 2 +- 4 files changed, 14 insertions(+), 7 deletions(-) hooks/post-receive -- Osmocom code for Iuh interface

8 years, 9 months

osmo-pcu.git branch nrw/litecell15-merge-and-rebase updated. 0.2-838-g379649c

by gitosis＠osmocom.org

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 "UNNAMED PROJECT". The branch, nrw/litecell15-merge-and-rebase has been updated via 379649cfcdd8ff449cd97be895431ea45ed32383 (commit) via bfc6cec8a52df879d1196f115397f6762ccbdf3b (commit) via 64d1cc25d0c885deec2b914eb6d89bc7798e7bc1 (commit) via 7b883fffdcb0ade02717a22f7d6b9b1862134747 (commit) via 1c80421ddc9a6c0c27e1d826cae24b291401d710 (commit) via 66a1786fcd9d252e8af975b35ad2f9fca91fec5a (commit) via 17c1f04e855188c8329686283fd353d490549179 (commit) via e7813197080896f89d0f7dee9fc1d050f085b92c (commit) from d5415a22f15addf8937a12f37d4c212ec07561e9 (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-pcu/commit/?id=379649cfcdd8ff449cd97be895431ea… commit 379649cfcdd8ff449cd97be895431ea45ed32383 Author: Minh-Quang Nguyen <minh-quang.nguyen(a)nutaq.com> Date: Wed Sep 7 14:17:49 2016 -0400 Implementation of NSVC failure related alarms: - Too many NS-ALIVE timer expired - Unable to perform unblocking procedure - Unable to perform reset prodecure Alarms ID are manufacture-defined by NuRAN Wireless Change-Id: Ida791c30a50c929975c2610c312fd844f9c7ccb5 http://cgit.osmocom.org/osmo-pcu/commit/?id=bfc6cec8a52df879d1196f115397f67… commit bfc6cec8a52df879d1196f115397f6762ccbdf3b Author: Minh-Quang Nguyen <minh-quang.nguyen(a)nutaq.com> Date: Wed Sep 7 10:31:20 2016 -0400 LC15: Implementation of PDTCH queue is full alarm. The alarm cause ID is manufacture-defined by NuRAN Wireless. Change-Id: I9ea5146f9940177e08c9f0b3087b0ab4b0c170d9 http://cgit.osmocom.org/osmo-pcu/commit/?id=64d1cc25d0c885deec2b914eb6d89bc… commit 64d1cc25d0c885deec2b914eb6d89bc7798e7bc1 Author: Minh-Quang Nguyen <minh-quang.nguyen(a)nutaq.com> Date: Wed Sep 7 10:21:54 2016 -0400 LC15: Implementation of receiving unknown BTS message alarm. The alarm cause ID is manufacture-defined by NuRAN Wireless. Change-Id: I0c86d987d9e36779ac5ffba184038b906effbc16 http://cgit.osmocom.org/osmo-pcu/commit/?id=7b883fffdcb0ade02717a22f7d6b9b1… commit 7b883fffdcb0ade02717a22f7d6b9b1862134747 Author: Minh-Quang Nguyen <minh-quang.nguyen(a)nutaq.com> Date: Wed Sep 7 10:01:20 2016 -0400 LC15: Implementation of receiving unknown L1 primitive message alarm. The alarm cause ID is manufacture-defined by NuRAN Wireless. Change-Id: I22bb10b795bdc403af259e68f652b7b5b11dcb57 http://cgit.osmocom.org/osmo-pcu/commit/?id=1c80421ddc9a6c0c27e1d826cae24b2… commit 1c80421ddc9a6c0c27e1d826cae24b291401d710 Author: Minh-Quang Nguyen <minh-quang.nguyen(a)nutaq.com> Date: Wed Sep 7 09:54:36 2016 -0400 LC15: Implementation of receiving unknown L1 SAP message alarm. The alarm cause ID is manufacture-defined by NuRAN Wireless. Change-Id: Ieab57aff503f86cbcf7a91e088cb1a8ea790557f http://cgit.osmocom.org/osmo-pcu/commit/?id=66a1786fcd9d252e8af975b35ad2f9f… commit 66a1786fcd9d252e8af975b35ad2f9fca91fec5a Author: Minh-Quang Nguyen <minh-quang.nguyen(a)nutaq.com> Date: Wed Sep 7 09:35:37 2016 -0400 Implementation of no PDCH available alarm. The alarm cause ID is defined by NuRAN Wireless. Change-Id: I382c14b57a062ec7eb4c8421767896df581de634 http://cgit.osmocom.org/osmo-pcu/commit/?id=17c1f04e855188c8329686283fd353d… commit 17c1f04e855188c8329686283fd353d490549179 Author: Minh-Quang Nguyen <minh-quang.nguyen(a)nutaq.com> Date: Wed Sep 7 09:05:00 2016 -0400 LC15: Implementation of L1 transport open failure alarm. The alarm cause ID is manufacture-defined by NuRAN Wireless Change-Id: I401d81b9bf6af82c9ea08329d89f9f720bae7003 http://cgit.osmocom.org/osmo-pcu/commit/?id=e7813197080896f89d0f7dee9fc1d05… commit e7813197080896f89d0f7dee9fc1d050f085b92c Author: Minh-Quang Nguyen <minh-quang.nguyen(a)nutaq.com> Date: Wed Sep 7 09:00:46 2016 -0400 Implementation of direct DSP access failure alarm. The alarm cause ID is manufacture-defined by NuRAN Wireless Change-Id: I14a8d15b9a0f9b823d850ba2582e62bb39fc9734 ----------------------------------------------------------------------- Summary of changes: src/gprs_bssgp_pcu.cpp | 45 ++++++++++++++ src/gprs_bssgp_pcu.h | 1 + src/osmo-bts-litecell15/lc15_l1_if.c | 8 +++ src/pcu_l1_if.cpp | 115 +++++++++++++++++++++++++++++++++++ src/pcuif_proto.h | 18 +++++- src/tbf.cpp | 2 + 6 files changed, 187 insertions(+), 2 deletions(-) hooks/post-receive -- UNNAMED PROJECT

8 years, 9 months

openbsc.git branch neels/ipa_nano3G updated. 0.15.0-511-g5c4ecfb

by gitosis＠osmocom.org

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/ipa_nano3G has been updated discards 9a9ac0cba6fd67da056fc1a583e4f66082aba783 (commit) discards 671cda5f839085c589db819e6f6afb0b22c130dd (commit) discards ace36b88a8bd935019e0f6234903d07d0c88b4f7 (commit) discards 4a5ed39a587cf82112dbcbf44c03ea6d8f919a3a (commit) discards 0aa69b0144b8effa730187f4f26472ede6292159 (commit) discards bfdd09caf1d29d64671b5a44f68fd19f113bc01e (commit) discards e3577d0381abb62951a2422dc53711312b99bae6 (commit) discards e2f15ce84c2a12b9ba001e0a807501ca6fc07ade (commit) discards 352593d9754f1a1597478bcd06ec0c1928017cbb (commit) discards 8bb6714086ef83354fd40e457c055e0ea1224878 (commit) discards ca6210868dc517b3bfa66bf90f4bb7ac95b7c813 (commit) discards 0ebadb9558e131ad524f4df5404a748bf64e99f8 (commit) discards 27f276ac384a8f2fb9e4f8226fbf54bc1e6a7263 (commit) discards f84b806854de79e2c12af41276f5767f064da510 (commit) discards c8e1261d6ae0b25fc9439219f4a8d70b0b0b8dbe (commit) discards a73c821483216c972dda840e5f4c882029f9a912 (commit) discards 1e538c390fc9ed47bf08b6750068aa47f73dd05c (commit) discards 690bc355af46d78adbe6fd1485503cf1c3c59ca3 (commit) discards cf8e40bb99fd15c2b767eb99db4f720edebff3f8 (commit) discards 3cc06f8d27b62efaee7e0151ac89676bfa0b4140 (commit) discards 64e3cba4dd34390deb429d871338c91e954e7be9 (commit) discards 5c7a9b7a7317f99c1499748f7fa2c00938f2707d (commit) discards 6caa820449d75882bfe750dc917981787c5831d1 (commit) discards 05b2363fbe713f87a136ab224f66b32870873d56 (commit) discards 0c6ea7c06aa50de170559a7890edc7b56c741b16 (commit) discards e0f8fd3ee0b83406c12f5d42126a932757070643 (commit) discards b6d46a42d19b6ca452c54021e071326e989467d4 (commit) discards e688da5bf1b7bed447011e230f2eeada557ac520 (commit) discards 338321e7aca2bc512fb6bc5a0eb352b2a18698f4 (commit) discards e72e1b4803f42a42535ee52c3fcabf68f00fe5ea (commit) discards fa3c3efd084b1026c5c017d5ea55c8c653d1b1f6 (commit) discards 587c00dd7df86f5c7a8d761d12e61bea509d0263 (commit) discards 96b318b5db316622f02321a4ec812d574545849f (commit) discards b87bc0e54e9cbce5435d996967dbc80f668028ca (commit) via 5c4ecfb63113220b52cb2adc347465aae6798120 (commit) via d1e2eaed4d1565c42fb4a28c16d4309ff0767ff4 (commit) via 03844c840c87eb722dcede7a21ca754f81757718 (commit) via b6780cf50d9f381939ad39de684e6f0fba0ca790 (commit) via 25a2896d13436371395e18a5db45ec9f1884ba5d (commit) via 322e28ceac3c94bb47a88a412f7b33ded8db9ff9 (commit) via 10922d4c98be605e23c512ec9387b058aa41373b (commit) via a4b274ae8c851f794e95e29c818f87b6eb22907d (commit) via acc3ef3a182c4c48c70296058d47fdb4f21a488f (commit) via 4ddafd77de373f3a70524fbf6160bd4ab7de951b (commit) via 571975bde8eebb160f2cfc3bee4ab9d98d24e189 (commit) via 44459de737dcbe686d6c25d6280ce15fda8ed2b4 (commit) via 9f0633d37adb83f670971aaf136b13a26808b124 (commit) via f7b6940a1f947246b03a571019c3da800cbf0da5 (commit) via 879a2347563d8caa41dd045088ab2ade4656706f (commit) via cb2e75bc25e01ab8c391770cc843ef21e9a8d89b (commit) via 8e6bb2b2b061034d5c9149cc4e081db85e308c82 (commit) via caac5431fb25fcadbab2a3fa012801a32b1bd17a (commit) via 22977c38c8737505e4f5e6154d1937012e8b8558 (commit) via 25bc0d985e41fdc2776a1862f06d321b58422d12 (commit) via d8de08464ecbad5c5459b5ea1a791f9c63bdaa20 (commit) via c4aacfbab9ea91d1c7354ff7aadaacc529113ed2 (commit) via c9ee684535e9f618182a3ab834c817a7e9ea59e5 (commit) via 26f4753514508dc3266b6f7596a52aceeed7c57a (commit) via 86f055b93124b1b94aa6c74cff30e7d983d026a4 (commit) via 380218e45332b353b58bd9e38bca577804212ea1 (commit) via bf30bcc4e2fc9ba082da05c208fb305225daa6c2 (commit) via a23c088381e7f3cd7de4d8247ec962d833e67171 (commit) via 0736093e06ecad5a9d4becc8cc129544d0a276cc (commit) via c481a944e953bf534b76c8f88a6544cdd30c1c47 (commit) via 289c73dbbb34ab6627136f2db569f15574850c8a (commit) via 486d42254baed89f6eaac291823f55480cedc8f6 (commit) via 5310c8ce80b71182af161ef28e8f7fa812b2b28e (commit) via 60d734d998d3db5900ecd4b4b2359022848a8e6a (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 (9a9ac0cba6fd67da056fc1a583e4f66082aba783) \ N -- N -- N (5c4ecfb63113220b52cb2adc347465aae6798120) 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=5c4ecfb63113220b52cb2adc347465aa… commit 5c4ecfb63113220b52cb2adc347465aae6798120 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Mon Apr 25 15:40:54 2016 +0200 RAB parameters: use shorter 32 bit IP address format This is needed for the ip.access nano3G femto cell. ----------------------------------------------------------------------- Summary of changes: hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

8 years, 9 months

osmo-iuh.git branch sysmocom/ipa_nano3G updated. 75bfa56be9aa9fe98e88278e3a58ade29c2d69f0

by gitosis＠osmocom.org

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 575301ae326141af5745b60e286054448b6f1723 (commit) discards ce605fab0a1d3b6eeb417bf31ceeed03dfe724c1 (commit) discards 544b76d6e2db765c57e35af0aa99f162a28685fe (commit) via 75bfa56be9aa9fe98e88278e3a58ade29c2d69f0 (commit) via 6ffacf5ea61308243cf2b0bb0b74e2f0923d19c0 (commit) via 8380eb2a01e6b5eb375adf1e570fa7293226fd47 (commit) via e75a6297da9337db95e94c4eb1cebc1e72fb9d41 (commit) via 6dc074c9aa4eed9f6a69d2bc613f4852aaaa2fc7 (commit) via 01c71fc2dd3c3545a5a3f0d83391a28590dc9f69 (commit) via 4d91ab277b4acc1bc2bdb5edc81d8c09b2bd3e47 (commit) via f495b2347bfc0c974e33988f8240be5cb7b2db3b (commit) via 926153b9af0659e8c214f40424e29cda0c821607 (commit) via 4d8eb4cbd7e7ecc1ad04e3b38ab5121dca2580b1 (commit) via 1d03f19e06ae5ca51e3f37fa01c6585df6d8ad26 (commit) via 085cd67672c9006be6e6f89abb80cff8926ef245 (commit) via 4d675a7df9fd9f3b435da4cbea8446a1e9df22b3 (commit) via 4c45d2b9fd364122f561239a7a8572f904effee6 (commit) via a1bf4f330f50746a3ca7feff5464fe3e3cf17861 (commit) via 0a43722a488aa650ce0192a409734b9ddc093603 (commit) via 6458c30db459c666bce4a517c46b8dfdc1889f53 (commit) via 0961408e1bceb11586783a2c3484f92924429068 (commit) via de0acd2ff2cde071d8d0c6818658107d97c24cd1 (commit) via f706d6c06529c6c6fc2284ce9348a7058653b321 (commit) via fef2e860030217b4a6edddc22b791a35ff224ed5 (commit) via c23146e7f18b0f1bea67ba7b48ad4bc6cc76958b (commit) via 156fa393fc7472ba57683905c054adc6892b3cbd (commit) via fd666890f7f1dc6fc8edc9f923ccf12461d5cbcc (commit) via a9cf70f665c553e7d31ed3c7a68bca326db0d964 (commit) via 802acd0da459b4d74bf4a64d8c12aba0f2a6c09c (commit) via 75f8116132a452af9e2b9c95a9fe1d1142605567 (commit) via 95d0ba5f401db53d5ce3f296ec02bd33865a387b (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 (575301ae326141af5745b60e286054448b6f1723) \ N -- N -- N (75bfa56be9aa9fe98e88278e3a58ade29c2d69f0) 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=75bfa56be9aa9fe98e88278e3a58ade… commit 75bfa56be9aa9fe98e88278e3a58ade29c2d69f0 Author: Harald Welte <laforge(a)gnumonks.org> Date: Sat Apr 30 23:52:02 2016 +0200 hack: Accept also UE_Identity_PR_pTMSIRAI in HNBAP from nano3G I have the feeling that the nano3G simply forwards whatever identity it receives from the MS in RRC via HNBAP, without sending any IDENTITY REQUESTS by itself. That seems like a violation of the RANAP specification, but well. As opposed to Neels' earlier commit, the phone I was testing with (GT-I9100) is using the UE_Identity_PR_pTMSIRAI (PS identity) instead of UE_Identity_PR_tMSILAI (CS identity) when trying its first attempt to register to the network, so let's support that equally. http://cgit.osmocom.org/osmo-iuh/commit/?id=6ffacf5ea61308243cf2b0bb0b74e2f… commit 6ffacf5ea61308243cf2b0bb0b74e2f0923d19c0 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=8380eb2a01e6b5eb375adf1e570fa72… commit 8380eb2a01e6b5eb375adf1e570fa7293226fd47 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. Change-Id: Ia47e398e50e316842cd260dc0d9a4e2d8a1c627c ----------------------------------------------------------------------- Summary of changes: .gitignore | 2 + Makefile.am | 2 +- asn1/utils/asn1tostruct.py | 2 +- configure.ac | 3 + contrib/jenkins.sh | 110 +- doc/Makefile.am | 12 + doc/examples/Makefile.am | 23 + doc/examples/osmo-hnbgw.cfg | 32 + include/osmocom/Makefile.am | 2 +- include/osmocom/iuh/Makefile.am | 2 + include/osmocom/iuh/vty.h | 9 + include/osmocom/ranap/ranap_ies_defs.h | 2967 -------------------------------- move-asn1-header-files.sh | 25 +- src/Makefile.am | 12 +- src/hnbgw.c | 191 +- src/hnbgw.h | 17 +- src/hnbgw_cn.c | 3 +- src/hnbgw_vty.c | 153 ++ src/ranap_msg_factory.c | 7 +- src/tests/dummy_cn_sua.c | 12 +- src/tests/test-ranap.c | 3 +- src/tests/test-ranap.ok | 4 +- 22 files changed, 485 insertions(+), 3108 deletions(-) create mode 100644 doc/Makefile.am create mode 100644 doc/examples/Makefile.am create mode 100644 doc/examples/osmo-hnbgw.cfg create mode 100644 include/osmocom/iuh/Makefile.am create mode 100644 include/osmocom/iuh/vty.h delete mode 100644 include/osmocom/ranap/ranap_ies_defs.h create mode 100644 src/hnbgw_vty.c hooks/post-receive -- Osmocom code for Iuh interface

8 years, 9 months

openbsc.git branch sysmocom/iups deleted. 0.15.0-425-gd174636

by gitosis＠osmocom.org

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, sysmocom/iups has been deleted was d1746360a11d9d8a0745854a0a7ce419e2aa612c ----------------------------------------------------------------------- d1746360a11d9d8a0745854a0a7ce419e2aa612c IuPS: Change GTP-U endpoint to SGSN in PMM_IDLE and page UE when data arrives ----------------------------------------------------------------------- hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

8 years, 9 months

osmo-pcu.git branch nrw/litecell15-merge-and-rebase updated. 0.2-830-gd5415a2

by gitosis＠osmocom.org

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 "UNNAMED PROJECT". The branch, nrw/litecell15-merge-and-rebase has been updated discards aa24b65060e2db64044ea82c6b4059bdb813e02b (commit) via d5415a22f15addf8937a12f37d4c212ec07561e9 (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 (aa24b65060e2db64044ea82c6b4059bdb813e02b) \ N -- N -- N (d5415a22f15addf8937a12f37d4c212ec07561e9) 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-pcu/commit/?id=d5415a22f15addf8937a12f37d4c212… commit d5415a22f15addf8937a12f37d4c212ec07561e9 Author: Minh-Quang Nguyen <minh-quang.nguyen(a)nutaq.com> Date: Tue Sep 6 16:20:43 2016 -0400 Implementation of wrong PCU interface version alarm. When the PCU receives wrong PCU interface version in BTS information indication message. It will send a critical alarm to the BTS before stopping itself. The BTS will do remaining task by forwarding this alarm to core network using standard TS 12.21 failure event report message where the alarm cause ID is manufature-defined by NuRAN Wireless. Change-Id: I0e1131a53ff86ccfccca44d45cae4606240f3c68 ----------------------------------------------------------------------- Summary of changes: src/pcuif_proto.h | 2 ++ 1 file changed, 2 insertions(+) hooks/post-receive -- UNNAMED PROJECT

8 years, 9 months

osmo-pcu.git branch master updated. 0.2-829-g16ddc90

by gitosis＠osmocom.org

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 "UNNAMED PROJECT". The branch, master has been updated via 16ddc90eabad423d247753f7d89639659e049d35 (commit) from 7c7a86c080edd9c92778c941bbe484f59a81f93c (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 ----------------------------------------------------------------- ----------------------------------------------------------------------- Summary of changes: src/osmo-bts-litecell15/lc15_l1_if.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- UNNAMED PROJECT

8 years, 9 months

osmo-iuh.git branch neels/distcheck updated. 5451dfdae4e15d15d7ecbd55314edbe3257c4564

by gitosis＠osmocom.org

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, neels/distcheck has been updated discards 66838e957ae2a595bd82895039d90ccf6afe8aa2 (commit) discards da62d064d1c7cb7499812dfbe7b81ab07d3c51ca (commit) discards 11277b46276e0bbe7de0696b0e0d1c19bfbac149 (commit) discards 89299137a2e8c22f114f5d468604f4e1232a4600 (commit) discards 5ab8fa2b3bbe9d9bef779d2778c42a8dc69f2061 (commit) discards 0537738d0a9c294f5db36b0f831a0858970f5a6c (commit) discards 7076f61ed1e1d292eeaf8a551b93334a076f8817 (commit) discards 314307cdac1f80faa525ccc69fc152bb75cbf7cd (commit) via 5451dfdae4e15d15d7ecbd55314edbe3257c4564 (commit) via 1c8177a120cb66165b7edeae1795c9a5a56e0437 (commit) via 961cbe54c0102f001205df463f57c8f8cf43d16e (commit) via e3a3f8c4df64c4d3a44027911446a932f4e61a14 (commit) via 27407f915040f67a86e34018afec117af7b8a84d (commit) via 746b30cc0deb070369d940763f638cc8509952d4 (commit) via 22064ffe9b31d7e39a7fcc1aa297540d6e71bc4a (commit) via ebca81c4a42e26aeab60d237913ece755eb93eed (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 (66838e957ae2a595bd82895039d90ccf6afe8aa2) \ N -- N -- N (5451dfdae4e15d15d7ecbd55314edbe3257c4564) 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=5451dfdae4e15d15d7ecbd55314edbe… commit 5451dfdae4e15d15d7ecbd55314edbe3257c4564 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Sat Aug 27 14:01:51 2016 +0200 jenkins.sh: enable make distcheck Change-Id: I967d4de9682cb2a45210f689ec076ef457841179 http://cgit.osmocom.org/osmo-iuh/commit/?id=1c8177a120cb66165b7edeae1795c9a… commit 1c8177a120cb66165b7edeae1795c9a5a56e0437 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Sat Aug 27 00:04:20 2016 +0200 build: parallel build: require ../libosmo-ranap.la from tests/ This rule is bad because it re-invokes $(MAKE), but it seems to fix the parallel build. It should probably be done differently. Change-Id: I8107e08e4c211f20d671f520bf6bab9356f3c90e http://cgit.osmocom.org/osmo-iuh/commit/?id=961cbe54c0102f001205df463f57c8f… commit 961cbe54c0102f001205df463f57c8f8cf43d16e Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Thu Aug 18 13:13:55 2016 +0200 build: move headers to include/osmocom/* This came up while fixing 'make distcheck'; this is certainly not the easiest way but it makes sense to have the headers in include/, like we do in openbsc. The easy alternative might be to add -I$(top_srcdir)/src to src/Makefile.am. Remove -I$(top_srcdir)/src from src/tests/Makefile.am, no longer needed. Change-Id: I5a82e029dcdc4df0a60a31271a4883393fe59234 http://cgit.osmocom.org/osmo-iuh/commit/?id=e3a3f8c4df64c4d3a44027911446a93… commit e3a3f8c4df64c4d3a44027911446a932f4e61a14 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Sat Aug 27 00:03:44 2016 +0200 build: cosmetic: hnbap: undup asn1 src path Change-Id: I0507277995302261c87db1b0c48105065cf13ae4 http://cgit.osmocom.org/osmo-iuh/commit/?id=27407f915040f67a86e34018afec117… commit 27407f915040f67a86e34018afec117af7b8a84d Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Sat Aug 27 00:13:55 2016 +0200 build: distcheck: add missing bits for testsuite distcheck Got some errors during 'make distcheck', copying the way openbsc.git does these things. Change-Id: I13d76cd56dfb8fe4eb02d6fcada78a9e3311b51b http://cgit.osmocom.org/osmo-iuh/commit/?id=746b30cc0deb070369d940763f638cc… commit 746b30cc0deb070369d940763f638cc8509952d4 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Sat Aug 27 00:11:26 2016 +0200 build: distcheck: look for asn1 in top_srcdir, not top_builddir Change-Id: Iebcff240ba2fae964dad2a2c481fcbfd29e14e69 http://cgit.osmocom.org/osmo-iuh/commit/?id=22064ffe9b31d7e39a7fcc1aa297540… commit 22064ffe9b31d7e39a7fcc1aa297540d6e71bc4a Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Sat Aug 27 00:00:26 2016 +0200 build: distcheck: add missing distclean files Change-Id: I24d72b2b1bae52a1b2cf8a989396d2aac31d119e http://cgit.osmocom.org/osmo-iuh/commit/?id=ebca81c4a42e26aeab60d237913ece7… commit ebca81c4a42e26aeab60d237913ece755eb93eed Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Fri Aug 26 23:56:44 2016 +0200 build: fix ranap gen, use same for gen hnbap and rua gen fix extraneous rebuild for each make invocation: touch the ranap.stamp file in src/ as the make target suggests. fix for 'make distcheck': ranap gen: move generated sources to builddir, not srcdir. Thus we also -I the builddir include to pick up those headers. hnbap and rua have the same situation as ranap (they generate numerous files from a single make rule). Use the same makefile semantics for those two (commit for ranap gen omitted the same changes for hnbap and rua). The generated headers are thus moved to include/osmocom/*/, so adjust #include statements accordingly (*_common.h, *_ies_defs.h). Also move hnbap_common.h to include/osmocom/hnbap and rua_common.h to include/osmocom/rua, since the *_ies_defs.h want to include them; and since *_ies_defs.h are now in include/osmocom/*, we want a '<foo>' include now. Also adjust gitignore. Change-Id: I32213666fcdfc144008fa7d46497c0938d093e86 ----------------------------------------------------------------------- Summary of changes: hooks/post-receive -- Osmocom code for Iuh interface

8 years, 9 months

osmo-pcu.git branch nrw/litecell15-merge-and-rebase updated. 0.2-830-gaa24b65

by gitosis＠osmocom.org

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 "UNNAMED PROJECT". The branch, nrw/litecell15-merge-and-rebase has been updated discards b9d2b8ea071bcb6e5717729dda5dd41922fd9ca2 (commit) via aa24b65060e2db64044ea82c6b4059bdb813e02b (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 (b9d2b8ea071bcb6e5717729dda5dd41922fd9ca2) \ N -- N -- N (aa24b65060e2db64044ea82c6b4059bdb813e02b) 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-pcu/commit/?id=aa24b65060e2db64044ea82c6b4059b… commit aa24b65060e2db64044ea82c6b4059bdb813e02b Author: Minh-Quang Nguyen <minh-quang.nguyen(a)nutaq.com> Date: Tue Sep 6 16:20:43 2016 -0400 Implementation of wrong PCU interface version alarm. When the PCU receives wrong PCU interface version in BTS information indication message. It will send a critical alarm to the BTS before stopping itself. The BTS will do remaining task by forwarding this alarm to core network using standard TS 12.21 failure event report message where the alarm cause ID is manufature-defined by NuRAN Wireless. Change-Id: I0e1131a53ff86ccfccca44d45cae4606240f3c68 ----------------------------------------------------------------------- Summary of changes: src/pcu_l1_if.cpp | 2 +- src/pcuif_proto.h | 12 +----------- 2 files changed, 2 insertions(+), 12 deletions(-) hooks/post-receive -- UNNAMED PROJECT

8 years, 9 months

osmo-pcu.git branch nrw/litecell15-merge-and-rebase updated. 0.2-830-gb9d2b8e

by gitosis＠osmocom.org

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 "UNNAMED PROJECT". The branch, nrw/litecell15-merge-and-rebase has been updated via b9d2b8ea071bcb6e5717729dda5dd41922fd9ca2 (commit) from 16ddc90eabad423d247753f7d89639659e049d35 (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-pcu/commit/?id=b9d2b8ea071bcb6e5717729dda5dd41… commit b9d2b8ea071bcb6e5717729dda5dd41922fd9ca2 Author: Minh-Quang Nguyen <minh-quang.nguyen(a)nutaq.com> Date: Tue Sep 6 16:20:43 2016 -0400 Implementation of PCU alarm feature Change-Id: I0e1131a53ff86ccfccca44d45cae4606240f3c68 ----------------------------------------------------------------------- Summary of changes: src/bts.h | 7 ++++ src/osmobts_sock.cpp | 2 ++ src/pcu_l1_if.cpp | 93 +++++++++++++++++++++++++++++++++++++++++++++++++++- src/pcu_l1_if.h | 8 +++++ src/pcu_main.cpp | 3 ++ src/pcuif_proto.h | 68 ++++++++++++++++++++++++++++++++++++++ 6 files changed, 180 insertions(+), 1 deletion(-) hooks/post-receive -- UNNAMED PROJECT

8 years, 9 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-commitlog September 2016