| MMS Post via SOAPUI to ISG to NowSMS |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 09, 2011 ⬆ |
◄ ► |
| Author | Message | |||
| Dinesh New member Username: Dbirlase Post Number: 1 Registered: 05-2010 |
Hi, We are trying to Interface sending MMS via the MM7. MM7 Schema is REL-6-MM7-1-0 3GPP MMS Version is 6.3.0 when i try to send to nowsms, I see that the nowsms doesn't recognize this. <HTML><HEAD><TITLE> Unknown Request </TITLE></HEAD><BODY><H1> Unknown request: content type is unknown </H1></BODY></HTML> On the ISG platform where i am sending this via SOAP, i get this. When i enable the wireshark, and see what is going on, i get a unknown request from the nowsms. May 17, 2010 1:24:26 AM com.lucent.isg.parlayx.mms.utils.MMSException convertAxisFault INFO: faultMsg:[First Element must contain the local name, Envelope , but found HTML] May 17, 2010 1:24:26 AM com.lucent.isg.parlayx.mms.protocol.mm7.MMSCNENode putMsg FINE: this mm7 message failed for mmsc: mmsc3 May 17, 2010 1:24:26 AM com.lucent.isg.parlayx.mms.protocol.mm7.MMSCNENode putMsg() FINER: RETURN I have read the nowsms, and saw that Also note that the MM7 XML portion of the document (the first part of the main multipart content) should not use any Content-Transfer-Encoding, it should always be expressed without any encoding. For the portion of the document that includes the MMS content itself, you can use Content-Transfer-Encoding of either quoted-printable or base64, or no encoding can be specified in which case it is assumed that the binary data is to be included as is. But according to the RFC, the way we send the MMS is correct. Just the Nowsms is not able to understand the request. Below is the sample output from the when we sent a Soap request via the ISG via a MMS Simulator. POST / HTTP/1.1 Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_0278FA78E3FEC186E21274071792416; type="text/xml"; start="<0.urn:uuid:0278FA78E3FEC186E21274071792417@apache.org>" SOAPAction: "" User-Agent: Axis2 Host: 10.165.48.37:40009 Content-Length: 301535 --MIMEBoundaryurn_uuid_0278FA78E3FEC186E21274071792416 Content-Type: text/xml; charset=UTF-8 Content-Transfer-Encoding: 8bit Content-ID: <0.urn:uuid:0278FA78E3FEC186E21274071792417@apache.org> <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header><TransactionID xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-0" xmlns:axis2ns3="http://schemas.xmlsoap.org/soap/envelope/" axis2ns3:mustUnderstand="1">TID-15334947332</TransactionID></soapenv:Header><soa penv:Body><SubmitReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-0"><MM7Version>6.3.0</MM7Version><SenderIdentification><VASPID>P1000001</VASPID>< VASID>P1000001#A1#C1</VASID><SenderAddress><ShortCode>12580</ShortCode></SenderA ddress></SenderIdentification><Recipients><To><Number>6592962676</Number></To></ Recipients><ServiceCode>01</ServiceCode><DeliveryReport>true</DeliveryReport><Re adReply>false</ReadReply><Priority>High</Priority><Subject>Dinesh-hello word</Subject><DistributionIndicator>false</DistributionIndicator><Content href="cid:urn:uuid:0278FA78E3FEC186E21274071792396" allowAdaptations="true" /></SubmitReq></soapenv:Body></soapenv:Envelope> --MIMEBoundaryurn_uuid_0278FA78E3FEC186E21274071792416 Content-Type: multipart/mixed; boundary="----=_Part_1_2000721638.1274071792192" Content-Transfer-Encoding: binary Content-ID: <urn:uuid:0278FA78E3FEC186E21274071792396> ------=_Part_1_2000721638.1274071792192 Content-Type: image/jpeg Content-ID: 001 Content-Disposition: attachment; filename=MyByteArrayDataSource I get a error code on my client, which says the MMSC return doesn't not recognize by the nowsms. PXMMS-004 Error response The result code indicates that the MMSC return some response cannot be recognized as a MM7_submit.RES or RSError Is there any RFC limitation or a bug? http://www.ietf.org/rfc/rfc2046.txt Dinesh. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2128 Registered: 08-2008 |
Hi Dinesh, Please see http://www.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_c ontent/Submitting_MMS_Messages_MM7.htm If you post to "/", then MM1 content is expected. If you are posting MM7, the URI needs to start with "/mm7". If you do not include an "Authorization:" header to identify the user (or create an "MMSC VASP" account with an IP address as its name), then you also need to include "MMSC VASP" credentials in the URI like this: "/mm7/account=password". -- Des NowSMS Support | |||
| Dinesh New member Username: Dbirlase Post Number: 2 Registered: 05-2010 |
thanks des, i tried to post direct to the nowsms with the /mm7 and it works. | |||
