| Problem with submiting message |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| Maep New member Username: Maep Post Number: 1 Registered: 02-2006 |
Hi guys, i have a huge problem with MMS. Situation is the following: i send MMS by nowSMS to the url (my page). Page returns a response, but nowSMS is not satisfied by my response, so it send messages again and again. This is a message, that i get: -----mime-boundary-009FD24F.09844A10--- Content-Type: text/xml; charset=utf-8 Content-ID: <mm7_msg> <?xml version='1.0' ?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <SOAP-ENV:Header> <MM7Header SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:xml-MM7Header"> <Transaction-ID xsi:type="xsd:string"> 20060313133147-4846A54E@localhost </Transaction-ID> </MM7Header> </SOAP-ENV:Header> <SOAP-ENV:Body> <MultiMediaSubmit SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns="urn:MM7Submit.Req"> <Version xsi:type="xsd:string">1</Version> <Message-Type xsi:type="xsd:string">MM7Submit.Req</Message-Type> <VASP-ID xsi:type="xsd:string">777</VASP-ID> <VAS-ID xsi:type="xsd:string">777</VAS-ID> <Recipient Recipient-Type="TO" xsi:type="xsd:string">11111/TYPE=PLMN</Recipient> <Priority xsi:type="xsd:string">Normal</Priority> <Delivery-Report xsi:type="xsd:boolean">False</Delivery-Report> <Read-Reply xsi:type="xsd:boolean">False</Read-Reply> <Subject xsi:type="xsd:string">11111</Subject> </MultiMediaSubmit> </SOAP-ENV:Body> </SOAP-ENV:Envelope> -----mime-boundary-009FD24F.09844A10--- Content-Type: multipart/mixed; boundary="---mime-boundary-F4F79C91.B34959D2---" Content-ID: <mms_cid> this is my response: <?xml version='1.0' ?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema"> <SOAP-ENV:Header> <mm7:TransactionID xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-3" env:mustUnderstand="1"> 20060313133147-4846A54E@localhost </mm7:TransactionID> </env:Header> <env:Body> <MultiMediaSubmitResponse xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-3"> <MM7Version>5.3.0</MM7Version> <Message-Type xsi:type="xsd:string">MM7Submit.RES</Message-Type> <Status> <StatusCode>1000</StatusCode> <StatusText>Success</StatusText> </Status> </MultiMediaSubmitResponse> </env:Body> </env:Envelope> Where am i mistaken? Thank you so much in advance | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5636 Registered: 10-2002 |
It might help to enable the MMSCDEBUG.LOG in NowSMS, to see what NowSMS is seeing. Are you including an HTTP header in the response? At a minimum, you need: HTTP/1.1 200 OK Content-type: text/xml (blank line) XML data here And actually, we don't require the "Content-type" header in this particular case, but it's a good idea to include it. The only case that I could see where the message would continue to be retried would be if we're not getting a valid HTTP header. Also, it looks like you're using the Ericsson MM7 format. Or actually mixing Ericsson MM7 and standard MM7 in the response. But NowSMS is using Ericsson MM7 format in its submission. In this case, I would suggest including a <Message-ID> field in the response, otherwise NowSMS will think that the request failed. (NowSMS won't retry, but it will mark it in the logs as failed.) -bn | |||
| Maep New member Username: Maep Post Number: 2 Registered: 02-2006 |
Hi Bryce, yes, i don't forget about header  Actually, it looks like that: HTTP/1.1 200 OK Server: Microsoft-IIS/5.1 Date: Fri, 10 Mar 2006 12:51:58 GMT X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Connection: close Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 897 about <Message-ID>... what data should i put inside? I don't see any message_id in request... | |||
| Maep New member Username: Maep Post Number: 3 Registered: 02-2006 |
In log i see following: 09:12:21:644 [7] HttpResponseWait: Ok 09:12:21:644 [7] ThreadProcessVASPQ: mm7 - got unknown response 09:12:21:644 [7] ThreadProcessVASPQ: HTTP/1.1 100 Continue Server: Microsoft-IIS/5.1 Date: Tue, 14 Mar 2006 02:12:21 GMT X-Powered-By: ASP.NET | |||
| Maep New member Username: Maep Post Number: 4 Registered: 02-2006 |
And i think it's interesting to know, that using standart response (no ericsson things) <?xml version="1.0" ?> <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-3" env:mustUnderstand="1"> 20060314094933-0B7E7511@localhost </mm7:TransactionID> </env:Header> <env:Body> <SubmitRsp xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-3"> <MM7Version>5.6.0</MM7Version> <Status> <StatusCode>1000</StatusCode> <StatusText>Success</StatusText> </Status> <MessageID>041502073667</MessageID> </SubmitRsp> </env:Body> </env:Envelope> causes the same error (got unknown response) | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5649 Registered: 10-2002 |
It's the "HTTP/1.1 100 Continue" response that is causing the problem. That has me a little confused. We should be handling that ok. But apparently we are not. Is it possible for you to capture an Ethereal trace, so that I can see the raw data and try to figure out what is different about this particular "100 Continue" response? Also, I should probably ask what version of NowSMS is being used. v5.51 and later should be ok with the "100 Continue" response, but earlier versions might not be. | |||
| Maep New member Username: Maep Post Number: 5 Registered: 02-2006 |
Hi Bryce,i/ve got v5.51 version. I'm not able to capture Etherial trace, cause for some unknown reason it refuses to capture localhost-to-localhost traffic:\ | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5662 Registered: 10-2002 |
Give the v5.51k update a try to see if it makes any difference. It's a ZIP file that can be downloaded from http://www.nowsms.com/download/latestpatch.zip Meanwhile, I'll attempt to recreate an MM7 scenario that involves an "HTTP/1.1 100 Continue" scenario and hope I can easily recreate the problem. -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5663 Registered: 10-2002 |
Ok, I just ran a test here with a server that generated "HTTP/1.1 100 Continue" responses. I didn't have any problems. But, in reviewing changes between v5.51 and v5.51k, I can see where v5.51 might not handle this reponse properly. So, I'd suggest the patch that I mentioned above. -bn | |||
