Sporadic corrupt MMS

Sporadic corrupt MMS SearchSearch
Author Message
Oliver Evans
New member
Username: Oli

Post Number: 1
Registered: 09-2006
Posted on Tuesday, September 19, 2006 - 06:46 pm:   

We are testing out the Now SMS 2006 MMSC functionality, we have set it up to use a K800i as a gsm modem and our application server is submitting MMS send requests via MM7 as a VASP.

Our configuration works, but we regularly see corrupt MMS's being created, showing up as 1k in size in the MMSCDATA dir.

Has anyone seen any behaviour like this, it sounds similar to this:

http://support.nowsms.com/discus/messages/12/2786.h tml

but the order of our attachments appears to be correct.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6548
Registered: 10-2002
Posted on Tuesday, September 19, 2006 - 09:51 pm:   

I'd be curious to see one of these corrupt MMS messages to see if it provides any clue.

Better yet, if you can run with the MMSCDEBUG.LOG enabled (it will hurt performance, but if you're sending out via a GSM modem, not significantly), when you encounter one of these corrupt messages, we could try matching it up with the MM7 submission in the MMSCDEBUG.LOG. It may be that there is some formatting issue with the particular MM7 submission that is not being understood correctly and resulting in such a message.

-bn
Oliver Evans
New member
Username: Oli

Post Number: 2
Registered: 09-2006
Posted on Wednesday, September 20, 2006 - 11:43 am:   

Thanks for the prompt reply Bruce, heres the information requested.

application/zipMMS Info
MMSCDEBUG.new.zip (2656.3 k)


Look forward to hearing from you.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6552
Registered: 10-2002
Posted on Wednesday, September 20, 2006 - 04:39 pm:   

Hi Oliver,

There is a MIME boundary problem in the MM7 submission that results in a corrupt message.

If you take a closer look at the MM7 submission, you'll find that the same MIME boundary string is used for both the inner and the outer parts of the message.

Both are using boundary="LhcydYXUTseI5dg27Gf2rjxouZkLvBIrwxGrZYiu"

And I believe this is what is causing the confusion.

These boundary strings need to be unique.

-bn
Oliver Evans
New member
Username: Oli

Post Number: 3
Registered: 09-2006
Posted on Wednesday, September 20, 2006 - 05:34 pm:   

Cheers Bryce, I see how that would cause a problem. Thanks for your time.