| Problem with messages sent by MM4 from LG Chocolate to Nokia 6101 |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 05, 2007 ⬆ |
◄ ► |
| Author | Message | |||||
| Joseph Smith New member Username: Falangjoe Post Number: 11 Registered: 08-2006 |
Software Version v2006.10.16 Customer: Union Telephone I am testing MM4 with Verizon by way of Versign. They were using an LG Chocolate to test with. I was using a Nokia 6101. Sending to the Chocolate was fine. When a video or sound file was sent, there was no problem. When a picture was sent, the message would arrive blank on the Nokia 6101. I changed to a LG 1400i and the pictures would show up. They change to a Motorola Q and the Nokia 6101 could receive everything. Also, I have seen this behavior while testing with another carrier. They were sending from an Audiovox phone and the same Nokia 6101 was receiving. I had the same type of problem with two Now WIreless MMSC gateways connected, and Bryce gave me a fix for that. Although, on our production gateway, I did not use this fix. I have the following logs. Verizon to Union Telephone LGChocolateToNokia6101_2403932803_to_3074779951 and ????? to Union Telephone AudioboxToNokia6101_2146500025_To_3077470341 Thanks, Joseph
| |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6859 Registered: 10-2002 |
Hi Joseph, What version are you running on the production gateway? Is it prior to 2006.09.12? I'm trying to recall exactly what the problem was with 2 NowSMS MMSCs connected via MM4 that could sometimes trigger images not to appear. I seem to recall it being the way that our MM4 receiver was handling the "content-id:" header, and it was confusing the content adaptation logic. As I review this, I'm suspicious that while the previous patch addressed this issue specifically for a problem that would occur NowSMS to NowSMS, that there still is a potential problem related to MM4 and the "Content-id:" header, independent of content adaptation (content adaptation is definitely not a factor in your example). I'm going to put together a test scenario to see if my potential problem theory is real, or if I'm not seeing something correctly. While I look at this, it would help if you could send me one of the problem raw ".mms" files ... such as C:\PROGRA~1\NowSMS\MMSCDATA\20061201/13/3D7C6223.mms referenced in one of the logs. If that file is no longer present, you might need to repeat the test to capture one of these files. I'd suggest e-mailing it directly to nowsms@now.co.uk, but put "Attention: Bryce" in the subject line. -bn | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6860 Registered: 10-2002 |
Never mind the question about the version, I see you mentioned it at the top of your message. | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6861 Registered: 10-2002 |
Confirmed. I've manually created some MM4 message transmissions and recreated a problem that I suspect is what you are experiencing. There is a problem with "Content-ID:" headers getting lost in the translation from MM4 to MM1. This causes problems for SMIL files that reference content by the "Content-ID:" header instead of by filename. The end result is that the handset receives the image, but doesn't display it because it is not part of the SMIL presentation. We've got a fix (it was a rather simple issue), but it needs to go through some more testing before I post it. -bn | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6870 Registered: 10-2002 |
Joseph, I've posted an update that addresses this issue with the MM4 receiver losing the "Content-ID:" header in the translation to MM1 format. http://www.nowsms.com/download/newpatch.zip -bn | |||||
| Joseph Smith New member Username: Falangjoe Post Number: 12 Registered: 08-2006 |
Thanks Bryce | |||||
| Joseph Smith New member Username: Falangjoe Post Number: 13 Registered: 08-2006 |
Bryce, I updated are MMSC. When testing MM4 with another carrier, I saw some new problems. They were supposed to have sent a picture + sound + text message, but the sound could not be played. Also, they sent a video message, but that could not be played. Although the picture could be viewed on the Nokia 6101 unlike before. Can you take a look at these messages? I was doing all receiving with a Nokia 6101. Thanks, Joseph
| |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6873 Registered: 10-2002 |
Joseph, There's definitely no video in that first message, although the SMIL file does reference a video file. The question would be whether or not there was when the message originally came in via MM4. The MM4/SMTP parser in the MMSC does look at the content types for each component and will skip over any content parts where the content type is not listed in MMSCTYPE.INI. (Side note: We should consider changing this behaviour so that it only applies to messages submitted via generic SMTP, not messages submitted via MM4.) video/3gpp is the MIME type that is generally used for MMS compatible video. You might want to try retesting, and look at the MMSCDEBUG.LOG. Is there an entry that says something like this: ParseAttachmentsFromInboundMessage: Skipping filename, content type type/subtype If so, you could add the type/subtype and extension to MMSCTYPE.INI. But I would also like to know what the type/subtype is. In the second example, the audio is also missing. So I'd ask the same question about it. -bn | |||||
LG Chocolate
Video Message?
