Delivery Report Error | Search |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 19, 2007 ⬆ |
◄ ► |
Author | Message | |||
R. Fuertes New member Username: Rfuertes Post Number: 1 Registered: 05-2007 |
Hello All When we recieve an mms delivery report (mm7), nowsms is loggin an error. Here's the log, can you see what's wrong?. (private data changed manually) Thanks in advance. The POST we receive: POST / HTTP/1.1 TE: deflate,gzip;q=0.3 Connection: TE, close Authorization: Basic dGVzdDp0AAA Host: xx.xxx.xxx.xxx:11111 User-Agent: libwww-perl/5.803 Content-Length: 970 Content-Type: text/xml; charset="utf-8" SOAPAction: "" <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Header> <ns1:TransactionID soapenv:mustUnderstand="0" xsi:type="xsd:string" xmlns:ns1="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2">20070530190215-BF9012CB@xxx.xx.xx.xx </ns1:TransactionID> </soapenv:Header> <soapenv:Body> <DeliveryReportReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2"> <MM7Version>5.3.0 </MM7Version> <MessageID>34666666666-5DB008ECA33 </MessageID> <Recipient> <Number displayOnly="false">34666666666 </Number> </Recipient> <Sender> <ShortCodedisplayOnly="false">5555 </ShortCode> </Sender> <Date>2007-05-30T19:10:32 </Date> <MMStatus>SPOOLED </MMStatus> <StatusText>1000/SPOOLED </StatusText> </DeliveryReportReq> </soapenv:Body> </soapenv:Envelope> Nowsms ERROR: 19:04:02:692 [11] SendCommand: HTTP/1.0 500 Internal Error 19:04:02:692 [11] SendCommand: Content-Type: text/html 19:04:02:692 [11] SendCommand: Connection: close 19:04:02:692 [11] SendCommand: Date: Wed, 30 May 2007 17:04:02 GMT 19:04:02:692 [11] SendCommand: Expires: Wed, 30 May 2007 17:04:02 GMT 19:04:02:692 [11] SendCommand: 19:04:02:692 [11] SendCommand: <HTML><HEAD><TITLE> 19:04:02:692 [11] SendCommand: Unknown Request 19:04:02:692 [11] SendCommand: </TITLE></HEAD><BODY><H1> 19:04:02:692 [11] SendCommand: Unknown request: content type is unknown 19:04:02:692 [11] SendCommand: </H1></BODY></HTML> 19:04:02:692 [11] ThreadProcessConnection: Processing Complete | |||
R. Fuertes New member Username: Rfuertes Post Number: 2 Registered: 05-2007 |
Any comments? at least you can say "this won't work anymore" and I can take a decision and change the software if it's necessary thank | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7155 Registered: 10-2002 |
Hi, I don't understand the transaction flow of the example above. I assume that MM7 is being posted to NowSMS, and you have posted the raw HTTP POST here? If that is the case, then the problem is that when posting MM7 to the MMSC, you must have /MM7 in the POST URL. If you do not, then it is assumed to be an MM1 request, hence the error about the content type being unknown. -bn | |||
R. Fuertes New member Username: Rfuertes Post Number: 3 Registered: 05-2007 |
ok I'll check it. thanks |