osmo-bsc with remote osmo-stp.

[Andrew Back]

On 18/06/18 19:29, Andrew Back wrote:
> Hi 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.

Just to note that I now have voice calls working using the osmo-mgw
configs that Pau previously shared via the list. Thanks for your help
and to all who have contributed to the stack — it's exciting to be using
the new post-NITB architecture for the first time!

Regards,

Andrew