osmocom-commitlog August 2017

osmocom-commitlog@lists.osmocom.org

1 participants
244 discussions

libosmo-sccp.git branch pre_release updated. 0.0.6.3-287-g9d1a3f6
by gitosis＠osmocom.org 09 Aug '17

09 Aug '17

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 "SCCP Library". The branch, pre_release has been updated discards ad2db7aedd625da964c6856056fcd16519dbc3b7 (commit) discards fd63ccca545fdeebd2a621ac41fc5f5d9c1b2d80 (commit) discards 75ed8def84103db9a3ae22d5ebce8d2cb84aacc8 (commit) discards b75258e51a4efb6cff2f3e956b50fa020233c6c2 (commit) discards 3c3f70a2457f437f07836280eaebe9f5c6a7514c (commit) discards 02f7c45b69c9f2d71b34eef059a43929a831d65e (commit) discards b35f6d1c1e81a3d4187915234ca332fc26a0858b (commit) discards 06956848a3ec1b64c6bb3d71abde8db44440d80f (commit) via 9d1a3f66457508e16dd2d1d33fe7bf5ed24b633b (commit) via 2373f2778a135e4fc37ff5c741ac3293b18b8d87 (commit) via e634a6f3251cf556ca8d1466b044775e44a48a79 (commit) via 037d46abc181d5a763f2171a5e08154eb163fd0c (commit) via 603e065f43a9b0a6d9d92584ba458fefee32b516 (commit) via c881c4912709be005cbb3ffb02ba06f13c69d24b (commit) via 775ac6f6b1c47066db58608f9497f0e4916bbcc4 (commit) via a212398f7c39ab0e919e0c9efde8a1c8a37678bb (commit) via b352ca030d8870930493f36e2b3702760ff4b44a (commit) via b711e1450444c5882a8d9a941094183484fa47db (commit) via 81a029a4e46bb7c62b2401ec055fe44c5b7568cd (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 (ad2db7aedd625da964c6856056fcd16519dbc3b7) \ N -- N -- N (9d1a3f66457508e16dd2d1d33fe7bf5ed24b633b) 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-sccp/commit/?id=9d1a3f66457508e16dd2d1d33fe… commit 9d1a3f66457508e16dd2d1d33fe7bf5ed24b633b Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Thu Jul 27 17:33:06 2017 +0200 cosmetic: ws in log Change-Id: If5a56ec170d4e91ce070f6fa9c9cfe5bbc121186 http://cgit.osmocom.org/libosmo-sccp/commit/?id=2373f2778a135e4fc37ff5c741a… commit 2373f2778a135e4fc37ff5c741ac3293b18b8d87 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Jul 26 18:15:47 2017 +0200 sccp_helpers: check buf len in append_to_buf() Change-Id: I2e6d656871f952be8e719573fedf2154832841d7 http://cgit.osmocom.org/libosmo-sccp/commit/?id=e634a6f3251cf556ca8d1466b04… commit e634a6f3251cf556ca8d1466b044775e44a48a79 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Thu Jul 27 13:53:03 2017 +0200 sccp-addr vty: set RI to SSN_PC when setting a point-code Change-Id: I75c67d289693f1c2a049ac61cf2b2097d6e5687d http://cgit.osmocom.org/libosmo-sccp/commit/?id=037d46abc181d5a763f2171a5e0… commit 037d46abc181d5a763f2171a5e08154eb163fd0c Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Thu Jul 27 15:22:06 2017 +0200 fix osmo_sccp_addr_dump(): actually print RI Adjust xua_test accordingly. Change-Id: I93e0aa706867e7b1de7f7a6071e3c8af89772af0 http://cgit.osmocom.org/libosmo-sccp/commit/?id=603e065f43a9b0a6d9d92584ba4… commit 603e065f43a9b0a6d9d92584ba458fefee32b516 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Jul 26 18:07:53 2017 +0200 add osmo_sccp_addr_name() and three value_string[]s osmo_sccp_addr_dump() just prints the raw values. In osmo_sccp_addr_name(), use osmo_ss7_pointcode_print() and newly added RI, SSN and GT value_string[] to print more human readable log output. Change-Id: Ie1aedd7894acd69ddc887cd65a8a0df4b888838c http://cgit.osmocom.org/libosmo-sccp/commit/?id=c881c4912709be005cbb3ffb02b… commit c881c4912709be005cbb3ffb02ba06f13c69d24b Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Thu Jul 27 13:51:46 2017 +0200 introduce OSMO_SCCP_RI_NONE to indicate unset RI Allows to automatically set an RI in future change I75c67d289693f1c2a049ac61cf2b2097d6e5687d "sccp-addr vty: set RI to SSN_PC when setting a point-code" Change-Id: I6e2f31b023b08cba2f2ee8234e6108efcaca41c0 http://cgit.osmocom.org/libosmo-sccp/commit/?id=775ac6f6b1c47066db58608f949… commit 775ac6f6b1c47066db58608f9497f0e4916bbcc4 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Thu Jul 27 13:50:31 2017 +0200 constify ss7_instance arg of osmo_ss7_pointcode_print() Change-Id: I8c6b7188d004033e75e9c41f4a65c418d13a79c5 http://cgit.osmocom.org/libosmo-sccp/commit/?id=a212398f7c39ab0e919e0c9efde… commit a212398f7c39ab0e919e0c9efde8a1c8a37678bb Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Jul 26 17:31:53 2017 +0200 consistency: use OSMO_SS7_PC_INVALID for osmo_sccp_user A previous patch added ss7_instance primary_pc validity checks by means of OSMO_SS7_PC_INVALID. To be consistent, also adjust sccp_user accordingly. (see I7f0f0c89b7335d9da24161bfac8234be214ca00c) Remove the osmo_sccp_user's pc_valid field, replaced by pc=OSMO_SS7_PC_INVALID. Adjust all code paths. Simplify some log printing, using the fact that osmo_ss7_pointcode_print() now outputs "(no PC)" for unset point codes. Change-Id: I8684c9b559712072c772012890bbf7efa7c8eb35 http://cgit.osmocom.org/libosmo-sccp/commit/?id=b352ca030d8870930493f36e2b3… commit b352ca030d8870930493f36e2b3702760ff4b44a Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Jul 26 17:31:53 2017 +0200 ensure valid primary_pc in osmo_ss7_instance Initialize osmo_ss7_instance.cfg.primary_pc = OSMO_SS7_PC_INVALID. Adjust all code paths using primary_pc to ensure it is indeed valid. Rationale: It looks like we are going to use the primary point-code of an SS7 instance to derive a local SCCP address, e.g. for osmo-bsc and osmo-hnbgw. cs7-instance 1 point-code 1.2.3 ! sets osmo_ss7_instance.primary_pc = 1.2.3 sccp-address msc point-code 0.0.1 routing-indicator PC hnb iucs remote-addr msc ! derives cs7 instance 1 and local pc 1.2.3 If 'point-code 1.2.3' is omitted, this becomes '0.0.0' without the user noticing, and this happens for each client that omits it. I would like to barf when no local PC is set. Change-Id: I7f0f0c89b7335d9da24161bfac8234be214ca00c http://cgit.osmocom.org/libosmo-sccp/commit/?id=b711e1450444c5882a8d9a94109… commit b711e1450444c5882a8d9a941094183484fa47db Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Jul 26 17:31:53 2017 +0200 add OSMO_SS7_PC_INVALID, add osmo_ss7_pc_is_valid() Introduce OSMO_SS7_PC_INVALID to mark an unset point code. Add static osmo_ss7_pc_is_valid() (name matches schema of osmo_ss7_pc_is_local()). In osmo_ss7_pointcode_print(), return "(no PC)" if !osmo_ss7_pc_is_valid(), for convenient printing of any PC state. Subsequent patches will use this for osmo_ss7_instance (I7f0f0c89b7335d9da24161bfac8234be214ca00c) as well as osmo_sccp_user (I8684c9b559712072c772012890bbf7efa7c8eb35). Rationale: Currently, in osmo_ss7_vty.c we had "if (inst->cfg.primary_pc)" suggesting 0 is invalid, but in struct osmo_sccp_user we have flag pc_valid suggesting 0 is indeed valid. All known point code formats are <= 24bit, so we can easily use 0xffffffff as indicator for an unset PC, which removes the need to remember to set a second field for validity and keeps the structs nice and lean. Change-Id: Ib5715bf03a4de7713a7a809dfd821c700255ba8c ----------------------------------------------------------------------- Summary of changes: include/osmocom/sigtran/osmo_ss7.h | 9 ++++- include/osmocom/sigtran/sccp_sap.h | 2 + src/osmo_ss7.c | 16 ++++++-- src/osmo_ss7_vty.c | 5 +-- src/sccp_internal.h | 1 - src/sccp_scoc.c | 12 ++---- src/sccp_scrc.c | 2 +- src/sccp_user.c | 81 +++++++++++++++++++++++++++----------- src/sccp_vty.c | 2 +- tests/ss7/ss7_test.c | 1 - 10 files changed, 88 insertions(+), 43 deletions(-) hooks/post-receive -- SCCP Library

1 0

openbsc.git branch pmaier/aoip3 updated. 0.15.0-937-gf4d091166
by gitosis＠osmocom.org 09 Aug '17

09 Aug '17

1 0

openbsc.git branch pmaier/aoip3 updated. 0.15.0-936-g4cca03749
by gitosis＠osmocom.org 09 Aug '17

09 Aug '17

1 0

osmo-bts.git branch laforge/virt-bts deleted. 0.4.0-113-gc2bb8f8
by gitosis＠osmocom.org 09 Aug '17

09 Aug '17

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 BTS-side code (Abis, scheduling, ...)". The branch, laforge/virt-bts has been deleted was c2bb8f8fe80ad870ed501e0aab8f53ebca1a7f62 ----------------------------------------------------------------------- c2bb8f8fe80ad870ed501e0aab8f53ebca1a7f62 WIP: Initial check-in of a new virtual BTS ----------------------------------------------------------------------- hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

1 0

openbsc.git branch master updated. 0.15.0-840-gf8b2d46dc
by gitosis＠osmocom.org 09 Aug '17

09 Aug '17

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 "Legacy: The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)". The branch, master has been updated via f8b2d46dc00ff4da96c6932b6cfd5b792b36b209 (commit) via 69031ab255f3682174c7740b6957da03753a3a74 (commit) via fdb690c8030b2357f980f86805da3a88a5bc07c5 (commit) from 29ed8002c3a8c7e64f2328ef6031543628d18000 (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=f8b2d46dc00ff4da96c6932b6cfd5b79… commit f8b2d46dc00ff4da96c6932b6cfd5b792b36b209 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Mon Jul 24 13:36:42 2017 +0200 timer vty: also print the default value in cmd doc Rationale: allows seeing all timer defaults at once by doing OsmoBSC(config-net)# timer ? Before, defaults are visible only by doing on each timer: OsmoBSC(config-net)# timer t1234 <tab> Change-Id: I8259234e5c62e058dde56d531071440bbab11462 http://cgit.osmocom.org/openbsc/commit/?id=69031ab255f3682174c7740b6957da03… commit 69031ab255f3682174c7740b6957da03753a3a74 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Mon Jul 24 13:06:45 2017 +0200 vty: add 'default' keyword to timer config Change-Id: I4e837e8bedfad7ac4fd50048ecb016ddb37c2397 http://cgit.osmocom.org/openbsc/commit/?id=fdb690c8030b2357f980f86805da3a88… commit fdb690c8030b2357f980f86805da3a88a5bc07c5 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Mon Jul 24 13:45:12 2017 +0200 cosmetic: vty for timers: remove obsolete range check The VTY parsing already ensures the parameter range being 1..65535, no need to check the range again. Change-Id: I1cffa5b01cd5c589f1e42998e32135f1da8c960b ----------------------------------------------------------------------- Summary of changes: openbsc/src/libbsc/bsc_vty.c | 47 ++++++++++++++++++++++++-------------------- 1 file changed, 26 insertions(+), 21 deletions(-) hooks/post-receive -- Legacy: The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

1 0

osmocom-bb.git branch master updated. osmocon_v0.0.0-1835-ga52abd5d
by gitosis＠osmocom.org 09 Aug '17

09 Aug '17

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 Open Source GSM Base Band stack". The branch, master has been updated via a52abd5d4f415760c6aa50da6b1e3ad333f4b1bb (commit) from 5e0fa863cb6a66c2073bb218489e6291755c2283 (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/osmocom-bb/commit/?id=a52abd5d4f415760c6aa50da6b1e3… commit a52abd5d4f415760c6aa50da6b1e3ad333f4b1bb Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Thu Jul 27 12:25:34 2017 +0600 vty_interface.c: use RPLMN from settings if preset Previously, when testcard was attached via VTY interface, the initial values were used for MCC / MNC, LAC and TMSI, even if correct RPLMN settings were set. Change-Id: Ic70889cdb6be95f06d0c2df710524b4128b5f72b ----------------------------------------------------------------------- Summary of changes: src/host/layer23/src/mobile/vty_interface.c | 15 +++++++++++++++ 1 file changed, 15 insertions(+) hooks/post-receive -- The Open Source GSM Base Band stack

1 0

osmo-bts.git branch master updated. 0.4.0-576-gbc56094
by gitosis＠osmocom.org 09 Aug '17

09 Aug '17

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 BTS-side code (Abis, scheduling, ...)". The branch, master has been updated via bc56094cacd868cdb0336b215e4268bb69cab168 (commit) from de99be4afbc35e22f4f0263b0e9661dcecdc1ea2 (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-bts/commit/?id=bc56094cacd868cdb0336b215e4268b… commit bc56094cacd868cdb0336b215e4268bb69cab168 Author: Harald Welte <laforge(a)gnumonks.org> Date: Fri Jul 28 14:38:28 2017 +0200 GSMTAP: Don't log fill frames via GSMTAP There's very little point in sending fill frames (such as empty PAGING) or dummy UI frames via GSMTAP all the time. They serve no purpose other than to bloat the log files and make it more difficult for users to find the interesting bits among all this noise. Change-Id: Icd18dafb235933c9e6aa9d98ddd8fac1522cc9ac ----------------------------------------------------------------------- Summary of changes: src/common/l1sap.c | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

1 0

openbsc.git branch master updated. 0.15.0-837-g29ed8002c
by gitosis＠osmocom.org 09 Aug '17

09 Aug '17

1 0

openbsc.git branch master updated. 0.15.0-836-g4e5b90a59
by gitosis＠osmocom.org 09 Aug '17

09 Aug '17

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 "Legacy: The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)". The branch, master has been updated via 4e5b90a594f987266a7e9492f30780eb92b9639c (commit) via 31655d84faa7f7fe823111856ae2035d44aca0eb (commit) via 3e4295287f1a2866e6e512517a2c94f608ecbd30 (commit) from 18ca1ce2ea9f0c353e6886a9d05c61238bba9dc6 (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=4e5b90a594f987266a7e9492f30780eb… commit 4e5b90a594f987266a7e9492f30780eb92b9639c Author: Pablo Neira Ayuso <pablo(a)gnumonks.org> Date: Mon Aug 7 14:01:10 2017 +0100 libmsc: remove 'deferred' parameter in sms_route_mt_sms() No need to cache the sms object, just cache what we need into the smpp_cmd structure. This simplifies what that I introduced in 93ffbd0029d1 ("libmsc: send RP-ACK to MS after ESME sends SMPP DELIVER-SM-RESP"). Change-Id: Iba5f864f9bb963baff95969e306b1b7cff00c1e3 http://cgit.osmocom.org/openbsc/commit/?id=31655d84faa7f7fe823111856ae2035d… commit 31655d84faa7f7fe823111856ae2035d44aca0eb Author: Pablo Neira Ayuso <pablo(a)gnumonks.org> Date: Mon Aug 7 14:01:07 2017 +0100 libmsc: remove duplicate lines in deliver_to_esme() This code is accidentally doing the same thing twice, remove it. Change-Id: I68087a850399e22951d2407e4d8a09c671a775c9 http://cgit.osmocom.org/openbsc/commit/?id=3e4295287f1a2866e6e512517a2c94f6… commit 3e4295287f1a2866e6e512517a2c94f608ecbd30 Author: Pablo Neira Ayuso <pablo(a)gnumonks.org> Date: Mon Aug 7 14:01:05 2017 +0100 libmsc: remove dead code in sms_route_mt_sms() The following branch: if (!rc && !gsms->receiver) rc = GSM411_RP_CAUSE_MO_NUM_UNASSIGNED; at the end of sms_route_mt_sms() always evaluates false. Just a bit before, in such function, we have this: if (!gsms->receiver) { ... #ifdef BUILD_SMPP ... #else ... #endif return rc; } So, if there is no receiver, we just stop running code and return the RP cause via the rc variable. Same applies to the smpp_first check under the BUILD_SMPP ifdef (that I have removed in this snippet to keep this commit message small). Change-Id: Ic3502b5b169bc7a73a67fd6ff53d8b6c0dc045c8 ----------------------------------------------------------------------- Summary of changes: openbsc/src/libmsc/gsm_04_11.c | 22 ++++++++-------------- openbsc/src/libmsc/smpp_openbsc.c | 32 +++++++++++++------------------- openbsc/src/libmsc/smpp_smsc.h | 5 +++-- 3 files changed, 24 insertions(+), 35 deletions(-) hooks/post-receive -- Legacy: The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

1 0

openbsc.git branch master updated. 0.15.0-833-g18ca1ce2e
by gitosis＠osmocom.org 09 Aug '17

09 Aug '17

1 0

← Newer
1
...
18
19
20
21
22
23
24
25
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-commitlog August 2017