osmocom-commitlog

osmocom-commitlog@lists.osmocom.org

7948 discussions

osmo-iuh.git branch neels/wip updated. 88667ba84be4288ae45a357385b7a2e9b60a4789
by gitosis＠osmocom.org 02 May '16

02 May '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, neels/wip has been updated discards e309e52e32f93f99443ebe6a41ca1c360198f4bf (commit) discards 65dd2c8315d44f1da0c89ebcf91ab7c32228f6c8 (commit) via 88667ba84be4288ae45a357385b7a2e9b60a4789 (commit) via 0116ab219ff76dfd5b6b9973711a5cd6d134372f (commit) via bb289e3b810683dadc5e2dd0b345b97cd3e8bddb (commit) via 0a461568f0d9186328a4878daa040bcdb33160c7 (commit) via 14da5411a4fbe05eccff5b4f0934d52773a3f97a (commit) via f764a15c2339d5b24f0258d6605d5c38229209cc (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 (e309e52e32f93f99443ebe6a41ca1c360198f4bf) \ N -- N -- N (88667ba84be4288ae45a357385b7a2e9b60a4789) 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=88667ba84be4288ae45a357385b7a2e… commit 88667ba84be4288ae45a357385b7a2e9b60a4789 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Tue Apr 5 11:53:09 2016 +0200 hnb-test: plmn_id: use 0xf for unused digit http://cgit.osmocom.org/osmo-iuh/commit/?id=0116ab219ff76dfd5b6b9973711a5cd… commit 0116ab219ff76dfd5b6b9973711a5cd6d134372f Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Apr 13 19:09:41 2016 +0200 debug log: rx-unitdata ----------------------------------------------------------------------- Summary of changes: contrib/jenkins.sh | 64 +++++++++++++++++++++++++++++++++++++++++++++++++ src/hnbgw.c | 1 + src/ranap_msg_factory.c | 16 ++++++++++++- src/tests/test-ranap.c | 57 +++++++++++++++++++++++++++++++++++++++++++ src/tests/test-ranap.ok | 29 +++++++++++++++------- 5 files changed, 158 insertions(+), 9 deletions(-) create mode 100755 contrib/jenkins.sh hooks/post-receive -- Osmocom code for Iuh interface

1 0

openbsc.git branch neels/cscn updated. 0.15.0-425-g0cdb711
by gitosis＠osmocom.org 02 May '16

