Phuong Nguyen wrote:
Well, specifically, one of my question is about the fetchurl.
As far as I understand, the steps of sending an MMS with MBuni (mmssend) and
Kannel is as follow:
1. mmssend -f [EMAIL PROTECTED] -t +41xxx -m test.mms
2. Mbuni decodes the test.mms, gets some header info and compose an WAP push
notification, sends the notification
via Kannel (in my case, connected with a Nokia 7110 mobile phone), something
like
this:
http://localhost:13013/cgi-bin/sendsms?username=aaa&password=aaa&text=%01%06%03%BE%AF%84%8C%82%98a-qf1134725961.1.x92374%40%00%8D....
Simply speak, the notificaiton says "There is an MMS in the url:
http://someserver.com/[EMAIL PROTECTED]/wx6"
the mobile will do an WAP/HTTP request to get the mms file.
Firstly, I though there might be some firewall problem or some thing wrong
with the fetch url, so I code a fixed
fetch url (change the code of: mms_makefetchurl()) to a server that is
visible to my mobile browser
(i.e: I could open the mobile browser and get the file:
www.myserver.com/test.mms; of course the mobile browser will complain that
unknow content type; but the point is that the link is accessible and is not
blocked by firewall or by the telcom provider)
3. However, when I received the notification and tried "received MMS", the
mobile showed that it connected to the MMS gateway of the provider,
getting the MMS but then give the error "Transmision error".
now, you can do it that way... it's the MMSC profile limitation.
When you access the .mms file directly via the WAP mobile browser you use the
general WAP profile on the phone, which will allow you contacting actually any
HTTP server and hence also any content-types. But the browser does not know
about the mms mime-type and that there is actually an application living besides
it that could "handle" it.
Now, when you send the MMS indication via Kannel, what happens is the following:
* your phone receives the MMS notification via WAP Push (hence SMS bearer)
* you say "yes, download"
* now the phone will use the _MMSC_ config profile of the phone to access the
MMS URL that is specified in the notification.
* and here we break, since telcos setup that MMSC profile architecture in this
way:
* APN is dedicated to MMSC, due to non-charging GPRS traffic
* the APN allows you only to make HTTP traffic or WAP traffic via the own
machnines of telco
* that's why you can't "grap" the MMS from your own HTTP "MMSC" server ;))
I think the idea is so simple that the WAP gateway of the telcom provider
will get the mms via HTTP request and pass it back to my mobile phone.
nop, because while your phone polls for the MMS it will use the MMSC config
profile of the phone and that's a dedicated WAP gateway allowing only HTTP
traffic to their own MMSC.
But I could not see what exactly the mobile phone did when I press "receive
MMS".
So my question is that: The server that public the mms file is only a normal
webserver or it should know some MMS related protocols (like MM7) ?
nop, it would be enough to be a plain HTTP server... the problem is IP
firewalling at telcos side for the whole MMSC access architecture. If you could
use the WAP GW of the MMSC profile to reach your own HTTP server, you would be
able to download the message, even, while ACK'ing towards the MMSC (your HTTP
server) wouldn't work, but the phone may silently discard it.
(the reason is that I don't have the access right to install mbuni on a
public machine, that why I changed the fetchurl to a normal public
webserver.
now, you need a GPRS APN to get to mbuni... that's the more generic problem ;)
However, if the server that host the mms files should also speak MMS
protocols then I have to find a way to install mbuni on that machine)
nop... you can't simply download .mms files. Not without re-configuring the
polling device, hence the receiving phone. You must let the user switch from the
restrictive MMSC config profile for MMS sending/receiving to a more relaxed setup.
Hope I clearified the situation. If you need more assistance, contact me.
Stipe
mailto:stolj_{at}_wapme-group.de
-------------------------------------------------------------------
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
-------------------------------------------------------------------
_______________________________________________
Users mailing list
[email protected]
http://mbuni.org/mailman/listinfo/users_mbuni.org
