| The nowmms transform of mms to wap page encapsulation? |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
the nowmms transform of mms to wap page encapsulation? | |||
| Bryce Norwood - NowSMS Support |
Hi, Did you have a specific question about it? In the v4.20 release of the Now SMS/MMS Gateway (the version that you download if you download the trial version from our web site), we introduced a "multimedia WAP push" function. The idea was that you could submit a message with content objects to the gateway using an approach similar to the way that you would submit an MMS message. However, the objects would be packaged and delivered as a WAP push to the WAP browser instead of as an MMS message. There were multiple purposes for this functionality. One purpose was that some types of content (like Java files) are better received through a WAP browser than an MMS client. The other purpose was that with quite a few operators having blocked MMS delivery from external MMSCs, we needed a good alternative option for multimedia message delivery. In the v5.0 release of the Now SMS/MMS Gateway, which is currently in beta testing (http://www.nowsms.com/beta5), we expanded some upon this concept. In addition to supporting direct MMS delivery via its built-in MMSC, the v5.0 release also supports connections to external MMSCs. Based upon recipient address masks, you can define different routings for how the gateway routes an MMS message. It can perform direct MMS delivery via the built-in MMSC; external routing via MM7, MM4, EAIF or MM1 (including MM1 over a GPRS modem); or it can convert the MMS message to a multimedia WAP push message for delivery. (Note: At this time, in this MMS to multimedia WAP push conversion, we don't make any attempt to handle SMIL, only the individual objects are converted.) -bn | |||