02 May '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 7d8d86644746dafed2263ede8e75cc7d43b3a6f3 (commit) discards e87078e4469ca12483645022c06e8c7d4af7e1ff (commit) discards 84d0e05d89115c189791284676a492c5f9b97d30 (commit) discards 318eaf3aea3367b88bee5a5084c3352b4748a065 (commit) discards b2c66d12bab45df939133fc65eae30c3a7759340 (commit) discards 3494f218422a326cee7b188350fbee61b388bbd3 (commit) discards 427cbc07eb9de3e68d8e43835ddf9d19c38c7a84 (commit) via 0cdb711b5716f0149a92e054e446f271e21d061a (commit) via 004000df739cb082532adf2c3d626988daf8c7f4 (commit) via bcfe01c6ac016f9bee03ee6fd65cad16c0aa4aab (commit) via 074a50e5650b66bfc4f0a0d402343f339b3a46e5 (commit) via 0d06f85e87faaf9a0519d9403e6ab23e91b59a3a (commit) via 2d4bdec0cf41f4b9932c2a4395a3a6fd14bc2acf (commit) via 5c4386c6928d65252eaf327044aae63b5dfbc01e (commit) via fc68c83ddbda55fc2aaa908a3a6a6fca2af71761 (commit) via 74101106a1114d819dfce83cd5a50837c8bd5d0e (commit) via db916bfd8dcceaeb0414ea0628e99a8e7955e660 (commit) via a54358879f1ab928659568ebd6547fc65265f662 (commit) via a54b47b04876152d6f5473d528480a67ccc89803 (commit) via 3b922064a478f3a403d3a40d3f22c9a5675390fa (commit) via 5b3fd465d16547f1175b211dd5366123f260fedb (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 (7d8d86644746dafed2263ede8e75cc7d43b3a6f3) \ N -- N -- N (0cdb711b5716f0149a92e054e446f271e21d061a) 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=0cdb711b5716f0149a92e054e446f271… commit 0cdb711b5716f0149a92e054e446f271e21d061a 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=004000df739cb082532adf2c3d626988… commit 004000df739cb082532adf2c3d626988daf8c7f4 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=bcfe01c6ac016f9bee03ee6fd65cad16… commit bcfe01c6ac016f9bee03ee6fd65cad16c0aa4aab 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=074a50e5650b66bfc4f0a0d402343f33… commit 074a50e5650b66bfc4f0a0d402343f339b3a46e5 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=0d06f85e87faaf9a0519d9403e6ab23e… commit 0d06f85e87faaf9a0519d9403e6ab23e91b59a3a 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=2d4bdec0cf41f4b9932c2a4395a3a6fd… commit 2d4bdec0cf41f4b9932c2a4395a3a6fd14bc2acf 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. http://cgit.osmocom.org/openbsc/commit/?id=5c4386c6928d65252eaf327044aae63b… commit 5c4386c6928d65252eaf327044aae63b5dfbc01e Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Apr 27 01:30:24 2016 +0200 cscn: (re-)add SMPP initialization Remove legacy code from the original NITB version -- the SMPP init functions have since been refactored in 1b0e5540dba697c9cf213e4f0aebc4baaf1618cb. Add SMPP initialization in the refactored version: call the alloc_init before reading config file, and call start with the global network struct after config is read. ----------------------------------------------------------------------- Summary of changes: openbsc/include/openbsc/gprs_sgsn.h | 5 ---- openbsc/src/gprs/gprs_gmm.c | 4 +-- openbsc/src/gprs/gprs_sgsn.c | 19 -------------- openbsc/src/gprs/sgsn_libgtp.c | 52 +++++++++++++++++++++++++++---------- openbsc/src/libiu/iu.c | 8 +++--- openbsc/src/osmo-cscn/cscn_main.c | 2 +- 6 files changed, 45 insertions(+), 45 deletions(-) hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

1 0

openbsc.git branch lafore/utran-ggsn created. 0.15.0-420-ga6c42ad
by gitosis＠osmocom.org 02 May '16

02 May '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, lafore/utran-ggsn has been created at a6c42ad366103ba87b17d45ebc786af75666025a (commit) - Log ----------------------------------------------------------------- http://cgit.osmocom.org/openbsc/commit/?id=a6c42ad366103ba87b17d45ebc786af7… commit a6c42ad366103ba87b17d45ebc786af75666025a Author: Harald Welte <laforge(a)gnumonks.org> Date: Mon May 2 08:34:57 2016 +0200 SGSN: Don't indicate GERAN in Iu mode PDP CTX ACT REQ to GGSN ----------------------------------------------------------------------- hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

1 0

osmo-iuh.git branch neels/wip_hnb_list_double_del deleted. ccd3cdffcad16493fa8ea2570a11b498168aa790
by gitosis＠osmocom.org 01 May '16

01 May '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, neels/wip_hnb_list_double_del has been deleted was ccd3cdffcad16493fa8ea2570a11b498168aa790 ----------------------------------------------------------------------- ccd3cdffcad16493fa8ea2570a11b498168aa790 hnbgw: dumb fix of context map hnb_list double delete ----------------------------------------------------------------------- hooks/post-receive -- Osmocom code for Iuh interface

1 0

osmo-iuh.git branch laforge/wip deleted. 216ac210bfb0e540545ae22faa3da7ee44ccdd28
by gitosis＠osmocom.org 01 May '16

01 May '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, laforge/wip has been deleted was 216ac210bfb0e540545ae22faa3da7ee44ccdd28 ----------------------------------------------------------------------- 216ac210bfb0e540545ae22faa3da7ee44ccdd28 add pkg-config file for libosmo-ranap ----------------------------------------------------------------------- hooks/post-receive -- Osmocom code for Iuh interface

1 0

