Re: SE T610 MMS notifications - FYI
Stipe Tolj <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Organization | Wapme Systems AG |
| Message-ID | <[email protected]> |
Paul Keogh wrote: > > Somebody had a problem recently about sending MMS notifications > to the SE T610. > > I've just found an item on the SE developer site that says WAP pushes > (ie. MMS notifications) are limited to 120 bytes for this and other > SE devices. I've tested it and its true :-(. hip hip hurey. That's why we have standards and specs. So other people can say: no, we do it the other way ;) > See http://www.sonyericsson.com/developer/viewSolution.do?id=5519 > > This seems very wrong to me ! > > How the $£^&% are you supposed to know what device you're pushing the > notification out to ? you don't! -- at least if you haven't registered a device by type previously via it's associated MSISDN. But this is utopical, and also breaks the idea of SIM/MSISDN <-> device independency. > This is the first MMS device I've encountered with this limitation. > > Anyone from SE on this list wish to defend this design decision ? yep, heads up please. Stipe mailto:[email protected] ------------------------------------------------------------------- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf, NRW, Germany phone: +49.211.74845.0 fax: +49.211.74845.299 mailto:[email protected] http://www.wapme-systems.de/ ------------------------------------------------------------------- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.2.2 (Cygwin) mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2 nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H g2HyLAEKQIp30Q== =aYCI -----END PGP PUBLIC KEY BLOCK-----