Dear all Many thanks again for your help. We try to configure ourselves Osmocom & Ericsson nodes, and we'll ask you some assistance if needed.
Best regards Jean-Marc HEYRENDT Orange Labs -----Message d'origine----- De : Neels Hofmeyr <[email protected]> Envoyé : jeudi 30 novembre 2023 15:46 À : HEYRENDT Jean Marc Ext DSCS/DSEC <[email protected]> Cc : [email protected] Objet : Re: Questions on OSMOCOM & real nodes integration ---------------------------------------------------------------------------- -------------------------------- CAUTION : this email originated from outside of the organisation. Do not click links, open attachments or answer unless you recognize the sender and know the content is safe. ATTENTION : Ce courriel provient de l'extérieur de l'organisation. Ne cliquez pas sur les liens, n'ouvrez pas les pièces jointes, ne répondez pas si vous ne reconnaissez pas l'expéditeur et si vous ne savez pas si le contenu est sûr. ---------------------------------------------------------------------------- -------------------------------- On Thu, Nov 30, 2023 at 09:17:58AM +0000, [email protected] wrote: > if we look to the schema, do we need an Osmocom-mgw ? We presume Yes OsmoBSC requires a co-located MGW. So far all of our users that we know of use osmo-mgw for that. The MGCP protocol is standardized, so it would be interesting to interface with a third party MGW and see what happens. > If Yes, Is it possible to just have one Osmocom-mgw hosted on the > Osmocom-bsc ? Yes of course > In this case, There will be RTP traffic between Osmocom-bts and > Osmocom-mgw (hosted on Osmocom-bsc) And there will be RTP traffic > between Osmocom-mgw (hosted on Osmocom-bsc) and mgw Ericsson. > And there will be MGCP traffic between Osmocom-mgw (hosted on > Osmocom-bsc) and Osmocom-bsc. Yes, the reason why Osmocom is divided in so many components is that you may interface with third party components at "any" edge. The scenario you describe above is what some of our users do: OsmoBSC is responsible for the BSS "sphere", including the BSC co-located MGW. OsmoBSC talks 3GPP standardized A-interface towards an Ericsson MSC. OsmoBSC does not interact with or even needs to know anything about the MSC's MGW setup, it only sends the call leg's RTP to the RTP address:port that the MSC indicated in the BSSAP Assignment Command. It does not matter what component/what brand of MGW that RTP address:port belongs to, as far as the BSC is concerned. Of course the hard part is configuring all the details correctly. Sometimes we also need to resolve a customer's CN's specific peculiarities by implementing new features, and occasionally we find and fix bugs in Osmocom that we did not know about yet. So if you have problems with integration that you need assistance with, one option is the dedicated commercial support that is available for Osmocom, for example from [email protected] (my employer). You may also get assistance here on this mailing list, where individual community members invest their own free time free of charge. ~N -- - Neels Hofmeyr <[email protected]> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschäftsführer / Managing Directors: Harald Welte
smime.p7s
Description: S/MIME cryptographic signature
