Mbuni: Open Source MMS Gateway
Please see ETSI standard TS 123 140 (available from 3GPP website)
MM1: MMS Relay/Server - MMS User Agent
Tested successfully with at least the following
MMS clients/handsets: Nokia 3650, 6600; Samsung X100, E700; SonyEricsson T300,
600 series; I-mate (PocketPC); OpenWave SDK emulator
- MMS Send to/Receive from client/handset: Fully implemented
- Delivery/read reports: Fully implemented
- MMS over HTTP: Some phones (such as Nokia 6600) transmit MMS over
HTTP (skipping WAP stack). Because Mbuni is de-coupled from WAP gateway,
works well in this case.
MM3: MMS Relay/Server - External Servers
MMS-to-email passes the Yahoo! Mail test, as well as various email
readers (Apple Mail, Outlook, etc)
- MMS-to-email and Email-to-MMS fully implemented
- No generalised interface provided beyond the above at this stage
MM4: Interworking of different MMS Gateways
- Inter-gateway message exchange implemented via SMTP
- Number prefix-based routing as default
- Plug-in interface for generalised routing
MM6: MMS Relay/Server - MMS User Database
- Can be configured to communicate with external user
database via a set of scripts specified in config file
- Control of subscriber provisioning status, notification status
supported through script
- Generalised mechanism for determining what numbers (MSISDNs) are
local and which ones foreign, based on plug-in
MM7: MMS Relay/Server - MMS VAS Applications
- SOAP and EAIF implementation.
MM8: MMS Relay/Server - Billing System
Reference points MM2 is irrelevant as the gateway acts as
nothing is planned for reference point MM5.
- Supports billing and CDR generation through generic interface to
a billing API (dynamically loadable module)
Support for persistent message store
(MMBox as defined in v1.2 of the OMA MMS spec.) is implemented.
As of version 1.1.0, Mbuni also acts as MMS VAS Applications Gateway (i.e.
an application talking to the MMSC on the MM7 interface)