MM7 message format | Search |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through May 02, 2013 ⬆ |
◄ ► |
Author | Message | |||
samir New member Username: Samirprogrammer Post Number: 2 Registered: 02-2011 |
Strage Same format but diffrent xml::: Required format: <?xml version='1.0' ?> <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/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"> vas00001-sub </mm7:TransactionID> </env:Header> <env:Body> <mm7:SubmitReq xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0"> <MM7Version>5.3.0</MM7Version> <SenderIdentification> <VASPID>xxxx</VASPID> <VASID>xxxx</VASID> <SenderAddress> <ShortCode>1234</ShortCode> </SenderAddress> </SenderIdentification> <Recipients> <To> <Number>xxxxxxxxxxxx</Number> </To> </Recipients> <MessageClass>Informational</MessageClass> <DeliveryReport>True</DeliveryReport> <Priority>Normal</Priority> <Subject>logo</Subject> </mm7:SubmitReq> </env:Body> </env:Envelope> ------------------------------------ --------------------------------- Now SMS Format <?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-0" env:mustUnderstand="1">20110823125211-967FA5B2-x40x-localhost</TransactionID> </env:Header> <env:Body> <SubmitReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0"> <MM7Version>5.3.0</MM7Version> <SenderIdentification> <VASPID>xxxx</VASPID> <VASID>xxx/VASID> <SenderAddress>xxxx</SenderAddress> </SenderIdentification> <Recipients> <To> <Number>xxxxxxxxxxxxx</Number> </To> </Recipients> <DeliveryReport>True</DeliveryReport> <ReadReply>True</ReadReply> <Priority>Normal</Priority> <Subject>mms</Subject> <Content href="cid:mms_cid" /> </SubmitReq> </env:Body> </env:Envelope> PLZZZ HElp!!!!!!!! | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3461 Registered: 08-2008 |
Hi, I see only one difference of any significance. Your first example has this: <SenderIdentification> <VASPID>xxxx</VASPID> <VASID>xxxx</VASID> <SenderAddress> <ShortCode>1234</ShortCode> </SenderAddress> The second example from NowSMS has this: <SenderIdentification> <VASPID>xxxx</VASPID> <VASID>xxx/VASID> <SenderAddress>xxxx</SenderAddress> </SenderIdentification> The first example is not valid according to the MM7 schema being used: http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0 If you refer to that schema, you will find that the SenderAddress element is defined as type xs:string. The first example would be valid if the MM7 schema was changed to http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2 If you refer to the REL-5-MM7-1-2 schema, you'll see that SenderAddress element is defined as type tns:addressType. NowSMS decides how to format the MM7 data based upon the MM7 schema version that is being used. If you configure NowSMS to use the REL-5-MM7-1-0 schema, it will generate: <SenderIdentification> <VASPID>xxxx</VASPID> <VASID>xxx/VASID> <SenderAddress>xxxx</SenderAddress> </SenderIdentification> If you change the NowSMS configuration to use the REL-5-MM7-1-2 schema, it will generate: <SenderIdentification> <VASPID>xxxx</VASPID> <VASID>xxxx</VASID> <SenderAddress> <ShortCode>1234</ShortCode> </SenderAddress> There are subtle differences between different MM7 schema versions, and NowSMS generates slightly different formats depending on the restrictions of the schema being used. -- Des NowSMS Support | |||
samir New member Username: Samirprogrammer Post Number: 4 Registered: 02-2011 |
Dear Des, Thanks i tried that also but not working i think Diffrence is below -----Requered----- <mm7:TransactionID xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0" env:mustUnderstand="1"> vas00001-sub </mm7:TransactionID> </env:Header> <env:Body> <mm7:SubmitReq ---------------- Now SMS format <TransactionID xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0" env:mustUnderstand="1">20110823125211-967FA5B2-x40x-localhost</TransactionID> </env:Header> <env:Body> <SubmitReq xmlns}} | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3468 Registered: 08-2008 |
Maybe we should backup and ask what the error is that you are receiving? It may have nothing to do with MM7. From an XML standpoint, those two different ways of saying the same thing. What is the error that you are seeing? -- Des NowSMS Support | |||
samir New member Username: Samirprogrammer Post Number: 5 Registered: 02-2011 |
Below error i m recieving 15:22:41:953 [9] HttpResponseWait: Ok 15:22:41:953 [9] ThreadProcessVASPQ: mm7 - got unknown response 15:22:41:953 [9] ThreadProcessVASPQ: HTTP/1.1 500 Internal Server Error Date: Sat, 10 Sep 2011 11:21:05 GMT Server: Jetty/5.1.8 (SunOS/5.10 x86 java/1.6.0_14 Connection: close Content-Type: text/xml; charset="utf-8" Content-Length: 400 <?xml version="1.0" encoding="UTF-8"?> <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"><soap-env:Body><soap-env:Fault><faultcode>Client</faultcode><faultstring>Reque st processing error.</faultstring><detail><Status><StatusCode>4004</StatusCode><StatusText>Cou ld not access SOAP headers.</StatusText></Status></detail></soap-env:Fault></soap-env:Body></soap-e nv:Envelope> | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3471 Registered: 08-2008 |
Ok Samir, It should not make a difference, but let's try the issue of "SubmitReq" vs. "mm7:SubmitReq". They should be syntactically equivalent as long as the correct "xmlns" is present. However, maybe this receiving system does not understand. An updated version of NowSMS is at http://www.nowsms.com/download/nowsms20110912.zip After installing this update, edit VASPOUT\outboundroutename\VASP.INI Under the [VASP] header, add: NSMM7=mm7 This setting will cause NowSMS to prefix "SubmitReq" with "mm7:" Please let me know how this affects the problem. -- Des NowSMS Support |