Project

General

Profile

Actions

Bug #5308

open

confusion around mgw e1 line vs trunk dichtomy

Added by laforge 2 months ago. Updated about 1 month ago.

Status:
Stalled
Priority:
Normal
Assignee:
Category:
RTP/Media
Target version:
-
Start date:
11/14/2021
Due date:
% Done:

0%

Spec Reference:

Description

there seems to be some lack of logical clarity how the MGCP endpoint names are constructed for use with E1.

  • osmo-mgw uses the trunk number to construct the "e1-N" part in "ds/e1-0/s-1/su16-0"
    • any e1_input line_nr can be mapped to any trunk_nr in the config
  • osmo-bsc unconditionally uses the e1_input line_nr to construct the "e1-N" part in "ds/e1-0/s-1/su16-0"
This means that the entire setup will only work, if osmo-mgw is confiugred to use the same trunk_nr as e1_input line_nr, which
  1. is weird, as why would you make something configurable if it only works in one way, and
  2. is not mentioned or documented anywhere in either the osmo-mgw or osmo-bsc documentation, and also not really visible from the example configs, AFAICT

So I think we have two ways forward:

  1. make osmo-mgw always use the e1 line_nr for constructing the enpdoint names
  2. allow osmo-bsc to configure the mgw-side trunk number [for each timeslot?]
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)