| MMS wap push |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 21, 2010 ⬆ |
◄ ► |
| Author | Message | ||||
| Kumara New member Username: Dial12345 Post Number: 14 Registered: 07-2009 |
Hi According to my observation , when a wap push is submitted to an SMPP server from MMSC , always 2 messages are submitted . The first message does not contain any data , only the second message contains data. (content URL , destination number etc ... ) So can you please let me know why two messages are used for this. Can this be done by using only one message. A sample packet trace is also attached herewith.
Thanks, Kumara. | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1336 Registered: 08-2008 |
Hi Kumara, You will find that in most commercial MMSC deployments around the world, this is the case. Here is an old thread that discusses configuration parameters that can be used to shorten the MMS notification: http://support.nowsms.com/discus/messages/1/641.html There is also a summary of tips in the following article: http://www.nowsms.com/support/bulletins/tb-nowsms-010.htm I'll go ahead and post the summary of configuration recommendations for shortening the MMS notification from the above article: 1. Use the shortest possible host name (in number of characters) for the "Local Host Name or IP Address" setting of the MMSC. This host name must be included in the every MMS Notification that is generated by the MMSC. Every byte saved in the host name saves a byte in the size of the resulting notification messages. 2. If possible, use Port 80 as the "HTTP Port" for the MMSC. If a port other than port 80 is used, it must be appended to the host name when generating the URL. 3. Edit MMSC.INI, and under the [MMSC] header, add CompactMMSURL=Yes. This setting shortens the length of the dynamic path that is generated when sending MMS messages and will save a few bytes in every MMS notification with no other effect. 4. Edit MMSC.INI, and under the [MMSC] header, add MMSNotificationNoSubject=Yes. By default, NowSMS will include the message subject in the MMS Notification message. Having the subject present can help someone who has a mobile phone configured for manual message download to determine whether or not they want to download the message. However, the specification does not require the subject to be present in the notification, and omitting it can prevent long MMS notifications. 5. Edit MMSC.INI, and under the [MMSC] header, add Nokia3510Compatible=No. This setting reduces the size of the MMS notification by approximately 30 bytes, at the expense of compatibility with early model GSM MMS phones (specifically the original Nokia 3510 and Panasonic GD87). These phones did not understand the short form of MMS content type encoding in the MMS header, and required the long form. The MMS specifications do require that the handsets support the short form of this encoding, and technically these early model handsets were non-conformant. While GSM operators may want to maintain compatibility with these early model handsets, this should not be a consideration in CDMA environments. -- Des NowSMS Support | ||||
MMS wap push
