MMSC is doing adaptation (only when sending via URL parms)

MMSC is doing adaptation (only when sending via URL parms) SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through October 31, 2007 » MMSC is doing adaptation (only when sending via URL parms) « Previous || Next »
Author Message
Tim
New member
Username: Trsills

Post Number: 1
Registered: 10-2007
Posted on Wednesday, October 10, 2007 - 03:08 pm:   

I'm using a gsm connected phone (n95 via usb) and am able to send mms/sms messages via the web interface no problem (and no apparent file size issues for the mms messages). I have several gif images of varying size 2-12k that I've been testing with. I can send both an sms message and an mms messages with an attachment of 2k via URL parameters. I can also do it via the mms php script. Yet, if I try to do a larger image via URL parameters (say 5k or more), Cingular says that 'one or more of the message components have been deleted by MMS Adaptation. Either the message was too large or the components were unsuitable for your terminal'.

I've tried searching this site for some similiar discussion but couldn't find anything. Can you provide some insight as to what's different between the post crafted by the web interface and when using the URL parameters? I'm following the examples in the pdf support document.

Thanks,



Tim
New member
Username: Trsills

Post Number: 2
Registered: 10-2007
Posted on Friday, October 12, 2007 - 12:53 am:   

Bryce- disregard this post...

I found the source of the error (although pretty wacky results it had created).

thx
Malcolm - Now Support
Moderator
Username: Malcolm

Post Number: 193
Registered: 12-2006
Posted on Thursday, October 18, 2007 - 06:48 pm:   

Hi Tim,

I'd be curious to hear what the source of the error was.

My guess would be that it was a MIME content type issue. When you post an MMS via NowSMS, NowSMS uses the file extension (e.g., ".jpg") to determine what MIME content type to specify.

NowSMS reads the file extension to content type mappings from the Windows registry ... or it also uses the MMSCTYPE.INI file.

Login Login / Register Logout Logout Search Last 30 Days Topics Topics