RE: Things I learned about MMS clients (so far)

Jörg Pommnitz <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <[email protected]>
The final mystery is solved. My MMS client works with Vodafone D2
in Germany. It turned out, that the WAP gateway did not know
about the binary encoding for "application/vnd.wap.mms-message".

I'm now able to send MMS messages with all four German network
operators.

Thanks to everybody who helped me on and off the list!

Kind regards
  Jörg

-----Ursprüngliche Nachricht-----
Von: Jörg Pommnitz 
Gesendet: Freitag, 30. Januar 2004 17:38
An: Kannel-Devel (E-Mail)
Betreff: Things I learned about MMS clients (so far)


Some obstacles I overcame and that are not readily
obvious from the standards:

1. The Vodafone MMS WAP gateway dislikes fragmented IP packets.
   They obviously get dropped somewhere.
   Conclusion: make sure your SAR segment size is smaller then 
               the GPRS SDU size. 1000 Bytes works for me.

2. The E-Plus MMSC is picky. It does not accept anything but
   application/vnd.wap.multipart.mixed or .related as MMS payload.

3. The E-Plus MMS WAP gateway is very picky. If you send a POST
   request that exceeds the default 1400 Byte SDU size, it will
   reject it. You have to announce larger SDUs with the
   WSP Server-SDU-Size capability field.

Hope this helps others.

Kind regards
  Jörg
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.