MM7 Message Correct?

MM7 Message Correct? SearchSearch
Author Message
Anonymous
 
Posted on Monday, May 16, 2005 - 04:38 pm:   

I am having problems with the following MM7 5.5.0 message but I can't see any problems with the format! Can someone verify this?

POST / HTTP/1.1
Content-Type: multipart/related; boundary="----=_Part_4_23637981.1115989991245"
SoapAction: ""
User-Agent: Java/1.4.2_07
Host: 127.0.0.1:100
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
Content-Length: 1114


------=_Part_4_23637981.1115989991245
CONTENT-TYPE: text/xml; charset="UTF-8"
CONTENT-TRANSFER-ENCODING: 8BIT

<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header><mm7:Transacti onID xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-M M7-1-2">2</mm7:TransactionID></env:Header><env:Body><SubmitReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1 -2"><MM7Version>5.3.0</MM7Version><SenderIdentification><VASPID>MMStool</VASPID> <VASID>1234</VASID><SenderAddress><Number>1234</Number></SenderAddress></SenderI dentification><Recipients><To><Number>0123456789</Number></To></Recipients><Subj ect>test</Subject><ExpiryDate>2005-05-13T14:43:11</ExpiryDate><DeliveryReport>tr ue</DeliveryReport><Priority>Normal</Priority><Content href="cid:3d63afb18000003"/></SubmitReq></env:Body></env:Envelope>

------=_Part_4_23637981.1115989991245
CONTENT-TYPE: text/plain; charset="UTF-8"
CONTENT-TRANSFER-ENCODING: 8BIT
CONTENT-ID: <3d63afb18000003>

test
------=_Part_4_23637981.1115989991245--
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4512
Registered: 10-2002
Posted on Monday, May 16, 2005 - 06:58 pm:   

I suspect the bulletin board software here put some unexpected line breaks and white space into your XML above.

What is the error that you get back?

What server are you posting to? (If you're posting to the NowSMS MMSC, you need to include "/mm7" in your URL, and post to the HTTP port of the MMSC.)

One minor thing to note ... MMS content is usually multipart, so most MMSCs will expect your "text/plain" part to be a "multipart/related" part.