From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: Reg. MMS Support in oFono
Date: Tue, 20 Jul 2010 00:16:17 -0700 [thread overview]
Message-ID: <1279610177.4572.53.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTimFG3k_KjmHIjME1z1Si32VMorrrA4crdnSskDn@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]
Hi Satya,
> I have one doubt regarding MMS features.
>
>
> In previous mail list ofono team mention that "MMS is not supported by
> oFono, these belong in a separate daemon". Related link is as follows
> : http://lists.ofono.org/pipermail/ofono/2010-June/002672.html
>
>
> I thought it is ConnMan.
>
>
> But in ConnMan mailing list it is saying that "oFono will export these
> via a Socks5 or HTTP proxy to the MMS application without having
> ConnMan involved". Related link is as
> follows : http://lists.connman.net/pipermail/connman/2010-June/001515.html
>
>
> May I know what is that daemon that supports MMS features (upload /
> download, MMS read receipt indication, Delivery report indication).
this is all true. The MMS application/daemon will talk over a Socks5
proxy to oFono to get access to the MMSC. And will use oFono's D-Bus
interface to get MMS push notifications.
For MMS support we are on purpose trying to avoid using ConnMan and will
handle all TCP connections that the MMS application/daemon needs via a
proxy. This is important to not interfere with the Internet connections.
In general the contexts for MMS are just for MMS only and so we handle
them internally in oFono.
I might look rather complicated and complex right now, but once the
basic pieces are getting merged into oFono, I hope this becomes a lot
clearer.
Regards
Marcel
prev parent reply other threads:[~2010-07-20 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 6:57 Reg. MMS Support in oFono =?unknown-8bit?b?4LC44LCk4LGN4LCvIOCwleCwv+Cwt+Cxi+CwsOCxjQ==?=
2010-07-20 7:14 ` Stefan Schmidt
2010-07-20 7:16 ` Marcel Holtmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1279610177.4572.53.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox