| MMS notifitacions |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Edmund Boile |
Hi  First of all, please, forgive me my terrible english  I am using GSM modem with SMSC and see in logs the folowing things: In MMSC log: -------------------------------- 2003-08-28 09:48:19,MMSIN,80.216.21.25,+49xxxxxx,+49xxxxxx,20030828/09/97D427C2,SAR-+49xxxx xx-c3-2-1.req,24171 2003-08-28 09:48:19,MMSIN,80.216.21.25,+49xxxxxx,+49xxxxxx,20030828/09/97D427C2,SAR-+49xxxx xx-c3-2-2.req,24171 2003-08-28 09:49:41,MMSRETRIEVE,80.216.21.25,,+49xxxxxx,20030828/09/97D427C2.MMS,OK,24208 -------------------------------- And in SMSOUT log: -------------------------------- 2003-08-28 09:48:25,SAR-+49xxxxxx-c3-2-1.req,MMS user +49xxxxxx(user),+49xxxxxx,OK -- COM2:,Binary=1;DCS=F5;UDH=0B05040B8423F00003C30201;Data=C306226170706C6963617469 6F6E2F766E642E7761702E6D6D732D6D65737361676500AF848C82983937443432374332008D9089 18802B34383630303431383631312F545950453D504C4D4E009646773A20416C6C6B6C6F64206261 63616E6E6F008A808E025E9088058103093A8083687474703A2F2F38302E34392E323135 2003-08-28 09:48:31,SAR-+49xxxxxx-c3-2-2.req,MMS user +49xxxxxx(user),+49xxxxxx,OK -- COM2:,Binary=1;DCS=F5;UDH=0B05040B8423F00003C30202;Data=2E36383A3434332F32303033 303832382F30392F39374434323743322E4D4D533F69643D253262343836303034313836313100 -------------------------------- This is all abount sending one MMS message. I see, that sending this one MMS takes 2 SMS messages. I am begginer in a MMS protocol stack and transaction flow, and wondering what are those 2 SMS message ? Are they a multiparted (2 parts) MM Notification.ind message sent by the MMS Proxy-Relay (Now SMS MMSC) to the MMS Client (mobile phone) using the WAP PUSH framework ? If yes, i am wondering is it possible to shorten this MM notification that could fit in one (instead of two) SMS messages ? | |||
| Bryce Norwood - NowSMS Support |
Yes, they are essentially an m_notification_ind message encapsulated in a WAP push, and as the content is larger than 140 bytes, when the push gets sent over SMS, it is sent as a concatentated SMS message in 2 parts. It is often possible to get the notification to fit into a single SMS message, but it can be tricky. First, I'll let you in on an undocumented INI file setting. I believe I've mentioned this on the discussion board before, but it is not in the documentation. In the MMSC.INI file, under the [MMSC] section header, add the parameter CompactMMSURL=Yes. This shortens the length of the MMS message URL that the MMSC generates. Also under this same section header, add MMSNotificationNoSubject=Yes, which removes the subject line from being included in the MMS notification. (If the MMS client prompts before download, it will be less friendly without the message having a subject before you download, but that is a small price to pay.) Next, you need the shortest domain name (in number of characters) that you can find, so that it can be used as the "Local Host Name or IP Address" for the gateway. For example, we have in the past used "ihub.com" and "now.ws", which are good short host names for domains that result in very short MMS message URLs. Also, make sure that you are using port 80 for the MMSC, as that will also shorten the message URL. Usually, with a short domain/host name, and those INI file settings, you can get the notification into a single message without any ill effects. There are additional parameters which can also decrease the size of the MMS notification, however these settings should be used with caution as we have observed problems with these settings: MMSNotificationNoSender=Yes This removes the sender from the MMS notification envelope. We have observed that some phones, most notably the SonyEricsson T68i cannot reply to a message where the sender is not included in the notification. I believe some other phones (Sharp GX-1?) will also ignore the message completely. Nokia3510Compatible=No This uses a more compact encoding for the MMS notification ... but we have observed that it causes problems with the original release of the Nokia 3510 ... and we have also observed that the Panasonic GD87 does not understand the notification when this format is used. So in short, I would recommend the following entries in MMSC.INI under the [MMSC] section header: CompactMMSURL=Yes MMSNotificationNoSubject=Yes Then do what you can to shorten the host name of the MMSC to the shortest name (in number of characters) you can use. The other settings can be experimented with, but there are known compatibility problems when they are used. -bn | |||
