Editing Task:MMS
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
- | The aim of this page is to list potential obstacles and solutions in regards to implementing MMS in Maemo 5 | + | __FORCETOC__ |
+ | |||
+ | == Introduction == | ||
+ | The aim of this page is to list potential obstacles and solutions in regards to implementing MMS in Maemo 5 ”Fremantle” on the N900. | ||
== Use case == | == Use case == | ||
Line 12: | Line 15: | ||
To successfully implement MMS sending and receiving on the N900 the following has to be done: | To successfully implement MMS sending and receiving on the N900 the following has to be done: | ||
- | === | + | === Hooking in to the SMS receiving part and take control when the notification about MMS is received.=== |
- | According to [http://talk.maemo.org/showpost.php?p=319365&postcount=15 this] post by danielwilms the final SDK for Maemo5 should let us do this through Telepathy. | + | According to [http://talk.maemo.org/showpost.php?p=319365&postcount=15 this] post by danielwilms the final SDK for Maemo5 should let us do this through Telepathy. Hopefully. At least a way to handle SMS. |
- | + | ||
- | + | ||
=== Fetch the MMS from the provider.=== | === Fetch the MMS from the provider.=== | ||
Multiple issues with this. | Multiple issues with this. | ||
- | * Fremantle | + | * Does Fremantle currently support adding more than one APN? Someone with a device please confirm. Seems it does not. |
- | + | "On the tested proto unit, connectivity options seem to be unfinished yet and e.g. there are no Internet access point settings other than Wireless LAN so I can't elaborate on the supported options and settings yet. However, even without configurable settings, the N900 automatically recognized my SIM card and set up the right Internet access point by itself." <ref>[http://my-symbian.com/other/preview_n900.php My-Symbian.com PREVIEW]</ref> | |
- | + | "And the point is that right now, you can only define one APN in Maemo5, at least in the release I've got." <ref>[http://talk.maemo.org/showpost.php?p=335857&postcount=22 dart45 @ talk.maemo.org]</ref> | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | * Most operators only allow fetching of MMS when accessing via a specific [http://en.wikipedia.org/wiki/Access_Point_Name APN]. To access this you would have to temporarily suspend your current 3G connection and switch over to this (is this correct? need someone with knowledge on this). On S60 you won't get dropped as long as you are on a 3G connection (on the other hand this is tested with a provider who got the same APN for both Internet and MMS, only diff is different startpage - does this matter?). | |
- | + | ||
- | * | + | * If the user only got access to GPRS the current connection (if in-use) have to to be temporarily suspended while fetching the MMS. Can't this be solved by doing a "Deffered Retrieval" <ref>[http://www.openmobilealliance.org/Technical/release_program/docs/CopyrightClick.aspx?pck=MMS&file=V1_3-20080128-C/OMA-TS-MMS-CTR-V1_3-20080128-C.pdf Figure 7. Page 16]</ref> |
- | + | * Accessing the MMS "server" through a specific connection: iptables tweaking? Discussion at [[http://wiki.maemo.org/Mms_implemention_conversation#Technical Mms_implemention_conversation#Technical]] The following is based on that conversation: | |
- | + | ||
- | * Accessing the MMS "server" through a specific connection: iptables tweaking? Discussion at [[Mms_implemention_conversation#Technical]] | + | |
** The problem here is routing specific data to the specific connection. While this is possible with some clever routes, this does raise the problem with operators having the same gateway for both GPRS and MMS connections, which might lead to a collision (if both they are indeed the same gateway, it should be no problem just getting the MMS over the current connection?). | ** The problem here is routing specific data to the specific connection. While this is possible with some clever routes, this does raise the problem with operators having the same gateway for both GPRS and MMS connections, which might lead to a collision (if both they are indeed the same gateway, it should be no problem just getting the MMS over the current connection?). | ||
** One possibility is to tag the appropiate packets with iptables and then sent to a different routing table. | ** One possibility is to tag the appropiate packets with iptables and then sent to a different routing table. | ||
** To overcome the problem with different gateways on the same subnet one could add a hard dumb route to the specific gateway via route, then set the Internet gateway to a higher priority. e.g. rename 123.123.123.0 -> MMS route via iproute2 NAT. Something like http://lartc.org/howto/lartc.rpdb.multiple-links.html maybe? | ** To overcome the problem with different gateways on the same subnet one could add a hard dumb route to the specific gateway via route, then set the Internet gateway to a higher priority. e.g. rename 123.123.123.0 -> MMS route via iproute2 NAT. Something like http://lartc.org/howto/lartc.rpdb.multiple-links.html maybe? | ||
- | ** Another solution would be a mms-fetcher-daemon running as a specific user (e.g. mmsd) and use iptables to route all these packages to the correct interface. This works around when both the GPRS and the MMSC specified is on the same IP but requires different connections. i.e. "route add 1.2.3.4 ppp:mmc - fails if there is also a server on 1.2.3.4 on ppp:normal" | + | ** Another solution would be a mms-fetcher-daemon running as a specific user (e.g. mmsd) and use iptables to route all these packages to the correct interface. This works around when both the GPRS and the MMSC specified is on the same IP but requires different connections. i.e. "route add 1.2.3.4 ppp:mmc - fails if there is also a server on 1.2.3.4 on ppp:normal" |
** '''At the core of it - whats needed is a separate interface (e.g. ppp0, ppp1 etc) for each APN the user sets up'''. | ** '''At the core of it - whats needed is a separate interface (e.g. ppp0, ppp1 etc) for each APN the user sets up'''. | ||
+ | ** How to hold multiple sessions open? | ||
- | * Applications should be able to request a certain IAP to be activated; thus should the MMS app be able to request the correct APN | + | * Applications should be able to request a certain IAP to be activated; thus should the MMS app be able to request the correct APN. [http://wiki.maemo.org/Mms_implemention_conversation#Higher_level_technical Source] |
- | + | ||
- | + | ||
=== Format the MMS and display it correctly.=== | === Format the MMS and display it correctly.=== | ||
Line 56: | Line 49: | ||
# [http://sourceforge.net/projects/mmslib/ Java] [http://sourceforge.net/projects/freshmeat_messaging-midp/ JavaSE/JavaME] | # [http://sourceforge.net/projects/mmslib/ Java] [http://sourceforge.net/projects/freshmeat_messaging-midp/ JavaSE/JavaME] | ||
# [http://projects.xplico.org/mmsdec.html C] | # [http://projects.xplico.org/mmsdec.html C] | ||
- | |||
# [http://python-mms.sourceforge.net/ Python] | # [http://python-mms.sourceforge.net/ Python] | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
== References == | == References == | ||
- | |||
<references /> | <references /> | ||
- | |||
- | |||
- | |||
- |
Learn more about Contributing to the wiki.