neels has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-mgw/+/33534 )
Change subject: mgcp: fix "L: a:" header parsing: heed ";" separator
......................................................................
mgcp: fix "L: a:" header parsing: heed ";" separator
In the "L: a:" header, read the first codec name only up to the ";"
separator, and ignore the rest.
According to RFC-2705, the "L: a:" header may include multiple codecs
like "GSM-EFR;GSM" in:
L: p:20, a:GSM-EFR;GSM, nt:IN
osmo-mgw can handle only a single codec here. Since recently, osmo-msc
is our first client that may actually send more than one codec. This
uncovered a bug that leads to failing voice calls:
* osmo-mgw parses the entire list "GSM-EFR;GSM" as a single codec name,
* puts that into the ptmap without scrutiny,
* and even sends it back in the OK response, in the *SDP* part, as a
single "GSM-EFR;GSM" codec entry.
We do not care very much about the "a:" codec list, because we always
establish codecs via SDP later. So all we need to fix this is: parse the
first codec done correctly, and ignore the rest.
Related: OS#6081
Change-Id: I0342e85b32ed89f3a1fdb6131c3c8ded8f47a455
---
M src/libosmo-mgcp/mgcp_protocol.c
1 file changed, 33 insertions(+), 2 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-mgw refs/changes/34/33534/1
diff --git a/src/libosmo-mgcp/mgcp_protocol.c b/src/libosmo-mgcp/mgcp_protocol.c
index 80e0f8a..978af42 100644
--- a/src/libosmo-mgcp/mgcp_protocol.c
+++ b/src/libosmo-mgcp/mgcp_protocol.c
@@ -672,8 +672,8 @@
case 'a':
/* FIXME: LCO also supports the negotiation of more than one codec.
* (e.g. a:PCMU;G726-32) But this implementation only supports a single
- * codec only. */
- if (sscanf(lco_id + 1, ":%16[^,]", codec) == 1) {
+ * codec only. Ignoring all but the first codec. */
+ if (sscanf(lco_id + 1, ":%16[^,;]", codec) == 1) {
talloc_free(lco->codec);
/* MGCP header is case insensive, and we'll need
codec in uppercase when using it later: */
--
To view, visit https://gerrit.osmocom.org/c/osmo-mgw/+/33534
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-mgw
Gerrit-Branch: master
Gerrit-Change-Id: I0342e85b32ed89f3a1fdb6131c3c8ded8f47a455
Gerrit-Change-Number: 33534
Gerrit-PatchSet: 1
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-MessageType: newchange
Attention is currently required from: jolly.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-msc/+/33498 )
Change subject: ASCI: Use a unique call-id for RTP streams
......................................................................
Patch Set 3: Code-Review+1
(4 comments)
This change is ready for review.
Commit Message:
https://gerrit.osmocom.org/c/osmo-msc/+/33498/comment/36d32225_1d982bfd
PS3, Line 9: The call-id may be used by the MGW to identify which connections belong
( "The MGCP protocol features the 'C' (call-id) to identify which connections belong..." )
https://gerrit.osmocom.org/c/osmo-msc/+/33498/comment/0d52ca22_340d5025
PS3, Line 13: The use of MNCC callref as call-id is replaced by a unique call-id. The
(" So far we sent the MNCC callref as call-id. Instead, add a separate unique call_id number space. Assign a unique call-id to each transaction...")
https://gerrit.osmocom.org/c/osmo-msc/+/33498/comment/259eccc8_26ee3bd8
PS3, Line 16: indipendant
("independent")
https://gerrit.osmocom.org/c/osmo-msc/+/33498/comment/6e7cff4c_b569f184
PS3, Line 20: Related: OS#4854
can we also add
Related: OS#3294
thx
--
To view, visit https://gerrit.osmocom.org/c/osmo-msc/+/33498
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-msc
Gerrit-Branch: master
Gerrit-Change-Id: I36c5f159fa0b54fb576ff8bd279928b895554793
Gerrit-Change-Number: 33498
Gerrit-PatchSet: 3
Gerrit-Owner: jolly <andreas(a)eversberg.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Attention: jolly <andreas(a)eversberg.eu>
Gerrit-Comment-Date: Thu, 29 Jun 2023 23:05:45 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: laforge.
jolly has posted comments on this change. ( https://gerrit.osmocom.org/c/osmocom-bb/+/33532 )
Change subject: mobile: Fix gsm_refer_pcs(): PCS can only be ARFCN 512..810
......................................................................
Patch Set 2:
(1 comment)
Patchset:
PS2:
> This would only allow cells in the DCS range to refer to cells with PCS frequencies. […]
double entry, sorry.
--
To view, visit https://gerrit.osmocom.org/c/osmocom-bb/+/33532
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmocom-bb
Gerrit-Branch: master
Gerrit-Change-Id: Id99c8534bf853f4f24f99364790c1ac1df6cc007
Gerrit-Change-Number: 33532
Gerrit-PatchSet: 2
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: jolly <andreas(a)eversberg.eu>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Comment-Date: Thu, 29 Jun 2023 17:44:33 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: jolly <andreas(a)eversberg.eu>
Gerrit-MessageType: comment