osmo-iuh.git branch sysmocom/ipa_nano3G updated. 575301ae326141af5745b60e286054448b6f1723
by gitosis＠osmocom.org 01 May '16

01 May '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 77c960c023c42f06bacf6dae085d04193266bed6 (commit) discards ecb259dbb9bdd5196a89dc3205602bba2ae3de06 (commit) discards 87b3bbfb39aa84239d76796353a3acb1d6aec889 (commit) discards e874a5db5aabd717eba5a8dc02b19cef48cb88ec (commit) discards 30dc1920bbcbf80146892808a38cfdbffeeafc6a (commit) discards 4bd1c9f605103b6ff3393ec9185bd47501eea6a3 (commit) discards 81fb7cb24bf5c66d9d196455ad22801f25e05e61 (commit) via 575301ae326141af5745b60e286054448b6f1723 (commit) via ce605fab0a1d3b6eeb417bf31ceeed03dfe724c1 (commit) via 544b76d6e2db765c57e35af0aa99f162a28685fe (commit) via bb289e3b810683dadc5e2dd0b345b97cd3e8bddb (commit) via 0a461568f0d9186328a4878daa040bcdb33160c7 (commit) via 14da5411a4fbe05eccff5b4f0934d52773a3f97a (commit) via f764a15c2339d5b24f0258d6605d5c38229209cc (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 (77c960c023c42f06bacf6dae085d04193266bed6) \ N -- N -- N (575301ae326141af5745b60e286054448b6f1723) 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=575301ae326141af5745b60e2860544… commit 575301ae326141af5745b60e286054448b6f1723 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=ce605fab0a1d3b6eeb417bf31ceeed0… commit ce605fab0a1d3b6eeb417bf31ceeed03dfe724c1 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=544b76d6e2db765c57e35af0aa99f16… commit 544b76d6e2db765c57e35af0aa99f162a28685fe 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. ----------------------------------------------------------------------- Summary of changes: src/ranap_msg_factory.c | 6 +----- src/tests/test-ranap.c | 57 +++++++++++++++++++++++++++++++++++++++++++++++++ src/tests/test-ranap.ok | 23 +++++++++++++++----- 3 files changed, 76 insertions(+), 10 deletions(-) hooks/post-receive -- Osmocom code for Iuh interface

1 0

osmo-iuh.git branch master updated. bb289e3b810683dadc5e2dd0b345b97cd3e8bddb
by gitosis＠osmocom.org 01 May '16

01 May '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 bb289e3b810683dadc5e2dd0b345b97cd3e8bddb (commit) via 0a461568f0d9186328a4878daa040bcdb33160c7 (commit) via 14da5411a4fbe05eccff5b4f0934d52773a3f97a (commit) from f764a15c2339d5b24f0258d6605d5c38229209cc (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=bb289e3b810683dadc5e2dd0b345b97… commit bb289e3b810683dadc5e2dd0b345b97cd3e8bddb Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun May 1 15:20:56 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=0a461568f0d9186328a4878daa040bc… commit 0a461568f0d9186328a4878daa040bcdb33160c7 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=14da5411a4fbe05eccff5b4f0934d52… commit 14da5411a4fbe05eccff5b4f0934d52773a3f97a Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun May 1 15:42:19 2016 +0200 test-ranap: Add test case about constrained integer range decode There was a bug in the asn1c/libffasn1c APER patch that caused constrained integer ranges to be decoded incorrectly. Add a test case for that to avoid people falling into that trap... ----------------------------------------------------------------------- Summary of changes: src/hnbgw.c | 1 + src/ranap_msg_factory.c | 16 +++++++++++++++- src/tests/test-ranap.c | 28 ++++++++++++++++++++++++++++ src/tests/test-ranap.ok | 24 +++++++++++++----------- 4 files changed, 57 insertions(+), 12 deletions(-) hooks/post-receive -- Osmocom code for Iuh interface

1 0

openbsc.git branch sysmocom/ipa_nano3G updated. 0.15.0-419-g4ff5aa4
by gitosis＠osmocom.org 01 May '16

