Project

General

Profile

Actions

Feature #2411

open

No support for RTP dynamic payload types - AMR/HR/EFR payload types are hardcoded

Added by ipse over 6 years ago. Updated about 6 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
07/30/2017
Due date:
% Done:

0%

Spec Reference:

Description

We haven't looked at the details, but I think it's worthwhile to file this bug to keep a note.

It seems OsmoNITB and OsmoBTS doesn't support dynamic RTP payload types (aka PT). Supporting dynamic PTs is a requirement to interface OsmoNITB/OsmoBTS with external SIP/RTP clients via MNCC socket if we want to use anything except GSM-FR.

Calls between OsmoBTS's work fine, because they always allocate the same PT - e.g. 98 for AMR. But when we deal with external clients we can't control PT allocation of the other side calls will fail or you will hear sound only in one direction (external party to OsmoBTS). Because the other party will ask to send AMR RTP with a PT it selects (e.g. 102 for the sake of an example),but OsmoBTS will send it with PT 98.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)