OpenBSC and MMS

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/.

Harald Welte laforge at gnumonks.org
Tue Aug 16 09:02:25 UTC 2011


Hi Gus and others,

On Mon, Aug 15, 2011 at 11:54:55AM -0700, Gus Bourg wrote:

> So in order to support MO Originated MMS the following need to happen:
> 1) OpenGGSN needs to send RADIUS
> 2) An HTTP Proxy that appends the MSISDN as an HTTP Request Header needs to
> be had

Well, I'm not sure if it absolutely has to be radius based.  Of course,
it would be industry standard.  But I guess a quicker/simpler solution
could be invented, where the GGSN directly sends a simple "Source IP,
MSISDN, IMSI" tuple to the proxy.

> There are opensource PPGs available (See: Kannel).  Where the challenge is,
> is that OpenBSC does not have an SMPP Interface today (at least not
> osmo-nitb).

I don't think we want to add this to osmo-nitb.  Rather, we want to
externalize the entire SMS processing from the osmo-nitb process.  That
external process could then be interfaced using SMPP or other SMS
related protocols like EMI/UCP.

Regards,
	Harald
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)




More information about the OpenBSC mailing list