FW: OpenBSC on 3rd party MSC

Hello everyone, I am still not be able to figure out how to configure the A interface on the OsmoBSC side to talk to MSC, I will really appreciated if someone could share a similar configuration. Or if someone could point me to the right document, I looked through the OsmoBSC user manual(http://ftp.osmocom.org/docs/latest/osmobsc-usermanual.pdf) and could not find the A interfaces config section. Thanks, Weiqi -----Original Message----- From: wyao(a)corrections.com <wyao(a)corrections.com> Sent: Tuesday, April 16, 2019 12:02 PM To: 'Harald Welte' <laforge(a)gnumonks.org> Cc: OpenBSC(a)lists.osmocom.org Subject: RE: OpenBSC on 3rd party MSC Thanks Harald for your reply, Looks like the issue is the connection between OsmoBSC and my MSC. I checked again on my MSC side, looks like it interfaces with softBSC on AoIP, connect to BSC port 2427 and 5000. So basically it just require a softBSC IP address to be able to connect. I found an example cfg called osmo-bsc-mgcp.cfg under the OpenBSC folder, but I have no clue if this is the right one to modify. I will appreciate if you can provide some example BSC configuration like this. Also, Should I still keep the OsmoSTP? Thanks again! Regards, Weiqi -----Original Message----- From: Harald Welte <laforge(a)gnumonks.org> Sent: Saturday, April 13, 2019 5:51 AM To: wyao(a)corrections.com Cc: OpenBSC(a)lists.osmocom.org Subject: Re: OpenBSC on 3rd party MSC Hi Weiqi, On Thu, Apr 11, 2019 at 04:00:08PM -0400, wyao(a)corrections.com wrote: This is correct. However, the terminology is a bit messed-up. So it's best to not use OpenBSC anymore but alsways call it OsmoBSC. sidenote: You will have to add osmo-mgw for handling voice calls later on, but that is irrelevant until you get the signalling plane up and running. Your SS7 routing seems to be misconfigured. The STP receives SCCP from OsmoBSC, but there's no (currently active/working) route for the MSC. Hence the message cannot be routed and is discarded. RESET message... The BSC is trying to send a BSSMAP RESET to the MSC, but there's no response. It's a SS7 routing / SIGTRAN configuration issue. You need to make sure the osmo-stp and osmo-bsc SS7 related configuration exactly matches the configuration on the MSC side. Also, depending on your SIGTRAN network setup, you may not even need osmo-stp. That would be the case e.g. if the MSC or an existing STP in your core network would already provide a M3UA SGW functionality to which the AS/ASP of OsmoBSC can connect to. It's really not possible to give you an easy answer without fully understanding your core networks SS7/SIGTRAN configuration, routing, addresses, point codes, etc. SIGTRAN and SS7 are rather complex protocol stacks themselves. There's little we can do on the Osmocom side to avoid that. We can just provide all the possible settings/options so you can configure it to match your network topology. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)