Feature #3489
make MGW endpoint domain name part configurable
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 "1@172.31.49.100" (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
History
#1 Updated by neels over 1 year ago
- Related to Feature #3490: Add config option to allow arbitrary domain names in endpoints added
#2 Updated by neels over 1 year ago
#3 Updated by laforge about 1 year ago
- Assignee set to osmith
#5 Updated by osmith 10 months ago
- Status changed from In Progress to Resolved
- Assignee changed from osmith to neels
- % Done changed from 0 to 100
Oh, neels already implemented it: https://gerrit.osmocom.org/#/c/osmo-mgw/+/12357/
