Project

General

Profile

Actions

Feature #6171

open

mgcp-client API: there should be a separate mgcp_codec_param for each codec in mgcp_msg.codecs[]

Added by dexter 6 months ago. Updated 4 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
09/08/2023
Due date:
% Done:

90%

Spec Reference:

Description

This was previously discussed in ticket #5723, which got deleted due to an error.

There is a problem we face with the mgcp_client API. mgcp_client_fsm in particular.

The problem is that we are not able to assign different payload type numbers for the same codec. So it is not possible to have the following configuration:

codec: AMR, payload-type: 112
codec: AMR, payload-type: 113

However, this would be necessary in case we want to define AMR once in octet-aligned and once in bandwith-efficient configuration, which brings us to the second problem. Since there is only one mgcp_codec_param struct member "param", which only lets us to define exactly one set of codec parameters we cannot even define two different configurations.

Also in some cases it would be also convenient to circumvent the SDP parsing/generation of osmo-mgcp-client and use a user defined SDP string directly.


Related issues

Related to OsmoBTS - Bug #5688: osmo-bts-sysmo and osmo-bts-trx use different GSM-HR RTP packet formatResolveddexter09/20/2022

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)