This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-commitlog@lists.osmocom.org/.
gitosis at osmocom.org gitosis at osmocom.orgThis 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 39645b824a08b355fa48361491d5a1c3e9e6bd4d (commit) via 1e96af63259272b73625e1aa40f1b935aece7c29 (commit) from 7c44415d785422b8f7e02059420e7c6feb89f4e9 (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=39645b824a08b355fa48361491d5a1c3e9e6bd4d commit 39645b824a08b355fa48361491d5a1c3e9e6bd4d Author: Jacob Erlbeck <jerlbeck at sysmocom.de> Date: Mon Mar 16 12:27:11 2015 +0100 bssgp: Handle BSSGP STATUS messages Currently incoming BSSGP STATUS messages are just logged and apart from that ignored. Since it is possible that the gbproxy can eventually send both valid replies (from the primary SGSN) and STATUS(unknown BVCI) messages (from the secondary SGSN). Since the PCU assumes in this case that the BVC has been successfully reset and unblocked, it will not send a BVC RESET message after receiving an NS_UNBLOCK. This commit changes gprs_bssgp_pcu_rcvmsg to pass BSSGP STATUS messages to bssgp_rcvmsg() which will in turn call bssgp_prim_cb() with primitive NM_STATUS. Then the BVC RESET or UNBLOCK procedure will be started if the IE in the message matches and the PCU assumes that the BVC should have been successfully reset and unblocked respectively while the STATUS message tells otherwise. Note that bssgp_rcvmsg() from libosmocore is otherwise used for the SGSN side only, albeit it generally just decodes messages, does basic protocol handling and eventually invokes PRIM indications. The only exception here is the handling of BVC RESET, which is implemented specifically for the SGSN. Ticket: OW#1414 Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=1e96af63259272b73625e1aa40f1b935aece7c29 commit 1e96af63259272b73625e1aa40f1b935aece7c29 Author: Jacob Erlbeck <jerlbeck at sysmocom.de> Date: Tue Mar 17 08:11:25 2015 +0100 bssgp: Set blocking and reset timer to 30s Currently the timer T1 and T2 are hard-coded to 1s which is pretty low in consideration of a possible high latency connection to the SGSN. This commit introduces macros for the timer values and sets them to 30s. Sponsored-by: On-Waves ehf ----------------------------------------------------------------------- Summary of changes: src/gprs_bssgp_pcu.cpp | 76 ++++++++++++++++++++++++++++++++++++++++++++------ 1 file changed, 68 insertions(+), 8 deletions(-) hooks/post-receive -- UNNAMED PROJECT