Project

General

Profile

Actions

Bug #6177

closed

AMR-WB not returned in MDCX OK

Added by neels 6 months ago. Updated 3 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
09/13/2023
Due date:
% Done:

0%

Spec Reference:

Description

In the test I am currently running, it so happens that osmo-msc enables AMR-WB for 3G.
(My testing is about something else entirely, just noting this down now because it caught my attention.)

I see an MDCX to osmo-mgw with AMR and AMR-WB included.
The OK response however only includes AMR, no AMR-WB.

The osmo-mgw log doesn't show any trouble:

Sep 13 23:14:38 arn-testnitb osmo-mgw[46256]: 20230913231438724 DLMGCP NOTICE endpoint:rtpbridge/1@mgw MDCX: modifying existing connection ... (mgcp_protocol.c:1169)
Sep 13 23:14:38 arn-testnitb osmo-mgw[46256]: 20230913231438724 DLMGCP NOTICE endpoint:rtpbridge/1@mgw CI:764B8A8A Got media info via SDP: port:4024, addr:10.9.25.182, duration:20, payload-types:112=AMR 113=AMR-WB  (mgcp_sdp.c:444)
Sep 13 23:14:38 arn-testnitb osmo-mgw[46256]: 20230913231438724 DLMGCP NOTICE endpoint:rtpbridge/1@mgw CI:764B8A8A MDCX: connection successfully modified (mgcp_protocol.c:1372)

Find out why AMR-WB is dropped in the response, and fix.


Files

mdcx_with_amrwb.pcapng mdcx_with_amrwb.pcapng 796 Bytes neels, 09/13/2023 11:25 PM

Related issues

Related to OsmoMGW - Bug #6293: osmo-mgw "decides" for a codec during MGCP handling; instead it should handle all configured payload type numbers as they arrive in RTPNew12/07/2023

Actions
Related to OsmoMGW - Feature #6136: libosmo-mgcp-client should ignore unknown codecs in SDPStalledjolly08/08/2023

Actions
Actions #1

Updated by laforge 4 months ago

  • Assignee set to neels
Actions #2

Updated by neels 3 months ago

  • Related to Bug #6293: osmo-mgw "decides" for a codec during MGCP handling; instead it should handle all configured payload type numbers as they arrive in RTP added
Actions #3

Updated by neels 3 months ago

  • Related to Feature #6136: libosmo-mgcp-client should ignore unknown codecs in SDP added
Actions #4

Updated by neels 3 months ago

From recent code exposure, I know now that osmo-mgw currently decides on a single matching codec,
at CRCX/MDCX time, and returns only that codec in MGCP OK messages.

So the reason probably isn't the AMR-WB codec, but that osmo-mgw always returns only one codec.
Also related: osmo-mgw completely fails CRCX/MDCX that contain even one unknown codec.
So it has successfully parsed AMR-WB, because we see an OK response.

Actions #5

Updated by neels 3 months ago

  • Status changed from New to Rejected
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)