This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Andrew Back andrew at carrierdetect.comHi Harald, On 16/06/18 15:58, Harald Welte wrote: > Hi Andrew, > > On Fri, Jun 15, 2018 at 05:27:12PM +0100, Andrew Back wrote: >> I've had success with running a NITB based on the new architecture fine >> when everything is on one host. However, I'd now like to split this >> across multiple hosts. > > that should be no problem whatsoever and is actually what we had originally > during development before trying to make it easy for people who run everything > on one host. > > Also, please note that all our automatic integration / functional test suites > run each service in a separate docker container, each on its own IP address. > > See e.g. http://git.osmocom.org/docker-playground/tree/ttcn3-bsc-test/osmo-bsc.cfg > for the osmo-bsc.cfg we use in this setup. Many thanks, the osmo-bsc and osmo-msc configs helped and I now have handsets registered and can send/receive SMS. However, when I make a voice call it fails and on the osmo-mgw for osmo-msc, I see in the logs: Jun 18 16:28:47 cc4 osmo-mgw[507]: #033[0;m<0011> mgcp_msg.c:208 Not able to find a free endpoint Jun 18 16:28:47 cc4 osmo-mgw[507]: #033[0;m<0011> mgcp_msg.c:322 Unable to find Endpoint `rtpbridge/*@mgw' Jun 18 16:28:47 cc4 osmo-mgw[507]: #033[0;m<0011> mgcp_protocol.c:329 CRCX 5: failed to find the endpoint There are two separate instances of osmo-mgw, each running on a dedicated host, with minimal configs as per the NITB instructions, but using standard port numbers for both since there is no conflict. Regards, Andrew