01 May '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, sysmocom/ipa_nano3G has been updated discards 699c3b688825c9a6f8165902f2319d93de1e9c45 (commit) via 4ff5aa42797fd59d6b3fc080c7ada55e4a9163d1 (commit) via fc68c83ddbda55fc2aaa908a3a6a6fca2af71761 (commit) via 74101106a1114d819dfce83cd5a50837c8bd5d0e (commit) via db916bfd8dcceaeb0414ea0628e99a8e7955e660 (commit) via a54358879f1ab928659568ebd6547fc65265f662 (commit) via a54b47b04876152d6f5473d528480a67ccc89803 (commit) via 3b922064a478f3a403d3a40d3f22c9a5675390fa (commit) via 5b3fd465d16547f1175b211dd5366123f260fedb (commit) via 0991c684d342c292e8e5b0fb42f93fc615643580 (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 (699c3b688825c9a6f8165902f2319d93de1e9c45) \ N -- N -- N (4ff5aa42797fd59d6b3fc080c7ada55e4a9163d1) 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=4ff5aa42797fd59d6b3fc080c7ada55e… commit 4ff5aa42797fd59d6b3fc080c7ada55e4a9163d1 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: openbsc/include/openbsc/gprs_sgsn.h | 5 ---- openbsc/src/gprs/gprs_gmm.c | 4 +-- openbsc/src/gprs/gprs_sgsn.c | 19 -------------- openbsc/src/gprs/sgsn_libgtp.c | 52 +++++++++++++++++++++++++++---------- openbsc/src/libiu/iu.c | 8 +++--- openbsc/src/libmsc/gsm_04_08.c | 7 ++--- openbsc/src/osmo-cscn/cscn_main.c | 2 +- 7 files changed, 47 insertions(+), 50 deletions(-) hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

1 0

openbsc.git branch sysmocom/iu updated. 0.15.0-418-gfc68c83
by gitosis＠osmocom.org 01 May '16

