osmo-bsc integration to osmo-msc

[Ron]

Hi Harald,

Installed the osmo-stp in the same machine with osmo-msc and osmo-bsc but unfortunately, osmo-bsc logs still shows connection timeout and tries to reconnect again.

<000a> bsc_msc.c:278 Attempting to reconnect to the MSC()
<000a> bsc_msc.c:271 Attempting to reconnect to the MSC().
<000a> bsc_msc.c:171 Attempting to connect MSC() at 192.168.100.11:6666
<000a> bsc_msc.c:211 MSC() Connection in progress
<000a> bsc_msc.c:67 MSC() Connection timeout.
<000a> osmo_bsc_msc.c:391 Lost MSC connection. Freing stuff.

We used the config files from the "doc/examples” folder.

We also tried to change the IP address from the local IP and 127.0.0.1 but still the same issue.

I’m not sure if my osmo-msc and osmo-bsc is out-dated but we also tried to get an updated version of both osmo-msc and osmo-bsc. Still we were unable to install it correctly. We have the following error:

Errors:
osmo-msc:
configure: error: Package requirements (libosmo-mgcp-client >= 1.0.0) were not met:

No package 'libosmo-mgcp-client’ found

osmo-bsc:
configure: error: Package requirements (libosmo-legacy-mgcp >= 0.0.1) were not met:

No package 'libosmo-legacy-mgcp' found

I’m checking what package to install but unfortunately, those package requirements is unavailable from the nightly-build and from the git repo.

Best Regard,

Ron Menez
ron.menez at entropysolution.com<mailto:ron.menez at entropysolution.com>



On Sep 17, 2017, at 10:06 PM, Harald Welte <laforge at gnumonks.org<mailto:laforge at gnumonks.org>> wrote:

On Sun, Sep 17, 2017 at 01:45:26PM +0000, Ron wrote:
We’ll be trying to install osmo-stp too to integrate both osmo-bsc and osmo-msc.

FYI: It's part of the libosmo-sccp.git repository.  It also contains an example config
file.  If you start all three programs on the same machine with the
included example program files, they should find each other.

Documentation is still not produced yet.  This new "post NITB"
architecture is too recent.  It's basically the "osmocom bleeding edge"
and it will take another couple of weeks (expected) until there's the
corresponding user manuals.

After manuals have been created and all related wiki pages
updated/created, we will officially "deprecate" OsmoNITB development,
which means that new patches will have to be first merged to
OsmoBSC/OsmoMSC, before they can be back-ported to OsmoNITB.  We'll also
likely only accept bug fixes for legacy OsmoNITB at that point, while
new features must go to OsmoBSC+OsmoMSC.

Regards,
Harald

--
- Harald Welte <laforge at gnumonks.org<mailto:laforge at gnumonks.org>>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                 (ETSI EN 300 175-7 Ch. A6)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20170918/281b4e62/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmo-stp.cfg
Type: application/octet-stream
Size: 444 bytes
Desc: osmo-stp.cfg
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20170918/281b4e62/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmo-bsc.cfg
Type: application/octet-stream
Size: 2250 bytes
Desc: osmo-bsc.cfg
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20170918/281b4e62/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmo-msc.cfg
Type: application/octet-stream
Size: 325 bytes
Desc: osmo-msc.cfg
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20170918/281b4e62/attachment-0002.obj>