| Unknown content type upon MMS submit |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through June 02, 2011 ⬆ |
◄ ► |
| Author | Message | ||||
| linak New member Username: Linak Post Number: 1 Registered: 03-2010 |
Hello, We have implemented application that submits MM7 request, but we are failing to get successful response from NowSMS. We get the following response: 19:22:19:265 [2] SendCommand: HTTP/1.0 500 Internal Error 19:22:19:265 [2] SendCommand: Content-Type: text/html 19:22:19:265 [2] SendCommand: Connection: close 19:22:19:265 [2] SendCommand: Date: Mon, 01 Mar 2010 17:22:19 GMT 19:22:19:265 [2] SendCommand: Expires: Mon, 01 Mar 2010 17:22:19 GMT 19:22:19:265 [2] SendCommand: 19:22:19:265 [2] SendCommand: <HTML><HEAD><TITLE> 19:22:19:265 [2] SendCommand: Unknown Request 19:22:19:265 [2] SendCommand: </TITLE></HEAD><BODY><H1> 19:22:19:281 [2] SendCommand: Unknown request: content type is unknown 19:22:19:281 [2] SendCommand: </H1></BODY></HTML> Please see attached the request that we are sending
Can you tell what is the problem? Do you need anything else that might help you to help us? Thank you Lina | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1890 Registered: 08-2008 |
Hi Lina, The URL path must start with /mm7 to identify it as an MM7 request. Also, the next thing you'll have to do is identify yourself for authentication. The easiest way is to include the credentials in the URL /mm7/account=password, where "account" and "password" match an account defined in the "MMSC VASP" account list. -- Des NowSMS Support | ||||
| linak New member Username: Linak Post Number: 2 Registered: 03-2010 |
Thank you for fast response. We did all the above, see attached request:
Now we get the following response: HTTP/1.1 200 OK Content-Length: 599 Content-Type: text/xml <?xml version="1.0" ?> <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Header> <TransactionID xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2" env:mustUnderstand="1">unknown</TransactionID> </env:Header> <env:Body> <RSErrorRsp xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2"> <MM7Version>5.3.0</MM7Version> <Status> <StatusCode>4003</StatusCode> <StatusText>Unsupported Operation</StatusText> <Details>Invalid MIME boundary</Details> </Status> </RSErrorRsp> </env:Body> </env:Envelope> It seems that all the boundaries are there, do you see what is the problem? thank you Lina | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1891 Registered: 08-2008 |
Hi Lina, It is always confusing when you start a MIME boundary marker with "--". Your inner part MIME boundary is ok (the one that contains part12 in the boundary name). The outer part MIME boundary is not. I believe that you wanted 4 "-" characters in the first "boundary=" parameter. When the boundary marker appears in the content, it is always prefaced by an extra "--". This is difficult to explain. But hopefully that is clear enough. -- Des NowSMS Support | ||||
| linak New member Username: Linak Post Number: 3 Registered: 03-2010 |
It was, thanks you very much. Lina | ||||
