Project

General

Profile

Actions

Feature #3489

closed

make MGW endpoint domain name part configurable

Added by neels over 5 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
08/20/2018
Due date:
% Done:

100%

Spec Reference:

Description

So far we create endpoints at the MGW using names like "1@mgw", i.e. with domain name "mgw".
When connecting to an SCCPlite MSC, I find the MSC issuing a CRCX on endpoint "" (the IP address osmo-mgw is bound to).
The domain name used by MSC and osmo-bsc must be the same, so that they address the same endpoint, and osmo-mgw expects exactly one given domain name.
osmo-mgw's domain name is configurable by 'mgcp' / 'domain NAME'.

Add to osmo-bsc an 'msc 0' / 'mgw domain NAME' config item, so that it can be set to match the domain name the SCCPlite MSC sends.


Related issues

Related to OsmoMGW - Feature #3490: Add config option to allow arbitrary domain names in endpointsResolvedneels08/20/2018

Actions
Actions #1

Updated by neels over 5 years ago

  • Related to Feature #3490: Add config option to allow arbitrary domain names in endpoints added
Actions #2

Updated by neels over 5 years ago

Actions #3

Updated by laforge over 5 years ago

  • Assignee set to osmith
Actions #4

Updated by osmith about 5 years ago

  • Status changed from New to In Progress
Actions #5

Updated by osmith about 5 years ago

  • Status changed from In Progress to Resolved
  • Assignee changed from osmith to neels
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)