| MM7 400 Message Validation Failed |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 07, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| Lol New member Username: Lol Post Number: 1 Registered: 11-2008 |
Currently we are attempting to use the NOW.SMS as the MMS External Application to submit and receive MMS messages from and to the Operator’s MMSC using MM7 interface. I enable MMSCDEBUG.LOG. Mobile operator is return error "400 Message Validation Failed". How can you fix it? 14:37:09:750 [10] ThreadProcessVASPQ: POST /mm7/MMSServiceSOAPPort HTTP/1.1 Authorization: Basic xxxxxxxxxxxxxxxxx Host: 172.18.40.95:50504 SOAPAction: "" Content-Length: 1887 Content-Type: multipart/related; boundary="---mime-boundary-0EBB547D.20F03ABE---"; type="text/xml"; start="<mm7_msg>" Connection: close 14:37:09:750 [10] ThreadProcessVASPQ: -----mime-boundary-0EBB547D.20F03ABE--- Content-Type: text/xml; charset=utf-8 Content-ID: <mm7_msg> <?xml version="1.0" encoding="UTF-8"?> <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">20071101143709-B695623A@172.21.5.188</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>cellone</VASPID> <VASID>cellone</VASID> <SenderAddress><ShortCode>5050</ShortCode></SenderAddress> </SenderIdentification> <Recipients> <To> <Number>+xxxxxxxxxxxxx</Number> </To> </Recipients> <ServiceCode>50504</ServiceCode> <DeliveryReport>true</DeliveryReport> <ReadReply>true</ReadReply> <Priority>Normal</Priority> <Subject>mm7</Subject> <Content href="cid:mms_cid" /> </SubmitReq> </env:Body> </env:Envelope> -----mime-boundary-0EBB547D.20F03ABE--- Content-Type: multipart/related; start="<4725B493.smil>"; type="application/smil"; boundary="---mime-boundary-1EC7783B.66CD98FC---" Content-ID: <mms_cid> -----mime-boundary-1EC7783B.66CD98FC--- Content-Type: application/smil; name="4725B493.smil"; charset=utf-8 Content-ID: <4725B493.smil> Content-location: 4725B493.smil <smil> <head> <layout> <region id="Image" height="100%" width="100%" fit="meet"/> <region id="Text" height="100%" width="100%" fit="scroll"/> </layout> </head> <body> <par dur="3s"> <text src="4725B493.txt" region="Text"/> </par> </body> </smil> -----mime-boundary-1EC7783B.66CD98FC--- Content-Type: text/plain Content-ID: <4725B493.txt> Content-location: 4725B493.txt test de -----mime-boundary-1EC7783B.66CD98FC----- -----mime-boundary-0EBB547D.20F03ABE----- 14:37:09:765 [10] HttpResponseWait: Ok 14:37:09:765 [10] ThreadProcessVASPQ: mm7 - got unknown response 14:37:09:765 [10] ThreadProcessVASPQ: HTTP/1.1 400 Message Validation Failed x-nokia-mmsc-mm7-request-status: 2007 x-nokia-mmsc-mm7-request-status-text: Message format corrupt x-nokia-mmsc-version: 3.2 Content-Length: 0 | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 233 Registered: 08-2008 |
My first guess would be that maybe you are encountering a problem that we encountered with Vodafone UK (the problem has since been fixed by the provider of their MMSC, but it is possible that your operator has not gotten this update). http://blog.nowsms.com/2008/10/mms-mm7-soap-problems-with-vodafone-uk.html In this particular case, I think it was with a Nokia MMSC ... the MM7 implementation of the Nokia MMSC had a bug with MIME boundary handling, and a customer of ours did some further testing to discover a work-around. More details for this particular solution can be found in the link that I referenced above. If the above doesn't resolve your issue, then I am not sure why the MMSC is indicating that "message validation failed". There do not seem to be any flaws in the message structure. I would suggest verifying that the VASPID, VASID and ServiceCode values are correct for the way your account is provisioned on the MMSC. Additionally, I noticed that you are supplying a login name and password for the MM7 connection. According to the Nokia MM7 documentation that I have, the Nokia MMSC does not support this type of authentication (although it should ignore it). Another potential issue ... While the MM7 XML generated by NowSMS is perfectly legal, we have encountered some MM7 implementations in the past where the implementation was "quirky" and expected certain name space prefix values to use. Basically, they were following the examples in the MM7 specification and expecting it to match the example exactly, without realising that these prefixes were configurable within the XML. In particular, the Nokia MMSC might expect certain name space prefix values to be used ... which is not a requirement of the MM7 specification. Try this ... Edit the VASPOUT\MM7accountname\VASP.INI file, adding the following parameter settings under the [VASP] header of that file: NSSoapEnvelope=soapenv NSXMLSchema=xsd NSXMLSchemaInstance=xsi NSMM7TransactionID=ns1 This is an example default MM7 SOAP envelope header generated by NowSMS with default settings: <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">20071102120921-A4D2CC3B@bigkahuna</TransactionID> </env:Header> This is an example MM7 SOAP envelope header that would be generated with the settings that I gave you above: <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="1" xmlns:ns1="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2">20071102120643-A1231342@bigkahuna</ns1:TransactionID> </soapenv:Header> <soapenv:Body> Our default syntax is consistent with the 3GPP MM7 specification. But I took a look at Nokia's MM7 documentation, and this latter example more closely matches the examples provided in Nokia's MM7 documentation, so it might be possible that they might require these specific name space settings. That's a lot of different things to try. Hopefully the first suggestion resolves your issue. -- Des NowSMS Support | |||
