Fail to receive mms from operator Unknown request: content type is...

Fail to receive mms from operator Unknown request: content type is... SearchSearch
Author Message
sokha
New member
Username: Sokha

Post Number: 1
Registered: 06-2011
Posted on Friday, June 17, 2011 - 06:10 am:   

Dear All,

below is log from wiresark

POST http://192.168.xxx.191:8088/mm7 HTTP/1.1
Host: 192.168.xxx.191:8088
Connection: Keep-alive
soapAction: ""
x-mmsc-msg-from: mm7
content-length: 1527
Mime-Version:1.0
Content-Type:multipart/related;type="text/xml";start="<1.xml>";boundary="------- -------------------------------------=_NextPart_0_24856"

this is a multi-part message in MIME format.

----------------------------------------------=_NextPart_0_24856
Content-Type:text/xml;charset=UTF-8; name=1.xml
Content-Transfer-Encoding:8bit
Content-Location:1.xml
Content-ID:<1.xml>

<?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header><mm7:TransactionID xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2" env:mustUnderstand="1">YQO000sBu5S0</mm7:TransactionID></env:Header><env:Body><D eliverReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2"><MM7Version>5.3.0</MM7Version><Recipients><To><Number>1000</Number></To></Reci pients><MMSRelayServerID>925000</MMSRelayServerID><Sender><Number>12345678901</N umber></Sender><TimeStamp>2011-06-17T10:46:44+07:00</TimeStamp><Priority>Low</Pr iority><Subject>Tedt</Subject></DeliverReq></env:Body></env:Envelope>

----------------------------------------------=_NextPart_0_24856
Content-Type:multipart/mixed;boundary="Sub1------------------------------------- -------=_NextPart_0_24856"
Content-ID:multipart

--Sub1--------------------------------------------=_NextPart_0_24856
Content-Type:text/plain;charset=UTF-8; name=1.xml
Content-Transfer-Encoding:8bit
Content-Location:1.xml
Content-ID:<1.xml>

Original MMS is empty or corrupt!

--Sub1--------------------------------------------=_NextPart_0_24856--

----------------------------------------------=_NextPart_0_24856--
HTTP/1.0 500 Internal Error
Content-Type: text/html
Connection: close
Date: Fri, 17 Jun 2011 05:05:45 GMT
Expires: Fri, 17 Jun 2011 05:05:45 GMT

<HTML><HEAD><TITLE>
Unknown Request
</TITLE></HEAD><BODY><H1>
Unknown request: content type is unknown
</H1></BODY></HTML>


what is actually wrong?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3269
Registered: 08-2008
Posted on Saturday, June 18, 2011 - 02:10 am:   

Hi sokha,

The NowSMS MMSC is confused because the "POST" URI in the HTTP packet is an absolute URL:

POST http://192.168.xxx.191:8088/mm7 HTTP/1.1
Host: 192.168.xxx.191:8088

The MMSC expects a relative URI:

POST /mm7 HTTP/1.1
Host: 192.168.xxx.191:8088

Normally, an absolute URL is only present if the submission is occurring via an HTTP Proxy (and in this case, there is no "Host:" header).

If you can change the MM7 request to use a relative URI, this will fix the problem.

If this is outside of your control, we will release an update next week to allow an absolute URL in the HTTP POST request. (The HTTP 1.1 spec says that servers MUST support this format, but that clients should not generate this format.) The MMSC already supports both formats for MM1 submissions, but not for MM7.

I expect an update to be available by Wednesday, June 22.

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3277
Registered: 08-2008
Posted on Monday, June 20, 2011 - 09:47 pm:   

Follow-up: An update to address this issue where the MMSC will not accept MM7 HTTP POST if an absolute URL format is used in the raw POST is available at http://www.nowsms.com/download/nowsms20110620.zip

Note that while the HTTP specification says that an HTTP server MUST accept a POST with an absolute URL in the raw POST, it also says that an HTTP client SHOULD NOT use an absolute URL unless connecting via an HTTP proxy.

--
Des
NowSMS Support