Feature #2710
closed
Support shared osmo-mgw process between osmo-msc and osmo-bsc in the same host
Added by pespin over 6 years ago.
Updated about 6 years ago.
Description
In development systems as well as in embedded products where we run osmocom's network-in-the-box, it's pretty convenient to run only one osmo-mgw process and have osmo-msc and osmo-bsc both use it. We should document in here what's needed to achieve that, and document how a config file for osmo-mgw osmo-msc and osmo-bsc would look like in this scenario.
This will resolve isself as soon as we leave the decision on which endpoint to use to osmo-mgw. Than osmo-bsc and osmo-msc could use one mgw at the same time without interfering.
- Status changed from New to In Progress
- % Done changed from 0 to 100
- % Done changed from 100 to 60
The TTCN3 testsuit must change in order to expect a wildcarded CRCX. All following MGCP operations will not significantly change. The MSC will just use the endpoint that TTCN3 assigns.
I came a bit further here. I managed to get MSC_Tests.TC_lu_and_mt_call passed with the dynamic endpoint. However. I did not find out yet how to assign an endpoint. I think it would be enough to just replace the * in the string with a 1. Currently I am replacing the whole endpoint name, which is a little too much. Also I do not understand how the BSC tests exactly do that.
- % Done changed from 60 to 90
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
Also available in: Atom
PDF
