Bug #6177
closedAMR-WB not returned in MDCX OK
0%
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
Related issues
Updated by neels 5 months ago
- Related to Feature #6136: libosmo-mgcp-client should ignore unknown codecs in SDP added
Updated by neels 5 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.