01 May '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, sysmocom/iu has been updated via fc68c83ddbda55fc2aaa908a3a6a6fca2af71761 (commit) via 74101106a1114d819dfce83cd5a50837c8bd5d0e (commit) via db916bfd8dcceaeb0414ea0628e99a8e7955e660 (commit) via a54358879f1ab928659568ebd6547fc65265f662 (commit) via a54b47b04876152d6f5473d528480a67ccc89803 (commit) via 3b922064a478f3a403d3a40d3f22c9a5675390fa (commit) via 5b3fd465d16547f1175b211dd5366123f260fedb (commit) from 0991c684d342c292e8e5b0fb42f93fc615643580 (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/openbsc/commit/?id=fc68c83ddbda55fc2aaa908a3a6a6fca… commit fc68c83ddbda55fc2aaa908a3a6a6fca2af71761 Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun May 1 15:29:52 2016 +0200 Support raw IPv4 address in RAB Assignment Response There are different Iu dialects in terms of encoding the transport layer address inside RAB Assignment req + resp. Let's be liberal in what we accept, and simply use the length as an indicator of the format. Wireshark uses similar heuristics. http://cgit.osmocom.org/openbsc/commit/?id=74101106a1114d819dfce83cd5a50837… commit 74101106a1114d819dfce83cd5a50837c8bd5d0e Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun May 1 15:23:41 2016 +0200 RAB Assignment Response: Handle TEID changes When the RNC confirms the RAB Assignment, it can each time indicate a new TEID for the GTP-U endpoint on the RNC side. We need to update our information about the PDP context and include that in the UPDATE PDP CONTEXT that we're sending towards the GGSN. This is similar to updating the RNC-side IP address of the GTP endpoint. http://cgit.osmocom.org/openbsc/commit/?id=db916bfd8dcceaeb0414ea0628e99a8e… commit db916bfd8dcceaeb0414ea0628e99a8e7955e660 Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun May 1 13:36:48 2016 +0200 iu_rab_act_ps: Use GGSN-side TEI in RAB Assignment Requeset When we send the RAB Assignment Request to the RNC, we need to tell it the GGSN-side TEI for data, not "our" (SGSN side) TEID. In the RAB-Assignment.req we inform the RNC of the TEID on the GGSN side, and in the RAB-Assignment.resp the RNC informs us of the TEID on the RNC side. http://cgit.osmocom.org/openbsc/commit/?id=a54358879f1ab928659568ebd6547fc6… commit a54358879f1ab928659568ebd6547fc65265f662 Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun May 1 12:43:21 2016 +0200 Identify PDP context by RAB ID, not TEI When receiving an RAB-Assignment response from the RNC, we should use the RAB ID (=NSAPI) to resolve the PDP context. We cannot use the TEID, as the TEID chosen by the RNC for this RAB has no relationship to the TEID we were using for the RAB-Assignment request. TEIDs are local to each of the peer, like UDP port numbers. http://cgit.osmocom.org/openbsc/commit/?id=a54b47b04876152d6f5473d528480a67… commit a54b47b04876152d6f5473d528480a67ccc89803 Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun May 1 12:21:45 2016 +0200 libiu: Fix missing break statements in switch in cn_ranap_handle_co() http://cgit.osmocom.org/openbsc/commit/?id=3b922064a478f3a403d3a40d3f22c9a5… commit 3b922064a478f3a403d3a40d3f22c9a5675390fa Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun May 1 10:59:12 2016 +0200 SGSN: Use PDP Context NSAPI as RAB ID As Dieter has pointed out, the RANAP spec requires the RAB ID to be equal to the NSAPI of the PDP context for which it is established. http://cgit.osmocom.org/openbsc/commit/?id=5b3fd465d16547f1175b211dd5366123… commit 5b3fd465d16547f1175b211dd5366123f260fedb Author: Harald Welte <laforge(a)gnumonks.org> Date: Sat Apr 30 22:04:50 2016 +0200 Fix parsing of auto-generated config file When starting with empty config file, saving it by 'write file', and then re-starting osmo-cscn, it would complain: Error occurred during reading below line: long name Osmocom Circuit-Switched Core Network The problem is that the vty parser is configured to expect a single token and not a list of tokens here, but we initialize the default value with multiple words (which are treated as separate token). ----------------------------------------------------------------------- Summary of changes: openbsc/include/openbsc/gprs_sgsn.h | 5 ---- openbsc/src/gprs/gprs_gmm.c | 4 +-- openbsc/src/gprs/gprs_sgsn.c | 19 -------------- openbsc/src/gprs/sgsn_libgtp.c | 52 +++++++++++++++++++++++++++---------- openbsc/src/libiu/iu.c | 8 +++--- openbsc/src/osmo-cscn/cscn_main.c | 2 +- 6 files changed, 45 insertions(+), 45 deletions(-) hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

1 0

asn1c.git branch aper-prefix updated. 1b38a280d97c9c3b705d1e3d9f62ba5c4468c3dd
by gitosis＠osmocom.org 30 Apr '16

30 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 "Lev Walkin's asn1 compiler". The branch, aper-prefix has been updated via 1b38a280d97c9c3b705d1e3d9f62ba5c4468c3dd (commit) from 98427f733c59baba8d6aa4daea3dc53d315458a1 (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/asn1c/commit/?id=1b38a280d97c9c3b705d1e3d9f62ba5c44… commit 1b38a280d97c9c3b705d1e3d9f62ba5c4468c3dd Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun May 1 01:02:17 2016 +0200 aper fix for decoding constrained integer with lower boundary When decoding a constrained integer with a lower boundary, we need to make sure the lower bound is added after decoding the raw offset inside the range. Before this change, RANAP_CauseMisc_unspecified_failure (115) would be encoded as 2 (115 - 113 = 2), but would be decoded as 2, rather than 113+2 = 115. Code for this was taken from openairinterface5g/openair3/S1AP/MESSAGES/ASN1/asn1cpatch.p0 which unfortunately doesn't carry much of a revision history :/ ----------------------------------------------------------------------- Summary of changes: skeletons/INTEGER.c | 33 +++++++++++++++++++++------------ 1 file changed, 21 insertions(+), 12 deletions(-) hooks/post-receive -- Lev Walkin's asn1 compiler

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-commitlog