RE: OSMO SMSc functionality

Thanks harald for the detailed response. Unfortunately the testing scenario we want to try is to have a sperate MSC instance from another vendor , hence we cannot use the Osmo MSC . We have already tested the SG interworking between Amarisoft EPC and Osmo MSC,both MO/MT CSFB SMS was working fine. -----Original Message----- From: Harald Welte <laforge(a)gnumonks.org> Sent: Friday, March 22, 2019 2:03 PM To: Alex Alwin Thomas <aathomas(a)fb.com> Cc: openbsc(a)lists.osmocom.org; Saumya Raval <sraval(a)fb.com> Subject: Re: OSMO SMSc functionality Hi Alex, On Fri, Mar 22, 2019 at 06:31:09PM +0000, Alex Alwin Thomas wrote: Yes. No, this is not possible. The OsmoMSC internal SMSC functionality doesn't implement any external/standard interfaces. Unfortuantely not. However, you can of course use the Amarisoft SGs to talk to OsmoMSC SGs and support SMS services this way. You'd need OsmoMSC and OsmoHLR on the Osmocom side. You would not have any interworking with external HLRs. As there is no DIAMETER support in OsmoHLR, you'd have to manually ensure that the same subscriber information (IMSI/K/OPc/...) is present in the Amarisoft HSS and the OsmoHLR. Having a GSUP-to-DIAMETER gateway is on our wishlist, exactly to support scenarios like this: Use some 3rd party vendor EPC for 4G in parallel with the Osmocom stack for 2G/3G, both accessing one shared subscriber database. However, unfortuantely nobody has yet been able to dedicate any resources to this task. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> https://urldefense.proofpoint.com/v2/url?u=http-3A__laforge.gnumonks.org_&a… ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)