think about contributions.
On Mon, 20 Dec 2004 14:31:41 +0100, Søren Hansen [EMAIL PROTECTED] wrote:
ons, 17 11 2004 kl. 15:08 +0200, skrev Dziugas Baltrunas:
several months have already passed since Søren Hansen started or
renewed discussion about mmsbox issues and implementation
(http
ons, 17 11 2004 kl. 15:08 +0200, skrev Dziugas Baltrunas:
several months have already passed since Søren Hansen started or
renewed discussion about mmsbox issues and implementation
(http://www.mail-archive.com/devel@kannel.org/msg03298.html).
It would be interesting to know how far Søren
Hi list,
several months have already passed since Søren Hansen started or
renewed discussion about mmsbox issues and implementation
(http://www.mail-archive.com/devel@kannel.org/msg03298.html).
It would be interesting to know how far Søren is with his
implementation as well as Stipe's approach
it a bit more thought, and this is what I'm thinking:
mmsbox receives the MMS submission from phone
mmsbox does magic to figure out MSISDN of submitter. (TODO)
binary encoded MMS is sent along with msisdn to bearerbox.
bearerbox relays MMS to...
[snip]
...sends decoded MMS to smtp server.
I'm going
ons, 2004-07-14 kl. 14:08 skrev Søren Hansen:
*: I'm very keen on doing this, but as I work as a programmer for at
company that develops and hosts mobile solutions, I should ask my boss
for permission to develop this mmsbox for Kannel.
Well, what do you know? He took the time to respond to my
Hansen
Cc: [EMAIL PROTECTED]
Betreff: Re: mmsbox
Søren Hansen schrieb:
ons, 2004-07-14 kl. 14:08 skrev Søren Hansen:
*: I'm very keen on doing this, but as I work as a programmer for at
company that develops and hosts mobile solutions, I should ask my boss
for permission to develop
Forgot another _crucial_ thing!
How does the phone get to your MMSC HTTP server (mmsbox). Via public
(GPRS) or private (dial-in) IP connectivity?
Why I'm asking this is simple. Phones do _not_ include their own
MSISDN into the From: header that is in the MMS Encap PDUs. The MMS
clients
Pommnitz, Jörg schrieb:
I think MMS will require a working SAR implementation. MMS messages
can easily exceed 64KB. So, some work on the WAP side of things will
be necessary.
SAR is available in Kannel. The only thing not yet present is ESAR
(extended SAR) for messages beyond 256KB.
Our
is that the content adaptation task can't be separated
from MMSC as it's the only entity receiving the User Agent Profile
(UAProf) or at least Accept headers. Shall we think about the adapter
submodule of the mmsbox?
regards,
Dziugas Baltrunas
is that the content adaptation task can't be separated
from MMSC as it's the only entity receiving the User Agent Profile
(UAProf) or at least Accept headers. Shall we think about the adapter
submodule of the mmsbox?
what do you mean with adapter submodule? A module that transcodes
the MMS on-the-fly
I'm considering writing an mmsbox(*), but until I go ahead and code it,
I need to get a few things straight about the architecture of Kannel,
and how an mmsbox would fit into it. Here' what I'm thinking about
doing:
Mobile phone submits MMS
mmsbox listening for HTTP requests receives MMS from
11 matches
Mail list logo
