| Question of Sending MMS |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 09, 2011 ⬆ |
◄ ► |
| Author | Message | ||||
| Johnny New member Username: Johny Post Number: 10 Registered: 02-2009 |
Hi... I sent MMS message in the “Send MMS Message ” and received MMS message. However, When I checked the MMS log, something values were added in the received logs. "1" is sending log and "2" is received log. "1" sending log  "2" received log  Why some values are added when I received the mms message? I attached following contents when I sending mms message
| ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2683 Registered: 08-2008 |
Hi Johnny, What was the full path through which the message travelled? How exactly are you viewing it in the received log, since it would normally be decoded before presented to you? I just tried a simple test sending the message, and didn't notice any extra bytes at the end. When you use the "Send MMS Message" form, NowSMS will make some modifications to the MMS header, including changing sender/recipient/subject based upon what was entered in the form, changing the message type, inserting mandatory headers, but it does not modify the content. That said, I would not recommend constructing a binary MMS message for most users, unless they have a very specific testing scenario. (And if you do have a specific testing scenario, I would recommend putting the MMS content on a separate web server and using the "Send MMS Notification" function instead, as you would have no MMS header modifications.) The reasons that I don't recommend creating a binary MMS message directly are: 1.) MM4 and MM7 do not use the binary MMS message format, so NowSMS is going to have to decode and convert it to another format. 2.) You are at the mercy of the binary MMS encoder. In particular, this message doesn't include SMIL, which is going to cause problems with presentation on some handsets. (You should also note that OMA DRM is not supported on the iPhone.) -- Des NowSMS Support | ||||
| Johnny New member Username: Johny Post Number: 11 Registered: 02-2009 |
I run the packet capture program such as wireshark. I sent the mms in the “Send MMS Message” When the message was received in the mobile phone, I captured the logs. The log was captured, before mms message pass through the our wap gateway. So, I think that message will send with extra values to the now sms. Did you send same contents? At this time, can’t you check the extra log values? If the way to capture the log is wrong, please let me konw | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2692 Registered: 08-2008 |
Hi Johnny, My question is ... what is the path that the MMS message took to get from NowSMS to the receiving mobile phone? Was it routed through an operator MMSC? It is very common for MMS messages to go through transformations as they are routed and processed by operator MMSCs. -- Des NowSMS Support | ||||
| Johnny New member Username: Johny Post Number: 12 Registered: 02-2009 |
My question is ... what is the path that the MMS message took to get from NowSMS to the receiving mobile phone? ->The message are send and receive through the now mmsc. This is simple receiving sequence. Now MMSC ----> Wap GW ----> Handset I captured the log between Now MMSC and Wap Gateway. Was it routed through an operator MMSC? -> No. We have two MMSC. One is Java MMSC, the other is Now MMSC. However we don’t route from Now MMSC to Java MMSC. When I send the mms using the now sms, the message is sent and received to the Now MMSC. When I attach the another contents such as image files and received it I can't check extra byte. When AMR audio DRM.MMS contents is attached, extra byte is occured. AMR audio DRM.MMS contents type is DRM type. | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2696 Registered: 08-2008 |
Hi Johnny, Ok. This is a bug when using the "Send MMS Message" form to send a pre-compiled MMS message. If it is possible for you to insert a "Date:" header into the pre-compiled MMS message, this will avoid the problem. ("Date:" is an optional field, but the bug occurs when NowSMS is inserting a "Date:" header.) Or, if your "To:" recipient list in the pre-compiled MMS message (in this case it is +10000000000) matches the recipient on the form, then this should also avoid any problem. Alternatively, instead of sending a pre-compiled MMS, specify the DRM file as one of the MMS message components directly on the "Send MMS Message" form, and let NowSMS build the binary MMS envelope. We are working on a fix, however, hopefully one of these work-arounds will resolve your immediate problem. -- Des NowSMS Support | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2743 Registered: 08-2008 |
Hi Johnny, A follow-up. There was an updated posted yesterday that addresses this issue without any work-arounds. http://www.nowsms.com/download/nowsms20101214.zip -- Des NowSMS Support | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2748 Registered: 08-2008 |
Follow-up. One of the DLLs in the update mentioned above was not updated properly for the install. This resulted in unnecessary retries for some SMPP configurations. The link above has been replaced with an updated version of the install and should now identify itself as version 2010.12.15. If you previously downloaded from this link, it has been replaced with http://www.nowsms.com/download/nowsms20101215.zip -- Des NowSMS Support | ||||
