Attention is currently required from: pespin.
Hello Jenkins Builder, laforge, pespin,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-upf/+/28312
to look at the new patch set (#2).
Change subject: implement GTPv1-U ECHO response
......................................................................
implement GTPv1-U ECHO response
Accept data on the GTPv1-U socket and respond to GTPv1-U ECHO REQUEST
messages.
We should keep a deterministic recovery counter that increases with
every restart. As a quick and dirty way just use the current time at
startup for now, until osmo-upf reaches production maturity.
Related: OS#5599
Change-Id: I135370a7723e2c667ec681f50c21107cde63ea5b
---
M include/osmocom/upf/Makefile.am
M include/osmocom/upf/upf.h
A include/osmocom/upf/upf_gtpu_echo.h
M src/osmo-upf/Makefile.am
M src/osmo-upf/upf.c
M src/osmo-upf/upf_gtp.c
A src/osmo-upf/upf_gtpu_echo.c
7 files changed, 176 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-upf refs/changes/12/28312/2
--
To view, visit https://gerrit.osmocom.org/c/osmo-upf/+/28312
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-upf
Gerrit-Branch: master
Gerrit-Change-Id: I135370a7723e2c667ec681f50c21107cde63ea5b
Gerrit-Change-Number: 28312
Gerrit-PatchSet: 2
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: newpatchset
Attention is currently required from: pespin.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-upf/+/28312 )
Change subject: implement GTPv1-U ECHO response
......................................................................
Patch Set 1:
(1 comment)
File src/osmo-upf/upf_gtpu_echo.c:
https://gerrit.osmocom.org/c/osmo-upf/+/28312/comment/310f1b2a_e9945117
PS1, Line 61: msg = msgb_alloc_headroom(1024, 128, "GTP-echo-resp");
> Would be good having this in a tx_echo_resp function.
the rx part is so trivial and it is a private function, but separate tx is semantically nicer indeed
--
To view, visit https://gerrit.osmocom.org/c/osmo-upf/+/28312
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-upf
Gerrit-Branch: master
Gerrit-Change-Id: I135370a7723e2c667ec681f50c21107cde63ea5b
Gerrit-Change-Number: 28312
Gerrit-PatchSet: 1
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Sat, 18 Jun 2022 11:50:21 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment
laforge has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-tetra/+/28377 )
Change subject: update git URLs (git -> https; gitea)
......................................................................
update git URLs (git -> https; gitea)
Change-Id: If7ebc0ef0d82cdad8094f4b6d17f4e477f3189ed
---
M README.md
1 file changed, 2 insertions(+), 2 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-tetra refs/changes/77/28377/1
diff --git a/README.md b/README.md
index 818e78c..fa0980b 100644
--- a/README.md
+++ b/README.md
@@ -28,9 +28,9 @@
You can clone from the official osmo-tetra.git repository using
- git clone git://git.osmocom.org/osmo-tetra.git
+ git clone https://gitea.osmocom.org/tetra/osmo-tetra
-There is a cgit interface at http://git.osmocom.org/osmo-tetra/
+There is a web interface at <https://gitea.osmocom.org/tetra/osmo-tetra>
Mailing List
------------
--
To view, visit https://gerrit.osmocom.org/c/osmo-tetra/+/28377
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-tetra
Gerrit-Branch: master
Gerrit-Change-Id: If7ebc0ef0d82cdad8094f4b6d17f4e477f3189ed
Gerrit-Change-Number: 28377
Gerrit-PatchSet: 1
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-MessageType: newchange
laforge has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-smlc/+/28375 )
Change subject: Fill README with content; convert to markdown
......................................................................
Fill README with content; convert to markdown
Change-Id: I54297aba4dbb4f521caaeb555de9e5404f9e6dcd
---
D README
A README.md
M contrib/osmo-smlc.spec.in
3 files changed, 70 insertions(+), 5 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-smlc refs/changes/75/28375/1
diff --git a/README b/README
deleted file mode 100644
index 06fa1ea..0000000
--- a/README
+++ /dev/null
@@ -1,4 +0,0 @@
-About OsmoSMLC
-==============
-
-FIXME
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..354e683
--- /dev/null
+++ b/README.md
@@ -0,0 +1,69 @@
+osmo-smlc - Osmocom Serving Mobile Location Centre
+==================================================
+
+This repository contains a C-language implementation of a minimalistic
+GSM Serving Mobile Location Centre (SMLC) for 2G (GSM). It is part of the
+[Osmocom](https://osmocom.org/) Open Source Mobile Communications project.
+
+OsmoSMLC exposes
+ * 3GPP Lb interface towards the BSC
+ * The Osmocom typical telnet VTY and CTRL interfaces.
+ * The Osmocom typical statsd exporter.
+
+OsmoSMLC supports the following location methods:
+ * currently only the Timing Advance based method of determining a mobile station; operator must configure the
+ locations of the cells in the osmo-smlc configuration file
+
+Homepage
+--------
+
+You can find the OsmoSMLC issue tracker and wiki online at
+<https://osmocom.org/projects/osmo-smlc> and <https://osmocom.org/projects/osmo-smlc/wiki>
+
+
+GIT Repository
+--------------
+
+You can clone from the official osmo-smlc.git repository using
+
+ git clone https://gitea.osmocom.org/cellular-infrastructure/osmo-smlc
+
+There is a web interface at <https://gitea.osmocom.org/cellular-infrastructure/osmo-smlc>
+
+
+Documentation
+-------------
+
+User Manuals and VTY reference manuals are [optionally] built in PDF form
+as part of the build process.
+
+Pre-rendered PDF version of the current "master" can be found at
+[User Manual](https://ftp.osmocom.org/docs/latest/osmosmlc-usermanual.pdf)
+as well as the [VTY Reference Manual](https://ftp.osmocom.org/docs/latest/osmosmlc-vty-reference.pdf)
+
+
+Mailing List
+------------
+
+Discussions related to osmo-smlc are happening on the
+openbsc(a)lists.osmocom.org mailing list, please see
+<https://lists.osmocom.org/mailman/listinfo/openbsc> for subscription
+options and the list archive.
+
+Please observe the [Osmocom Mailing List
+Rules](https://osmocom.org/projects/cellular-infrastructure/wiki/Mailing_List_Rules)
+when posting.
+
+Contributing
+------------
+
+Our coding standards are described at
+<https://osmocom.org/projects/cellular-infrastructure/wiki/Coding_standards>
+
+We us a gerrit based patch submission/review process for managing
+contributions. Please see
+<https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit> for
+more details
+
+The current patch queue for osmo-smlc can be seen at
+<https://gerrit.osmocom.org/#/q/project:osmo-smlc+status:open>
diff --git a/contrib/osmo-smlc.spec.in b/contrib/osmo-smlc.spec.in
index a5852b8..72e2376 100644
--- a/contrib/osmo-smlc.spec.in
+++ b/contrib/osmo-smlc.spec.in
@@ -77,7 +77,7 @@
%files
%license COPYING
-%doc AUTHORS README
+%doc AUTHORS README.md
%{_bindir}/osmo-smlc
%dir %{_docdir}/%{name}/examples
%dir %{_docdir}/%{name}/examples/osmo-smlc
--
To view, visit https://gerrit.osmocom.org/c/osmo-smlc/+/28375
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-smlc
Gerrit-Branch: master
Gerrit-Change-Id: I54297aba4dbb4f521caaeb555de9e5404f9e6dcd
Gerrit-Change-Number: 28375
Gerrit-PatchSet: 1
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-MessageType: newchange
laforge has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-sip-connector/+/28373 )
Change subject: Convert + Expand README file
......................................................................
Convert + Expand README file
README.md in-line with that of other osmocom CNI projects:
* markdown syntax
* link to manuals, issue tracker, gerrit contributions, etc.
Change-Id: Ieadbbe4d2963e713d569460d053460f4f99d40eb
---
D README.asciidoc
A README.md
M contrib/osmo-sip-connector.spec.in
3 files changed, 83 insertions(+), 35 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-sip-connector refs/changes/73/28373/1
diff --git a/README.asciidoc b/README.asciidoc
deleted file mode 100644
index acd491b..0000000
--- a/README.asciidoc
+++ /dev/null
@@ -1,34 +0,0 @@
-Osmo SIP Connector
-==================
-
-Simple utility to map MNCC to SIP and SIP to MNCC. The VTY interface
-can be used to make configurations. The code doesn't have any RTP or
-transcoding support.
-
-Call identities can be either the MSISDN or the IMSI of the subscriber.
-
-
-Requirements of Equipment
-^^^^^^^^^^^^^^^^^^^^^^^^^
-
-* DTMF need to be sent using SIP INFO messages. DTMF in RTP is not
-supported.
-
-* BTS+PBX and SIP connector+PBX must be in the same network (UDP must be
-able to flow directly between these elements)
-
-* No handover support.
-
-* IP based BTS (e.g. Sysmocom sysmoBTS but no Siemens BS11)
-
-* No emergency calls
-
-Limitations
-^^^^^^^^^^^
-
-* PT of RTP needs to match the one used by the BTS. E.g. AMR needs to use
-the same PT as the BTS. This is because rtp_payload2 is not yet supported
-by the osmo-bts software.
-
-* AMR SDP file doesn't include the mode-set params and allowed codec modes.
-This needs to be configured in some way.
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..4064db6
--- /dev/null
+++ b/README.md
@@ -0,0 +1,82 @@
+osmo-sip-connector - Osmocom SIP connector
+==========================================
+
+This implements an interface between the MNCC (Mobile Network Call Control)
+interface of OsmoMSC (and also previously OsmoNITB) and SIP.
+
+Call identities can be either the MSISDN or the IMSI of the subscriber.
+
+Requirements of Equipment
+-------------------------
+
+* DTMF need to be sent using SIP INFO messages. DTMF in RTP is not
+supported.
+* BTS+PBX and SIP connector+PBX must be in the same network (UDP must be
+able to flow directly between these elements)
+* No handover support.
+* IP based BTS (e.g. Sysmocom sysmoBTS but no Siemens BS11)
+* No emergency calls
+
+Limitations
+-----------
+
+* PT of RTP needs to match the one used by the BTS. E.g. AMR needs to use
+the same PT as the BTS. This is because rtp_payload2 is not yet supported
+by the osmo-bts software.
+
+* AMR SDP file doesn't include the mode-set params and allowed codec modes.
+This needs to be configured in some way.
+
+Homepage
+--------
+
+You can find the osmo-sip-connector issue tracker and wiki online at
+<https://osmocom.org/projects/osmo-sip-conector> and <https://osmocom.org/projects/osmo-sip-conector/wiki>
+
+
+GIT Repository
+--------------
+
+You can clone from the official osmo-msc.git repository using
+
+ git clone https://gitea.osmocom.org/cellular-infrastructure/osmo-sip-connector
+
+There is a web interface at <https://gitea.osmocom.org/cellular-infrastructure/osmo-sip-connector>
+
+
+Documentation
+-------------
+
+User Manuals and VTY reference manuals are [optionally] built in PDF form
+as part of the build process.
+
+Pre-rendered PDF version of the current "master" can be found at
+[User Manual](https://downloads.osmocom.org/docs/latest/osmosipconnector-usermanu…
+as well as the [VTY Reference Manual](https://downloads.osmocom.org/docs/latest/osmosipconnector-vty-refe…
+
+
+Mailing List
+------------
+
+Discussions related to osmo-sip-connector are happening on the
+openbsc(a)lists.osmocom.org mailing list, please see
+<https://lists.osmocom.org/mailman/listinfo/openbsc> for subscription
+options and the list archive.
+
+Please observe the [Osmocom Mailing List
+Rules](https://osmocom.org/projects/cellular-infrastructure/wiki/Mailing_List_Rules)
+when posting.
+
+Contributing
+------------
+
+Our coding standards are described at
+<https://osmocom.org/projects/cellular-infrastructure/wiki/Coding_standards>
+
+We us a gerrit based patch submission/review process for managing
+contributions. Please see
+<https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit> for
+more details
+
+The current patch queue for osmo-sip-connector can be seen at
+<https://gerrit.osmocom.org/#/q/project:osmo-sip-connector+status:open>
diff --git a/contrib/osmo-sip-connector.spec.in b/contrib/osmo-sip-connector.spec.in
index 29baf9b..58bba32 100644
--- a/contrib/osmo-sip-connector.spec.in
+++ b/contrib/osmo-sip-connector.spec.in
@@ -69,7 +69,7 @@
%files
%license COPYING
-%doc README.asciidoc
+%doc README.md
%doc %{_docdir}/%{name}/examples
%{_bindir}/osmo-sip-connector
%dir %{_sysconfdir}/osmocom
--
To view, visit https://gerrit.osmocom.org/c/osmo-sip-connector/+/28373
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-sip-connector
Gerrit-Branch: master
Gerrit-Change-Id: Ieadbbe4d2963e713d569460d053460f4f99d40eb
Gerrit-Change-Number: 28373
Gerrit-PatchSet: 1
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-MessageType: newchange