Project

General

Profile

Actions

Bug #4141

open

No osmux specific code in place during codec negotiation

Added by pespin over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
sysmocom
Target version:
-
Start date:
08/05/2019
Due date:
% Done:

0%

Spec Reference:

Description

Current code in OsmoBSC and OsmoMSC doesn't take into account that Osmux is to be used when codec negotiation goes one. That means that supported codec list needs to be correctly configured manually in VTY in order to avoid selecting incorrect codecs (like non-AMR). Moreover if an MS doesn't support AMR, since we don't have transcoding yet, the call cannot take place.

Different scenarios need to be listed here and think about what we want to do in each case.

No data to display

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)