| NowSMS/MMS Gateway Responses vs my operator's mms responses |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through March 23, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Khwezi Mngoma New member Username: Nexus Post Number: 4 Registered: 11-2003 |
I have been cracking my head over this problem, and I just can't seam to understand what is wrong. Please see the MMS output below: Note*: I used the NowSMS MMS Message example as my starting point, I am sure you will find a lot of similarities. Content-Type: multipart/related; boundary="NextPart_000_0028_01C19839.84698430"; type=text/xml; start="</SoapSectionStartEFF001CC>" Content-Length: n SOAPAction: "" --NextPart_000_0028_01C19839.84698430 Content-Type: text/xml; charset='utf-8' Content-ID: </SoapSectionStartEFF001CC> <?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-M M7-1-3" env:mustUnderstand="1">Replace</mm7:TransactionID> </env:Header> <env:Body> <SubmitReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1 -3"><MM7Version>5.6.0</MM7Version><SenderIdentification><VASPID>Replace</VASPID> <VASID>Replace</VASID></SenderIdentification><Recipients><To><Number>Replace</Nu mber></To></Recipients><ServiceCode>Replace</ServiceCode><LinkedID>Replace</Link edID><MessageClass>Replace</MessageClass><TimeStamp>Replace</TimeStamp><Earliest DeliveryTime>Replace</EarliestDeliveryTime><ExpiryDate>Replace</ExpiryDate><Deli veryReport>Replace</DeliveryReport><Priority>Replace</Priority><Subject>Replace< /Subject><ChargedParty>Replace</ChargedParty><DistributionIndicator>Replace</Dis tributionIndicator><Content href="cid:CCDDFF0.705547541CA@mig.co.za" allowAdaptations="replace" /></SubmitReq> </env:Body> </env:Envelope> --NextPart_000_0028_01C19839.84698430 Content-Type: multipart/mixed; boundary=StoryParts-74526-8432-2002-77645 Content-ID: <CCDDFF0.705547541CA@mig.co.za> --StoryParts-74526-8432-2002-77645 Content-Type: text/plain; charset='us-ascii' This is a test mms message (Text Only) --StoryParts-74526-8432-2002-77645-- --NextPart_000_0028_01C19839.84698430-- ***********************************************************Responses NowSMS/MMS Response ******************** <?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-0" env:mustUnderstand="1"> Replace </mm7:TransactionID> </env:Header> <env:Body> <mm7:SubmitRsp xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0"> <MM7Version>5.3.0</MM7Version> <Status> <StatusCode>1000</StatusCode> <StatusText>Success</StatusText> </Status> <MessageID>20031222/11/71000C0E@khwezi</MessageID> </mm7:SubmitRsp> </env:Body> </env:Envelope> ********************** My Operator's Response ********************** <?xml version='1.0' ?> <E:Envelope xmlns:E="http://schemas.xmlsoap.org/soap/envelope/" xmlns:s="http://www.w3.org/2001/XMLSchema-instance" xmlns:y="http://www.w3.org/2001/XMLSchema"> <E:Header> <ns1:TransactionID xmlns:ns1="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0">45e044:f99c7d53e2:-8000pravin-pc/172.16.129.52</ns1:TransactionID> </E:Header> <E:Body> <E:Fault> <faultcode>Client</faultcode> <faultstring>malformed message</faultstring> <detail> <RSErrorRsp> <MM7Version>5.3.0</MM7Version> <Status> <StatusCode>4004</StatusCode><StatusText>malformed message</StatusText><Details>malformed MIME message: start boundary not found</Details> </Status> </RSErrorRsp> </detail> </E:Fault> </E:Body> </E:Envelope> Mow, here is the jist of the matter, why is the preceding different from each other, why are they processing the message differently if the 3GPP and MM7 standards are there to help avoid these things. I am in distress because this is the only thing that is standing between me and my first MMS message. Please help me solve this problem. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1484 Registered: 10-2002 |
Have you tried having NowSMS generate the MM7 request to your operator? (If you do, try with our latest patches at http://www.nowsms.com/download/nowsms5-patch4.zip, as a few MM7 related problems were fixed.) These are early days for MM7 ... and basically, there are a lot of interoperability issues and quirks of different implementations at present. My advice would be to simplify and experiment. Don't include so many headers in your submission ... also, include line breaks in case that is a problem. | |||
