Project

General

Profile

Feature #2659

prepare osmo-mgw architecture for other endpoint types

Added by laforge almost 2 years ago. Updated about 1 month ago.

Status:
New
Priority:
High
Assignee:
Category:
-
Target version:
-
Start date:
11/18/2017
Due date:
% Done:

0%


Description

there is still a lot of legacy that ties osmo-mgw to the old concept of "a statically allocated array of rtp-bridge endpoints"


Checklist

  • get rid of endpoint integers and replace it with string (e.g. in log messages)
  • dispatch messages like CRCX/MDCX to endpoint class specific operations after message decodin
  • implement endpoint name matching based on endpoint class prefix like 'rtpbridge/'
  • implement a simple "audio file playback" endpoint endpoint class to verify abstraction is complete

Related issues

Related to E1/T1 Hardware Interface - Bug #3260: Implement libosmo-abis input for new E1 interfaceNew05/11/2018

Related to OsmoMGW - Feature #2547: Add E1/T1 endpoint type to osmo-mgwNew10/06/2017

History

#1 Updated by laforge 3 months ago

  • Related to Bug #3260: Implement libosmo-abis input for new E1 interface added

#2 Updated by laforge 3 months ago

  • Related to Feature #2547: Add E1/T1 endpoint type to osmo-mgw added

#3 Updated by laforge 3 months ago

  • Assignee changed from sysmocom to laforge

#4 Updated by laforge 3 months ago

  • Priority changed from Normal to High

#5 Updated by laforge about 1 month ago

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)